I'm S-Off with Rumrunner, unlocked bootloader, and the latest TWRP recovery. Yet every ROM I try to flash fails. I've only been able to ADB sideload one rooted 4.4 Rom. Am I missing something? I'm on HBoot 1.55. Any pointers would be greatly appreciated. :laugh:
poopoo152010 said:
I'm S-Off with Rumrunner, unlocked bootloader, and the latest TWRP recovery. Yet every ROM I try to flash fails. I've only been able to ADB sideload one rooted 4.4 Rom. Am I missing something? I'm on HBoot 1.55. Any pointers would be greatly appreciated. :laugh:
Click to expand...
Click to collapse
Need more info to help. Are they failing during the installer? Is there an error? Are they just not starting up? What are you wiping before you flash? Are you flashing from within recovery?
Sent from my HTC One using Tapatalk
lampel said:
Need more info to help. Are they failing during the installer? Is there an error? Are they just not starting up? What are you wiping before you flash? Are you flashing from within recovery?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I am flashing from within recovery. Wiping data/cache/dalvik. Here is what I get with every zip I try to flash.
Installing '/sdcard/Download/First-M7-GSM-LAST.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/Download/First-M7-GSM-LAST.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
script aborted: Can't install this package (Wed Nov 6 18:25:54 PST 2013) over newer build (Sun Nov 10 13:21:41 UTC 2013).
Can't install this package (Wed Nov 6 18:25:54 PST 2013) over newer build (Sun Nov 10 13:21:41 UTC 2013).
E:Error executing updater binary in zip '/sdcard/Download/First-M7-GSM-LAST.zip'
Error flashing zip '/sdcard/Download/First-M7-GSM-LAST.zip'
poopoo152010 said:
I am flashing from within recovery. Wiping data/cache/dalvik. Here is what I get with every zip I try to flash.
Installing '/sdcard/Download/First-M7-GSM-LAST.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/Download/First-M7-GSM-LAST.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
script aborted: Can't install this package (Wed Nov 6 18:25:54 PST 2013) over newer build (Sun Nov 10 13:21:41 UTC 2013).
Can't install this package (Wed Nov 6 18:25:54 PST 2013) over newer build (Sun Nov 10 13:21:41 UTC 2013).
E:Error executing updater binary in zip '/sdcard/Download/First-M7-GSM-LAST.zip'
Error flashing zip '/sdcard/Download/First-M7-GSM-LAST.zip'
Click to expand...
Click to collapse
I'd add system to your list of wipes. Are all the roms your trying to flash 4.4?
Sent from my HTC One using Tapatalk
lampel said:
I'd add system to your list of wipes. Are all the roms your trying to flash 4.4?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
If I add system won't it wipe any Roms I downloaded? I've tried a few 4.4 roms, and 4.3. All of them fail. I can install kernels or gapps no problem. Right now I'm back on a 4.3 Rom that successfully sideloaded. I'm going to stick with it until I figure this out. I feel like I might have done something wrong because superuser never sticks either. Haven't rooted an HTC since the Evo 3D.
poopoo152010 said:
If I add system won't it wipe any Roms I downloaded? I've tried a few 4.4 roms, and 4.3. All of them fail. I can install kernels or gapps no problem. Right now I'm back on a 4.3 Rom that successfully sideloaded. I'm going to stick with it until I figure this out. I feel like I might have done something wrong because superuser never sticks either. Haven't rooted an HTC since the Evo 3D.
Click to expand...
Click to collapse
No, wiping system won't delete downloaded roms but it will delete roms you have flashed. Downloads are on the 'sdcard' which is really /data/media/0 but twrp specifically doesn't wipe it when you wipe 'data' unless you explicitly tell it to. I think a lot of devs wipe system as part of their install process so generally it's an unneeded step but I'd do it just to eliminate that as a potential issue.
Sent from my HTC One using Tapatalk
lampel said:
No, wiping system won't delete downloaded roms but it will delete roms you have flashed. Downloads are on the 'sdcard' which is really /data/media/0 but twrp specifically doesn't wipe it when you wipe 'data' unless you explicitly tell it to. I think a lot of devs wipe system as part of their install process so generally it's an unneeded step but I'd do it just to eliminate that as a potential issue.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Boot into bootloader and do
Code:
fastboot getvar all
paste the output here.
Well I installed the the newest clockworkmod recovery and everything is flashing just fine now. Now if I could figure out why I lose data on the kitkat roms I'll be set. But I think that's for another forum. Thanks for all the help.
Sent from my HTC One using xda app-developers app
shpitz461 said:
Boot into bootloader and do
Code:
fastboot getvar all
paste the output here.
Click to expand...
Click to collapse
I hope no one minds that I hijacked this thread. I'm having the same problem. I've tried flashing several ROMS and everything fails. I have the latest version of TWRP. Does any of this output help anyone help me?
(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: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(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: 4153mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
FongLai said:
I hope no one minds that I hijacked this thread. I'm having the same problem. I've tried flashing several ROMS and everything fails. I have the latest version of TWRP. Does any of this output help anyone help me?
(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: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(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: 4153mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
Click to expand...
Click to collapse
First, you may want to edit your post and remove your serial and imei. Second, need more info: are you trying to flash 4.4 roms also? Has anything been successful? Since you have twrp I'm assuming your still bootloader unlocked. Are you getting an error?
Sent from my HTC One using Tapatalk
I'm having the same problem, everything ive tried to flash has failed. Pac-man ROM is the only one thats flashed successfully for me. ive tried using CWM and TWRP, and every single one fails on me. Ive wiped the big 3, and have formatted the system as well.....Ive also tried to flash 4.3 and 4.4 roms, and nothing seems to work. I have no idea what else to try. any info anyone needs to help me fix this issue, id be more than happy to provide. I dont know where to start with troubleshooting....Any and all help would be appreciated...Please and thank you
lampel said:
First, you may want to edit your post and remove your serial and imei. Second, need more info: are you trying to flash 4.4 roms also? Has anything been successful? Since you have twrp I'm assuming your still bootloader unlocked. Are you getting an error?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I've actually went back to stock and updated to the 4.3 release. I'm having a whole new set of problems now. That's for another post though. Thanks!
Related
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.
Hey All,
To get things started I was just looking to root/rom my friends phone to get him the wifi hotspot among some other goodies associated with custom roms. I have a good amount of experience regarding flashing, rooting, command line, etc.. I change my S4 rom weekly, and have had some experience with HTC recoveries dating back to my old, old, (OLD) HTC Apache (Yeah that was windows mobile 5). More recently I've worked with a HTC EVO.
Here's where I stand with this HTC EVO 4g LTE.
I originally tried to flash a RUU that was 'one click' thinking that it would be similar to the 1-Click Root and Recovery found for Samsung Devices, I was wrong. I know now that I needed S-OFF for this particular file and well, things didnt go well. The RUU froze (guessing because of the security reasons).
So the device now only boots to the HTC Splash indefinately or I can get it into the bootloader.
In an attempt to road of recovery, I have:
Installed TWRP v2.6.1.0 - Leaving **TAMPERED**, (I suspect)
HTCDev unlocked - Leaving **UNLOCKED**
I'd be happy to just get this thing to boot stock rom, from there I think I can S-OFF and get a custom rom on. But one step at at time.
I've tried running RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.17.651.4_Radio_1.13.11.0830_NV_3.02_003_PRL25007_release_334470_signed.zip as an attempt to recover stock, I've read reports that I might need to relock the phone to get this to work. Is this true?
I've read and read and read and tried and tried to no avail, just looking for a little pointer to get me in the right direction.
Included is my fastboot getvar all:
Code:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0000
(bootloader) version-baseband: 1.13.11.0830
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.651.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT27FS401770
(bootloader) imei: 990000667854337
(bootloader) product: jewel
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ7510000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b28ce9b8
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you so much in advance for any advice or guidance.
ragnsep said:
Hey All,
To get things started I was just looking to root/rom my friends phone to get him the wifi hotspot among some other goodies associated with custom roms. I have a good amount of experience regarding flashing, rooting, command line, etc.. I change my S4 rom weekly, and have had some experience with HTC recoveries dating back to my old, old, (OLD) HTC Apache (Yeah that was windows mobile 5). More recently I've worked with a HTC EVO.
Here's where I stand with this HTC EVO 4g LTE.
I originally tried to flash a RUU that was 'one click' thinking that it would be similar to the 1-Click Root and Recovery found for Samsung Devices, I was wrong. I know now that I needed S-OFF for this particular file and well, things didnt go well. The RUU froze (guessing because of the security reasons).
So the device now only boots to the HTC Splash indefinately or I can get it into the bootloader.
In an attempt to road of recovery, I have:
Installed TWRP v2.6.1.0 - Leaving **TAMPERED**, (I suspect)
HTCDev unlocked - Leaving **UNLOCKED**
I'd be happy to just get this thing to boot stock rom, from there I think I can S-OFF and get a custom rom on. But one step at at time.
I've tried running RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.17.651.4_Radio_1.13.11.0830_NV_3.02_003_PRL25007_release_334470_signed.zip as an attempt to recover stock, I've read reports that I might need to relock the phone to get this to work. Is this true?
I've read and read and read and tried and tried to no avail, just looking for a little pointer to get me in the right direction.
Included is my fastboot getvar all:
Code:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0000
(bootloader) version-baseband: 1.13.11.0830
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.651.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT27FS401770
(bootloader) imei: 990000667854337
(bootloader) product: jewel
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ7510000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b28ce9b8
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you so much in advance for any advice or guidance.
Click to expand...
Click to collapse
Yes, relock the bootloader and try the official RUU again. fastboot oem lock.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I get [Error 158] IMAGE ERROR after **RELOCKING** the bootloader. Do I need any firmware zips on my sdcard renamed to P175xxx or whatever is specified for other RUUs?
ragnsep said:
I get [Error 158] IMAGE ERROR after **RELOCKING** the bootloader. Do I need any firmware zips on my sdcard renamed to P175xxx or whatever is specified for other RUUs?
Click to expand...
Click to collapse
Try running the RUU found here:
http://forum.xda-developers.com/showthread.php?t=2653730
Bottom of the first post, is the most recent HTC RUU.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
Try running the RUU found here:
http://forum.xda-developers.com/showthread.php?t=2653730
Bottom of the first post, is the most recent HTC RUU.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, I noticed this is a different image version...
Out of curiosity, was the partition table on this RUU very different from the previous one? And was that the issue?
ragnsep said:
Thanks, I noticed this is a different image version...
Out of curiosity, was the partition table on this RUU very different from the previous one? And was that the issue?
Click to expand...
Click to collapse
This one has the partition set up the way it should have been from the start. More space internal for apps and such. Did it work?
Sent from my EVO using XDA Premium 4 mobile app
Have you tried flashing a custom recovery then flashing a sense Rom (you're on 3.17 so anything based on that or 3.16 will be compatible with the version your log says you're on)? If that works then at least you can go for s off before trying anything else.
Sent from my 831C using xda app-developers app
Hello XDA, I have been looking around and I didn't see much stuff on AT&T HTC One M8,
I am hoping this thread will be of use for some of you.
THIS IS FOR ADVANCED USERS ONLY
I AM NOT RESPONSIBLE FOR YOUR PHONE
YOU ARE DOING THIS AT YOUR OWN RISK
YOU HAVE BEEN WARNED
Stock Backups
1.12.502.18
1.58.502.1
MAKE SURE YOU DO A FACTORY RESET AFTER RESTORING
Stock Recoveries
1.12.502.18
1.58.502.1
OTAs
1.12.502.18_to_1.58.502.1_UPDATE
Radio
radio_1.16.21331931.LA11G_20.31A.4145.02L
Other Thoughts..
As of 8/23/2014 I still receive the 1.12.502.18 to 1.58.502.1 OTA Update..
If this helped you in anyway please..
DONATE
Thanks
MLIGN said:
Hello XDA, I have been looking around and I didn't see much stuff on AT&T HTC One M8,
I am hoping this thread will be of use for some of you.
THIS IS FOR ADVANCED USERS ONLY
I AM NOT RESPONSIBLE FOR YOUR PHONE
YOU ARE DOING THIS AT YOUR OWN RISK
YOU HAVE BEEN WARNED
Stock Backups
1.12.502.18
1.58.502.1
MAKE SURE YOU DO A FACTORY RESET AFTER RESTORING
Stock Recoveries
1.12.502.18
1.58.502.1
OTAs
1.12.502.18_to_1.58.502.1_UPDATE
Radio
radio_1.16.21331931.LA11G_20.31A.4145.02L
Other Thoughts..
As of 8/23/2014 I still receive the 1.12.502.18 to 1.58.502.1 OTA Update..
If this helped you in anyway please..
DONATE
Click to expand...
Click to collapse
could you please post the latest OTA 2.23 with android 4.4.3 thanks
Nobody has it, run the ruu its safer and it appears to not have the [email protected] drain that they pulled the update because of
JEANRIVERA said:
could you please post the latest OTA 2.23 with android 4.4.3 thanks
Click to expand...
Click to collapse
JEANRIVERA said:
could you please post the latest OTA 2.23 with android 4.4.3 thanks
Click to expand...
Click to collapse
I haven't been running the AT&T version of this phone for the past week..
I also heard that they pulled the OTA..
As soon as it is back. I'll go back to AT&T to get the OTA, Radio, and Stock Backup for you all!
Which restore is the 4.4.2? My cousins phone is stuck rebooting, so I reset it and its stuck on boot.
AT&T stock recovery 2.23.502.3
For those that might need it, here is the stock recovery from the 2.23 RUU. If anyone is interested, I could also add to this post exactly how I get the recovery. It took me about 2 hours to get all the info together that I needed in order to pull it off.
Steps to extract stock recovery:
1. Flash stock RUU.
2. Boot into TWRP. Don't flash TWRP to phone, but boot into it running on computer. Do this by using the command "fastboot boot recovery.img". Same steps as flashing a new recovery, but in this case you just boot the phone into this version of recovery. You can use the instructions at the link below, just replace flash with boot.
http://teamw.in/project/twrp2/225
3. Root phone by installing SuperSU. Flash the SuperSU.zip from your booted recovery.
4. Reboot phone and update SuperSU from the play store.
5. Connect phone to computer and use ADB to copy recovery partition to img file on phone. I used the guide at this page:
http://forum.xda-developers.com/showthread.php?t=2450045
For the AT&T M8 the block you need to dump is mmcblk0p43
So the command will be this:
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img
Is the 1.58.502.1 stock backup without root?
Answerd my own question by flashing it,no root witch is cool cause all I would have to do to receive ota is flash the stock recovery alongside. Thank you for this ,I used it to go back to stock and use SunShine to S-OFF
Sent from my SM-T700 using Tapatalk
how do you actually use these to get back to stock?
ive had a botched attempt at updating the firmware and installing venomone.
i tried installing these via the all in one kit but it didnt work, it had me try relocking my bootloader and still didnt work.
so now im stuck with a relocked bootloader, and cant figure out how to get back to stock =/
The_Zodiac said:
how do you actually use these to get back to stock?
ive had a botched attempt at updating the firmware and installing venomone.
i tried installing these via the all in one kit but it didnt work, it had me try relocking my bootloader and still didnt work.
so now im stuck with a relocked bootloader, and cant figure out how to get back to stock =/
Click to expand...
Click to collapse
Download zip file and extract it with root explorer of choice
:navigate to extract location and open the extracted folder,once in that folder you should open the next folder and copy the numbered folder over to your TWRP/backup folder as if it was a backup you made.
Or start searching how to RUU back to stock with adb/fastboot
Sent from my SM-T700 using Tapatalk
jball said:
Download zip file and extract it with root explorer of choice
:navigate to extract location and open the extracted folder,once in that folder you should open the next folder and copy the numbered folder over to your TWRP/backup folder as if it was a backup you made.
Or start searching how to RUU back to stock with adb/fastboot
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
yeah ended up finding the RUU to get back to stock, now my problem is i cant re unlock my bootloader
(Thread here http://forum.xda-developers.com/att-htc-one-m8/help/help-getting-to-stock-att-m8-t2912921)
thanks for helping man
With the OP permission I could make a video of how to use the stock backup from downloading of the file to executing the flashing for a more visual learning
Sent from my SM-T700 using Tapatalk
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
The_Zodiac said:
yeah ended up finding the RUU to get back to stock, now my problem is i cant re unlock my bootloader
(Thread here http://forum.xda-developers.com/att-htc-one-m8/help/help-getting-to-stock-att-m8-t2912921)
thanks for helping man
Click to expand...
Click to collapse
Are you still using the tool kit ?
Try your original key and use the adb/fastboot method .or how about posting the steps you've taken in attempts at unlocking your bootloader this time
Sent from my SM-T700 using Tapatalk
jball said:
With the OP permission I could make a video of how to use the stock backup from downloading of the file to executing the flashing for a more visual learning
Sent from my SM-T700 using Tapatalk
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
Are you still using the tool kit ?
Try your original key and use the adb/fastboot method .or how about posting the steps you've taken in attempts at unlocking your bootloader this time
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
was able to get it to work with a new unlock.bin from htd.dev
Great work. Helpful!
Thanks
I am currently on CM11 and want to get back to stock and update to latest firmware. I will need to flash both the backup and recovery 1.12.502.18 and then ota update. Then I can reflash a custom recovery again. Is that correct?
Here is my info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *REMOVED
(bootloader) imei: *REMOVED
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
MLIGN said:
Hello XDA, I have been looking around and I didn't see much stuff on AT&T HTC One M8,
I am hoping this thread will be of use for some of you.
THIS IS FOR ADVANCED USERS ONLY
I AM NOT RESPONSIBLE FOR YOUR PHONE
YOU ARE DOING THIS AT YOUR OWN RISK
YOU HAVE BEEN WARNED
Stock Backups
1.12.502.18
1.58.502.1
MAKE SURE YOU DO A FACTORY RESET AFTER RESTORING
Stock Recoveries
1.12.502.18
1.58.502.1
OTAs
1.12.502.18_to_1.58.502.1_UPDATE
Radio
radio_1.16.21331931.LA11G_20.31A.4145.02L
Other Thoughts..
As of 8/23/2014 I still receive the 1.12.502.18 to 1.58.502.1 OTA Update..
If this helped you in anyway please..
DONATE
Click to expand...
Click to collapse
how about earlier hboots ,to downgrade
mws1986 said:
I am currently on CM11 and want to get back to stock and update to latest firmware. I will need to flash both the backup and recovery 1.12.502.18 and then ota update. Then I can reflash a custom recovery again. Is that correct?
Here is my info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *REMOVED
(bootloader) imei: *REMOVED
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Did you ever figure it out? I'm on the same boat and need to update my firmware. I have the same info as you, s-on, same bootloader version, same radio, etc. That's what I was thinking of doing. Flash stock rom, flash recovery, get ota, then flash twrp recovery again. I'm on att as well.
Gilbertinho said:
Did you ever figure it out? I'm on the same boat and need to update my firmware. I have the same info as you, s-on, same bootloader version, same radio, etc. That's what I was thinking of doing. Flash stock rom, flash recovery, get ota, then flash twrp recovery again. I'm on att as well.
Click to expand...
Click to collapse
That probably isn't going to do what you want. OTA will only update you to Android 4.4.2 and hboot 3.16, which is what you've already got.
What version firmware are you trying to update to. Or asked another way, what ROM are you trying to run? The issue is a bit complicated now, as the current custom ROMs are split on firmware 3.x or 4.x (neither of which are "officially" released by AT&T yet).
redpoint73 said:
That probably isn't going to do what you want. OTA will only update you to Android 4.4.2 and hboot 3.16, which is what you've already got.
What version firmware are you trying to update to. Or asked another way, what ROM are you trying to run? The issue is a bit complicated now, as the current custom ROMs are split on firmware 3.x or 4.x (neither of which are "officially" released by AT&T yet).
Click to expand...
Click to collapse
I am currently running ViperOneM8 1.8 and am trying to run ViperOneM8 2.5.0 which requires you to have the 4.4.3 base firmware. From my understanding AT&T released this OTA. The newer roms require 4.4.4 which AT&T has yet to release. I am not trying to update to 4.4.4 since that requires S-OFF, which I dont want to/don't know how to do. Thanks for the reply by the way!
I had someone inexperienced bring me this phone which they botched. They were able to use htcdev and unlock the bootloader and install TWRP, but that is all. No s-off. They must have wiped it because there is no OS on it and they want it back to stock now. So, I figured I would relock the bootloader and flash the most current ota. Nope. It isn't having it. I tried the 3.28 ota but after the check in hboot, it reads "checking" with "press power to reboot" over the top of the text. I have tried other ruu's and zips only to get checksum errors or signature verification errors. I forgot to mention that when twrp was installed, not a single custom rom would intall. They all failed. The person that brought it to me did mention something about trying to get to the google play edition firmware but they didn't know much about it. Does anyone have any ideas on where I can go from here? Anything would be very helpful. Thank you!
adb getvar all, and tell us hboot number, radio, verify it is s-on, and also what is CID?
What RUUs did you try?
Which 3.28 OTA did you try? One hasn't been released by AT&T yet.
redpoint73 said:
adb getvar all, and tell us hboot number, radio, verify it is s-on, and also what is CID?
What RUUs did you try?
Which 3.28 OTA did you try? One hasn't been released by AT&T yet.
Click to expand...
Click to collapse
C:\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45FWM10802
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
I have tried all the att ruu's and the unbranded 3.28. In twrp I tried sense and non sense roms, all of which failed.
Delete your IMEI from the post, as this is private info.
Sorry, I should have mentioned to delete the IMEI. Although I did not request to cut and paste all the getvar data.
EDIT: Reported to mods, and they deleted the IMEI.
---------- Post added at 03:35 PM ---------- Previous post was at 03:30 PM ----------
In bootloader, you've verified the bootloader is relocked?
Also, you tried the 2.23 RUU? I know you said you tried "all" the RUUs (it helps to be specific and list everything individually). But I ask because this RUU was released, but now its not listed on HTC's support site (as the OTA was pulled due to battery drain issues) so some people think the RUU itself was also "pulled". Although the direct RUU download still exists and works:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Also, you can try the bootable RUU, which some folks have had better luck with: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Or another approach: What version of TWRP? Some older versions were known to have some flashing issues for some folks. Any specific error messages?
With bootloader unlocked, try to fastboot erase cache, and fastboot flash the latest TWRP. Or try Philz recovery. Then try again to flash a ROM.
whoops, I forgot about the imei. Thanks. Yes, I tried 2.23 and it read no image or wrong image. I will unlock the bootloader again and install the most current twrp and give it a try. anything helps. thanks!
iRootAll said:
I tried 2.23 and it read no image or wrong image.
Click to expand...
Click to collapse
Did you try the bootable version I linked?
Have you tried installing the latest TWRP, wipe the phone and flash a nandroid backup?
Hello all,
I've been browsing the forums for a few days now trying to fix my issue, but nothing I have found seems to be of much help, so I have decided to register here myself and get some assistance directly.
So, I rooted my phone and flashed twrp and cyanogenmod. After several bugs and overall irritation, I have decided to just go back to stock recovery, ROM, etc. (After all, I am a mechanical engineer - software is not my forté.)
In attempting to unroot my device, however, it seems that I just messed things up even further.
Steps taken:
1) Rebooted device into fastboot
2) fastboot oem lock
3) Reboot into RUU mode (black screen w/ htc logo)
4) Ran RUU.exe
5) (bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 35.173s
At this point, I thought that maybe it was because I was still S-ON so I was going to place rumrunner on the virtual SD. Now my PC won't recognize my phone, so I don't know how to flash rumrunner to go to S-OFF or if that's even the correct next step. So basically, I have bootloader and twrp, and that's it.
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35ZW915640
(bootloader) imei: 354439051027912
(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: 3658mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
MJGiuffre said:
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Click to expand...
Click to collapse
wrong way
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
there is no ruu for your sofware, older one will not work its just how htc are made, try this ruu its the latest.( make sure you are not supercid before running it, it can mess up the phone) from your first post it looks like you are fine unless u changed it to supercid.
http://dl3.htc.com/application/RUU_...06_10.46.1718.01L_release_424933_signed_2.exe
it should work at least it worked on mine
---------- Post added at 03:07 PM ---------- Previous post was at 03:00 PM ----------
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
also u can try one of the guru resets that matches your software , or look for a stock unrooted nandroid for att htc one , u need the 5,12 sofware , older one may not work properly. also before runing a ruu make sure your bootloader is loked or relocked. good luck.