Database Develop

URGENT Guys, my device is down !

Guys I am trying to update the device from original ROM to official OTA ICS 4.0 with sense 3.6
I've downloaded the ROM successfully, but when the device restarted to to install the update it shows the bootloader menu !
my device is s-on with recovery installed.
SOMEONE HELP ME !

micho119 said:
Guys I am trying to update the device from original ROM to official OTA ICS 4.0 with sense 3.6
I've downloaded the ROM successfully, but when the device restarted to to install the update it shows the bootloader menu !
my device is s-on with recovery installed.
SOMEONE HELP ME !
Click to expand...
Click to collapse
I think i read your post regarding the same yesterday.
you did not that you have a custom recovery installed...
in this case you will not be able to flash the ruu as you are required to be stock with s-on
head over to arhd thread to get the closest experience to the stock rom.
download the arhd rom, flash in recovery

letmedanz said:
I think i read your post regarding the same yesterday.
you did not that you have a custom recovery installed...
in this case you will not be able to flash the ruu as you are required to be stock with s-on
head over to arhd thread to get the closest experience to the stock rom.
download the arhd rom, flash in recovery
Click to expand...
Click to collapse
But I remember that I've did this before and reinstalled a stock ROM using RUU exe file, can't I do this now?
Does WWE ROM have Arabic language?
I am very depressed because of this problem, I want to have official HTC ICS ROM.

micho119 said:
But I remember that I've did this before and reinstalled a stock ROM using RUU exe file, can't I do this now?
Does WWE ROM have Arabic language?
I am very depressed because of this problem, I want to have official HTC ICS ROM.
Click to expand...
Click to collapse
In order to install the ICS OTA after it has been downloaded, you will need to restore the stock HTC recovery and then relock your bootloader.

tpbklake said:
In order to install the ICS OTA after it has been downloaded, you will need to restore the stock HTC recovery and then relock your bootloader.
Click to expand...
Click to collapse
thanks tpbklake, i could relock the bootloader but I don't know how to have the HTC Recovery back instead of the current one, any guide to do this?

am quoting tpbklake here, listen to him, he's the best around here
Grab a RUU and extract the recovery.img file from the ROM.zip. Then flash the recovery image in FASTBOOT USB mode using
fastboot flash recovery recovery.img

micho119 said:
thanks tpbklake, i could relock the bootloader but I don't know how to have the HTC Recovery back instead of the current one, any guide to do this?
Click to expand...
Click to collapse
Extract it from an official RUU/ROM.zip file and then flash it in FASTBOOT USB mode using the following command:
fastboot flash recovery [path to recovery.img]

micho119 said:
thanks tpbklake, i could relock the bootloader but I don't know how to have the HTC Recovery back instead of the current one, any guide to do this?
Click to expand...
Click to collapse
tpbklake said:
Extract it from an official RUU/ROM.zip file and then flash it in FASTBOOT USB mode using the following command:
fastboot flash recovery [path to recovery.img]
Click to expand...
Click to collapse
LOL. beat you to it

tpbklake said:
Extract it from an official RUU/ROM.zip file and then flash it in FASTBOOT USB mode using the following command:
fastboot flash recovery [path to recovery.img]
Click to expand...
Click to collapse
can't thank you enough man !, can you do me a final favor and send me a zip file with the recovery img? or at least give me a link to original rom because I am completely lost?
Thanks again mate.

micho119 said:
can't thank you enough man !, can you do me a final favor and send me a zip file with the recovery img? or at least give me a link to original rom because I am completely lost?
Thanks again mate.
Click to expand...
Click to collapse
Try the attached file in this post
http://forum.xda-developers.com/showpost.php?p=25088846&postcount=4

tpbklake said:
Try the attached file in this post
http://forum.xda-developers.com/showpost.php?p=25088846&postcount=4
Click to expand...
Click to collapse
when i am trying to flash anything it gives me the message
<bootloader> signature checking...
FAILED (remote: signature verify fail)
any idea on this?

micho119 said:
when i am trying to flash anything it gives me the message
<bootloader> signature checking...
FAILED (remote: signature verify fail)
any idea on this?
Click to expand...
Click to collapse
Did you already relock the bootloader? You need to flash the stock recovery first, then relock the bootloader.
Did you extract the recovery.img file from the PG32IMG.zip file or are you just trying to have the bootloader flash the PG32IMG.zip?
The signature checking failure leads me to believe that the bootloader is locked/relocked.

tpbklake said:
Did you already relock the bootloader? You need to flash the stock recovery first, then relock the bootloader.
Did you extract the recovery.img file from the PG32IMG.zip file or are you just trying to have the bootloader flash the PG32IMG.zip?
The signature checking failure leads me to believe that the bootloader is locked/relocked.
Click to expand...
Click to collapse
I've flashed the recovery, relock the bootloader using fastboot oem lock, downloaded the update OTA, when it turns off the bootloader screen is showing up without continuing the update !!, any advice?

micho119 said:
I've flashed the recovery, relock the bootloader using fastboot oem lock, downloaded the update OTA, when it turns off the bootloader screen is showing up without continuing the update !!, any advice?
Click to expand...
Click to collapse
Did it update the bootloader to 2.02.0002 or is it still 2.00.0000?

tpbklake said:
Did it update the bootloader to 2.02.0002 or is it still 2.00.0000?
Click to expand...
Click to collapse
Still 2.00.0000

micho119 said:
Still 2.00.0000
Click to expand...
Click to collapse
So there was no indication on the HBOOT screen to press the Volume Up to apply the update or anything like that?

no, nothing at all like this !

micho119 said:
no, nothing at all like this !
Click to expand...
Click to collapse
How did you end up flashing the recovery? Did you use the PG32IMG.zip and copy it to your sd card or did you extract the recovery.img file and manually flash it?
If you used the PG32IMG.zip file then that probably changed the mainver value and that's why the OTA is not running.

Well guess what, my device is now crashed !, it is stock at the green HTC logo, I can not access anything except for the bootloader !.
i've installed the Android Revolution HD but it didn't work as well, my device is now in mess.

micho119 said:
Well guess what, my device is now crashed !, it is stock at the green HTC logo, I can not access anything except for the bootloader !.
i've installed the Android Revolution HD but it didn't work as well, my device is now in mess.
Click to expand...
Click to collapse
You never did answer my question about how you flashed the HTC stock recovery.
Anyway, If you unlocked your bootloader and reinstalled a custom Recovery and then attempted to install ARHD, did you manually extract and flash the boot.img file in FASTBOOT USB mode?
That may be all you need to do to get the phone booted.

Problem with manually upgrading firmware to 1.31.651.2

Hi, I've been trying to manually upgrade my firmware to 1.31.651.2 using fastboot but I keep getting an error in the command prompt saying "error: cannot load 'firmware.zip': Unknown error"
I'm s-off (used revone) and my bootloader is unlocked. I've redownloaded the file multiple times, but it always gets stuck at that point.

sai5o4 said:
Hi, I've been trying to manually upgrade my firmware to 1.31.651.2 using fastboot but I keep getting an error in the command prompt saying "error: cannot load 'firmware.zip': Unknown error"
I'm s-off (used revone) and my bootloader is unlocked. I've redownloaded the file multiple times, but it always gets stuck at that point.
Click to expand...
Click to collapse
Did you rename the firmware? What commands are you using in fastboot?
Sent from my jacked HTC One!!

celder187 said:
Did you rename the firmware? What commands are you using in fastboot?
Sent from my jacked HTC One!!
Click to expand...
Click to collapse
Yeah, I renamed the firmware and put it in the folder with fastboot. I also have another copy with the original name there as well.
From bootloader, I do fastboot oem rebootRUU, fastboot flash zip firmware.zip <--where I get the error. I've tried doing fastboot flash zip (original file name) but the same error occurs.

sai5o4 said:
Yeah, I renamed the firmware and put it in the folder with fastboot. I also have another copy with the original name there as well.
From bootloader, I do fastboot oem rebootRUU, fastboot flash zip firmware.zip <--where I get the error. I've tried doing fastboot flash zip (original file name) but the same error occurs.
Click to expand...
Click to collapse
When you are in bootloader does it say FastbootUSB when you connect the phone?

Yes, it does.

Please help, possible brick after following guide to flash firmware

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

[Q] I Have Completely Bork'd My Phone

After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams

misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
You've had an htc one for two years?

BableMan said:
You've had an htc one for two years?
Click to expand...
Click to collapse
No. Started out with my Nexus S, then moved to a Nexus 4, then gave that to my wife and got an HTC One. I love this phone so much I wish I'd had it for two years already, but no.
Do you have any idea of a new path I can try?

misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Sent from my HTC One using Tapatalk

Delgra said:
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Click to expand...
Click to collapse
I have tried both actually. I used Hansoon2000's (I'm at work so hopefully I'm referencing that correctly) all in one toolkit to try to flash the RUU.zip file back to the device. It fails while transferring to the device every single time.
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
How do I flash the RUU.zip from the command line? I have tried using "Install zip from sideload" but I get a Status Error 7 when trying to flash ROM.zip files, and I have tried using ADB PUSH to push the ROM.zip over to the phone but since there's no file structure it doesn't really ever end up anywhere on the phone. (I'm using ROM.zip generically here for my CM ROMs, not RUU) Is there a command line or ADB function to flash the RUU.zip file that I'm not aware of?
Thanks,
Chris

misterasset said:
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
Thanks,
Chris
Click to expand...
Click to collapse
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.

nkk71 said:
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.
Click to expand...
Click to collapse
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris

misterasset said:
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris
Click to expand...
Click to collapse
Please:
1- date of bootloader
2- a "fastboot getvar all" (remove IMEI and s/n)
3- link to the RUU you are trying to use.
Don't forget pressing the little thanks button for people who have helped

No offense but it sounds as if you simply aren't running an ruu.zip correctly. I'm not understanding all this hensonn2000 or toolkit talk that you have going on. You flash ruu.zip while the phone is in fastboot oem RUU mode. Not that complicated. Also the error 155 was the bootloader being unlocked if I recall correctly. You have to relock it before flashing or running the appropriate RUU. Specially if youre s-on.

Thanks guys. I ended up getting it all working. I did not have the Bootloader relocked and that was why the RUU kept failing.
Thanks again for the extra direction,
Chris

RUU.exe giving error 155

hi all.
need help.
i wanted to revert back to stock.
followed htc1guru tutorial.
downloaded ruu.exe.
i downgraded to hboot 1.44 write my cid back to htc__044 and on s-off
but after executing .exe im getting error 155.
googled it most of the people posted because they having hboot 1.55, so couldnt find any solution for my case.
any help? thanks a lot.
good day

shdin271 said:
hi all.
need help.
i wanted to revert back to stock.
followed htc1guru tutorial.
downloaded ruu.exe.
i downgraded to hboot 1.44 write my cid back to htc__044 and on s-off
but after executing .exe im getting error 155.
googled it most of the people posted because they having hboot 1.55, so couldnt find any solution for my case.
any help? thanks a lot.
good day
Click to expand...
Click to collapse
try this method
This is the instructions posted by Scotty85
I'm just re-posting it for you
Quote:
http://androidforums.com/t-one-all-t...ml#post5864243
Quote:
here is how you extract rom.zip:
Quote:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,your done with it.
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Quote:
here are some directions to flash "rom.zip"
if you're working with a booted,operational phone,you can flash the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboot oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. don't interrupt it while the cmd window shows its writing's,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you don't have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse

clsA said:
try this method
Click to expand...
Click to collapse
thanks for the reply. i think i missed something in bootloader status (relocked locked)
according to this tutorial http://forum.xda-developers.com/showthread.php?t=2541082, my bootloader should be locked not relocked. i tried it with relocked.
havent tried it yet, but ill hold on for a few days testing my new radio. if the problem persists, ill use this method. again thanks bro.

shdin271 said:
thanks for the reply. i think i missed something in bootloader status (relocked locked)
according to this tutorial http://forum.xda-developers.com/showthread.php?t=2541082, my bootloader should be locked not relocked. i tried it with relocked.
havent tried it yet, but ill hold on for a few days testing my new radio. if the problem persists, ill use this method. again thanks bro.
Click to expand...
Click to collapse
locked and relocked are the same thing