Help reverting back to stock. - One (M7) Q&A, Help & Troubleshooting

I'm trying to unroot and revert back to stock and having a bit of a nightmare. I didn't make my own nandroid backup before I installed a customer rom (lesson learnt), so I downloaded the one I needed off a thread on here (UK Unbranded CWM). Every time I try to flash the nandroid I get an MD5 sum mismatch error. I've tried various methods people have suggested across the internet to no joy. Is there a stock .401 rom knocking about? I saw mikes thread but that has the latest 4.22 stock rom, is there one for an older version? Thanks.

if you have s-off you should
1)download this ruu http://androidfiles.org/ruu/getdownload.php?file=M7/RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
2)lock your bootloader (use command "fastboot oem lock")
3)run ruu
4)done

Rayskull said:
if you have s-off you should
1)download this ruu http://androidfiles.org/ruu/getdownload.php?file=M7/RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
2)lock your bootloader (use command "fastboot oem lock")
3)run ruu
4)done
Click to expand...
Click to collapse
Thank you very much. I've managed to restore from a nandroid backup and I've installed stock recovery, I'm now installing a OTA as prompted by the device. As I now have stock rom, recovery and no root access, gain I still use revone to lock bootloader and go S-On? The reason I want to use revone is so that it doesn't say 're-locked'. If so, how? Thanks for all your help.

if you recieved the OTA i think there's no need to relock the bootloader, but if you want to... so yes, use revone.
"./revone -l" to lock it (no relocked warning)
if you recieve the tampared warning use:
"./revone -t"
cheers

Related

[Q] Want to restore TELUS unit to as stock as possible

Hi Guys,
I want to restore a TELUS Canada HTC One back to as stock as possible for warranty exchange purposes.
There is no RUU available for TELUS, but I do have a TWRP Nandroid backup. The device's HBOOT has been updated to 1.54, and the device is currently S-OFF / SuperCID via Revone and obviously unlocked bootloader with TWRP recovery. As well, the device is running the ARHD ROM.
What order / process do I need to follow to get this back to as stock-like as possible?
WorldIRC said:
Hi Guys,
I want to restore a TELUS Canada HTC One back to as stock as possible for warranty exchange purposes.
There is no RUU available for TELUS, but I do have a TWRP Nandroid backup. The device's HBOOT has been updated to 1.54, and the device is currently S-OFF / SuperCID via Revone and obviously unlocked bootloader with TWRP recovery. As well, the device is running the ARHD ROM.
What order / process do I need to follow to get this back to as stock-like as possible?
Click to expand...
Click to collapse
-Manually flash back the stock 1.44 hboot (and any custom splash you may have flashed)
-Nandroid restore (make sure it includes recovery, if not manually flash the stock one)
- Set CID back to stock
- S-on with revone
- Relock bootloader
Let me know if you need help with any of the steps.
crushalot said:
-Manually flash back the stock 1.44 hboot (and any custom splash you may have flashed)
-Nandroid restore (make sure it includes recovery, if not manually flash the stock one)
- Set CID back to stock
- S-on with revone
- Relock bootloader
Let me know if you need help with any of the steps.
Click to expand...
Click to collapse
Where would I get the stock 1.44 HBOOT and stock Recovery? I'm using the TELUS TWRP Recovery from here: http://forum.xda-developers.com/showthread.php?t=2207874
WorldIRC said:
Where would I get the stock 1.44 HBOOT and stock Recovery? I'm using the TELUS TWRP Recovery from here: http://forum.xda-developers.com/showthread.php?t=2207874
Click to expand...
Click to collapse
The Nandroid should include the stock recovery.
The stock hboot can be downloaded here: http://d-h.st/qfc
It is from post 2 of sneakyghost's guide which has the instructions as well:
http://forum.xda-developers.com/showthread.php?t=2316726
Let me know if you need anything else.
crushalot said:
The Nandroid should include the stock recovery.
The stock hboot can be downloaded here: http://d-h.st/qfc
It is from post 2 of sneakyghost's guide which has the instructions as well:
http://forum.xda-developers.com/showthread.php?t=2316726
Let me know if you need anything else.
Click to expand...
Click to collapse
Curious -- since making a Nandroid requires a custom recovery, how would that Nandroid contain the stock recovery?
WorldIRC said:
Curious -- since making a Nandroid requires a custom recovery, how would that Nandroid contain the stock recovery?
Click to expand...
Click to collapse
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.
crushalot said:
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.
Click to expand...
Click to collapse
Awesome -- I'll be trying this once my replacement unit has arrived. I'll let you know how everything works out.
crushalot said:
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.
Click to expand...
Click to collapse
Not sure why I'm having so much difficulty with this.
I've restored the 1.44 HBOOT referenced above.
I've restored the stock TELUS ROM via TWRP referenced above.
I can boot into the phone, but I have no touch-screen response now. Also, that TWRP backup did not include the stock recovery and I'm not sure which one I should push.
Tried flashing: http://forum.xda-developers.com/showpost.php?p=41953560&postcount=32 and now I have a red triangle recovery.....
OK, everything is normal. The red triangle means it is the stock recovery.
The touchscreen doesn't work because you must have updated your firmware. If you still have s-off then you can downgrade that back to stock before s-on and re-lock. Go to this thread:
http://forum.xda-developers.com/showthread.php?t=2316726
Download and install the package he has for " Base 1.29 Firmware, original unmodified"
After that you should be stock and just need to s-on and re-lock the bootloader.
crushalot said:
OK, everything is normal. The red triangle means it is the stock recovery.
The touchscreen doesn't work because you must have updated your firmware. If you still have s-off then you can downgrade that back to stock before s-on and re-lock. Go to this thread:
http://forum.xda-developers.com/showthread.php?t=2316726
Download and install the package he has for " Base 1.29 Firmware, original unmodified"
After that you should be stock and just need to s-on and re-lock the bootloader.
Click to expand...
Click to collapse
That site needs a "decryption key"?
WorldIRC said:
That site needs a "decryption key"?
Click to expand...
Click to collapse
Not sure what thats about. I will look into it and try to host those files on my site. However for now, you only need the touchpad driver part of the firmware which can be downloaded from his thread without a key here:
https://mega.co.nz/#!7YB1GCAJ!LaWJ8x5Vsjrw9YrLTIe262ZslZBNwRgp6i0qx2M_lIw
crushalot said:
Not sure what thats about. I will look into it and try to host those files on my site. However for now, you only need the touchpad driver part of the firmware which can be downloaded from his thread without a key here:
https://mega.co.nz/#!7YB1GCAJ!LaWJ8x5Vsjrw9YrLTIe262ZslZBNwRgp6i0qx2M_lIw
Click to expand...
Click to collapse
How am I flashing this?
WorldIRC said:
How am I flashing this?
Click to expand...
Click to collapse
Same way as the firmware zip's. You use the same guide from post 1.
crushalot said:
Same way as the firmware zip's. You use the same guide from post 1.
Click to expand...
Click to collapse
Thought so, wasn't 100% sure
Anyways - that worked. I have control of my Touch Screen. I'll await your response on the rest of the firmware, at which point I'll finish everything up and send you some beer for your time
WorldIRC said:
Thought so, wasn't 100% sure
Anyways - that worked. I have control of my Touch Screen. I'll await your response on the rest of the firmware, at which point I'll finish everything up and send you some beer for your time
Click to expand...
Click to collapse
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.
crushalot said:
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.
Click to expand...
Click to collapse
Will give it a shot later today and let you know!
crushalot said:
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.
Click to expand...
Click to collapse
Well now I've done it. Reflashed the firmware, put my CID back to TELUS001. Went back to S-ON, locked BOOTLOADER.
Now I am showing TAMPERED / LOCKED.
I reunlocked the bootloader, and am now showing TAMPERED / UNLOCKED, with stock recovery. I put back on TWRP and it shows TAMPERED / UNLOCKED.
I tried re-running REVONE and I am unable to go back to S-OFF.
What the heck happened?
WorldIRC said:
Well now I've done it. Reflashed the firmware, put my CID back to TELUS001. Went back to S-ON, locked BOOTLOADER.
Now I am showing TAMPERED / LOCKED.
I reunlocked the bootloader, and am now showing TAMPERED / UNLOCKED, with stock recovery. I put back on TWRP and it shows TAMPERED / UNLOCKED.
I tried re-running REVONE and I am unable to go back to S-OFF.
What the heck happened?
Click to expand...
Click to collapse
Can you verify your hboot is back down to level 1.44?
If it is, we should be able to revone to s-off again, but we may need to try a few times.
Did you have tampered displayed before you went s-on?
It did display locked rather than relocked so that it good. However it must be picking something up as non original as that is what causes the tampered flag.
crushalot said:
Can you verify your hboot is back down to level 1.44?
If it is, we should be able to revone to s-off again, but we may need to try a few times.
Did you have tampered displayed before you went s-on?
It did display locked rather than relocked so that it good. However it must be picking something up as non original as that is what causes the tampered flag.
Click to expand...
Click to collapse
Yes, I am on HBOOT 1.44 from April 2013.
Tampered was not present before (I had hidden it with Revone). Tampered came back only after I re-locked the bootloader (with the stock recovery via firmware file you provided to me).
I tried to go S-OFF but I keep getting error 2 or 6 when doing ./revone -P
Meanwhile no issues doing 2 other phones with Revone (fresh out of box).
WorldIRC said:
Yes, I am on HBOOT 1.44 from April 2013.
Tampered was not present before (I had hidden it with Revone). Tampered came back only after I re-locked the bootloader (with the stock recovery via firmware file you provided to me).
I tried to go S-OFF but I keep getting error 2 or 6 when doing ./revone -P
Meanwhile no issues doing 2 other phones with Revone (fresh out of box).
Click to expand...
Click to collapse
I had one phone that gave me trouble with revone. I tried it like 20 times and nothing was working. Then I ran all the commands in a terminal window on the phone rather than adb shell and it worked. Can you try that?
There are also some other good tips in the revone thread, but I forget them all and will have to read it again.
It wouldn't have been the recovery as that for sure was the stock recovery. Did you download the stock nandroid or did you make it yourself?

S-Off issues... need help!

i apologize in advance for the noob issues... I am having issues trying to achieve s-off on my htc one. i am rooted right now, running stock 4.3 GPE rom. I have TWRP recovery installed. everything works perfectly. however i would like to do a complete conversion so i will recieve OTA updates from google, and not have to worry about flashing roms. so when i first tried to achieve s-off , i was using revone method. i was getting an error code (-1) then i read that that method wouldnt work, if you were running 4.3. so i then restored my nandroid backup, which i was running 4.1.2. but before flashing my backup i did a system wipe, just to be safe. so i tried revone method again. only now i get error code (-6) so i gave up. but i think when i did my system wipe , i lost my stock back up? so my 2 questions are, where is my nandroid backup? did i lose it when i did a system wipe? and how can i achieve s-off? i am not sure how to tell what firmware version i am running, i didnt see it in settings anywhere, nor do i know what hboot i have (1.44 or 1.54?) how do i tell? thanks guys!
ssreynolds said:
i apologize in advance for the noob issues... I am having issues trying to achieve s-off on my htc one. i am rooted right now, running stock 4.3 GPE rom. I have TWRP recovery installed. everything works perfectly. however i would like to do a complete conversion so i will recieve OTA updates from google, and not have to worry about flashing roms. so when i first tried to achieve s-off , i was using revone method. i was getting an error code (-1) then i read that that method wouldnt work, if you were running 4.3. so i then restored my nandroid backup, which i was running 4.1.2. but before flashing my backup i did a system wipe, just to be safe. so i tried revone method again. only now i get error code (-6) so i gave up. but i think when i did my system wipe , i lost my stock back up? so my 2 questions are, where is my nandroid backup? did i lose it when i did a system wipe? and how can i achieve s-off? i am not sure how to tell what firmware version i am running, i didnt see it in settings anywhere, nor do i know what hboot i have (1.44 or 1.54?) how do i tell? thanks guys!
Click to expand...
Click to collapse
Ok sir, I try to help you.
First, you need to have knowledge with ADB and fastboot, but you should have them both in a folder since you unlocked your device through HTCdev. Then open a terminal and navigate to this particular folder. When you connected your HTC One M7 with the computer and UNINSTALLED HTCSync you can type "adb devices" to ensure you have a connection to your cell phone. Then you have to boot into the bootloader with this command "adb reboot bootloader" and there you see on the first couple of lines your HBOOT version. You'll see it! Then you boot into the recovery from the bootloader and install a ROM from this side that matches a version of rumrunner s off: http://android-revolution-hd.blogspot.ch/p/android-revolution-hd-mirror-site-var.html
Secondly then getting updates from Google you need to proceed these steps:
http://forum.xda-developers.com/showthread.php?t=2358781
This will turn your device into a Google Play Edition!
Hit the thanks button if you understood it, for questions simply ask again
LibertyMarine said:
Ok sir, I try to help you.
First, you need to have knowledge with ADB and fastboot, but you should have them both in a folder since you unlocked your device through HTCdev. Then open a terminal and navigate to this particular folder. When you connected your HTC One M7 with the computer and UNINSTALLED HTCSync you can type "adb devices" to ensure you have a connection to your cell phone. Then you have to boot into the bootloader with this command "adb reboot bootloader" and there you see on the first couple of lines your HBOOT version. You'll see it! Then you boot into the recovery from the bootloader and install a ROM from this side that matches a version of rumrunner s off: http://android-revolution-hd.blogspot.ch/p/android-revolution-hd-mirror-site-var.html
Secondly then getting updates from Google you need to proceed these steps:
http://forum.xda-developers.com/showthread.php?t=2358781
This will turn your device into a Google Play Edition!
Hit the thanks button if you understood it, for questions simply ask again
Click to expand...
Click to collapse
that helps some, lol. so i now know how to find out what hboot version i have (i'm assuming that because i have 4.3 i am running hboot 1.54).... so thank you! i saw the rumrunner thread for the latest s-off. i will proceed with those steps... as far as completing the full google play conversion that actually sounds pretty easy once you have s-off. i can handle that. ( change cid to googl0001 and flash the new ruu, and stock recovery done!)
so now i just need to know what firmware version i have?
did i delete my back up when i did a system wipe?
To reiterate...
I am on hboot 1.44, rooted running a stock GPE 4.3 Rom. Also, I feel stupid, but I can't seem to find out what firmware version I have? So I have tried twice with no avail. First I tried the typical revone method , but i was getting an error code -1, because I was on 4.3. So I flashed my backup, and returned to my stock rom on 4.1.2, and tried again. This time I was getting an error code -6? So I temporarely gave up, until I saw the rumrunner method here on xda. Worst part is when I returned to stock, I did a system wipe before flashing back to my 4.3 GPE rom, and deleted my backup! So I am nervous about flashing anything else, being that I dont have a backup! Long story short, all I want to do is finish a complete GPE conversion, and I need s-off to change my CID. At this point, all I need to do is achieve s-off, flash the GPE CID, and then flash a stock recovery and I'm done! So any thoughts on how to help me achieve s-off without potentionally bricking this thing?
edit: my build number is JWR66Y.H1 , does this mean I am on 3.07.1700.1
ssreynolds said:
To reiterate...
I am on hboot 1.44, rooted running a stock GPE 4.3 Rom. Also, I feel stupid, but I can't seem to find out what firmware version I have? So I have tried twice with no avail. First I tried the typical revone method , but i was getting an error code -1, because I was on 4.3. So I flashed my backup, and returned to my stock rom on 4.1.2, and tried again. This time I was getting an error code -6? So I temporarely gave up, until I saw the rumrunner method here on xda. Worst part is when I returned to stock, I did a system wipe before flashing back to my 4.3 GPE rom, and deleted my backup! So I am nervous about flashing anything else, being that I dont have a backup! Long story short, all I want to do is finish a complete GPE conversion, and I need s-off to change my CID. At this point, all I need to do is achieve s-off, flash the GPE CID, and then flash a stock recovery and I'm done! So any thoughts on how to help me achieve s-off without potentionally bricking this thing?
edit: my build number is JWR66Y.H1 , does this mean I am on 3.07.1700.1
Click to expand...
Click to collapse
boot to bootloader -> FASTBOOT, connect your phone to PC and it will change to FASTBOOT USB (picture attached)
then type "fastboot getvar all" and post it (remove IMEI and s/n before posting), also post the date it shows on that white screen.
nkk71 said:
boot to bootloader -> FASTBOOT, connect your phone to PC and it will change to FASTBOOT USB (picture attached)
then type "fastboot getvar all" and post it (remove IMEI and s/n before posting), also post the date it shows on that white screen.
Click to expand...
Click to collapse
I don't have a camera to take a pic right now, but I can tell you the date is July 5th
ssreynolds said:
I don't have a camera to take a pic right now, but I can tell you the date is July 5th
Click to expand...
Click to collapse
no need for camera, but you still need to post a "fastboot getvar all" (remove IMEI and s/n)
nkk71 said:
no need for camera, but you still need to post a "fastboot getvar all" (remove IMEI and s/n)
Click to expand...
Click to collapse
will do, as soon as I get home!
however if I flash a stock rom like the one I have attached, couldnt I just use revone method (./revone -P)?
http://forum.xda-developers.com/showthread.php?t=2370507 > this rom would put me on firmware version 2.24.401.1
ssreynolds said:
will do, as soon as I get home!
however if I flash a stock rom like the one I have attached, couldnt I just use revone method (./revone -P)?
http://forum.xda-developers.com/showthread.php?t=2370507 > this rom would put me on firmware version 2.24.401.1
Click to expand...
Click to collapse
Why don't you use a RUU and flash the stock recovery, so you can recieve OTA updates and then you can just choose the correct rumrunner s off file and let it do the work. Then you don't really have to worry about the version number and btw. you can simply look it up in the settings. Can you pls ask if I didn't explane it well? Because this is very probable^^

[Q] return to stock after rum runner

I am TMOB101 (the german t-mobile) i have successfully s-offed using rum runner.
There is no RUU for my phone as far as i know..
Is there a way to s-on again?
does rum runner backup my original hboot, so i can restore it to go back s-on?
Nomader0 said:
I am TMOB101 (the german t-mobile) i have successfully s-offed using rum runner.
There is no RUU for my phone as far as i know..
Is there a way to s-on again?
does rum runner backup my original hboot, so i can restore it to go back s-on?
Click to expand...
Click to collapse
You can flash the GuruReset ROM for your version: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
Make sure you choose to flash stock recovery and boot etc.
When all back to fully stock you are then safe to s-on again by issuing the following command: fastboot oem writesecureflag 3
Hope that comes in useful
Nomader0 said:
I am TMOB101 (the german t-mobile) i have successfully s-offed using rum runner.
There is no RUU for my phone as far as i know..
Is there a way to s-on again?
does rum runner backup my original hboot, so i can restore it to go back s-on?
Click to expand...
Click to collapse
Why do you need to s-on? And with s-off you can flash any RUU that you want. To s-on again, the command is "fastboot oem writesecureflag 3", but you need to be COMPLETELY stock before you do this, or you'll have a hard brick.
Sent from my iPod touch using Tapatalk
thank you for your answers.. I want to s-on to send back for warranty issues (purple tint).
I just want to understand how it works..
Rum runner installed an unsecured hboot. correct?
in order to s-off i need to go back to stock hboot first? people install RUU so they can install 1)stock rom, 2)stock radio, 3) stock recovery 4)stock hboot correct?
the Guru Reset rom just installs rom, recovery and radio (no hboot?)
can i just install any RUU and s-on? i thought i needed the one matching my phone
ok i found this http://www.htc1guru.com/guides/return-stock-guide/ and answered most of my questions.. except one:
As i said there is no RUU for me.. i will use a nandroid to restore most of the stuff. BUT there will be a mismatch between my stock Rom installed and the firmware (what is written in bootloader screen OS:XXXXXXX) How can i fix that?
can i just install the TMOB101 firmware from here http://android-revolution-hd.blogspot.gr/p/android-revolution-hd-mirror-site-var.html and fix the mismatch?
Nomader0 said:
ok i found this http://www.htc1guru.com/guides/return-stock-guide/ and answered most of my questions.. except one:
As i said there is no RUU for me.. i will use a nandroid to restore most of the stuff. BUT there will be a mismatch between my stock Rom installed and the firmware (what is written in bootloader screen OS:XXXXXXX) How can i fix that?
can i just install the TMOB101 firmware from here http://android-revolution-hd.blogspot.gr/p/android-revolution-hd-mirror-site-var.html and fix the mismatch?
Click to expand...
Click to collapse
Once you flash the guru reset, and then perform the OTA, you'll be on the same firmware after install.
Yeah but that will be different than the one my cid is supposed to have.. won't HTC service notice?

Failed: Return to stock and unrooted (Verizon)

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

Soft Brick or Hard Brick?

Hi guys,
I had back to completely stock my m7 for guarantee 2 weeks ago. Yesterday i tried every possible way to s-off but i can't get it. So i tried run RUU for downgrade OS,hboot etc. relock bootloader. But accidentally RUU removed OS; no main version in getvar, stock recovery, relocked and there is a warning under relocked title it says ''security warning''
Run RUU or flash update.zip,rom.zip,ruu.zip no matter what,I get 'failed: remote signiture verify fail'. Phone does not boot, because no OS, so no adb. Is only way J-tag for ressurrect it
blitzzkrieg said:
Hi guys,
I had back to completely stock my m7 for guarantee 2 weeks ago. Yesterday i tried every possible way to s-off but i can't get it. So i tried run RUU for downgrade OS,hboot etc. relock bootloader. But accidentally RUU removed OS; no main version in getvar, stock recovery, relocked and there is a warning under relocked title it says ''security warning''
Run RUU or flash update.zip,rom.zip,ruu.zip no matter what,I get 'failed: remote signiture verify fail'. Phone does not boot, because no OS, so no adb. Is only way J-tag for ressurrect it
Click to expand...
Click to collapse
you can not downgrade with s-on!
re-unlock your bootloader, flash a custom recovery and a rom and achieve s-off with sunshine then follow nkk71's guide to return stock (linked in my sig)
alray said:
you can not downgrade with s-on!
re-unlock your bootloader, flash a custom recovery and a rom and achieve s-off with sunshine then follow nkk71's guide to return stock (linked in my sig)
Click to expand...
Click to collapse
I can't unlock bootloader back, flashing unlock_code.bin and allow prompt from phone, it goes to update screen, 2 minutes later i get red triangle screen. I have to unlock my bootloader without unlock_code but my hboot 1.57. So i think my device is dead
Try generating another unlock bin

Categories

Resources