Database Develop

How to update Touch firmware via TWRP

Hello, can i downgrade / update the Touchscreen Firmware with TWRP
i have S-ON - Hboot 1.54.. When i make it with :
Fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Error: 99 Unknown....
help pls ^^

kevios12 said:
Hello, can i downgrade / update the Touchscreen Firmware with TWRP
i have S-ON - Hboot 1.54.. When i make it with :
Fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Error: 99 Unknown....
help pls ^^
Click to expand...
Click to collapse
You can't if you still have s-on, you can only flash signed firmware

it*s makeable to sign the touchscreen firmware or the stock ruu 1.29 to sign and can i downgrade then?

[Q] Quick unroot question

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.

[Guide][How-to] Run 4.06.651.4 RUU on any windows without any problem..!!

Guyz this is my first guide to xda and i am very happy that i had made this guide...
credit goes to [email protected] for this lovely RUU and [email protected] for his help and support.
This simple step by step guide helps those people who are having issues in running 4.06.651.4 ruu in windows 8 or any other windows or those who are having error 155 in running the ruu
So
- first download 4.06.651.4 RUU from O.M.J's thread (http://forum.xda-developers.com/showthread.php?t=2658910)
-check the md5 match
-now download this firmware (http://www.androidfilehost.com/?fid=23329332407568410) and rename it to firmware.zip
-place this firmware,zip in your sdk folder
-now boot into bootloader and connect you phone through usb cable
-now relock the bootloader by using-
fastboot oem lock
-now flash the firmware using-
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
-now check that your hboot is now 1.56
-now run the ruu and follow the steps
Hurray you are now successfully updated to android 4.4.2
HIT THANKS BUTTON IF I HAVE HELPED YOU>>!!
Sprint HTC One
Android 4.4.2
hboot-1.56
os-4.06.651.4
radio-1.00.20.1108

[Q] Tutorial in order to update to the latest firmware 6.09.401.5 of HTC One S-ON???

Hello guys,
I have an HTC One S-ON and I want to try the new ROM with 4.4.3. In order to use those new ROMs, all the developers recommended to update first the firmware. Sadly, many of you have an S-OFF phone where are lots of tutorials that can help you. So, I've read a lot and made a short tutorial. If anyone of you can help me if a confirmation or not of this will be great and could help me to upgrade my phone to the latest firmware!!!
How to flash?
(bootloader needs to be relocked)
1.Re-lock your bootloader (this will most probably wipe content of your device)(Type in “fastboot oem lock”)
2.Copy downloaded .zip(from this site https://www.androidfilehost.com/?fid=23622183712460395) to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
3.Re-name .zip file to firmware.zip
4.Open command prompt
5.Boot your device in fastboot mode (vol down + power ===> fastboot)
6.Connect device to the PC
7.In command prompt cd to fastboot.exe location
8.Make sure you have correct modeid and cidnum (type: fastboot getvar all)(I've checked my phone with apk CID Getter and saw that I have modelid: PN0710000 and cidnum: HTC__032 and I think it is ok to flash the firmware)
9.Type: fastboot oem lock (if your device is not relocked yet)
10.Type: fastboot oem rebootRUU and wait for device to reboot(Is there a RUU file that should I download? This is the only trick part that I don't understand . I found this the latest http://www.htc1guru.com/dld/ruu_m7_u...igned_2-1-exe/ RUU file..but I'm not sure what to do with or if I really have to use it )
11.Type: fastboot flash zip firmware.zip and wait for process to complete
12.Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
13.Type: fastboot flash zip firmware.zip and wait for process to complete
14.Type: fastboot reboot
15.Unlock your bootloader and flash custom recovery if you are going to use custom ROM(Like the usual way using http://www.htcdev.com/bootloader and after that to change the stock Recovery with TWRP)
I hope I've understand everything and all will be right!
Thanks @mike1986. for the beginning tutorial. I've just updated it in order to uderstand the whole process.

Floare said:
Hello guys,
I have an HTC One S-ON and I want to try the new ROM with 4.4.3. In order to use those new ROMs, all the developers recommended to update first the firmware. Sadly, many of you have an S-OFF phone where are lots of tutorials that can help you. So, I've read a lot and made a short tutorial. If anyone of you can help me if a confirmation or not of this will be great and could help me to upgrade my phone to the latest firmware!!!
How to flash?
(bootloader needs to be relocked)
1.Re-lock your bootloader (this will most probably wipe content of your device)(Type in “fastboot oem lock”)
2.Copy downloaded .zip(from this site https://www.androidfilehost.com/?fid=23622183712460395) to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
3.Re-name .zip file to firmware.zip
4.Open command prompt
5.Boot your device in fastboot mode (vol down + power ===> fastboot)
6.Connect device to the PC
7.In command prompt cd to fastboot.exe location
8.Make sure you have correct modeid and cidnum (type: fastboot getvar all)(I've checked my phone with apk CID Getter and saw that I have modelid: PN0710000 and cidnum: HTC__032 and I think it is ok to flash the firmware)
9.Type: fastboot oem lock (if your device is not relocked yet)
10.Type: fastboot oem rebootRUU and wait for device to reboot you will see a black screen with a silver HTC logo(Is there a RUU file that should I download? This is the only trick part that I don't understand . I found this the latest http://www.htc1guru.com/dld/ruu_m7_u...igned_2-1-exe/ RUU file..but I'm not sure what to do with or if I really have to use it )
11.Type: fastboot flash zip firmware.zip and wait for process to complete
12.Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
13.Type: fastboot flash zip firmware.zip and wait for process to complete
14.Type: fastboot reboot
15.Unlock your bootloader and flash custom recovery if you are going to use custom ROM(Like the usual way using http://www.htcdev.com/bootloader and after that to change the stock Recovery with TWRP)
I hope I've understand everything and all will be right!
Click to expand...
Click to collapse
Basically the flashing the firmware steps when you are S-ON or S-OFF are the same. The only difference is if you are S-ON you must have a locked bootloader, the firmware version must be the same or higher and it must be signed.
Step 10 - You want the device in RUU mode to accept the firmware.
Step 11 - The flashing of the firmware the first time is to set up the device to accept the firmware. It should fail the first time.
Step 12/13 - Exact same code as step 11

majmoz said:
Basically the flashing the firmware steps when you are S-ON or S-OFF are the same. The only difference is if you are S-ON you must have a locked bootloader, the firmware version must be the same or higher and it must be signed.
Step 10 - You want the device in RUU mode to accept the firmware.
Step 11 - The flashing of the firmware the first time is to set up the device to accept the firmware. It should fail the first time.
Step 12/13 - Exact same code as step 11
Click to expand...
Click to collapse
@majmoz Thank you very much for your help! I did it in the end! I was calm and the target was hit..like I could say!
The moderators could close this thread. Thank you guyz for your hard work!

Can't flash custom recovery on my S-OFF, locked, M7

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.