Related
I (prematurely) update to the leaked version of the Android 2.2 release. I would like to revert back to 1.47.651.1 so I can install Cyanogen 6 Mod. I am fairly new to working with Android ROMs, but I have tried several things.
1.32.651.1 and .6 RUU's do not work. I get "ERROR [140]: Bootloader Version Error".
1.47.651.1's RUU, refuses to see the phone getting "ERROR [171]: USB Connection Error".
I tried multiple "update.zip" files to no avail. I constantly get "signature verification failed" when I try and revert back to these files (renamed as update.zip):
Supersonic_1.32.651.6_rooted.zip
Supersonic_1.32.651.1_rooted.zip
Evo-Froyo-2.2-Rooted-Stock-Odexed-netarchy-signed.zip
I've also tried PC36IMG.zip and receive a "Main Version Older. Update Failed" error.
Is there any way to revert back to 1.47/1.32.xx or am I stuck on this half-baked version of Android?
quite sure there is no root method for the ota update at the moment.
should have read the post saying to wait for root.
last but not least WRONG SECTION POST THIS IN Q AND A
ROFL 100th one today prob
This belongs in Q&A but...
Did you use the rooted or unrooted OTA update?
If you flashed the rooted version you're screwed until someone roots it.
If you flashed the unrooted version, just reboot into recovery and restore the nandroid I'm certain you made before flashing an updated ROM.
Here's another thread about this problem (also in Development)
Once on 2.2, no root...
If you flashed a rooted version of the latest leak I don't think you should have any problems...
I has Fresh 3.0b2 on my phone (based off of newest OTA, but rooted of course) and I just re-flashed the latest CM6 nightly
smw6180 said:
This belongs in Q&A but...
Did you use the rooted or unrooted OTA update?
If you flashed the rooted version you're screwed until someone roots it.
If you flashed the unrooted version, just reboot into recovery and restore the nandroid I'm certain you made before flashing an updated ROM.
Click to expand...
Click to collapse
Just a heads up, for the sake of confusion. I think you got the rooted and unrooted mixed up....
If you flashed the rooted version, you should be able to restore. If you flashed the UNrooted version, you have to wait for a Root method to be found.
Why flash why are you not doing a nandroid when you flash bell cw ask u and then it restores it just the way it was u know like using ghost on a pc
v1pe said:
If you flashed a rooted version of the latest leak I don't think you should have any problems...
I has Fresh 3.0b2 on my phone (based off of newest OTA, but rooted of course) and I just re-flashed the latest CM6 nightly
Click to expand...
Click to collapse
Sent from my EVO using XDA App
kwajr said:
Why flash why are you not doing a nandroid when you flash bell cw ask u and then it restores it just the way it was u know like using ghost on a pc
Sent from my EVO using XDA App
Click to expand...
Click to collapse
except that nandroid or not, you flash the UNROOTED OTA you are screwed for now. your nandroid will be there, but it won't be doing much for you if we can't root the new OTA.
Sorry about the wrong section; I was reading under development and I didn't think to switch.
Now just out of plain curiosity, how come the stock RUU will not work? I understand it is a different bootloader version, but doesn't it just install over it?
thefsfempire said:
Sorry about the wrong section; I was reading under development and I didn't think to switch.
Now just out of plain curiosity, how come the stock RUU will not work? I understand it is a different bootloader version, but doesn't it just install over it?
Click to expand...
Click to collapse
It doesnt work because HTC is not ****ing retarded. If they allowed it to work, what would be the point of them fixing the exploits that allow root?
The last two OTAs have come with bootloaders that have a concept of a minimum version requirement. It's a method to avoid downgrading. Despite the old OTA being "stock" or "official" or whatever you want to call it, it's a lower version than the minimum your current bootloader requires, meaning it would be a downgrade.
Sorry man, you're gonna have to sit tight while some nice dev bails you out.
Thanks for explaining. I don't mind waiting, I under stood the risks. Only thing is that I didn't quite understand how this part of it worked. Thanks for the explanation.
For science see if this method works:
http://forum.xda-developers.com/showthread.php?t=741294
jrmithdobbs said:
For science see if this method works:
http://forum.xda-developers.com/showthread.php?t=741294
Click to expand...
Click to collapse
I'd like to know that as well.
Permission denied when running flash_image through adb.
Does not seem to work on 2.2 FroYo OTA
So if you flashed a rooted rom you can just revert with a NAND backup. Are there any other ways to revert back to a previous version?
Also lets say you go from the currently 2.2 roms back to 1.47, can you then turn around and revert to stock?
sekigah84 said:
So if you flashed a rooted rom you can just revert with a NAND backup. Are there any other ways to revert back to a previous version?
Also lets say you go from the currently 2.2 roms back to 1.47, can you then turn around and revert to stock?
Click to expand...
Click to collapse
If you are rooted, you can do whatever. You can find a zip file of the original rom and just flash it from recovery. I'm not sure if it is possible to downgrade your radios when (I've never tried), but it probably is.
sekigah84 said:
So if you flashed a rooted rom you can just revert with a NAND backup. Are there any other ways to revert back to a previous version?
Also lets say you go from the currently 2.2 roms back to 1.47, can you then turn around and revert to stock?
Click to expand...
Click to collapse
The stock 2.2 rom removes the custom recovery, so you cant use nandroid to revert.
GumboChief said:
The stock 2.2 rom removes the custom recovery, so you cant use nandroid to revert.
Click to expand...
Click to collapse
This is why you use the rooted ones posted on XDA.
Before i start to flash CM7 ROM ... i had a question which i could find a concrete answer in other threads or the FAQs :
I'm on Defy US t-mobile 2.2.1 Froyo,
Can I get back to this for warranty by just flashing using the original SBF??
Or do i have root first and take a nandroid backup??
please adivce.
I come from original US Tmobile firmware also. There is no sbf for the official 34.4.9 system as it was an OTA update! HOWEVER you CAN EASILY flash back to 2.1 eclair system 3.6.360 using sbf and simply do the OTA update. Don't worry about a thing they all have (even official US Tmobile eclair) cg version=4. So there are no issues down-grading. Just don't flash the newest leaked Gingerbread 2.3.4 as it has a cg version=5 and can't be down-graded. So the CONCRETE ANSWER IS YES YOU CAN DOWNGRADE FROM CM7 BACK TO OFFICIAL 3.6.360(2.1.1) USING SBF AND THEN APPLY THE OTA UPDATE FOR 34.4.9(2.2.1)
I have a Nexus S and I'm attempting to Root/Install ROMs on a Defy. I must admit terms like SBF, 2ndInit, SuperOneClick were new to me. After almost 6 hours of reading and searching, and getting stuck at boot for a long time, I've successfully installed Pays 2.2 ROM on my phone, coming from 2.1 Eclair. But, I still haven't wrapped my head around the proper procedure for flashing ROMs. Can someone please answer the following questions?
1 - What is an SBF? How is it different from a Nandroid?
2 - Why does one have to flash an SBF as well as a ROM? This is confusing! Why do I flash a 2.2 Froyo SBF to install a 2.3.4 ROM? And in some cases why the Froyo SBF AFTER the Gingerbread ROM?
3 - If I want to switch between 2.3.3/4 ROMs (eg: MIUI and CM7) is it sufficient to just restore their Nandroids?
4 - I see a lot of talk about Downgrading. Why would one want to downgrade to 2.1, or even stay at 2.2 for that matter?
5 - How would one switch from a 2.3.4 ROM to a 2.2 ROM? Nandroid? Or SBF or both?
On the Nexus S, we just flash a custom recovery that stays put. Then we're free to restore Nandroids and things as we please. All this SBF stuff is a little beyond me. Any answers to these questions would be really appreaciated. Thanks!
thanx i wanted to ask the same....
What the guys above me said, good to see someone asking questions some of us dare'nt ask for fear of put downs or other negative replies.
Seriously asn thx for replying, about 6 hours earlier nearly wrote your reply word for word but didn't as didn't want to be labeled a stupid noob. FYI I've ROMed 4 winmob devices and a zte blade so im not a stupid noob
Here's what I don't understand (sorry for the noob question and the long post):
Here's what I did so far:
Started with stock US Froyo (Version.34.4.9.MB525.T-Mobile.en.US, Build Number: 3.4.2-107_JDN-9)
Rooted and installed ClockworkMod Recovery v2.5.1.8
Took a nandroid backup
Installed CM7 (as per FAQ):
flashed JRDNEM_U3_3.4.2_177-005_NORDIC
rooted using SuperOneClickv1.9.5-ShortFuse
installed 2ndInit SndInitDefy_1.4_2.apk
installed CM7 RC1v2 using Recovery - Custom Recovery
installed cm7-110715-1018-NIGHTLY by booting 2ndInit -> Recovery -> Stable recovery
This was actually my second install of CM7.
During my first install I did not flash Nordic and installed directly on top of Stock US 2.2.1 Froyo.
Then I only installed RC1v2 (no nightly) and the camcorder had very laggy recording.
So I decided to do it again by first flashing Nordic.
I did this by restoring my nandroid backup and it worked fine without flashing any fixed SBF.
Now I believe that the nightly probably fixed the camera and it wasn't because my I didn't flash Nordic first.
So my questions are:
* To downgrade, do I really need to apply a fixed SBF on top of my nandroid or is this only necessary if I started off on Eclair (and not if I started on Froyo) ?
The CM7 FAQ state that in order to downgrade from CM7 a nandroid backup AND a fixed SBF is needed.
Why would I need a fixed SBF if I have a nandroid backup.
* Is it ok to install CM7 on top of Stock US 2.2.1 Froyo or is it better to flash Nordic or does it not make a differnce at all?
* What are the BOOT179 nightlies (e.g. cm7-110716-0105-BOOT179-Jordan) and do I need to apply it if I'm already on RC1v2 and want to apply the latest nightly build?
Let's start with the big one, Defy has a locked bootloader, hence there's not an easy way to flash a custom rom, unfortunately no flash & go here. The bootloader check for signed moto products at a very low level, it's something like built-in in the hardware.
1) SBF is usually a stock ROM provided by Motorola, i say "usually" because you will find many leaked versions around. It is different from a nandroid backup, you cannot restore a SBF in the way you restore a nandroid. A SBF MUST be flashed with RSD Lite, which is an apposite tool delivered by Motorola.
2) Depending on the custom ROM you're going to install, you have to flash the appropriate SBF. For example, if you try to install a custom ROM based on froyo 2.2.2 to a phone which runs eclair you'll just get stuck at startup. Actually, before the Quarx work (GB) all the custom roms here were just customizations of SBFs. Now with the 2nd init stuff we've new opportunities but, until the bootloader is locked, we'll need the official SBFs as base for any custom rom, otherwise no way to bypass the check at startup.
3) It depends on the bootloader version. Your ROM should have the same bl version of the nandroid backup-ed one.
4) Actually there are two reasons ppl talk about downgrading. First, in case of the phone needs repairs you should reinstall the original ROM in order to avoid to void your warranty. Second, many custom ROM, included GB versions, are still buggy. Some ppl like them much, other ppl prefer going back to slower but more stable official ROMs.
5) I cant tell you for sure since i've never tried any GB so far, but, with RDS Lite + SBF you should be able to revert back.
All this, as far as i know, and i know not much..
EDIT:
I forgot something important, use fixed SBF + nandroids to preserve your downgradability. The way is 1) apply a nandroid 2) flash the fixed SBF with RDS Lite 3) apply a custom rom. If you don't and go directly with RDS Lite and the whole SBF then downgradability will be lost.
Thank you very much! I wish there was an FAQ for noobs. As per your edit, I'm pretty sure I've lost downgradability. Not too worried about it...yet.
But, you've helped a lot. I think I get it now. Thanks again!
After trying to reinstall the factory sbf on my (us t-mobile) defy I cannot get past the initial blur activation. I have tried to skip the set up but it just takes me right back to the first page. Worse yet when I try to activate blur it will freeze up and requires reboot. I have re-flashed the sbf and even tried a few others with the same result. Any idea what is happening here and how to fix it?
JORDN_U3_6.19.0 - no boot
JORDN_U3_6.36.0 - above problem
3.4.2-107 - wont flash
3.4.2-164 - above problem
message me with email address so i can send u right sbf
pmp326 said:
message me with email address so i can send u right sbf
Click to expand...
Click to collapse
What SBF do you have in mind?
I also tried to restore my stock US 2.2.1 after installing CM7 - just to see if it works.
So I restored my 2.2.1 nandroid and the applied this sbf: p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf
It worked, however, this will not bring you back to the official 2.2.1 US Froyo because above SBF is an earlier beta version and you will end up with 34.4.4.MB525.T-Mobile.en.US_3.4.2-107_JDN-4.
The official version is 34.4.9.MB525.T-Mobile.en.US_3.4.2-107_JDN-9.
you have to restore through nandroid from 2.2.1 test keys
you did make a backup before you went flashing right?
pmp326 said:
you did make a backup before you went flashing right?
Click to expand...
Click to collapse
Not sure if this question is directed at me but yes, I made a nandroid backup of my stock US 2.2.1 before installing CM7 (nordic + rc1v2 + nightlies).
Then I restored my nandroid (leaving the kernel version at the CEE one from CM7) and applied the p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf.
Then you end up with 34.4.4.MB525.T-Mobile.en.US_3.4.2-107_JDN-4, which is not the official US Froyo.
I don't really care about that (I was just testing it out) but if somebody needs to go back to stock US Froyo in order for example to send it to warranty this will not work.
you have to root 221 install clockwork recovery then restore original backup
that's what i did - but the restore will NOT restore the 2.2.1 kernel
there is also a 2.2.1 boot only sbf which is the kernal
I assume you mean T-mobile froyo bootonly.sbf, which is from Jan 26 2011. I haven't applied it but I'm quite sure that's also not the official 2.2.1 version.
My point is that unless there's a different and newer 2.2.1 SBF (other than 2.2.1-3.4.2-107_JDN-4) you will not be able to go back to stock official US 2.2.1 froyo and claim warranty.
Well... it's a long story.
I bought my China Retail Defy ME525 this May, accidentally flashed 3.4.2-155 deblur as stock rom. Two day before I accidentally flashed JORDN_U3_97.21.51 (again ).
Now I stuck there and unable to flash any other roms in RSDlite. I'm trying to update it to froyo and later restore my CM7 backup.
Here's my questions:
According to here, it is possible to get an OTA update. But did anyone actually make that?
Would ME525 be unable to get T-Mobile update due to its IMEI?
(This is a silly one, however I really don't find the answer). How could it be possible to install an nandroid backup after flashing a fixed sbf? my led never turn blue after I flashed the sbf. Cannot enter bootmenu PS: The fixed sbf is based on 3.4.2-107 TMobile US full sbf)
Is it possible to make up a update.zip that acts as installing nandroid backup?
Would it be the same to install a nandroid backup first and later flash fixed sbf?
you install the nandroid backup first and then flash the sbf...
JORDN_U3_97.21.51 is an eclair sbf which contains CG39.smg and CG31.smg ver=5. You can no longer flash ANY froyo sbf. In fact the only sbf you can flash now are 2.3.4 and 2.3.6 sbf and of course JORDN_U3_97.21.51. 2.3.6 sbf is ver=6 and has no know downgrade possibility. Follow this guide to get back to froyo http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143
Keep in mind that this is a "dirty" method of getting back to froyo and you are ALWAYS stuck on ver=5. What that means is that even after getting to froyo using this guide you are NOT free to flash any sbf you like. You can however, use this guide to get to froyo and install cm7 from there