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....
Hey I tried installing a 4.4 rom, got a boot loop recovery keeps crashing and I can get into fastboot now.
The computer is recognizing the phone and I can use fastboot to flash a new recovery but CWM and TWRP recoveries continue to crash on reboot... What can I do?
S-On or s-off ?
either way your best bet is an RUU. the GPE RUU if your s-off or the proper carrier/region RUU if your s-on.
mopardroid said:
Hey I tried installing a 4.4 rom, got a boot loop recovery keeps crashing and I can get into fastboot now.
The computer is recognizing the phone and I can use fastboot to flash a new recovery but CWM and TWRP recoveries continue to crash on reboot... What can I do?
Click to expand...
Click to collapse
ipfreelytech said:
S-On or s-off ?
either way your best bet is an RUU. the GPE RUU if your s-off or the proper carrier/region RUU if your s-on.
Click to expand...
Click to collapse
Thank you for the reply, I believe it is s-On the top of the bootloader screen shows tampered & unlocked..
if it doesn't say s-off and you don't remember doing S-off then you're s-on.
What is your CID? you'll need to track down an RUU that matches. Also since your s-on you can only go up in versions, not down so you have to match the mainver.
mopardroid said:
Thank you for the reply, I believe it is s-On the top of the bootloader screen shows tampered & unlocked..
Click to expand...
Click to collapse
ipfreelytech said:
if it doesn't say s-off and you don't remember doing S-off then you're s-on.
What is your CID? you'll need to track down an RUU that matches. Also since your s-on you can only go up in versions, not down so you have to match the mainver.
Click to expand...
Click to collapse
Yeah it says S-On, how would I find my CID and mainver from fastboot?
ipfreelytech said:
if it doesn't say s-off and you don't remember doing S-off then you're s-on.
What is your CID? you'll need to track down an RUU that matches. Also since your s-on you can only go up in versions, not down so you have to match the mainver.
Click to expand...
Click to collapse
Alright I found my CID: TELUS001 and main version: 1.29.661.5..
mopardroid said:
Yeah it says S-On, how would I find my CID and mainver from fastboot?
Click to expand...
Click to collapse
fastboot getvar all
dingdong3000 said:
fastboot getvar all
Click to expand...
Click to collapse
I cant find any RUU's that match that Main version # but I found a nandroid with the matching CID and Mainver.. is there anything I can do with that?
ipfreelytech said:
if it doesn't say s-off and you don't remember doing S-off then you're s-on.
What is your CID? you'll need to track down an RUU that matches. Also since your s-on you can only go up in versions, not down so you have to match the mainver.
Click to expand...
Click to collapse
Ok so I used fastboot to flash a bunch of different recoveries the only recoveries that will work are the CWM Sprint and TWRP sprint recoveries.. I can get into the recovery without it crashing but I am stuck there... I have tried to adb push a rom to the phone, that worked then the install failed.. any suggestions?
mopardroid said:
I cant find any RUU's that match that Main version # but I found a nandroid with the matching CID and Mainver.. is there anything I can do with that?
Click to expand...
Click to collapse
What hboot do you have
1. Download a fresh copy of the latest twrp 2.6.3.3 from here ------> http://techerrata.com/browse/twrp2/m7
2. Throw that recovery image into your fastboot folder and rename it twrp
Fastboot erase cache
Fastboot flash recovery twrp.img
Fastboot erase cache
Fastboot reboot-bootloader
Sometimes that erase cache command does the trick
Sent from my HTC One using Tapatalk
Sent from my HTC One using Tapatalk
InflatedTitan said:
What hboot do you have
1. Download a fresh copy of the latest twrp 2.6.3.3 from here ------> http://techerrata.com/browse/twrp2/m7
2. Throw that recovery image into your fastboot folder and rename it twrp
Fastboot erase cache
Fastboot flash recovery twrp.img
Fastboot erase cache
Fastboot reboot-bootloader
Sometimes that erase cache command does the trick
Sent from my HTC One using Tapatalk
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thank you very much I will give that a shot in just a moment. I checked my Hboot and it is 1.44. This is killing me I really appreciate the help.
InflatedTitan said:
What hboot do you have
1. Download a fresh copy of the latest twrp 2.6.3.3 from here ------> http://techerrata.com/browse/twrp2/m7
2. Throw that recovery image into your fastboot folder and rename it twrp
Fastboot erase cache
Fastboot flash recovery twrp.img
Fastboot erase cache
Fastboot reboot-bootloader
Sometimes that erase cache command does the trick
Sent from my HTC One using Tapatalk
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
That recovery worked without crashing. ADB is recognizing the device.. im going to sideloading a rom now, is there something else worth trying if that doesnt work?
mopardroid said:
That recovery worked without crashing. ADB is recognizing the device.. im going to sideloading a rom now, is there something else worth trying if that doesnt work?
Click to expand...
Click to collapse
Not really bro. Try to sideload any ROM, I'd shoot for a GE ROM since its a little smaller. As soon as you can get into an OS I hope you try to s-off lol. If you were s-off your problem would be fixed
Sent from my HTC One using Tapatalk
InflatedTitan said:
Not really bro. Try to sideload any ROM, I'd shoot for a GE ROM since its a little smaller. As soon as you can get into an OS I hope you try to s-off lol. If you were s-off your problem would be fixed
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Well sideload got to 100% then the phone shut off and when I turned it back on it just looped back into recovery again... going to try again :/ hope it works
InflatedTitan said:
Not really bro. Try to sideload any ROM, I'd shoot for a GE ROM since its a little smaller. As soon as you can get into an OS I hope you try to s-off lol. If you were s-off your problem would be fixed
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thank you SO much man its finally working and I can go to bed honestly I really appreciate the time you took to help!
My phone is all sorts of messed up...
Bottomline is that my bootloader is locked, I am S-Off, and I do not have root access
I've read that I cannot unlock my bootloader with htcdev if I am s-off
I tried unlocking my bootloader with revone, but I get a segmentation fault
How can I get my bootloader unlocked?
My firmware is 4.19.401.11
Someone please help me. I have been stuck with issues for over 24 hours now.
Thank you.
stringer barksdale said:
My phone is all sorts of messed up...
Bottomline is that my bootloader is locked, I am S-Off, and I do not have root access
I've read that I cannot unlock my bootloader with htcdev if I am s-off
I tried unlocking my bootloader with revone, but I get a segmentation fault
How can I get my bootloader unlocked?
My firmware is 4.19.401.11
Someone please help me. I have been stuck with issues for over 24 hours now.
Thank you.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2475914
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
Try this
http://forum.xda-developers.com/showthread.php?t=2475914
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for replying.
I have tried that, but I when I enter su, I don't get the # prompt, it stays at $.
stringer barksdale said:
Thanks for replying.
I have tried that, but I when I enter su, I don't get the # prompt, it stays at $.
Click to expand...
Click to collapse
Have a look at this
www.youtube.com/watch?v=1v29TIpcODs
Sent from my Nexus 7 using XDA Premium 4 mobile app
stringer barksdale said:
Thanks for replying.
I have tried that, but I when I enter su, I don't get the # prompt, it stays at $.
Click to expand...
Click to collapse
not sure if you're still looking for a solution to this, but you can use @scotty1223's commands in custom recovery (CWM or TWRP 2.6.3.3+) http://forum.xda-developers.com/showthread.php?t=2475914
if you don't have a custom recovery (and therefore cannot "fastboot flash recovery ..."), you can use of these "firmware" packages (m7_u/ul only):
http://www.androidfilehost.com/?w=files&flid=13085
fastboot oem rebootRUU
fastboot flash zip fw_m7ul_TWRP_2.6.3.3_1.26.401.33.zip
fastboot reboot-bootloader
-> enter RECOVERY (should be TWRP now)
and use the adb commands to unlock.
Hi Everyone
While trying to unroot my one i eventually got stuck on my bootloader. What happened was that I typed in "fastboot oem lock" in adb and now I can't go into recovery or reboot. I know I should install a RUU at this point but I can't find an RUU for my phone! When I get "fastboot getvar all" I see that my "version-main" is 3.23.666.1 (is that the right one to look at?) and so I've scoured for hours for an RUU but only found OTAs which I don't know how to use. If it helps I'm on HBOOT 1.55.
I also remember pressing unroot in OTA unroot (I don't remember the exact app name) and tried pressing restore root but it did nothing so I started doing the above stuff with RUUs.
I'm pretty stumped right now and I would appreciate any help at all, thank you!
KoalaSuccess said:
Hi Everyone
While trying to unroot my one i eventually got stuck on my bootloader. What happened was that I typed in "fastboot oem lock" in adb and now I can't go into recovery or reboot. I know I should install a RUU at this point but I can't find an RUU for my phone! When I get "fastboot getvar all" I see that my "version-main" is 3.23.666.1 (is that the right one to look at?) and so I've scoured for hours for an RUU but only found OTAs which I don't know how to use. If it helps I'm on HBOOT 1.55.
I also remember pressing unroot in OTA unroot (I don't remember the exact app name) and tried pressing restore root but it did nothing so I started doing the above stuff with RUUs.
I'm pretty stumped right now and I would appreciate any help at all, thank you!
Click to expand...
Click to collapse
If you have an unlocktoken flash it with fastboot flashunlocktoken Unlock_code.bin
If you dont have it, go to htcdev.com and visit unlock bootloader section and follow instructions there.
Once your bootloader is unlocked again, flash twrp recovery and ABD sideload some ROM.
After this you can start all over again whatever it is you were trying to do.
P.S. this will not get you the right RUU package but it will get your phone back to useful condition.
My advice is first you find an RUU for your phone and then do the bootloader manipulations.
7ftnick said:
If you have an unlocktoken flash it with fastboot flashunlocktoken Unlock_code.bin
If you dont have it, go to htcdev.com and visit unlock bootloader section and follow instructions there.
Once your bootloader is unlocked again, flash twrp recovery and ABD sideload some ROM.
After this you can start all over again whatever it is you were trying to do.
P.S. this will not get you the right RUU package but it will get your phone back to useful condition.
My advice is first you find an RUU for your phone and then do the bootloader manipulations.
Click to expand...
Click to collapse
Thanks for the reply! I did that and my phone was working fine again. I went to go flash a stock rom that I found and it flashed fine but now the NFC logo flashes in the status bar even though it's not on. Also, my wifi doesn't work! It constantly says turning on wifi.. I'm trying to flash a different stock rom but I can't enter recovery anymore I would be fine except no wifi is a bit of a problem. Thank you for the reply by the way, is there a chance you can help me find an RUU for my phone? I've searched everywhere but there doesn't seem to be one.
KoalaSuccess said:
Thanks for the reply! I did that and my phone was working fine again. I went to go flash a stock rom that I found and it flashed fine but now the NFC logo flashes in the status bar even though it's not on. Also, my wifi doesn't work! It constantly says turning on wifi.. I'm trying to flash a different stock rom but I can't enter recovery anymore I would be fine except no wifi is a bit of a problem. Thank you for the reply by the way, is there a chance you can help me find an RUU for my phone? I've searched everywhere but there doesn't seem to be one.
Click to expand...
Click to collapse
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
SaHiLzZ said:
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
Click to expand...
Click to collapse
I took a look and I'll try it! Do you know if my device is Bell? I'm not sure how to tell.
SaHiLzZ said:
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
Click to expand...
Click to collapse
So I managed to get my phone working again thanks to your guide! but once I went in to get my S-OFF the program got stuck on pouring 2 after I left it for an hour I hard reset my phone and now I can't boot into recovery or main OS, just bootloader. But in bootloader I see at the top that it says my phone is S-OFF but I can't do the remove tampered because I can't use adb because I can't boot into main OS! I've tried flashing different recovery TWRP but it isn't changing anything..
Any help would be greatly appreciated
KoalaSuccess said:
So I managed to get my phone working again thanks to your guide! but once I went in to get my S-OFF the program got stuck on pouring 2 after I left it for an hour I hard reset my phone and now I can't boot into recovery or main OS, just bootloader. But in bootloader I see at the top that it says my phone is S-OFF but I can't do the remove tampered because I can't use adb because I can't boot into main OS! I've tried flashing different recovery TWRP but it isn't changing anything..
Any help would be greatly appreciated
Click to expand...
Click to collapse
did you erased cache after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery again.
alray said:
did you erased cache after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery again.
Click to expand...
Click to collapse
Yeah I did try to erase cache, no luck. but I managed to fix it by turning my S-OFF back to S-ON by typing fastboot oem writesecureflag 3
after that I flashed twrp again and then i was able to boot up to OS again. Thanks for the help everyone!
KoalaSuccess said:
Yeah I did try to erase cache, no luck. but I managed to fix it by turning my S-OFF back to S-ON by typing fastboot oem writesecureflag 3
after that I flashed twrp again and then i was able to boot up to OS again. Thanks for the help everyone!
Click to expand...
Click to collapse
well that is strange, you should have kept s-off and try other things first but well, its to late. At least your phone is working now
i have unlocked my bootloader and now im not able to roll back to stock firmware.
please help me.
Pinchyneilprince said:
i have unlocked my bootloader and now im not able to roll back to stock firmware.
please help me.
Click to expand...
Click to collapse
Which version of OST are you using? You need to use version 6.0.4
Pinchyneilprince said:
i have unlocked my bootloader and now im not able to roll back to stock firmware.
please help me.
Click to expand...
Click to collapse
Did you use
Code:
fastboot flashing unlock_critical
or just
Code:
fastboot oem unlock-go
You have to do
Code:
fastboot flashing unlock_critical
to be able to reflash bootloader
Thank q sir.
Doktaphex said:
Did you use
Code:
fastboot flashing unlock_critical
or just
Code:
fastboot oem unlock-go
You have to do
Code:
fastboot flashing unlock_critical
to be able to reflash bootloader
Click to expand...
Click to collapse
This worked for me thank q sir.
Doktaphex said:
Did you use
Code:
fastboot flashing unlock_critical
or just
Code:
fastboot oem unlock-go
You have to do
Code:
fastboot flashing unlock_critical
to be able to reflash bootloader
Click to expand...
Click to collapse
I am in same position! Bricked maybe ...
I previously got an unlock bootloader key and all was great.
I then went to relock my bootloader and now I can only get into download mode.
I tried loading up into OST but it freezes on ‘reflash service bootloader’.
I was on the latest Android P Beta.
I even tried unlocking the bootloader using the original .bin file but that didn’t work.
Is there anything I can do?
Deleted....
I had the same problem yesterday evening.... I download the rollback zip to Oreo on Nokia developper website, i copy it on my external sd card, i boot in recovery mode, wipe all data, and i choose apply an update from sd card, and i zelect the zip, and it works well!
The only problem is the loss of all your data if it was not saved...
poczynek said:
Did you use or just
You have to do
I am in same position! Bricked maybe ...
I previously got an unlock bootloader key and all was great.
I then went to relock my bootloader and now I can only get into download mode.
I tried loading up into OST but it freezes on ‘reflash service bootloader’.
I was on the latest Android P Beta.
I even tried unlocking the bootloader using the original .bin file but that didn’t work.
Is there anything I can do?
Click to expand...
Click to collapse
If u are on locked bootloader then OST won't work. OST will work only in Unlocked bootloader.
And u can't enter in recovery mod. Only download mod. Correct? Same happened with me also. Now my phone is in service centre for tha past 11 days. They told Motherboard issue and can claim warranty. So i am waiting for new motherboard and my 7+.
Pinchyneilprince said:
i have unlocked my bootloader and now im not able to roll back to stock firmware.
how do u unlocked bootloader?
Click to expand...
Click to collapse
speechless said:
Pinchyneilprince said:
i have unlocked my bootloader and now im not able to roll back to stock firmware.
how do u unlocked bootloader?
Click to expand...
Click to collapse
U can pay and buy unlock code. Guys doing this in telegram. Contact them
Click to expand...
Click to collapse
Rajeev said:
speechless said:
U can pay and buy unlock code. Guys doing this in telegram. Contact them
Click to expand...
Click to collapse
i dont have creditcart to pay :crying: anyway can u send me his profile link pls
Click to expand...
Click to collapse
speechless said:
Rajeev said:
i dont have creditcart to pay :crying: anyway can u send me his profile link pls
Click to expand...
Click to collapse
I don't have buddy. I lost all contacts.. sorry..
Click to expand...
Click to collapse
Rajeev said:
speechless said:
I don't have buddy. I lost all contacts.. sorry..[/QUO
It's ok bro no prob
Click to expand...
Click to collapse
Click to expand...
Click to collapse
siberflyers said:
I had the same problem yesterday evening.... I download the rollback zip to Oreo on Nokia developper website, i copy it on my external sd card, i boot in recovery mode, wipe all data, and i choose apply an update from sd card, and i zelect the zip, and it works well!
The only problem is the loss of all your data if it was not saved...
Click to expand...
Click to collapse
can you give me thd link pls
Doktaphex said:
Did you use
Code:
fastboot flashing unlock_critical
or just
Code:
fastboot oem unlock-go
You have to do
Code:
fastboot flashing unlock_critical
to be able to reflash bootloader
Click to expand...
Click to collapse
can you plz tell me how do you use codes with OST, thanks