PDA

View Full Version : .621 -> flashed liberty3 v2.0 and now I cant get into CWM Bootstrap RECOVERY



ezrollin
01-18-2013, 12:40 PM
I updated from .596 -> .605 then finally to .621 via OTA (NO ROM)
Everything was working great in .621 then I downloaded the Liberty3 v2.0 ROM from my ROM Toolbox utility.
I tried to install Liberty3 v2.0 from within my ROM Toolbox and it wouldnt let me.
I had to go into ClockworkMOD Reboot Recovery to install the .zip and it wouldnt boot up anymore... couldnt even get it to boot up!
I tried to flash the only update SBF file I had which was .605 now my Bootloader is messed up too!
The bootloader says:
v30.04
Err: A5,70,70,00,00 (those are zeros)

MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Connect USB data cable

Did I brick?? HELP Please!!! Thanks!

P.S. I have .605 clockworkmod backups and one .621 CWM backup but I just cant get to my CWM recovery to load it! :(

GoCliffGo05
01-18-2013, 01:08 PM
You'll need to SBF with the .621 file using RSD Lite. Once on .621 you can't go back to previous versions. That's why your BL says mem pack blank. The file, along with a guide can be found in my signature.

Sent from my DROID RAZR HD using Xparent Cyan Tapatalk 2

Goose306
01-18-2013, 09:09 PM
Also the link in my sig for Blur ROMs on 621 is where you want to go if you do want to run Liberty its patched to work on it.

Tapped from my 4.2 jelly-beaned d2vzw using tapatalk HD

ezrollin
01-19-2013, 09:29 AM
I think that trying to SBF from .621 -> .605 was what really screwed it up.
If I flash .605 it says MEM_MAP blank and fails, if I try flashing .621 the bootloader now says "Code is corrupt" and fails
I've tried flashing .605 = 3 times and .621 8 times but nothing ever works.
I cant ever get past the BROKEN BOOTLOADER
RSD Lite runs fine until it gets to the: "Switching to BP Pass" then "Loading RAM downloader for bootloader" part it gets to 98%, then hangs forever, then comes up with a FAIL
The fail says: "Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F address: 0x174000 command: ADDR (0xE023203F)"
Do I need to be using ADB? I dont know of that program yet
Dont I need to flash a new copy of Bootloader 30.04 before I can do ANYTHING? thanks!!!

ezrollin
01-19-2013, 01:38 PM
Hm whats the difference between this 7z (7zip?) .621 update here: 602 SBF - Droid X - RootzWiki (http://rootzwiki.com/topic/17934-602-sbf/) file name: "621.sbf.7z" its 157 MB
BUT
the .621 GZ (gzip?) found here: xda-developers - View Single Post - [SBF and Update] Original Gingergread 2.3.4 SBF for Droid X MB810 Verizon USA (http://forum.xda-developers.com/showpost.php?p=22982080&postcount=1) file name: "1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US.sbf.gz" is 184 MB maybe I should try flashing the 7z instead?


new copy of the download worked!!!! thanks!!

GoCliffGo05
01-19-2013, 01:47 PM
If you are on Verizon grab the 621 file from the "x sbf files" link in my signature. Its the file at the bottom of the list, its the right one.

Sent from my DROID RAZR HD using Xparent Cyan Tapatalk 2

Goose306
01-19-2013, 06:37 PM
All you should need to do is flash the SBF. The boot loader is fine. You still have the original bootloader regardless and 621 and 605 share the same bootloader. What changed is the cdt table, or the mem_map. That's why 605 gives you that error as signature check fails on flashing the cdt table from 605 and so the device can't validate partition signatures. Flashing the 621 will unbrick it though. I would redownload the 621 sbf file, and also make sure you are using the correct version of RSD Lite and drivers.

Tapped from my 4.2 jelly-beaned d2vzw using tapatalk HD

ezrollin
01-19-2013, 08:11 PM
In conclusion, I think it was just a bad download of the .621 SBF file from my droid X (I didnt check MD5s)
after getting a download manager, it downloaded correctly and worked
Now I guess its the same thing for that Liberty3 v2.0 mod, just a bad download I presume...? I'm scared to try again (might be a waste of time)

Goose306
01-20-2013, 08:36 AM
In conclusion, I think it was just a bad download of the .621 SBF file from my droid X (I didnt check MD5s)
after getting a download manager, it downloaded correctly and worked
Now I guess its the same thing for that Liberty3 v2.0 mod, just a bad download I presume...? I'm scared to try again (might be a waste of time)

It was the version of Liberty you downloaded... See my post a few posts up to get the correct version for the 621 system version

Tapped from my 4.2 jelly-beaned d2vzw using tapatalk HD