Does anyone have a stock, untouched system image for 2.6.651.11? If so, please share if you are willing. Thanks in advance.
I take it no one has the system image? I guess my options are to install the 2.6.651.11 RUU and then take the update. Has anyone done that? I saw somewhere that someone had that not work.
bpdamas said:
I take it no one has the system image? I guess my options are to install the 2.6.651.11 RUU and then take the update. Has anyone done that? I saw somewhere that someone had that not work.
Click to expand...
Click to collapse
you can always flash the 2.11 RUU , always take a look see into Android development folder , it has everything you need.
http://forum.xda-developers.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
BUBBA DUB'S said:
you can always flash the 2.11 RUU , always take a look see into Android development folder , it has everything you need.
http://forum.xda-developers.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
Click to expand...
Click to collapse
Thanks for the reply. The android development folder has everything other than the untouched system image for 2.6.651.11 unless I am just missing it. Basically, I want to take the OTA but you need a fully stock system to do that (per post #2 in here). I know I can flash the 2.6.651.11 RUU but was hoping to avoid that if I could. All I need is the untouched system image to avoid it. If anyone reads this and flashes the 2.6.651.11 RUU, before you update or flash another RUU, if you could grab the system image backup through TWRP, I would definitely appreciate it. Hopefully this helps clear things up.
bpdamas said:
Thanks for the reply. The android development folder has everything other than the untouched system image for 2.6.651.11 unless I am just missing it. Basically, I want to take the OTA but you need a fully stock system to do that (per post #2 in here). I know I can flash the 2.6.651.11 RUU but was hoping to avoid that if I could. All I need is the untouched system image to avoid it. If anyone reads this and flashes the 2.6.651.11 RUU, before you update or flash another RUU, if you could grab the system image backup through TWRP, I would definitely appreciate it. Hopefully this helps clear things up.
Click to expand...
Click to collapse
I'm pretty sure the OTA files are the untouched back ups, but why go through all that trouble when the RUU.exe file for 2.11 is posted there? That will skip the step of going back to 2.6 to try to take the OTA. Plus it won't work if you flash the 2.6 RUU, you would have to go all the way back to 1.32 to take the 2.6 OTA to take the 2.11 OTA. @OMJ what do you recommend? And also are you S - on or S- Off?
BUBBA DUB'S said:
I'm pretty sure the OTA files are the untouched back ups, but why go through all that trouble when the RUU.exe file for 2.11 is posted there? That will skip the step of going back to 2.6 to try to take the OTA. Plus it won't work if you flash the 2.6 RUU, you would have to go all the way back to 1.32 to take the 2.6 OTA to take the 2.11 OTA. @OMJ what do you recommend? And also are you S - on or S- Off?
Click to expand...
Click to collapse
I am S-OFF. I am currently on 2.11. I want to go to 2.19. I can run the RUU.exe for 2.11 but I am trying to avoid that. If you can tell me how to get into the OTA zip or rom.zip (from the RUU.exe) then I could grab the system img and flash that through fastboot. Once I restore the stock system image for 2.11 (removing root and going back to stock) I can take the OTA (in theory).
bpdamas said:
I am S-OFF. I am currently on 2.11. I want to go to 2.19. I can run the RUU.exe for 2.11 but I am trying to avoid that. If you can tell me how to get into the OTA zip or rom.zip (from the RUU.exe) then I could grab the system img and flash that through fastboot. Once I restore the stock system image for 2.11 (removing root and going back to stock) I can take the OTA (in theory).
Click to expand...
Click to collapse
Oh gotcha, I thought you were on 2.6 trying to get to 2.11 and by that I ment 2.11.651.19 hopefully @OMJ or @benny3 can lead you where you are trying to go.
Edit: if you're S off you could just flash the firmware for 2.11.651.19 which would allow you to save time as well.
BUBBA DUB'S said:
Oh gotcha, I thought you were on 2.6 trying to get to 2.11 and by that I ment 2.11.651.19 hopefully @OMJ or @benny3 can lead you where you are trying to go.
Edit: if you're S off you could just flash the firmware for 2.11.651.19 which would allow you to save time as well.
Click to expand...
Click to collapse
I agree I could flash the firmware but I want to be able to take the OTA in the future. I don't think I will be able to if I just flash the firmware (somebody correct me I'm wrong).
bpdamas said:
I agree I could flash the firmware but I want to be able to take the OTA in the future. I don't think I will be able to if I just flash the firmware (somebody correct me I'm wrong).
Click to expand...
Click to collapse
Being S off you don't have to worry about taking the OTA, you can just flash firmware then rooted ROM , or RUU if you wanna go back to stock.
BUBBA DUB'S said:
Being S off you don't have to worry about taking the OTA, you can just flash firmware then rooted ROM , or RUU if you wanna go back to stock.
Click to expand...
Click to collapse
I appreciate the discussion and understand I can just flash the firmware but I want to be able to take the OTA. If I don't have an internet connection on my computer for long periods of time, I won't be able to take the update without downloading something from here. Having the stock system image allows me to take and flash the image without internet on my computer and then I can take the OTA.
bpdamas said:
I appreciate the discussion and understand I can just flash the firmware but I want to be able to take the OTA. If I don't have an internet connection on my computer for long periods of time, I won't be able to take the update without downloading something from here. Having the stock system image allows me to take and flash the image without internet on my computer and then I can take the OTA.
Click to expand...
Click to collapse
The OTA will fail the way you want to it unless you go back all the way to 1.32 to 2.6 to 2.11. I just ran the RUU for 2.11.651.19 coming from 2.6.651.11 with no issues, being S off you don't even have to relock your boot. I guess your best best would be to do that, flash twrp, keep it set to read only and make a back up of the system image to have it for how you want to take the OTA's in the future.
w/o a system img of 2.6 you're not going to accomplish this...bite the bullet, flash the 2.11 RUU, and this time make sure to create a system img for future...then you'll be able to take the next ota
Related
So I don't know why, but the RUU exe files just don't work for me. I've done everything but start fresh on my PC, but it's exam week in a computer modeling class and I just can't do that right now!
I've had nothing but problems since I attempted one of the 2-step processes out there for updating to the radios/kernels, so I really want to get through an RUU so I know I'm clean at my lowest levels.
I have found the PH98...zip files for the shipped version of the ROM, but thoes don't work due to my version of HBOOT (not mainver.. that never got updated).
Does anyone out there have one for the newest RUU? At this point, I think flashing that from HBOOT is the only option I have.
I have no idea how to extract it myself, so I can do that too if someone can tell me how!
Thanks for any help.
a-jive said:
So I don't know why, but the RUU exe files just don't work for me. I've done everything but start fresh on my PC, but it's exam week in a computer modeling class and I just can't do that right now!
I've had nothing but problems since I attempted one of the 2-step processes out there for updating to the radios/kernels, so I really want to get through an RUU so I know I'm clean at my lowest levels.
I have found the PH98...zip files for the shipped version of the ROM, but thoes don't work due to my version of HBOOT (not mainver.. that never got updated).
Does anyone out there have one for the newest RUU? At this point, I think flashing that from HBOOT is the only option I have.
I have no idea how to extract it myself, so I can do that too if someone can tell me how!
Thanks for any help.
Click to expand...
Click to collapse
u can just pull the "rom.zip" from the RUU and rename to PH98IMG.zip and ur good to go.
dl this for a how-to on how to do this..
http://forum.xda-developers.com/attachment.php?attachmentid=486701&d=1294753279
You did relock your bootloader before running the RUU right?
andybones said:
u can just pull the "rom.zip" from the RUU and rename to PH98IMG.zip and ur good to go.
dl this for a how-to on how to do this..
http://forum.xda-developers.com/attachment.php?attachmentid=486701&d=1294753279
Click to expand...
Click to collapse
Awesome, thanks!
OLDsJUNKIE said:
You did relock your bootloader before running the RUU right?
Click to expand...
Click to collapse
Oh yeah. Really, tried everything. It sees the phone, reads the current build, goes through the next screen or two, and then once it says "Rebooting to Bootloader" it either sits there for a couple minutes till it times out and errors or errors immediately. I cannot find any other posts of people having problems, so I'm really at a loss. Makes me worried about having more troubles once the official ICS build comes out... but I probably have a lot of time till then.
Thanks guys!
Tried this as well, and my phone is not seeing the file
Make sure you are naming the file correctly "PH98IMG. zip" the instructions provided give a different file name than want the Rezound uses.
a-jive said:
Make sure you are naming the file correctly "PH98IMG. zip" the instructions provided give a different file name than want the Rezound uses.
Click to expand...
Click to collapse
I updated to the latest ota that verizon sent out. I didnt flash a rom, only perm rooted/unlocked...I relocked my phone tried the ruu exe many times didnt work..I done a backup of my nandroid but it took me back to the earlier firmware but still have the updated radio..So, I will relock it and place this on my sd card and try again..I was getting error 140 on the ruu exe
Here is the no-brainer fix for those that end up having Mainver issues, or maybe want to come back from an ICS ROM to GB and RUU and the normal methods don't work...
Go to www.scottsroms.com and hit the download section, look for Rezound and Stock Roms. Grab his boot image for the latest OTA.
Then download his "Cleanflash" utility and copy the boot.img file to that directory on your PC.
Run it and select option "2".
That restores the stock boot image and mainver right there. If you made a Nandroid of your system from before you went to ICS, boot into recovery and restore it. His tool will also install Amon Ra or CWM recovery, just like the boot image, download the one you want and copy that recovery.img to the cleanflash folder and run the tool.
I went from a completely hosed ICS install which would not allow RUU or Hbooting the PH98IMG.zip file... nothing worked, was contemplating replacing the phone, when I tried Scott's tool to push the stock boot image to the phone and then restored my Nandroid.
Worked 100% in under 5 minutes, the Nandroid Restore taking most of that time.
Hope this helps!
I s offed with the ICS leaked firmware and want to downgrade to the gb radios. I have seen lots of posts saying different things and would like someone with experience doing this to tell me what you did and in what order
Sent from my ADR6425LVW using Tapatalk 2
pmania said:
I s offed with the ICS leaked firmware and want to downgrade to the gb radios. I have seen lots of posts saying different things and would like someone with experience doing this to tell me what you did and in what order
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
If your S-off and on Juopunut bear's modified Hboot, you can just download the exe. version of the GB ota found in this thread http://forum.xda-developers.com/showthread.php?t=1338916 . Just be aware that once you run it you will be completely stock again including locked bootloader. If you still want to preserve your locked status I would flash this hboot in this thread..http://forum.xda-developers.com/showthread.php?t=1618140
Now, you will still be locked but able to run fastboot commands without unlocking. Now, you have to flash Amon recovery found here..http://www.mediafire.com/?l9dgzvvsdku7g3c This is the recovery that works for GB firmware. If you upgrade back to leaked ICS then you will have to flash 3.15.
Prior to flashing Amon Ra recovery.. you may watch to do a factory reset in hte stock recovery to prevent any possible data connection issues. Once you did that and now have flashed Amon ra.. you can either flash a rooted rom to get root back or to go to developer menu in Amon ra and install SU there.
Remember if you now flash GB based roms you don't need any patches, but if you flash ICS roms you will need this patch here.. http://forum.xda-developers.com/showthread.php?t=1508118
It will be the old firmware patch you want to download.
After all this you should be set !
???
mjh68 said:
Remember if you now flash GB based roms you don't need any patches, but if you flash ICS roms you will need this patch here.. http://forum.xda-developers.com/showthread.php?t=1508118
Click to expand...
Click to collapse
Why is the 'old firmware patch' necessary when moving from GB to ICS; is something not getting properly overwritten when using a PHxxxxx.zip instead of a full RUU?
jdmba said:
Why is the 'old firmware patch' necessary when moving from GB to ICS; is something not getting properly overwritten when using a PHxxxxx.zip instead of a full RUU?
Click to expand...
Click to collapse
I am talking about if he stays on Gingerbread firmware , but wants to run ICS roms. Then he would need to flash the old firmware patch so his SD card mounts properly.
Yes, I get that ...
Yes, I understand why people need a patch after running the PHxxxx.zip
I am asking why the PHxxxx.zip leaves that a necessary step. What is missing from the PHxxxx.zip that requires this to be done.
I suspect when VZW releases their RUU, such a step will not be necessary (i.e., it will properly update the firmware). So I am trying to get to the bottom of why the PHxxxx.zip does not properly update the firmware.
mjh68 said:
If your S-off and on Juopunut bear's modified Hboot, you can just download the exe. version of the GB ota found in this thread http://forum.xda-developers.com/showthread.php?t=1338916 . Just be aware that once you run it you will be completely stock again including locked bootloader. If you still want to preserve your locked status I would flash this hboot in this thread..http://forum.xda-developers.com/showthread.php?t=1618140
Now, you will still be locked but able to run fastboot commands without unlocking. Now, you have to flash Amon recovery found here..http://www.mediafire.com/?l9dgzvvsdku7g3c This is the recovery that works for GB firmware. If you upgrade back to leaked ICS then you will have to flash 3.15.
Prior to flashing Amon Ra recovery.. you may watch to do a factory reset in hte stock recovery to prevent any possible data connection issues. Once you did that and now have flashed Amon ra.. you can either flash a rooted rom to get root back or to go to developer menu in Amon ra and install SU there.
Click to expand...
Click to collapse
Very useful information mjh. Two points/questions:
1. If the OP doesn't need to use fastboot commands, they can simply flash a PH98IMG.zip of the AmonRA recovery. They can be found in the Amon Ra thread. That way they still get custom recovery without having to change away from the stock HBoot. (I did this earlier today.)
2. Does the factory reset need to be done in AmonRa or bootloader?
---------- Post added at 05:05 PM ---------- Previous post was at 04:57 PM ----------
jdmba said:
Yes, I understand why people need a patch after running the PHxxxx.zip
I am asking why the PHxxxx.zip leaves that a necessary step. What is missing from the PHxxxx.zip that requires this to be done.
I suspect when VZW releases their RUU, such a step will not be necessary (i.e., it will properly update the firmware). So I am trying to get to the bottom of why the PHxxxx.zip does not properly update the firmware.
Click to expand...
Click to collapse
I'm not sure I follow what you're asking about here. mjh doesn't mention running the PHxxxx.zip at all. If you're S-OFF, you don't need to, as the boot image will already be installed properly in recovery.
If you're S-ON, then you have to run the PH98IMG.zip in bootloader after installing a ROM like CleanROM 4.4. That's for installing the boot image, and more or less the same PH98IMG.zip that is included in the upgrades.
The firmware fix is not a PH98IMG.zip and can be flashed in recovery, regardless of S-ON. If I understand correctly, the latest ICS firmware changes around some of the mount points (and probably other things), and thus the ICS ROMs assume those new mount points. Running the firmware patch just updates the system files to point to the right place given the old firmware. (Please correct me if I'm wrong.) As it's not normally needed (ICS ROM assumes ICS firmware), there's no reason it would be included in the PH98IMG.zip that has the boot image. Plus it's probably a different command than what the boot image flashes -- I'm not sure the bootloader can do more complex control flows like that.
destro158 said:
I'm not sure the bootloader can do more complex control flows like that.
Click to expand...
Click to collapse
Which is the basis of my question ... that a RUU will be able to properly handle the issue and the PHxxxx.zip cannot.
Thanks for trying to answer. Perhaps your last sentence is my answer.
jdmba said:
Which is the basis of my question ... that a RUU will be able to properly handle the issue and the PHxxxx.zip cannot.
Thanks for trying to answer. Perhaps your last sentence is my answer.
Click to expand...
Click to collapse
An RUU will put you on the proper firmware for the ROM you are installing. It doesn't have to deal with the issue of you possibly running a different firmware than what the ROM was built for because it will just install the right firmware.
Almost There
destro158 said:
An RUU will put you on the proper firmware for the ROM you are installing. It doesn't have to deal with the issue of you possibly running a different firmware than what the ROM was built for because it will just install the right firmware.
Click to expand...
Click to collapse
Thanks ... we are getting SUPER close to the answer to my question. I guess the final nail would be .... 'why does the PHxxxxx.zip not do that'
jdmba said:
Thanks ... we are getting SUPER close to the answer to my question. I guess the final nail would be .... 'why does the PHxxxxx.zip not do that'
Click to expand...
Click to collapse
The PH98IMG.zip does fix that. You only need the patch if you're running an ICS Rom (anything based on 3.xx firmware) while still on GB firmware (2.xx and below)
Sent from my ADR6425LVW using XDA
scubasteve85 said:
The PH98IMG.zip does fix that. You only need the patch if you're running an ICS Rom (anything based on 3.xx firmware) while still on GB firmware (2.xx and below)
Click to expand...
Click to collapse
Is there a PH which will also push the ICS firmware at the same time?
jdmba said:
Is there a PH which will also push the ICS firmware at the same time?
Click to expand...
Click to collapse
Yes. The RUU (or whatever you want to call it) just leaked is a PH98IMG.zip that will do the full hboot, firmware, radio, and Rom upgrade and is installed in the bootloader.
Sent from my ADR6425LVW using XDA
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
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Hi everyone,
I have an M8 that has been rooted and has s-off. One of my friends helped me do this. It is at version 4.4.2. When I download the OTA package, it boots to teamwin and when I try to flash the ota package it fails. Is there something that I am missing? Do I need to un-root it and turn s-on? Thanks in advance.
kmac212 said:
Hi everyone,
I have an M8 that has been rooted and has s-off. One of my friends helped me do this. It is at version 4.4.2. When I download the OTA package, it boots to teamwin and when I try to flash the ota package it fails. Is there something that I am missing? Do I need to un-root it and turn s-on? Thanks in advance.
Click to expand...
Click to collapse
You need to revert back to stock recovery. Stock recovery is required to install OTA.
Unrooting is not needed to OTA. Going back S-on is not needed either, and absolutely not recommended.
How would I go about going back to stock recovery? I think I tried this in the past but was never able to get it to work correctly.
kmac212 said:
How would I go about going back to stock recovery? I think I tried this in the past but was never able to get it to work correctly.
Click to expand...
Click to collapse
See is someone has posted it, then flash in fastboot.
You are still on the stock ROM? What software number in Settings>About>Software information?
Alternately, if you don't care about your personal data being wiped and setting up the phone again (there are various ways to backup and restore your data, especially since you are rooted) you can just RUU up to the current OS version.
redpoint73 said:
See is someone has posted it, then flash in fastboot.
You are still on the stock ROM? What software number in Settings>About>Software information?
Alternately, if you don't care about your personal data being wiped and setting up the phone again (there are various ways to backup and restore your data, especially since you are rooted) you can just RUU up to the current OS version.
Click to expand...
Click to collapse
As far as I know it is still the stock Rom. The software number is 1.58.502.1 I would prefer if I did not have to wipe my phone. Thanks for helping, I appreciate it
kmac212 said:
As far as I know it is still the stock Rom. The software number is 1.58.502.1 I would prefer if I did not have to wipe my phone.
Click to expand...
Click to collapse
You can get the stock recovery for that software number here: http://forum.xda-developers.com/att-htc-one-m8/development/att-stock-backups-recoveries-otas-t2855966
If the ROM isn't stock, the OTA will fail and tell you so. You can get the stock ROM backup from the same thread,
redpoint73 said:
You can get the stock recovery for that software number here: http://forum.xda-developers.com/att-htc-one-m8/development/att-stock-backups-recoveries-otas-t2855966
If the ROM isn't stock, the OTA will fail and tell you so. You can get the stock ROM backup from the same thread,
Click to expand...
Click to collapse
I used the stock recovery for the same version as my phone, but now when I go into recovery mode, it is a red triangle with an exclaimation mark. Any suggestions for how to get past this? Thanks!
kmac212 said:
I used the stock recovery for the same version as my phone, but now when I go into recovery mode, it is a red triangle with an exclaimation mark. Any suggestions for how to get past this? Thanks!
Click to expand...
Click to collapse
That is what stock recovery is. You can OTA by booting normally and checking for software update in settings.
redpoint73 said:
You can get the stock recovery for that software number here: http://forum.xda-developers.com/att-htc-one-m8/development/att-stock-backups-recoveries-otas-t2855966
If the ROM isn't stock, the OTA will fail and tell you so. You can get the stock ROM backup from the same thread,
Click to expand...
Click to collapse
So I got my recovery back to stock. I download the update fine but when it goes to reboot into recovery, it starts to update and a little into it, I get a red triangle and I have to reboot my phone. When it comes back up, I get the message saying "There was a problem with this software update that prevented installation." Any suggestions?
kmac212 said:
So I got my recovery back to stock. I download the update fine but when it goes to reboot into recovery, it starts to update and a little into it, I get a red triangle and I have to reboot my phone. When it comes back up, I get the message saying "There was a problem with this software update that prevented installation." Any suggestions?
Click to expand...
Click to collapse
Delete the OTA file (believe it should be in Downloads folder) and try to download the update again.
Or just RUU as I mentioned previously.
redpoint73 said:
Delete the OTA file (believe it should be in Downloads folder) and try to download the update again.
Or just RUU as I mentioned previously.
Click to expand...
Click to collapse
Hi Redpoint, I deleted the OTA file and tried again with the same results. How would I go about RUU? And you mentioned before that this will wipe my device, correct? Will it change me being rooted and having s-off? Thank you so much for the assistance, I really appreciate it
kmac212 said:
Hi Redpoint, I deleted the OTA file and tried again with the same results. How would I go about RUU? And you mentioned before that this will wipe my device, correct? Will it change me being rooted and having s-off?
Click to expand...
Click to collapse
RUUs are linked on my Index thread under "RUUs": http://forum.xda-developers.com/showthread.php?t=2751432
Yes, the RUU will wipe the device. So backup anything you want to keep accordingly.
You can RUU all the way up to Lollipop. Just download the RUU to a PC, connect the phone, and run the RUU executable. The rest is self-explanatory by the RUU program, and very easy.
Since you are s-off, no need to relock the bootloader to RUU. Relocking the bootloader is required to run the RUU with s-on. I know that you are s-off (and this doesn't apply to you), but just wanted to add that in case anyone else reads this and tries it (to avoid confusion).
S-off will remain after RUU.
You will lose root. So after RUU, just install custom recovery again, and root by your desire method again. The same would happen if you updated by OTA.