Hey everyone,
So I have successfully HTC Unlocked my Rezound bootloader, installed Amon Ra, and then installed and booted the CM9 unofficial. Problem was that CM9 wasn't quite as cooperative as I'd hoped - it is unofficial, after all, and so I decided to abandon that in favor of Nils' Business ROM. Here's where I ran into issues.
I have tried everything in every order I can find online and think of, including Nils' writeup. So, for the life of me, I cannot get the leaked ICS RUU to boot (4.03.605.2 as listed in his instructions on XDA). Install runs fine every time I do it from the relocked (I checked) stock HBOOT, all steps included. Every time it reboots (and I've tried forcing it back into hboot to do the install a second time) it just goes to the white HTC screen and starts boot looping. Tried it a million ways, no go. Also worth noting - the stock recovery doesn't install properly, either. Some'fin is hinky, here.
So I've tried just "assuming" it went fine anyhow and then proceeding with the install for Nils' ROM and same deal, no go, although with one difference. With Nils' ROM, it does display the boot splash screen "Nils Business ROM" or what have you about 1 out of every 4 "boots" in the loop cycle, and then reboots again.
I think I am going to perform S-OFF tomorrow if I have the time, and then try it again using the S-OFF instructions, but I would sincerely appreciate any help from you all. Honestly, I'm at near wit's end with this device, and I don't want to be, I enjoy this chase too much, but I *really* want the reward at the end of it, lol.
Any help is deeply appreciated.
- Katie
Re: [Q]
I'm guessing because of the corrupted recovery, you have a bad download of the RUU. Try re downloading and check the md5 hash for a match. The ruu should reboot itself after the first pass and end up in bootloader again for the second pass.... If not then after the first pass just hold down power + vol down to get back to bootloader.
Hope this helps
Sent from my ADR6425LVW using xda app-developers app
Make sure that you have a booting ROM before you s-off. You will cause yourself all kinds of heartache if you don't.
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Snuzzo said:
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Click to expand...
Click to collapse
Hey, thanks. Yeah, the RUU does check out just fine against an MD5SUM.
nm.... just read your original post again and you say you did relock the phone. I was hoping it was something simple like that that was overlooked.
Carry on...
feralicious said:
Nothing to see here, folks, move along.
Click to expand...
Click to collapse
Right now, I cannot S-OFF because it requires a working stock image, and I'll be lucky to get anything more than CM9 unofficial working here.
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
feralicious said:
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
Click to expand...
Click to collapse
Well that's the trick. CM9 didn't work well enough to even be worth backing up. I'm trying to reinstall it again now just to see if I get there - and it looks like I will. Once I'm back up with that, I'm not sure where to go from there. The phone barely worked under CM9. Really hoping to get Nils' ROM on there, since it gives all the nice features of a stock device without the bloatware. Even if I never get S-OFF, I'll be perfectly happy with just Nils' software.
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
feralicious said:
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
Click to expand...
Click to collapse
I did try wiping everything first. No luck. I will try the CleanWipe tomorrow, because right now, whatever my issues are, I'm being prevented from solving them since I can't S-OFF and I can't even seem to get a working ROM to make the phone worth having! Ugh.
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Thank you, your magnanimity! Seriously, lol, you're gracing my thread just by being here. :victory:
feralicious said:
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Click to expand...
Click to collapse
Thanks for the clicky, Feralicious. Same results, unfortunately. I'm going to try doing the RUU flash of Nils' ROM instead. Do you guys know where I can get the ICS firmware by itself? I cannot be sure that it's actually flashed right, unfortunately.
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
I'll do that stuff and let you know. Thank you!
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
ncc74656m said:
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
Click to expand...
Click to collapse
My DNA said something about failing when I locked it. But it locked just fine.
Since it is failing.
fastboot oem rebootRUU
fastboot oem lock ----if unlocked
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Should work Maybe
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
Click to expand...
Click to collapse
Ok, so, this part including a factory reset got me to "HTC Quietly Brilliant" screen, but then it bootloops again. Tried factory resetting again to no avail. Trying the second part.
Flyhalf205 said:
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Click to expand...
Click to collapse
Same thing as before unfortunately. :/ Performed a factory reset afterwards to be safe - no go. Everything shows OK though in both this and the above install. *shrug*
Flyhalf205 said:
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
ncc74656m said:
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
Click to expand...
Click to collapse
I really wouldn't see why you would need a Sense rom to get s-off. I would imagine it would just need su and busybox installed. But nandroid then try a sense rom again. Make sure you flash the boot.img through fastboot
Related
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
I had much the same problem with my cdma, hboot 1.5, S-On shooter. When I was S-On none of the ICS roms would work. The all bootlooped on me. If you follow the rooting method found here on xda, it will get you back to a stock Rooted GB Rom.
go into hboot -> fastboot USB-> run command dos -> fastboot cwm-4.0.1.4-shooter.IMG -> flash the 2.17 firmware-> enjoy.
I had to S-off with Juopunutbear, then re-run that root/flash to get past the bootloops.
Sent from my Shooter using xda app-developers app
Unfortunately I have tried that and it still is not working.
My only suggestion would be to try it a few times, other then that, its above my head.
Sent from my shooter using xda app-developers app
rookiemistake said:
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
Click to expand...
Click to collapse
Have you tried one of the ruu exe files that you run from your computer? If you are trying to go stock, you should be able to relock the bootloader and run the ruu and that's it.
Sent from my ICS 3VO with Tapatalk 2
First of all I want to thank everyone that has been attempting to assist me with my problem. I have tried to relock since I am on htcdev unlock and then run an ruu force via my computer. I get an installation aborted error when trying to flash pg86img via recovery. I don't know what else to say.
You can't flash a bootloader zip from recovery. You have to flash it from hboot. Also make sure the zip is named correctly "PG86IMG.zip" without the quotes. Also make sure the zip is on the root of your sd as in not in any folders. Once you've named the zip correctly and placed it correctly then power off the phone. Hold down the volume down button and tap the power button. You should boot into the bootloader wait until the phone recognizes the zip and follow the on screen instructions. Hopefully this helps.
#Root-Hack_Mod*Always\=LTE
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
rookiemistake said:
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
Click to expand...
Click to collapse
To get the ota release (if it ever comes ) I do believe you will need to be locked and running the existing gingerbread rom. While I am not positive, I think the system uses the props file to determine if an update is applicable, and it will likely not recognize the teamgenesis rom version as being upgradeable.
Now I will likely get flames for saying this, but if you want to put the meanrom v2.4 of ICS on the phone, it can be done with s-on, you just need to follow the correct process. I ran that rom for a while, and it is very stock like, stable, and has a few enhancements that you will not find on a non-rooted stock rom. I never found anything wrong or not working with that rom.
To get it to load, first I downloaded flashimagegui from market, put the meanrom zip file on the sd card and made sure I had a recovery that I could get into. I am using TWRP v2.1.1, lots of folks talk about others like ext4, and I am only going to say use whichever you like, after all it is your phone.
Then with the phone unlocked via the htc method, I started the flashimage app, and browsed to the meanrom file. It extracted the kernel and flashed it. Once that was done, with clear cache buttons selected, rebooted to recovery, and used the install menu selection of TWRP to again flash the same rom file. Once it flashed the file, selected clear cache and dalvik just to be safe, selected reboot system, and it worked great.
Have a great weekend.
So, apparently I am still doing something wrong. I have put the pg86img on the root, relocked to the bootloader, and let it run it's course. However, it will get through with reading it and stops and does not finish anything with loading the system information. I have also tried to run the ruu via usb connection. I keep running into a c++ issue saying runtime error. I have wiped everything and thankfully I did make a backup of the rom and other information that I was runing so I can currently fall back on that.
I am on hboot 1.5, 2.17, and teamgenesis ICS rom for evo 3d.
Apparently there have been rumors that Sprint has finally released the ICS OTA, not that it really matters anymore, but I have run into a few interesting glitches, such as WIFI not staying connected while asleep or disconnecting.
If I have to I am willing to pay to do a netmeeing with someone in order to be able to fix this.
Sorry if it sounds like I am getting frustrated, but I have tried every walkthrough that I have found and have not had any luck with any of them.
Please help.
I forgot to say I am s-on
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
jeggen said:
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
Click to expand...
Click to collapse
So now I'm just in a boot loop. I relocked, installed stock recovery and ran RUU. When I did that I booted just long enough that I could almost slide the ring to unlock before I rebooted. Then the device just constantly reboots.
I unlocked again, installed TWRP 2.2.2.0 in case there was a bug causing flashing issues. Recovery boots just fine now. I flashed Stock Rooted DeOdexed 1.22.651.3 from here since that was the version I had before this whole fiasco. I'm going to try to restore backup again but don't know how to get out of this horrible mess. Worse part about it is that it's my wife's phone! Help please!
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
metalfan78 said:
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
Click to expand...
Click to collapse
I reflashed stock recovery, relocked bootloader (fastboot oem lock), ran RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3_Radio_1. 05.11.0606_NV_SPCS_2.45_003_release_268323_signed. exe), and still had the boot loop problem. RUU said it completed but the bootloader still said "relocked". Isn't RUU supposed to totally wipe and restore the entire device?
I recall on my old EVO there was a zip you could place in the SDcard that the bootloader automatically looked for and would use to reflash to factory everything. Is there a way to do this with the EVO 4g LTE?
Is it possible that radios/firmware somehow got borked even though I am on S-ON? Is there a way to reflash them from bootloader?
Just thinking through ideas I'd try next and something that could possibly help recover or at least put me in a position to go back to Sprint for help.
Could have been a bad download. I think there is info on re locking in the development sticky section. It might give you some more information on what to do next.
"We're coming from a pure power source"
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
jeggen said:
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
Click to expand...
Click to collapse
I sent you a PM
Sent from my EVO using xda premium
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
jeggen said:
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
Awesome glad you got it fixed.
Sent from my EVO using xda premium
Hi,
I have a Sprint CDMA HTC EVO 3D. I tried root and get S-OFF for it. Unfortunately I failed and now the phone fail to boot.
Below is what I did from which you might be able to diagnose it and give me suggestions.
(1) The original status of mu phone is:
Stock rom, I never root it before.
HBOOT-1.58.0000
Android Version: 4.03
HTC Sense version: 3.6
Software version: 2.95.651.6.710RD
(2) My root procedures:
I followed this post: http://forum.xda-developers.com/showthread.php?t=1813818
I successfully unlocked phone with HTCDev, successfully Flashed 4EXT recovery, and successfully installed Superuser-3.1.3-arm-signed.zip. I also booted into sytem, everything worked well.
However I failed in next step of JuopunutBear's Wire Trick (S-OFF). When I ran ControlBear.exe, it finally hanged there.
Current status of my phone:
Unfortunately I did not make a backup to my original ROM, so there is no way to revert back by restoring backup.
Now the phone is in unlocked status, I was able to boot to HBOOT and also enter 4Ext recovery, however I am not able to boot into Android. If I try to boot into Android, it always hang at black screen.
I am able to boot to fastboot (USB) mode, I tried to flash some stock ROM (listed at http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209), but I failed. For example, I ran a RUU of 2.89.exe, it detected my phone version is 2.95, and further update RUU failed.
Looks like my partition is ruined, but I might be wrong.
ANyone can help me to restore my phone to working status? At least I need the phone to be able to boo to Android.
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
lsdyna said:
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
Click to expand...
Click to collapse
EDIT:
Okay. I've got some questions.
1. You're stuck on some black screen as you said. It boots past the white HTC splash and then it's stuck on that black screen, right. Do you mean the juopunutbear "arrow screen" - juopunutbears boot.img?
2. I think if you had flashed the original boot img everything would have been fine.
3. The easiest way is to flash to stock, so lets try to figure out why it doesn't flash.
MrJyrks said:
Okay. So from what I understood, you are stuck on the black juopunutbear screen, right?
Click to expand...
Click to collapse
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
lsdyna said:
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
Click to expand...
Click to collapse
And you can boot to recovery, right?
EDIT:
One more thing. Which ruu were you trying to run
Edit2:
What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Edit3:
BTW, this was on the wire trick page... http://unlimited.io/jbtroubleshooting.htm - TROUBLESHOOTING There was everything you needed to know when you failed at something. Remember that page. You may need it the next time you try to do the wiretrick.
Q: Were you using a linux distro for the wire trick and did you use the appropriate files for wire trick since GB and ICS have separate tools?
If you want I may assist you in gaining s-off if we get this thing functional again.
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
MrJyrks said:
And you can boot to recovery, right?
EDIT: One more thing. Which ruu were you trying to run
Edit2: What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Click to expand...
Click to collapse
lsdyna said:
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
Click to expand...
Click to collapse
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Edit: This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Now I only want to revert my phone to stock, not considering root at present time.
I searched 2.95 ROM, unfortunately the highest version that I can find is 2.89. Does this mean I have no way to revert my phone to live? Thanks a lot.
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
lsdyna said:
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
Click to expand...
Click to collapse
If you have access to the recovery, most likely, yes.
Hello MrJyrks,
Thank you so much for the link! I am eager to try that. Before I do that I think I shall ask two questions to avoid further mess up the device:
Question #1: To install the deodexed rom, which is the correct way:
(1) Rename the ZIP file to PG86IMG.ZIP, put to root of sdcard, then boot, letting the Bootloader to do the update.
(2) In 4EXT recovery, enable smartflash, enable script asserts, then install the zip from the root of sdcard.
Question #2: You said I shall flash boot image, can you tell me how to do this? I mean, where shall I get the boot image file? Flash it with 4EXT? SHall I do it before or after install ROM zip file?
Thank you very much for your helps!!!
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I tried install the stock ROM from your link (using 4EXT with smartflash enabled and script asserts enabled.) . Amazing that installation completed successfully (indeed this is the first ROM zip that I was able to install successfully since I mess up the device). When I exit After that, it did some further update which I guess is the boot.img that you mentioned.
4EXT it said 'a pending update for your boot partition is detected' and I think it was doing the boot image flash that you mentioned, right?
Unfortunately when I boo the device, I still got black screen.
Now I am unlocked and also rooted (since I successfully installed superuser in 4EXT). DO you think I shall lock the devioce before installing the stock ROM? If so, one possible issue is that if I relock the device, I found 4EXT is not available. In that case, how shall I install the ROM zip file?
Thanks.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
Further update:
I flashed boot image by: fastboot flash boot boot.img which is included in the stock ROM zip file.
The flash went successfully. However, I am still not able to boot to Android. WHat I have is the device hang there, alternatively displaying logo with white background, and black screen.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
lsdyna said:
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
Click to expand...
Click to collapse
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
MrJyrks, thank you so much!!!
MrJyrks said:
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
Click to expand...
Click to collapse
Similar problem, can't return to stock
I have a problem similar to lsdyna's, and am hoping that even though this post is old, MrJyrks or someone might be able to help me.
I am unsuccessfully trying to return my phone to stock. First a bit of history.
I had 2.95.651.6.710RD s-on hboot 1.58 Android Version: 4.03 HTC Sense version: 3.6 on my phone, and wanted root. I didn't need s-off, just wanted to root so could do some tweaking (stop some apps from autostarting, stop some form getting network access, etc.) so loaded 4EXT Recovery Touch, and got root (fastboot oem get_identifier_token method), got superuser in there, and happily began tweaking. Famous last words... I didn't make a backup right away (learned my lesson!) and suddenly found a 'overtweaked' sluggish phone on my hands.
Thought best thing would be to lose the root & return to stock & start over, carefully, making backups.
So I used Fastboot (fastboot oem lock) to lock it (worked) and proceeded to try to load RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe into it [via my computer], but didn't realize until reading MrJyrks post that a lower RUU couldn't be used.
I now am relocked (phone does boot up, but can tell the system tweaks are still slogging it), lost the recovery, and wondering what to do... do I try putting recovery back in & using the Negalite 2.95 stock deodex ROM MrJyrks mentioned? If so, how do I use that zip file method verses the exe one I tried thru my computer?
Thanks for the help
You had issues with the RUU because your main version is higher than that contained in the RUU.
Unlock, flash recovery again. Boot into recovery and flash this zip: https://copy.com/wlVvwssXXNN00Pe
That will lower your main version. Relock the bootloader, put the phone into fastboot USB mode, then run the RUU while in fastboot USB mode.
Should be back to stock after that.
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
I had already had my phone's bootloader unlocked and rooted and had a GPe ROM installed and worked perfectly. THEN I saw that you could literally make it a Google Play edition phone complete with OTA and worked on trying to achieve that. Getting my phone S-Off wasn't working because I believe of my HBOOT version (1.55) so I was told to download this stock ROM that would downgrade me to reach a version that I could then run revone to achieve S-OFF.
POST: http://forum.xda-developers.com/showpost.php?p=45487258&postcount=55
I ran a backup through TWRP first and then flahsed this ROM, which has kept my HTC One at the HTC One splash screen. I connected it to my computer/ADB and got it into the bootloader to go into custome recovery BUT the recovery takes me to a black screen with a phone and red triangle, so it's like my recovery isn't there anymore. Fine.
I download the latest TWRP for my phone(triple checked) and ran the fastboot flash recovery command through ADB but it says
"(bootloader) signature checking...FAILED (remote: signature verify fail)"
is there some sort of way to disable the signature check using ADB or am I actually going about this the wrong way?
I'll admit, I don't do this stuff oftem, so ask as many questions as needed as I probably left out details you may need
I may be wrong but you may have to re-lock the bootloader and run the ruu back to stock.
nandroid backup restore won't change the hboot so I don't think you'll have any luck there.
I'm running ARHD 40 just till we can find a way to run s-off on our AT&T devices.
noobsquared said:
I may be wrong but you may have to re-lock the bootloader and run the ruu back to stock.
nandroid backup restore won't change the hboot so I don't think you'll have any luck there.
I'm running ARHD 40 just till we can find a way to run s-off on our AT&T devices.
Click to expand...
Click to collapse
Not to sound n00b-ish, but what would be the best way of doing this?
EDIT: Actually it is relocked already! Duh! On the bootloader screen it says "TAMPERED" and then "RELOCKED" below that
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
noobsquared said:
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
Click to expand...
Click to collapse
I actually had that downloaded but I was just concerned if that was the right move since it wipes the phone.
noobsquared said:
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
Click to expand...
Click to collapse
I hate to say this actually, but I can't find that .exe in the link. I don't know exactly what I'm looking for in it.
h_smith said:
I hate to say this actually, but I can't find that .exe in the link. I don't know exactly what I'm looking for in it.
Click to expand...
Click to collapse
Here you go:
http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
You can always unlock the bootloader again, install twrp and try to boot and see if that works.
Install the nandroid backup matching your system and you can then get to your data.
noobsquared said:
You can always unlock the bootloader again, install twrp and try to boot and see if that works.
Install the nandroid backup matching your system and you can then get to your data.
Click to expand...
Click to collapse
But how would I do that if I can't even boot up the phone past the splash screen? I did all of the unlocking and TRWP installing via the phone
Downloading and installing the file right now. It's going slow as hell but I'll run when I get the chance
THANK YOU FOR STICKING WITH ME!
h_smith said:
But how would I do that if I can't even boot up the phone past the splash screen? I did all of the unlocking and TRWP installing via the phone
Downloading and installing the file right now. It's going slow as hell but I'll run when I get the chance
THANK YOU FOR STICKING WITH ME!
Click to expand...
Click to collapse
Sure thing man. It's stuck at that screen because when your phone is unlocked, it allows custom recovery but when it's locked, it won't boot unless it finds the stock recovery. I am not 100% sure but I've had that issue as well. I had to run the RUU to get back to stock since you can't lock the bootloader with custom recovery and expect it to boot. It may vary from device to device but I've always had to RUU back to stock or fastboot flash stock recovery to get past that screen before you lock the bootloader. You can try again, there is stock recovery posted by someone in forums. Download that, try to go in fastboot mode and try fastboot flash recovery recovery_name.img. I think once you've locked the bootloader it may not work but worth a shot.
noobsquared said:
Sure thing man. It's stuck at that screen because when your phone is unlocked, it allows custom recovery but when it's locked, it won't boot unless it finds the stock recovery. I am not 100% sure but I've had that issue as well. I had to run the RUU to get back to stock since you can't lock the bootloader with custom recovery and expect it to boot. It may vary from device to device but I've always had to RUU back to stock or fastboot flash stock recovery to get past that screen before you lock the bootloader. You can try again, there is stock recovery posted by someone in forums. Download that, try to go in fastboot mode and try fastboot flash recovery recovery_name.img. I think once you've locked the bootloader it may not work but worth a shot.
Click to expand...
Click to collapse
Thank you. I'm downloading the .exe and will post the results. But it looks like that might take a few hours :/
hey is there another link? that one is so slow and keeps timing out :/
You can either use download manager or chrome browser is pretty good at managing that.
Try this: http://d-h.st/VWf
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
I just did a google search for the term RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_R and gave you the second result I got. Just search for the name of the file and you will find plenty of links.
Hope that helps.
This sounds like the exact same problem I had. The RUU and directions solved that one for me too...
Link to RUU: http://www.htc.com/us/support/news.aspx?p_id=628&p_name=htc-one-att
Other thread: http://forum.xda-developers.com/showthread.php?t=2492266
THANK YOU NOOB!!
I managed to get it fixed. Turns out HTC hosted that exact file so I downloaded it and it fixed my phone. Good times..