Hello everyone,
I have a HTC One which I want to unroot. I downloaded several Ruu's, but al of them gave the same error. The relocking of the bootloader was succesful. But then the story begins. It is first trying to "Update signature" (Not sure for the exact English words, because its in dutch). Then an error window comes up witch says that i have to find the right update tool and should try again.
I tried several times, but with the same result. I first tried to unroot from Android Revolutioin HD 12.0, then I tried a different rom to unroot from, Vanilla Rootbox. I also removed the HTC drivers and installed them again.
When I try to unlock the bootloader again, the phone runs into a bootloop. So my phone is useless at the moment.
edit: Oh, if forgot: when in bootloop, I can enter bootloader/recovery with vol down/power, but in recovery i cant acces my internal sd-card...
Can someone please help me?
What is your CID? You have to use the correct RUU for your phone unless you're supercid or s-off. Any other will fail.
iElvis said:
What is your CID? You have to use the correct RUU for your phone unless you're supercid or s-off. Any other will fail.
Click to expand...
Click to collapse
According to the guide it was sufficient to pick any Europe Ruu. But my cid was HTC__E11 i thought....
Which guide are you using?
iElvis said:
Which guide are you using?
Click to expand...
Click to collapse
It's a dutch one.
Translated summary:
- Download the right Ruu, it has to have HTC Europe in the name link
- Download/extract mini sdk link
- Boot in fastboot
- CMD: fastboot oem lock
- Run ruu.exe, follow instructions
wybren said:
It's a dutch one.
Translated summary:
- Download the right Ruu, it has to have HTC Europe in the name link
- Download/extract mini sdk link
- Boot in fastboot
- CMD: fastboot oem lock
- Run ruu.exe, follow instructions
Click to expand...
Click to collapse
That's the correct procedure. Did you try the 1.29 Europe RUU? Did you ever change your CID?
iElvis said:
That's the correct procedure. Did you try the 1.29 Europe RUU? Did you ever change your CID?
Click to expand...
Click to collapse
I tried the 1.28.401.7_ and the 1.20.401.1
Why/how should I try to change my CID?
Can't find a proper 1.29 ruu file. Can somebody please help me out? Im even willing to pay for it :crying: PM me
You need S-OFF to flash an older RUU as otherwise you cannot downgrade the bootloader
EddyOS said:
You need S-OFF to flash an older RUU as otherwise you cannot downgrade the bootloader
Click to expand...
Click to collapse
That's a good point. OP, what's on your bootloader screen? Did you ever flash the new firmware?
iElvis said:
That's a good point. OP, what's on your bootloader screen? Did you ever flash the new firmware?
Click to expand...
Click to collapse
Now my bootloader screen says:
Tampered, unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
April 20 2013 15:46:23:14316
As last I flashed Android Revoluiton HD 12.0, and after that the latest Vanilla Rootbox..
When I open custom recovery, it begins with saying:
ClockworkMod Recovery v6.0.3.0
E: Can't mount /cach/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Afterwards I tried to push a rom zipfile using ADB, first I tried to push to /data/media/0/:
"Failed to copy 'rom.zip' to '/data/media/0/': Is a directory"
Then It succeed using /data/media/ but when I tried to flash, it said "Can't mount /sdcard/"
So is trying to S-off the still the right way?
I suspect the RUU is failing because you've got a 4.2.2 rom and you've been trying to flash 4.1.2 RUUs, so it's failing the version check even though you have your original hboot. Try flashing a stock 4.1.2 rom, and if that doesn't work, try s-off.
iElvis said:
I suspect the RUU is failing because you've got a 4.2.2 rom and you've been trying to flash 4.1.2 RUUs, so it's failing the version check even though you have your original hboot. Try flashing a stock 4.1.2 rom, and if that doesn't work, try s-off.
Click to expand...
Click to collapse
I have no clue how to flash a rom right now, see my last post. Can't flash anything in recovery...
wybren said:
I have no clue how to flash a rom right now, see my last post. Can't flash anything in recovery...
Click to expand...
Click to collapse
Just download the ruu.exe file to your PC, turn oo your phone on and connect it to your PC (driver should be installed).
Just double klick at the ruu.exe file and wait ... you have to confirm some popups ..
But i´m not shure if it is possible to downgrade the hboot even with s-off anybody tried already?
Bajo76 said:
Just download the ruu.exe file to your PC, turn oo your phone on and connect it to your PC (driver should be installed).
Just double klick at the ruu.exe file and wait ... you have to confirm some popups ..
But i´m not shure if it is possible to downgrade the hboot even with s-off anybody tried already?
Click to expand...
Click to collapse
I already tried two ruu's, 1.20.401.1 and 1.28.401.7, with the same result: Stops when it is trying to update the signatures, and then says I have to look for a more proper ruu...
Ok, so follow this instructions to get s-off.
here
when done flash the ruu.exe you already downloaded again
Bajo76 said:
Ok, so follow this instructions to get s-off.
here
when done flash the ruu.exe you already downloaded again
Click to expand...
Click to collapse
Already at the first step I got this:
c:\adt\sdk\platform-tools>adb push revone /data/local/tmp/
failed to copy 'revone' to '/data/local/tmp/': Is a directory
What dooes it says if you type
adb shell
?
Bajo76 said:
What dooes it says if you type
adb shell
?
Click to expand...
Click to collapse
It shows an '~ #' and a blinking '_'
ok download this and save it to folder:
c:\adt\sdk\platform-tools
Enable usb-debugging on phone (developer tools)
Boot your phone normaly (Dont turn it off) and connect it through usb wih your pc.
Then type the command again:
adb push revone /data/local/tmp/
Related
Not sure if I am in the right place to ask this question, well, i'll ask anyway.
I unlocked my bootloader using Revolutionary. I now need to revert to stock for warranty. I downloaded the INDIA RUU from goo manager.
I managed to replace the Revolutionary HBOOT by changing mainver. However, my radio is not getting replaced, no matter what I try. As a result, my phone bootloops though the RUU install was successful. So I had to revert to Revolutionary by installing WWE ASIA RUU. This was successful because the Radios are the same ie 3805.04.03.27_M.
I am currently on
HBOOT - 6.13.1002
Radio-3805.04.03.27_M
How can I go back to HBOOT 1.13 and Radio 38.02.01.11_M?
HBOOT - 6.13.1002 is still Revolutionary HBOOT?
I think that this is the easiest way to get stock bootloader and rom back. You need to find the latest WWE ASIA RUU for that.
Is that this one: RUU_VIVO_SENSE30_S_hTC_Asia_WWE_3.09.707.1_Radio_20.4802.30.0822U_3822.10.08.28_M_release_226940_signed.exe ?
If you have the latest RUU succesfully installed including the HBOOT, you're OK.
Inferi0r said:
HBOOT - 6.13.1002 is still Revolutionary HBOOT?
I think that this is the easiest way to get stock bootloader and rom back. You need to find the latest WWE ASIA RUU for that.
Is that this one: RUU_VIVO_SENSE30_S_hTC_Asia_WWE_3.09.707.1_Radio_20.4802.30.0822U_3822.10.08.28_M_release_226940_signed.exe ?
If you have the latest RUU succesfully installed including the HBOOT, you're OK.
Click to expand...
Click to collapse
thanks for the reply...but i don't think i explained my problem properly.
I first downloaded PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager. This is India RUU, but Froyo. This was what was installed on my phone first.
I first changed the mainver and renamed this RUU to PG32IMG.zip and let the bootloader install it. The HBOOT flashed perfectly, so my HBOOT became 1.09 but my radio was stuck at the same. This led the phone to bootloop because of incompatible radios.
So i tried extracting radio.img from PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip and renamed to PG32IMG.zip and bootloader flash it. But it does not flash. My question is how do I replace the current radio with 38.02.01.11_M? The current radio is 3805.04.03.27_M.
craynet said:
thanks for the reply...but i don't think i explained my problem properly.
I first downloaded PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager. This is India RUU, but Froyo. This was what was installed on my phone first.
I first changed the mainver and renamed this RUU to PG32IMG.zip and let the bootloader install it. The HBOOT flashed perfectly, so my HBOOT became 1.09 but my radio was stuck at the same. This led the phone to bootloop because of incompatible radios.
So i tried extracting radio.img from PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip and renamed to PG32IMG.zip and bootloader flash it. But it does not flash. My question is how do I replace the current radio with 38.02.01.11_M? The current radio is 3805.04.03.27_M.
Click to expand...
Click to collapse
If you currently have a GB ROM on your phone you also have a GB radio. If you attempt to flash the Froyo RUU you have downloaded, you are going to brick your phone because you cannot flash an older Froyo radio over a GB radio. This is a sure way to brick your phone.
fastboot....
tpbklake said:
If you currently have a GB ROM on your phone you also have a GB radio. If you attempt to flash the Froyo RUU you have downloaded, you are going to brick your phone because you cannot flash an older Froyo radio over a GB radio. This is a sure way to brick your phone.
Click to expand...
Click to collapse
yeah, you are right...i now remember that this will brick my phone, a risk not worth taking.
just a quick question, my phone is factory unlocked (the user I bought if from bought it on amazon.de) and currently I have an ICS rom with ICS radio, can I flash the GB RUU and then update to oficial ICS?
Do I still have to make goldcards and stuff?
skinniezinho said:
just a quick question, my phone is factory unlocked (the user I bought if from bought it on amazon.de) and currently I have an ICS rom with ICS radio, can I flash the GB RUU and then update to oficial ICS?
Do I still have to make goldcards and stuff?
Click to expand...
Click to collapse
With Revolutionary S-OFF, the RUU will not successfully overwrite the HBOOT and you will end up with a phone that won't boot past the HTC screen.
You would need to follow this procedure to allow the GB RUU to run successfully:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
This would leave you with a stock, unrooted phone. You woud be able to use HTCDEV.com to ulock the bootloader so you could root, but you are much better off staying S-OFF and using custom ICS ROMs.
tpbklake said:
With Revolutionary S-OFF, the RUU will not successfully overwrite the HBOOT and you will end up with a phone that won't boot past the HTC screen.
You would need to follow this procedure to allow the GB RUU to run successfully:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
This would leave you with a stock, unrooted phone. You woud be able to use HTCDEV.com to ulock the bootloader so you could root, but you are much better off staying S-OFF and using custom ICS ROMs.
Click to expand...
Click to collapse
Well I was stupid enought to flash the RUU so ended like you said.
I have macOs, downloaded fastboot and did fine till 2d.
I have the rom.zip but when I try to do
"fastboot flash hboot rom.zip"
it says:
cannot load 'rom.zip'
and the same if I try the vivo_downgrade.img
But if I do fastboot reboot-bootloader
It works..any suggestions?
exnerjan said:
This procedure is tested only AplhaRevX.
1. Install RUU ROM from: http://forum.xda-developers.com/show....php?t=1033922
2. Downgrade HBOOT
2a. download this file: http://alpharev.nl/vivo_downgrade.img
2aa. Connect your phone to the USB
2b.Turn your phone into FastBoot not to HBOOT!!! (VOL DOWN + POWER Button)
2c. Install over fastboot: cmd: "fastboot flash hboot vivo_downgrade.img" (you must install sdk tools)
2d. still fastboot cmd: fastboot reboot-bootloader
3. Start Installation RUU ROM, but DON´T INSTALL !!!!
3a. go tu C:\Users\%username%\AppData\Local\Temp and at last folder find rom.zip
3b. open it, and copy tu folder sdk hboot and instal the same as step 2c.
Click to expand...
Click to collapse
skinniezinho said:
Well I was stupid enought to flash the RUU so ended like you said.
I have macOs, downloaded fastboot and did fine till 2d.
I have the rom.zip but when I try to do
"fastboot flash hboot rom.zip"
it says:
cannot load 'rom.zip'
and the same if I try the vivo_downgrade.img
But if I do fastboot reboot-bootloader
It works..any suggestions?
Click to expand...
Click to collapse
Make sure that you have vivo_downgrade.img in the same folder where you run fastboot from.
Also, you cannot flash a ROM.zip file using the command fastboot flash hboot.
tpbklake said:
Make sure that you have vivo_downgrade.img in the same folder where you run fastboot from.
Also, you cannot flash a ROM.zip file using the command fastboot flash hboot.
Click to expand...
Click to collapse
So I do I do?
edit:
Just found it:
6. Rename this "rom.zip" file to "PG32IMG.zip"
7. Now take your SD card from Phone and connect it to your PC using a card reader or some other phone.
8. Paste that renamed "PG32IMG.zip" at the root of your SD Card.
9. Now power off your phone. Pull out the battery.
10. Insert the SD Card back in the phone. Insert the battery.
11. Now hold your volume down key and press power button. Keep the volume down key pressed. It will start your phone in boot-loader menu.
12. Select FASTBOOT if its not already selected and press power button.
13. It will search your SD Card for files and will find "PG32IMG.zip" file and will ask if you want to update.
14. Press the volume up button as instructed to continue and then sit back and relax.
Once finished it will ask you to reboot. Once rebooted, you'll be back on stock ROM with S-On.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1705913
Guys just a quick question.
Is any way to remove the "relocked" status of the bootloader?
My phone came from warranty,downgraded hboot with htcdev+alpharevx, now I must go to stock again because I need to send it again, did the whole thing but the bootloader says "relocked"
skinniezinho said:
Guys just a quick question.
Is any way to remove the "relocked" status of the bootloader?
My phone came from warranty,downgraded hboot with htcdev+alpharevx, now I must go to stock again because I need to send it again, did the whole thing but the bootloader says "relocked"
Click to expand...
Click to collapse
The only way is to load a stock RUU/ROM that has bootloader 1.13. If you have a ROM that uses HBOOT 2.00-2.02 then it will always show RELOCKED or UNLOCKED.
tpbklake said:
The only way is to load a stock RUU/ROM that has bootloader 1.13. If you have a ROM that uses HBOOT 2.00-2.02 then it will always show RELOCKED or UNLOCKED.
Click to expand...
Click to collapse
do you know wich one is it?for wwe phone.
skinniezinho said:
do you know wich one is it?for wwe phone.
Click to expand...
Click to collapse
wwe -> 2.30.405.1
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
Alright so I'm pretty much screwed. I wiped everything off my phone except for the boot loader.
I've tried every single method I could find such as reverting back to stock or adb sideloading a custom rom.
They both have failed. Every time I try to revert to a ruu it either tells me it cant verify the signature or it cant verify the model id.
I am extremely frustrated and desperate. Please any help at all would be appreciated.
Relevant Info:
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
ra1nx said:
Alright so I'm pretty much screwed. I wiped everything off my phone except for the boot loader.
I've tried every single method I could find such as reverting back to stock or adb sideloading a custom rom.
They both have failed. Every time I try to revert to a ruu it either tells me it cant verify the signature or it cant verify the model id.
I am extremely frustrated and desperate. Please any help at all would be appreciated.
Relevant Info:
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Click to expand...
Click to collapse
Since you re on HBOOT 1.44 you can try Revone to gain S-OFF and then the RUU will work and get you back to stock!
What is your CID?
What's the error on trying to sideload or adb push to sdcard?
Ivanovic said:
Since you re on HBOOT 1.44 you can try Revone to gain S-OFF and then the RUU will work and get you back to stock!
What is your CID?
Click to expand...
Click to collapse
I was thinking of trying something like this, but I wasn't sure if you could gain S-OFF without an OS installed.
I'll try to use Revone and I'll see if it works
My CID is ROGERS001.
ra1nx said:
I was thinking of trying something like this, but I wasn't sure if you could gain S-OFF without an OS installed.
I'll try to use Revone and I'll see if it works
My CID is ROGERS001.
Click to expand...
Click to collapse
For Revone to work you need ADB. So boot into custom recovery and run the commands needed for Revone.
Normally it requires usb debugging ON but you should give it a try.
SaHiLzZ said:
What's the error on trying to sideload or adb push to sdcard?
Click to expand...
Click to collapse
I could side load a custom rom before, but once I tried to install it the usual way through TWRP the installation failed.
Now after re-locking my bootloader to attempt the reversion to stock, and then unlocking after it failed, I can't even get ADB to recognize my device.
I got the same problem. Using TWRP, side load gives an error. This is my comlete error when trying to install
Comlete error is:
Error flashing zip '/sdcard/M7_UL_JB43..
updating partition details
e:unable to mount /data
e: unable to mount internal storage
so do you have the recovery? If so, then as adb is not recognizing your device, probably is a driver issue.. (also you need to connect to adb while in recovery. not on fastboot or when phone is trying to boot)
If it its a reaction on my post, yes i have the recovery adb is recognozing my devices i can push a rom to my SDcard but when i try to install i get that error.
i had the same problem on Win XP with TWRP, on Win 7 it works fine.
Did you try flash different recovery? CWM? can be pushed to sdcard as well
The push is not the issue, thats works correct. CWM can't find my SDcard at all and in TWRP i can browse to SDcard see the rom click on it but then i got the errors.
cuyo11 said:
so do you have the recovery? If so, then as adb is not recognizing your device, probably is a driver issue.. (also you need to connect to adb while in recovery. not on fastboot or when phone is trying to boot)
Click to expand...
Click to collapse
Okay so I updated TWRP to the latest version and re-installed my HTC drivers and I managed to sideload a custom rom and install it!!!!
Thank you very much to everyone who left a response and helped, I finally have my phone back up and running :good:
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
Please help me
I try to unroot my HTC One. I used the "HTC one AIO kit" for that and now I'm stuck in the follow picture:
***Tampered***
***Relocked***
***Security Warning***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048 MB
Aug 9 2013 16:15:36.0
HBOOT
Blablabla..
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
SHOW BARCODE
The problem is that I can not install the original RUU (Danish version) I get an "Error 155" when I do it. I have tried to make S-Off from the "HTC One AIO kit", but it says "device not found"
You are S-On. Most likely that's why can't install RUU. you should look yo install ARHD 31.6 and S-off. Then you can install RUY
sent from my mobile device
SaHiLzZ said:
You are S-On. Most likely that's why can't install RUU. you should look yo install ARHD 31.6 and S-off. Then you can install RUY
sent from my mobile device
Click to expand...
Click to collapse
I downloaded the android revolution 31.6 and tried to install via cmd. But it goes to say the following:
..sending zip (1161503 kb).. OKAY
..writing `zip`..infosignature checking..
FAILED (remote: 12 signature verify fail)
mohbar said:
I downloaded the android revolution 31.6 and tried to install via cmd. But it goes to say the following:
..sending zip (1161503 kb).. OKAY
..writing `zip`..infosignature checking..
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
you don't send the zip you flash in from custom recovery
clsA said:
you don't send the zip you flash in from custom recovery
Click to expand...
Click to collapse
When I go into Recovery, i get the picture with af phone and a red triangle in it..
mohbar said:
When I go into Recovery, i get the picture with af phone and a red triangle in it..
Click to expand...
Click to collapse
unlock your bootloader at htcdev.com and install custom recovery (TWRP)
clsA said:
unlock your bootloader at htcdev.com and install custom recovery (TWRP)
Click to expand...
Click to collapse
Ok, now I installed TWRP 2633
But how can I then install the ARHD 31.6 and s-off ? I have download the ROM on th PC but cant establish file connection with the pc ?
mohbar said:
Ok, now I installed TWRP 2633
But how can I then install the ARHD 31.6 and s-off ? I have download the ROM on th PC but cant establish file connection with the pc ?
Click to expand...
Click to collapse
boot your phone in TWRP main menu, make sure your arhd zip is in your adb/fastboot folder of your computer.
Code:
adb push <name_of_rom_file>.zip /sdcard/
then in twrp select ''install''
alray said:
boot your phone in TWRP main menu, make sure your arhd zip is in your adb/fastboot folder of your computer.
Code:
adb push <name_of_rom_file>.zip /sdcard/
then in twrp select ''install''
Click to expand...
Click to collapse
Finally i can start up the phone again - thanks for that. So now how can I s-off it and unroot the device..?
Yes.
sent from my mobile device
SaHiLzZ said:
Yes.
sent from my mobile device
Click to expand...
Click to collapse
Yes to what? Im asking how can i change the phone from s-on to s-off ..?
mohbar said:
Yes to what? Im asking how can i change the phone from s-on to s-off ..?
Click to expand...
Click to collapse
follow rumrunner s-off guide here http://forum.xda-developers.com/showthread.php?t=2488772
alray said:
follow rumrunner s-off guide here http://forum.xda-developers.com/showthread.php?t=2488772
Click to expand...
Click to collapse
Ok Ill try that..
alray said:
follow rumrunner s-off guide here http://forum.xda-developers.com/showthread.php?t=2488772
Click to expand...
Click to collapse
Hmm It says error: run rumrunner again and READ (no adb connettion to the device. Debugging on??Drivers?)
I have debugging on and installed the drivers. And I have tested that adb connection is there for the device (show serial code to the device)
I have closed all antivriuses (Bitdefender and windows firewall).
I click on soju.exe when I have the phone opened in the program (ROM) HTC sense.
Any ideas..?
make sure your phone is connected via a USB 2.0 port - forsome reason it doesn't like USB 3.0.
also are you using the old method or the universal method? i suggest finding your phone's mainversion via ADB and see if there's a rumrunner app that matches the main version number.
thegh0sts said:
make sure your phone is connected via a USB 2.0 port - forsome reason it doesn't like USB 3.0.
also are you using the old method or the universal method? i suggest finding your phone's mainversion via ADB and see if there's a rumrunner app that matches the main version number.
Click to expand...
Click to collapse
I have tried the universal one here: http://rumrunner.us/downloads-2/
I also tried one of the verizons with ROM: 1.10.605.2 and everything was ok, until I get a message "Fu*k it..............continuously......."
How can I see mainversion via adb?