Related
Hello guys,
I have S-OFF, supercid, relocked bootloader phone
First I installed Firmware package from 2.17.401.1 RUU sucressfully my terminal quoted and then after reboot My phone was not reacting to any tipping on the screen. I only reached the screen where it demands the pin to type in.
So I flashed it again with firmware.zip from 1.29.401.12. Flash sucessfully (terminal quoted) and now it rebooted to the htc one logo and nothing else happens. I even cannot turn it off. Please help.
Update: I managed to reboot it but it is not reacting when i want to put in my PIN
Put the device under direct light (perhaps like a bulb) and press the power and volume down buttons together until the device reboots. While it is under direct light, do not cover the light sensors (on the left of the upper speaker grill) with your hand.
TarekElsakka said:
Put the device under direct light (perhaps like a bulb) and press the power and volume down buttons together until the device reboots. While it is under direct light, do not cover the light sensors (on the left of the upper speaker grill) with your hand.
Click to expand...
Click to collapse
ok i now restarted it but the touchscreen does not react when it asks me to put in the PIN
Reflash ROM..
Sent from my HTC One
Sindroid said:
Reflash ROM..
Sent from my HTC One
Click to expand...
Click to collapse
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Exxorzist said:
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Click to expand...
Click to collapse
I've had the same issue. Which rom do you use? CM wasn't working for me, so I had to flash Sense rom like ARHD 11 or Trickdroid 7.5
I also flashed the older firmware.zip and still no touch responsiveness. You will also have to flash a newer cwm touch recovery if you are using it, helps navigating through aroma http://goo.im/devs/Flyhalf205/M7/Recovery/recovery-clockwork-touch-6.0.3.2-m7.img
Exxorzist said:
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Click to expand...
Click to collapse
You need to flash this firmware: http://www.androidrevolution.nl/downloader/download.php?file=2.17.401.1-custom.zip again, and then flash the custom recovery stated above this post. Next, flash the latest Android Revolution which is on the newest base which other roms don't have yet. This should fix your issue. CM roms cannot be used by your device in its current state, as the touch drivers aren't compatible. You must use a Sense rom
MacHackz said:
You need to flash this firmware: http://www.androidrevolution.nl/downloader/download.php?file=2.17.401.1-custom.zip again, and then flash the custom recovery stated above this post. Next, flash the latest Android Revolution which is on the newest base which other roms don't have yet. This should fix your issue. CM roms cannot be used by your device in its current state, as the touch drivers aren't compatible. You must use a Sense rom
Click to expand...
Click to collapse
I flashed the firmware again sucessfully to 2.17.401.1
Since 2 days my Bootloader is relocked again but I am S-OFF. When I want to flash custom recovery I do have to unlock it again? How do I do that because I am still not able to use touchscreen and type in PIN?
George_Mn said:
I've had the same issue. Which rom do you use? CM wasn't working for me, so I had to flash Sense rom like ARHD 11 or Trickdroid 7.5
I also flashed the older firmware.zip and still no touch responsiveness. You will also have to flash a newer cwm touch recovery if you are using it, helps navigating through aroma http://goo.im/devs/Flyhalf205/M7/Recovery/recovery-clockwork-touch-6.0.3.2-m7.img
Click to expand...
Click to collapse
Exxorzist said:
I flashed the firmware again sucessfully to 2.17.401.1
Since 2 days my Bootloader is relocked again but I am S-OFF. When I want to flash custom recovery I do have to unlock it again? How do I do that because I am still not able to use touchscreen and type in PIN?
Click to expand...
Click to collapse
type fastboot oem flash unlocktoken unlock_code.bin
MacHackz said:
type fastboot oem flash unlocktoken unlock_code.bin
Click to expand...
Click to collapse
Thanks. I unlocked it and flashed the custom recovery
./fastboot-mac flash recovery recovery.img
sending 'recovery' (7422 KB)... OKAY
writing 'recovery'... OKAY
Then i rebootet it and touchscreen is still not reacting. Shall I now flash the revolution hd rom?
Exxorzist said:
Thanks. I unlocked it and flashed the custom recovery
./fastboot-mac flash recovery recovery.img
sending 'recovery' (7422 KB)... OKAY
writing 'recovery'... OKAY
Then i rebootet it and touchscreen is still not reacting. Shall I now flash the revolution hd rom?
Click to expand...
Click to collapse
Does touchscreen work in recovery mode?
What ROM do you currently have?
MacHackz said:
Does touchscreen work in recovery mode?
What ROM do you currently have?
Click to expand...
Click to collapse
Yes touchscreen works in recovery. I am at the moment not using any rom. I have bought a branded phone and all I did was giving it S-OFF, unlock bootloader, supercid, root.
And now after I flashed firmware 2.17, i simply want to put a rom on it like Revolution HD 11
Exxorzist said:
Yes touchscreen works in recovery. I am at the moment not using any rom. I have bought a branded phone and all I did was giving it S-OFF, unlock bootloader, supercid, root.
And now after I flashed firmware 2.17, i simply want to put a rom on it like Revolution HD 11
Click to expand...
Click to collapse
Flash Android Revolution 11 and it should work! :fingers-crossed:
MacHackz said:
Flash Android Revolution 11 and it should work! :fingers-crossed:
Click to expand...
Click to collapse
Stupid question. How do I get the zip file onto my Phone? Because I cannot type in my pin and then connect it as usual and pulling it via Android File Transfer over to my phone.
Exxorzist said:
Stupid question. How do I get the zip file onto my Phone? Because I cannot type in my pin and then connect it as usual and pulling it via Android File Transfer over to my phone.
Click to expand...
Click to collapse
Check my ADB push guide in my sig, jump to step 3
No need to relock bootloader when S-Off. If you upgrade firmware. If you upgrading to 2.17 f/w u need to flash new recovery as well.
Use sideload in recovery to reflash ROM.
Sent from my HTC One
MacHackz said:
Check my ADB push guide in my sig, jump to step 3
Click to expand...
Click to collapse
You are my hero!!!!!
Everything works great. Is there also the camera update included that was released by HTC in 1.29 because before I had 1.28.
Exxorzist said:
You are my hero!!!!!
Everything works great. Is there also the camera update included that was released by HTC in 1.29 because before I had 1.28.
Click to expand...
Click to collapse
It's all included You can also check the modded camera apk in my signature which allows you to take photos and focus using your volume buttons
Glad it worked
Thank you so much for this tip I thought I was SOL when it went into the WSOD and I couldn't turn it off.
Im really struggling to carry out an unroot on both my HTC one and S3. I want to sell the devices but need to return them to standard rom.
I have looked and read so many differnt threads that I'm totally confused about which method to use and which files to use.
My HTC is rooted with a TEAM recovery, I've looked at the bootloader and it tells me its s-on. All I want to do is return to stock O/S so the phone can update to the latests release. I don't need any of the settings keeping, infact it's best for it to be completely clean.
Is there an easy to follow guide I can use that points me to all the files I need etc?
If anyone can help me out I would very much appreciate it.
thanks all.
uktivo said:
Im really struggling to carry out an unroot on both my HTC one and S3. I want to sell the devices but need to return them to standard rom.
I have looked and read so many differnt threads that I'm totally confused about which method to use and which files to use.
My HTC is rooted with a TEAM recovery, I've looked at the bootloader and it tells me its s-on. All I want to do is return to stock O/S so the phone can update to the latests release. I don't need any of the settings keeping, infact it's best for it to be completely clean.
Is there an easy to follow guide I can use that points me to all the files I need etc?
If anyone can help me out I would very much appreciate it.
thanks all.
Click to expand...
Click to collapse
Did you read this http://forum.xda-developers.com/showthread.php?t=2358738 this is the guide you are looking for.... and this is the 2nd sticky on this forum....
and btw you should ask your question in the q&a, help and troubleshooting forum next time, not in general forum
Apologies for the wrong position of posting.. I have read this sticky but there are lots of conflicting information in there. Perhaps my geekness is just not what it supposed to be.
Sent from my Z30 using Tapatalk
Sorry hit enter to quickly.
I think in general I'm unsure of some of the terminology used. It also mentions about certain firmware not having touch panel working after unroot etc. So as a non geek type, it does sort of scare you into not doing anything at all. I've looked on YouTube and there are loads of video tutorials but again, most of the links to the correct ruu are broken or old.
Hence my question. Is there an updated thread giving noob step by step instructions.. hope that makes sense?
Sent from my Z30 using Tapatalk
Reboot your phone in bootloader, Select fasboot, then connect phone to pc via usb. Go to your fastboot/adb folder of your computer and start a cmd prompt from there. Type "fastboot getvar all" copy paste info here. Dont paste imei and s/n.
Sent from my HTC One using xda app-developers app
alray said:
Reboot your phone in bootloader, Select fasboot, then connect phone to pc via usb. Go to your fastboot/adb folder of your computer and start a cmd prompt from there. Type "fastboot getvar all" copy paste info here. Dont paste imei and s/n.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
That alone had helped. I completely forgot you need to start the command prompt from the adb folder. I've been trying to navigate to it with little success
Sent from my Z30 using Tapatalk
alray said:
Reboot your phone in bootloader, Select fasboot, then connect phone to pc via usb. Go to your fastboot/adb folder of your computer and start a cmd prompt from there. Type "fastboot getvar all" copy paste info here. Dont paste imei and s/n.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for your support so far. Please see attached. If you could point me in the right direction please that would be greatly appreciated.
UPDATE.
I've gained s-off using revone system and I believe I've found the right RUU for my firmware 1.28.401.7 which is this one:
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
How do i know flash this ruu.zip file to the phone? I've tried the steps in the mentioned thread above but keep getting errors.
uktivo said:
Thanks for your support so far. Please see attached. If you could point me in the right direction please that would be greatly appreciated.
UPDATE.
I've gained s-off using revone system and I believe I've found the right RUU for my firmware 1.28.401.7 which is this one:
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
How do i know flash this ruu.zip file to the phone? I've tried the steps in the mentioned thread above but keep getting errors.
Click to expand...
Click to collapse
Now that you are s-off:
1 -I would recommend you tu use the .EXE RUU and not the .ZIP RUU. Will be much easier for you :
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe/ just place the .exe on your desktop
2- put your phone back in fastboot mode (reboot using power and vol -, select fastboot, connect to usb computer)
3- open a cmd prompt from your adb/fastboot folder
4- change your cid to supercid by pushing this command:
Code:
fastboot oem writecid 11111111
5- check that your cid changed properly:
Code:
fastboot oem readcid
it should reply something like this:
Code:
(bootloader) cid: 11111111
OKAY [ 0.010s]
finished. total time: 0.011s
6- keep phone connected to pc and reboot it, check you have a good battery charge. launch the ruu.exe and follow instruction from the utility.
7- now your phone is back to stock, you are not rooted anymore and your bootloader is locked. you need the change back your cid to HTC__001 if you want to receive OTA updates.
-put your phone back in fastboot mode (reboot using power + vol -, select fastboot, connect to usb computer)
-open a cmd prompt from your adb/fastboot folder
-
Code:
fastboot oem writecid HTC__001
-check that your cid changed properly:
Code:
fastboot oem readcid
it should reply something like this:
Code:
(bootloader) cid: HTC__001
OKAY [ 0.010s]
finished. total time: 0.011s
8- boot your phone normally, go trough the setup procedure, then download and install all ota updates.
9- factory reset your phone
10- you are rdy to sell it, its now 100% stock, updated and s-off (dont go back to s-on!)
alray said:
Now that you are s-off:
1 -I would recommend you tu use the .EXE RUU and not the .ZIP RUU. Will be much easier for you :
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe/ just place the .exe on your desktop
2- put your phone back in fastboot mode (reboot using power and vol -, select fastboot, connect to usb computer)
3- open a cmd prompt from your adb/fastboot folder
4- change your cid to supercid by pushing this command:
Code:
fastboot oem writecid 11111111
5- check that your cid changed properly:
Code:
fastboot oem readcid
it should reply something like this:
Code:
(bootloader) cid: 11111111
OKAY [ 0.010s]
finished. total time: 0.011s
6- keep phone connected to pc and reboot it, check you have a good battery charge. launch the ruu.exe and follow instruction from the utility.
7- now your phone is back to stock, you are not rooted anymore and your bootloader is locked. you need the change back your cid to HTC__001 if you want to receive OTA updates.
-put your phone back in fastboot mode (reboot using power + vol -, select fastboot, connect to usb computer)
-open a cmd prompt from your adb/fastboot folder
-
Code:
fastboot oem writecid HTC__001
-check that your cid changed properly:
Code:
fastboot oem readcid
it should reply something like this:
Code:
(bootloader) cid: HTC__001
OKAY [ 0.010s]
finished. total time: 0.011s
8- boot your phone normally, go trough the setup procedure, then download and install all ota updates.
9- factory reset your phone
10- you are rdy to sell it, its now 100% stock, updated and s-off (dont go back to s-on!)
Click to expand...
Click to collapse
Could not have done this with out your help.. VERY MUCH appreciated.
uktivo said:
Could not have done this with out your help.. VERY MUCH appreciated.
Click to expand...
Click to collapse
No problem, i'm just doing what somebody else here on xda did for me a couple weeks ago.
alray said:
No problem, i'm just doing what somebody else here on xda did for me a couple weeks ago.
Click to expand...
Click to collapse
Only me again. lol.
I'm all updated now thanks. BUT. I noticed my recovery has now gone. I used to use team recovery but I'm happy to install any (easiest). Don't suppose you know how to do this please?
thanks again.
uktivo said:
I noticed my recovery has now gone. I used to use team recovery but I'm happy to install any (easiest).
Click to expand...
Click to collapse
Your recovery isnt gone, The ruu process replaced your custom twrp recovery with the stock recovery of htc. If you want to re-install twrp recovery you have to re-unlock your bootloader trough htcdev.com and then download the twrp.zip and flash it to the recovery partition of your phone.
uktivo said:
All I want to do is return to stock O/S so the phone can update to the latests release. I don't need any of the settings keeping, infact it's best for it to be completely clean.
Click to expand...
Click to collapse
With a custom recovery (like twrp), you will NOT be stock and you will NOT receive future OTA updates. (you will see them but you won't be able to install them because you need stock recovery to install ota)
if you still want to install twrp for some reasons follow those steps:
1- re-unlock your bootloader trough HTCdev.com
refer to this xda video tutorial : http://www.youtube.com/watch?v=xuIq0gmYpFA
2- download lastest version of twrp (openrecovery-twrp-2.6.3.0-m7.img) recovery: http://goo.im/devs/OpenRecovery/m7/
3- place the .img file inside your adb/fastboot folder of your computer
4- reboot phone in bootloader, then select fastboot and connect usb cable
5- open cmd prompt from you fastboot folder
6- type this command to flash twrp:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
7- type this command to reboot into bootloader:
Code:
fastboot reboot bootloader
8- now you can enter the custom recovery
alray said:
Your recovery isnt gone, The ruu process replaced your custom twrp recovery with the stock recovery of htc. If you want to re-install twrp recovery you have to re-unlock your bootloader trough htcdev.com and then download the twrp.zip and flash it to the recovery partition of your phone.
With a custom recovery (like twrp), you will NOT be stock and you will NOT receive future OTA updates. (you will see them but you won't be able to install them because you need stock recovery to install ota)
if you still want to install twrp for some reasons follow those steps:
1- re-unlock your bootloader trough HTCdev.com
refer to this xda video tutorial : http://www.youtube.com/watch?v=xuIq0gmYpFA
2- download lastest version of twrp (openrecovery-twrp-2.6.3.0-m7.img) recovery: http://goo.im/devs/OpenRecovery/m7/
3- place the .img file inside your adb/fastboot folder of your computer
4- reboot phone in bootloader, then select fastboot and connect usb cable
5- open cmd prompt from you fastboot folder
6- type this command to flash twrp:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
7- type this command to reboot into bootloader:
Code:
fastboot reboot bootloader
8- now you can enter the custom recovery
Click to expand...
Click to collapse
Sorry for my delayed thanks but I've been away on business for the last few days and not had chance to catch up on this thread. Thanks again.
Sent from my Z30 using Tapatalk
I want to return to stock so I can take an OTA. I am currently running Sprint 4.3, rooted, unlocked bootloader, S-ON, software version 3.04.651.2.
I have been reading up on the proper way to return to stock and just want to double check that I have the right information before i break something.
1. Download 3.04.651.2 RUU (or do I want 4.06.651.4 or 4.06.651.2?)
2. USB debugging turned on
3. nandriod
4. go into fastboot
5. Connect phone to computer and go to Andriod SDK folder platform-tools and open a command window
6. type fastboot oem lock in the command window
7. go back to fastboot and run the RUU (how exactly do I run the RUU?)
8. Am I done now? Will these steps give me the stock rom, locked bootloader and stock recovery?
is this how I flash the RUU from the command window?
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip (if filename = firmware.zip)
Fastboot reboot
Thanks for the clarification.
Kev1jm2 said:
I want to return to stock so I can take an OTA. I am currently running Sprint 4.3, rooted, unlocked bootloader, S-ON, software version 3.04.651.2.
I have been reading up on the proper way to return to stock and just want to double check that I have the right information before i break something.
1. Download 3.04.651.2 RUU (or do I want 4.06.651.4 or 4.06.651.2?)
2. USB debugging turned on
3. nandriod
4. go into fastboot
5. Connect phone to computer and go to Andriod SDK folder platform-tools and open a command window
6. type fastboot oem lock in the command window
7. go back to fastboot and run the RUU (how exactly do I run the RUU?)
8. Am I done now? Will these steps give me the stock rom, locked bootloader and stock recovery?
is this how I flash the RUU from the command window?
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip (if filename = firmware.zip)
Fastboot reboot
Thanks for the clarification.
Click to expand...
Click to collapse
If you have a (S-ON) device you can go to OMJ's thread and run the RUU.exe for instructions:
http://forum.xda-developers.com/showthread.php?t=2658910
read the instructions under the image on the page...
If you want to flash the modified firmware you need (S-OFF), then you would follow these instructions:
I downloaded 4.06.651.4..
then renamed 4.06.651.4.zip to "firmware.zip"..
then moved firmware.zip to 'where-ever fastboot & adb are installed'..
then open command prompt in that folder..
then rebooted to bootloader..
plug phone through USB port, phone should say FASTBOOT USB
cmd: "fastboot oem rebootRUU" (without quotes of course)
cmd: "fastboot flash zip firmware.zip"
cmd: "fastboot reboot" (to reboot)
Hope this helps!
predator1584 said:
If you have a (S-ON) device you can go to OMJ's thread and run the RUU.exe for instructions:
http://forum.xda-developers.com/showthread.php?t=2658910
read the instructions under the image on the page...
If you want to flash the modified firmware you need (S-OFF), then you would follow these instructions:
I downloaded 4.06.651.4..
then renamed 4.06.651.4.zip to "firmware.zip"..
then moved firmware.zip to 'where-ever fastboot & adb are installed'..
then open command prompt in that folder..
then rebooted to bootloader..
plug phone through USB port, phone should say FASTBOOT USB
cmd: "fastboot oem rebootRUU" (without quotes of course)
cmd: "fastboot flash zip firmware.zip"
cmd: "fastboot reboot" (to reboot)
Hope this helps!
Click to expand...
Click to collapse
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Kev1jm2 said:
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Click to expand...
Click to collapse
The 4.06.651.4 RUU is the same as taking the OTA but...it will wipe your device
I would suggest getting s-off before you go any further it will save you headaches down the road.
Kev1jm2 said:
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Click to expand...
Click to collapse
no luck with the s-off way. got a file size error in cmd. trying the s-on version now.
Nope, got another error. Something about using an incorrect ruu. Bootloader is locked now though...And now its unlocked again. going to try OMJ's tool with the 3.04.651.2 ruu
OMJ's tool worked when my software version matched the tool's version. getting the OTA now. Apparently you cant jump software versions.
Thanks for your help.
Kev1jm2 said:
no luck with the s-off way. got a file size error in cmd. trying the s-on version now.
Nope, got another error. Something about using an incorrect ruu. Bootloader is locked now though...And now its unlocked again. going to try OMJ's tool with the 3.04.651.2 ruu
OMJ's tool worked when my software version matched the tool's version. getting the OTA now. Apparently you cant jump software versions.
Thanks for your help.
Click to expand...
Click to collapse
I did not have to relock my phone to RUU it for a repair at HTC. If you run into trouble just reapply your token.bin file to re unlock dev mode and try again. I agree though S-OFF is the way to go if you can sort it out.
I've accidentally erased everything on my HTC One, including the ROM I had on there and the ROM install file. I am now stuck in the Bootloader screen and only options I have are to enter TWRP v2.6.3.3. Is there a way that I can flash a ROM via USB in the Bootloader? I've tried resetting my phone and it comes up with the HTC logo on the white screen and won't boot.
return to stock rom
Chaos Water2 said:
I've accidentally erased everything on my HTC One, including the ROM I had on there and the ROM install file. I am now stuck in the Bootloader screen and only options I have are to enter TWRP v2.6.3.3. Is there a way that I can flash a ROM via USB in the Bootloader? I've tried resetting my phone and it comes up with the HTC logo on the white screen and won't boot.
Click to expand...
Click to collapse
Restart from scratch find the ruu.exe for your phone make sure it has the right specs of your phone (android,sense,and service provider) once found follow these instructions
1.) Go to Fastboot
2.) Run the commands
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
3.) Run the RUU
The first command locks your bootloader (allowing RUU), the third command allows the RUU to run on your phone without having to actually boot all the way (normally it just boots into this screen for you).
This will put you back to ur stock Rom when rooting again make sure to make backups of everything or you will have same problem again
Make sure you have all the updated drivers for your computer
Chaos Water2 said:
I've accidentally erased everything on my HTC One, including the ROM I had on there and the ROM install file. I am now stuck in the Bootloader screen and only options I have are to enter TWRP v2.6.3.3. Is there a way that I can flash a ROM via USB in the Bootloader? I've tried resetting my phone and it comes up with the HTC logo on the white screen and won't boot.
Click to expand...
Click to collapse
adb works in custom recovery, you can push, sideload, or OTG a ROM to your phone,
check the Frequently Asked Question sticky page 3
smokeytime420 said:
Restart from scratch find the ruu.exe for your phone make sure it has the right specs of your phone (android,sense,and service provider) once found follow these instructions
1.) Go to Fastboot
2.) Run the commands
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
3.) Run the RUU
The first command locks your bootloader (allowing RUU), the third command allows the RUU to run on your phone without having to actually boot all the way (normally it just boots into this screen for you).
This will put you back to ur stock Rom when rooting again make sure to make backups of everything or you will have same problem again
Make sure you have all the updated drivers for your computer
Click to expand...
Click to collapse
A RUU.exe file only requires the bootloader locked if S-ON. When the bootloader is locked, the RUU is executed with a double click in Windows. There is no need to do the other steps in 2, they are only needed if the RUU is a zip file. Here are the steps for flashing RUU.zip:
In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
that is true
majmoz said:
A RUU.exe file only requires the bootloader locked if S-ON. When the bootloader is locked, the RUU is executed with a double click in Windows. There is no need to do the other steps in 2, they are only needed if the RUU is a zip file. Here are the steps for flashing RUU.zip:
In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
Click to expand...
Click to collapse
That is true method is similar but this is how I got my phone to return to stock be for I could go anywhere else I tryed reflashing a recovery it didn't take I even tryed flashing the ruu.zip through fastboot it always failed on me since I couldn't go any further than that I searched other methods of flashing ruu that's what I came across and it worked for me also if you have s-off this usually turns it back on it did for me on step 2 not all of those steps are needed but the last one is what gets the phone ready to receive the info from the ruu.exe being run on a computer
hello guys. i've recently bought a M7_UL (i believe it's the unlocked, international version) that has S-OFF with locked bootloader. some people say you still can flash recovery since you're S-OFF, others, that even if when S-OFF, you still have to unlock bootloader in order to flash a recovery. well, i can't do none of these. everything is properly installed (device drivers, most recent Mini ADB and Fastboot and TWRP) but some commands such as "adb devices" (though changing "adb" to "fastboot" actually shows my device) and "fastboot flash recovery xxx.img", simply doesn't work. i've also tried the HTCdev method but "fastboot oem get_identifier_token" command gives me nothing. also tried this tutorial here --> https://forum.xda-developers.com/showthread.php?t=2470340 but the cmd doesn't even recognize this "echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 " line. what am i doing wrong?
i really didn't want to create this topic and did quite a research, but every tutorial i've found so far didn't work for me. heeelppp :crying:
manofawker said:
hello guys. i've recently bought a M7_UL (i believe it's the unlocked, international version) that has S-OFF with locked bootloader. some people say you still can flash recovery since you're S-OFF, others, that even if when S-OFF, you still have to unlock bootloader in order to flash a recovery. well, i can't do none of these. everything is properly installed (device drivers, most recent Mini ADB and Fastboot and TWRP) but some commands such as "adb devices" (though changing "adb" to "fastboot" actually shows my device) and "fastboot flash recovery xxx.img", simply doesn't work. i've also tried the HTCdev method but "fastboot oem get_identifier_token" command gives me nothing. also tried this tutorial here --> https://forum.xda-developers.com/showthread.php?t=2470340 but the cmd doesn't even recognize this "echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 " line. what am i doing wrong?
i really didn't want to create this topic and did quite a research, but every tutorial i've found so far didn't work for me. heeelppp :crying:
Click to expand...
Click to collapse
The first thing you need to know is that adb commands will only works when the phone is booted in a custom recovery or when booted in the rom (the "USB debugging" option must be turned on to use adb from the rom, not required when using from a custom recovery).
When the phone is booted in bootloader mode, only fastboot commands will work (and fastboot commands will not works when in recovery or when in the rom).
If your phone is S-OFF you can definitively flash a recovery even if the bootloader is locked. But the method used to flash it is different then the usual method (the "fastboot flash recovery name_of_recovery.img" command will only work with an unlocked bootloader). You'll need to zip the custom recovery .img file with an android-info.txt file matching your phone info and flash that zip file from RUU mode.
i.e:
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver HTC logo
Code:
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
where "firmware.zip" is the file containing your recovery .img file and the android-info.txt file
Code:
fastboot reboot-bootloader
I can make you a "firmware.zip" file if you're unsure how to do it. If you need it just reply what custom recovery version you need and post your "fastboot getvar all" output so I know your phone info (hide your imei)
Once the recovery is flashed, you can boot in recovery and unlock the bootloader using the tutorial you've linked. This method of unlocking the bootloader will not wipe your phone.
alray said:
The first thing you need to know is that adb commands will only works when the phone is booted in a custom recovery or when booted in the rom (the "USB debugging" option must be turned on to use adb from the rom, not required when using from a custom recovery).
When the phone is booted in bootloader mode, only fastboot commands will work (and fastboot commands will not works when in recovery or when in the rom).
If your phone is S-OFF you can definitively flash a recovery even if the bootloader is locked. But the method used to flash it is different then the usual method (the "fastboot flash recovery name_of_recovery.img" command will only work with an unlocked bootloader). You'll need to zip the custom recovery .img file with an android-info.txt file matching your phone info and flash that zip file from RUU mode.
i.e:
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver HTC logo
Code:
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
where "firmware.zip" is the file containing your recovery .img file and the android-info.txt file
Code:
fastboot reboot-bootloader
I can make you a "firmware.zip" file if you're unsure how to do it. If you need it just reply what custom recovery version you need and post your "fastboot getvar all" output so I know your phone info (hide your imei)
Once the recovery is flashed, you can boot in recovery and unlock the bootloader using the tutorial you've linked. This method of unlocking the bootloader will not wipe your phone.
Click to expand...
Click to collapse
hi, alray, thanks for taking the time to answer me. i'd like you to make this firmware.zip for me but "fastboot getvar all" gives me this
Code:
C:\miniadb_m7>fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.005s
what's wrong?
manofawker said:
The first thing you need to know is that adb commands will only works when the phone is booted in a custom recovery or when booted in the rom (the "USB debugging" option must be turned on to use adb from the rom, not required when using from a custom recovery).
When the phone is booted in bootloader mode, only fastboot commands will work (and fastboot commands will not works when in recovery or when in the rom).
If your phone is S-OFF you can definitively flash a recovery even if the bootloader is locked. But the method used to flash it is different then the usual method (the "fastboot flash recovery name_of_recovery.img" command will only work with an unlocked bootloader). You'll need to zip the custom recovery .img file with an android-info.txt file matching your phone info and flash that zip file from RUU mode.
i.e:
phone will reboot in ruu mode, a black screen with silver HTC logo
where "firmware.zip" is the file containing your recovery .img file and the android-info.txt file
hi, alray, thanks for taking the time to answer me. i'd like you to make this firmware.zip for me but "fastboot getvar all" gives me this
what's wrong?
Click to expand...
Click to collapse
Are there only one android device connected to your computer ("fastboot devices" listing only your phone?)
alray said:
Are there only one android device connected to your computer ("fastboot devices" listing only your phone?)
Click to expand...
Click to collapse
yes, just the one i'm trying to flash recovery
manofawker said:
yes, just the one i'm trying to flash recovery
Click to expand...
Click to collapse
what about:
Code:
fastboot oem dmesg
and
Code:
fastboot oem last_dmesg
Tried on another computer?
alray said:
what about:
Code:
fastboot oem dmesg
and
Code:
fastboot oem last_dmesg
Tried on another computer?
Click to expand...
Click to collapse
none of these worked. strangely enough, commands like "fastboot reboot" and "fastboot devices" actually do something... i've tried to execute the cmd in compatibility mode, but it was in vain. tomorrow i'm gonna try all of this on my friend's PC and let you know if i have any success.