So I am trying to Un-Root my HTC DNA, and I was following these steps
http://forum.xda-developers.com/showthread.php?t=2017525
But when I'm running the RUU, i get an error 155: Unknown error.
Telling me to get the correct ROM Update Utility, but i can't find it anywhere but on that website.
Once the RUU Update has failed and I restart the phone,it goes straight into boot menu with ****TAMPERED*****. ******RELOCKED******, and *******Security Warning******* At the top and when I try to do a factory data reset on the phone, it goes into the fastboot menu, with the same notifications uptop.
Any idea what might be going on?
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
cmay227 said:
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
Click to expand...
Click to collapse
I have tired to do it in all three of my USB Ports.
All i can say is try starting the RUU.exe and have your phone booted normally. not in fastboot. it worked for me both ways. might be something to try. If it fails again try re-downloading the file, rinse and repeat.
cmay227 said:
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
Click to expand...
Click to collapse
Pretty sure you can't relock unless you used htcdev.
As Adryn said if you used htcdev I'm pretty sure we can still "relock" but the exploit has permanatly changed the CID of all our phones. So fastboot oem lock still works and the ruu will revert the phone to its "stock" state as in factory shipped software and bloat but the bootloader will still reflect that it has been tampered with and the same token can be used to unlock again immediately afterward. So what I'm saying to all others is that the exploit is irreversible. There were a couple guys toying with it in the irc yesterday. But unless you absolutely have to do this theres really NO reason because you won't be able to cover the tracks of the hacking you've already done to your phone.
jonesin said:
As Adryn said if you used htcdev I'm pretty sure we can still "relock" but the exploit has permanatly changed the CID of all our phones. So fastboot oem lock still works and the ruu will revert the phone to its "stock" state as in factory shipped software and bloat but the bootloader will still reflect that it has been tampered with and the same token can be used to unlock again immediately afterward. So what I'm saying to all others is that the exploit is irreversible. There were a couple guys toying with it in the irc yesterday. But unless you absolutely have to do this theres really NO reason because you won't be able to cover the tracks of the hacking you've already done to your phone.
Click to expand...
Click to collapse
To me the main benefit of running the RUU was to get rid of the Tampered status in the boot loader screen. But your right it will say Relocked instead of locked. no way around that......so kinda pointless warranty wise.just removes root
Well I'm in the process of redownloading the RUU file.
I am still kind of curious, how come I can't reset to factory default through the boot loader or though the settings -> restore feature? Does it have to do with being rooted?
If you don't have a good reason to unroot, I would encourage you to wait. Those have have unrooted, and relocked, have had problems unlocking a second time.
I've locked and relocked many times and It was a pain in the ass to get unlocked status back. I would get the unlock prompt on the phone and choose yes but it ended up always still saying relocked. I finallly read to shut phone down completly before going into fasboot. I was just choosing restart. Have not had a issue unlocking since. Unlock code takes everytime.
Sent from my HTC6435LVW using xda app-developers app
OP, if you're attempting to get the 'locked' message on the bootloader back, you won't (as others have stated,) but if you're trying this to get your warranty back, the persons at Verizon won't look at this when you return the device. Neither will the people at the Verizon corporate office. All they will do is completely reflash the device including bootloader and that will be that.
Mazer
Sent from my rooted and debloated Droid DNA.
Mazer_R said:
OP, if you're attempting to get the 'locked' message on the bootloader back, you won't (as others have stated,) but if you're trying this to get your warranty back, the persons at Verizon won't look at this when you return the device. Neither will the people at the Verizon corporate office. All they will do is completely reflash the device including bootloader and that will be that.
Mazer
Sent from my rooted and debloated Droid DNA.
Click to expand...
Click to collapse
Thanks from the reply. I mainly wanted to un-root it to 1) Check for updates an 2) Restore to OEM to see if a problem I am/was having with my Aux jack could have been fixed that way.
I managed to get it to work...I think what the problem was, was that I had PDANET installed, so when the phone rebooted to flash the ruu, Pdanet started and caused the flash to fail. I disabled Pdanet and any other non-essential programs that were running in the background on my laptop, and the flashing worked.
I wasn't too worried about the root or the unlocked status because I'll be returning it under the 14 day guarantee.
Related
EDIT: UPDATE .... i managed to get the phone rebooted .... held the force reboot buttons for literally over a min in desperation.... not i need to fully unroot and start from scratch but am having trouble with that still.... can anyone help me either (A) get s-off ... or (B) get it so that i am completely unrooted so i can start over from scratch to get s-off????
Ok folks, i am officially stuck.... its been quite awhile since i have really asked for help on here but i am stuck in a really bad way!!!
Here is how i got to where i am
Just bought my brand new EVO LTE today and went to root it using "[ROOT] RegawMOD EVO 4G LTE Rooter | Updated 06.13.12" from this section!
everything seemed to work great and it said everything rooted properly.... I love Clockwork mod recovery so i then flashed that and it worked properly to or so i thought! so i went to create an origional Nand but it would not work, so i decided to flash TWRP back instead and do that way. when going into the bootloader it said "Tampered" as expected, but it still said S-on so obviously not a proper and correct root.
So i ran RegaMOD again as it said in the instructions, but it would never get passed the HTCdev part, it would just say "sucessfully logged out" and sit there forever and do nothing. So after a few tries of that i decided to unroot and start over from scratch. I could not find an unroot method for RegaMOD so i then went to the other root method "How to Root HTC Evo 4G LTE! [Windows/Mac/Linux] - by Zedomax" in this section and saw it had an unroot method which i followed to the letter! did full unroot through SuperSU and then downloaded the stock RUU from that section for my phone with the proper version number.
everything seemed to be running fine went to the black "HTC" screen and everything was going smoothly.... then the update failed and my phone stayed on the black HTC screen. my computer prompted me to recover which i could not really do as you can't pull the battery on this phone. So i then tried to update the RUU again except this time it did not list a current software version, only the one i was updating too.... it failed again 2 more times!!
when plugged into the computer my phone displays the black "HTC" screen
when plugged into the charger it displays the following screen info (bootloader look)
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PUT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 26 2012,19:54:01
FASTBOOT AO <---- MIGHT BE FASTBOOT AC HARD TO TELL
Update Fail!
when un-plugged it says almost the same thing
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PUT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 26 2012,19:54:01
FASTBOOT <---- THIS IS THE ONLY CHANGE
Update Fail!
no buttons do anything at all, in any combination or holding pattern
PLEASE HELP ME!!!!! THANKS TO ALL IN ADVANCE!!!
just one thing, s-on or s-ff has nothing to do with root
did you relock your bootloader before running the RUU?
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
no, i did not re-lock the boot loader.... didnt know you needed to, not used to that on the OG EVO... how do you go about redoing that? I always thought S-OFF was an important part of root..... the main reason i looked and noticed it was since i flashed clockworkmod recovery and wanted to go back to TWRP i read on their page that "You must be S-OFF or have taken HTC's unlock to use a recovery on your device!" I guess that since i used HTC unlock i could flash, but either way, should i need to go back to stock for any reason, could you please tell me the proper steps?
Thanks a million!!!
smw6180 said:
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
Click to expand...
Click to collapse
Sorry I just got excited, I have run root on my last 2 phones (much more research on those) and just kinda fell into a super late night lazy not thinking groove... please dont be offended, the reason a rarely dont ask for help is i usually have not needed it.... no need to get hostile.... thankyou for the responce
smw6180 said:
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
Click to expand...
Click to collapse
+1
shootin4aces said:
Sorry I just got excited, I have run root on my last 2 phones (much more research on those) and just kinda fell into a super late night lazy not thinking groove... please dont be offended, the reason a rarely dont ask for help is i usually have not needed it.... no need to get hostile.... thankyou for the responce
Click to expand...
Click to collapse
Wasn't being hostile and I'm not offended. It's just there are entirely too many people who haven't been paying attention to what they're doing and get upset about it when it all blows up in their face.
And for the record every phone is different. I've rooted my last 4 Android phones, 3 evo's and the hero, and root was different on each one, with different potential problems. Being excited is great. But you need to take the time to learn what you're doing, first.
shootin4aces said:
no, i did not re-lock the boot loader.... didnt know you needed to, not used to that on the OG EVO... how do you go about redoing that? I always thought S-OFF was an important part of root..... the main reason i looked and noticed it was since i flashed clockworkmod recovery and wanted to go back to TWRP i read on their page that "You must be S-OFF or have taken HTC's unlock to use a recovery on your device!" I guess that since i used HTC unlock i could flash, but either way, should i need to go back to stock for any reason, could you please tell me the proper steps?
Thanks a million!!!
Click to expand...
Click to collapse
read the post above yours he did tell you how to do it..lol
Oh and before I forget: Don't use CWM. Unless they've fixed it in the last couple of days it breaks your /misc partition, which is quite probably what caused your issues in the first place.
Use TWRP. After you have root/unlocked you can download goomanager from the Play Store...it will install it for you.
smw6180 said:
Wasn't being hostile and I'm not offended. It's just there are entirely too many people who haven't been paying attention to what they're doing and get upset about it when it all blows up in their face.
And for the record every phone is different. I've rooted my last 4 Android phones, 3 evo's and the hero, and root was different on each one, with different potential problems. Being excited is great. But you need to take the time to learn what you're doing, first.
Click to expand...
Click to collapse
+1 and wrong section
This is the method I used on my 4lte without a problem. But you should read entire post before attempting cause it flashes TWRP recovery automatically along with SU. Clockwork still is buggy.
http://forum.xda-developers.com/showthread.php?p=26955832
from my "Beach Watcher" 4LTE
thankyou
all problems have been fixed, thankyou everyone for all your help
again, sry for posting in the wrong forum with this issue, and i am sorry if i came off as a noob! I'm really not, just completely jumped the gun and am very very tired as i have been up for almost 36 hours now
thankyou again for all the help, and as i normally do, i will perform all my research before my next venture.... a lot has changed between this phone and my last one that i rooted and modded, i will be more prepared in the future!
Selders, you're here now?! Good to see ya here
sent from a shining jewel 4g LTE
So I'm one of the lucky few who got their phone unlocked and rooted before VZW and HTC put us all over a barrel buy taking the Inc4G off the supported devices list over at HTCDev. I've been happily plugging along until recently when the latest OTA update started getting pushed. Now every night my phone trys to run the update, which of course fails because I'm running a custom recovery instead of the stock one. It's annoying for a few reasons
It kills my battery if I don't leave it plugged in
I can't get messages or calls
It happens every friggin' night!
Is there any way to just permanently decline the upgrade? I can decline/defer it for a couple days at a time but then it just comes back. It's to the point where I'm debating getting rid of the phone and going back to my Nexus.
coffeedragon said:
So I'm one of the lucky few who got their phone unlocked and rooted before VZW and HTC put us all over a barrel buy taking the Inc4G off the supported devices list over at HTCDev. I've been happily plugging along until recently when the latest OTA update started getting pushed. Now every night my phone trys to run the update, which of course fails because I'm running a custom recovery instead of the stock one. It's annoying for a few reasons
It kills my battery if I don't leave it plugged in
I can't get messages or calls
It happens every friggin' night!
Is there any way to just permanently decline the upgrade? I can decline/defer it for a couple days at a time but then it just comes back. It's to the point where I'm debating getting rid of the phone and going back to my Nexus.
Click to expand...
Click to collapse
Using root explorer or another program like it, go to system/app/ and delete these two files:
1) HtcOMADM_SettingsPlugin_VZW.apk
2) HtcOMADM_VZW.apk
popup will never be seen again, and removes the annoying software update plugin in settings.apk
enjoy
You will want to delete the relatively large OTA package sitting in the /cache directory (possibly /cache/fota/ - but I can't check without root).
Also wouldn't hurt to rename the otacerts.zip file found in /etc/security by renaming it to otacerts.zip.bak
coffeedragon said:
So I'm one of the lucky few who got their phone unlocked and rooted before VZW and HTC put us all over a barrel buy taking the Inc4G off the supported devices list over at HTCDev. I've been happily plugging along until recently when the latest OTA update started getting pushed. Now every night my phone trys to run the update, which of course fails because I'm running a custom recovery instead of the stock one. It's annoying for a few reasons
It kills my battery if I don't leave it plugged in
I can't get messages or calls
It happens every friggin' night!
Is there any way to just permanently decline the upgrade? I can decline/defer it for a couple days at a time but then it just comes back. It's to the point where I'm debating getting rid of the phone and going back to my Nexus.
Click to expand...
Click to collapse
Why not upgrade to latest RUU and just reunlock the bootloader and reinstall the recovery to force SuperSU?
That's what I did.
EDIT: As long as you still have your unlock_code.bin file
articzap said:
Why not upgrade to latest RUU and just reunlock the bootloader and reinstall the recovery to force SuperSU?
That's what I did.
EDIT: As long as you still have your unlock_code.bin file
Click to expand...
Click to collapse
once you're unlocked you're unlocked, and can get the unlock_code.bin anytime on the site the way you did the first time by selecting other for phone.
andybones said:
once you're unlocked you're unlocked, and can get the unlock_code.bin anytime on the site the way you did the first time by selecting other for phone.
Click to expand...
Click to collapse
i think once you have an unlock code you can use it again to unlock after relock, i could be wrong since i never had one.
ok i misread you can't get an unlock code anymore, but if you have a code you can reuse it.
articzap said:
Why not upgrade to latest RUU and just reunlock the bootloader and reinstall the recovery to force SuperSU?
That's what I did.
EDIT: As long as you still have your unlock_code.bin file
Click to expand...
Click to collapse
@articzap - Can you explain the steps you took to do that?
mdimbler said:
@articzap - Can you explain the steps you took to do that?
Click to expand...
Click to collapse
I made a thread just for this...
http://forum.xda-developers.com/showthread.php?t=1947600
I uploaded the RUU.exe AND pulled the ROM.zip from the RUU and uploaded that to be able to put on SD-Card and install though bootloader. (my preferred method, much easier, and usually running the RUU through the computer an error will prevent you from upgrading. the ROM.zip through bootloader, will only fail if the download is corrupt, but I provided MD5 for that reason..)
IF you are unlocked with HTCdev unlock, u must lock the bootloader first, install the PJ53IMG.zip file, then unlock bootloader again.
you do this the same exact way you did when you first unlocked your phone..
unless of coarse you saved your unlock_code.bin.
but if you didn't you can always just get it back on the htcdev unlock site..
once your phone is unlocked, it is unlocked..
there is NO worry of locking your bootloader and then being un-able to unlock it again.
hope this clears it up guys...
Thanks guys! I got it done using these instructions.
I'm trying to help a buddy of mine. He has a Thunderbolt, issued through work. It is stock, unrooted, locked, never modded. He recently got the ICS OTA update. Phone was functional, but laggy and a bit unstable. He did a factory reset, and initially the phone was fine for a few hours, then it was acting buggy. After a reboot it was fine for a bit, then froze. Usable time kept diminishing with subsequent reboots. He tried another factory reset, and the phone won't boot now. If you power it up, you get the white screen with the HTC logo, then a black screen, and nothing ever happens. I can get to Hboot. I can get to fastboot. Not sure if recovery does anything. I get the recovery screen, then a reboot, and then nothing.
I've been trying to read up on how to fix this, and I'm not sure how to go about it since the phone is currently locked, and won't boot. I looked at the Thunderbolt All In One tool, but it looks like it needs the phone to be booted to start the process.
My end goal is to get back to stock, unrooted, (Gingerbread, then OTA update I suppose), and S-on. But to do that, I need to obtain s-off first. Any info would be greatly appreciated.
I've attached a couple of pics.
Thank you.
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
cujo6801 said:
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
Click to expand...
Click to collapse
Good to know. Thank you. I think because it was employer issued, he's going to try to get a newer device if we can't get it running. But I just had to make some attempt to get it running.
Pm disconnecktie as you should be able to flash via abd beings you can get in to fastboot. He knows a lot about the workings of these phones.
Sent from my ADR6425LVW using Tapatalk 2
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Fastboot does work. I was able to do the "fastboot devices" command before, and saw the phone. I was also able to "fastboot flash zip" the file from post 12 from this tread (link below), BUT even though the file transferred from the computer to the phone, the actual flash failed... I'm assuming because the phone is locked.
http://forum.xda-developers.com/showthread.php?t=2120985&page=2
Try downloading the official ota zip over at the developer section. Put it on the root of your sd card and rename it to PG05IMG. Then run the update through fastboot. I seriously doubt this will solve the problem long term but it may work. I have doubts. I am beginning to think htc released the ota purely for development purposes. More and more people are popping in here with problems similar to this.
Sent from my ADR6400L using Tapatalk 2
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
SoundTech said:
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
Click to expand...
Click to collapse
You need to be rooted to use a rom
Sent from my Nexus 7 using Tapatalk 2
Yeah, that wasn't too swift of me, was it now?
I grabbed the zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2144326
Tried Hboot with the file renamed, same results as previous post. Tried fastboot flash zip, same results as above. No joy.
Going to try to see if HTCDev will get the bootloader unlocked in the current phone state.
Well since the ota isn't a downgrade I thought it may work. If HTC dev is able to unlock his bootloader maybe he can get further.
Sent from my personally built from source CM10.1 N7.
Bootloader is unlocked now, since it was all through fastboot. Still S-on. Tried with the OTA zip still on the SD card as "PG05IMG.zip." It loaded, started to check, started to parse for a moment, then went back to the Hboot screen, reboot got me nowhere. I need to go deal with the rest of life now. I'll try again tomorrow. I appreciate everyone's help today. Thank you.
At this point just s off and install a recovery then you can flash that ROM.
Sent from my Nexus 7 using Tapatalk 2
Use this guide here. Make sure you have plenty of time before hand and FOLLOW THE DIRECTIONS IN ORDER TO A T. It is very important that you don't skip over stuff. This is the only current method to get s off with ics.
Sent from my ADR6400L using Tapatalk 2
Long day at work, but back to it. Making sure the battery is charged up, and downloading files.
I'm looking at a post on ThunderboltForums. Making absolutely sure here: Is THAT the one I should be following?
Follow-up: At the end of step 28, after flashing the .19 ROM, is says to use the All-In-One tool. IF I plan to be stock, unrooted, locked, S-on, it seems I'm there at this point, and I can let the OTA update run. Is that correct?
Thanks again.
Looks like I'm on stock Gingerbread, S-off, re-locked, stock recovery. Heck, it finally boots! I'll see about trying OTA update tomorrow.
Thanks again.
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Huh. I never did use the tool. I went through the steps on the ThunderboltForums post all the way through flashing the .19 ROM. Unless I missed something or did something wrong, before the flash it said I would be re-locked and S-on. After the flash it said the phone should be "back to normal". The next step was the All-In-One tool. But the device actually booted into android with the .19 ROM. That was the first time I saw it boot since I got my hands on it. Perhaps the process in that thread helped repair whatever part of the system was buggered up to begin with?
Regardless, I tried the OTA update, and the phone took the ICS update through Verizon. It seems to be running better now than it did before. It's back in my buddy's possession, and he's in the process of getting his apps and data reinstalled.
He thanked me profusely for getting it running again. So I, in turn, pass his thanks on to everyone here that helped me out, the people that worked to get the Thunderbolt resources to where they are now, and to the forum in general for existing and doing what it does. Thank you all.
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
tigerxchaos said:
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
Click to expand...
Click to collapse
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
mikeyk101 said:
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
Click to expand...
Click to collapse
Thanks very much for the suggestion. I'll give this a try shortly.
It's just weird that this RUU successfully took another phone back to fully stock. The only difference between the two is that the other phone never had CleanROM installed on it.
EDIT: Just realized one other thing, at one point I manually updated the radios on the first phone (the one that is now giving me trouble) but didn't do this on the one that went back to stock properly. I'm going to give the PC method a try since it mentions the radios in the file name.
Sent from my SCH-I535 using xda app-developers app
Went ahead and ran the full RUU from my PC as suggested above. Unfortunately it didn't accomplish the goal. The RUU completed successfully, but HBOOT still says ***RELOCKED***. I tried unlocking and then relocking again, and got the same error:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.958s
Not sure where to go from here.
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
mikeyk101 said:
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
Click to expand...
Click to collapse
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
tigerxchaos said:
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
Click to expand...
Click to collapse
IIRC, when it says Tampered across the top of the bootloader, it just means that the bootloader is unlocked and that a other than factory recovery has been installed such as TWRP or AmonRa. Relocked means that the bootloader had originally been unlocked at some point and then locked again. If it were me, I would
1. Try to unlock the bootloader again,
2. Reinstall either AmonRa or TWRP if either is not there, then
3. Wipe everything such as cache, dalvik cache, wipe ALL data/factory reset, and possibly even wipe system.
(Normally you would not want to wipe system because pretty much everything is then gone but since you have the RUU.exe, you have the means to reinstall the original OS.)
4. After wiping everything above, reboot from recovery to bootloader and try running that RUU again.
You are right though and this is weird. Normally when you run a full factory RUU, it should reset EVERYTHING back to factory original condition.
BTW, I have just been trying to come up with a workable solution. I was kind of hoping that someone with more experience would pipe in. Unfortunately it looks like the Rezound and development is dying a slow but sure death and many have moved on...
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
mikeyk101 said:
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
Click to expand...
Click to collapse
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
tigerxchaos said:
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
Click to expand...
Click to collapse
I didn't quite elaborate on what I was thinking. But you are absolutely correct about doing S-on with an engineered hboot and that it would brick it. However, since it is going back as a warranty replacement, maybe bricking it might not be such a bad idea. LOL. I should have added that by using the fake locked hboot, it may trick the phone into thinking it really was locked. And then flash the second one and the banner just might stay showing locked. I have actually gone back and forth between the two but have always been locked so I am not sure how yours would work out. BTW, that second one is the original factory hboot extracted off the full OTApkg.zip for 4.05.605.14 and packaged in a ph98img file. I extracted it in the event that I might have to S-on again sometime in the future. I also extracted the original factory recovery and packaged that in a ph98img file as well in case I ever had to revert back to stock for the same reason. I just have to unroot (I am using supersu), reinstall the factory recovery, reinstall the factory hboot, do a factory wipe in recovery and finally do the write secure flag command and I am golden. I know that there are still many very cool roms out there. I used to be a big fan of CleanROM but that is no longer supported by the developer. Since then I have gotten kind of used to using a rooted stock rom. I know I may be missing some bells and whistles but I mostly rooted and S-offed just because I could and have a few more choices available to me. I hope you are able to find a solution.
I had this happen a wile ago what worked for me was that I ran the ruu to back to stock, then go through the unlock process, once unlocked s-off. Once s-off run ruu, then follow directions in this link http://forum.xda-developers.com/showthread.php?t=1612937
Sent from my Infected Rezound using xda app-developers app
Full disclosure, this isn't my phone and I'm helping a coworker who did some things. The phone was originally purchased without service as she was switching from AT&T to T-mobile and didn't have it setup yet.
Incident: The phone was unlocked and rooted when last night she used a "toolkit" (I have no idea which one and she said she deleted the folder with everything), then locked it with the toolkit and used the fastboot oem unlock to get back in. When the stock rom was installed again the screen wouldn't work and I was able to navigate with a OTG mouse connected. All of the custom roms work fine as far as the screen goes but the stock one is like it's missing a driver. The other issue here is the SIM card doesn't pickup a network, I verified the Access Point is setup correctly and tried with both the LTE (fast) setup and regular. It's entirely possible that the radio was hosed to start with and we didn't find out until the sim card was purchased on Monday. At this point I'd just like to get it back to FULL stock and see if she can do anything with the Warranty (not sure if this is really possible yet). So, on to things I've tried.
1. Display Issue on Stock, I read this could be a kernel issue and attempted to flash several Stockish roms from here. Also the kernel from mugetsu666. That kernel a long with the other 3-4 stock roms from page 1. Nothing resolved.
2. No Signal. While going through the stock and custom roms all I really need is the signal to work. The PA install had the wrong APN settings and I updated them with the Defaults. No change, so I moved on to radios, maybe that's it. Flashed all the radios from here and a couple other random ones from the individual rom I was using. Nothing.
3. Ok, at this point I just want back to stock. This phone is toast and I'm tired of dealing with it for the day. Found the t-mobile ruu file here and attempted to run it as admin on a windows 7 and 8 machines. The bootloader was locked before attempting this and I tried in fastboot or just the phone being on. All I get is error 170 which is the usb connection issue. Fastboot does recognize my device so the RUU should pickup, now i'm really stuck.
Needless to say it's hasn't been a productive day at work. Any assistance is greatly appreciated. THANKS!!
I see you tired the T-Mobile ruu have your tried offival att ruu yet?
Sent from inside the T.A.R.D.I.S
joselv456 said:
I see you tired the T-Mobile ruu have your tried offival att ruu yet?
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
You should run the revone s-off before you do anything after unlocking the bootloader. The first RUU should have been ATT since it is an ATT phone, like the last poster mentioned. After you unlock the bootloader, run revone to get s-off, then get superCID and run whatever RUU you like ATT,GPE, or T-Mo.
This one?. The link is dead. Can I use another supercid by at or M7?
Thanks for the help. I'm really a Samsung user so this is new
C Murder said:
You should run the revone s-off before you do anything after unlocking the bootloader. The first RUU should have been ATT since it is an ATT phone, like the last poster mentioned. After you unlock the bootloader, run revone to get s-off, then get superCID and run whatever RUU you like ATT,GPE, or T-Mo.
Click to expand...
Click to collapse
Bootloader unlocked
s-off complete
CID-11111111
I'm running the Signed2 from this list.
http://www.androidruu.com/index.php?developer=M7
Error 170, USB issue. Fastboot can see the device but the RUU can't, odd.
Edit: Running the RUU when the phone is booted to PA gets pasted the error 170. Now it's an error 155 and it's stuck on the HTC logo. Powering it off and it's still hosed.
Sooooo, I think there is more wrong here than a simple RUU update. I noticed under the *** UNLOCKED *** that the model is M7_UL, which i'm finding is a Europe model. I'm toast.. warm buttery toast i think.
Side note: Don't offer to help coworkers if you haven't worked on a phone like this before.
I have m7ul which was originally a t-mobile device when I got it used. I flashed the GE ruu no problem. You should be ok with that device.
Sent from my HTC One using Tapatalk 4
kronikwisdom said:
Bootloader unlocked
s-off complete
CID-11111111
I'm running the Signed2 from this list.
http://www.androidruu.com/index.php?developer=M7
Error 170, USB issue. Fastboot can see the device but the RUU can't, odd.
Edit: Running the RUU when the phone is booted to PA gets pasted the error 170. Now it's an error 155 and it's stuck on the HTC logo. Powering it off and it's still hosed.
Click to expand...
Click to collapse
Did you try running the tmobile RUU.exe from your pc. I know it's in the Tmobile HTC One forum. I'm sure it's here somewhere too. The kernels and recovery are there too, with guides to take you back to stock.
C Murder said:
Did you try running the tmobile RUU.exe from your pc. I know it's in the Tmobile HTC One forum. I'm sure it's here somewhere too. The kernels and recovery are there too, with guides to take you back to stock.
Click to expand...
Click to collapse
Yes, I've tried the tmobile RUU from these forums.
I've just made things worse now it seems because I updated the CID back to "T-MOB010" and now the recovery image won't stick. Seems like I'm missing something else from the boot.img but I've tried to flash the original firmware.zip on these forums. So tired of this thing.
Monday and I'm still at this. After relocking my boot loader per the request of the owner I'm unable to unlock it now. Requested a new code and that didn't change anything. The command to unlock from fastboot completes and writes successfully but the screen doesn't popup on my phone to accept the unlock.
Fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 kb)... <--- not sure if that's correct, the file is actually 256b but maybe it's under 1 so it doesn't show.
OKAY [ 0.150s ]
writing 'unlocktoken'...
OKAY [ 0.010s ]
finished. total time: 0.160s
this phone is going further down hill.
last ditch effort and I ran the RUU from Tmobile on an old XP machine, worked. back to stock.. not sure what to say but i'm tired of looking.. haha
I don't know why she needed to do all that soff in the first place ... This device doesn't require soff to flash roms or even soff to flash tmobile roms on the att m7 or vise versa
It's a lot like nexus model the boot.img flashes In roms soff is usually needed to do that on other htc devices not the One
Simple carrier unlock and Bootloader unlock with recovery is all you need to flash any Rom onto any m7 besides sprint and vzw
Soff and supercid doesnt seem like it was necessary in her case
HTC is touchy stuff takes reading 10 times over before attempting anything...
If we had a samsung Odin method we would be golden ..
Glad it's fixed
Sent from my HTC One using xda app-developers app