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?
Related
Hey guys,
Right, I have a hardware issue with my phone so need to return it to Three UK.
Currently I have Android Revolution HD 11 on my phone and have updated to 2.17 firmware, s-off.
So I need stock, firmware to be reverted to 1.28.771 and to change my CID to H3G__001 (currently HTC__001). There doesn't appear to be an RUU for three.
First off I'm assuming the H3G nandroid backup in the "[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads" thread doesn't actually touch the firmware so it would remain at 2.17?
So my thinking is this:
Flash the generic europe RUU (do I need to lock my bootloader before doing this)? (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe)
Change CID to H3G__001
Nandroid restore of H3G ROM. (M7 CWM Nandroid Backup / CID H3G__001 / 1.28.771.x )
s-off to lock and remove tamper.
s-on.
OTA update?
Will this work?
Or does anyone have a link to the 1.28.771 firmware?
Thanks for the help.
Ardmanz said:
Hey guys,
Right, I have a hardware issue with my phone so need to return it to Three UK.
Currently I have Android Revolution HD 11 on my phone and have updated to 2.17 firmware, s-off.
So I need stock, firmware to be reverted to 1.28.771 and to change my CID to H3G__001 (currently HTC__001). There doesn't appear to be an RUU for three.
First off I'm assuming the H3G nandroid backup in the "[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads" thread doesn't actually touch the firmware so it would remain at 2.17?
So my thinking is this:
Flash the generic europe RUU (do I need to lock my bootloader before doing this)? (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe)
Change CID to H3G__001
Nandroid restore of H3G ROM. (M7 CWM Nandroid Backup / CID H3G__001 / 1.28.771.x )
s-off to lock and remove tamper.
s-on.
OTA update?
Will this work?
Or does anyone have a link to the 1.28.771 firmware?
Thanks for the help.
Click to expand...
Click to collapse
Any ideas?
You don't have to lock the bootloader and you need s-off to downgrade.
http://forum.xda-developers.com/showpost.php?p=42396455&postcount=20
Rest of the steps...well sounds good but unfortunatelly i'm not expert so dunno
I'm really interested if it works this way for you as i have a VF-uk one, and once i have to go back to stock this info would be really helpful.
Please let we know your progress
Good luck
prodizo said:
You don't have to lock the bootloader and you need s-off to downgrade.
http://forum.xda-developers.com/showpost.php?p=42396455&postcount=20
Rest of the steps...well sounds good but unfortunatelly i'm not expert so dunno
I'm really interested if it works this way for you as i have a VF-uk one, and once i have to go back to stock this info would be really helpful.
Please let we know your progress
Good luck
Click to expand...
Click to collapse
Hey,
Yup this worked perfectly (almost). Reset your CID to your originally carriers before running the nandroid backup or it will be missing your carriers boot screen.
The only thing is the recovery seems to be missing. I'd expect the HTC recovery to load when selecting it from the bootloader but all I get is a red triangle. I obviously need to sort this before sending it back (Monday).
Any ideas?
I haven't s-on'd yet because I want to sort out recovery first. That should be pretty simple though.
I guess I just need a link to stock recovery.img.
Just tried and mine does same. I have stock recovery so thats fine.
Hope you get a nice new one:laugh:
Cheers
Stock recovery will display a red triangle..your all set
Sent from my HTC One using xda app-developers app
Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.
Ardmanz said:
Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.
Click to expand...
Click to collapse
Ardmanz said:
Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.
Click to expand...
Click to collapse
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?
Grand_Goblin said:
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?
Click to expand...
Click to collapse
Yup, those are the exact steps that I took.
Note* make sure you just boot into custom recovery and don't actually flash it when restoring your nandroid backup. Having custom recovery on your device is a dead give away.
Grand_Goblin said:
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?
Click to expand...
Click to collapse
Ardmanz said:
Yup, those are the exact steps that I took.
Note* make sure you just boot into custom recovery and don't actually flash it when restoring your nandroid backup. Having custom recovery on your device is a dead give away.
Click to expand...
Click to collapse
sorry man, but "flash it" refers to?
I don't get it and I don't wanna mess up
Grand_Goblin said:
sorry man, but "flash it" refers to?
I don't get it and I don't wanna mess up
Click to expand...
Click to collapse
Normally you would use the following command to install custom recovery:
Code:
fastboot flash recovery recovery.img
Use this command instead:
Code:
fastboot boot recovery.img
That allows you to boot into custom recovery without actually installing it onto your phone.
Ardmanz said:
Normally you would use the following command to install custom recovery:
Code:
fastboot flash recovery recovery.img
Use this command instead:
Code:
fastboot boot recovery.img
That allows you to boot into custom recovery without actually installing it onto your phone.
Click to expand...
Click to collapse
matursuwun - Thank You so much! (in Javanese)
Hello All,
Here's my dilemma. I successfully rooted my HTC One (AT&T), and was recently attempting to unroot it. I followed this one here http://forum.xda-developers.com/showthread.php?t=2182823. Since I have the AT&T version, I downloaded the first one the list found there, however it wouldn't verify. Next I downloaded the AT&T AIO here http://forum.xda-developers.com/showthread.php?t=2242635. I was able to use that to figure out according to the info it displayed that I actually needed the Google Edition one from the previous link. I thought that was weird since I dont have the google edition one. But when I fast booted that one, everything appeared to go through with a hitch.....Until it restarted.
After it restarted, I only have a black screen. No start up. I restarted the phone and went into the bootloader and to my surprise, the bootloader was black instead of the normal white.
I've tried several RUUs found here http://www.androidruu.com/index.php?developer=M7
I've tried both the exe and flashing the zip.
I have no clue what to try next. Please XDA, your my only hope.
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
iElvis said:
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
Click to expand...
Click to collapse
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Tylegn said:
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Click to expand...
Click to collapse
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
iElvis said:
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
Click to expand...
Click to collapse
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Tylegn said:
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Click to expand...
Click to collapse
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
iElvis said:
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
Click to expand...
Click to collapse
I received the phone directly from HTC through a sell to earn contest.
Not sure if it matters much but I unlocked the bootloader through HTC Dev.
To unroot,
1) Put phone in bootloader with fastboot
2) Relocked bootloader
3) fastboot oem rebootRUU
4) fastboot flash zip 2.24.401.1.zip (failed)
Used one of the AIOs that stated I had modelid: PN0712000 and cidnum: CWS__001. That when I grabbed the GE version.
5) fastboot flash zip 3.06.1700.10.zip
6) Phone finished, rebooted to a black screen
7) Rebooted into bootloader (Which is now black instead of white)
8) Sad ever since....
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
ageldea consider
iElvis said:
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
Click to expand...
Click to collapse
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Tylegn said:
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Click to expand...
Click to collapse
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
Found the stock recovery. Attempted to flash it and got this:
sending 'recovery' <16303 KB>...
OKAY [ 1.786s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote: 12 signature verify fail>
finished. total time: 3.178s
Is there a different way I should be doing it.
HTC One has the Gray HTC logo chilling on the screen...
Also tried in normal fastboot mode...
Tylegn said:
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
Click to expand...
Click to collapse
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
iElvis said:
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
Click to expand...
Click to collapse
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
ADD: I just successfully flashed the stock recovery.... Too scared to muck something up so I'll waif for your superior guidance!
Thanks again
Tylegn said:
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
Click to expand...
Click to collapse
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
iElvis said:
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
Click to expand...
Click to collapse
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Tylegn said:
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Click to expand...
Click to collapse
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
iElvis said:
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
Thank you so much! I believe I can take it from here.....Until I brick my phone when the signed 4.3 comes out. LOL
Until next time. Thanks iElivis you are a BADA$$!:good::good::good:
There is no ruu for my phone (02___001) so now I have s off I was going to run a stock ruu and update to the latest firmware. If I send the phone back for repair and change my cid to HTC_001 would HTC know I have changed my cid even if I s on?
Anyone help me at all?
stovie_steve said:
Anyone help me at all?
Click to expand...
Click to collapse
Two things:
1- I dont know if they keep a record of IMEI (or s/n) <--> carrier, but I think they have to and do.
2- the CID is stored in several partitions, not only the one you change with fastboot writecid.
HOWEVER, it really depends on how far they're going to dig into this, if they are going to check their IMEI database or check the different partitions on the phone, just to "prove you wrong", I guess they could.
But then again, would it be worth all that hassle for them?
I dont have any experience with repair centers or how far they would go to prove that you changed something on your phone, and it's really quite country (and HTC people) dependent; for some they have no problem with an unlocked or relocked phone, and other even have a problem with S-Off (though they can't prove the phone didn't ship that way in the first place)
Better have someone from your region (O2 so UK?) post their experience(s)
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
stovie_steve said:
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
Click to expand...
Click to collapse
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
nkk71 said:
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
Click to expand...
Click to collapse
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
stovie_steve said:
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
Click to expand...
Click to collapse
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
nkk71 said:
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
Click to expand...
Click to collapse
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
stovie_steve said:
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
Click to expand...
Click to collapse
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
stovie_steve said:
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
Click to expand...
Click to collapse
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
stovie_steve said:
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
Click to expand...
Click to collapse
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
nkk71 said:
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
Click to expand...
Click to collapse
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
stovie_steve said:
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
Click to expand...
Click to collapse
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
nkk71 said:
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
Click to expand...
Click to collapse
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
stovie_steve said:
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
Click to expand...
Click to collapse
Ok, my thoughts, in a nutshell
1. Unlock bootloader via HTC dev <- YES
2----- try rumrunner 3.62
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off <- Ok, try, if it fails use above rumrunner 3.62
Once S-Off:
--- remove tampered: revone or http://forum.xda-developers.com/showthread.php?t=2477792
5. Restore nandroid backup for my 02 version 1.28.206.7
--- set phone to LOCKED, using revone (or http://forum.xda-developers.com/showthread.php?t=2475914)
------- you will need to have SU privileges which you can get using revone or flashing SuperSU; if you do flash SuperSU, uninstall it after getting LOCKED
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match) <- Yep
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Once you have your bootloader "LOCKED", no TAMPERED, no red text on bootup, do "fastboot oem writesecureflag 3"
reboot three times and see if everything sticks, and don't take any other OTAs.
Hit me with a thanks if this was useful
So you think I shouldn't upgrade to the latest OTA once I get s on?
stovie_steve said:
So you think I shouldn't upgrade to the latest OTA once I get s on?
Click to expand...
Click to collapse
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
nkk71 said:
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
Click to expand...
Click to collapse
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
nkk71 said:
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
Click to expand...
Click to collapse
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
stovie_steve said:
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
Click to expand...
Click to collapse
the touchscreen drivers were part of the 2.xx firmware package, not hboot, so if you don't use a full RUU, it will break the touchscreen drivers, but you can use an OTG cable + mouse.
stovie_steve said:
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
Click to expand...
Click to collapse
Unfortunately you can't (anymore), but this one should be close enough: http://d-h.st/users/guich/?fld_id=25920#files, or the best thing is to get a hold of the OTA 3.62.206.1 file and extract it from it.
Anyway, in my humble opinion, first things first: unlock using HTCdev and see if you can get rumrunner to S-Off on 3.62.
Hello,
probably silly question and you will order me to study xda.
Unfortunately, i have came through almost every single topic, and can't get to "move" from my situation.
I received Htc One with Hboot v 1.54.000, locked bootloader - S-ON.
Software number 2.24.111.5 (android 4.2.2 with Sense 5). My cid (read through CidGetter from playstore) - T-MOB101.
I am trying to avoid unlocking bootloader via htc-dev, as afaik it voids the warranty.
I am not interested in custom roms. Rather, i would like to "fool" the phone and make it like it was European distribution, with no branding, so i would receive OTA as anyone else with unbranded phone.
If i understood correctly, to achieve this, basically i need to change my CID to european or supercid, which will enable to install any ruu from htc. But european otas would be enough for me. To change cid, i need S-OFF, right ?
There are basically three methods, if i read correctly, right ?
1, Revone - doesn't work with Hboot 1.54
2, Moonshine - Works without htc-dev unlocking, but installs custom bootloader, which will disable otas to install.
3, Rumrunner - Works with 1.54 bootloader, but i need to htc dev unlock ?
So, am i understanding correctly, that as long as i dont want to htc dev unlock, i am stuck to my cid, and dependent from german t-mobile ? So i can only hope, some dev will find exploit in Hboot 1.54 ?
Isn't there any miracle, that could help to solve my problem ?
Thanks
Rumrunners is the only solution with an htc dev unlock...
If you will remove the cid and put an european is the best thing to do.
You can always put the locked string
Yes,
but Htc will know, that i requested unlock keys.
Won't be that problem ?
Also, does htc-dev unlock automatically mean warranty void ?
remusator said:
Yes,
but Htc will know, that i requested unlock keys.
Won't be that problem ?
Also, does htc-dev unlock automatically mean warranty void ?
Click to expand...
Click to collapse
Yeah, i know that htc will know, but i never had a problem.
When i had the Evo 3D i unlocked with htcdev and after s-offed, so i relocked and s-on for warranty e no prob
MY friends with this phone didn't had any problem with warranty also with an unlocked with htcdev...
Remusator - I'm looking for the same thing: I have UK orange firmware, and was hoping to get stock/unbranded CID so I can get regular OTAs. Please let me know if you figure it out
Desperately waiting and hoping for some dev to soff without dev.
Today an arcticle came through my hands, saying "Unlocked htc one - kitkat till end of the month". Still don't have even Jelly :/
Is someone working on this ? Please
Guich said:
Yeah, i know that htc will know, but i never had a problem.
When i had the Evo 3D i unlocked with htcdev and after s-offed, so i relocked and s-on for warranty e no prob
MY friends with this phone didn't had any problem with warranty also with an unlocked with htcdev...
Click to expand...
Click to collapse
Hello, thanks for answer. :good:
If i agree to unlock my bootloader, could i achieve things mentioned in first post ?
Could you please give me some more detailed guide (alternatively steps with topic links), which i need to proceed ?
Al i need is to fool the phone to think, that it's unlocked and receive ota's like any other european unlocked htc one.
Thanks
remusator said:
Hello, thanks for answer. :good:
If i agree to unlock my bootloader, could i achieve things mentioned in first post ?
Could you please give me some more detailed guide (alternatively steps with topic links), which i need to proceed ?
Al i need is to fool the phone to think, that it's unlocked and receive ota's like any other european unlocked htc one.
Thanks
Click to expand...
Click to collapse
OK, European unbranded:
1- get s-off: http://rumrunner.us/ (follow instructions !)
2- change CID to European unbranded such as HTC__001
fastboot oem writecid HTC__001 <- two underscores
3- I assume your model number (MID) is already PN0710000
4- remove TAMPERED, and set your phone back to LOCKED, you can use this tool from within CWM recovery: http://forum.xda-developers.com/showthread.php?t=2527194
5- Run the following RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
after the above, your phone will not be fooled into thinking it's European unbranded, it will be European unbranded, and you'll receive the OTAs.
Let me know if you need more explanations, and hit the thanks button if I've helped
Hello, thanks.
However, i am completely stock. So i don't have CWM recovery yet.
In which step will i get it ? Or am i missing something ?
Also, CID change - is it really so easy ? I have seen some guides where people needed to download, edit and then flash some hex files.
remusator said:
Hello, thanks.
However, i am completely stock. So i don't have CWM recovery yet.
In which step will i get it ? Or am i missing something ?
Also, CID change - is it really so easy ? I have seen some guides where people needed to download, edit and then flash some hex files.
Click to expand...
Click to collapse
OK, so before point 1 above:
a) use HTCdev to unlock
b) download CWM http://forum.xda-developers.com/showthread.php?t=2173863 and flash it in bootloader/FASTBOOT USB:
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
--> enter recovery
c) for rumrunner to work, you need a close to stock rom with root access, so get one from here: http://www.htc1guru.com/downloads/stock-rom-downloads/, probably this one should work: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
you need to push that to your phone:
adb push <name of rom>.zip /data/media/ <- this will take 5 to 10 minutes without any progress bar, then report success
d) in CWM recovery, now select "install zip" -> "choose zip" and flash the rom
If you're using the Guru Reset ROM, then select WIPE, select ROOT, unselect "stock recovery"
and then proceed to rumrunner
"Also, CID change - is it really so easy ?" <- yes with S-off, it is easy, and you wont have any hex-editing to do, now or in future OTAs
Hit the thanks button if i've helped
Thanks, and what will be my phone status after this procedure ?
What hboot version, son/soff, unlocked/locked.
And what recovery ? Original, or cwm ?
remusator said:
Thanks, and what will be my phone status after this procedure ?
What hboot version, son/soff, unlocked/locked.
And what recovery ? Original, or cwm ?
Click to expand...
Click to collapse
the phone will be unTAMPERED, LOCKED (not relocked), 100% out-of-the box European unbranded, HTC Sense 5 ROM v1.28.401.7, but you'll receive OTAs up to 4.3 I think.
recovery will be stock recovery not CWM, so you can receive OTA
The phone will remain S-Off, and I suggest keeping it, if YOU INSIST on going S-On you can do so after running the RUU, but before taking any OTAs, by using "fastboot oem writesecureflag 3"
nkk71 said:
the phone will be unTAMPERED, LOCKED (not relocked), 100% out-of-the box European unbranded, HTC Sense 5 ROM v1.28.401.7, but you'll receive OTAs up to 4.3 I think.
recovery will be stock recovery not CWM, so you can receive OTA
The phone will remain S-Off, and I suggest keeping it, if YOU INSIST on going S-On you can do so after running the RUU, but before taking any OTAs, by using "fastboot oem writesecureflag 3"
Click to expand...
Click to collapse
Ok, just to make sure.
When will be CWM recovery replaced with original one ? After running RUU ?
I definitely don't insist on S-ON. My warranty will be void anyways because of htc-dev unlock. And in case my phone would break down, i need S-OFF to restore everything to original.
Are there any security risks when i'm S-OFF ? Such as malware android applications etc ? As i have understood, no.
Can / should i take some full backup of my original rom, device, bootloader, recovery in case that something goes totally wrong ?
Many many thanks
What you gave me here is most complete tutorial imho
remusator said:
Ok, just to make sure.
When will be CWM recovery replaced with original one ? After running RUU ?
Click to expand...
Click to collapse
Exactly after running the RUU.exe it will restore EVERYTHING back to stock: hboot, recovery, firmware, kernel, ROM, radio
remusator said:
I definitely don't insist on S-ON. My warranty will be void anyways because of htc-dev unlock. And in case my phone would break down, i need S-OFF to restore everything to original.
Click to expand...
Click to collapse
I don't know much about warranty and what IS and IS NOT allowed, every users experience seems different, just read one today: he sent it s-off, rooted, custom rom, etc. but the blown speakers were fixed, and no questions asked.
remusator said:
Are there any security risks when i'm S-OFF ? Such as malware android applications etc ? As i have understood, no.
Click to expand...
Click to collapse
No security issues whatsoever, S-Off will only allow you to write to certain partitions you can't with S-On. The ROM (Android 4.x.x) is responsible for the malware etc.
remusator said:
Can / should i take some full backup of my original rom, device, bootloader, recovery in case that something goes totally wrong ?
Click to expand...
Click to collapse
Sure, backups are always good.
And I just checked, there's also a Guru Reset here: http://www.htc1guru.com/downloads/stock-rom-downloads/ (not your version but close enough)
And there are a couple of nandroids around as well.
remusator said:
Many many thanks
What you gave me here is most complete tutorial imho
Click to expand...
Click to collapse
You're welcome, you can always press that little THANKS button to say I was helpful
I will definitely give you thx-es
One last question.
Do i need the root ? Do i need root for rumrunner to work ?
Can't I just insted running programs from htcguru use these commands ?
http://forum.xda-developers.com/showthread.php?t=2477792 ?
Will it be the same ?
Aand how can i make full backup of whole phone ? Without installing CWM recovery and then nandroid.
remusator said:
I will definitely give you thx-es
One last question.
Do i need the root ? Do i need root for rumrunner to work ?
Can't I just insted running programs from htcguru use these commands ?
http://forum.xda-developers.com/showthread.php?t=2477792 ?
Will it be the same ?
Aand how can i make full backup of whole phone ? Without installing CWM recovery and then nandroid.
Click to expand...
Click to collapse
Yeah, su is required for rumrunner.
Yes, htcguru file use that command.
After the flash of recovery, a nandroid will backup only the OS.
For the sd you've to copy it into your pc.
remusator said:
I will definitely give you thx-es
One last question.
Do i need the root ? Do i need root for rumrunner to work ?
Can't I just insted running programs from htcguru use these commands ?
http://forum.xda-developers.com/showthread.php?t=2477792 ?
Will it be the same ?
Aand how can i make full backup of whole phone ? Without installing CWM recovery and then nandroid.
Click to expand...
Click to collapse
Guich said:
Yeah, su is required for rumrunner.
Yes, htcguru file use that command.
After the flash of recovery, a nandroid will backup only the OS.
For the sd you've to copy it into your pc.
Click to expand...
Click to collapse
Guich beat me to it
1- Yes you need root
2- the link you provided only works if you are S-Off already
3- backup everything to PC (pics, music, etc)
4- use Call Logs Backup & Restore and SMS Backup & Restore if you need them (free apps in Play Store)
5- use Helium for apps+data, since you can't use Titanium
6- backup ROM using nandroid
7- dont worry too much about the nandroid, there are ones on @crushalots site
nkk71 said:
--> enter recovery
c) for rumrunner to work, you need a close to stock rom with root access, so get one from here: http://www.htc1guru.com/downloads/stock-rom-downloads/, probably this one should work: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
you need to push that to your phone:
adb push <name of rom>.zip /data/media/ <- this will take 5 to 10 minutes without any progress bar, then report success
Click to expand...
Click to collapse
Hello, i cannot get through this point. I have installed HTC Sync, then uninstalled, so only drivers remained on my system.
I can use adb when the phone is normally booted, but then i don't have permission to write to that location.
When i reboot to recovery, adb devices shows empty list. Also that funny thing in windows taskbar starts spinning, finds "One", but fail to install driver.
Update1:
Ok, i managed to update adb driver to Android one. (http://forum.xda-developers.com/showthread.php?t=1830108 device manager section)
Now i'm at next step. I pushed zip to /data/media/, but after choosing install zip, there is none on sdcard.
Trying to push that again.
Update2:
File appeared after second push. Installing right now. Hope phone will wake after this procedure. Fingers crossed, holding breath.
Update3
Ok, i flashed RUU, everything is fine until now.
Slovak language / Slovakia as location is missing. Should / can i change my CID for something and install corresponding RUU for that CID, so i would have Slovak Language ? I also get red text saying "THIS IS TEST DEVICE...."
I think, the correct CID for my region is HTC__032 - East Europe
What is the language dependent on ? Because the same RUU you recommended for me is also for HTC__032. Is the file same and languages are allowed based on CID, or how does this work ?
Also HTC_001 is in the first wave of updates ?
Thanks
delete pls
remusator said:
Hello, i cannot get through this point. I have installed HTC Sync, then uninstalled, so only drivers remained on my system.
I can use adb when the phone is normally booted, but then i don't have permission to write to that location.
When i reboot to recovery, adb devices shows empty list. Also that funny thing in windows taskbar starts spinning, finds "One", but fail to install driver.
Update1:
Ok, i managed to update adb driver to Android one. (http://forum.xda-developers.com/showthread.php?t=1830108 device manager section)
Now i'm at next step. I pushed zip to /data/media/, but after choosing install zip, there is none on sdcard.
Trying to push that again.
Update2:
File appeared after second push. Installing right now. Hope phone will wake after this procedure. Fingers crossed, holding breath.
Update3
Ok, i flashed RUU, everything is fine until now.
Slovak language / Slovakia as location is missing. Should / can i change my CID for something and install corresponding RUU for that CID, so i would have Slovak Language ? I also get red text saying "THIS IS TEST DEVICE...."
I think, the correct CID for my region is HTC_032 - East Europe
Click to expand...
Click to collapse
Been gone for a while, so what's your status now? How far did you get.
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