I tried to return my sprint HTC One to stock but was unsuccessful. I was s-off, unlocked bootloader and rooted. I also unlocked the phone using the "sprint htc one sim unlock helper". I tried to return it to stock but failed. I went from s-off to s-on, then locked the bootloader, and then tried to run the RUU but it failed. I ran Sprint_HTC_One_m7wls_1.29.651.10_RUU but it failed. Then I ran the Sprint_HTC_One_m7wls_3.04.651.2_RUU and it also failed. I also ran Sprint_HTC_One_m7wls_4.06.651.4_RUU and it failed also. I don't know what to do anymore. If anyone can help I would appreciate it very much. I have attached pictures of the errors I get.
View attachment 2812728
View attachment 2812729
This the what I got after I ran Sprint_HTC_One_m7wls_4.06.651.4_RUU. I don't know why the security warning showed up.
View attachment 2812730
Chunky McNasty said:
I tried to return my sprint HTC One to stock but was unsuccessful. I was s-off, unlocked bootloader and rooted. I also unlocked the phone using the "sprint htc one sim unlock helper". I tried to return it to stock but failed. I went from s-off to s-on, then locked the bootloader, and then tried to run the RUU but it failed. I ran Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip but it failed. Then I ran the Sprint_HTC_One_m7wls_3.04.651.2_RUU.zip and it also failed. I also ran Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip and it failed also. I don't know what to do anymore. If anyone can help I would appreciate it very much. I have attached pictures of the errors I get.
View attachment 2812728
View attachment 2812729
View attachment 2812730
Click to expand...
Click to collapse
you have to usethe latest ruu, being s-on now, 4.06.651.4. you can't downgrade being s-on, you will need stock recovery also, and bootloader locked as you are already
522
Aldo101t said:
you have to usethe latest ruu, being s-on now, 4.06.651.4. you can't downgrade being s-on, you will need stock recovery also, and bootloader locked as you are already
Click to expand...
Click to collapse
I did use 4.06.651.4 and it didn't work. When I run the ruu it gets to the end on the process and then says update unsuccessful. And can you explain more about the stock recovery. I thought I just need the bootloader to be locked and then I can run the ruu.
Chunky McNasty said:
I did use 4.06.651.4 and it didn't work. When I run the ruu it gets to the end on the process and then says update unsuccessful. And can you explain more about the stock recovery. I thought I just need the bootloader to be locked and then I can run the ruu.
Click to expand...
Click to collapse
if you are s-on you need to flash the stock recovery, same way you flashed a custom recovery, using fastboot.....fastboot flash recovery(name of recovery).img
Related
Successfully gained S-Off and Unlock via Revone. Needed to revert to return phone. Successfully locked and gained S-On, although "tampered" appeared on the b/l screen...
Problem now is WiFi no longer works. I cannot flash a complete ROM via RUU, it fails at updating signature. I cannot flash an OTA zip for the same reason. I cannot enter recovery - all I get is the red triangle.
I cannot regain S-Off, or Unlock (via Revone). Error 2.
I've tried firmware.zip - many parts fail. Although my ROM version is now dated April 12th not May 3rd.
Other than WiFi and tampered, the phone works.
I'm stuck!
You should have done s on only when everything else is stock, your lucky your phone even turns on.
I would try to re unlock it, flash a custom recovery and flash a rom get it working again. Then s off and try the whole going stock procedure again.
Sent from my Tricked out HTC One
It won't unlock from Revone
Unlock by flashing the unlock token from htc dev
Sent from my Tricked out HTC One
Done that. However, if the bootloader's knackered, or partly so, a Custom ROM won't flash a new bootloader. Not sure why I need the interim step. My idea was to S-off now unlocked a try RUU again
LenAsh said:
Done that. However, if the bootloader's knackered, or partly so, a Custom ROM won't flash a new bootloader. Not sure why I need the interim step. My idea was to S-off now unlocked a try RUU again
Click to expand...
Click to collapse
Let us know what happens after you run an ruu and try to s off again
Sent from my Tricked out HTC One
Flashed Cwm Ok. Relocked bl. Flashed odex stock 4.2.2 Ok. WiFi now works. Flashed 4.2.2 recovery. Still not getting in to stock recovery. Tampered still showing. RUU dies as before.
Sent from my GT-I9300 using xda premium
I tried to RUU to 1.29 to go back to stock unrooted. I relocked my bootloader and went to install the RUU and it said Bootloader version error. Please get the correct Rom Update Utility. i am on 1.31. Any help is much aprreciated!!
XCrunner23 said:
I tried to RUU to 1.29 to go back to stock unrooted. I relocked my bootloader and went to install the RUU and it said Bootloader version error. Please get the correct Rom Update Utility. i am on 1.31. Any help is much aprreciated!!
Click to expand...
Click to collapse
You have to be S-Off
Follow this http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
EmSeeMAC said:
You have to be S-Off
Click to expand...
Click to collapse
is there a way to do this without recovery
XCrunner23 said:
is there a way to do this without recovery
Click to expand...
Click to collapse
I'm not sure, I'm trying to figure this out myself
I did it without recovery just a few hours ago due to new touch panel of 4.3. I booted into bootloader and ran the RUU while on Fastboot USB option! It'll go from there
XCrunner23 said:
I tried to RUU to 1.29 to go back to stock unrooted. I relocked my bootloader and went to install the RUU and it said Bootloader version error. Please get the correct Rom Update Utility. i am on 1.31. Any help is much aprreciated!!
Click to expand...
Click to collapse
I had the same problem. First time I tried I realized I forgot to relock my bootloader so I took care of that then the second time I tried it failed again with the same error you got. I've ruu before and never had this happen. Luckily my phone didn't get wiped.
Sent from my HTCONE using Tapatalk 2
If you are ever attempting to downgrade the firmware you n yet be S-Off. If you are S-Off then there is also no need to relock bootloader when running an RUU. Now, if you are attempting to go back to Locked without Tampered or Relocked then you must lock it before running RUU but I would honestly say that it is better to stay S-Off after doing it once because it is east to go back to S-Off and you don't need to be rooted to go back to S-Off and at the same time you will always be able to downgrade if need be if you want to unroot properly.
Sent from my HTCONE using Tapatalk 4
So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2
MacSkizzle said:
So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2
Click to expand...
Click to collapse
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can I get s-off? All I can access is my bootloader.
jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded, extracted, and ran the correct soju but I get an error. It says to run rumrunner again and READ... I don't know what I did wrong. I did this with my phone in fastboot usb mode, is that right?
MacSkizzle said:
Can I get s-off? All I can access is my bootloader.
Click to expand...
Click to collapse
I'm pretty sure that's all you need. But I could be wrong.
TriBeard said:
I'm pretty sure that's all you need. But I could be wrong.
Click to expand...
Click to collapse
When I run the rumrunner program, I type 'Yes' twice then I get an error telling me to run rumrunner again and READ. What did I do wrong?
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
I'll try this tonight when I get home from work, thanks for the input.
ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
This didn't do it either. PLEASE SOMEONE HELP ME
I don't know if you can flash OMJ's firmware if your bootloader is set to "Relocked". I could be wrong but I think what you need to do is unlock it again first and install a recovery. Then flash OMJ's stock firmware from recovery. From there you can probably do the S-OFF process and RUU back to stock.
You do need to be able to boot into your ROM for S-OFF to work, as you start the S-OFF process while the phone is booted up and running.
MacSkizzle said:
This didn't do it either. PLEASE SOMEONE HELP ME
Click to expand...
Click to collapse
Look HERE
i wanted to get stock Rom from custom Rom with image version 3.04.651.2 . So I downloaded latest ruu. Which is also 3.04.651.I re-locked boot loader and started ruu
It cleaned user data till 3% then got stuck at sending file.
Then returned error that it can't upgrade this version of ruu.
Now I'm at stuck at the white screen with boot loader , fastboot modes etc option. Custom recovery is gone. I can't unlock it again
I don't have s-off enable.
While erasing data it's on HTC black screen with logo.
Then it says sending . And then it gives error saying it can't update using this ruu. Try another version. I'm lost.:crying:
Please help me please.
What Winver? Alongside what FW version are you on while attempting to go to 3.04?
EPayne123 said:
What Winver? Alongside what FW version are you on while attempting to go to 3.04?
Click to expand...
Click to collapse
Tried running RUU two more times and it worked.
Now I want to figure how to Unlock relocked Bootloader. I think its only possible via S-off.
Now the problem is that ADB is offline mode.. how Do I adb and push the needed files for s-off
I am on windows xp
aashishbhargav said:
Tried running RUU two more times and it worked.
Now I want to figure how to Unlock relocked Bootloader. I think its only possible via S-off.
Now the problem is that ADB is offline mode.. how Do I adb and push the needed files for s-off
I am on windows xp
Click to expand...
Click to collapse
Update you android sdk/platform tools folder that will fix the offline status
There are no files needing to be pushed to get s-off
bigdaddy619 said:
Update you android sdk/platform tools folder that will fix the offline status
There are no files needing to be pushed to get s-off
Click to expand...
Click to collapse
Thanks, I got the online status.
Now I am with "Relocked" Bootloader, Hboot 1.55, 4.3 Android.
I read that I cannot get S-off on this built. Therefore I tried Rumrunner. But that is failing too after few reboots.
So what is the way to get Bootloader unlocked. Cannot Unlock via HTC DEV Since its Relocked.
My purpose here to unlock bootloader is ROOT the phone and unlock Sim Lock.
how to unlock Re-locked bootloader without ROOT access
aashishbhargav said:
Thanks, I got the online status.
Now I am with "Relocked" Bootloader, Hboot 1.55, 4.3 Android.
I read that I cannot get S-off on this built. Therefore I tried Rumrunner. But that is failing too after few reboots.
So what is the way to get Bootloader unlocked. Cannot Unlock via HTC DEV Since its Relocked.
My purpose here to unlock bootloader is ROOT the phone and unlock Sim Lock.
Click to expand...
Click to collapse
So in other words,
how to unlock Re-locked bootloader without ROOT access if you are on 4.3 and Hboot 1.55
aashishbhargav said:
So in other words,
how to unlock Re-locked bootloader without ROOT access if you are on 4.3 and Hboot 1.55
Click to expand...
Click to collapse
You can use your unlock token if you still have it. If not you can use HTC-Dev again
bigdaddy619 said:
You can use your unlock token if you still have it. If not you can use HTC-Dev again
Click to expand...
Click to collapse
thanks a ton. I swear I tried it thrice before. But I think because of drivers I got error message saying "too Many links"
I tried dev token again and it worked.
Now I have to figure out way to unlock SIM. So far all methods are proving useless after Sprint has decided to screw people with blocking s off and removing api that allowed SIM unlock
aashishbhargav said:
thanks a ton. I swear I tried it thrice before. But I think because of drivers I got error message saying "too Many links"
I tried dev token again and it worked.
Now I have to figure out way to unlock SIM. So far all methods are proving useless after Sprint has decided to screw people with blocking s off and removing api that allowed SIM unlock
Click to expand...
Click to collapse
You can use rumrunner to s-off then ruu back to 1.29 and get sim unlock
bigdaddy619 said:
You can use rumrunner to s-off then ruu back to 1.29 and get sim unlock
Click to expand...
Click to collapse
thanks followed your lead and got the SIM unlock. Will dashing sense 5.5 android 4.3 Rom again lock me ?
I posted in the Verizon forums a day ago, but have received little to no help. Now I hope that someone can help me here.
Original post http://forum.xda-developers.com/showthread.php?t=2599610
I used this thread to unroot and return to stock http://forum.xda-developers.com/show...highlight=s-on
I had done this before with one of CM 10 and I kept the files used in this thread.
I switched to AOKP kitkat 12-30-13. I wanted to return to stock and unrooted.
I got to the oem ruu and kept receiving this message. FAILED (remote: 90 hboot pre-update! please flush image again immediately)
I did this repeatedly as followed. It went over 5 times. I figured this was a problem. Now I am stuck in the bootloader where my phone is locked and S-on. I tried to flash it again and now I get remote: 12 signature verify failed.
It also says ***TAMPERED*** at the top of bootloader, above ***LOCKED***
Edit: I wanted to mention that I do have a backup of my kitkat state at the beginning of all of this. It is in twrp, but I can't flash install the twrp.img, signature verify failed.
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
sweetnsour said:
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
Click to expand...
Click to collapse
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
geeibara said:
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
Click to expand...
Click to collapse
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
sweetnsour said:
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
Click to expand...
Click to collapse
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
geeibara said:
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
Click to expand...
Click to collapse
to be able to reflash twrp you need to unlock your bootloader that is why you are getting signature fail error