Related
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....
I was following Vomer's guide on my One, which has been working great. I had HBOOT 1.54, S-Off, SuperCID, and pushed the firmware twice, got the success message, and waited and when it says finished used adb to tell it to reboot. Now I get the splash, with the lock gone, as expected, and then the screen goes black. If I hold power, or power and down, the hardware keys start blinking and then nothing. A few seconds later I get the splash again, then blank again.
It appears to be communicating briefly over USB because my laptop starts trying to install a HTC MTP device (drive is already on the PC and has been fine) before it looses comms and drops out. I can't seem to get adb device to recognize it....
PLEASE tell me someone can help me recover my phone!!! I will be immensely grateful.
And what the HBOOT version you wanted to downgrade to?
Ivanovic said:
And what the HBOOT version you wanted to downgrade to?
Click to expand...
Click to collapse
I wasn't trying to downgrade HBOOT, just rather ensure my firmware was up to date. I'd had mine set up as a GPE and was flashing the DE (after supercid).
By way of an update, I've been able to get into bootloader and I'm a bit scared on what to do next so I dont screw this up. I notice that I still have S-OFF, but HBOOT is now showing 1.56 and it says RELOCKED at the top. My plan was to use rumrunner (just because of the HBOOT, but it is erroring anyway) to unlock bootloader, and then to look up the fastboot commands to push a ROM and recovery. Any advice?
Downgrade to 1.44 and change cid according to the Rom you want. Then unlock or set your bootloader to LOCKED
Here is the file for 1.44 http://www69.zippyshare.com/v/95229262/file.html
Sent from my HTC One using Tapatalk
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
vettejock99 said:
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
Click to expand...
Click to collapse
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Ivanovic said:
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Click to expand...
Click to collapse
Awesome. So I've got HBOOT 1.44, S-OFF, bootloader unlocked, supercid, and TWRP 2.6.3.3 flashed again, and I tried sideloading ARHD rom. It all looked good but same thing for the moment, I get the splash and then black......I can't figure out why I can't boot into a rom right now. About to try flashing ROM again.
Okay, so didnt' work. After sideload flashing gets to 100% it just does nothing. Manually rebooting gets me back into the splash then blackness bootloop......
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
The former didn't get me anywhere, but I did follow your thinking and decided to use the RUU and start over. I'm happy to report that got me going, and then I was able to get AR HD on. I probably had to do that all along once I wiped the ROM and recovery, as sideloading clearly wasn't going to work (in retrospect) as it has an AROMA installer.
Thanks so much everyone!!
SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
Nice that everything is solved now.
Verstuurd van mijn HTC One
Hi,
My goal was to revert my HTC One to stock, no tampered, no locked, etc. After hours of trying to find a solution to S-Off, I was finally successful with gaining S-Off, Removing the Tampered Flag, Re-locking, and returning to S-On.
I'm not entirely sure what happened next. I think I most have chosen "reboot" so that I could get back in and apply a new RUU.
Instead, my phone returned to bootloader, with a surprise reappearance of the "Tampered" flag, and a new one now, "Security Warning".
Attempts to reboot simply return me to bootloader. Attempts to access Recovery return me to bootloader. Attempts to power down work. And when I power on again it returns me to bootloader.
What. The. Hell. Happened.
Thanks in advance for any help.
Additional Details: Here are the steps I took to achieve each change:
S-Off - Rumrunner - Successful
Remove Tampered - Via this thread:
Code:
adb devices
adb shell
su
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
exit
adb reboot bootloader
Reset Lock Status -
Code:
./revone -l
(the directions I had stated "-L" but capital wasn't recognized, and lowercase worked.
Reset S-On -
Code:
fastboot oem writesecureflag 3
Looks like something screwed up. Once you are S-OFF, you do not need to lock the bootloader or S-ON to run RUU. It is (was) your get out of jail card.
Can you select factory reset from the bootloader menu? What is the result? If no go, then unlock bootloader, flash custom recovery, restore backup and/or flash custom rom, and restart the process.
Also what RUU were you trying to run, and why? Warranty related?
SaHiLzZ said:
Looks like something screwed up. Once you are S-OFF, you do not need to lock the bootloader or S-ON to run RUU. It is (was) your get out of jail card.
Can you select factory reset from the bootloader menu? What is the result? If no go, then unlock bootloader, flash custom recovery, restore backup and/or flash custom rom, and restart the process.
Also what RUU were you trying to run, and why? Warranty related?
Click to expand...
Click to collapse
Thanks for the reply. I was going to do T-mobile's trade-in program (every 6 months), but need the phone back to stock or they won't accept.
When I chose factory reset, it returned me to the bootloader.
My guess is it is freaking out because I relocked everything but still have a custom ROM.
Thanks for the advice, now time to hunt through the threads to figure out how to do all those things again. It has been a while, I've been unlocked for ages.
Your best bet will be to flash a ruu from tmobile based on 1.44hboot. As the new 1.55 hboot may not like being s-on.
So, in very short.
1. unlock bootloader,
2. flash custom recovery,
3. restore backup and/or flash custom rom (adb push/sideload/otg cable)
4. S-OFF
5. Run http://www.htc1guru.com/dld/ruu-zip...0-20-10-40-1150-04-release-324846-signed-zip/
6. Figure out how to lock bootloader.. using nkk71's guide
hi all
i was tried to flash my M7 from 4.3 to 4.4.2
downloaded the OTA update 4.19.401.7
contained :
DATA
META-INF
PATCH
System
Firmware.zip
Fotaboot
Skin_fota
the wrong step is : extracted the Firmware.zip file only
and flashed it only by :
fastboot oem rebootRUU
fastboot flash zip firmware.zip
now the phone is bricked, only boot to the HTC logo and black screen
when i try to press power bottom, the (Back & Home) led blinking
i was boot to bootloader and copy this information to you :
***LOCKED***
M7_UL PVT SHIP S-ON
HBOOT-1.56.0000 (it was 1.55 before)
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-4.19.401.9 (it was 3.62.401.1)
eMMC-boot 2048MB
Feb 7 2014,01:06:01.0
i was try to rename the OTA file to Firmware.zip and flash it again, but always failed
i was try to flash downgrade Firmware (3.62.401.1) also failed
i was try to flash RUU.exe (1.28.401.7) from the Fastboot screen and from the rebootRUU screen also failed
i was try to wipe and re-flash the same Firmware.zip file, it's flashed with no failed steps, but still bricked and no system to boot into
can you help me ?
My suggestion:
You are acting nervous, don´t know, from where you got the solutions you´ve tried. Your phone is not bricked if you have access to your bootloader as you wrote but yo can´t flash the needed things with a locked bootloader. Would be better to ask before every step, if you don´t know what to do.
1st you can send your device to HTC for repair...i think you have to pay for that
or 2nd (read and think about the warranty):
Unlock your bootloader via HTC.Dev. http://www.htcdev.com/devcenter
With locked bootloader it won´t run. If you have access to your bootloader, you are able to flash a recovery via Fastboot-USB and have access to adb. With S-On you can´t run the RUU you´ve tried, because you can´t downgrade your phone. S-Off would be the solution, but at the moment you can´t get it with your high HBoot version.
I think, the correct firmware is ready on your phone and you should
- unlock your bootloader with your Unlock_code.bin from HTC.Dev, flash it via Fastboot-USB fastboot flash unlocktoken Unlock_code.bin, accept the message on your phone, then
- flash TWRP 2.6.3.3 m7 recovery via fastboot, fastboot erase cache then fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
- sideload Maximus Rom or ARHD 52.0 via adb in recovery adb sideload HTC_One_-_MaximusHD_32.0.0.zip (if other rom, you have to replace the correct filename of the zip)
- or sideload the stock odexed rom 4.19.401.9 from the same download area at ARHD for the One
- check the MD5 sum before sideload! http://www.flashplayerpro.com/MD5Checksum/downloadMD5Checksum.htm
(even saw, the links of ARHD are down at the moment - the server problems of mike 1986 are not gone. Try it tomorrow or read the last sites of the thread to find alternative links),
- wipe data, system, dalvik cache and cache in recovery (not sd card)
- install the rom.zip via recovery, reboot into bootloader and
- flash the boot.img copied out of the rom via fastboot. fastboot erase cache then fastboot flash boot boot.img then fastboot erase cache
Then your device hopefully will boot again.
If the steps of flashing roms with TWRP are after reading this not really known, read the FAQ before.
If you are able to go to bootloader then give it a try. Unlock bootloader then try to flash firmware.
Sent from my HTC One using xda app-developers app
manishvy said:
If you are able to go to bootloader then give it a try. Unlock bootloader then try to flash firmware.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Correct me if i'm wrong but with S-ON you need the bootloader to be locked/re-locked to flash the firmware.zip
alray said:
Correct me if i'm wrong but with S-ON you need the bootloader to be locked/re-locked to flash the firmware.zip
Click to expand...
Click to collapse
Dont care about anything.. just goto HTC dev website, follow the steps and unlock the boot loader and flash the firmware..
alray said:
Correct me if i'm wrong but with S-ON you need the bootloader to be locked/re-locked to flash the firmware.zip
Click to expand...
Click to collapse
naresh_r said:
Dont care about anything.. just goto HTC dev website, follow the steps and unlock the boot loader and flash the firmware..
Click to expand...
Click to collapse
alray is correct mate! with S-On you need to have bootloader locked/relocked to be able to flash anything in ruu mode.
moha_moha20106 said:
hi all
i was tried to flash my M7 from 4.3 to 4.4.2
downloaded the OTA update 4.19.401.7
can you help me ?
Click to expand...
Click to collapse
OP, didn't we agree that you were going to wait??
I'm not entirely sure if stock recovery will read an OTG cable + stick, but worth a try:
if you haven't unlocked yet, get yourself an OTG cable + stick, put the OTA.ZIP (yes all of it, not just firmware), on the stick. connect it to your phone, and reboot into stock recovery, then press POWER + VOLUP (and hope it sees the otg), and use the "apply from sdcard" option to install the OTA.
Neo XL said:
My suggestion:
You are acting nervous, don´t know, from where you got the solutions you´ve tried. Your phone is not bricked if you have access to your bootloader as you wrote but yo can´t flash the needed things with a locked bootloader. Would be better to ask before every step, if you don´t know what to do.
1st you can send your device to HTC for repair...i think you have to pay for that
or 2nd (read and think about the warranty):
Unlock your bootloader via HTC.Dev. http://www.htcdev.com/devcenter
With locked bootloader it won´t run. If you have access to your bootloader, you are able to flash a recovery via Fastboot-USB and have access to adb. With S-On you can´t run the RUU you´ve tried, because you can´t downgrade your phone. S-Off would be the solution, but at the moment you can´t get it with your high HBoot version.
I think, the correct firmware is ready on your phone and you should
- unlock your bootloader with your Unlock_code.bin from HTC.Dev, flash it via Fastboot-USB fastboot flash unlocktoken Unlock_code.bin, accept the message on your phone, then
- flash TWRP 2.6.3.3 m7 recovery via fastboot, fastboot erase cache then fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
- sideload Maximus Rom or ARHD 52.0 via adb in recovery adb sideload HTC_One_-_MaximusHD_32.0.0.zip (if other rom, you have to replace the correct filename of the zip)
- or sideload the stock odexed rom 4.19.401.9 from the same download area at ARHD for the One
- check the MD5 sum before sideload! http://www.flashplayerpro.com/MD5Checksum/downloadMD5Checksum.htm
(even saw, the links of ARHD are down at the moment - the server problems of mike 1986 are not gone. Try it tomorrow or read the last sites of the thread to find alternative links),
- wipe data, system, dalvik cache and cache in recovery (not sd card)
- install the rom.zip via recovery, reboot into bootloader and
- flash the boot.img copied out of the rom via fastboot. fastboot erase cache then fastboot flash boot boot.img then fastboot erase cache
Then your device hopefully will boot again.
If the steps of flashing roms with TWRP are after reading this not really known, read the FAQ before.
Click to expand...
Click to collapse
Dear , i will send my phone to the HTC Maintenance center and ask them to resolve it with my warranty
if i UNLOCK my phone and S-OFF , i think i will loose my 9months warranty
if they told my the problem is by you (me), i will ask them to maintain it and pay money
thank you very much
nkk71 said:
alray is correct mate! with S-On you need to have bootloader locked/relocked to be able to flash anything in ruu mode.
OP, didn't we agree that you were going to wait??
I'm not entirely sure if stock recovery will read an OTG cable + stick, but worth a try:
if you haven't unlocked yet, get yourself an OTG cable + stick, put the OTA.ZIP (yes all of it, not just firmware), on the stick. connect it to your phone, and reboot into stock recovery, then press POWER + VOLUP (and hope it sees the otg), and use the "apply from sdcard" option to install the OTA.
Click to expand...
Click to collapse
Dear, i'm sorry for that
yes, we agreed before for waiting...
but the HTC MEA always lier
i was try to connect the OTG cable, but the bootloader didn't read it, i think the OTG function is by system, not by bootloader
thank you very much dear
Hi, i know i'm an idiot. someone please help me
i have an htc one (m7)
unlocked bootloader (wroked fine)
tried rooting (worked fine)
installed custom recovery
tried flashing a custom rom, my nephew pressed the power button and the computer shut down.
now i have an expensive brick to play with.
have been looking for an ruu file to flash via hassoon's toolkit but i have found nothing but broken files.
CID: HTC001
modelid: pn0710000
Bootloader: relocked
S-on
No recovery installed. (error comes up when trying to flash a new one via fastboot cmd)
Please help! :good:
darrylu8 said:
Hi, i know i'm an idiot. someone please help me
i have an htc one (m7)
unlocked bootloader (wroked fine)
tried rooting (worked fine)
installed custom recovery
tried flashing a custom rom, my nephew pressed the power button and the computer shut down.
now i have an expensive brick to play with.
have been looking for an ruu file to flash via hassoon's toolkit but i have found nothing but broken files.
CID: HTC001
modelid: pn0710000
Bootloader: relocked
S-on
No recovery installed. (error comes up when trying to flash a new one via fastboot cmd)
Please help! :good:
Click to expand...
Click to collapse
The PC has nothing to do with flashing a rom ... what really happened
clsA said:
The PC has nothing to do with flashing a rom ... what really happened
Click to expand...
Click to collapse
it was while i tried to flash via the toolkit. was an error message came up, (can't remember what it said)
i just need to find a way to get s-off while my phone has nothing on it. theres no recovery (option is there though!)
i have bootloader/fastboot access. read somewhere that i have to relock the bootloader to flash an ruu. but others say i need s-off and the bootloader doesn't matter. its getting quite frustrating lol
darrylu8 said:
it was while i tried to flash via the toolkit. was an error message came up, (can't remember what it said)
i just need to find a way to get s-off while my phone has nothing on it. theres no recovery (option is there though!)
i have bootloader/fastboot access. read somewhere that i have to relock the bootloader to flash an ruu. but others say i need s-off and the bootloader doesn't matter. its getting quite frustrating lol
Click to expand...
Click to collapse
Yeah calm down ...
ditch the toolkit and just install fastboot/adb
use the zip below to make a fastboot folder in c:\
we'll be working from their
I'll post the steps you need to get your phone up and running
clsA said:
Yeah calm down ...
ditch the toolkit and just install fastboot/adb
use the zip below to make a fastboot folder in c:\
we'll be working from their
I'll post the steps you need to get your phone up and running
Click to expand...
Click to collapse
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot