Guys,
Usually I am pretty good at this stuff, but I am banging my head against the wall trying to figure out how to get an RUU to flash to get stock AT&T firmware back on this HTC One I have to send back for warranty exhange. Keep getting Error 155 on the RUU.
Thanks,
Y2J
y2jdmbfan said:
Guys,
Usually I am pretty good at this stuff, but I am banging my head against the wall trying to figure out how to get an RUU to flash to get stock AT&T firmware back on this HTC One I have to send back for warranty exhange. Keep getting Error 155 on the RUU.
Thanks,
Y2J
Click to expand...
Click to collapse
If it is an AT&T phone then just take it to an AT&T service center. They will exchange it even if it has been rooted, s-offed/on, different ROM, it does not matter. HTC will not touch it but AT&T has no issues. You do not need to go through all the trouble of changing it back. Read later post in this thread
http://forum.xda-developers.com/showthread.php?t=2333894
It confirms what i am saying...
Solarenemy68 said:
If it is an AT&T phone then just take it to an AT&T service center. They will exchange it even if it has been rooted, s-offed/on, different ROM, it does not matter. HTC will not touch it but AT&T has no issues. You do not need to go through all the trouble of changing it back. Read later post in this thread
http://forum.xda-developers.com/showthread.php?t=2333894
It confirms what i am saying...
Click to expand...
Click to collapse
Unfortunately I already have the replacement device from HTC...
Just flash an ATT stock rom, then restore the stock recovery. Done.
cschmitt said:
Just flash an ATT stock rom, then restore the stock recovery. Done.
Click to expand...
Click to collapse
Via RUU? I've tried a bunch of times with the RUU's that are out there and keep getting error 155.
y2jdmbfan said:
Via RUU? I've tried a bunch of times with the RUU's that are out there and keep getting error 155.
Click to expand...
Click to collapse
No, via CWM/TWRP like this rom. Then flash the stock recovery in fastboot pulled from the 4.18.502.7 firmware.zip from here.
cschmitt said:
No, via CWM/TWRP like this rom. Then flash the stock recovery in fastboot pulled from the 4.18.502.7 firmware.zip from here.
Click to expand...
Click to collapse
Where do I get the stock recovery? Not sure which file in the list of the link you provided has the recovery.img.
Thanks!
y2jdmbfan said:
Where do I get the stock recovery? Not sure which file in the list of the link you provided has the recovery.img.
Thanks!
Click to expand...
Click to collapse
Here's the signed firmware.zip from the OTA: firmware_4.18.502.7.zip
You can flash it in fastboot with
Code:
fastboot oem rebootRUU
fastboot flash zip firmware_4.18.502.7.zip
fastboot flash zip firmware_4.18.502.7.zip (yes, twice!)
fastboot erase cache
fastboot reboot
This will give you the stock recovery, radio, hboot, etc.
cschmitt said:
Here's the signed firmware.zip from the OTA: firmware_4.18.502.7.zip
You can flash it in fastboot with
Code:
fastboot oem rebootRUU
fastboot flash zip firmware_4.18.502.7.zip
fastboot flash zip firmware_4.18.502.7.zip (yes, twice!)
fastboot erase cache
fastboot reboot
This will give you the stock recovery, radio, hboot, etc.
Click to expand...
Click to collapse
Now I am getting this error...I am S-On BTW if that makes a difference...
C:\platform-tools>fastboot flash zip firmware_4.18.502.7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47880 KB)...
OKAY [ 3.170s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 3.415s
Post the output of fastboot getvar all minus IMEI and S/N.
cschmitt said:
Post the output of fastboot getvar all minus IMEI and S/N.
Click to expand...
Click to collapse
C:\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
I think the issue is that you can't downgrade firmware from 4.19 to 4.18 with s-on. Was the phone s-off at one time?
cschmitt said:
I think the issue is that you can't downgrade firmware from 4.19 to 4.18 with s-on. Was the phone s-off at one time?
Click to expand...
Click to collapse
Yes it was. I accidentally put back s-on before I flashed the RUU. The phone had s-off and a custom software when I purchased it. The phone was acting up so I called HTC and got an advanced replacement and already have the replacement. I wanted to flash back to a stock firmware and remove s-off and lock the bootloader before I send the old phone back to HTC.
Unless you are willing to s-off again you're stuck with that firmware. The stock recovery can be pulled from the zip and flashed separately with fastboot though.
cschmitt said:
Unless you are willing to s-off again you're stuck with that firmware. The stock recovery can be pulled from the zip and flashed separately with fastboot though.
Click to expand...
Click to collapse
Oh I would s-off again no problem, but I can't get rumrunner or firewater to work...Any hints would be great based on the getvar I posted above.
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
C:\platform-tools>
Anyone have any ideas to get firewater working?
I have flashed Android Revolution HD 52.0 and then tried to do firewater, but it kicks me back to the command prompt after the initial chugging...
Related
LOOKS LIKE S-OFF FOR 1.54 HAS HAPPENED. NO NEED TO DOWNGRADE CHECK THE POST HERE
MODS Lock This One Up!!!
I was about to give up on s-off since I got the OTA update but there is hope.
I got s-off doing the following:
1.) Unlock your device via HTCDev
2.) Download and flash CWM Recovery
3.) Flash the stock nandroid for your phone...
a. TWRP Nandroid AT&T Thanks JEANRIVERA
b. TWRP Nandroid AT&T Thanks JEANRIVERA
c. TWRP Nandroid AT&T Thanks cschmittIf any one has other links to other devices let me know... I think this will work on all of the variants.:laugh:
Please note that this nandroid was made with TWRP and may need to be restored with TWRP.
On a side note... The original nandroid that I had linked was also created with TWRP and as I was unable to locate the restore function in my TWRP I did restore with CWM.
4.) then relock your device
Code:
fastboot oem lock
5.) grab 1847-ruu-m7-ul-jb-50-cingular-12650212.exe here and run it... Thanks cschmitt
6.) goto the tutorial here... and follow the directions...
This has worked for me... and I hope this will help someone else. All the information came from other people, I just happened to put it in the right order.
If this did not work for you there are New instructions here... Thanks domohan
IT IS IMPORTANT TO DO ALL THE STEPS IN ORDER...
I take no responsibility for anything you do with this information.
If I forgot to mention your name specifically... I'm Sorry and Thanks!
If I helped you hit the thank you button.
I see, new hboot. Downgrading it is then. Interesting that they haven't forced htc to shut off the unlocking service.
worked as advertised
Thanks a lot. A process for sure but worked for me following the ATT OTA update to .15. Although, I went on to follow the guide at wonderhowto dot com for installing the ASOP Google Edition. Thanks again.
Yeah that was the update that got me ... I am really glad that it worked for someone else... :laugh:
I am having trouble flashing the nandroid. I have tried to both flash the zip as well as unpack it and try to do a restore. Any thoughts?
---------- Post added at 06:33 PM ---------- Previous post was at 05:38 PM ----------
Ok, I actually flashed this one http://forum.xda-developers.com/showthread.php?t=2252959
Then ran the .12 RUU and am now S-OFF. Thanks for this!
well i am glad you got that working... The way i did the nandroid was by extracting the zip to clockworkmod\backups ... then choosing restore... I had TWRP but could not find the restore Nandroid option.
The only way I see this actually working is that the RUU just checks the HBOOT version, and not the build date. Otherwise, the .12 RUU would fail to install because the OTA HBOOT has a newer build date.
If this is true, then all AT&T users better get S-OFF now (if they know what S-OFF does). I have a feeling the 4.2.2 update will come out with a newer HBOOT with a higher number. Then surely, any 4.1.2 RUU will not work.
In any case, it seems to be working for those of us who weren't paying attention and downloaded the OTA... But the message is still S-OFF now while you can, 'cause they will patch the thing eventually.
I was getting Error = -6 codes and this method worked perfectly for me! Thanks so much!
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
i used this and it worked flawlessly for me, great looking out man. im now s-off with tampered removed
TabascoJoe said:
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
Click to expand...
Click to collapse
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
INeFFeCTiVE said:
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
Click to expand...
Click to collapse
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Here are the steps I did to unlock bootloader, root and acquire s-off:
I went back to fully stock unrooted s-on to get the OTA just to b on the safe side. This is where I knew the update screwed up the current s-off method so I unlocked the bootloader using HTCDev. Then proceed to root and pushed the revone file to the appropriate folder location. I followed all the commands from revone up to where u Chmod 755 revone. After that since I already had root, I simply type su then proceeded with the s-off and unlock command. Removed tampered label and voila!!! Back in business with latest software.
Sent from my HTC One using xda premium
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
I think what happened was the new update screwed up the motochopper temp root exploit and that's y I think u can't s-off with the updated software. But there is always a way...
Sent from my HTC One using xda premium
TabascoJoe said:
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Click to expand...
Click to collapse
You can't use the AT&T RUU because your HBOOT is higher than the one in the RUU. S-ON is preventing any older HBOOT to be flashed.
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
It would certainly be worth a try. The hardware is the same, so I don't see why not... as long as your boot loader is 1.44.00000 (not sure on the amount of zero's) this should work.
I'm pretty sure there are nandroid images for TMO out there so give it a try.
vinny.1967 said:
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
Click to expand...
Click to collapse
let me know if it's work with you
me_rashad said:
let me know if it's work with you
Click to expand...
Click to collapse
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
vinny.1967 said:
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
Click to expand...
Click to collapse
I did get the OTA too and having the same pesky error -6. The bootloader version still says 1.44.0000, how do we know if its patched or not? Shouldn't the version number increase? What is your version?
Ok, so somehow I've managed to screw this phone up royally. Any help would be greatly appreciated.
I just switched to Android from iPhone and I think I tried too much too fast.
I successfully followed the guide to convert my AT&T HTC One to a Google Play Edition. I got S-OFF and changed the CID to GOOGL001 and successfully got 4.4 up and running.
I'd been using that for a few months and decided I wanted to try the HTC Sense Stock Software 4.3 (being new to android I just kind of wanted to try it myself in addition to stock android) I've been through a ton of steps and attempts now that I won't bore you with, but here's where I'm at now:
I'm stuck in a bootloop. My phone will load to welcome and ask for a language and then reboots about 2 seconds later.
I can successfully get into fastboot and run commands against the device. If I flash a recovery, it seems to work for one or two boots and then it will crash and restart until I flash it again (tried with TWRP and CWM)
I am currently Tampered Unlocked but can perform fastboot oem lock and unlock. I have S-ON, HBOOT 1.54 and Radio 4T.
My goal is to go back to stock for this device with 4.3 and Sense, but since I stupidly did S-ON before I changed the CID I'm not able to run the RUU exe and since my phone is in a bootloop I don't know how to get root access to run rumrunner to S-OFF.
I've been researching and trying stuff for several days now with no luck and this forum seems to have the best advice of most that I've seen. Can anyone help? Thanks so much for your time!
I had a similar experience in which I completely removed android OS from the phone If u flash the HTC with TWRP and you are able to successfully enter the recovery... TWRP has under advance button and option called adb sideload.
basically download the Google edition that successfully ran your device and place it under the adb.exe folder.
Steps
On the phone
Access recoverty TWRP
go to advance
Click on adb sideload
Swipe to activate adb sideload
Connect phone to computer.
On computer
Go to run and enter cmd press enter
go to the folder where you have the adb.exe
and the command that you enter is adb sideload «filename.zip» press enter and let it work
Sent from my HTC One using xda app-developers app
TopoX84 said:
I had a similar experience in which I completely removed android OS from the phone If u flash the HTC with TWRP and you are able to successfully enter the recovery... TWRP has under advance button and option called adb sideload.
basically download the Google edition that successfully ran your device and place it under the adb.exe folder.
Steps
On the phone
Access recoverty TWRP
go to advance
Click on adb sideload
Swipe to activate adb sideload
Connect phone to computer.
On computer
Go to run and enter cmd press enter
go to the folder where you have the adb.exe
and the command that you enter is adb sideload «filename.zip» press enter and let it work
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply and info! Ok, took your advice and flashed TWRP 2.6.3.3 to recovery. (I can only boot to recovery when I'm unlocked, not sure if that matters or not)
I'm trying to send RUU-HTC_One_GE-4.4.2-3.62.1700.1.zip (Is that the correct file I should be using)
The sideload gets to 100% but then instantly fails when it tries to run on the device:
ADB Sideload Complete
Failed
Updating partition details...
E: Unable to mount '/cache
E: Unable to mount '/cache
E: Unable to mount '/cache
Starting ADB sideload feature...
Cancelling ADB sideload...
Starting ADB sideload feature
Installing '/data/media/0/sideload.zip...
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
I've tried a few different versions with similar results (same file pre rooted) and same thing happens.
Any thoughts on what I could be doing wrong (because I'm sure that it's me that's the problem here. )
Give this a try... At the bottom of the op thread it says if adb sideload fails....
http://forum.xda-developers.com/showthread.php?t=2318497
If the link above didn't work you might want to try pushing the Rom to the phone via adb push...
See link below.
http://forum.xda-developers.com/showpost.php?p=43674827&postcount=5
Sent from my HTC One using xda app-developers app
I'm able to push the zip file ok, but when I try to do "install zip" it fails again. I get error flashing zip Updating Partition Detials
Is there anyway for me to achieve s-off from where I am now? If I change my CID back to the AT&T HTC one and then relock and s-on I would be able to use the stock ruu exe, correct?
I would look for a stock Rom GPE since you changed the CID and your s-on
I would look for a 4.3 or 4.4 stock Rom... Make sure also that TWRP is the latest . And try again both steps above. if that doesn't work my inclination would be to flash the Rom via fastboot.
try using this ROM, when i had the issues with my HTC i used it to sideload or push and it worked flawlessly.
http://forum.xda-developers.com/showthread.php?t=2460035
CtrlAltDave said:
Is there anyway for me to achieve s-off from where I am now? If I change my CID back to the AT&T HTC one and then relock and s-on I would be able to use the stock ruu exe, correct?
Click to expand...
Click to collapse
You are correct to what you said unfortunately the only way for you to perform a s-off based on the information given is using rumrunner in which you need your device to boot completely to the OS
Sent from my HTC One using xda app-developers app
no reason to post one after other where i can edit using the computer
Thanks for all of your help and patience with me. I think this phone hates me. I get error flashing with every zip I throw at the phone. I get error flashing zip in TWRP and Installation aborted with CWM. Tried with 4.3 and 4.4 stock GPE rom. Same results if I sideload or push. I also get an error when i try to fastboot flash the same roms. 99 unknown fail when bootloader unlocked and 12 signature verify fail if bootloader locked. Both of these are using fastboot oem rebootRUU and then fastboot flash zip rom.zip.
I pasted my getvar all below thinking that might help. I noticed my version-main is blank as well. Could that be causing any problems?
C:\Users\dfarrar\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm beyond frustrated at this point because I've spent so much time trying to get this working and I'm at a loss. That's what I get for messing around before I learned enough I guess. Thanks again for helping me out. I owe you!
here is mine...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*******
(bootloader) imei: *************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3756mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
the problem as i see it might be the cidnum and modelid, if you get a rom with both config it might be able to flash
CtrlAltDave said:
Thanks for all of your help and patience with me. I think this phone hates me. I get error flashing with every zip I throw at the phone. I get error flashing zip in TWRP and Installation aborted with CWM. Tried with 4.3 and 4.4 stock GPE rom. Same results if I sideload or push. I also get an error when i try to fastboot flash the same roms. 99 unknown fail when bootloader unlocked and 12 signature verify fail if bootloader locked. Both of these are using fastboot oem rebootRUU and then fastboot flash zip rom.zip.
I pasted my getvar all below thinking that might help. I noticed my version-main is blank as well. Could that be causing any problems?
C:\Users\dfarrar\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm beyond frustrated at this point because I've spent so much time trying to get this working and I'm at a loss. That's what I get for messing around before I learned enough I guess. Thanks again for helping me out. I owe you!
Click to expand...
Click to collapse
try this rom out .... RUU-HTC_One_GE-2.14.1700.15
http://forum.xda-developers.com/showthread.php?t=2358781&page=112
http://forum.xda-developers.com/showthread.php?t=2570785&page=3
Same errors with that rom. Won't work through adb push with twrm or cwm. Won't work with sideload and won't work fastboot flash zip. Could I have permanently broken this thing?
CtrlAltDave said:
Same errors with that rom. Won't work through adb push with twrm or cwm. Won't work with sideload and won't work fastboot flash zip. Could I have permanently broken this thing?
Click to expand...
Click to collapse
no it's not broken ...
Flash this stock recovery and also change your CID back to AT&T
fastboot oem writecid CWS__001
then
http://d-h.st/2Lr
fastboot flash recovery recovery_signed.img
Next boot into stock recovery / factory reset
this is done from the bootloader using the volume up/down to navigate and Power button to select. After you choose recovery you have to push vol up and power to see the factory reset option.
When it's done reflash TWRP recovery and try and sideload a new Rom
I recommend >> Download - ARHD 31.6
Would he be able to change back to the AT&T cod having s-on??? As far as I know you can only change with s-on only when you have supercid in place
Sent from my HTC One using xda app-developers app
TopoX84 said:
Would he be able to change back to the AT&T cod having s-on??? As far as I know you can only change with s-on only when you have supercid in place
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
yeah your right he need to get back s-off also after he gets ARHD 31.6 running
ARHD did the trick! For some reason none of the stock GPE roms would load but this one worked flawlessly. I was able to sideload and install, get supersu and then use rumrunner to get back to s-off. Plus this rom gives me everything that I wanted. I can keep kitkat and still get sense and zoe and whatnot. Never mind going back to stock, I think I'll stick with this for a while and try it out. Thanks so much for your help everyone!
To be in the safe side you might want to consider changing the cid to supercid...
Sent from my HTC One using xda app-developers app
CtrlAltDave said:
ARHD did the trick! For some reason none of the stock GPE roms would load but this one worked flawlessly. I was able to sideload and install, get supersu and then use rumrunner to get back to s-off. Plus this rom gives me everything that I wanted. I can keep kitkat and still get sense and zoe and whatnot. Never mind going back to stock, I think I'll stick with this for a while and try it out. Thanks so much for your help everyone!
Click to expand...
Click to collapse
Good to here it all worked out for you
and remember STAY S-OFF
SuperCID and S-Off for life. Thanks again!
Thanks All
Don't know if any of you will check back on this ancient post, but I read around for a long time and this totally ended up working for me. So belated thanks.
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
TopoX84 said:
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I did just as you posted this, thanks!
codejunkie83 said:
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
or you could try this which is supposed to be the latest version that at&t has gotten out
http://androidromupdate.com/2013/10/09/att-htc-one-official-4-3-ota-update-stock-ruu-3175023/
Sent from my HTC One using xda app-developers app
TopoX84 said:
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
EDIT: I also tried that latest AT&T version from androidromupdate, but it failed the same
codejunkie83 said:
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
Click to expand...
Click to collapse
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Okay, seems like I've followed all of those steps. I ran fastboot oem lock, but each time I try the RUU I get the 155 message. I had just installed the latest HTC drivers last week, as that was when I went to the GPE. I'm using the same USB port that I had been using then, so no differences there.
Thank you for your responses - if you need any more information I'll be glad to give it.
TopoX84 said:
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Click to expand...
Click to collapse
Okay, so one thing that I have noticed - my main versions seems to be X.XX.1540.X, which as best I can tell is the US Dev Edition. However, my CID is CWS_001, which should have X.XX.502.X as the main version. Unfortunately, I think the conflict here is causing my RUUs to fail. Any suggestions?
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
codejunkie83 said:
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
Click to expand...
Click to collapse
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
mb_guy said:
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
codejunkie83 said:
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
Click to expand...
Click to collapse
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
mb_guy said:
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
Click to expand...
Click to collapse
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
codejunkie83 said:
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
Click to expand...
Click to collapse
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
BTW: have you tried "fastboot oem unlock" again
mb_guy said:
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
Click to expand...
Click to collapse
Thanks, will do!
Trying to get an RUU to run to update the HTC One M7 from T-Mobile. I've tried both the 3.24 that the phone has, and the 4.xx new one from the Original Android Dev forum. Both of them fail. 3.xx when trying to verify information, and 4.xx after step 1/5 pushing boot. 4.xx gives error 171 USB issue. I've got the drivers installed, as well as ADB and Fastboot. It connects to the phone and the RUU file reboots it, but instead of going to bootloader it goes to a black screen with HTC in silver, then the RUU on the computer fails.
Any ideas what I might be doing wrong? I have fastboot/bootloader access, but can't boot past the HTC O1ne screen.
Edit: I GOT IT!!! If you're in the same spot as me, make sure to put the RUU in your ADB directory. It wasn't working for me, moved it, worked like a charm.
detox702 said:
Trying to get an RUU to run to update the HTC One M7 from T-Mobile. I've tried both the 3.24 that the phone has, and the 4.xx new one from the Original Android Dev forum. Both of them fail. 3.xx when trying to verify information, and 4.xx after step 1/5 pushing boot. 4.xx gives error 171 USB issue. I've got the drivers installed, as well as ADB and Fastboot. It connects to the phone and the RUU file reboots it, but instead of going to bootloader it goes to a black screen with HTC in silver, then the RUU on the computer fails.
Any ideas what I might be doing wrong? I have fastboot/bootloader access, but can't boot past the HTC O1ne screen.
Click to expand...
Click to collapse
Are you S-On or S-Off? Do you have stock recovery? Is your MID and CID the same as the RUU? Is your bootloader "Locked"? Do you have the stock hboot for the RUU you are trying to run? The hboot has to be the same or lower than hboot in the RUU!
majmoz said:
Are you S-On or S-Off? Do you have stock recovery? Is your MID and CID the same as the RUU? Is your bootloader "Locked"? Do you have the stock hboot for the RUU you are trying to run? The hboot has to be the same or lower than hboot in the RUU!
Click to expand...
Click to collapse
Everything is stock. The co-worker never bothered with rooting/etc. S-On. T-Mo phone using a T-Mo RUU. Locked bootloader. Pretty sure the hboot is the same as well.
detox702 said:
Everything is stock. The co-worker never bothered with rooting/etc. S-On. T-Mo phone using a T-Mo RUU. Locked bootloader. Pretty sure the hboot is the same as well.
Click to expand...
Click to collapse
Reboot to bootloader (FASTBOOT USB), then run the command: fastboot getvar all This will tell you the id information about the phone. There may be some light shed on the status of the phone.
majmoz said:
Reboot to bootloader (FASTBOOT USB), then run the command: fastboot getvar all This will tell you the id information about the phone. There may be some light shed on the status of the phone.
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4312mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
C:\adb>
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
C:\adb>[/QUOTE]
First of all please remove the serialno and imei from your original post. Nothing looks out of the order. Could the RUU be corrupt? Check the MD5 checksum just to be sure. Or download another RUU from a different site. I have used this site's RUU in the past.
majmoz said:
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
C:\adb>
Click to expand...
Click to collapse
First of all please remove the serialno and imei from your original post. Nothing looks out of the order. Could the RUU be corrupt? Check the MD5 checksum just to be sure. Or download another RUU from a different site. I have used this site's RUU in the past.[/QUOTE]
I apparently got it. Moved the file from C:\Downloads to C:\adb, ran it, success. Thanks for the pointers, though.
I was following this guide: http://forum.xda-developers.com/showthread.php?t=2497614
I did the first flash which is supposed to fail, when I did it the 2nd time it got stuck on the first step in the command window ((bootloader) [RUU]WP,rcdata,0). I waited a long time but had no choice but to close the command prompt. Now I'm stuck w/ a green progress bar and the silver htc logo. Am I bricked? fastboot recognizes the device as "???????"
Update: I got it to recognize the device again. I'm trying to flash RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3, but it doesn't recognize my phone so I extracted rom.zip manually and am trying to flash it. I'm getting this error now when I try to flash the 2nd time:
Code:
"target reported max download size of 1528479744 bytes
sending 'zip' (206214 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.025s"
I'm currently stuck with the 4 triangles so until I manage to flash SOMETHING successfully I'm soft-bricked I guess.
Update 2: I extracted the zip again. It's a lot larger this time so I guess I got a bad zip last time. :-/ In any case the rom.zip is over 1.5 GB now and when I try to flash it I get this in the console and fastboot.exe stops responding:
Code:
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <snip>
(bootloader) imei: <snip>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4074mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.115s
Perhaps someone can just point me in the right direction for a dev edition zip. Will this one work? http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-zip/
@clsA, You've helped me in the past. Perhaps you could point me in the right direction? I'm using the RUU executable you mentioned in my old thread, but since they weren't recognizing my phone I decided to extract the rom.zip. Unfortunately that doesn't appear to be working either as you can see above.
Dr3x1 said:
@clsA, You've helped me in the past. Perhaps you could point me in the right direction? I'm using the RUU executable you mentioned in my old thread, but since they weren't recognizing my phone I decided to extract the rom.zip. Unfortunately that doesn't appear to be working either as you can see above.
Click to expand...
Click to collapse
Are you looking to use the latest dev edition version or you abosulately want to flash this old one? You could update your firmware to 6.07.1540.2 (that will also get you out of RUU mode) and then flash the 7.17.1540.2 ruu and take the ota update to 7.17.1540.21.
alray said:
Are you looking to use the latest dev edition version or you abosulately want to flash this old one? You could update your firmware to 6.07.1540.2 (that will also get you out of RUU mode) and then flash the 7.17.1540.2 ruu and take the ota update to 7.17.1540.21.
Click to expand...
Click to collapse
o/ Thanks for the reply. I finally managed to get out of RUU mode, but not until I accidentally downgraded to Hboot 1.44 and could no longer communicate w/ the device ('cuz windows). After booting linux I managed to flash a Zip of M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.
I'm currently doing OTA updates. How far will I get with what I flashed? Can I get the latest? I won't be too upset if I can't, but it'd be nice.
Dr3x1 said:
o/ Thanks for the reply. I finally managed to get out of RUU mode, but not until I accidentally downgraded to Hboot 1.44 and could no longer communicate w/ the device ('cuz windows). After booting linux I managed to flash RUU Zip M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.
I'm currently doing OTA updates. How far will I get with what I flashed? Can I get the latest? I won't be too upset if I can't, but it'd be nice.
Click to expand...
Click to collapse
you will eventually get their with the OTA's but why not just jump to the 6.x RUU and update from their
@alray has all the files you need in his thread in his signature
clsA said:
you will eventually get their with the OTA's but why not just jump to the 6.x RUU and update from their
@alray has all the files you need in his thread in his signature
Click to expand...
Click to collapse
Thanks for the links. Hopefully it updates my firmware too so I can talk to my device w/ Windows again. If not I'll do it manually though. Appreciate the help again! ^_^
Doesn't look like the RUU.exe will work still. It recognizes my phone now but gets stuck on 0/5 sending... The ZIP is too large as well. Fastboot.exe crashes every time I try to flash it. Oh well. OTA updates it is I guess.
Dr3x1 said:
Doesn't look like the RUU.exe will work still. It recognizes my phone now but gets stuck on 0/5 sending... The ZIP is too large as well. Fastboot.exe crashes every time I try to flash it. Oh well. OTA updates it is I guess.
Click to expand...
Click to collapse
flash the firmware / then try the RUU