Well guys im absolutely stumped. I bought a DNA off ebay in hopes of unbricking it and getting it back in business. My goal is to put STOCK VZW rom back on it. Im absolutely puzzled as to what im doing wrong here. The Phone will only boot in bootloader mode. It is recognized in ADB. (Please forgive me if im using wrong terminology) Ive downloaded the STOCK RUU. Once the device is plugged in and I open the RUU and get to the part where it ask me to update the image. Both fields are blank. There is nothing in either fields. When I click update ROM my computer just crashes and gets hung. As far as some additional info, My bootloader was UNLOCKED and is now relocked, has S-ON and HBOOT 1.33.0001. Any suggestions as to what im doing wrong. I just want a stock DNA back.
xbcustoms said:
Well guys im absolutely stumped. I bought a DNA off ebay in hopes of unbricking it and getting it back in business. My goal is to put STOCK VZW rom back on it. Im absolutely puzzled as to what im doing wrong here. The Phone will only boot in bootloader mode. It is recognized in ADB. (Please forgive me if im using wrong terminology) Ive downloaded the STOCK RUU. Once the device is plugged in and I open the RUU and get to the part where it ask me to update the image. Both fields are blank. There is nothing in either fields. When I click update ROM my computer just crashes and gets hung. As far as some additional info, My bootloader was UNLOCKED and is now relocked, has S-ON and HBOOT 1.33.0001. Any suggestions as to what im doing wrong. I just want a stock DNA back.
Click to expand...
Click to collapse
It appears that this has the ENG Boot on it, When it powers up it says something about being illegal to distribute outside of HTC, but then immediately goes into boot loader mode.
xbcustoms said:
It appears that this has the ENG Boot on it, When it powers up it says something about being illegal to distribute outside of HTC, but then immediately goes into boot loader mode.
Click to expand...
Click to collapse
That's not eng hboot. If it's s on it can't have eng hboot.
Sent from my HTC6435LVW using xda app-developers app
if it is unlocked flash twrp with fastboot and flash a rom from recovery.
xbcustoms said:
As far as some additional info, My bootloader was UNLOCKED and is now relocked, has S-ON and HBOOT 1.33.0001.
Click to expand...
Click to collapse
123421342 said:
if it is unlocked flash twrp with fastboot and flash a rom from recovery.
Click to expand...
Click to collapse
Wonder if it got locked while on something it shouldn't have been.
Who relocked it, you or the seller/previous user?
I know in some cases relocking a boot loader on a custom recovery and kernel/ROM basically renders the device useless as it can't boot in either direction if it doesn't have fast boot available.
Perhaps the better course here is to fast boot a stock recovery to it, and maybe a stock boot.img, but it'll maybe take a few tries to find the right version to pass, unless the hboot version is ROM version specific.
Just an idea.
Tapatalked from my HTC DNA - ReVolt
I'm getting ready for a job interview and read this thread too fast, but send me a PM if you would like my help and I will help you get things figured out later today.
I put the badass in Team BAMF
CharliesTheMan said:
I'm getting ready for a job interview and read this thread too fast, but send me a PM if you would like my help and I will help you get things figured out later today.
I put the badass in Team BAMF
Click to expand...
Click to collapse
I am in the SAME boat with this phone.. How did you guys make out? LOCKED bootloader, S-ON.
I had this same problem as well. I was able to get it to boot by flashing the 2.06 firmware found here: http://forum.xda-developers.com/showthread.php?t=2314771
Someone had a custom rom on this DNA, and somehow relocked it with it on. So now, I have a custom rooted rom, but I cannot get the Moonshine (fails on temproot- maybe because its already rooted?) or Revone to work to clean up the mess.
Related
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
wards.jfasa said:
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
Click to expand...
Click to collapse
im going to say a bad ruu re unlock and start over i dont know if its on xda too but on scotts roms site it has info to lock without the re locked showing good luck
I am having the same problem, but I found a way around it. If I boot the kernel through fastboot it will boot up. (You'd need to re unlock). My hboot doesn't really work anymore..
------
3(d)vo one s
Newts my hero.
evo bryan said:
im going to say a bad ruu re unlock and start over i dont know if its on xda too but on scotts roms site it has info to lock without the re locked showing good luck
Click to expand...
Click to collapse
Im not even sure at this point how to re-unlock it. i am wondering if i should have flashed to an older ruu though.
How do I extract the kernel from the ruu? or is there a download available? I have searched....just cannot find it.
wards.jfasa said:
How do I extract the kernel from the ruu? or is there a download available? I have searched....just cannot find it.
Click to expand...
Click to collapse
flashimage gui is able to do it inside android, im guessing it stores it in a tempory folder, let me see if i can find the temp folder where it stores before rebooting to flash it...........brb
did you check this post http://forum.xda-developers.com/showthread.php?t=1627897
This helped me out when I was Juopunutbear S-OFF'ing my phone. But I was at Hboot 1.50.
http://androidforums.com/evo-3d-all...mware-upgrade-ruu-flash-unbricking-guide.html
Pretty good guide.
wards.jfasa said:
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
Click to expand...
Click to collapse
The security warning is because you are using a custom rom so will not be able to use the RUU through the bootloader.
What you need to do is download the RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00. 1216_signed.exe from here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
If you then run that exe while your phone is in fastboot and connected to your pc it will factory reset your phone and put you back on stock rom and kernel.
I have a good friend who recieved the OTA today for ICS on his Rezound, he isn't too keen on the rooting world but wanted all of the benefits so he had one of our mutual friends root the device for him, in doing so the improperly flashed a ROM and eventually had to re-flash his phone back to stock.
so now his S boot it ON and he has RELOCKED on his bootloader in pink. His device is however rooted, so anyways whenever he goes to update his phone to ICS it goes into the bootloader and cannot install the OTA.
Im sorry the vague details but I am trying to better understand his issue, I have a thunderbolt and am somewhat familiar with the htc devices, it also doesn't help that the person who originally rooted and unlocked his phone as well as relocked it is out of town at the moment so I am trying to do the best I can to assist him. Thanks for any help!
Jabberwocky237 said:
I have a good friend who recieved the OTA today for ICS on his Rezound, he isn't too keen on the rooting world but wanted all of the benefits so he had one of our mutual friends root the device for him, in doing so the improperly flashed a ROM and eventually had to re-flash his phone back to stock.
so now his S boot it ON and he has RELOCKED on his bootloader in pink. His device is however rooted, so anyways whenever he goes to update his phone to ICS it goes into the bootloader and cannot install the OTA.
Im sorry the vague details but I am trying to better understand his issue, I have a thunderbolt and am somewhat familiar with the htc devices, it also doesn't help that the person who originally rooted and unlocked his phone as well as relocked it is out of town at the moment so I am trying to do the best I can to assist him. Thanks for any help!
Click to expand...
Click to collapse
Run the ICS RUU on it
Sent from my Galaxy Nexus
instructions
do you have any instructions for flashing an ICS RUU?
Jabberwocky237 said:
do you have any instructions for flashing an ICS RUU?
Click to expand...
Click to collapse
Check my thread, you can download it, then rename it PH98IMG.zip, put it on the SD card not in any folders, and then boot into hboot, and accept the prompts, make sure it reboots 3 times
I did.
Followed the instructions in this post:
http://forum.xda-developers.com/showpost.php?p=25165453&postcount=1
RUU, S-ON, check for update, and it updated.
Do you have to be on stock recovery to flash the ICS RUU or is ok to be on Amon Ra? As long as you are relocked it should work right?
*---(___() said:
Do you have to be on stock recovery to flash the ICS RUU or is ok to be on Amon Ra? As long as you are relocked it should work right?
Click to expand...
Click to collapse
Yes, it will replace your recovery with stock. It's all part of the RUU image.
*---(___() said:
Do you have to be on stock recovery to flash the ICS RUU or is ok to be on Amon Ra? As long as you are relocked it should work right?
Click to expand...
Click to collapse
YES...on stock recovery!!! There is a thread in the General SEction for all questions pertaining to OTA...its great...everything is consolidated including great FAQ's and some directions and links.
Hi,
I already had an unlocked bootloader but I installed a ROM that updated my HBOOT to 1.58 LOCKED. Now I was trying to wipe that with a super wipe and now I'm stuck being unable to get to the recovery (it just brings me back to the bootloader) and my normal start up is stuck at the HTC logo. Can anybody tell me what I should do? What direction I should go into fixing this? I already had s-off from before.
Thank you.
jaku78 said:
Hi,
I already had an unlocked bootloader but I installed a ROM that updated my HBOOT to 1.58 LOCKED. Now I was trying to wipe that with a super wipe and now I'm stuck being unable to get to the recovery (it just brings me back to the bootloader) and my normal start up is stuck at the HTC logo. Can anybody tell me what I should do? What direction I should go into fixing this? I already had s-off from before.
Thank you.
Click to expand...
Click to collapse
You probably don't have recovery. There are many threads on "how to install recovery"..Also, you have this: (It works on both CDMA - which you have, I suppose, and GSM)
Also, you have some interesting stuff HERE
What pro said. Also, if you're s-off, the locked bootloader doesn't matter. If you have trouble after trying to flash a recovery, you could also run the ruu.exe to reset everything back to stock (you'll stay s-off) and then flash a new hboot and recovery and then custom ROM. I did that recently and it fixed my issues.
Thanks for the fast replies both of you. That's really interesting situation because I know I had recovery before. You think I should still go for it?
EDIT: Looking at that video it looks like its installing an app, my phone won't get past booting up. Basically all I got is my HBOOT. I'm going to try what coal suggested.
What Coal told me to do worked, I'm back into stock and it boots up fine now. I'm going to try to get a new hboot and recovery now.
I was able to get down to 1.4 HBOOT again and flashed a CM10 ROM. Thanks for your help guys, you lead me in the right direction
You are welcome..
Sent from my Evo 3D GSM using xda premium
jaku78 said:
Thanks for the fast replies both of you. That's really interesting situation because I know I had recovery before. You think I should still go for it?
EDIT: Looking at that video it looks like its installing an app, my phone won't get past booting up. Basically all I got is my HBOOT. I'm going to try what coal suggested.
What Coal told me to do worked, I'm back into stock and it boots up fine now. I'm going to try to get a new hboot and recovery now.
I was able to get down to 1.4 HBOOT again and flashed a CM10 ROM. Thanks for your help guys, you lead me in the right direction
Click to expand...
Click to collapse
You would just have flashed another recovery using a PG86IMG.zip. or fastboot ..
---------- Post added at 10:18 AM ---------- Previous post was at 10:17 AM ----------
coal686 said:
What pro said. Also, if you're s-off, the locked bootloader doesn't matter. If you have trouble after trying to flash a recovery, you could also run the ruu.exe to reset everything back to stock (you'll stay s-off) and then flash a new hboot and recovery and then custom ROM. I did that recently and it fixed my issues.
Click to expand...
Click to collapse
The "LOCKED" or "RELOCKED" status matters if you are trying to flash boot,recovery partitions etc using fastboot.
mnomaanw said:
The "LOCKED" or "RELOCKED" status matters if you are trying to flash boot,recovery partitions etc using fastboot.
Click to expand...
Click to collapse
I agree that it matters, but you can gain access to those fastboot commands if you are S-OFF by flashing a custom recovery such as JBear, Revolutionary, or the engineering (ENG) bootloader, at least on the CDMA model of the Evo 3D/V. I highly recommend that over unlocking the bootloader since having a locked hboot makes it much easier to return to 100% stock. Not so much with relocked since the only way to get rid of that status is to set S-ON and do the wire tick.
ramjet73
Hey guys. Yes I have searched, but have only found instructions so far for going back to stock gingerbread.
I need to send my amaze in to get fixed under warranty, and I'm assuming they won't like it if I send them the phone with an unlocked bootloader, rooted, and CM10 installed, and that's what I need help with. How can I reinstall stock ICS, unroot, and lock the bootloader of the amaze? And will it show as "relocked" or "locked"? Of course I plan on putting the root and unlocked bootloader and CM10 once I get it back, so I'm looking for a reversible way to do this. Thanks in advance!
Just to be clear. For your bootloader to say 'locked' you'll need to have S-Off and NOT unlock the bootloader again. But once that's done just flash the ICS ruu. Here's a link
http://forum.xda-developers.com/showthread.php?t=1647728
Double0EK said:
Just to be clear. For your bootloader to say 'locked' you'll need to have S-Off and NOT unlock the bootloader again. But once that's done just flash the ICS ruu. Here's a link
http://forum.xda-developers.com/showthread.php?t=1647728
Click to expand...
Click to collapse
Thank you. So I am S-ON right now. In order to make the bootloader say "locked" again to make HTC happy with my warranty, I'd have to be stuck with ICS and whatever updates HTC decides to give us from then on once I got it back from HTC?
No. That's the only way for it to say "locked" if you relock it it will say "relocked"
So if you really want it to say "locked" you'll need to S-Off first. Then flash the RUU.
Once you get it back you can do as you feel.
bruner1981 said:
Thank you. So I am S-ON right now. In order to make the bootloader say "locked" again to make HTC happy with my warranty, I'd have to be stuck with ICS and whatever updates HTC decides to give us from then on once I got it back from HTC?
Click to expand...
Click to collapse
What makes you think you will be stuck with anything? Everything u need to do is reversible and then re-doable.
Im just not really sure which part u think would make it stuck. Let us know and im sure we can explain the cofusion
After unlocking the bootloader with S-ON and installing a custom recovery/rom how do you revert to Stock.
I've tried relocking the bootloader, and using the AllinOneToolkit by Hanson to install the Factory RUU but it keeps failing after the HTC boot logo appears and the zip RUU file gets transferred to the phone. Keeps saying Failed with 12 signatures or something.
Then I read with S-ON that you had to use Hanson's tool and perform Fix Mainver, but that doesnt do anything either. Keeps saying, error cannot find device.
So, how do I go back to Stock?
Would appreciate any help!
Boot into fastboot, type "fastboot OEM lock" in the command prompt. Put the appropriate RUU on your external SD card and rename it PH85ING.zip and boot into bootloader.
Edit: its PH85IMG.zip. sorry about my fatty fingers. Also, make sure to check the md5 sum on the RUU. I always had trouble with the download.
Sent from my HTC Ruby using xda app-developers app
fubag said:
After unlocking the bootloader with S-ON and installing a custom recovery/rom how do you revert to Stock.
I've tried relocking the bootloader, and using the AllinOneToolkit by Hanson to install the Factory RUU but it keeps failing after the HTC boot logo appears and the zip RUU file gets transferred to the phone. Keeps saying Failed with 12 signatures or something.
Then I read with S-ON that you had to use Hanson's tool and perform Fix Mainver, but that doesnt do anything either. Keeps saying, error cannot find device.
So, how do I go back to Stock?
Would appreciate any help!
Click to expand...
Click to collapse
Fails after htc boot logo? If you are flashing an RUU, you should never see any boot screen until after its done flashing. What carrier are you on and what steps exactly r u fillowing to flash the ruu...?
aj_2423 said:
Fails after htc boot logo? If you are flashing an RUU, you should never see any boot screen until after its done flashing. What carrier are you on and what steps exactly r u fillowing to flash the ruu...?
Click to expand...
Click to collapse
its not the actual boot logo but that black screen with the HTC logo that I think is part of the stocky recovery maybe?
I have yet to try the PHS.IMG method in fastboot.
Thanks for the help!
fubag said:
its not the actual boot logo but that black screen with the HTC logo that I think is part of the stocky recovery maybe?
I have yet to try the PHS.IMG method in fastboot.
Thanks for the help!
Click to expand...
Click to collapse
Lol what do you mean you havent tried it? Flashing the PH85IMG.zip though the bootloader is the ONLY way to flash the RUU.
If you are on tmo follow this
http://forum.xda-developers.com/showthread.php?p=24294337
Sent from my
aj_2423 said:
Lol what do you mean you havent tried it? Flashing the PH85IMG.zip though the bootloader is the ONLY way to flash the RUU.
If you are on tmo follow this
http://forum.xda-developers.com/showthread.php?p=24294337
Sent from my
Click to expand...
Click to collapse
This only applies to tmobile versions? What about if we are on another carrier, I tried renaming the OTA updates but it doesnt do anything.
fubag said:
This only applies to tmobile versions? What about if we are on another carrier, I tried renaming the OTA updates but it doesnt do anything.
Click to expand...
Click to collapse
noo it has nothing to do with what carrier you're using at the moment...
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