Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
OfficialLocdoGg said:
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
Click to expand...
Click to collapse
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
alray said:
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
Click to expand...
Click to collapse
OfficialLocdoGg said:
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
Click to expand...
Click to collapse
its fine to flash a ruu with phone booted in bootloader btw.
alray said:
its fine to flash a ruu with phone booted in bootloader btw.
Click to expand...
Click to collapse
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
OfficialLocdoGg said:
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
Click to expand...
Click to collapse
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Boot into bootloader/FASTBOOT USB
Type:
Code:
[B][I]fastboot oem lock[/I][/B]
Type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
majmoz said:
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
Click to expand...
Click to collapse
Thanks. This restored the phone to a usable state. I'm going to try firewater now.
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.
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.
Hey guys I badly need help!!! I was able to convert my HTC One GSM to Google Edition just last week, but today I want to restore it to its factory ROM so I can also restore the warranty. Now the problem became visible when I tried to flash a stock ROM (not the GPE ROM). Listed below are the problems I am facing at the moment:
1. Stuck in FASTBOOT USB, and cannot boot to ROM.
2. Can't boot to recovery. Everytime I highlight and select recovery the phone just shows up the "Google" logo, then vibrates, then back fastboot USB.
3. Factory Reset not working, again shows up "Google" then restarts to fastboot usb mode.
4. I ran cmd in sdk-tools, typed in "fastboot devices", and my phone is detected. But when I type "adb devices", my phone is not listed.
5. I tried flashing CWM or TWRP through fastboot in cmd but the reply is"remote: signature verify fail", as wellas flashing a RUU for my device.
6. On bootloader is written:
*** TAMPERED ***
*** RELOCKED ***
M7_UK PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v30.120.3274.0520
OS-2.14.1700.15
eMMC-boot 2048MB
Guys I really badly need help to fix my phone. I don't wanna spend for repairs or throw it in the garbage. I am very sure there's a way to fix this and get it to work, but I am rookie in android as I've been an iOs user for a couple of years.
ClydeWinux said:
Hey guys I badly need help!!! I was able to convert my HTC One GSM to Google Edition just last week, but today I want to restore it to its factory ROM so I can also restore the warranty. Now the problem became visible when I tried to flash a stock ROM (not the GPE ROM). Listed below are the problems I am facing at the moment:
1. Stuck in FASTBOOT USB, and cannot boot to ROM.
2. Can't boot to recovery. Everytime I highlight and select recovery the phone just shows up the "Google" logo, then vibrates, then back fastboot USB.
3. Factory Reset not working, again shows up "Google" then restarts to fastboot usb mode.
4. I ran cmd in sdk-tools, typed in "fastboot devices", and my phone is detected. But when I type "adb devices", my phone is not listed.
5. I tried flashing CWM or TWRP through fastboot in cmd but the reply is"remote: signature verify fail", as wellas flashing a RUU for my device.
6. On bootloader is written:
*** TAMPERED ***
*** RELOCKED ***
M7_UK PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.33250.14
OpenDSP-v30.120.3274.0520
OS-2.14.1700.15
eMMC-boot 2048MB
Guys I really badly need help to fix my phone. I don't wanna spend for repairs or throw it in the garbage. I am very sure there's a way to fix this and get it to work, but I am rookie in android as I've been an iOs user for a couple of years.
Click to expand...
Click to collapse
try flashing the appropriate firmware files for an particular RUU before flashing RUU n check?
Harish_Kumar said:
try flashing the appropriate firmware files for an particular RUU before flashing RUU n check?
Click to expand...
Click to collapse
Yes I have tried flashing the appropriate RUU file but in CMD it returns "remote: signature verify fail"
ClydeWinux said:
Yes I have tried flashing the appropriate RUU file but in CMD it returns "remote: signature verify fail"
Click to expand...
Click to collapse
not RUU...i am talking about firmware files
for instance if you are about to flash an 4.3 sense 3.22 rom..flash its firmware in RUU mode before flashing the actual RUU
Harish_Kumar said:
not RUU...i am talking about firmware files
for instance if you are about to flash an 4.3 sense 3.22 rom..flash its firmware in RUU mode before flashing the actual RUU
Click to expand...
Click to collapse
Oh my, are the firmware files included inside the RUU.zip? or should I download the firmware files separately? @Harish_Kumar
ClydeWinux said:
Oh my, are the firmware files included inside the RUU.zip? or should I download the firmware files separately? @Harish_Kumar
Click to expand...
Click to collapse
RUU Zip will be encrypted..you cant extract files from it
you have to download firmware files seperately...you can find them in android development section
check here -> http://forum.xda-developers.com/showthread.php?t=2182823
I almost forgot... you should be S-off in order to flash the firmware
and even RUU Flashing requires S-off
Harish_Kumar said:
RUU Zip will be encrypted..you cant extract files from it
you have to download firmware files seperately...you can find them in android development section
check here -> http://forum.xda-developers.com/showthread.php?t=2182823
I almost forgot... you should be S-off in order to flash the firmware
and even RUU Flashing requires S-off
Click to expand...
Click to collapse
Ok I have flashed the firmware for my phone and now it's on 3.58.1700.5. Should I download a RUU.zip version 3.58.1700.5 and flash it on my phone? because until now I can't flash CWM or TWRP. @Harish_Kumar
ClydeWinux said:
Ok I have flashed the firmware for my phone and now it's on 3.58.1700.5. Should I download a RUU.zip version 3.58.1700.5 and flash it on my phone? because until now I can't flash CWM or TWRP. @Harish_Kumar
Click to expand...
Click to collapse
arent you able to flash custom recovery like CWM or TWRP even after flashing firmware files? if everything's right you should be able to
56562336461
Harish_Kumar said:
arent you able to flash custom recovery like CWM or TWRP even after flashing firmware files? if everything's right you should be able to
Click to expand...
Click to collapse
Everytime I tried to flash custom recovery (CWM/TWRP) in cmd it returns "remote: signature verify fail", I used command "fastboot flash recovery cwm.img". And now I tried to load up recovery from menu, and it's stuck on a 'dead-android-icon-with-exclamation-error' logo. @Harish_Kumar
I was following Vomer's guide on my One, which has been working great. I had HBOOT 1.54, S-Off, SuperCID, and pushed the firmware twice, got the success message, and waited and when it says finished used adb to tell it to reboot. Now I get the splash, with the lock gone, as expected, and then the screen goes black. If I hold power, or power and down, the hardware keys start blinking and then nothing. A few seconds later I get the splash again, then blank again.
It appears to be communicating briefly over USB because my laptop starts trying to install a HTC MTP device (drive is already on the PC and has been fine) before it looses comms and drops out. I can't seem to get adb device to recognize it....
PLEASE tell me someone can help me recover my phone!!! I will be immensely grateful.
And what the HBOOT version you wanted to downgrade to?
Ivanovic said:
And what the HBOOT version you wanted to downgrade to?
Click to expand...
Click to collapse
I wasn't trying to downgrade HBOOT, just rather ensure my firmware was up to date. I'd had mine set up as a GPE and was flashing the DE (after supercid).
By way of an update, I've been able to get into bootloader and I'm a bit scared on what to do next so I dont screw this up. I notice that I still have S-OFF, but HBOOT is now showing 1.56 and it says RELOCKED at the top. My plan was to use rumrunner (just because of the HBOOT, but it is erroring anyway) to unlock bootloader, and then to look up the fastboot commands to push a ROM and recovery. Any advice?
Downgrade to 1.44 and change cid according to the Rom you want. Then unlock or set your bootloader to LOCKED
Here is the file for 1.44 http://www69.zippyshare.com/v/95229262/file.html
Sent from my HTC One using Tapatalk
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
vettejock99 said:
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
Click to expand...
Click to collapse
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Ivanovic said:
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Click to expand...
Click to collapse
Awesome. So I've got HBOOT 1.44, S-OFF, bootloader unlocked, supercid, and TWRP 2.6.3.3 flashed again, and I tried sideloading ARHD rom. It all looked good but same thing for the moment, I get the splash and then black......I can't figure out why I can't boot into a rom right now. About to try flashing ROM again.
Okay, so didnt' work. After sideload flashing gets to 100% it just does nothing. Manually rebooting gets me back into the splash then blackness bootloop......
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
The former didn't get me anywhere, but I did follow your thinking and decided to use the RUU and start over. I'm happy to report that got me going, and then I was able to get AR HD on. I probably had to do that all along once I wiped the ROM and recovery, as sideloading clearly wasn't going to work (in retrospect) as it has an AROMA installer.
Thanks so much everyone!!
SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
Nice that everything is solved now.
Verstuurd van mijn HTC One
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