So i ran the RUU for ICS through the bootloader (i am s-off). After I booted into the stock OTA, I flashed my TWRP recovery and then restored my nandroid of NeoMax 1.6 i had made just before flashing the RUU. So my question is does restoring my nandroid I made before flashing the RUU wipe out my flash of the official ruu putting me back where i was before i flashed the latest ICS RUU? any clarification would be really great. I basically just wanted to get back to having my phone and rom set up how i liked it because i am so sick of doing it over and over again. Also, would restoring only certain parts of my nandroid in TWRP change anything? Thanks again for any help
Software wise, not really. Firmware wise, not at all.
Related
I would like to start flashing some new ROMS. Why I'm not sure, because my random reboots are almost never. You have to flash new radio for the gingerbread roms. So when I restore a nandroid back up of my current ROM which uses the latest OTA will I have to reflash radio also?
Radio HAS to be flashed in hboot, recovery does not control it. So yes you would have to flash the 2.2 radio in hboot when restoring a 2.2 ROM. Its common sense, if you cant flash the radio in recovery why would you think a restore would revert it?
Lot of hostility there man... i knew that radios are flashed in hboot but i didnt know that recovery didnt back that part up. he was asking a legitimate question theres no need to be so upset.
mbh87 said:
Radio HAS to be flashed in hboot, recovery does not control it. So yes you would have to flash the 2.2 radio in hboot when restoring a 2.2 ROM. Its common sense, if you cant flash the radio in recovery why would you think a restore would revert it?
Click to expand...
Click to collapse
Due to my lack of common sense I was not sure if restoring effects radio. I haven't had to flash radio as of yet. But now that you mention it, when I updated to my latest ROM it was thru hboot using the RUU. Thanks for the answer.
So I achieved s-off on my first try, and was feeling cocky. So, I downloaded Newt's new 4.0, with the patch for old firmware from Nil's Rom. I am writing this from my rezound now, but whenever I try to go back to chingy's gb Rom, it hangs at the 4g screen. I have tried to use the image the Rom produces, pm98img from another gingerbread Rom, incredikernal, and fast l
booting the boot.IMG file from said sources. What am I doing wrong? Besides messing with stuff I shouldn't. I thought going back to gingerbread would be simple if I stayed on old firmware. Does anyone know where to go from here? I can install Newt's xXx Rom and boot with no problem. Any help would be greatly appreciated.
Sent from my ADR6425LVW using XDA
Edit: I fixed it by using the PH98IMG ruu, then using the juonutbear hboot patch. Then reloaded Amon Ra. Flashed Chingy's rom, then my back up. There was alot of drama in the middle of all that. Mostly caused by the user. I flashed so many different things, that i would have trouble telling you what i flashed to get back. I scoured xda for several hours before attempting to try this, and hours more before i asked for help. Thanks to those that helped.
easyy fix
the 2.1 is just a patch you need to do 2.0 first which is newtoroot rom then 2.1 for the patch and yes you do need to use the sense4_boot.img again
The old ROMs didn't contain firmware. So if you installed the ICS leak RUU then you have the new firmware and need to flash the "old firmware" patch. As far as kernels go, you should always flash the kernel that came with the ROM(except for GB ROMs where you can use incredikernel).
I think this will work for you. Backup your current ROM(if you want), then flash a GB RUU, then flash a GB ROM/kernel. Make a backup of that. Now you should have a GB firmware backup and an ICS firmware backup.
MrSmith317 said:
The old ROMs didn't contain firmware. So if you installed the ICS leak RUU then you have the new firmware and need to flash the "old firmware" patch. As far as kernels go, you should always flash the kernel that came with the ROM(except for GB ROMs where you can use incredikernel).
I think this will work for you. Backup your current ROM(if you want), then flash a GB RUU, then flash a GB ROM/kernel. Make a backup of that. Now you should have a GB firmware backup and an ICS firmware backup.
Click to expand...
Click to collapse
He was saying he just installed Newt's rom,but still on GB firmware. I think all you have to do is reflash Chingy's rom, but wipe first and then make sure your installing GB's kernel. I have had similar issues , where I had to install a rom with the stock kernel first before going back to custom kernels. So maybe install Scott's earlier GB rom first or Nil's GB business sense rom they both use the stock kernel.
Not sure why that seems to work, but for awhile I had the exact same issue going from ICS to GB and back. Only solution I ever found was to wipe a few times install a rom , then stock kernel.
Mjh got it right. I have back ups of both. whenever i try to go back to gingerbread now, i get stuck at the 4g splash. i have tried several gb kernels and still no dice. i think a ruu is in order. I have the exe RUU on my pc. It is taking forever for the PM98IMG Ruu to download. Can i run exe file on my S-off phone and then use recovery to load one of my older gb roms.S-off was easy compared to this. Thanks for any and all advice.
JeramyEggs said:
Mjh got it right. I have back ups of both. whenever i try to go back to gingerbread now, i get stuck at the 4g splash. i have tried several gb kernels and still no dice. i think a ruu is in order. I have the exe RUU on my pc. It is taking forever for the PM98IMG Ruu to download. Can i run exe file on my S-off phone and then use recovery to load one of my older gb roms.S-off was easy compared to this. Thanks for any and all advice.
Click to expand...
Click to collapse
Yes, you can ruu , just remember if your on stock hboot you will have to relock and that will affect what your bootloader says. Otherwise, also make sure after the ruu to reflash amon ra recovery.
Did you try the stock ota kernel ?http://forum.xda-developers.com/showthread.php?t=1476152
Try the GB kernel on this page and see if it works before RUUing.
Sent from my ADR6425LVW using xda premium
Hi, everyone. I am sure someone is going to shaking their heads at my idiocy after reading this post but I hope someone can save me. So I went to all that trouble to update my phone to ICS from Gingerbread and retain S-off and rooted. After playing with it a little, I decided I like my previous state better. Before I updated my phone, I backed up my phone using the clockworkmod recovery that was installed using revolutionary's tool. That was also the recovery that I flashed after I updated to ICS. So I figure all I have to do was restore the backup. I boot into recovery and all I did was select "backup\recovery" and then the date that I did the backup. The restore finished and I rebooted my system. Everything should be fine now, right? Wrong! As the phone bootup, it would read HTC then Sprint before rebooting again and again. I never reach the lockscreen. Right now I can still reach recovery through the bootloader but that is it.
So how can I recover? Was I supposed to wipe something before restoring? If so, which options am i supposed to use (wipe all data?) because specific details will prevent me from making another bonehead move. If not, what do I do?
Problem is, I got impatient to downgrade from ICS and never bothered to backup after the update to ICS. Just a reminder to all that "backup, backup and backup). So I am stucked right now and need help. HELPPPPPPP......
Tommy
I can see from my bootloader that it is still HBoot 1.58 instead of HBoot 1.4 before the ICS update. Would flashing the boot.img from the clockworkmod backup work?
xionchen4628 said:
Hi, everyone. I am sure someone is going to shaking their heads at my idiocy after reading this post but I hope someone can save me. So I went to all that trouble to update my phone to ICS from Gingerbread and retain S-off and rooted. After playing with it a little, I decided I like my previous state better. Before I updated my phone, I backed up my phone using the clockworkmod recovery that was installed using revolutionary's tool. That was also the recovery that I flashed after I updated to ICS. So I figure all I have to do was restore the backup. I boot into recovery and all I did was select "backup\recovery" and then the date that I did the backup. The restore finished and I rebooted my system. Everything should be fine now, right? Wrong! As the phone bootup, it would read HTC then Sprint before rebooting again and again. I never reach the lockscreen. Right now I can still reach recovery through the bootloader but that is it.
So how can I recover? Was I supposed to wipe something before restoring? If so, which options am i supposed to use (wipe all data?) because specific details will prevent me from making another bonehead move. If not, what do I do?
Problem is, I got impatient to downgrade from ICS and never bothered to backup after the update to ICS. Just a reminder to all that "backup, backup and backup). So I am stucked right now and need help. HELPPPPPPP......
Tommy
Click to expand...
Click to collapse
xionchen4628 said:
I can see from my bootloader that it is still HBoot 1.58 instead of HBoot 1.4 before the ICS update. Would flashing the boot.img from the clockworkmod backup work?
Click to expand...
Click to collapse
You need to downgrade your bootloader to something lower than 1.58 if you want to run ROM's based on GB or AOSP. You can go back to 1.4 if you want, or the Jbear GB (1.50.5050) version. You should leave the rest of your firmware at the ICS level.
The bootloaders can be found in this post. Download the one you want, put it in the root of your SD card, rename it to PG86IMG.zip and flash it from the current bootloader. You should then be able to boot your CWM backup, and don't forget to delete the PG86IMG.zip file from the root of your SD card after you flash it.
ramjet73
Thanks, ramjet. My phone is back to the state that it was in before my ICS update. Sorry for all the work that you put in to help me upgrade in the first place. Since I restore from my GB backup, all I did was flash the bootloader and everything went to normal. If somewhere done the line, I decided to update to ICS again, I know all the steps that need to be done (thanks to you and all the users who provided the various files). Thanks again. I love this community!
ramjet73 said:
You need to downgrade your bootloader to something lower than 1.58 if you want to run ROM's based on GB or AOSP. You can go back to 1.4 if you want, or the Jbear GB (1.50.5050) version. You should leave the rest of your firmware at the ICS level.
The bootloaders can be found in this post. Download the one you want, put it in the root of your SD card, rename it to PG86IMG.zip and flash it from the current bootloader. You should then be able to boot your CWM backup, and don't forget to delete the PG86IMG.zip file from the root of your SD card after you flash it.
ramjet73
Click to expand...
Click to collapse
xionchen4628 said:
Thanks, ramjet. My phone is back to the state that it was in before my ICS update. Sorry for all the work that you put in to help me upgrade in the first place. Since I restore from my GB backup, all I did was flash the bootloader and everything went to normal. If somewhere done the line, I decided to update to ICS again, I know all the steps that need to be done (thanks to you and all the users who provided the various files). Thanks again. I love this community!
Click to expand...
Click to collapse
Well the rest of firmware (other than the hboot) is now updated to the Sprint ICS 2.89.651.2 level, so you should be able to run the ICS ROM's that don't require the 1.58 bootloader and there are quite a few of those. So it wasn't a waste of time and effort.
ramjet73
I'm currently Unlocked, S-OFF AT&T and running ARHD 11.0 with the 2.19 firmware update. I didn't do the hboot update to get rid of the red developer writing because of the scary warning. Now I want to return to this version "AT&T Stock Rooted ODEX - 1.26.502.12".
Can I just run "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2"? Or is there a firmware I can just flash again so I can restore my nandroid backup? When I tried to do my nandroid I lost all touch functions. After looking up why, I realized it's because of the 2.19 and Updated recovery I did.
I believe I can run the RUU and everything will be fine, but I just want to be positive.
Thanks in advance.
dmjlabelle said:
I'm currently Unlocked, S-OFF AT&T and running ARHD 11.0 with the 2.19 firmware update. I didn't do the hboot update to get rid of the red developer writing because of the scary warning. Now I want to return to this version "AT&T Stock Rooted ODEX - 1.26.502.12".
Can I just run "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2"? Or is there a firmware I can just flash again so I can restore my nandroid backup? When I tried to do my nandroid I lost all touch functions. After looking up why, I realized it's because of the 2.19 and Updated recovery I did.
I believe I can run the RUU and everything will be fine, but I just want to be positive.
Thanks in advance.
Click to expand...
Click to collapse
I was running CM10 nightlies like 2 weeks ago and it had some bugs I couldn't deal with. The RUU got me back to full stock pretty easy.
I believe you'll need to relock your bootloader though.
So I see a number of people reporting using Baseband: 1.13.11.1105, including Captain_Throwback. I'm on Baseband: 1.13.11.0830 and am having some trouble with the phone connection - dropped calls, static on the line, etc. but data is fine (in fact I can make voip calls through hangouts no problem, but incoming calls are normal phone).
I looked at C_T's firmware collection on themikmik but that only contains up to Baseband: 1.13.11.0830 with the 3.17 software version.
I'm S-OFF via rumrunner after having flashed the 2.10 hboot and 4.13 651.4 Sense 5 Android 4.3 - Deodex to update the partitions to the new format. I've since flashed CM11 snapshot M12. Same phone issues on the rooted Sense and CM11.
Thanks to Captain_Throwback for all the excellent guides and collections here. Any suggestions from you or anyone here on where to find the latest baseband, and if you think this or maybe a custom PRL may help. (Is it possible to flash a custom PRL in CM11 or do I have to flip back to my Sense nandroid first?)
Thanks!
The baseband you're looking for can be found with the 4.3 RUU. You can find said RUU in the first post of my Hboot thread (top link in my sig). Not sure how you updated your Hboot but not your firmware, but I suggest running the RUU. You'll remain S-off afterwards.
To answer your other question you have to be running a Sense ROM to install a custom PRL.
OK that's what i thought - that the baseband should come with the hboot. Can i try just the 2.10 hboot in captain_throwback's thread or does it need to be the full ruu? Otherwise the process would simply be to backup, ruu, flash recovery and restore, right?
Related question, is 2.8.0.3 the latest twrp that works with cm11 or is there a 2.8.1.0 that works as well?
cmags said:
OK that's what i thought - that the baseband should come with the hboot. Can i try just the 2.10 hboot in captain_throwback's thread or does it need to be the full ruu? Otherwise the process would simply be to backup, ruu, flash recovery and restore, right?
Related question, is 2.8.0.3 the latest twrp that works with cm11 or is there a 2.8.1.0 that works as well?
Click to expand...
Click to collapse
I would run the RUU. Once done, you'll need to unlock and install TWRP again. Then you can restore your backup. As far as recovery goes I'm not sure which is most recent.
Well, that was only partially successful, and I could use some suggestions.
I did a nandroid of my CM11 M12 snapshot image, and ran the RUU in your post (RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4_R…igned_one_step.exe).
Afterwards Hboot is 2.10, and Radio is 1.13.11.1105. Great. Bootloader remains S-OFF (expected), and unlocked (unexpected, but cool).
I run fastboot flash recovery TWRP-Recovery-2.8.0.3-jewel-CPTB.img. Boot into recovery, restore my CM11 image, and reboot. Phone just spins on the boot animation.
Rebooted into recovery, wiped cache/dalvik/system/data, install flash CM fresh, wipe again, then restore (without boot) - same issue. About to wipe again and try restoring Sense nandroid, or flashing roms (CM and Sense) anew to see if i get different results.
Any other thoughts? Any way to verify the partition layout? Any way to get a log of what its hung up on while spinning the boot animation?
Thanks!
The issue you're describing reminds me of the issue that comes about from being S-on and having to flash the kernel separately from the ROM. You say you're S-off so that's not the issue, obviously. If you ran the RUU then you are on the new partition layout. Not getting any errors in recovery when you flash the ROM, are you? You might want to 're-download the ROM, check the MD5, and flash again.
Got it sorted out. Something must have gotten corrupted in the nandroid. A stock nandroid worked fine. So i restored cm11 then flashed the rom over the top to fix the boot partition. Im all set now, though the updated baseband didnt fix the static and dropped calls. Must be a hardware issue.