Please note you must be bootloader unlocked and S-OFF for this to work
you are doing this at your own risk dont blame me if something goes wrong i have tested this twice one on CM and once on Stock
that being said
This guide will help you return to stock un-rooted, locked, and s-on in the event you ever need to use the warranty
You will need the decrypted RUU from here
http://forum.xda-developers.com/sho...pers.com/showpost.php?p=46153741&postcount=31
I recommend copy and paste for the command so you don’t mistype something
This will lock your bootloader and make it show LOCKED not RELOCKED
While still in the bootloader type
Code:
Fastboot oem rebootRUU
Once in ruu mode *blackscreen with HTC text* its time to flash the decrypted ruu make sure you have placed the rom in the folder and named it Rom.zip
Run following command
Code:
Fastboot flash zip Rom.zip
It appears some people are confused on the following. You must confirm your device successfully flashes the ruu before contiuning
It could work the first time or could error out multiple times typically it fails the first time then completes the 2nd bu not a promise also make sure you have checked the md5 hash
You will most likely get the following error
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Don’t worry this is normal (typically fails the first time) (also it could boot you out of ruu mode when it does) just make sure your phone still shows its in ruu mode
If it is not just retype
Code:
fastboot oem rebootRUU
Then re-run the command
Code:
Fastboot flash zip Rom.zip
Once it finishes the phone will stay in ruu mode simply type
Code:
Fastboot reboot-bootloader
At this point you are stock unrooted and bootloader locked but still s-off to change this type
Code:
fastboot oem writesecureflag 3
you should get a message back saying
“(bootloader) writesecureflag: partitions signature pass
OKAY [ 1.666s]
finished. total time: 1.666s”
now type
fastboot reboot-bootloader
and verify you are now S-ON andtype
Code:
fastboot reboot
and your phone will load to stock
note this will be stock version m7wlv_1.10.605.8 so you will need to take the ota to update to 605.10
hope this helps
Thanks for this!
Fantastic Post
Thanks so much for this.
Frankie1588 said:
Thanks for this!
Click to expand...
Click to collapse
godhamba said:
Thanks so much for this.
Click to expand...
Click to collapse
hope it helps i did it twice before making the post to make sure dont wanna lead anyone down wrong direction
bmt626 said:
hope it helps i did it twice before making the post to make sure dont wanna lead anyone down wrong direction
Click to expand...
Click to collapse
I need HELP! I read the BIG RED PRINT about being bootloader unlocked but I still foolishly locked the bootloader prior to running this......I'm still S-Off but it will not flash the RUU. And now it is in a boot loop into recovery. I've tried running the lock unlock ADB scipt but I can't seem to get the device to connect in ADB mode.....fastboot works fine.
Hopefully I don't have a nice looking paper weight.
and BTW the reason i locked the BL is because I was reading other info on the web ( Youtube ) and got in a hurry.....LET THIS BE A REMINDER.
tpierce67 said:
I need HELP! I read the BIG RED PRINT about being bootloader unlocked but I still foolishly locked the bootloader prior to running this......I'm still S-Off but it will not flash the RUU. And now it is in a boot loop into recovery. I've tried running the lock unlock ADB scipt but I can't seem to get the device to connect in ADB mode.....fastboot works fine.
Hopefully I don't have a nice looking paper weight.
and BTW the reason i locked the BL is because I was reading other info on the web ( Youtube ) and got in a hurry.....LET THIS BE A REMINDER.
Click to expand...
Click to collapse
You do need to lock the bootloader at one point in my guide
What command did you run to lock the boot loader
Adb only works when booted in to a os
My advice is boot into bootloader then flash a custom recovery and flash cm from cm run unlock command in adb and try again following my directions
Sent from my HTC6500LVW using Tapatalk now Free
Thanks for the assit. I ran fastoot oem lock as the first step. I saw a couple of vids on youtube with those instructions. I will try your suggestions and see what happens. I left the phone at work cause I have iMac at home and I figured it was a paper weight at this point. Hopefully I will have better luck tomorrow.
tpierce67 said:
Thanks for the assit. I ran fastoot oem lock as the first step. I saw a couple of vids on youtube with those instructions. I will try your suggestions and see what happens. I left the phone at work cause I have iMac at home and I figured it was a paper weight at this point. Hopefully I will have better luck tomorrow.
Click to expand...
Click to collapse
just run this command from an
Code:
adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
that should make it read unlocked again i ran fastboot oem lock when i was first testing and that command got me back
tpierce67 said:
Thanks for the assit. I ran fastoot oem lock as the first step. I saw a couple of vids on youtube with those instructions. I will try your suggestions and see what happens. I left the phone at work cause I have iMac at home and I figured it was a paper weight at this point. Hopefully I will have better luck tomorrow.
Click to expand...
Click to collapse
let me know if you have issues ill be happy to help out
This is what i get when i try to flash a customer reovery
C:\Fastboot>fastboot flash recovery ope
sending 'recovery' (8504 KB)...
OKAY [ 1.156s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.987s
I need to find a way to unlock the bootloader. I'm stuck in bootloader mode.
---------- Post added at 02:15 PM ---------- Previous post was at 02:07 PM ----------
my bootloader screen reads
tampered
relocked
security warning
M7_WLV PVT SHIP S-ON RH
I'm not sure what happened since yesterday but I left my office it still read S-Off. I tried to install Rummrunner but since I can't enable USB debugging it won't flash.
tpierce67 said:
This is what i get when i try to flash a customer reovery
C:\Fastboot>fastboot flash recovery ope
sending 'recovery' (8504 KB)...
OKAY [ 1.156s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.987s
I need to find a way to unlock the bootloader. I'm stuck in bootloader mode.
---------- Post added at 02:15 PM ---------- Previous post was at 02:07 PM ----------
my bootloader screen reads
tampered
relocked
security warning
M7_WLV PVT SHIP S-ON RH
I'm not sure what happened since yesterday but I left my office it still read S-Off. I tried to install Rummrunner but since I can't enable USB debugging it won't flash.
Click to expand...
Click to collapse
Use your unlock token
Sent from my One using xda app-developers app
123421342 said:
Use your unlock token
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
Thank you for the reply. I used rummrunners method for unlock and S-Off. My HTC One is a Verizon model and not unlockable on the HTCdev website. so I don't have a token.
@tpierce67 - did you try the echo command he mentioned a few posts back to get it to read unlocked again? Edit: I think it just now clicked (re-read through for the 3rd time) why you probably weren't able to run that command... no custom recovery, no rom, no adb...
@bmt626 - so I take it SuperCID isn't necessary before running this?
jntdroid said:
@tpierce67 - did you try the echo command he mentioned a few posts back to get it to read unlocked again?
@bmt626 - so I take it SuperCID isn't necessary before running this?
Click to expand...
Click to collapse
Nope I left my Cid as vzw
Sent from my HTC6500LVW using Tapatalk now Free
Does this only work if you have the unlock token? or are you able to use this method if you used RumRunner Method to get S-Off?
kobusestas said:
Does this only work if you have the unlock token? or are you able to use this method if you used RumRunner Method to get S-Off?
Click to expand...
Click to collapse
I would assume both but I only used rumrunner I don't have an unlock token
Sent from my HTC6500LVW using Tapatalk now Free
bmt626 said:
I would assume both but I only used rumrunner I don't have an unlock token
Sent from my HTC6500LVW using Tapatalk now Free
Click to expand...
Click to collapse
And it worked for you without having the unlock token? My goal is to simply have the option to return to S-ON stock Locked in case I ever needed it. I used RumRunner to unlock my device.
I was able to do this without issues.. but It's showing tampered and I have no custom recovery?
Am I screwed for now? Or is there anything additional I can do? PC won't read it.. and it won't boot..
I have the option for recovery but it kicks me back out to fastboot..
jntdroid said:
@tpierce67 - did you try the echo command he mentioned a few posts back to get it to read unlocked again? Edit: I think it just now clicked (re-read through for the 3rd time) why you probably weren't able to run that command... no custom recovery, no rom, no adb...
@bmt626 - so I take it SuperCID isn't necessary before running this?
Click to expand...
Click to collapse
The Echo command is an ADB command and I can't get that far. I'm running out of options.
@bmt626 - thanks again for this... I'm about to run it, but have one random, anal question... do you see any reason at all that I would need my sim in and the phone activated for this to work? I can't think of one, but just wanted to throw it out there to make myself feel better before running this
Related
Hi, I have been the happy owner of an international HTC One X for just over a month now. I'm from Australia and my carrier is Vodafone.I have been using the Lee-Droid One Xtreme Rom without issue for almost the entire time I've owned the phone, however two days ago some huge issues appeared.
First the handset resest itself, this had happened before but this time it was stuck on the "HTC Quietly Brilliant" splash screen. I tried to wipe the cache from recovery but recovery wouldn't boot. I plugged the phone into my laptop and used "fastboot erase cache" which seemed to work but did not solve my problem, still hanging at the splash screen.
I then noticed that my bootloader had somehow locked itself again so I flashed my Unlock_code.bin again, the handset displayed the usual prompts which I followed but when my phone reset I was greeted with the now familiar hanging bootsplash plus a warning about the ROM being for internal HTC use only.
I also noticed this message in my terminal:
FAILED (status read failed (Cannot send after transport endpoint shutdown))
Can someone please help me here? I'm hesitant to send the phone away because I unocked the bootloader via htcdev.com so my warranty is invalid most likely.
Thanks for your time and sorry if this is a duplicate thread, I had done a few searches already and found nothing that spunded like my problem though.
Did your bootloader say locked or relocked
Sent from my HTC One X using Tapatalk 2
Did u flash de cwm last recovery? There are some problems with usb, try to use another One, install drivers, restart pc.
Htc One X Venom ViperX Rom & Show-p Kernel
@KrisPerry - the bootloader says either :
***LOCKED***
or
***LOCKED***
***SECURITY WARNING***
@drangonesdenano
last recovery I flashed CWM 5.8.4.0
have tried restarting pc, no change.
i use linux so there are no drivers to reinstall.
none of the cables i have fit, but this is the original htc cable, it seems to be in decent condition, i'll try and see if i can borrow one from a friend though.
sorry for taking a while to reply to you guys, i've been having login troubles with the xda site. thankyou for your help thusfar. any ideas?
Try closing and opening bootloader again, then flash recovery if not working properly. Has to do with usb ... I think ..not to cable. Then tell us
Htc One X Venom ViperX Rom & faux123 b004b7 Kernel
dragonesdenano said:
Try closing and opening bootloader again, then flash recovery if not working properly. Has to do with usb ... I think ..not to cable. Then tell us
Htc One X Venom ViperX Rom & faux123 b004b7 Kernel
Click to expand...
Click to collapse
hi, sorry for taking so long to reply, i have been having some major troubles with both my computer and then getting enough charge into the phone. i ended up writing this script:
Code:
#!/bin/sh
while true
do
./fastboot getvar battery-voltage
./fastboot reboot-bootloader
sleep 10
done
writing from a different pc with a fresh linux mint install i've tried unlocking the bootloader again but this time i'm getting this from the terminal:
Code:
./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (No such device))
finished. total time: 9.179s
what do you think? i bought a second usb cable and have been switching between the two but it makes no difference... i can't flash recovery because the bootloader is locked and i seem to be stuck in a bootloop so i can't boot into CWM either.
i've been reading about people flashing RUU's, is that what i need to do?
Just a gentle bump on this thread, I've been without a phone for over a week now and it's getting pretty annoying (first world problems). Has anyone seen this before? What should I do? Any help would be greatly appreciated.
Cheers, Toby.
RUUs
So I'm looking into the possibility of flashing an RUU, what are my options for doing so under Linux?
I've found this link: http://forum.xda-developers.com/showthread.php?t=1465747
Has anyone used openRUU? Does it work for the HOX?
The only other option I can see is making a Windows virtual machine... My only concern is installing the drivers, will that work seeing as I can only access fastboot?
Also I'm not sure exactly where to find an RUU... I've checked out this link: http://www.filefactory.com/f/7cc7b2fbdd03c031/
but my RUU (1.29.862.11) wasn't there and I've struggled to find a download elsewhere....
any clues?
Any help would be devoured thankfully.
Toby.
Free bump...
Sent from my HTC One X using xda premium
TobyJamesJoy said:
So I'm looking into the possibility of flashing an RUU, what are my options for doing so under Linux?
I've found this link: http://forum.xda-developers.com/showthread.php?t=1465747
Has anyone used openRUU? Does it work for the HOX?
The only other option I can see is making a Windows virtual machine... My only concern is installing the drivers, will that work seeing as I can only access fastboot?
Also I'm not sure exactly where to find an RUU... I've checked out this link: http://www.filefactory.com/f/7cc7b2fbdd03c031/
but my RUU (1.29.862.11) wasn't there and I've struggled to find a download elsewhere....
any clues?
Any help would be devoured thankfully.
Toby.
Click to expand...
Click to collapse
The RUU doesn't do anything fancy, it just packages the boot.img, recovery? and ROM, and uses the same method we would use to flash the bits individually.
If there is no RUU for your version, I hope you took the advise of making a backup.
Update
whynot66 said:
Free bump...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks man!
So I've set out on a mission and made a Virtualbox Windows XP install, installed the sdk and HTC sync, configured the usb settings, and the virtual install seems to be able to detect my handset in fastboot.
Good times.
I was able to run all the fastboot commands I wanted, including "fastboot oem get_identifier_token" which wasn't previously working on the Linux side and now through some kind of voodoo works a charm under Linux too. After running this command I visited the htcdev site and requested a new Unlock_code.bin but that didn't work, still getting FAILED errors...
One thing I have noticed is that every time I run "fastboot oem get_identifier_token" I get a dramatically different token, wil this result in a different Unlock_code.bin? Maybe one of the will work eventually (doubtful).
On the other hand it seems that I've got everything ready to flash an RUU, I just need that RUU... So does anyone know where I can find it?
BenPope said:
The RUU doesn't do anything fancy, it just packages the boot.img, recovery? and ROM, and uses the same method we would use to flash the bits individually.
If there is no RUU for your version, I hope you took the advise of making a backup.
Click to expand...
Click to collapse
I've read this thread:
http://forum.xda-developers.com/wiki/HTC_One_X
and flashing the RUU seems to be the only way to go seeing as my bootloader is locked and won't unlock. Becuase you flash RUUs with a locked bootloader right?
I've read about vodafone releasing this RUU so I'm pretty sure it exists, I'm just not sure how to get it.
I did make a nandroid backup of the stock rom, is it possible to flash that?
I don't care how much data I lose, so long as I get a functional telephone in return.
TobyJamesJoy said:
I've read this thread:
http://forum.xda-developers.com/wiki/HTC_One_X
and flashing the RUU seems to be the only way to go seeing as my bootloader is locked and won't unlock. Becuase you flash RUUs with a locked bootloader right?
I've read about vodafone releasing this RUU so I'm pretty sure it exists, I'm just not sure how to get it.
I did make a nandroid backup of the stock rom, is it possible to flash that?
I don't care how much data I lose, so long as I get a functional telephone in return.
Click to expand...
Click to collapse
Hmmm, so you were unlocked but.now it won't unlock? Odd.
With a stock recovery, you should still be able to flash signed ROMs, perhaps not your backup though.
If it's not on filefactory, it's probably not widely available. Google is your friend, I guess.
BenPope said:
Hmmm, so you were unlocked but.now it won't unlock? Odd.
With a stock recovery, you should still be able to flash signed ROMs, perhaps not your backup though.
If it's not on filefactory, it's probably not widely available. Google is your friend, I guess.
Click to expand...
Click to collapse
yeah, weird huh?
forgive my ignorance but what exactly is a signed rom?
i'm not sure what recovery i've got at the moment, last one i flashed was CWM 5.8.4.0 but that won't boot anymore.. do i need recovery to flash my backup?
in my backup i have a boot.img, recovery.img the md5 sum and a few tarballs (cache, data, system), if i flash recovery.img will i get the stock recovery? or do i need an unlocked bootloader to do that?
and if i get stock recovery what can i flash from there with a locked bootloader?
you were saying that an RUU does the same things as flashing the components individually, but also you say that i might not to be flash my backup, so i'm a bit confused.... n00bdom......
TobyJamesJoy said:
yeah, weird huh?
forgive my ignorance but what exactly is a signed rom?
i'm not sure what recovery i've got at the moment, last one i flashed was CWM 5.8.4.0 but that won't boot anymore.. do i need recovery to flash my backup?
in my backup i have a boot.img, recovery.img the md5 sum and a few tarballs (cache, data, system), if i flash recovery.img will i get the stock recovery? or do i need an unlocked bootloader to do that?
and if i get stock recovery what can i flash from there with a locked bootloader?
you were saying that an RUU does the same things as flashing the components individually, but also you say that i might not to be flash my backup, so i'm a bit confused.... n00bdom......
Click to expand...
Click to collapse
A signed ROM is an official one from HTC, signed by their private key. The CID also has to match your phone. Then the standard recovery will allow it to be flashed.
I find it strange that you are locked.with a nonstandard recovery. I think you should get back to unlocked before proceeding.
Try unlocking your phone from scratch using the normal procedure.
Why doesn't that work? What stage fails? What error do you get?
BenPope said:
A signed ROM is an official one from HTC, signed by their private key. The CID also has to match your phone. Then the standard recovery will allow it to be flashed.
I find it strange that you are locked.with a nonstandard recovery. I think you should get back to unlocked before proceeding.
Try unlocking your phone from scratch using the normal procedure.
Why doesn't that work? What stage fails? What error do you get?
Click to expand...
Click to collapse
I've tried this numerous times, everything works right up to the final stage. My device is recognised by fastboot, I can get the identifier token, flash the Unlock_code.bin, it writes to the handset properly, the handset displays the black screen with "yes" and "no" options and the warnings about voiding your warranty, i choose "yes" and the phone reboots into fastboot while the terminal reads like so:
Code:
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (No such device))
that's under Linux, in my Windows XP virtual box it reads the same except the final line is:
Code:
FAILED (status read failed (Unkown error))
I've tried this on two different PCs, one running arch linux, another on ubuntu 12.04, also on a fresh install of Linux Mint 13. I've tried every different usb port available and I've tried generating different Unlock_code.bin files - nothing seems to work.......
Brickland.
Idea
This may have something to do with my udev rules, these are the ones i'm currently using, I can't remember now where i found them but they govern how the OS handles certain devices. Here's my /etc/udev/rules.d/51-android.rules
Code:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", MODE="0666", OWNER="tobias"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c02",SYMLINK+="android_adb"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c01",SYMLINK+="android_fastboot"
does anyone with some linux knowhow see anything wrong with them?
or am i barking up the wrong tree?
TobyJamesJoy said:
This may have something to do with my udev rules, these are the ones i'm currently using, I can't remember now where i found them but they govern how the OS handles certain devices. Here's my /etc/udev/rules.d/51-android.rules
Code:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", MODE="0666", OWNER="tobias"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c02",SYMLINK+="android_adb"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c01",SYMLINK+="android_fastboot"
does anyone with some linux knowhow see anything wrong with them?
or am i barking up the wrong tree?
Click to expand...
Click to collapse
I think you only need this (and a fraction of it at that) if adb devices shows nothing.
TobyJamesJoy said:
I've tried this numerous times
Snip
Brickland.
Click to expand...
Click to collapse
I have no idea, I've never unlocked mine.
Sorry dude, but I'm sure it can be recovered, you just to find the right incantation.
BenPope said:
I think you only need this (and a fraction of it at that) if adb devices shows nothing.
Click to expand...
Click to collapse
hmm, i'm not sure i follow you but you have hit on one glaring omission of mine, i've never been able to get adb working.... maybe i should forage around for tips in that area.
are you saying that i only need the proper udev rules to get adb working and i should be able to do it with a fraction of the code? what do you mean by "if adb devices shows nothing"?
I have no clue what to do now, I've searched the forums for days now. I don't know what other options I have now. I had my phones bootloader unlocked and s-off. Even had clockworkmod installed (I believe it was version 6.0.4.5) I planned on putting it back to stock when I found out it wouldn't keep a signal and randomly rebooting. I don't know what happened or what I probably did to make it happen, but now I am stuck.
Where I stand now is looking at my phone in the bootloader. I can access fastboot from there but not the recovery. When I try to boot into recovery it seems to hang on a black screen, then after a little wait it shows me a picture of a phone with a red exclamation point inside a triangle. I guessing I would be safe to assume in saying that my recovery is shot. My bootloader says that it is locked with s-on and that it has been tampered (I attached a picture below). I've even tried using an RUU, however I don't know if I am doing it properly.
So I guess my question is this, Is there anything I can do from this point?
I've already accepted the fact I might as well have a brick. Just hoping there is a last resort.
try new recovery
Since you can get into fastboot, type fastboot devices and see if yours shows in list.
If not, check out HTC usb drivers and make sure they're right. Then get most current recovery
like PhilZ's or Clockwork or TWRP.
After connection is sure, type fastboot erase cache.
Then name your recovery recovery.img and flash it: fastboot flash recovery recovery.img.
Then type fastboot reboot-bootloader.
Try getting into your new recovery and go from there.
Forgot to attache the picture, my bad.
I will try that now.
No dice. What I get is this.
sending 'recovery' (9138 KB)...
FAILED (data transger failure (Unknown error))
finished. total time: 0.001s
...
Somehow, you got back to S-0n Locked, and it's not gonna let you do a custom recovery now.
If I'm not mistaken, since you're still only hboot 1.54, you can flash an RUU to get back to full stock. You can grab the RUU here, http://forum.xda-developers.com/showthread.php?t=2428276. Just make sure it's the VZW one. You can follow the directions here, http://forum.xda-developers.com/showthread.php?t=2251800. That thread is in the Sprint forum, but its the same process. You should be able to skip the first part where they re-lock the bootloader. Hope this helped.
I've tried that with different versions of it, many times. After I type the 'fastboot flash zip Rom.zip' all I get is
sending 'zip' (1178304 KB)...
Edit: Then it just hangs there indefinitely until I cancel it
d0m_ said:
I've tried that with different versions of it, many times. After I type the 'fastboot flash zip Rom.zip' all I get is
sending 'zip' (1178304 KB)...
Edit: Then it just hangs there indefinitely until I cancel it
Click to expand...
Click to collapse
If you're locked and s-on I don't believe you can flash an RUU. Could be wrong, but from what I remember, you can't.
Sent from my HTC6500LVW using Tapatalk
brholt6 said:
If you're locked and s-on I don't believe you can flash an RUU. Could be wrong, but from what I remember, you can't.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
If that is the case, then how would I flash an RUU?
eman7131 said:
You should be able to skip the first part where they re-lock the bootloader. Hope this helped.
Click to expand...
Click to collapse
So if we are S-Off, there is no need to relock the bootloader before flashing RUU?
d0m_ said:
If that is the case, then how would I flash an RUU?
Click to expand...
Click to collapse
You would have to wait until there is a newer RUU made available, I think. If you didnt get a failed flag when sending the RUU, I would let it sit there for a while. If you did then I don't know what to tell you.
"So if we are S-Off, there is no need to relock the bootloader before flashing RUU?"
The reason I said what I did was because he was already locked. And it depends on what you're looking to do.
You need to use a signed ruu since your s-on. You can get it in the second post of santods rom radio kernel thread in development.
Once stock and running, use weaksauce and firewater to get unlocked and s-off again, if so desired.
There is no need to relock the bootloader if you are s-off, to do an ruu.
I've tried that before, probably more than once. It seems that when I'm in either fastboot or the RUU option " black screen silver HTC" it seems to freeze.
Has to be a driver issue with your pc, or a hardware issue with the phone. My guess is the drivers.
so i think i finally figured it out. long story short i uninstalled the drivers and then reinstalled and then plugged my phone in and tried it again. now i see the black screen and silver HTC with the green bar underneath it. not sure how long that stays on but i'm to scared to touch it
That is just a splash screen for ruu mode. Once in that mode, you use other fastboot cmds to flash the ruu ( fastboot flash zip nameoffile.zip ). Once the ruu finishes in the cmd window on your pc, it will still be at that screen untill you type ( fastboot reboot ).
d0m_ said:
Forgot to attache the picture, my bad.
I will try that now.
Click to expand...
Click to collapse
i have the same problem
View attachment 3237063
any solution?
Morgandust said:
i have the same problem
View attachment 3237063
any solution?
Click to expand...
Click to collapse
what all have you tried? did you try to uninstall and reinstall the driver? that is what did if for me.
d0m_ said:
what all have you tried? did you try to uninstall and reinstall the driver? that is what did if for me.
Click to expand...
Click to collapse
you remember the name of the driver? QHUSB_DLOAD?
Morgandust said:
you remember the name of the driver? QHUSB_DLOAD?
Click to expand...
Click to collapse
not off hand, just a quick google search should be able to do it. i think it was their sync software. then after it is installed only uninstall the sync manager.
Hello,
My HTC One will not unlock relocked bootloader using fastboot oem get_identifier_token
The error is as follows:
C:\adb>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.061s]
finished. total time: 0.062s
Please Help me my phone will also not take an RUU update from the EXE or Zip on sd card. It freezes on the recovery screen with red text warning. I am S-On, Re-locked and have no ROM installed at the moment.
Anyone?
lpcar04 said:
Hello,
My HTC One will not unlock relocked bootloader using fastboot oem get_identifier_token
The error is as follows:
C:\adb>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.061s]
finished. total time: 0.062s
Please Help me my phone will also not take an RUU update from the EXE or Zip on sd card. It freezes on the recovery screen with red text warning. I am S-On, Re-locked and have no ROM installed at the moment.
Click to expand...
Click to collapse
You need to go into developer options and check to allow OEM Unlocking.
ok is there any way you can help me to do that using adb as i do not have a rom installed currently and cannot get a RUU to flash completely
lpcar04 said:
ok is there any way you can help me to do that using adb as i do not have a rom installed currently and cannot get a RUU to flash completely
Click to expand...
Click to collapse
Sorry. I have no idea about that. It's a new "security" feature in 5.1 and others have been having the same problem and I don't know if anyone has been able to figure out how to unlock without running an ruu.
lpcar04 said:
ok is there any way you can help me to do that using adb as i do not have a rom installed currently and cannot get a RUU to flash completely
Click to expand...
Click to collapse
Do you have custom recovery or stock?
Does ADB work in recovery?
stock adb works in download and bootloader
stifilz said:
Do you have custom recovery or stock?
Does ADB work in recovery?
Click to expand...
Click to collapse
stock adb works in download and bootloader
jollywhitefoot said:
You need to go into developer options and check to allow OEM Unlocking.
Click to expand...
Click to collapse
Thanks given. S-off, I relocked to install update .19 and it wouldn't unlock after, with s-off I just installed twrp captain throwback and SU beta. Titanium backup pro wouldn't remove apps, and busy box pro wouldn't install. This fixed it.
Huge thanks.
On mine HTC one M9 i can not turn on, its som demo android 5.1. can i turn on som howe with adb comand?
Same here
moki_king said:
On mine HTC one M9 i can not turn on, its som demo android 5.1. can i turn on som howe with adb comand?
Click to expand...
Click to collapse
Same here bro, Please let me know if find any solution.
M9 softbricked??
So im in the same boad. I managed to lock myself out of my phone. Flashed stock recovery to update to android 6. NOW I'm stuck in bootloader. I can boot to recovery, download and oemRUU. When I try to run RUU i get the battery below 30% error but my phone says its 100% when I "power down" in recovery. when i try ADB SIDELOAD i get BL-unlock fail. runing unlocktoken the phone disply the warning andout unlocking the bootloader and i select YES then it display "set_unlock_bootloader_magic_type_fail" the phone reboots and the bootloader stays "re-locked"
I cant flash custom recovery or system without getting a "S-On" error or boot loader lock error. i can however flash "hosd". I tried the battery charge batt file but i don't get any readings running the command.
any help would be appreciated.
---------- Post added at 11:46 AM ---------- Previous post was at 11:42 AM ----------
jpwhre said:
Thanks given. S-off, I relocked to install update .19 and it wouldn't unlock after, with s-off I just installed twrp captain throwback and SU beta. Titanium backup pro wouldn't remove apps, and busy box pro wouldn't install. This fixed it.
Huge thanks.
Click to expand...
Click to collapse
how did you get S-Off without a working rom?
WarmYster said:
So im in the same boad. I managed to lock myself out of my phone. Flashed stock recovery to update to android 6. NOW I'm stuck in bootloader. I can boot to recovery, download and oemRUU. When I try to run RUU i get the battery below 30% error but my phone says its 100% when I "power down" in recovery. when i try ADB SIDELOAD i get BL-unlock fail. runing unlocktoken the phone disply the warning andout unlocking the bootloader and i select YES then it display "set_unlock_bootloader_magic_type_fail" the phone reboots and the bootloader stays "re-locked"
I cant flash custom recovery or system without getting a "S-On" error or boot loader lock error. i can however flash "hosd". I tried the battery charge batt file but i don't get any readings running the command.
any help would be appreciated.
---------- Post added at 11:46 AM ---------- Previous post was at 11:42 AM ----------
how did you get S-Off without a working rom?
Click to expand...
Click to collapse
I got s-off a week after it came out in April. The last lollipop update, htc moved the ability to unlock bootloader into developer options in phone and I didn't know, til I stumbled across this thread.
Fixed!!!
jpwhre said:
I got s-off a week after it came out in April. The last lollipop update, htc moved the ability to unlock bootloader into developer options in phone and I didn't know, til I stumbled across this thread.
Click to expand...
Click to collapse
O OK. brought my phone back from the graveyard. Found the correct RUU so all is good again.:fingers-crossed:
have you fix it? i have the same problem, please can someone help me? i don't know what i can do. my phone show me just the bootloader/download mode ecc i was s-off but i put s-on again and i have re locked my phone to update to android 6.0. please please help me.
jezzyna said:
have you fix it? i have the same problem, please can someone help me? i don't know what i can do. my phone show me just the bootloader/download mode ecc i was s-off but i put s-on again and i have re locked my phone to update to android 6.0. please please help me.
Click to expand...
Click to collapse
Make sure the RUU is the correct one matching the CID of your phone
change the name of the RUU to 0PJAIMG.ZIP and put it on SDCard then reboot to download mode
should be yellow text at bottom of screen (volume up to flash volume down to cancel)
(make sure SD card is fat32 and the 0PJAIMG zip file is the only thing on the card)
Have a look in the link for RUU
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Mr Troop said:
Make sure the RUU is the correct one matching the CID of your phone
change the name of the RUU to 0PJAIMG.ZIP and put it on SDCard then reboot to download mode
should be yellow text at bottom of screen (volume up to flash volume down to cancel)
(make sure SD card is fat32 and the 0PJAIMG zip file is the only thing on the card)
Have a look in the link for RUU
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
there was installed the 2.10.771.2 version so, i'm going to download this version?
i'm so confused i want to fix it asap i want my mobile back
jezzyna said:
there was installed the 2.10.771.2 version so, i'm going to download this version?
i'm so confused i want to fix it asap i want my mobile back
Click to expand...
Click to collapse
I found this one,third one in list 1.32.771.15
http://androidruu.com/?developer=M9
lpcar04 said:
Hello,
My HTC One will not unlock relocked bootloader using fastboot oem get_identifier_token
The error is as follows:
C:\adb>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.061s]
finished. total time: 0.062s
Please Help me my phone will also not take an RUU update from the EXE or Zip on sd card. It freezes on the recovery screen with red text warning. I am S-On, Re-locked and have no ROM installed at the moment.
Click to expand...
Click to collapse
hey bro any help yet? im currently s-on, RELOCKED and running stock rom. i've been trying to get the marshmallow update but i think im stuck now.
Suavie103 said:
hey bro any help yet? im currently s-on, RELOCKED and running stock rom. i've been trying to get the marshmallow update but i think im stuck now.
Click to expand...
Click to collapse
You have to enable developers options Easter egg. Go to settings/about/software information/more and keep tapping build number. You will get a toast notification telling you to tap "X#" times to enable until you see "developer mode (blah blah blah)" Go back to settings and you'll see developers options. Open it and check "allow unlock bootloader"
If you can't get marshmallow, reboot to bootloader. Check software status at top. If it says modified you won't take OTA. Back up your device internal storage to pc and flash lolipop ruu.exe and if that doesn't take, find stock ruu thread and put lolipop on sd card and reboot to download mode. This will reset status to "official" and allow you to take both parts of OTA for marshmallow. This method will wipe your entire device including internal storage (thus need for backup to pc prior)
HTC backup has been discontinued in marshmallow. You can restore from, but Google picks up backup on marshmallow.
Hi guys, I hope someone brighter than me has an answer to following:
I ran HTC 10 with systemless root and HTC unlocked bootloader and wanted to try to take Nougat OTA.
This failed with red exclamation mark, I then flashed stock recovery and relocked the bootloader and tried the Nougat RUU downloadable from HTC.
This then worked and my phone is on Nougat alright, but now I want my bootloader unlocked again for twrp and root.
Trying the HTC unlock method results in this:
C:\android-tools>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
Doesn't work anymore??
So, I thought let's try Sunshine.apk again, it worked great on my M8, but this seem to force stop on Nougat when it tries to gain temproot.
I am lost... Anyone who knows a solution please?
clubbtraxx said:
Hi guys, I hope someone brighter than me has an answer to following:
I ran HTC 10 with systemless root and HTC unlocked bootloader and wanted to try to take Nougat OTA.
This failed with red exclamation mark, I then flashed stock recovery and relocked the bootloader and tried the Nougat RUU downloadable from HTC.
This then worked and my phone is on Nougat alright, but now I want my bootloader unlocked again for twrp and root.
Trying the HTC unlock method results in this:
C:\android-tools>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
Doesn't work anymore??
So, I thought let's try Sunshine.apk again, it worked great on my M8, but this seem to force stop on Nougat when it tries to gain temproot.
I am lost... Anyone who knows a solution please?
Click to expand...
Click to collapse
Did you try that command from bootloader or from download mode??
clubbtraxx said:
Hi guys, I hope someone brighter than me has an answer to following:
I ran HTC 10 with systemless root and HTC unlocked bootloader and wanted to try to take Nougat OTA.
This failed with red exclamation mark, I then flashed stock recovery and relocked the bootloader and tried the Nougat RUU downloadable from HTC.
This then worked and my phone is on Nougat alright, but now I want my bootloader unlocked again for twrp and root.
Trying the HTC unlock method results in this:
C:\android-tools>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
Doesn't work anymore??
So, I thought let's try Sunshine.apk again, it worked great on my M8, but this seem to force stop on Nougat when it tries to gain temproot.
I am lost... Anyone who knows a solution please?
Click to expand...
Click to collapse
I have not tried it, but I once read that you should insert the normal command when you unlocked it the first time, ie with the $ fastboot flash unlocktoken Unlock_code.bin and it happens the same way, if you do not have the file and you are looking for the OEM ID with $ fastboot oem get_identifier_token, you may need to activate the developer options to unlock OEM and that is your problem.
Sorry for the translated English
Tech_Savvy said:
Did you try that command from bootloader or from download mode??
Click to expand...
Click to collapse
From bootloader, that's the way I was used to and it has always worked that way anyways.
Are you saying it should be done from download mode?
Qbraham said:
I have not tried it, but I once read that you should insert the normal command when you unlocked it the first time, ie with the $ fastboot flash unlocktoken Unlock_code.bin and it happens the same way, if you do not have the file and you are looking for the OEM ID with $ fastboot oem get_identifier_token, you may need to activate the developer options to unlock OEM and that is your problem.
Sorry for the translated English
Click to expand...
Click to collapse
I indeed tried with the original Unlock_code.bin file first, but it refuses to do it complaining about 'not being able to flash that partition with S-on'...
I did enable in developer options OEM unlock checkbox also. Still no joy on current Nougat ROM.
clubbtraxx said:
From bootloader, that's the way I was used to and it has always worked that way anyways.
Are you saying it should be done from download mode?
Click to expand...
Click to collapse
yup it shud be done from download mode
Tech_Savvy said:
yup it shud be done from download mode
Click to expand...
Click to collapse
Thanks! I don't know why I didn't try that myself but it indeed works as expected from there.
Back to unlocked and setting up once again
clubbtraxx said:
Thanks! I don't know why I didn't try that myself but it indeed works as expected from there.
Back to unlocked and setting up once again
Click to expand...
Click to collapse
Congratulations on getting it, I have a question regarding, how to unlock the unlock from Download Mode? Is the cell phone returning the first time it is unlocked?
clubbtraxx said:
Hi guys, I hope someone brighter than me has an answer to following:
I ran HTC 10 with systemless root and HTC unlocked bootloader and wanted to try to take Nougat OTA.
This failed with red exclamation mark, I then flashed stock recovery and relocked the bootloader and tried the Nougat RUU downloadable from HTC.
This then worked and my phone is on Nougat alright, but now I want my bootloader unlocked again for twrp and root.
Trying the HTC unlock method results in this:
C:\android-tools>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
Doesn't work anymore??
So, I thought let's try Sunshine.apk again, it worked great on my M8, but this seem to force stop on Nougat when it tries to gain temproot.
I am lost... Anyone who knows a solution please?
Click to expand...
Click to collapse
Kind of an OT question, but how did you relock your HTC 10? Was it as simple as typing "fastboot oem lock" in fastboot?
tibere86 said:
Kind of an OT question, but how did you relock your HTC 10? Was it as simple as typing "fastboot oem lock" in fastboot?
Click to expand...
Click to collapse
Test in download mode, if it does not work in fastboot
Just brought a HTC one M9 off eBay, its in excellent cosmetic condition, i'll get the basics out of the way quickly, it is already S-OFF, super CID, 401 WWE edition firmware, but the bootloader is locked, now I am very used to HTC one M7s and M8, but this download mode rubbish is all new to me, the problem is, when I power on the phone, instead of it booting normally, it just loops into the bootloader, ive uploaded some picts for you too see.
now when I enter download mode, there is no fastboot in the available options on the phone, so I cant issue any fastboot commands, like to unlock the bootloader, do I have any other options ? I also have access to the basic recovery mode, the HTC one, not TWRP or anything like that.
Also, does anyone know where I can find the 4.xx.401.x RUU for these phones, its not on the HTC website ?
Please help, or is this a lost phone and should I just send it back ?
Seanie280672 said:
Just brought a HTC one M9 off eBay, its in excellent cosmetic condition, i'll get the basics out of the way quickly, it is already S-OFF, super CID, 401 WWE edition firmware, but the bootloader is locked, now I am very used to HTC one M7s and M8, but this download mode rubbish is all new to me, the problem is, when I power on the phone, instead of it booting normally, it just loops into the bootloader, ive uploaded some picts for you too see.
now when I enter download mode, there is no fastboot in the available options on the phone, so I cant issue any fastboot commands, like to unlock the bootloader, do I have any other options ? I also have access to the basic recovery mode, the HTC one, not TWRP or anything like that.
Also, does anyone know where I can find the 4.xx.401.x RUU for these phones, its not on the HTC website ?
Please help, or is this a lost phone and should I just send it back ?
Click to expand...
Click to collapse
For fastboot, treat download mode as fastboot. If you're having trouble with using download mode to flash something or boot something, use bootloader mode. For more details about RUUS, unlocking the bootloader, and using S-OFF to your advantage, take a look at the read me thread stickied at the top of the General thread.
(Note: You may or may not find RUUS for your phone, as they got leaked somehow.)
Sent from my HTC One M9 using Tapatalk
lazyguyMC said:
For fastboot, treat download mode as fastboot. If you're having trouble with using download mode to flash something or boot something, use bootloader mode. For more details about RUUS, unlocking the bootloader, and using S-OFF to your advantage, take a look at the read me thread stickied at the top of the General thread.
(Note: You may or may not find RUUS for your phone, as they got leaked somehow.)
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
when i type fastboot devices in download mode, it doesnt list the serial number
Seanie280672 said:
when i type fastboot devices in download mode, it doesnt list the serial number
Click to expand...
Click to collapse
Try doing the same in bootloader mode, and check your drivers and executables.
The easiest way to get drivers is to install HTC Sync Manager and then immediately uninstall it.
Sent from my HTC One M9 using Tapatalk
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
lazyguyMC said:
Try doing the same in bootloader mode, and check your drivers and executables.
The easiest way to get drivers is to install HTC Sync Manager and then immediately uninstall it.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Also, looking at the CID, the seller probably tried to flash stock firmware and locked the bootloader. You'll need to clean up after him.
Sent from my HTC One M9 using Tapatalk
lazyguyMC said:
Try doing the same in bootloader mode, and check your drivers and executables.
The easiest way to get drivers is to install HTC Sync Manager and then immediately uninstall it.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
thanks, ive installed htc sync manager now, also, my adb and fastboot maybe out of date, im using the 15 seconds install one, but had another look at it and saw its from 2013, do you know where i can find the latest versions ?, ive been using a Samsung for the last year or so which I absolutely hated, so went back to HTC, so you understand if im a little out of touch.
https://developer.android.com/studio/releases/platform-tools.html#download
You're welcome.
lazyguyMC said:
https://developer.android.com/studio/releases/platform-tools.html#download
You're welcome.
Click to expand...
Click to collapse
Thanks again
also, yes thats what im thinking too, they s-off'd the phone and super CID'd the phone, then locked the bloody bootloader, on a plus note, I just got a result in bootloader mode using fastboot devices command, gave me the serial number, but when using the fastboot oem get_identifier_token command it just gave me FAILED: (remote: unknown command), going to try in download mode now instead.
UPDATE: just tried in download mode too, now that also gave me a result when I typed fastboot devices, gave me my serial number, but when trying to get the token ID I got:
C:\adb>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.065s]
finished. total time: 0.065s
Seanie280672 said:
Thanks again
also, yes thats what im thinking too, they s-off'd the phone and super CID'd the phone, then locked the bloody bootloader, on a plus note, I just got a result in bootloader mode using fastboot devices command, gave me the serial number, but when using the fastboot oem get_identifier_token command it just gave me FAILED: (remote: unknown command), going to try in download mode now instead.
Click to expand...
Click to collapse
Remember to read the readme thread from top to bottom. Your questions will probably be answered there.
lazyguyMC said:
Remember to read the readme thread from top to bottom. Your questions will probably be answered there.
Click to expand...
Click to collapse
Oh well, wont even boot into download mode anymore, tried to flash the developer edition RUU, but says the battery is below 30%, so when I power down the phone to charge it, as soon as I plug the charger in, its booting itself back to the bootloader, not sure if its actually charging whilst its in this more, but id say the phone is pretty much fubar.
Seanie280672 said:
Oh well, wont even boot into download mode anymore, tried to flash the developer edition RUU, but says the battery is below 30%, so when I power down the phone to charge it, as soon as I plug the charger in, its booting itself back to the bootloader, not sure if its actually charging whilst its in this more, but id say the phone is pretty much fubar.
Click to expand...
Click to collapse
Just make sure not to throw it away yet. Someone will eventually help you.
Sent from my HTC One M9 using Tapatalk
Just a stab in the dark but did you go into developer options and check oem unlocking?
As mentioned before, I can only suggest you to read the ReadMe thread. Of course, you can't flash a dev edition RUU in the current state. You're using the wrong MID.
Pfaffinator said:
Just a stab in the dark but did you go into developer options and check oem unlocking?
Click to expand...
Click to collapse
I only got the phone yesterday, and never been able yet to boot to a working rom yet, so couldnt check it, sent the phone back to her now for a full refund, sod it, cant be bothered with it, brought another working one instead, will s-off it, unlock it etc the proper way when I get it tomorrow.
Flippy498 said:
As mentioned before, I can only suggest you to read the ReadMe thread. Of course, you can't flash a dev edition RUU in the current state. You're using the wrong MID.
Click to expand...
Click to collapse
I couldnt even get into download mode any longer after I reset the phone and tried to reboot back to download mode, I got as far as the black screen with the silver HTC logo and then it would just boot back to the bootloader, couldnt even charge the phone, everytime I powered off and plugged in the charger it would switch itself on, and the same for recovery, so just gave up and sent it back to her.