Related
Hi,
Now that I have S-Off on hboot 1.54, Im seeing the red text on bootup, is this due to being S-Off ? If I go S-On, will it remove the text ?
I ask because I need to send the phone back to htc so need to get back to stock.
also, Is this the command to go S-ON ?
fastboot oem writesecureflag 3
Now that you're s-off, you've to flash a custom hboot form Sneaky thread
After you won't see the text
Guich said:
Now that you're s-off, you've to flash a custom hboot form Sneaky thread
After you won't see the text
Click to expand...
Click to collapse
If I send the phone back to HTC with this custom hboot, will that cause any warranty issues ?
akuma24 said:
If I send the phone back to HTC with this custom hboot, will that cause any warranty issues ?
Click to expand...
Click to collapse
If you will send to htc for warranty, you can reflash an original hboot/firmware and rom
Guich said:
If you will send to htc for warranty, you can reflash an original hboot/firmware and rom
Click to expand...
Click to collapse
ok, just so that Im clear,
I flash a custom hboot to get rid of the red text.
restore my nandroid backup,
remove TAMPERED message,
lock the bootloader
flash stock hboot
restore recovery,
set security on, or leave it off
???
akuma24 said:
ok, just so that Im clear,
I flash a custom hboot to get rid of the red text.
restore my nandroid backup,
remove TAMPERED message,
lock the bootloader
flash stock hboot
restore recovery,
set security on, or leave it off
???
Click to expand...
Click to collapse
DO NOT GO S-ON with custom hboot, that will most likely brick your phone.
Anyway, plenty of people have sent their phone back with S-Off and received back with S-Off. As long as you are LOCKED (not RELOCKED), not TAMPERED, etc. they can't complain abut S-off, because some devices are actually shipped S-Off.
If you do prefer to go S-On again before sending it, make sure you have done all the steps to remove any sign of unlocking your phone. S-On should be THE VERY LAST STEP, once you are satisfied everything is back to stock and no warning messages.
nkk71 said:
DO NOT GO S-ON with custom hboot, that will most likely brick your phone.
Anyway, plenty of people have sent their phone back with S-Off and received back with S-Off. As long as you are LOCKED (not RELOCKED), not TAMPERED, etc. they can't complain abut S-off, because some devices are actually shipped S-Off.
If you do prefer to go S-On again before sending it, make sure you have done all the steps to remove any sign of unlocking your phone. S-On should be THE VERY LAST STEP, once you are satisfied everything is back to stock and no warning messages.
Click to expand...
Click to collapse
any idea if simply going back to s-on while remove the text without changing the hboot etc
akuma24 said:
any idea if simply going back to s-on while remove the text without changing the hboot etc
Click to expand...
Click to collapse
The S-On/S-Off flag should not have anything to do with the red text (99.9% sure). In theory, having stock ROM and stock RECOVERY, and maybe relocked bootloader should remove the TAMPERED and red warning text.
However it seems that for some this does work, and for others it doesn't. I've personally even unlocked an HTC One (using HTCdev cause S-On), installed custom recovery, custom ROM, and even though it showed TAMPERED, it did NOT show the red warning text.
Still trying to figure out what combination would make it go away. Maybe, I'll mess with that over the weekend and see if I can find something.
nkk71 said:
The S-On/S-Off flag should not have anything to do with the red text (99.9% sure). In theory, having stock ROM and stock RECOVERY, and maybe relocked bootloader should remove the TAMPERED and red warning text.
However it seems that for some this does work, and for others it doesn't. I've personally even unlocked an HTC One (using HTCdev cause S-On), installed custom recovery, custom ROM, and even though it showed TAMPERED, it did NOT show the red warning text.
Still trying to figure out what combination would make it go away. Maybe, I'll mess with that over the weekend and see if I can find something.
Click to expand...
Click to collapse
I have stock rom on at the moment but custom recovery, will try and restore the recovery and see if that does the trick.
The tampered flag I have removed by:
./adb devices
./adb shell
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
exit
./adb reboot bootloader
Got the courage to try
fastboot oem writesecureflag 3
and can CONFIRM the red text has now gone, phew, no need to mess around with custom hboots
akuma24 said:
I have stock rom on at the moment but custom recovery, will try and restore the recovery and see if that does the trick.
The tampered flag I have removed by:
./adb devices
./adb shell
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
exit
./adb reboot bootloader
Click to expand...
Click to collapse
akuma24 said:
Got the courage to try
fastboot oem writesecureflag 3
and can CONFIRM the red text has now gone, phew, no need to mess around with custom hboots
Click to expand...
Click to collapse
thank you both
skinniezinho said:
thank you both
Click to expand...
Click to collapse
so just to confirm, in order for the red text warning to go away you did:
1- stock rom
2- stock recovery
3- lock bootloader
4- s-on (whas that necessary? did the above three steps not remove the red warning)
Thanks for reporting back.
nkk71 said:
so just to confirm, in order for the red text warning to go away you did:
1- stock rom
2- stock recovery
3- lock bootloader
4- s-on (whas that necessary? did the above three steps not remove the red warning)
Thanks for reporting back.
Click to expand...
Click to collapse
No, I already had stock rom (needed for rumrunner)
I tried to restore the recovery which said it was successful but I still had CWM instead of stock recovery
Al i did was go back to S-ON
My current setup is stock rom, cwm, unlocked bootloader and s-on and the red text has disappeared.
It seems S-OFF is what triggers the message.
looks like the TAMPERED message is back seeing the bootloader is still unlocked
Any Ideas how to verify I have stock recover ?
Tried the following and can no longer get to CWM, instead it just says Entering Recovery and reboots and boots up normally, is that right ?
./fastboot flash recovery recovery.img
sending 'recovery' (16383 KB)...
OKAY [ 2.155s]
writing 'recovery'...
OKAY [ 1.021s]
finished. total time: 3.176s
akuma24 said:
looks like the TAMPERED message is back seeing the bootloader is still unlocked
Any Ideas how to verify I have stock recover ?
Tried the following and can no longer get to CWM, instead it just says Entering Recovery and reboots and boots up normally, is that right ?
./fastboot flash recovery recovery.img
sending 'recovery' (16383 KB)...
OKAY [ 2.155s]
writing 'recovery'...
OKAY [ 1.021s]
finished. total time: 3.176s
Click to expand...
Click to collapse
Do a "fastboot erase cache", then you'll be able to get back to recovery.
Screenshots of "stock recovery" attached
Thanks, now to remove root :laugh:
Then I think I am fully back to stock. Ring Ring.......Welcome to HTC Customer Services.......
nkk71 said:
so just to confirm, in order for the red text warning to go away you did:
1- stock rom
2- stock recovery
3- lock bootloader
4- s-on (whas that necessary? did the above three steps not remove the red warning)
Thanks for reporting back.
Click to expand...
Click to collapse
nothing of that.just the steps.
I was on CWM Touch, Insertcoin 5.0 and unlocked bootloader S-OFF
akuma24 said:
Thanks, now to remove root :laugh:
Then I think I am fully back to stock. Ring Ring.......Welcome to HTC Customer Services.......
Click to expand...
Click to collapse
You need to remove root before removing the custom recovery, relocking the bootloader, etc...
Can you check if you see any red text in Settings > About > Tell HTC and error reporting? I think this happened with S-OFF.
Sorry for the hijack, but I just saw your firmware @electronical, being 2.24.401.9... would you happen to have the OTA file for that, or the signed firmware package? Otherwise maybe the nonsigned? Thanks
Hi All,
I have merely followed the instructions of other devs here to get my phone back to complete stock O2. I believe this guide could work for other carrier based models as well
Mods - Feel free to post this wherever or make any changes.
These are the steps I took to get back to S-ON, reset the ***TAMPERED*** flag and lock the bootloader. The reason why I post this is because I had several issues getting back to stock, and this is for anyone who is having the same issues
I had several scary messages when going back to S-ON when I thought I was completely stock, which included the "Security Warning" message in bootloader when running fastboot oem writesecureflag 3. I also had a message when booting up the stock ROM in 3.62.206.1 saying "TAMPER DETECTED - REBOOTING after trying fastboot oem writesecureflag 3. Once in bootloader, the tampered message re-appeared and I was S-ON and LOCKED. After running all the steps, I have been able to reboot several times and factory reset without the ***TAMPERED*** reappearing
Step 1: Getting S-off
If you are using bootloader 1.44 - Use Revone http://forum.xda-developers.com/showthread.php?t=2314582
For bootloaders 1.5x you should download the Sunshine app at http://theroot.ninja/
The closer you are to stock ROM/stock kernel the better. To S-off it will cost you a mere $25, but it works in 5 mins and no need for computers/adb commands
Step 2: Remove ***TAMPERED***
After getting S-OFF, reset the ***TAMPERED*** flag and lock the bootloader using the following commands from these posts http://forum.xda-developers.com/showthread.php?p=46183050#post46183050 and http://forum.xda-developers.com/showthread.php?t=2477792 (credit to scotty1223)
To LOCK the Bootloader
To LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Click to expand...
Click to collapse
To reset the TAMPER in bootloader
Enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Click to expand...
Click to collapse
Step 3: Downgrade your Hboot to 1.44
Download the Hboot 1.44 from http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
Before flashing, The android-info.txt file needs modified by clicking into the file (not extracting it) and changing the model ID to whatever your model is. This can be checked by running the command fastboot getvar all and checking the model ID number
Now flash the Hboot. To do this, boot to bootloader screen using the command adb reboot-bootloader
Type the following commands:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
After it finishes, execute the command again to complete the flash:
fastboot flash zip 1.29.401.12_hboot_1.44.zip
Fastboot reboot
Step 4: Run an earlier RUU from 1.29.xxx.xx
We need to run and earlier RUU first. For now, change CID to HTC__032
Download RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed from thanks to crushalot, http://d-h.st/Gt8. This will reset the phone back to complete stock, but not stock for the original CID O2___001. Once the RUU installs, reboot into bootloader and run the following command
fastboot oem writecid O2___001.
Check your bootloader and you should see the phone is still S-OFF and the CID is now for O2.
Step 5: Getting S-OFF again
This is if for some reason the phone has gone back to S-ON. To be honest, I did this step anyways just to be safe. Download, push and flash revone using the commands on the toolkit and ensure that the phone is not ***TAMPERED***
Using Revone, Unlock the bootloader - adb reboot bootloader to check it is unlocked
Step 6: Restoring an earlier backup
Download M7 CWM Nandroid Backup CID O2__102 1.27.206.1 2013-03-30 from crushalot's page on XDA and extract the file to the PC until you have a folder with a date on it and time (2013-03-11.17.58.27)
Make a new folder in your HTC one called clockworkmod. Inside here place a new folder called backup (all lower case). Place the backup here
Also, download http://forum.xda-developers.com/showthread.php?t=2200628 and place onto your SD Card. Once you flash the nandroid backup, go ahead and flash this. It will fix the missing preload apps (calculator, flashlight etc) which happens when unlocking the bootloader, and if these apps are missing can cause future OTA's to fail
Download CWM recovery and rename to CWMTG.img and place in your adb folder. You can also download Hassoon's Toolkit and copy the recovery from there if you like. At this point, ensure your bootloader is UNLOCKED.
From the fasboot menu, type the following
Fastboot boot CWMTG.img
This will boot into the recovery without installing it. Restore the nandroid backup you downloaded earlier and install the preload fix. Reboot
Step 7: Restoring stock recovery, Locking the Bootloader and install updates via OTA
Download the stock recovery for O2 from here http://d-h.st/l1q and flash via fastboot
Once booted up, lock the bootloader using Revone and remove tampered (run the command anyway even if it doesn't say ***TAMPERED***. Check for OTA - The one I got was for 2.24.206.1
Step 8: Returning to S-ON
Verify that the bootloader is LOCKED, not ***TAMPERED*** and hboot is 1.54 with the OS confirming your firmware
Type the command: Fastboot oem writesecureflag 3
Enjoy complete stock and continue with the OTA's
If I helped in any way just click thanks!
Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already
dispereo said:
Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already
Click to expand...
Click to collapse
Don't know why the links don't post correctly - 13: http://forum.xda-developers.com/showthread.php?t=2200628
dispereo said:
Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already
Click to expand...
Click to collapse
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?
stovie_steve said:
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?
Click to expand...
Click to collapse
Also the red error message is because you are booting into a custom recovery and this is normal. It would also say entering recovery at the top of the screen. Are you using the CWMTG.img from hasoon's toolkit in your fastboot/adb folder?
stovie_steve said:
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?
Click to expand...
Click to collapse
I've been repeating it over and over again (rough guess, about 15x) and it doesn't work. Still the map memory error.
I put the recovery-clockwork-6.0.4.3-m7ul.img (and I tried 2 others on their website) in the c:\android (where my adb/fastboot exe are in)
My bootloader says "unlocked" (however I manually unlocked again, just in case) - no change.
I entered fastboot boot recovery-clockwork-6.0.4.3-m7ul.img and then it just reboots (assuming it crashes and has the failsafe reboot)
---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------
stovie_steve said:
Also the red error message is because you are booting into a custom recovery and this is normal. It would also say entering recovery at the top of the screen. Are you using the CWMTG.img from hasoon's toolkit in your fastboot/adb folder?
Click to expand...
Click to collapse
No I downloaded it manually. Because you say "fastboot boot" it won't flash it. But Hasoon's tool says "flash recovery" which sounds to me like overwriting (flashing) the current original, that would be thing i don't want. So i am a bit confused there.
dispereo said:
I've been repeating it over and over again (rough guess, about 15x) and it doesn't work. Still the map memory error.
I put the recovery-clockwork-6.0.4.3-m7ul.img (and I tried 2 others on their website) in the c:\android (where my adb/fastboot exe are in)
My bootloader says "unlocked" (however I manually unlocked again, just in case) - no change.
I entered fastboot boot recovery-clockwork-6.0.4.3-m7ul.img and then it just reboots (assuming it crashes and has the failsafe reboot)
---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------
No I downloaded it manually. Because you say "fastboot boot" it won't flash it. But Hasoon's tool says "flash recovery" which sounds to me like overwriting (flashing) the current original, that would be thing i don't want. So i am a bit confused there.
Click to expand...
Click to collapse
What I did was pull the recovery image from hasoon's toolkit, not download the recovery image from the website. If you download the toolkit and go to the directory where you downloaded it there is a folder called recoveries where I copied the image to my adb folder. I did NOT use the toolkit as this involved flashing it so please try it that way instead of downloading it from the website
As for manually unlocking again - how to you do this without revone working? And put of curiosity are you using the toolkit to push/flash revone? If so I would reboot the phone between every step and try it again
Try that and see
stovie_steve said:
What I did was pull the recovery image from hasoon's toolkit, not download the recovery image from the website. If you download the toolkit and go to the directory where you downloaded it there is a folder called recoveries where I copied the image to my adb folder. I did NOT use the toolkit as this involved flashing it so please try it that way instead of downloading it from the website
As for manually unlocking again - how to you do this without revone working? And put of curiosity are you using the toolkit to push/flash revone? If so I would reboot the phone between every step and try it again
Try that and see
Click to expand...
Click to collapse
I got to 17 now (had to adjust minor things to get that work, thanks for your help!) and the problem is, my phone obviously doesn't support revone anymore as it doesn't have the permissions. Can I lock manually (with the HTC Dev command?) and I haven't had a ****TAMPERED**** since I installed the RUU.zip, do I still need to do 17. remove the tampered flag ? If so, how to do that with revone not having the permissions?
Almost there... almost there... *nervous*
So, I updated, I couldn't wait for a reply.
Now I've got "relocked" in the hboot, which is the way HTC Dev intended it (as far as I understand). Is there a way to get rid of that afterwards?
dispereo said:
So, I updated, I couldn't wait for a reply.
Now I've got "relocked" in the hboot, which is the way HTC Dev intended it (as far as I understand). Is there a way to get rid of that afterwards?
Click to expand...
Click to collapse
you should set it to LOCKED (not relocked), using either revone or http://forum.xda-developers.com/showthread.php?t=2475914 (or any of the other method available)
Thanks! Will have a look into that. So my phone updated without an issue now, and I am on Android 4.3 actually which made me wonder... if I ever do have to do a factory reset, what's the phone being reset to? Do you know that by chance?
dispereo said:
Thanks! Will have a look into that. So my phone updated without an issue now, and I am on Android 4.3 actually which made me wonder... if I ever do have to do a factory reset, what's the phone being reset to? Do you know that by chance?
Click to expand...
Click to collapse
Factory reset will just wipe everything (rephrase DATA) off your phone, it will not change ROM, firmware or anything like that, so it will remain on 4.3
nkk71 said:
Factory reset will just wipe everything (rephrase DATA) off your phone, it will not change ROM, firmware or anything like that, so it will remain on 4.3
Click to expand...
Click to collapse
Awesome, thanks for that. Phew. So now I am just stuck on a "re-locked" bootloader because rumrunner can't seem to find a way to get S-OFF again, as hboot 1.55 was installed. So i prolly got to wait until someone found a way to do that.
Thanks A LOT (!!!) for your help!
dispereo said:
Awesome, thanks for that. Phew. So now I am just stuck on a "re-locked" bootloader because rumrunner can't seem to find a way to get S-OFF again. So i prolly got to wait until someone found a way to do that.
Thanks A LOT (!!!) for your help!
Click to expand...
Click to collapse
No problem
As for rumrunner it should work on 4.3 (ie base 3.62.xxx.x), if it's currently not, the guys are updating it quite frequently, but if I recall correctly, it's best to have unlocked bootloader and ROOT.
Cheers
nkk71 said:
No problem
As for rumrunner it should work on 4.3 (ie base 3.62.xxx.x), if it's currently not, the guys are updating it quite frequently, but if I recall correctly, it's best to have unlocked bootloader and ROOT.
Cheers
Click to expand...
Click to collapse
I found a major issue here... when you boot it up and are in the setup screen, it says in red:
This is a test device. Tell HTC is automatically enabled so that HTC can collect critical information about the device during testing. It is not possible to turn this feature off on this phone.
Where did that come from? That sucks...
dispereo said:
I found a major issue here... when you boot it up and are in the setup screen, it says in red:
This is a test device. Tell HTC is automatically enabled so that HTC can collect critical information about the device during testing. It is not possible to turn this feature off on this phone.
Where did that come from? That sucks...
Click to expand...
Click to collapse
That usually comes if you have S-Off, I though you said you went back S-On
nkk71 said:
That usually comes if you have S-Off, I though you said you went back S-On
Click to expand...
Click to collapse
I did! Weird... I am repeating the procedure again.
---------- Post added at 07:32 PM ---------- Previous post was at 07:09 PM ----------
dispereo said:
I did! Weird... I am repeating the procedure again.
Click to expand...
Click to collapse
The bootloader is definitely unlocked as I just did it manually again with the HTC Dev unlock_token.bin.
The locking procedure from the website you posted:
C:\Android>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1
seek=33796
dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
/dev/block/mmcblk0p3: cannot open for write: Permission denied
1|[email protected]:/ $
Rumrunner:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (28/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (27/120)
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
Press ENTER to exit
---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------
dispereo said:
I did! Weird... I am repeating the procedure again.
---------- Post added at 07:32 PM ---------- Previous post was at 07:09 PM ----------
The bootloader is definitely unlocked as I just did it manually again with the HTC Dev unlock_token.bin.
The locking procedure from the website you posted:
C:\Android>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1
seek=33796
dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
/dev/block/mmcblk0p3: cannot open for write: Permission denied
1|[email protected]:/ $
Rumrunner:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (28/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (27/120)
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
Press ENTER to exit
Click to expand...
Click to collapse
And someone had the same question here:
http://forum.xda-developers.com/showthread.php?t=2470957
Apparently with 1.55 it's not possible to get S-OFF (even though I didn't go S-ON at any stage, at least not myself...)
dispereo said:
Apparently with 1.55 it's not possible to get S-OFF (even though I didn't go S-ON at any stage, at least not myself...)
Click to expand...
Click to collapse
I'm 100% sure that before rumrunner was changed to a universal toolkit, there were quite a few packages for base 3.xx (hboot 1.55) including 3.62.401.x and they worked.
But like your output said:
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
Click to expand...
Click to collapse
you would need to flash a ROM with ROOT (maybe a Guru Reset) compatible with your firmware for it to work. (obviously you need to be unlocked to flash ROM)
Also, going from S-Off to S-On on hboot 1.55 will result in "tamper detected - rebooting" and showing TAMPERED again, so you'll need to do that before hboot 1.55 (at least I'm well over 50% sure of that by now).
If the universal rumrunner tool really does not work for you at this time, I'm sure they're fixing it and it will be along soon.
EDIT: fastboot oem writesecureflag 3 is what makes you go S-On, and you have to do it, no way it's done by itself
nkk71 said:
I'm 100% sure that before rumrunner was changed to a universal toolkit, there were quite a few packages for base 3.xx (hboot 1.55) including 3.62.401.x and they worked.
But like your output said:
you would need to flash a ROM with ROOT (maybe a Guru Reset) compatible with your firmware for it to work. (obviously you need to be unlocked to flash ROM)
Also, going from S-Off to S-On on hboot 1.55 will result in "tamper detected - rebooting" and showing TAMPERED again, so you'll need to do that before hboot 1.55 (at least I'm well over 50% sure of that by now).
If the universal rumrunner tool really does not work for you at this time, I'm sure they're fixing it and it will be along soon.
EDIT: fastboot oem writesecureflag 3 is what makes you go S-On, and you have to do it, no way it's done by itself
Click to expand...
Click to collapse
I might have done that, even though I thought I left that out. However, my bootloader says ***** relocked ***** , that's all. It doesn't say ***** tampered ***** (that definitely disappeared after putting the ruu.zip on, I didn't have to do anything. i was wondering about that because you specifially mention it in your walkthrough but for me it disappeared automatically right at the start of the procedure.)
dispereo said:
I might have done that, even though I thought I left that out.
Click to expand...
Click to collapse
No way to go S-On without doing it yourself, no big deal, as long as you can unlock again.
dispereo said:
It doesn't say ***** tampered ***** (that definitely disappeared after putting the ruu.zip on
Click to expand...
Click to collapse
In theory, as long as you have stock ROM and stock recovery, the tampered should not show up, even if unlocked (S-On or S-Off), however for some, it did stay, even under those conditions. no real idea why. repeating myself: tampered should go away as soon as you have stock recovery.
dispereo said:
i was wondering about that because you specifially mention it in your walkthrough
Click to expand...
Click to collapse
Not my guide, it's @stovie_steve guide. I'm just visiting :cyclops:
So if you want to start over again, you need to get unlocked, flash a ROM compatible with your current firmware, which has root, and use rumrunner to get s-off.
I'm off for tonight see you guys around....
Hey,
i'm about to set my One completely back to stock. My major problem at the moment is tah i already locked my Bootloader, but i have not installed a custom recovery, but i'm in need of one. So now I need to unlock the Bootloader again. But I dont know how to do ist without Root or a custom recovery... I thought about using HTCDev, but I just thougt that i shoulg not use it while my one is s-offed.
So please guys, help me !
wiiplayer94 said:
Hey,
i'm about to set my One completely back to stock. My major problem at the moment is tah i already locked my Bootloader, but i have not installed a custom recovery, but i'm in need of one. So now I need to unlock the Bootloader again. But I dont know how to do ist without Root or a custom recovery... I thought about using HTCDev, but I just thougt that i shoulg not use it while my one is s-offed.
So please guys, help me !
Click to expand...
Click to collapse
May be this will help you:
http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
wiiplayer94 said:
Hey,
i'm about to set my One completely back to stock. My major problem at the moment is tah i already locked my Bootloader, but i have not installed a custom recovery, but i'm in need of one. So now I need to unlock the Bootloader again. But I dont know how to do ist without Root or a custom recovery... I thought about using HTCDev, but I just thougt that i shoulg not use it while my one is s-offed.
So please guys, help me !
Click to expand...
Click to collapse
next time post a "fastboot getvar all" (excluding IMEI and s/n), so you don't start flashing things NOT for your phone.
that being said, if you don't want to use HTCdev, then you can flash a custom recovery (masked in a firmware package), in ruu mode.
if you have an m7_u / ul model:
To unlock again
since you can't use "fastboot flash recovery <name of recovery>.img" with a locked bootloader, you'll need to either use HTCdev or flash the recovery in RUU mode (only possible with S-Off):
fw_TWRP_2.6.3.3_1.26.401.3.zip 8.9 MB
https://mega.co.nz/#!6VcSlICK!lWPl1wgrah43yxom7mLkpPHi71kAXoSk-BdNpaTcxNc
MD5: BF37A63802EB37B37689DE08D133484F
fastboot oem rebootRUU
fastboot flash zip fw_TWRP_2.6.3.3_1.26.401.3.zip
fastboot flash zip fw_TWRP_2.6.3.3_1.26.401.3.zip <- it should go through just fine the first time, but just in case
fastboot reboot-bootloader
fastboot erase cache
-> enter RECOVERY (it'll be TWRP 2.6.3.3)
to unlock again, you use:
adb shell
~ # echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
in custom recovery
credits to @scotty1223 for http://forum.xda-developers.com/showthread.php?t=2475914
Trying to return my one back to stock (unlocked, s-off) to send in for purple tint repair.
I tried a few different methods involving the RUUs but never had any luck:
1. The RUU.exe for my specific phone (telus), always crashed when htc_fastboot.exe stopped responding.
2. Since there was no RUU.zip for the Telus version I extracted it out of the exe and tried flashing manually, but again fastboot stops responding.
3. Tried changing the CID to CWS__001 and using the matching RUU.exe, and while fastboot didn't crash it wasn't able to complete either (can't remember the exact error).
So I decided to use the Telus Guru Reset from htc1guru, which worked fine.
Now I need to get rid of the tampered flag and lock bootloader/s-on, but I can't boot a custom recovery with fastboot boot recovery.img.
I need to boot into recovery to either use the guru bootloader reset tool or to temporarily install superuser, so that I can manually remove the tampered flag.
Tried the latest version of both TWRP and CWM Touch, and also tried fastboot erase cache before each.
Every time fastboot succesfully pushes the img to the phone and outputs booting..., OKAY, and finished, but the phone gets stuck at the bootloader and never actually boots to the recovery (have to force power off).
Any ideas/help would be greatly appreciated.
xerockz said:
Trying to return my one back to stock (unlocked, s-off) to send in for purple tint repair.
I tried a few different methods involving the RUUs but never had any luck:
1. The RUU.exe for my specific phone (telus), always crashed when htc_fastboot.exe stopped responding.
2. Since there was no RUU.zip for the Telus version I extracted it out of the exe and tried flashing manually, but again fastboot stops responding.
3. Tried changing the CID to CWS__001 and using the matching RUU.exe, and while fastboot didn't crash it wasn't able to complete either (can't remember the exact error).
So I decided to use the Telus Guru Reset from htc1guru, which worked fine.
Now I need to get rid of the tampered flag and lock bootloader/s-on, but I can't boot a custom recovery with fastboot boot recovery.img.
I need to boot into recovery to either use the guru bootloader reset tool or to temporarily install superuser, so that I can manually remove the tampered flag.
Tried the latest version of both TWRP and CWM Touch, and also tried fastboot erase cache before each.
Every time fastboot succesfully pushes the img to the phone and outputs booting..., OKAY, and finished, but the phone gets stuck at the bootloader and never actually boots to the recovery (have to force power off).
Any ideas/help would be greatly appreciated.
Click to expand...
Click to collapse
boot recover has not worked sense hboot 1.44
clsA said:
boot recover has not worked sense hboot 1.44
Click to expand...
Click to collapse
I guess that explains the problem as I am on 1.57. Just re-flashed that guru reset, and checked the option to install superuser and busybox this time so now I should be able to fix the tampered flag and lock, without having to worry about booting to a custom recovery.
Okay so I got it locked and tampered removed, however I cannot remove Superuser.apk, the su binary, or busybox now that my bootloader is locked (using adb shell, su, rm -r /system/app/Superuser.apk). Tried factory reseting and the files are still there, not sure how I can get rid of them!
edit: I've found this old post, not sure if it's still relevant, or exactly what it's doing.
xerockz said:
Okay so I got it locked and tampered removed, however I cannot remove Superuser.apk, the su binary, or busybox now that my bootloader is locked (using adb shell, su, rm -r /system/app/Superuser.apk). Tried factory reseting and the files are still there, not sure how I can get rid of them!
edit: I've found this old post, not sure if it's still relevant, or exactly what it's doing.
Click to expand...
Click to collapse
Why not just run the Guru Reset again and select stock recovery and no root.
@xerockz try to install SuperSU app from Play Store. Open it and let update the binaries (normal!) and if successfull, you will after reboot get able to unroot for good in the app.
tetakpatalked from N7100
Hey guys, thanks for the suggestions. I ended up getting it all back to stock.
I believe the reason the RUUs weren't working was because I was on hboot 1.57.
I flashed 1.44 and then was unable to get fastboot to recognize the device under windows 8.1 (common driver issue apparently). I couldn't be bothered to try to fix the driver issue so I booted into a live Fedora usb which then let me use fastboot and flash the appropriate ruu.zip.
Now the ruu had hboot 1.55 so I was once again unable to fastboot boot recovery.img.
I ended up flashing TWRP again, trying the guru bootloader reset over and over, (for tampered and lock) wiped cache/dalvik, still wouldn't work.
Finally got it to work after fastboot format cache.
Now I was locked and no tampered flag, but still had TWRP flashed.
Tried pulling the signed_recovery.img out of the RUU zip and flashing it but obviously that doesn't work since I was locked at this point.
So I just flashed the entire RUU again, which fortunately worked even though I was locked.
Now I just had to S-ON, update OTA, and factory reset (through sense settings) and I'm completely back to stock.
14 hours of headache later and I finally got this thing reset.
It's unfortunate the return to stock guides fail to mention the RUUs don't work if you are on a newer hboot, and also that you need/can flash the RUU AFTER fixing tampered/locking.
xerockz said:
It's unfortunate the return to stock guides fail to mention the RUUs don't work if you are on a newer hboot, and also that you need/can flash the RUU AFTER fixing tampered/locking.
Click to expand...
Click to collapse
beg to differ [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
but glad you got everything sorted out :good: :good:
Hi, I am trying to get back to complete stock. With locked recovery and bootloader.
Im on HBOOT-1.55.0000
how would i go about factory resetting.
Could i just press factory reset in the bootloader menu?
No. I'm assuming you're boot loader unlocked but not S-Off.
There is a thread about this in Android development. But I'll give you a general outline.
You will do the following in fastboot:
First, you need to lock your boot loader. Then, go into ruu mode. Flash the firmware.zip. Reboot.
You should be good to go. However, it will say "relocked" not "locked" on your boot loader.