[Q] relock/unroot HTC One M7, hboot 1.57 - One (M7) Q&A, Help & Troubleshooting

Hi guys, hope you can help me out...
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !

andreih8017 said:
Hi guys, hope you can help me out...
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !
Click to expand...
Click to collapse
Ok well first off you need s-off to set your bootloader to ***LOCKED*** and to get back to 100% stock. As your on Hboot 1.57 the only way to gain s-off is with Sunshine App. Which will cost $25 to use.
The stock Rom on your Device won't be a complete stock Rom either. When you unlock the bootloader the device is wiped along with some preload data (crappy apps) which is critical if you want the device back to stock. Or to be able to accept OTA updates. If the device is Vodafone I'm not sure there is an RUU but you should be able to get a full stock Rom from somewhere. Please post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting. And we can see what is available for you. But if you want to go 100% stock to reinstate your warranty you will need s-off first :good:

Danny201281 said:
Ok well first off you need s-off to set your bootloader to ***LOCKED*** and to get back to 100% stock. As your on Hboot 1.57 the only way to gain s-off is with Sunshine App. Which will cost $25 to use.
The stock Rom on your Device won't be a complete stock Rom either. When you unlock the bootloader the device is wiped along with some preload data (crappy apps) which is critical if you want the device back to stock. Or to be able to accept OTA updates. If the device is Vodafone I'm not sure there is an RUU but you should be able to get a full stock Rom from somewhere. Please post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting. And we can see what is available for you. But if you want to go 100% stock to reinstate your warranty you will need s-off first :good:
Click to expand...
Click to collapse
Hey, thanx for the quick answer !
This is the result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
What do you mean by "Or to be able to accept OTA updates" ?? At his moment i won't be able to receive any updates anymore ? :crying:
Also, what about Firewater for S-OFF ?

andreih8017 said:
Hey, thanx for the quick answer !
This is the result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
What do you mean by "Or to be able to accept OTA updates" ?? At his moment i won't be able to receive any updates anymore ? :crying:
Click to expand...
Click to collapse
Unlocking the bootloader wipes /data partition to prevent unauthorized access to your data. Problem is that HTC packed some of their stock apps in /data/preload which mean you don't have these apps anymore after unlocking the bootloader. When installing an ota update, there is a script verifying the integrity of each files to be patched, inluding apps normally present in /data/preload. After the script will find out that these apps are missing, the ota update installation will abort. So no your phone can't install ota update anymore unless you restore your phone back to stock (which can be done with s-off btw).
Also, what about Firewater for S-OFF ?
Click to expand...
Click to collapse
Its discontinued. Firewater was using online resources no more available to do its magic.
From what I see from your "getvar all" you have the pretty standard version of the M7. Follow nkk71's guide linked in my signature. You want to follow the procedure using the 1.28.401.7 ruu.zip

@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,

andreih8017 said:
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
Click to expand...
Click to collapse
To safely go back to s-on without risking tampered you should have done it before installing the OTA updates as explained in @nkk71 guide.
So now you should downgrade with the ruu again then set s-on then install OTA updates to avoid the tampered flag returning. :good:

andreih8017 said:
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
Click to expand...
Click to collapse
how far did you go with the OTA's? as long as it's pre 7.xx (ie Lollipop), sunshine will still work, in case you the tampered sign back, you can use sunshine again to s-off, and redo it (the guide)
but as danny said, i (personally) only recommend it on 1.xx or 2.xx firmware.... i don't know the reason for tampered [sometimes/often] reappearing so i dont know what's involved or what triggers it

@Danny201281
@nkk71
i took a leap of faith and eneter the "fastboot oem writesecureflag 3" command. It worked like a charm. Afterwards i rebooted the bootloader 3 times and no "tampered" sign, but S-ON. I also rebooted the phone once and still no "tampered" sign, but S-ON. Guess it worked, right ?
As for the OTAs, i went until the last one available for HTC One - 6.09.401.11.
Thanks guys !

andreih8017 said:
@Danny201281
@nkk71
i took a leap of faith and eneter the "fastboot oem writesecureflag 3" command. It worked like a charm. Afterwards i rebooted the bootloader 3 times and no "tampered" sign, but S-ON. I also rebooted the phone once and still no "tampered" sign, but S-ON. Guess it worked, right ?
As for the OTAs, i went until the last one available for HTC One - 6.09.401.11.
Thanks guys !
Click to expand...
Click to collapse
You need to reboot the ROM three times at least, not the bootloader
Sent from my HTC One_M8 using Tapatalk

@nkk71
I did that also. Still working fine, "locked" and S-ON
Thanx,

andreih8017 said:
@nkk71
I did that also. Still working fine, "locked" and S-ON
Thanx,
Click to expand...
Click to collapse
cool, good to hear :good: :good:

Related

[Q] Unable to unlock, flash recovery or s-off or RUU

I have one hell of a problem.
Status of device:
-Google play edition kit kat htc one (converted from att version)
-No recovery, recovery is INACCESSABLE
-No root, and temp root does not work as well.
-Stock att RUU's not working (as of yet)
-I have tried firewatter, revone and rum runner to try and root so i can get s-off but unable.
-For whatever reason fastboot oem unlock does not as well as the unlock token.
Things i haven't tried because i cant find them:
-Google play edition RUU.exe file
-A standalone RUU for downgrading hboot 1.54 (which is my device currently)
-A modified RUU.exe that will allow me to restore to stock ANYTHING
-A RUU.zip that i can flash manually without s-off
Any suggestions?
j.sax.riley said:
I have one hell of a problem.
Status of device:
-Google play edition kit kat htc one (converted from att version)
-No recovery, recovery is INACCESSABLE
-No root, and temp root does not work as well.
-Stock att RUU's not working (as of yet)
-I have tried firewatter, revone and rum runner to try and root so i can get s-off but unable.
-For whatever reason fastboot oem unlock does not as well as the unlock token.
Things i haven't tried because i cant find them:
-Google play edition RUU.exe file
-A standalone RUU for downgrading hboot 1.54 (which is my device currently)
-A modified RUU.exe that will allow me to restore to stock ANYTHING
-A RUU.zip that i can flash manually without s-off
Any suggestions?
Click to expand...
Click to collapse
you probably have to redo the process at http://www.htcdev.com/bootloader/
redo the process and try to unlock your bootloader with the new unlock.bin
just follow the steps
OK.. Explain this. If you converted. You went SOFF. Then how do you end up with LOCKED Bootloader and SJON?
sent from my mobile device
I have had the same problem few weeks ago
First unlock your bootloader again with a new unlock.bin ...redo the hole process
http://www.htcdev.com/bootloader/
Second regain S-Off with rumrunner
Finaly you should be able to restore with a RUU
Dosent go
Boachti said:
I have had the same problem few weeks ago
First unlock your bootloader again with a new unlock.bin ...redo the hole process
Second regain S-Off with rumrunner
Finaly you should be able to restore with a RUU
Click to expand...
Click to collapse
It says on the prompt that it completed successfully with the unlock, however i do not receive a prompt on the device stating the developer options to accept or deny.
I will proceed as if i did and try my att ruu to try and update the device.
I tried with a google ruu and get signature verify fail, i think that i get the same issue with the att ruu.
IF you can suggest a RUU that will help me out of the situation i would really appreciate it.
Also if there is any reason why rum runner will not complete, i can swear adb is up everything should work but it just will not complete.
j.sax.riley said:
It says on the prompt that it completed successfully with the unlock, however i do not receive a prompt on the device stating the developer options to accept or deny.
I will proceed as if i did and try my att ruu to try and update the device.
I tried with a google ruu and get signature verify fail, i think that i get the same issue with the att ruu.
IF you can suggest a RUU that will help me out of the situation i would really appreciate it.
Also if there is any reason why rum runner will not complete, i can swear adb is up everything should work but it just will not complete.
Click to expand...
Click to collapse
Turning security back to ''on'' and relocking your bootloader on GPE was a bad decision, you probably bricked your device forever.
This is discussed in this thread: http://forum.xda-developers.com/showthread.php?t=2547894
With S-ON and Locked (Re-Locked) bootloader, your only hope is to flash a RUU of same or higher version than the version currently installed on your phone. You can't downgrade anything with s-on using a ruu.exe neither a ruu.zip. You are stuck until htc release a newer gpe ruu.
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO
alray said:
Turning security back to ''on'' and relocking your bootloader on GPE was a bad decision, you probably bricked your device forever.
This is discussed in this thread:
With S-ON and Locked (Re-Locked) bootloader, your only hope is to flash a RUU of same or higher version than the version currently installed on your phone. You can't downgrade anything with s-on using a ruu.exe neither a ruu.zip. You are stuck until htc release a newer gpe ruu.
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO
Click to expand...
Click to collapse
Is there any chance of spoofing the ruu.zip to make it look like a higher verison?
If not that can i just flash a recovery image even if its stock so i can have a recovery as i currently don't even have that which i think is the source of my problems.
j.sax.riley said:
Is there any chance of spoofing the ruu.zip to make it look like a higher verison?
If not that can i just flash a recovery image even if its stock so i can have a recovery as i currently don't even have that which i think is the source of my problems.
Click to expand...
Click to collapse
Unfortunately no. ''spoofing'' the ruu will require to decrypt it. With s-on you can't flash a decrypted ruu, you can only flash a ruu that is signed with HTC private key (decrypted ruu can't be signed back with HTC private key). S-OFF would have saved your phone in this case.
The only way to flash the stock recovery in your case is to flash a signed firmware.zip of the same of higher version.
Still waiting your ''fastboot getvar all'' output
alray said:
Unfortunately no. ''spoofing'' the ruu will require to decrypt it. With s-on you can't flash a decrypted ruu, you can only flash a ruu that is signed with HTC private key (decrypted ruu can't be signed back with HTC private key). S-OFF would have saved your phone in this case.
The only way to flash the stock recovery in your case is to flash a signed firmware.zip of the same of higher version.
Still waiting your ''fastboot getvar all'' output
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
j.sax.riley said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Afaik, there is no ruu you can flash. Your version is 3.62.1700.1 and the latest ruu I can find is 3.58.1700.5 which is a downgrade (require S-OFF) You'll need to find or wait for a ruu higher or equal to 3.62.1700.1
alray said:
Afaik, there is no ruu you can flash. Your version is 3.62.1700.1 and the latest ruu I can find is 3.58.1700.5 which is a downgrade (require S-OFF) You'll need to find or wait for a ruu higher or equal to 3.62.1700.1
Click to expand...
Click to collapse
That sux.
Are you sure there is no other way?
The htc regular version stock is version 4 something and so i was hopping that would override any bull**** i have going on.
i tired temp roots to see if i can s-off in os with firewater but i was unsuccesffully at gaining temp root.
Its funny to me because i swear reading somewhere that "andoid 4.4 is great" dont even have to root because of app ops or something but its obvious now thats a load of b.s and i should have just always run rooted as that has never done me wrong.
Do you know where i would find a ruu when one comes out? as one probably will with 4.4.3 coming out soon.
j.sax.riley said:
That sux.
Are you sure there is no other way?
Click to expand...
Click to collapse
If you can't s-off using rumrunner or firewater then no, idt there is other options.
j.sax.riley said:
The htc regular version stock is version 4 something and so i was hopping that would override any bull**** i have going on.
Click to expand...
Click to collapse
The international version ruu is a .401 base (not .1700) and require to change CID and probably MID. Changing those values require S-OFF!
j.sax.riley said:
Do you know where i would find a ruu when one comes out? as one probably will with 4.4.3 coming out soon.
Click to expand...
Click to collapse
htcdev.com under the ''kernel source code'' section, http://htc1guru.com and http://androidruu.com/?developer=M7
[*] Attempting to acquire root. This will take 5-10 minutes, be patient
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
This is my output from trying temp root with firewater method.
I am not sure what the issue is that is happening but i assume with the first failure the whole system collapses.
Thank you for the help btw, and i will keep my eyes open for a new ruu.
What do i need to be looking for in the ruu to make sure it will work with my phone?
Specific cid and mid?
j.sax.riley said:
What do i need to be looking for in the ruu to make sure it will work with my phone?
Specific cid and mid?
Click to expand...
Click to collapse
must be signed and same or higher version than 3.62.1700.1.
any .1700 version will match your CID and MID (GOOGL01 and PN0712000)
Last question,
Flashing a newer hboot or the "modified gpe bootloader"
Is it possible since im s-off, and will it change anything?
And why wont this zip work?
RUU Zip M7 Google Edition 4.4 3.58.1700.5
Because its version 3.58 and i am 3.62?
I like Htc phones and especially their commitment to bring timely updates.
But.....i do miss being able to use odin and never have to worry if your device gets f-ed up you can always reformat it to stock without trying to get a warranty replacement (which i cant because i'm rocking my google play edition) which is great and totally beats cyanogen mod for stability.
Although....i miss blink feed lol
j.sax.riley said:
Last question,
Flashing a newer hboot or the "modified gpe bootloader"
Is it possible since im s-off, and will it change anything?
Click to expand...
Click to collapse
Fomr the output of your fastboot getvar all, you are S-ON not S-OFF so you won't be able to flash a modifed hboot. Btw, if you flash a modified hboot in the future with s-off, you will brick your device if you s-on again (with a modified hboot)
j.sax.riley said:
And why wont this zip work?
RUU Zip M7 Google Edition 4.4 3.58.1700.5
Because its version 3.58 and i am 3.62?
Click to expand...
Click to collapse
Yes, 3.58 is a downgrade of version from what you have currently on your phone. Downgrading require S-OFF

As if I'd never touched it

Is there a way to make it so my HTC One is back to complete factory settings. I want it back as if I'd never touched it. Unrooted, locked, S-ON, HTC Sence, stock firmware, etc.
I'm not so great at all this stuff, so some simple instructions rather than just a tonne of links would be great! Eg. flash this, do this, install this recovery, etc.
Thanks,
Joe
smartiejoe said:
Is there a way to make it so my HTC One is back to complete factory settings. I want it back as if I'd never touched it. Unrooted, locked, S-ON, HTC Sence, stock firmware, etc.
I'm not so great at all this stuff, so some simple instructions rather than just a tonne of links would be great! Eg. flash this, do this, install this recovery, etc.
Thanks,
Joe
Click to expand...
Click to collapse
Maybe you should start by describing what you did to your phone? Also post the output of fastboot getvar all except IMEI
alray said:
Maybe you should start by describing what you did to your phone? Also post the output of fastboot getvar all except IMEI
Click to expand...
Click to collapse
First off, it is rooted, has twrp recovery, a 4.4 GPE ROM and is S-OFF.
I'll get the fastoobt getvar all results for you.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT368W908963
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3661mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae095083bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
smartiejoe said:
First off, it is rooted, has twrp recovery, a 4.4 GPE ROM and is S-OFF.
I'll get the fastoobt getvar all results for you.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT368W908963
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3661mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae095083bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
you want to return it to stock like if you had never touched it.. So you want stock software, locked bootloader and S-ON ? If you are not sending your phone for a repair under warranty, I'll recommend you to keep unlocked bootloader and S-OFF or at least locked bootloader but S-OFF. Do you want to be on latest stock version? If yes then its almost impossible to s-off again on hboot 1.56.
What is your goal to restore your phone back to 100% stock?
Also need to know what operating system is on your computer.
alray said:
you want to return it to stock like if you had never touched it.. So you want stock software, locked bootloader and S-ON ? If you are not sending your phone for a repair under warranty, I'll recommend you to keep unlocked bootloader and S-OFF or at least locked bootloader but S-OFF. Do you want to be on latest stock version? If yes then its almost impossible to s-off again on hboot 1.56.
What is your goal to restore your phone back to 100% stock?
Also need to know what operating system is on your computer.
Click to expand...
Click to collapse
Just in case I do need to send it off for repair or replacement, I don't want a tampered device. Just don't want that risk. I'm running WIndows 7.
smartiejoe said:
Just in case I do need to send it off for repair or replacement, I don't want a tampered device. Just don't want that risk. I'm running WIndows 7.
Click to expand...
Click to collapse
You should keep s-off unless really necessary, not ''just in case''. If you need to send your phone for repair in the future, with s-off, you'll be able to remove the tampered flag and s-on again before sending it back to repair. But atm turning back S-ON is the risk you should not take imo.
Again if you go back to stock and update your phone to the latest version then it will be very difficult or even not possible to s-off again.
Im waiting your decision to guide you.
S-OFF is a gift and should never be taken for granted. If you throw it away it may not be available to you again.
S-ON is an operation I would defer until I learned that I actually *need* to send in the phone to someone who cares if it is S-ON or not.
S-ON is always the last step in any "going back to stock " process, the very last thing before the phone leaves your possession. And even then the step is usually optional. Warranty repair people often don't care, eBay doesn't care, it's just really rare that there is *any* actual benefit.
Sent from my HTC One using xda app-developers app
alray said:
You should keep s-off unless really necessary, not ''just in case''. If you need to send your phone for repair in the future, with s-off, you'll be able to remove the tampered flag and s-on again before sending it back to repair. But atm turning back S-ON is the risk you should not take imo.
Again if you go back to stock and update your phone to the latest version then it will be very difficult or even not possible to s-off again.
Im waiting your decision to guide you.
Click to expand...
Click to collapse
Okay, I think I'll stick with S-OFF, I just want a really stable build, as close to stock as possible. Decent battery life, decent speed, and not too much hassle to return to complete stock if necessary.
I'll take your advice on what you think is best!
smartiejoe said:
Okay, I think I'll stick with S-OFF, I just want a really stable build, as close to stock as possible.
Click to expand...
Click to collapse
You can use the stock RUU for your phone version, so you'll be 100% stock rom but with s-off and unlocked bootloader
smartiejoe said:
not too much hassle to return to complete stock if necessary.
Click to expand...
Click to collapse
Easy to do with S-OFF
So you can use the latest RUU for your phone which you can find here
this will make your phone 100% stock (except s-off and unlocked bootloader). This will wipe everything on your phone so be sure to backup your media and personal data before on your computer.
download the exe file (about 1.5Gb)
plug your phone to your computer ( I assume your htc drivers are already installed correctly, if yes, your device is listed as ''My HTC'' in windows device manager)
launch the ruu.exe and follow instructions.
alray said:
You can use the stock RUU for your phone version, so you'll be 100% stock rom but with s-off and unlocked bootloader
Easy to do with S-OFF
So you can use the latest RUU for your phone which you can find here
this will make your phone 100% stock (except s-off and unlocked bootloader). This will wipe everything on your phone so be sure to backup your media and personal data before on your computer.
download the exe file (about 1.5Gb)
plug your phone to your computer ( I assume your htc drivers are already installed correctly, if yes, your device is listed as ''My HTC'' in windows device manager)
launch the ruu.exe and follow instructions.
Click to expand...
Click to collapse
Hi there,
I downloaded the RUU and ran it and followed all instructions but it encounters an error every time. It doesn't give any information on what the error is, it just stays on the silver HTC logo and the software says it has failed. It doesn't get stuck in a bootloop though.
Thanks,
Joe
smartiejoe said:
Hi there,
I downloaded the RUU and ran it and followed all instructions but it encounters an error every time. It doesn't give any information on what the error is, it just stays on the silver HTC logo and the software says it has failed. It doesn't get stuck in a bootloop though.
Thanks,
Joe
Click to expand...
Click to collapse
MD5 check the ruu file and make sure it match, if not download it again.
MD5: 9ad4111ce86981e3dffcce6d9ee80551
alray said:
MD5 check the ruu file and make sure it match, if not download it again.
MD5: 9ad4111ce86981e3dffcce6d9ee80551
Click to expand...
Click to collapse
Hi,
I redownloaded it and ran it and it has been stuck on "0/5 sending" for the last 20 minutes or so, the interface says the whole process should take 10 minutes, is this normal?
smartiejoe said:
Hi,
I redownloaded it and ran it and it has been stuck on "0/5 sending" for the last 20 minutes or so, the interface says the whole process should take 10 minutes, is this normal?
Click to expand...
Click to collapse
have you checked md5?
Maybe you could try another usb cable or another usb port
alray said:
have you checked md5?
Maybe you could try another usb cable or another usb port
Click to expand...
Click to collapse
I checked MD5 and that was all fine, I'm using a different port and now it sits on "updating (1/5) Checking Header..." for ages and I've not yet seen it move any further
smartiejoe said:
I checked MD5 and that was all fine, I'm using a different port and now it sits on "updating (1/5) Checking Header..." for ages and I've not yet seen it move any further
Click to expand...
Click to collapse
Try another usb cable. You could also try the 1.28.401.7 ruu
alray said:
Try another usb cable. You could also try the 1.28.401.7 ruu
Click to expand...
Click to collapse
I just read somewhere that hboot 1.44 might be needed, and I have 1.54. So I shall flash 1.44 and see if it works then!
EDIT: When trying to flash hboot 1.44 it won't even send the 501kb zip file, even through a brand new usb cable. Updating drivers now to see if that works

[Q] RUU stuck at "checking headers"

I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.
XDA Dev said:
I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.
Click to expand...
Click to collapse
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!
SaHiLzZ said:
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!
Click to expand...
Click to collapse
Haha, thanks, I guess nearly 3 years of lurking on these forums taught me something about posting.
I was using a Windows Vista SP2 PC to try this. I've just tried it on my Mac running Windows 7 SP1 with bootcamp, the RUU file (which still checks out with the correct MD5 hash) starts the installshield wizard normally, but as soon as I accept the terms and conditions, the program closes and nothing opens again. I checked on task manager, the process closes shortly after accepting the terms. I tried restarting and looking up for a solution but I couldn't find anything that worked.
Is Vista really the only reason it's stuck at checking headers? I know Vista is rather despised by a lot of people, but by 2014 it did get better. I'd rather use that machine because on my Mac running Windows 7 the RUU could not start up because I've made the Windows partition too small. (It has around 3gb free now whereas the vista machine has more than 150).
Sorry for the double post, but it's probably my last one on this thread.
Even if my boot loader was re-locked, I tried running the firewater program to get s-off, and it worked. (As a bonus it re-unlocked my boot loader without wiping the phone, but I re-locked it again to get the ruu working).
Then I tried downgrading to hboot 1.44, but for some reason it kept giving an error like "failed: remote 42 custom id check fail." I decided to try the sense 5.0 ruu anyway (on my vista PC), and it worked! The phone now says "relocked" but tampered is gone of course, and I have hboot 1.44, android 4.1 and htc sense 5.0, but still s-off.
The first update popped up (and it's not android 4.4 with sense 6, it's something in between) so I'm going to update until no more updates are available. Then I'm going to re-unlock the boot loader because I want to root my phone, and then set up all my stuff. When a new update comes out, I can just flash the original recovery, apply the update and then re-flash twrp to root again.
Thank you for the suggestion to install the older ruu. I'm still stumped on why the newer one didn't work (it would have caused much less hassle), but whatever. At least my phone is much cleaner now. It feels good to have it like this again, I'm not against custom roms but I like the stock software too.
I'm using my iPhone to write this, but trust me, my htc is in full working order now.
Until next problem I can't solve myself
Sent from my iPhone using Tapatalk
Thanks for updating back. Don't S-ON.
SaHiLzZ said:
Thanks for updating back. Don't S-ON.
Click to expand...
Click to collapse
Yeah, I'm not going to. I've updated to android 4.3 now and I'm still downloading updates--it updated hboot to 1.55 but I still have s-off, so I believe it stays s-off if I don't run the command to (I guess irreversibly) go back to s-on, which I don't even know. (I didn't do s-off before because I didn't care about the extra privileges and was afraid of bricking my phone, but now that I have it I don't mind so I'm keeping it).
Sent from my iPhone using Tapatalk

[Q] Restoring 100% to stock, not working as it should...

Hi guys,
First of all, I did read all the topics conserning to RUU, S-On/S-Off, rumrunner, moonshine, firewater, revone, and so on but I can't seem to figure out how to properly do this.
Currently the HTC is running MIUI v5 4.5.16 JB4.2. But for warranty it has to go back to the store and I want to restore it to completly stock ROM etc. without any evidence I had a custom ROM running.
What I did was, follow the steps to unlock the bootloader, flash a custom recover (TWRP v2.6.3.0) and finally root it after MIUI was flashed.
The info you guys prolly need are as followed:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.26.3263.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: .................
(bootloader) imei: ................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.038s
Click to expand...
Click to collapse
I tried to get S-Off but I keep getting strange errors on all of the given methods. This should work somehow I guess but how? Can somebody give me some kind of "roadmap" how to do it properly?
Currently fastboot shows:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
Mar 5 2014,15:58:33.0
Click to expand...
Click to collapse
At the moment I'm downloading "RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe". But I already noticed that if I turn S-On (fastboot oem lock) then the phone is stuck in fast boot mode...
Thanks!
I think S-off is danger may u brick ur phone, it's better to leave it
ahmed blue said:
I think S-off is danger may u brick ur phone, it's better to leave it
Click to expand...
Click to collapse
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...................
(bootloader) imei: ....................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4185mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".
BETA911 said:
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".
Click to expand...
Click to collapse
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.
Seanie280672 said:
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.
Click to expand...
Click to collapse
Well... It said it had a OTA update (like before) to 4.3 and I downloaded it. Reboot, installed, reboot --> bootloop. Now it's "HTC - quietly brilliant", black screen for couple of seconds and reboot to start from HTC logo again...
It's really beginning to piss me of.
But anyway, thanks for the help! A TWRP backup of 161 would be nice, then I'll install that one. The servers at htc1guru are giving me headache, speed is only between 50 and 250 kb/sec! I tried to download more then once but they keep failing on me when they reach bigger sizes and at this speed it's really really annoying to start over again...
Does "M7 CWM Nandroid Backup CID VODAP102 1.29.161.7" work for me? I guess not because it's 1.29 and I already have a higher version so it will give me the touchscreen issues?
To be honest, if this phone finally makes it to the store for repair I hope they can't repair it and let me choose an other phone. I had multiple Android phones the past years (with sometimes more then 2-3 different roms per week) and never had any of these long stretching problems!
The problem your having with the ota sounds like whilst you were installing the guru reset file, you must select to wipe data and also install stock recovery, it will fail without stock recovery.
Well, I did select to install the stock recovery and stock radio in the aroma installer. So I'm out of clues why it's giving me so much problems...
EDIT:
I unlocked the bootloader again and flashed TWRP. I'll try with your Vodafone image once you have time to share it with me. Already big thanks for the help!
here's the backup, you will need to extract the zip file and put the folder named backup into SDCARD/TWRP/BACKUPS/"your device serial number/
https://drive.google.com/uc?export=download&confirm=5940&id=0B_nEcSZr5peRZnpMSHRPRjlzX2c
This will put you on Vodafone 4.4.2 with sense 5.5, however you cant send your phone back until you have got rid of those 2 flags in the bootloader, only way to do that is s-off.
Ignore the folder called recovery, its just TWRP recovery to flash.
After installing, download the stock recovery from the link below and flash it to get OTAs
http://d-h.st/Cyq
Hit the thanks button please.
Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.
BETA911 said:
Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.
Click to expand...
Click to collapse
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom
alray said:
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom
Click to expand...
Click to collapse
I know. I tried to get s-off but none of the given tools succeeded. They all complete their full cycle and eventually after the last reboot I go and check the state and it still says s-on... Then I did read I need a proper ROM so the tools can work (better). I tried to install ARHD like you mention, but after flashing it was stuck in a bootloop again. Clearing the cache and davlik didn't solve it.
At the moment I only need to know if it's safe to update to the new 5.16.161.2 update while it's unlocked... I got TWRP installed but I know I have to flash the stock recovery in order to make the update work. But I'm afraid I'm going to brick it again if I lock it again, as I don't know if it's needed to let the update complete without any errors.

HTC One rooted - Return for Warranty [SOLVED]

Hi,
I have a HTC One that is rooted, and has the problem with the camera (Pink in dark places).
I've have MIUI custom rom, but to return for warranty i need to have the oficila rom.
What do i need to do for restore to the official rom, to turn s-on, and delete all races of a root phone.
I've only changed the software, not the CID.
MY CID is HTC_304.
Thanks for all the help
nurogo said:
Hi,
I have a HTC One that is rooted, and has the problem with the camera (Pink in dark places).
I've have MIUI custom rom, but to return for warranty i need to have the oficila rom.
What do i need to do for restore to the official rom, to turn s-on, and delete all races of a root phone.
I've only changed the software, not the CID.
MY CID is HTC_304.
Thanks for all the help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2541082
please post a "fastboot getvar all" (excluding IMEI and s/n) and i'll check which files you need
nkk71 said:
http://forum.xda-developers.com/showthread.php?t=2541082
please post a "fastboot getvar all" (excluding IMEI and s/n) and i'll check which files you need
Click to expand...
Click to collapse
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4232mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks
nurogo said:
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4232mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks
Click to expand...
Click to collapse
Anyone, please?
nurogo said:
Anyone, please?
Click to expand...
Click to collapse
use the 1.28.401.7 RUU http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
follow guide linked by nkk71
nurogo said:
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) security: on
Thanks
Click to expand...
Click to collapse
I thought you said you were S-OFF, but you are actually S-ON, so bootloader can only show RELOCKED
so two choices:
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
B) RELOCK bootloader (though you may have a hard time with a RELOCKED bootloader for warranty):
fastboot oem lock (to RELOCKED bootloader)
then use the ruu.exe alray linked
nkk71 said:
I thought you said you were S-OFF, but you are actually S-ON, so bootloader can only show RELOCKED
so two choices:
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
B) RELOCK bootloader (though you may have a hard time with a RELOCKED bootloader for warranty):
fastboot oem lock (to RELOCKED bootloader)
then use the ruu.exe alray linked
Click to expand...
Click to collapse
Thanks for all the help.
If I have understood correctly, i will not be able to get s-on after installing the stock rom.
I have to put s-off in order to install the stock rom?
Then to put in s-on, always appears relocked?
There are possibilities to install the stock rom without removing the S-ON?
nurogo said:
Thanks for all the help.
If I have understood correctly, i will not be able to get s-on after installing the stock rom.
I have to put s-off in order to install the stock rom?
Then to put in s-on, always appears relocked?
There are possibilities to install the stock rom without removing the S-ON?
Click to expand...
Click to collapse
no, sorry if I confused you.
for bootloader to say LOCKED (the same way it was when you first got it), you need to get S-OFF.
with S-OFF, you can set it back to LOCKED, and completely "out of the box", (using the ruu.zip process with the file i linked earlier), and can even go back S-ON (as mentioned in my guide) and it will still say LOCKED.
but without S-OFF, you can only get bootloader to show RELOCKED.
I hope that makes it a bit clearer.
nkk71 said:
no, sorry if I confused you.
for bootloader to say LOCKED (the same way it was when you first got it), you need to get S-OFF.
with S-OFF, you can set it back to LOCKED, and completely "out of the box", (using the ruu.zip process with the file i linked earlier), and can even go back S-ON (as mentioned in my guide) and it will still say LOCKED.
but without S-OFF, you can only get bootloader to show RELOCKED.
I hope that makes it a bit clearer.
Click to expand...
Click to collapse
Thanks,
Now i get it.
This is the guide i must follow, right?
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
nurogo said:
Thanks,
Now i get it.
This is the guide i must follow, right?
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
Click to expand...
Click to collapse
yes, first get s-off - should be easy enough considering your current getvar output, you have plenty of options, once you have s-off, you can use ruu.zip method to return to 100% "out of the box"
nkk71 said:
yes, first get s-off - should be easy enough considering your current getvar output, you have plenty of options, once you have s-off, you can use ruu.zip method to return to 100% "out of the box"
Click to expand...
Click to collapse
Tried to put s-off, but it gives the error:
revone failed (error code = 1)
Why this error? What i did wrong?
nurogo said:
Tried to put s-off, but it gives the error:
revone failed (error code = 1)
Why this error? What i did wrong?
Click to expand...
Click to collapse
what date is show in bootloader, if it is before June 2013, then install the ROM mentioned here:
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and try revone again, otherwise use rumrunner or firewater if revone is giving you a hard time.
nkk71 said:
what date is show in bootloader, if it is before June 2013, then install the ROM mentioned here:
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and try revone again, otherwise use rumrunner or firewater if revone is giving you a hard time.
Click to expand...
Click to collapse
Done...
Now i have s-off...
Now, what do i have to do is follow step by step the post #4 of your guide, correct?
http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
nurogo said:
Done...
Now i have s-off...
Now, what do i have to do is follow step by step the post #4 of your guide, correct?
http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
Click to expand...
Click to collapse
yes correct, follow instructions in the guide, if you already have a custom recovery installed:
1) use adb commands to remove TAMPERED and set LOCKED
2) flash the following ruu.zip: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
3) bootup once to make sure everything is OK, do not take OTA updates
4) if you believe S-ON is necessary for warranty, then go S-ON
after that you can take any OTAs you like,
but why bother since it's going to repair. where they will most like update it anyway
nkk71 said:
yes correct, follow instructions in the guide, if you already have a custom recovery installed:
1) use adb commands to remove TAMPERED and set LOCKED
2) flash the following ruu.zip: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
3) bootup once to make sure everything is OK, do not take OTA updates
4) if you believe S-ON is necessary for warranty, then go S-ON
after that you can take any OTAs you like,
but why bother since it's going to repair. where they will most like update it anyway
Click to expand...
Click to collapse
Thanks for all the help,
After do all that, how do i remove all traces of custom rom's (folders, files, TWRP, etc..)?
is there a way to format the phone, removing all that (like formating a hard drive)?
nurogo said:
Thanks for all the help,
After do all that, how do i remove all traces of custom rom's (folders, files, TWRP, etc..)?
is there a way to format the phone, removing all that (like formating a hard drive)?
Click to expand...
Click to collapse
The ruu will take care of that, it will wipe everything off your phone, including anything on the virtual sdcard
Sent from my HTC One using Tapatalk
Ok.. Here's the situation
Removed TAMPERED and now it says LOCKED
But when i try to copy the ruu.zip it says:
load_file: could not allocate 1034027008 bytes
error: cannot load "ruu.zip": Not enough space..
How can i solve this?
I have 20GB free of space...
nurogo said:
Ok.. Here's the situation
Removed TAMPERED and now it says LOCKED
But when i try to copy the ruu.zip it says:
load_file: could not allocate 1034027008 bytes
error: cannot load "ruu.zip": Not enough space..
How can i solve this?
I have 20GB free of space...
Click to expand...
Click to collapse
Cannot load = MyFileNameIsWrong
Sent from my HTC One using Tapatalk
nkk71 said:
Cannot load = MyFileNameIsWrong
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Check it, but it stays the same..
Look at the image
nurogo said:
Check it, but it stays the same..
Look at the image
Click to expand...
Click to collapse
type dir in the command window
you probably see it's names RUU.zip.zip

Categories

Resources