So just to be clear, I'm fully aware of the locked bootloader fiasco which makes it impossible to downgrade from 30.04 to 30.03 -- therefore downgrading to 2.3.15 impossible due it being on the 30.03 bootloader.
However, after looking around for a couple days I've been unable to find a clear answer to the following: is the bootloader -alone- the sole reason why downgrading is not possible?
I bring this up because I have a non US/VZW Droid X, which when launched, came with 2.3.15 on the 30.04 BL. As it turns out, this SBF was released, which should mean this is a stock 2.3.15 SBF with the 30.04 BL.
So back to my original question: If this stock SBF has the 30.04 bootloader, is there anything else that would prevent downgrading from 2.3.340 to 2.3.15?
TIA.
Related
Alright so I was trying to update to the new Fission ROM but it had the whole audio bug thing so I reverted back and was going to update to .340 before flashing back over to fission. I downloaded the update zips for 340 but I didn't know that it was recommended to flash one, reboot, flash the other, etc. Which may be why I'm stuck at this screen..
It's just black and says
"Bootloader
30.04
Err:A5,70,39,00,27
Battery OK
OK to Program
Transfer Mode:
USB"
I've tried to SBF but it's still stuck there. Can't boot into recovery, nothing. Can anyone help? Or am I going to have to try and get verizon to replace my phone.
Edit: Just realized I clicked development instead of general. Oops. Sorry mods.
Edit 2: I fixed it. I'll leave this here for anyone who has the same problem. I had to SBF back to .320 instead of .340 and then boot into recovery and wipe data/cache.
I had the same problem. I sbf'd .340 and that worked for me.
Sent from my DROIDX using Tapatalk
Good to see you fixed it. The reason you had to SBF back to .320 was because it was a full SBF, and .340 has only been seen in System-Only form which does not include a bootloader.
I was running the Fission 2.4.3 rom and it was having some problems because I read that it was because I was running on 2.2.1 kernel and I downloaded 2.3.340 Kernel Updater (2.6.32.9-g55626e1) and BP_C_1.09.07P Baseband Updater (also known as your radio file) from http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html then I installed both of those, now when I boot up to the Bootloader 30.03, it says, err:A5,70,00,00,23 Battery OK OK to Program Connect USB Data Cable. The phone also lets me boot in to the stock recovery by pressing Power and Home. Please help me I need help and I cant figure it out.
You should be on Bootloader 30.04. I would suggest grabbing the full .320 SBF, and the system-only .340 SBF, then flashing them both in order. After flashing them both go into the Motorola recovery and do a factory reset.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.
How do I do the SBF thing if I can only get in to the Bootloader 30.03 screen and the stock recovery screen. I have the clockwork recovery installed but i cant get to it. HELP
SBF is done from the bootloader menu you are already in. This link will help you with the process. If you are still on the original Froyo OTA, you will need the .320 Full SBF, and the .340 System-Only SBF. I cannot provide links to them due to a C&D notice, but they are not hard to find using Google.
When i flashed the sbf it get stuck at the sbf screen where it says bettery ok. At the top i have a bunch of errors. HELP I get error A5, 70, 70, 00, 1F
Bootloader is D2.35 and i am trying to flash 2.2.20 should i use 2.3.20
Yes unless your phone lives under a rock and somehow missed the 2.3.20 OTA update.
You have probably been updated and need the new 2.3.20 sbf file.
Once you are updated the 2.2.0 sbf won't flash your phone because the bootloader was changed in the update.
Sent from my DROID2 using XDA App
ok so right know i am downloading the 2.3.20 bootloader and sbf file should that work
i am sbfing the full 2.3.20 sbf
Thread can be closed
Silly me. I know exactly what I did, though. Maybe someone can help me out, please? This is my boss' phone! (no joke.. .although I did tell him stuff could happen).
Here's what happened, step by step.
1) The Atrix is from Telcel, and it was on 2.2. He told me the phone was rooted and unlocked.
2) So, I downloaded the .img files for the Orange FR version of Ginberbread (ORFR234-system.img, webtop.img, ORFR234-tegrapart-1100100.boot.img), and tried to use moto-fastboot.exe to flash them.
3) I could flash system.img and webtop.img. Tegrapart.1100100 gave me an error. So, the phone isn't unlocked.
4) I did a moto-fastboot reboot and used RSD to flash the .sbf unlocker (intl-fix-try1.sbf). Success.
5) I tried to go back to Flashboot on the phone, and I got an error message. Basically, I can only go into RSD now.
Which would be OK, I know I need to flash the original .sbf file.
The problem is - there's NO .sbf file I can go back to. Telcel's SBF is not available for download. And since I flashed the Orange France 2.3.4 system file, I'm not even sure I could go back, anyway.
So, what can I do? Can I go ahead and flash the Orange FR .sbf Gingerbread file using RSDLite? Should I do something else? At this point I don't know if the phone is unlocked (please, let it be so).
I suppose I only get one shot at fixing this issue, so I'll need any help I can get. Thanks!
Yes you can. I have flashed versions from other carriers before without problem. I would stay away from the AT&T version though. However, do not flash any froyo SBF, you will brick your (boss) phone. If after flashing the phone, you do not have internet access, check the apn settings. If you flash the unlock SBF than flash a stock SBF, the phone will be 'relocked'. Not in an actual sense, just that the unlocked text is gone, and fastboot will not accept any unsigned files for flashing. Why did you even unlock the phone for? Flashing SBF files do not require a unlocked phone. If after flashing the SBF file, you decide you need a unlocked bootloader, just re-flash the unlocking SBF file. Hope this helps!
matthew5025 said:
Yes you can. I have flashed versions from other carriers before without problem. I would stay away from the AT&T version though. However, do not flash any froyo SBF, you will brick your (boss) phone. If after flashing the phone, you do not have internet access, check the apn settings. If you flash the unlock SBF than flash a stock SBF, the phone will be 'relocked'. Not in an actual sense, just that the unlocked text is gone, and fastboot will not accept any unsigned files for flashing. Why did you even unlock the phone for? Flashing SBF files do not require a unlocked phone. If after flashing the SBF file, you decide you need a unlocked bootloader, just re-flash the unlocking SBF file. Hope this helps!
Click to expand...
Click to collapse
Thank you! I used a Brazil .sbf file and the phone is back! I'll unlock and upgrade now
Hey Guys, I know that there is a tutorial for this but i couldn't figure it out, I am having a Green Lens Defy, I have a broken display so.. I need to send it to service.
- I had a custom ROM on it
- Flashed Froyo_CEE_2.2.2 and the screen is black now
- Tried JORDN_U3_97.21.51 but no success
- I need to have the Froyo_CEE_2.2.2 on my device because it is the official ROM in Romania
Thx in advanced
go to bootloader
Flash 2.2.2 froyo sbf with rsd lite.
after that go to stock recovery, wipe data/chage than reboot yor phone
go to bootloader and flash 2.2.2 froyo sbf with rsd lite.
And it will boot up.
Blazs said:
go to bootloader
Flash 2.2.2 froyo sbf with rsd lite.
after that go to stock recovery, wipe data/chage than reboot yor phone
go to bootloader and flash 2.2.2 froyo sbf with rsd lite.
And it will boot up.
Click to expand...
Click to collapse
This way will not work in this case. As he flashed Chinese eclair (JORDN_U3_97.21.51) with BL5, he has no way back to froyo, which is BL4