• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Stuck at Bootloader :(

Vihzel

Vihzel

Destroying Balls Everyday
I'm stuck at the bootloader with Err: A5,70,39,00,27 and don't know what to do now.

I don't think I did anything wrong with flashing. I was basically trying to unroot my phone with system 2.3.13 to stock froyo. It said "PASS" in RSD Lite with 2.2 System Only SBF and unplugged my phone and rebooted. Now it keeps sending me to bootloader. I try holding down home + power but it keeps sending me to bootloader.

I've spent the last 4 hours trying to bring my phone back to stock 2.2 from rooted 2.2...

Anything I can do to get out of this?

Added info: My system was on 2.3.13. Am I able to flash the 2.3.13 sbf to get me out of this?
 
Googled your Err code and brought me to this thread over at DF. It looks like the kid flashed the wrong SBF to his phone. Are you sure you were on 2.2 ie 2.3.15 or 2.2.1 (2.3.320 or 2.3.340)? I would suggest re-flashing it and/or dl'ing a new copy that's compatible with what version of android you were on.

Edit: yes, you will need to flash that SBF file. Your bootloader version should be 30.01, yes?

I would SBF back to .13 and then use this to get to .320 then use the newest SBF to get your system to .340.
 
I was on 2.3.13. I don't exactly remember how I got 2.3.13. I was flashing the 2.2 System Only file from TBH, thinking that it would unroot my phone. I think I flashed the wrong SBF. Can I only go up to 2.3.320?
 
You can't SBF to get from .13 to .320 it won't update your MBM or your baseband/kernal. you'll have to SBF to get back to normal and use the update.zip I posted.
 
Also keep in mind that my bootloader says 30.01. I don't know if that makes a difference. I saw someone else say on a diff forum that I can flash back to 2.1. Is that possible?
 
If you can flash the maderstock.zip file from the bootloader that would be the easiest route to 2.3.340. Put the file on your sd card and rename it update.zip

However, some have said renaming the file causes md5 checksum errors, so since you can only get into bootloader, you might have to go the sbf route.
 
I'm not sure. The worst thing that would happen is what you are experiencing now where you will have to flash the correct SBF to recover. And you'll more than likely need a full sbf not just a system since your phone needs to recover from bad flash.

edit: ... you can't flash an update.zip from the bootloader. . unless i'm missing something. SBF is the only way to recover from this.
 
Something that I read on a different thread on this site is that since I am on the leaked version of Froyo (2.3.13) and because my bootloader didn't update from 30.01 (correct me if I'm wrong), then I can safely go back to 2.1.604without bricking my phone. I am going to try that method. I hope the person who said that is RIGHT! I've read that people who OTA updated to Froyo and tried to go back to the 2.1.604 SBF were bricked.
 
he's on 2.3.13 and his bootloader is 30.01, so I'm having him upgrade to 2.3.15. Hopefully that will work and he can then go to 2.3.340 by either sbf or ota.
 
why don't you get him to get on .340 by the update.zip I posted. to me that would seem faster than waiting for it to download OTA. And if you went to .340 via SBF he'll still have to flash the .zips xliderider posted to update everything else.
just my 0.02
 
Thank you guys so much for all of your assistance! I GREATLY appreciate it. :) Lesson learned for future endeavors.
 
You must log in or register to reply here.
Back
Top Bottom