[Q] HTC One weird issue - One (M7) Q&A, Help & Troubleshooting

Short explanation: My internal storage isnt recognized in android os and it is in twrp.
Long explanation
I followed a video on how to root a htc one m7 on youtube. This was my first time I ever rooted a phone.
I did a backup of the stock os after installing twrp and have it till this day on the phones internal storage.
I recently wanted to install multirom, it installed with an error. So I found an "uninstallmultirom.zip" file somewhere in the internet and from that moment...
My internal storage isnt recognized in android os but it is in twrp.
PS: I restored the phone using the backup I created earlier. It didnt fix the issue.
HTC ONE M7 Info:
version-main: 7.18.161.2
carrier: Vodafone UK
android version: 5.0.2
Is unlocked.

Cola Vs Pepsi said:
Short explanation: My internal storage isnt recognized in android os and it is in twrp.
Long explanation
I followed a video on how to root a htc one m7 on youtube. This was my first time I ever rooted a phone.
I did a backup of the stock os after installing twrp and have it till this day on the phones internal storage.
I recently wanted to install multirom, it installed with an error. So I found an "uninstallmultirom.zip" file somewhere in the internet and from that moment...
My internal storage isnt recognized in android os but it is in twrp.
PS: I restored the phone using the backup I created earlier. It didnt fix the issue.
HTC ONE M7 Info:
version-main: 7.18.161.2
carrier: Vodafone UK
android version: 5.0.2
Is unlocked.
Click to expand...
Click to collapse
relock and flash the 7.18.161.2 ruu
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

Help
Ok so I followed a youtube video and used the vodafone ruu.
It doesnt seem to flash the ruu :/

Cola Vs Pepsi said:
Ok so I followed a youtube video and used the vodafone ruu.
It doesnt seem to flash the ruu :/
Click to expand...
Click to collapse
did you used htc fastboot ?

yatindroid said:
did you used htc fastboot ?
Click to expand...
Click to collapse
I think I have. I used the same fastboot when I was rooting. Can you give me a link to the htc one?

Cola Vs Pepsi said:
I think I have. I used the same fastboot when I was rooting. Can you give me a link to the htc one?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95916177934539737
rename old fastboot to fastboot_old
put htc fastboot with rename it fastboot
then follow flash commands

yatindroid said:
https://www.androidfilehost.com/?fid=95916177934539737
rename old fastboot to fastboot_old
put htc fastboot with rename it fastboot
then follow flash commands
Click to expand...
Click to collapse
What commands will I follow?
The bootloader is relocked

Cola Vs Pepsi said:
Ok so I followed a youtube video and used the vodafone ruu.
It doesnt seem to flash the ruu :/
Click to expand...
Click to collapse
Cola Vs Pepsi said:
What commands will I follow?
The bootloader is relocked
Click to expand...
Click to collapse
Everything was explained in the link I gave you at post #2. (read the OP):
How To Flash
1. Rename file to RUU.zip
2. Place it in adb folder
3. Reboot phone to fastboot mode
4. S On need to relock bootloader (fastboot oem lock) , S Off lock not needed
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Rename htc_fastboot to fastboot or if you don't rename it, then the command will be "htc_fastboot flash zip RUU.zip"
Run the following commands from your adb folder:
6. htc_fastboot oem rebootRUU
7.htc_fastboot flash zip RUU.zip
8.htc_fastboot reboot-bootloader
Click to expand...
Click to collapse
Like yatin said, you need to use htc's fastboot to flash this ruu, not the normal fastboot. Rename your normal fastboot to "fastboot_old" like suggested by yatin then downloa htc's fastboot and save it in the same folder you have your old fastboot. once done open a command prompt:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot

alray said:
Everything was explained in the link I gave you at post #2. (read the OP):
How To Flash
Like yatin said, you need to use htc's fastboot to flash this ruu, not the normal fastboot. Rename your normal fastboot to "fastboot_old" like suggested by yatin then downloa htc's fastboot and save it in the same folder you have your old fastboot. once done open a command prompt:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
Click to expand...
Click to collapse
THANKS SO MUCH FOR THE HELP.
I though I bricked my phone at some point

Related

HTC only booting to white screen HTC One logo. Can't turn it off!

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.

Need to unroot both HTC one and S3 (GT-i9300)

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

[SOLVED] [Q] in bootloader at the OS version line text is red. Why ?

Hello Guys
Anyone know why my Os version is red line otherwise green...
look my picture please
thank you for ur response
ankorez said:
Hello Guys
Anyone know why my Os version is red line otherwise green...
look my picture please
thank you for ur response
Click to expand...
Click to collapse
Maybe its saying your installed system version doesn't match the one that came with the hboot version. Maybe the tampered is something to do with it.
ankorez said:
Hello Guys
Anyone know why my Os version is red line otherwise green...
look my picture please
thank you for ur response
Click to expand...
Click to collapse
This guy had a similar problem: http://forum.xda-developers.com/showthread.php?t=2493798&highlight=os+red+text
But then again, yours looks pretty weird: you bootloader is showing two firmware versions: 2.24.401.8 and (3.62.401.1) AND ON TOP OF THAT you're S-On, so you cannot flash unsigned firmware.
were you trying to flash a signed firmware package by any chance?
nkk71 said:
This guy had a similar problem: http://forum.xda-developers.com/showthread.php?t=2493798&highlight=os+red+text
But then again, yours looks pretty weird: you bootloader is showing two firmware versions: 2.24.401.8 and (3.62.401.1) AND ON TOP OF THAT you're S-On, so you cannot flash unsigned firmware.
were you trying to flash a signed firmware package by any chance?
Click to expand...
Click to collapse
i check it
thank you
nkk71 said:
This guy had a similar problem: http://forum.xda-developers.com/showthread.php?t=2493798&highlight=os+red+text
But then again, yours looks pretty weird: you bootloader is showing two firmware versions: 2.24.401.8 and (3.62.401.1) AND ON TOP OF THAT you're S-On, so you cannot flash unsigned firmware.
were you trying to flash a signed firmware package by any chance?
Click to expand...
Click to collapse
yes i have flash firmware from here : http://forum.xda-developers.com/showthread.php?t=2182823
and he say : Can I flash this firmware.zip on any HTC One?
in your thread the guy say he's fixed with gruureset but i don't found on the forum
ankorez said:
yes i have flash firmware from here : http://forum.xda-developers.com/showthread.php?t=2182823
and he say : Can I flash this firmware.zip on any HTC One?
in your thread the guy say he's fixed with gruureset but i don't found on the forum
Click to expand...
Click to collapse
But he was S-Off. You are S-On -> very dangerous flashing firmware with S-On, as you can only flash signed firmware, and only upgrade NO DOWNGRADE.
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
as opposed to:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot flash zip <name of firmware>.zip <- yes it has to be done twice, the first one will report failed, the second should succeed.
fastboot reboot
?
nkk71 said:
But he was S-Off. You are S-On -> very dangerous flashing firmware with S-On, as you can only flash signed firmware, and only upgrade NO DOWNGRADE.
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
as opposed to:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot flash zip <name of firmware>.zip <- yes it has to be done twice, the first one will report failed, the second should succeed.
fastboot reboot
?
Click to expand...
Click to collapse
yes it's my problem ! i have do this only
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
---------------
i 've found that http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
you think if i flash it my problem solved?
ankorez said:
yes it's my problem ! i have do this only
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
---------------
i 've found that http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
you think if i flash it my problem solved?
Click to expand...
Click to collapse
The Guru Reset will flash stock ROM (and stock recovery and radio, if you select them in the installer), but it may not solve the firmware issue.
I am just guessing, but because you only ran the "fastboot flash zip <name of firmware>.zip" once, your firmware may be in a state of limbo (if I can call it that):
on one hand it was prepared to upgrade to 3.62.401.1 and that's why it's in the brackets, but since you didn't run the fastboot command another time it actually stayed on 2.24.401.8, and that why you have two different firmware versions in bootloader; one installed 2.24.401.8 another "waiting" to be installed 3.62.401.1. (all this is only a theory)
So what are the options now? Since you were trying to upgrade your firmware (even with S-On, which I take is your preference to stay S-On), I guess you should do it, but this time do it correctly and run the fastboot command twice and make sure it reports success the 2nd time around.
Here's what I would recommend (taking into account you do not wish to S-Off),
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- update the firmware, but correctly this time
3- depending on what ROM you were on, either restore it, or get an updated version for your firmware
And actually, before that, if you just want to test the Guru Reset:
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- flash Guru Reset and see if that works out for you
Those are pretty much my thoughts
PS: when I say backup everything to PC, it's because (sometimes) flashing stock recovery will completely wipe your phone including internal storage (not to mention that unlocking bootloader does that too)
Hit the thanks button IF i helped
nkk71 said:
The Guru Reset will flash stock ROM (and stock recovery and radio, if you select them in the installer), but it may not solve the firmware issue.
I am just guessing, but because you only ran the "fastboot flash zip <name of firmware>.zip" once, your firmware may be in a state of limbo (if I can call it that):
on one hand it was prepared to upgrade to 3.62.401.1 and that's why it's in the brackets, but since you didn't run the fastboot command another time it actually stayed on 2.24.401.8, and that why you have two different firmware versions in bootloader; one installed 2.24.401.8 another "waiting" to be installed 3.62.401.1. (all this is only a theory)
So what are the options now? Since you were trying to upgrade your firmware (even with S-On, which I take is your preference to stay S-On), I guess you should do it, but this time do it correctly and run the fastboot command twice and make sure it reports success the 2nd time around.
Here's what I would recommend (taking into account you do not wish to S-Off),
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- update the firmware, but correctly this time
3- depending on what ROM you were on, either restore it, or get an updated version for your firmware
And actually, before that, if you just want to test the Guru Reset:
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- flash Guru Reset and see if that works out for you
Those are pretty much my thoughts
PS: when I say backup everything to PC, it's because (sometimes) flashing stock recovery will completely wipe your phone including internal storage (not to mention that unlocking bootloader does that too)
Hit the thanks button IF i helped
Click to expand...
Click to collapse
Thank you very much i have reflash firmware.zip x2 and the second flash has worked
Thankyou again for you rapid help
ankorez said:
Thank you very much i have reflash firmware.zip x2 and the second flash has worked
Thankyou again for you rapid help
Click to expand...
Click to collapse
My pleasure, if everything is OK now, please add [SOLVED] in the main thread title. Thanks.
By the way im the guy in the other thread,did not get any answers or help had no choice but to use ruu zip to downgrade then ota back up
sent from my s-off 801n M7_UL
steelmaggot said:
By the way im the guy in the other thread,did not get any answers or help had no choice but to use ruu zip to downgrade then ota back up
sent from my s-off 801n M7_UL
Click to expand...
Click to collapse
Quite right it was you, sorry I didnt help out, but I honestly didnt know what the problem was. Only after seeing this guy's screen with two different versions and S-ON, did I think it was an incomplete firmware flash.
Might have been the case with you as well, but I couldnt tell cause the versions were the same, and you were S-Off.
Anyway, lesson learned.

[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.

HTC One Stuck on Bootloader

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

Categories

Resources