Soft Brick or Hard Brick? - One (M7) Q&A, Help & Troubleshooting

Hi guys,
I had back to completely stock my m7 for guarantee 2 weeks ago. Yesterday i tried every possible way to s-off but i can't get it. So i tried run RUU for downgrade OS,hboot etc. relock bootloader. But accidentally RUU removed OS; no main version in getvar, stock recovery, relocked and there is a warning under relocked title it says ''security warning''
Run RUU or flash update.zip,rom.zip,ruu.zip no matter what,I get 'failed: remote signiture verify fail'. Phone does not boot, because no OS, so no adb. Is only way J-tag for ressurrect it

blitzzkrieg said:
Hi guys,
I had back to completely stock my m7 for guarantee 2 weeks ago. Yesterday i tried every possible way to s-off but i can't get it. So i tried run RUU for downgrade OS,hboot etc. relock bootloader. But accidentally RUU removed OS; no main version in getvar, stock recovery, relocked and there is a warning under relocked title it says ''security warning''
Run RUU or flash update.zip,rom.zip,ruu.zip no matter what,I get 'failed: remote signiture verify fail'. Phone does not boot, because no OS, so no adb. Is only way J-tag for ressurrect it
Click to expand...
Click to collapse
you can not downgrade with s-on!
re-unlock your bootloader, flash a custom recovery and a rom and achieve s-off with sunshine then follow nkk71's guide to return stock (linked in my sig)

alray said:
you can not downgrade with s-on!
re-unlock your bootloader, flash a custom recovery and a rom and achieve s-off with sunshine then follow nkk71's guide to return stock (linked in my sig)
Click to expand...
Click to collapse
I can't unlock bootloader back, flashing unlock_code.bin and allow prompt from phone, it goes to update screen, 2 minutes later i get red triangle screen. I have to unlock my bootloader without unlock_code but my hboot 1.57. So i think my device is dead

Try generating another unlock bin

Related

Unlock bootloader

I'm kinda new to IncS, cause I had Desire untill a few days ago and I have a lot of experience with this things on it.
So what's my point, I'm about to unlock bootloader over htcdev cause I have ICS sense 3.6 (www_asia_hk build 4.10.708.1 with 2.02 hboot so htcdev is the only option as I could find), and my question is will I be able to get it back to factory state (with LOCKED sign) with ruu if I have to get the phone back to the seller for waranty purpose?
Don't jump on me, I tried the search but all the answers I could find were incomplete.
Thanks in adwance.
nlooooo said:
I'm kinda new to IncS, cause I had Desire untill a few days ago and I have a lot of experience with this things on it.
So what's my point, I'm about to unlock bootloader over htcdev cause I have ICS sense 3.6 (www_asia_hk build 4.10.708.1 with 2.02 hboot so htcdev is the only option as I could find), and my question is will I be able to get it back to factory state (with LOCKED sign) with ruu if I have to get the phone back to the seller for waranty purpose?
Don't jump on me, I tried the search but all the answers I could find were incomplete.
Thanks in adwance.
Click to expand...
Click to collapse
You will be able to RELOCK the bootloader, but as long as you have a RUU that has unlockable bootloader in it installed, there will always be a tell-tale sign because the HBOOT screen will show "RELOCKED" instead of "LOCKED".
Also, part of the unlocking procedure at HTCDEV.com requires that you acknowledge that this process 'could void your warranty' and HTC will have a record that you unlocked the bootloader.
I don't worry about HTC cause I got sellers warranty, so repair won't be performed by the HTC service.
And one more question, so if I run ruu over relocked bootloader I won't get LOCKED sign again?
Edit:
After I unlock bootloader, if I do a downgrade to older hboot and s-off it via revolutionary, is there a way for getting back to factory state?
nlooooo said:
I don't worry about HTC cause I got sellers warranty, so repair won't be performed by the HTC service.
And one more question, so if I run ruu over relocked bootloader I won't get LOCKED sign again?
Edit:
After I unlock bootloader, if I do a downgrade to older hboot and s-off it via revolutionary, is there a way for getting back to factory state?
Click to expand...
Click to collapse
Yes, if you use the downgrade procedure, then you could flash a Gingerbread 2.3.3/Sense 2.1 RUU then HBOOT would not show a lock status as long as you left it on that ROM.
If you flash any RUU starting with GB 2.3.5/Sense 3.0 and above, then the HBOOT screen will always show RELOCKED on the HBOOT screen. This will also occur if you take an OTA update for the GB 2.3.5/Sense 3.0.

[Q] Re-locked, s-on, Security Warning, and cannot boot into Recovery. My options?

Hi guys.
First time posting, but have used the site extensively over the past 6-8 months. I have an AT&T HTC One. I had unlocked it, s-off, rooted, installed GPe, and decided to go back. The ROM I went back to was supposed to be MY stock ROM, but it turns out it was unbranded 4.2.2. I thought nothing of it, and as of yesterday, had sold my phone on ebay. I decided to wipe my phone to get ready to ship. I locked my bootloader and went to s-on, but when I went to factory reset, I got a "security warning" and it won't reboot into recovery. I've tried everything- tried to re-unlock it with htcdev, which freezes at the bootloader. I've tried to unlock via revone, since I still have root (root checker verified this to be the case), but get the -6 error when using terminal emulator in ROM Toolbox, and get the same error when doing it via adb commands. I've tried probably 50 different things about 10 different times, and am about to pull my hair out! I've read and searched probably hundreds of threads over the past 24 hours. Trying to flash stock RUU (the exe) just freezes as well. Any help would be appreciated! Let me know what info you need from me.
Android 4.2.2
Hboot 1.44
Software number 2.24.401.8
HTC SDK API level 5.34
Kernel version 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Baseband version 4A.18.3263.15_10.38h.1157.04L
Build number 2.24.401.8 CL235216 release-keys
Thanks guys! Awesome community!
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
but also Read Mike 1986's Return to stock Guide before - this will ensure you are aware of what needs doing before you start to do it
http://forum.xda-developers.com/showthread.php?t=2265618
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
The search option would have found these for you and saved some time and heartache :highfive:
L0rdNels0n said:
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Click to expand...
Click to collapse
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads (every RUU I've tried fails miserably, and extracted rom.zips don't work either). It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
AndyM3 said:
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads. It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
Click to expand...
Click to collapse
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
nkk71 said:
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
Click to expand...
Click to collapse
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
nkk71 said:
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
Click to expand...
Click to collapse
I downloaded a 1.20.401 RUU (should be 4.1.2, probably), and I am on mike1986's odexed ROM right now. I'd downgrade, but how? I can't install a custom recovery.
Edit: RUU exited with a "bootloader version error". Could I have downloaded a corrupt HBOOT or something? revone gave success messages about five times now, but the bootloader still says "LOCKED" and "S-ON".
AndyM3 said:
the bootloader still says "LOCKED" and "S-OFF".
Click to expand...
Click to collapse
So S-Off achieved great.
What's still the problem?
nkk71 said:
So S-Off achieved great.
What's still the problem?
Click to expand...
Click to collapse
Typo, sorry. It's S-ON.
AndyM3 said:
Typo, sorry. It's S-ON.
Click to expand...
Click to collapse
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
nkk71 said:
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
Click to expand...
Click to collapse
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
AndyM3 said:
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
Click to expand...
Click to collapse
Sometimes a factory reset can help with the unlock token, but since you're on 1.54 now it would make little difference.
Sorry & good luck
Sent from my HTC One using xda app-developers app
Yep. I'm in exactly the same boat. Actually, I am on 1.44 HBOOT, dated May 3rd, and none of the available options worked. And yes, I've tried the links included in subsequent posts. And I'm "locked" via same way as above. Since I was selling the phone and trying to revert to stock, my only option was to manually erase everything and send it off. I couldn't do a factory reset, because it just kicked me to bootloader with a "security warning" error. Couldn't install older RUU, as it would just hang at the HTC black screen with no green progress bar.
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
Same problem
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
PlaviiCZ said:
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
Sorry for my bad english, but I hope hope you'll understand.
Click to expand...
Click to collapse
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
clsA said:
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
Click to expand...
Click to collapse
Yeah, I'm dumbass...Yes, I did, and nothing...just "failed" in cmd. Should I try again to tell you, what is in cmd exactly written?
EDIT: Please help (
No one knows anything?

Failed: Return to stock and unrooted (Verizon)

I posted in the Verizon forums a day ago, but have received little to no help. Now I hope that someone can help me here.
Original post http://forum.xda-developers.com/showthread.php?t=2599610
I used this thread to unroot and return to stock http://forum.xda-developers.com/show...highlight=s-on
I had done this before with one of CM 10 and I kept the files used in this thread.
I switched to AOKP kitkat 12-30-13. I wanted to return to stock and unrooted.
I got to the oem ruu and kept receiving this message. FAILED (remote: 90 hboot pre-update! please flush image again immediately)
I did this repeatedly as followed. It went over 5 times. I figured this was a problem. Now I am stuck in the bootloader where my phone is locked and S-on. I tried to flash it again and now I get remote: 12 signature verify failed.
It also says ***TAMPERED*** at the top of bootloader, above ***LOCKED***
Edit: I wanted to mention that I do have a backup of my kitkat state at the beginning of all of this. It is in twrp, but I can't flash install the twrp.img, signature verify failed.
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
sweetnsour said:
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
Click to expand...
Click to collapse
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
geeibara said:
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
Click to expand...
Click to collapse
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
sweetnsour said:
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
Click to expand...
Click to collapse
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
geeibara said:
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
Click to expand...
Click to collapse
to be able to reflash twrp you need to unlock your bootloader that is why you are getting signature fail error

[Q] Stuck in bootloader s-on and tampered

Hi everyone. I searched for around half an hour through google and failed to find a situation identical to mine (maybe i havent looked long enough).
I was one step away from resetting the warranty by removing root and locking bootloader again so that i could send it to HTC for repair (its under warranty.
I locked the bootloader and turned s-on. Then after flashing a stock ruu (i was sure i had the correct version) it returned to bootloader and all of a sudden it says TAMPERED again with s-on..
The phone now will not get out of bootloader. Since its s-on i cant flash a rom or recovery or flash a ruu. When trying to flash a stock ruu it says signature verify fail
ran fastboot getvar all
Phone details:
Bootloader: 1.44.0000
Baseband 4V.13.3231.27
Currently TAMPERED bootloader, LOCKED with S-ON.
How do i now get s-off again from this position?
Thanks in advance!
UPDATE:::: I unlocked bootloader through HTCDEV. THis can be closed
You should be able to get S-off again using Revone with HBOOT 1.44. You should be able to find everything you need here http://forum.xda-developers.com/showthread.php?t=2314582 . I was unable to flash any RUU file until I achieved S-off, but I had to use firewater as I couldn't get revone to work with HBOOT 1.57. Here is the firewater link http://forum.xda-developers.com/showthread.php?t=2632351 .

[Q] HTC One stuck in bootloader with relocked bootloader, s-on and custom recovery

​my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh. I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
​my Hboot is version 1.57 and my OS is 6. 10.531.9
​I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
​if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.
kage_outram said:
​my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh.
I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
​my Hboot is version 1.57 and my OS is 6. 10.531.9
​I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
​if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.
Click to expand...
Click to collapse
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.
majmoz said:
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.
Click to expand...
Click to collapse
What commands do I put in to add the RUU
kage_outram said:
What commands do I put in to add the RUU
Click to expand...
Click to collapse
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer
majmoz said:
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer
Click to expand...
Click to collapse
what should happen next

Categories

Resources