Hi,
I can not successfully run RUU ROM. I though, that ruu can fix almost everything, but everytime I got error message 140. Before 3 month I download stock rom and successfully used it, but now the same rom doesnt work (from this site: http://shipped-roms.com/index.php?category=android&model=Ace ).
Bootloader is relocked.
Main problem is that after "standart" restart phone stuck on white screen with htc logo. If I restart to bootloader, via fastboot push boot.img to phone, than phone works almost wel.. ...until next restart.. :/
I know only one way how to fix - via stock rom. Or does exist any next solution?
I try to use this stock rom:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe
(before 3 month works perfect, now I got error 140...)
Here is my phone info:
INFOversion: 0.5
INFOversion-bootloader: 2.00.0029
INFOversion-baseband: 26.14.04.28_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 3.13.0.0
INFOserialno: SH18KRX02893
INFOimei: xxxxxxxxxxxxxx
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: HTC__102
INFObattery-status: good
INFObattery-voltage: 4204mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: fcef1579
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.004s
Thanks all for tips
You mean fastboot falsh boot boot.img (don't do that on S-on device)
try:
Step 1)
after runing ruu.exe in windows temp folder you can find room.zip
copy it to another location (in folder where you have fastboot and adb)
close ruu.exe
Step2)
If you are in android
adb reboot oem-78
or If you are in hboot (fastboot)
fastboot oem rebootRUU
when your phone restart and get in ruu flash mode
fastboot flash zip room.zip
Gussta said:
You mean fastboot falsh boot boot.img (don't do that on S-on device)
try:
Step 1)
after runing ruu.exe in windows temp folder you can find room.zip
copy it to another location (in folder where you have fastboot and adb)
close ruu.exe
Step2)
If you are in android
adb reboot oem-78
or If you are in hboot (fastboot)
fastboot oem rebootRUU
when your phone restart and get in ruu flash mode
fastboot flash zip room.zip
Click to expand...
Click to collapse
If I am understand well:
1) conect phone to pc, run instalation ruu
2) during instalation process find in win/temp folder rom.zip
3) copy this file tinto folder with adb files
4) cancel instalation
5) in phone run bootloader than fastboot
6) run command prompt in folder with adb and rom files, than run "fastboot oem rebootRUU"
7) wait a few minute until instalation end
8) run phone, than go to fastboot and from command prompt run "fastboot flash zip room.zip"
9) and now phone should be repaired
Is that right?
btw: if I want to turn on my phone, every time I have to flash boot.img via fastboot otherwise phone didnt start..
Pilsner12 said:
If I am understand well:
1) conect phone to pc, run instalation ruu
2) during instalation process find in win/temp folder rom.zip
3) copy this file tinto folder with adb files
4) cancel instalation
5) in phone run bootloader than fastboot
6) run command prompt in folder with adb and rom files, than run "fastboot oem rebootRUU"
7) wait a few minute until instalation end
8) run phone, than go to fastboot and from command prompt run "fastboot flash zip room.zip"
9) and now phone should be repaired
Is that right?
btw: if I want to turn on my phone, every time I have to flash boot.img via fastboot otherwise phone didnt start..
Click to expand...
Click to collapse
Almost
6) run command prompt in folder with adb, fastboot and rom files, than run "fastboot oem rebootRUU"
7) wait a few minute until phone goes in ruu install mode
8) than from command prompt run "fastboot flash zip room.zip"
9) and now phone should be repaired
Gussta said:
Almost
6) run command prompt in folder with adb, fastboot and rom files, than run "fastboot oem rebootRUU"
7) wait a few minute until phone goes in ruu install mode
8) than from command prompt run "fastboot flash zip room.zip"
9) and now phone should be repaired
Click to expand...
Click to collapse
I found rom.zip, ran "fastboot flash zip rom.zip" and now I am waiting more than 10 minutes (mabye more) and on phone is blask screen with white logo HTC and on command prompt isnt nothing new..
How long it takes, or what I should do?
Pilsner12 said:
I found rom.zip, ran "fastboot flash zip rom.zip" and now I am waiting more than 10 minutes (mabye more) and on phone is blask screen with white logo HTC and on command prompt isnt nothing new..
How long it takes, or what I should do?
Click to expand...
Click to collapse
I found other manual http://androidforums.com/desire-hd-all-things-root/716369-unroot-desire-hd-file-ruu-2.html but my phone stop working in same moment:
INFOzip header checking...
INFOzip info parsing...
after parsing nothing happens.. (more than hour)
Pilsner12 said:
I found rom.zip, ran "fastboot flash zip rom.zip" and now I am waiting more than 10 minutes (mabye more) and on phone is blask screen with white logo HTC and on command prompt isnt nothing new..
How long it takes, or what I should do?
Click to expand...
Click to collapse
Info pharsing musn't take to long. Maybe max min. or two.
Do you get any green stripe under HTC logo in black screen?
I didn't see that anytime.
In this step I think you can stop it with unplaging cable close cmd plug cable again and type fastboot reboot or try just close cmd open it again and type the same.
But never ever pull out battery. Rather unplug cable and wait that phone loose battery power. With pulling out battery you can burn eMMC disk.
After you reboot phone, you can try again.
---------- Post added at 09:26 PM ---------- Previous post was at 09:21 PM ----------
Pilsner12 said:
I found other manual http://androidforums.com/desire-hd-all-things-root/716369-unroot-desire-hd-file-ruu-2.html but my phone stop working in same moment:
INFOzip header checking...
INFOzip info parsing...
after parsing nothing happens.. (more than hour)
Click to expand...
Click to collapse
I didn't understand now.
You try several time with the same error or?
Gussta said:
Info pharsing musn't take to long. Maybe max min. or two.
Do you get any green stripe under HTC logo in black screen?
I didn't see that anytime.
In this step I think you can stop it with unplaging cable close cmd plug cable again and type fastboot reboot or try just close cmd open it again and type the same.
But never ever pull out battery. Rather unplug cable and wait that phone loose battery power. With pulling out battery you can burn eMMC disk.
After you reboot phone, you can try again.
---------- Post added at 09:26 PM ---------- Previous post was at 09:21 PM ----------
I didn't understand now.
You try several time with the same error or?
Click to expand...
Click to collapse
I didnt get any green stripe under HTC logo.
Yes, I try several times with same result - nothing happens..
I try for shure again stock rom and still not working. Error 155.
What actually mean "INFOzip info parsing"?
btw: how I can recognize, that eMMC disk is ok or corrupt?
Error 155 gets when either your bootloader is unlocked or u r using the wrong RUU
Factory reset your phone to remove any non-stock stuff from the ROM and try again.
If file fail with error don't get out from ruu, just start flasihng again.
Sometimes you have to flash twice in a row to get it.
After it's done type fastboot reboot-bootloader (takes you back to fastboot)
Do Factory reset again.
If you failed with flashing try with difrent rom.
INFOzip info parsing means that he is checking if room.zip is ok.
"btw: how I can recognize, that eMMC disk is ok or corrupt?"
If you change settings, contacts, alarm etc.. and when you shut down your phone, pull out your battery, wait one to two minutes, put it back in, power on phone and if you get everything back like it was before you maide changes it's probably bad eMMC. If everything get remembered you don't have problem with eMMC.
But error you get dosn't have anything with eMMC. With bad eMMC you can correctly flash ROM and after restarting your phone you can see that you haven't flash anything.
The reason is that phone first push everything to RAM and than on eMMC (because eMMC is slow).
When you push some data to phone and it get RAM you have it but because (and if not) eMMc can't save it, after restart you have nothing.
Gussta said:
Error 155 gets when either your bootloader is unlocked or u r using the wrong RUU
Factory reset your phone to remove any non-stock stuff from the ROM and try again.
If file fail with error don't get out from ruu, just start flasihng again.
Sometimes you have to flash twice in a row to get it.
After it's done type fastboot reboot-bootloader (takes you back to fastboot)
Do Factory reset again.
If you failed with flashing try with difrent rom.
INFOzip info parsing means that he is checking if room.zip is ok.
"btw: how I can recognize, that eMMC disk is ok or corrupt?"
If you change settings, contacts, alarm etc.. and when you shut down your phone, pull out your battery, wait one to two minutes, put it back in, power on phone and if you get everything back like it was before you maide changes it's probably bad eMMC. If everything get remembered you don't have problem with eMMC.
But error you get dosn't have anything with eMMC. With bad eMMC you can correctly flash ROM and after restarting your phone you can see that you haven't flash anything.
The reason is that phone first push everything to RAM and than on eMMC (because eMMC is slow).
When you push some data to phone and it get RAM you have it but because (and if not) eMMc can't save it, after restart you have nothing.
Click to expand...
Click to collapse
If I am understant well:
1) relock bootloader "fastboot oem lock"
2) Start phone into bootloader
3) from bootloader run factory reset
4) type fastboot reboot-bootloader run factory reset again
In case, that I have in my phone corrupted stock rom and phone trying use it, how I can use another rom?
via command prompt "fastboot flash zip rom.zip"?
(prepared from stock installation process)
Pilsner12 said:
If I am understant well:
1) relock bootloader "fastboot oem lock"
2) Start phone into bootloader
3) from bootloader run factory reset
4) type fastboot reboot-bootloader run factory reset again
In case, that I have in my phone corrupted stock rom and phone trying use it, how I can use another rom?
via command prompt "fastboot flash zip rom.zip"?
(prepared from stock installation process)
Click to expand...
Click to collapse
1) relock bootloader "fastboot oem lock"
2) Start phone into bootloader
3) from bootloader run factory reset
4) type fastboot rebootRUU
5) type fastboot flash zip rom.zip (if you get error repeat this step one more time)
6) type fastboot reboot-bootloader
7) run factory reset
---------- Post added at 03:47 PM ---------- Previous post was at 03:42 PM ----------
Pilsner12 said:
In case, that I have in my phone corrupted stock rom and phone trying use it, how I can use another rom?
via command prompt "fastboot flash zip rom.zip"?
(prepared from stock installation process)
Click to expand...
Click to collapse
I didn't understand what did you want to say with this part?
If you wanted to say: what to do if you flash stock rom?
Just flash another one with fastboot flash zip rom.zip
Gussta said:
1) relock bootloader "fastboot oem lock"
2) Start phone into bootloader
3) from bootloader run factory reset
4) type fastboot rebootRUU
5) type fastboot flash zip rom.zip (if you get error repeat this step one more time)
6) type fastboot reboot-bootloader
7) run factory reset
---------- Post added at 03:47 PM ---------- Previous post was at 03:42 PM ----------
I didn't understand what did you want to say with this part?
If you wanted to say: what to do if you flash stock rom?
Just flash another one with fastboot flash zip rom.zip
Click to expand...
Click to collapse
Yes, it is what I am wanted to say.. sorry for my english.
I try it exactly how is here described but it doesnt help.. (tryed other rom.zip)
I foud this manual: http://forum.xda-developers.com/showthread.php?t=2367322 but if I want to run aahk, command prompt reply:
Code:
File: "tools\bin\fre3vo" is missing or corrupt.
Download and extract again
Some virus scanners remove the necessary exploits for temproot.
Disable virus scan if that happens.
Pokračujte stisknutím libovolné klávesy...
I think only one way how this fix it is to gain S-OFF. Or does exist any other way?
..but I dont know how..
Pilsner12 said:
Yes, it is what I am wanted to say.. sorry for my english.
I try it exactly how is here described but it doesnt help.. (tryed other rom.zip)
I foud this manual: http://forum.xda-developers.com/showthread.php?t=2367322 but if I want to run aahk, command prompt reply:
Code:
File: "tools\bin\fre3vo" is missing or corrupt.
Download and extract again
Some virus scanners remove the necessary exploits for temproot.
Disable virus scan if that happens.
Pokračujte stisknutím libovolné klávesy...
I think only one way how this fix it is to gain S-OFF. Or does exist any other way?
..but I dont know how..
Click to expand...
Click to collapse
You can try with AAHK.
Here's the link for fre3vo: http://www.4shared.com/zip/nBCVzHMl/Fre3vo
If AAHK tell you that some files in tools\bin\ driectory missing, just find tham on google and download them.
Always turn off your virus scanners and HTC sync when you use aahk.
Related
Good evening!
I'm new to this so ill try to be as specific as I can. about a month ago I've bought the One x from a private store here in Israel and i think it was from taiwan or something. anyways, a couple of days ago i started messing with it, rooting it and everything.
I unlocked the bootloader via the htcdev.com, did the whole CMD thing and everything and flashed the android revolution HD rom (thats the name?)
so it was great and everything but it wasnt as complete as the rom my phone came with (I guess its the stock rom) so i tried the RD MIUI rom and it was fine, but still not what i was looking for and so i realized i need to come back to the stock rom, simple and clean.
now after the whole unlocking and rooting and everything, how the hell do i get my stock rom back? i want to lock back my phone, unroot it and put the old rom back on it and im very new to this whole HTC rooting thing, since i was using the galaxy s 1 and 2 before the HTC.
I searched the forum and couldnt find a guide, every post here is just links but no TUT's, as if everyone already knows everything!
anyways, I would really appreciate anybody helping me!
my phone is the international version i guess, bought in israel shipped from some asian country but is unlocked to all carriers and everything, not an AT&T version or anything.
First thing, make sure what is your original software version.
If you're not sure, run this in fastboot mode
go to bootloader
type fastboot getvar version-main
tell us what no. it show
then will be the next step to get the correct RUU for your device
ckpv5 said:
First thing, make sure what is your original software version.
If you're not sure, run this in fastboot mode
go to bootloader
type fastboot getvar version-main
tell us what no. it show
then will be the next step to get the correct RUU for your device
Click to expand...
Click to collapse
version-main: 1.29.707.11
finished. total time: 0.006s
thats the thing it showed me.
That's great.
Here is your RUU : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.105.14_release_260743_signed.exe
How to : go to bootloader / fastboot mode
(even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- run/doubleclick RUU and follow instructions.
Grab the stock boot.img & recovery from : http://forum.xda-developers.com/showpost.php?p=27261622&postcount=1149
ckpv5 said:
First thing, make sure what is your original software version.
If you're not sure, run this in fastboot mode
go to bootloader
type fastboot getvar version-main
tell us what no. it show
then will be the next step to get the correct RUU for your device
Click to expand...
Click to collapse
Can this be done with terminal emulator also?
If so how?
Sent from my HTC One X using CoreDroid Premium
Doo Doo said:
Can this be done with terminal emulator also?
If so how?
Sent from my HTC One X using CoreDroid Premium
Click to expand...
Click to collapse
If you are talking about the Terminal Emulator app, I don't think it can read the version-main as the getprop command will read what is written in the build.prop
But I maybe wrong as I'm not really familiar with Terminal Emulator except some basic command.
So how do we flash this whole thing?
GUARDIANBD said:
So how do we flash this whole thing?
Click to expand...
Click to collapse
Reboot to bootloader / fastboot mode where you see the word fastboot usb highlighted in red.
And the above files only for 1.29.707.11 software version, it won't work for others.
Doo Doo said:
Can this be done with terminal emulator also?
If so how?
Sent from my HTC One X using CoreDroid Premium
Click to expand...
Click to collapse
ckpv5 said:
That's great.
Here is your RUU : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.105.14_release_260743_signed.exe
How to : go to bootloader / fastboot mode
(even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- run/doubleclick RUU and follow instructions.
Grab the stock boot.img & recovery from : http://forum.xda-developers.com/showpost.php?p=27261622&postcount=1149
Click to expand...
Click to collapse
This should be stickied in this section as it is smack bang on the number.. AWESOME WORK
try'd to use the "fastboot getvar version-main" in linux terminal
i see FASTBOOT USB but i cannot get the info that u need..
so would this help?
Code:
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.96.0000
CPLD-None
MICROP-None
RADIO-1.1204.105.14
eMMC-bootmode : disabled
CPU-bootmode : disabled
MODEM PATH : OFF
May 10 2012,01:32:07
Not so sure about linux, but maybe the command is:
$ ./fastboot getvar version-main
ckpv5 said:
Not so sure about linux, but maybe the command is:
$ ./fastboot getvar version-main
Click to expand...
Click to collapse
just to get this straight :
to find this info what i need to do? i'v got dualboot WIN7 & Linux,at the Win drivers are installed + HTC SYNC
is there anything else i need to do ?
im in the HBOOT the 1X is connected and it says "FASTBOOT USB"
try'd to type in the cmd "fastboot getvar version-main" and nothing is happend
where this syntax is needed to put? via CMD or ADB?
Do you still have the fastboot folder/files that you downloaded when you unlock your
device ?
In Windows, open cmd prompt, cd to the fastboot folder where you have the fastboot.exe
example:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd\
C:\>cd fastboot
C:\fastboot>fastboot getvar version-main
version-main: 1.29.707.11
finished. total time: 0.044s
C:\fastboot>
Attached here the fastboot files & adb files in case anyone need them
ckpv5 said:
Do you still have the fastboot folder/files that you downloaded when you unlock your
device ?
In Windows, open cmd prompt, cd to the fastboot folder where you have the fastboot.exe
example:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd\
C:\>cd fastboot
C:\fastboot>fastboot getvar version-main
version-main: 1.29.707.11
finished. total time: 0.044s
C:\fastboot>
Attached here the fastboot files & adb files in case anyone need them
Click to expand...
Click to collapse
done
Code:
c:\fastboot>fastboot getvar version-main
version-main: 1.29.720.11
finished. total time: -0.000s
now i have CWM recovery
how can i revert back to stock from there?
ckpv5 said:
That's great.
Here is your RUU : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.105.14_release_260743_signed.exe
How to : go to bootloader / fastboot mode
(even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- run/doubleclick RUU and follow instructions.
Grab the stock boot.img & recovery from : http://forum.xda-developers.com/showpost.php?p=27261622&postcount=1149
Click to expand...
Click to collapse
This is just great, ill do this and post the result!
after I finish these steps, my phone will be just like it was when i first bought it? and will I be able to update it with original HTC updates and maybe the new JB when it comes out?
THANKS ALOT!!!!!!!
Also waiting ^_^
GUARDIANBD said:
Also waiting ^_^
Click to expand...
Click to collapse
ckpv5 said:
Do you still have the fastboot folder/files that you downloaded when you unlock your
device ?
In Windows, open cmd prompt, cd to the fastboot folder where you have the fastboot.exe
example:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd\
C:\>cd fastboot
C:\fastboot>fastboot getvar version-main
version-main: 1.29.707.11
finished. total time: 0.044s
C:\fastboot>
Attached here the fastboot files & adb files in case anyone need them
Click to expand...
Click to collapse
i flashed the recovery, flashed boot img and relocked, cleared all caches and everything but now when the phone powers up (i currently have the miui on it) it shows me the lock screen, freezes for a second and phone restarts over and over again, i cant use the rom update utility when the phone is in this weird loop... and idea? (((
ChuckTesta said:
i flashed the recovery, flashed boot img and relocked, cleared all caches and everything but now when the phone powers up (i currently have the miui on it) it shows me the lock screen, freezes for a second and phone restarts over and over again, i cant use the rom update utility when the phone is in this weird loop... and idea? (((
Click to expand...
Click to collapse
If you follow the step carefully, there is no phone power up needed. You need to run the RUU in fastboot, directly after step 3.
Put your device in bootloader mode. Press power and hold it, you wll see the three buttons blinks and the device will shutdown. Release the power button, hold the volume button, the device will boot to bootloader/fastboot mode. Connect to your PC and run RUU.
---------- Post added at 08:02 PM ---------- Previous post was at 07:59 PM ----------
GUARDIANBD said:
done
Code:
c:\fastboot>fastboot getvar version-main
version-main: 1.29.720.11
finished. total time: -0.000s
now i have CWM recovery
how can i revert back to stock from there?
Click to expand...
Click to collapse
There is no 1.29.720.11 RUU available at the moment. Unless you have a nandroid backup of your stock ROM and you have the OTA files with you, there is no way to return to Stock for 1.29.720.11 currently.
ckpv5 said:
If you follow the step carefully, there is no phone power up needed. You need to run the RUU in fastboot, directly after step 3.
Put your device in bootloader mode. Press power and hold it, you wll see the three buttons blinks and the device will shutdown. Release the power button, hold the volume button, the device will boot to bootloader/fastboot mode. Connect to your PC and run RUU.
---------- Post added at 08:02 PM ---------- Previous post was at 07:59 PM ----------
There is no 1.29.720.11 RUU available at the moment. Unless you have a nandroid backup of your stock ROM and you have the OTA files with you, there is no way to return to Stock for 1.29.720.11 currently.
Click to expand...
Click to collapse
Oh my bad, The RUU said to turn on the phone and connect it so I thought is should be on, will do it in a bit and post results.
Thanks alot ckpv5!!!!
ChuckTesta said:
Oh my bad, The RUU said to turn on the phone and connect it so I thought is should be on, will do it in a bit and post results.
Thanks alot ckpv5!!!!
Click to expand...
Click to collapse
Ya.. I know, HTC's instructions always misleading, like when to unlock bootloader, it says to remove the battery...
Anybody know if its poissible to flash the Stock pd98img.zip by using adb shell, i want to return to stock but my volume up key isnt working so is there any way that i can use the adb instead of my volume up key
adilrenzu said:
Anybody know if its poissible to flash the Stock pd98img.zip by using adb shell, i want to return to stock but my volume up key isnt working so is there any way that i can use the adb instead of my volume up key
Click to expand...
Click to collapse
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse
Hey there, im in this part of the process. Right now is in writing "ZIP"... since around 1 hour. it is normal? how long it will take?
Thank you
fefetron said:
Hey there, im in this part of the process. Right now is in writing "ZIP"... since around 1 hour. it is normal? how long it will take?
Thank you
Click to expand...
Click to collapse
It shouldn´t take that long. Make sure that you are using the oem cable. That USB ports are working fine and there´s no other stuff connected to your USB ports.
glevitan said:
It shouldn´t take that long. Make sure that you are using the oem cable. That USB ports are working fine and there´s no other stuff connected to your USB ports.
Click to expand...
Click to collapse
I only have the mouse in the usb port. im using the HTC cable. i have a htc inspire 4g
fefetron said:
I only have the mouse in the usb port. im using the HTC cable. i have a htc inspire 4g
Click to expand...
Click to collapse
ok, do the following. Eject the sdcard and try again without the sdcard. Report back please. :good:
glevitan said:
ok, do the following. Eject the sdcard and try again without the sdcard. Report back please. :good:
Click to expand...
Click to collapse
Just Waiting for the device.. nothing more
im traying to install new drivers.
i´ll back
glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse
Many thanks!
I too had this boot problem on a bad flash through the Hack Kit
(my fault by the way). From power on it took 20 mins to get to the first white HTC screen . Then a further 10 mins to start normal boot.
Apart from the LONG boot, everything worked perfectly. Using TermEm I could boot into bootloader and recovery. The rom, IceColdSandwich worked perfectly in every respect but the corrupted boot was doing my head in.
Using your tutorial, I managed to flash the correct bootloader and now all is good.
hboot before was 0.85.2007
hboot after is 0.85.0024
Sorry if this is a long post but I think it is worth it. Here is a log of the fastboot process:
F:\Android\DHD\Bootloader Image\Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT11BRX11244 device
F:\Android\DHD\Bootloader Image\Fastboot>fastboot oem rebootRUU
... OKAY [ 0.375s]
finished. total time: 0.376s
F:\Android\DHD\Bootloader Image\Fastboot>fastboot flash zip PD98IMG.zip
< waiting for device >
sending 'zip' (227 KB)... OKAY [ 0.056s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
OKAY [6586.776s]
finished. total time: 6586.834s
F:\Android\DHD\Bootloader Image\Fastboot>fastboot reboot
rebooting...
finished. total time: 8.532s
F:\Android\DHD\Bootloader Image\Fastboot>
I have to say that the timings, because of the LONG boot, are completely wrong, . I was tempted to pull the plug on a number of occasions but I gave myself a talking to and went for a coffee.
The whole process took about 2 hours and I am now the delighted owner of a normal booting DHD.
To anyone who wants to attempt this procedure, the watchword is patience. Whenever you think nothing is happening, DO NOTHING!
The different stages will eventually happen just as laid out as per Glevitan. Good luck with your attempt.
Once again, many thanks.
Edit: Just an afterthought, at one stage Windows had a failed attempt at installing usb drivers that ended up as an 'Unknown Device'. Just ignore it and keep going.
Edit: I just tried again and it worked, nevermind!
Just fyi: if you get an error after flashing the ZIP, just flash it again.
Thanks! This was helpful.
glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse
Hello,
I’ve been following guides to root my phone and put a custom ROM onto it. I had no experience in doing this so I thought I would follow an idiots guide and was stupid enough not to back up the original ROM along with not reading up properly on what I was about to do… (yes you can call me names I shall accept it)
The problem I'm having is after putting the custom ROM which was ViperX3.2.0 The phone just stays stuck on the HTC one Tm with beats audio and keeps resetting it self, anyway i can fix it? or have i bricked it.
I'm a complete noobie cause I've been looking around for the past 3 days and still can't find anything (or something I can understand) :angel:
- I've wiped cache, dalvik cache and battery stats
- I go to recovery and click mount sd card nothing happens mount usb storage nothing happens.
- I don't understand next to nothing, need like android for idiots. :good:
- When phones booting up my computer recognises something but has not drivers and fails (But i had drivers and could transfer stuff too and from)
So if you can help i will love you forever
Many Thanks
RIch
I'm going to quote the instructions on the ViperX page. Have you even followed these steps?
Code:
1. Make sure your that your HBOOT is 1.31 or greater
2. Check if you CID is supported, visit http://forum.xda-developers.com/showthread.php?t=1957376 for updates. Cheers Mike
3. Unlock your bootloader via HTCDev and install a custom recovery.
4. Download the ROM and place it on your virtual SD card.
5. Do a nandroid backup!
6. Extract boot.img from ROM zip and flash it using ‘fastboot flash boot boot.img’.
7. Use 'fastboot erase cache' to avoid boot issues.
8. Go into recovery and install the ROM.
9. Please choose fullwipe if you are asked, highly recommended if you go from one rom from another rom.
10. Reboot the device and enjoy!
Did you flash the boot.img file in fastboot? fastboot flash boot boot.img followed by fastboot erase cache
tomascus said:
I'm going to quote the instructions on the ViperX page. Have you even followed these steps?
Code:
1. Make sure your that your HBOOT is 1.31 or greater
2. Check if you CID is supported, visit http://forum.xda-developers.com/showthread.php?t=1957376 for updates. Cheers Mike
3. Unlock your bootloader via HTCDev and install a custom recovery.
4. Download the ROM and place it on your virtual SD card.
5. Do a nandroid backup!
6. Extract boot.img from ROM zip and flash it using ‘fastboot flash boot boot.img’.
7. Use 'fastboot erase cache' to avoid boot issues.
8. Go into recovery and install the ROM.
9. Please choose fullwipe if you are asked, highly recommended if you go from one rom from another rom.
10. Reboot the device and enjoy!
Click to expand...
Click to collapse
Like I Said I was stupid enough not to follow instruction, where to start. First my Hboot is not 1.31 but 1.12 or somthing. No clue what CID is Trust an idiot like me to do something like this HA.
I never did a nandroid backup, I'm hitting myself for that one quite badly
Apart from that i did everything else HA yes i did do fastboot boot boot.img folowed by somthing to do with cache
Richlilrich said:
Like I Said I was stupid enough not to follow instruction, where to start. First my Hboot is not 1.31 but 1.12 or somthing. No clue what CID is Trust an idiot like me to do something like this HA.
I never did a nandroid backup, I'm hitting myself for that one quite badly
Apart from that i did everything else HA yes i did do fastboot boot boot.img folowed by somthing to do with cache
Click to expand...
Click to collapse
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
tomascus said:
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Ahh, i've done what you just said it looks like i'm getting somewhere.
looks like i'm stuck on this one.
C:\fastboot>fastboot flash zip 3.16.61.6.zip
sending 'zip' (12875 KB)...
OKAY [ 1.786s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.130s
Just keep trying 'fastboot flash zip (lalala)' until it works.
Afterwards, you need to re-unlock your bootloader with 'fastboot flash unlocktoken unlock_code.bin'
then reflash boot.img 'fastboot flash boot boot.img'
then 'fastboot erase cache'
then reflash recovery 'fastboot flash recovery (lalalaa.img)'
tomascus said:
Just keep trying 'fastboot flash zip (lalala)' until it works.
Afterwards, you need to re-unlock your bootloader with 'fastboot flash unlocktoken unlock_code.bin'
then reflash boot.img 'fastboot flash boot boot.img'
then 'fastboot erase cache'
then reflash recovery 'fastboot flash recovery (lalalaa.img)'
Click to expand...
Click to collapse
I feel bad, wasting your time still. CMD has froze should i cancel ctrl +c? so i apologise in advance
C:\fastboot>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
also 0kb?
-EDIT-
DONE IT! However i don't have no signal and can't connect to wifi? did i miss a step?
also i would love the opportunity to learn about this stuff starting from the basics, any advice on some reading i should do? i know it's a cheeky question but it's a must I think LOL
But thank you for your time.
Rich
Richlilrich said:
I feel bad, wasting your time still. CMD has froze should i cancel ctrl +c? so i apologise in advance
C:\fastboot>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
also 0kb?
-EDIT-
DONE IT! However i don't have no signal and can't connect to wifi? did i miss a step?
also i would love the opportunity to learn about this stuff starting from the basics, any advice on some reading i should do? i know it's a cheeky question but it's a must I think LOL
But thank you for your time.
Rich
Click to expand...
Click to collapse
I'm happy for you.
Man, just search and you shall find
Try reflash boot.IMG or if it doesn't work- Full wipe and reflash ROM.
Sent from my HTC One X using xda app-developers app
tomascus said:
I'm happy for you.
Man, just search and you shall find
Try reflash boot.IMG or if it doesn't work- Full wipe and reflash ROM.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Whoopsie, did fastboot flash boot boot.img didn't start up so i thought i would check recovery and earse some caches, theres an error for it to load. (a phone laying down with an exclaimation mark) so i can't do a wipe
Reflash the custom recovery
Fastboot flash recovery recover.img
Fastboot erase cache
Anyway to get the recovery back? so i can try another ROM to see if that could possibly fix the problem, just can't get into recovery D: happy my phone turns on lol however no network or can't connect to wifi
by fashing the boot did nothing but crash it more.
so i had to redo what you taught me, thank you again and i'm back to where i said i was
Flash this one again
http://db.tt/Krlm4dPs
Fastboot flash recovery recovery.img
Rename the downloaded file to recovery.img before you flash !
Mr Hofs said:
Flash this one again
http://db.tt/Krlm4dPs
Fastboot flash recovery recovery.img
Rename the downloaded file to recovery.img before you flash !
Click to expand...
Click to collapse
Many thanks, recovery up and running. now that I know this I'll try to reinstall the ROM.
Are there any reasons why I'm not getting signal or WiFi? along with that from the unlock it seem rather slow,
But I guess it's time for me to experiment, now that i know how to fix it if I mess up
Maybe because of this :
When installing the viper you get a question about the custom kernel ....
Answer with NO !
Mr Hofs said:
Maybe because of this :
When installing the viper you get a question about the custom kernel ....
Answer with NO !
Click to expand...
Click to collapse
I am sure I have done that a few times, going to try re downloading and try to reinstall. May not be installing right,
Thanks
Just signed up to say thanks Mr Hofs for the help you've posted in this thread in particular but also in many other threads I've been referring to over the last 4 hours or so. I was well on my way to brickage following a screwed up attempt to root my HOX, but thanks to you I'm now up and running again. Admittedly I'm back at square one with a non-rooted handset, but I never would've believed that would be such a happy place to be, plus I feel a tiny bit less of a noob now.
Anyway, apologies for crashing your thread Richlilrich - as you were!
Screwed up my One X
tomascus said:
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Hey Guy's,
I know this thread is old and many of you might not see this anymore but I'm sure this is where I need to be.
I have a UK Quad Core HOX and rooted fine a while ago.
I placed Cyanogen on for a while and all was running fine but it doesn't have all the tweaks I'd like so looked around for another ROM.
I came across the ViperROM and thought - Great! Exactly what I wanted, checked the reviews - All good, checked my HBoot etc... All seems fine. Went ahead and installed it through CWM (5.8.4.0) like I have done a thousand times before and went and rewrote the boot.img and got a continuous HTC boot loop. Thought hey no harm no fuss and went back into recovery to restore my most recent back-up only to find that they had all gone - My stock recovery my previous tries at other ROMS and most importantly my most recent Backup!!!!
I followed the steps above over and over again, I can re-lock my HOX, reboot into RUU and flash the 3.16.61.6 firmware (and boot img inside zip) and it still bootloop's over and over....... (I can unlock again too)
I've tried adb pushing Stock and custom ROMS to the SD card which says success in windows cmd but says no files on SDcard.
What am I doing wrong?
P.S hboot details are;
Endeveavoru PVT Ship S-ON RL
HBOOT-1.36.0000
CPLD-None
Microp-None
Radio-5.1204.163R.30
eMMC-Bootmode: disabled
CPU-bootmode: disabled
HW Secure boot:enabled
Modem path : off
Nov 16 2012, 18:32:39
Hope someone can help
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
DrUmMiSt said:
Hey Guy's,
I know this thread is old and many of you might not see this anymore but I'm sure this is where I need to be.
I have a UK Quad Core HOX and rooted fine a while ago.
I placed Cyanogen on for a while and all was running fine but it doesn't have all the tweaks I'd like so looked around for another ROM.
I came across the ViperROM and thought - Great! Exactly what I wanted, checked the reviews - All good, checked my HBoot etc... All seems fine. Went ahead and installed it through CWM (5.8.4.0) like I have done a thousand times before and went and rewrote the boot.img and got a continuous HTC boot loop. Thought hey no harm no fuss and went back into recovery to restore my most recent back-up only to find that they had all gone - My stock recovery my previous tries at other ROMS and most importantly my most recent Backup!!!!
I followed the steps above over and over again, I can re-lock my HOX, reboot into RUU and flash the 3.16.61.6 firmware (and boot img inside zip) and it still bootloop's over and over....... (I can unlock again too)
I've tried adb pushing Stock and custom ROMS to the SD card which says success in windows cmd but says no files on SDcard.
What am I doing wrong?
P.S hboot details are;
Endeveavoru PVT Ship S-ON RL
HBOOT-1.36.0000
CPLD-None
Microp-None
Radio-5.1204.163R.30
eMMC-Bootmode: disabled
CPU-bootmode: disabled
HW Secure boot:enabled
Modem path : off
Nov 16 2012, 18:32:39
Hope someone can help
Click to expand...
Click to collapse
Would like to add that I would prefer Viper to stock but stock would help for now
Before going for RUU and stuff, try any other roms.
I'd say do this :
Flash TWRP - Better than CWM anyday.
Go to recovery. Mount USB. Copy Viper (or any other) rom to phone.
Reboot to bootloader.
Flash boot.img.
Fastboot erase cache.
Go to recovery.
Clean install ROM.
Reboot and wait for it. First boot takes pretty long sometimes.
There is no better recovery, a recovery is personal. I'm using CWM now for 2 years....never had a problem with that.....
Now the issue.
How to copy it is in the post above, however before you install the rom you need to make a real good full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the rom...and ofcourse flash the boot.img from the rom.zip
The option to mount in CWM is under mounts and storage copy the rom.zip over and unmount.
The way i personally follow is :
Flash the boot.img (fastboot, bootloader mode) then enter the recovery and follow the above....make sure you unplug the usb cable BEFORE installing the rom.zip
As you can see in the picture the phone boots up to this screen. A friend of mine bought an HTC One on ebay and he found out it was rooted/unlocked so he went to put it back to stock and may have bricked the device while doing so.
EDIT: so I am able to use fastboot, but not adb because I can't get into Windows. Flashing the stock Verizon RUU I found still doesn't get me anywhere though.
Is there any hope for this device? Thanks in advance!
You have to select bootloader to get to the recovery option. What kind of computer are you using and whats it running?
cmlusco said:
You have to select bootloader to get to the recovery option. What kind of computer are you using and whats it running?
Click to expand...
Click to collapse
Yea I saw that after messing around with it some more. It is Windows 7 x64.
I tried the one at the bottom of the page as I can't find one anywhere else. I also used the commands at the bottom to try and flash it.
http://www.htc1guru.com/downloads/ruu-zip-downloads/
When you go to device manager on your pc with the phone pluged in and in fastboot mode, does it show android phone or unknown device? Try using these drivers http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
You need a signed ruu which you can get here http://vzw1files.dyndns.org/RUUs/2....2_NV_VZW_3.71_002_release_341019_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip file.zip
May fail with flush error do above command again.
fastboot reboot
cmlusco said:
When you go to device manager on your pc with the phone pluged in and in fastboot mode, does it show android phone or unknown device? Try using these drivers http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
You need a signed ruu which you can get here http://vzw1files.dyndns.org/RUUs/2....2_NV_VZW_3.71_002_release_341019_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip file.zip
May fail with flush error do above command again.
fastboot reboot
Click to expand...
Click to collapse
OK cool I will try that once it downloads. It shows "My HTC" in the device manager. Also with the fastboot devices command it does give me the device ID.
EDIT: That worked! Thanks a lot for the RUU file, as I could not find that anywhere.
Hello. A friend of mine has the same problem. She tried to flash this RUU: "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted" but the phone doesn't boot. Here is more info about the problem: http://forum.xda-developers.com/showthread.php?t=2688936
Can she flash the RUU posted here?
This is what the hboot says:
Unlocked
m7_wlv pvt ship s-off rh
cid-11111111
hboot 1.54.0000
radio 1.12.42.0906
opendsp v31.120.274.0617
os 1.10.605.10
Thank you very much.
She can, but since she is s-off, its better to flash the decrypted one. http://vzw1files.dyndns.org/RUUs/2.10.605.1/PN07IMG_M7_WL_JB_50_VZW_2.10.605.1_DECRYPT.zip
cmlusco said:
She can, but since she is s-off, its better to flash the decrypted one.
Click to expand...
Click to collapse
First, thank you very much. She changed the CID to VZW__001. That's not a problem, right?
Does the CID and MID have to be compatible with the RUU? She has this MID: PN0731000.
Downloading this RUU, will report back.
Again, thank you.
Yes the cid and mid need to match the ruu. What you have now are the correct ones. However 11111111 is super cid, which would have also worked.
cmlusco said:
Yes the cid and mid need to match the ruu. What you have now are the correct ones. However 11111111 is super cid, which would have also worked.
Click to expand...
Click to collapse
Hello again. Before we try to flash the RUU, I would like to ask you the steps to do it. This is what we gonna do:
1. Download RUU
2. Rename to "ruu.zip" (Optional)
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
And that's it? Nothing else is needed, right?
EDIT: we flashed the RUU. Now the phone boots always in fastboot. No matter what option we choose, the phone does nothing and goes back to fastboot. On the bottom of hboot there is a new line in red: "Active cmdline overflow! (1073 Bytes)"
Ok try changing the cid back to 11111111 super cid, then run the ruu again and see what happens. Before doing both, use the cmd
fastboot erase cache
cmlusco said:
Ok try changing the cid back to 11111111 super cid, then run the ruu again and see what happens. Before doing both, use the cmd
fastboot erase cache
Click to expand...
Click to collapse
Hello. We just did it, and still the same problem. We were reading that some people solved this by doing a downgrade to hboot 1.44. But I don't want to make this problem worse.
You can try it, its worth a shot. Just flash an older ruu. http://vzw1files.dyndns.org/RUUs/. Dont remember which one goes with 1.44
cmlusco said:
You can try it, its worth a shot. Just flash an older ruu. Dont remember which one goes with 1.44
Click to expand...
Click to collapse
You can't be more kind. We made a downgrade, and now we can use CWM again. (We did the downgrade before reading your post, so we didn't use an older RUU) Now thinking hwat should be the next step: flashing a ROM (custom or stock, mounting a pendrive) or flashing an older RUU or anything else. Again, dude, you're awesome.
I'm stuck in a similar situation and any help would be appreciated so I don't screw this up. I can get into the bootloader but not into recovery (gets to the first TWRP screen then reboots). Safe mode works fine too.
Win7 64bit
S-off
Rooted
Stock ROM
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW-001
HBOOT-1.54.0000
RADIO-1.12.42.0731
OS-1.10.605.8
I can get into ADB. Would just like to know if I need to flash a new RUU or should I flash updated TWRP first? And the proper commands so I don't botch this.
Any help would be greatly appreciated.
Thanks
I would try reflashing twrp first. http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img
fastboot erase cache
fastboot flash recovery recovery.img
cmlusco said:
I would try reflashing twrp first.
fastboot erase cache
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Didn't work. Got to the TWRP splash screen and back into the bootloop again.
Ok then i would do an ruu. http://vzw1files.dyndns.org/RUUs/
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip (may fail with flush error, just do the cmd again)
fastboot reboot
Hi,
Similar problem here.
This is my situation:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
CID: VZW__001
MID: PN0731000
Only fastboot. Can't access to recovey (CWM). Can't access to OS, so no adb.
Every time I try to RUU it gives the "Signature verify fail" message.
So, I tried encrypted ROMs (those at vzw1files. dyndns. org), and I could go a step forward; but the flashing hungs up after giving this messages:
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
Thanks in advance, I hope I didn't screw it up.
The problem is nicouy that you are s-on, and on the newest kk firmware. An s-on phone will not allow you to "downgrade" firmware, and we do not yet have the latest ruu available, at least to my knowledge. So your kind of screwed right now untill we get our hands on a kk ruu.
Tried to install latest RUU file and failed. Now phone is stuck on htc logo with black screen only when plugged in pc. Also when unplugged, goes to bootload with no options and only shows RUU.
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Need help ASAP
Thanks
gmdiesel05 said:
Tried to install latest RUU file and failed. Now phone is stuck on htc logo with black screen only when plugged in pc. Also when unplugged, goes to bootload with no options and only shows RUU.
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Need help ASAP
Thanks
Click to expand...
Click to collapse
did you flash the ruu.zip 2 times .. the first flash only updates the hboot
clsA said:
did you flash the ruu.zip 2 times .. the first flash only updates the hboot
Click to expand...
Click to collapse
yes the second time it said device not found! In cmd window, i type adb devices and none there
This is what happens, and hangs there
C:\Users\Desktop\platform-tools>fastboot oem rebootRUU
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.072s]
finished. total time: 0.073s
C:\Users\Cedrik\Desktop\platform-tools>fastboot flash zip RUU-HTC_One_M8_GPE_5.0
.1-3.11.1700.5.zip
gmdiesel05 said:
yes the second time it said device not found! In cmd window, i type adb devices and none there
Click to expand...
Click to collapse
it has nothing to do with adb you phone is in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
what file are you trying to flash ?
clsA said:
it has nothing to do with adb you phone is in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
what file are you trying to flash ?
Click to expand...
Click to collapse
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. wont let me type in cmd
gmdiesel05 said:
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. now i cant flash a 2nd time
Click to expand...
Click to collapse
are you s-off ? is your phone a GSM M8 ?
Did you try the other method, just renaming the RUU to 0p6bimg.zip (<a 0 (Zero) not a capital o (O), naturally...)
What error do you get when the flashing of the RUU fails?
Like mentioned by clsA said, adb devices won't work in fastboot mode, it should be "fastboot devices" to check if it's connected
---------- Post added at 06:20 AM ---------- Previous post was at 06:18 AM ----------
gmdiesel05 said:
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. wont let me type in cmd
Click to expand...
Click to collapse
You changed CID and MID I take it?
CID - GOOGL001
MID - 0P6B17000
Would have helped a bit if we had an idea what the error was.
clsA said:
are you s-off ? is your phone a GSM M8 ?
Click to expand...
Click to collapse
sure is in s-off. and it is a GSM. Also its in GOOGL001 CID
I made sure I followed instruction properly so I dont screw up.
clsA said:
are you s-off ? is your phone a GSM M8 ?
Click to expand...
Click to collapse
Yeah he said his phone is S-OFF in OP
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Click to expand...
Click to collapse
gmdiesel05 said:
sure is in s-off. and it is a GSM. Also its in GOOGL001 CID
I made sure I followed instruction properly so I dont screw up.
Click to expand...
Click to collapse
just use the fastboot flash zip ruu.zip command again
clsA said:
just use the fastboot flash zip ruu.zip command again
Click to expand...
Click to collapse
I just closed cmd window and restared. redid fastboot flash zip ruu.zip and seems to hang still
hope i didnt screw this up....
gmdiesel05 said:
I just closed cmd window and restared. redid fastboot flash zip ruu.zip and seems to hang still
hope i didnt screw this up....
Click to expand...
Click to collapse
try and unplug the phone from the pc and hold volume up + power for 10 seconds
when the phone reboots try the ruu again .. if the bootloader says RUU in red don't do the fastboot oem rebootRUU command just go straight to flashing
The RUU flashes very slow are you waiting long enough ?
clsA said:
try and unplug the phone from the pc and hold volume up + power for 10 seconds
when the phone reboots try the ruu again .. if the bootloader says RUU in red don't do the fastboot oem rebootRUU command just go straight to flashing
The RUU flashes very slow are you waiting long enough ?
Click to expand...
Click to collapse
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything.
maybe im not waiting long enough?
ok heres the latest
FAILED <command write failed <No such device or address>>
gmdiesel05 said:
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything. Sorry you lost me here
maybe im not waiting long enough?
Click to expand...
Click to collapse
you have the file renamed just copy it to your Ext - sdcard and let the bootloader flash it
don't forget to delete or rename it on the sdcard before you reboot again or it will flash it again
ok heres the latest
FAILED <command write failed <No such device or address>>
gmdiesel05 said:
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything.
maybe im not waiting long enough?
Click to expand...
Click to collapse
Yeah this pretty much tells me you didn't properly read the guide to converting your device to GPE. When I mentioned "the 0p6bimg.zip" method I kind of figured you'd know to place it on SD Card and reboot into bootloader so that the bootloader can pick up the .zip file and flash it from there. Flashing in from RUU sort of gave it away there
Method 1
No computer required. Everything else still required. s-off, super CID/gpe CID etc..
1. Rename the RUU zip file 0p6bimg.zip (if your hboot is looking for a different name then rename it to whatever it's looking for)
2. Place the zip on your external SD card
3. Power off your phone
4. Boot into Hboot (hold down vol down as you power on the device)
5. it will load the zip and ask you if you want to proceed
6. Say yes
7. Wait
8. Profit
Click to expand...
Click to collapse
Didn't say anything about flashing it in RUU mode.
BerndM14 said:
Yeah this pretty much tells me you didn't properly read the guide to converting your device to GPE. When I mentioned "the 0p6bimg.zip" method I kind of figured you'd know to place it on SD Card and reboot into bootloader so that the bootloader can pick up the .zip file and flash it from there. Flashing in from RUU sort of gave it away there
Didn't say anything about flashing it in RUU mode.
Click to expand...
Click to collapse
i used
Method 2
ADB/FastBoot Method
Code:
adb reboot bootloader
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
you will the following message:
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Just run the same command again:
Code:
fastboot flash zip RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
Code:
fastboot reboot