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.
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.
okay,
I've unlocked the bootloader, rooted it, it's s-on and installed cm11. After less than a day, I've decided to go back to stock. Unfortunately, because cm11 is kitkat 4.4 it seems I can't even use an ruu, as they'll only go to 4.3 (which it seems i can't use because with s-on, I can't downgrade firmwares).
I've used Twrp 2.6.3.3 for recovery.
i've tried to use moonshine and rum runner, but they both fail, presumably because i've got cm11 installed. Also, when I connect to the pc, it only comes up as a media player or camera (depending on the settings in cyanogenmod), I've got debugging on and i believe everything else I should have.
In device manager, it calls itself "My HTC", yet in utorrent "HTC Aria"
When running (in cmd) "adb devices" it shows my phone, but when I do "fastboot devices" nothing comes up.
i've tried installing htc drivers, but nothing seems to change it. Some have mentioned forcing drivers but I don't know where to get the specific htc one driver.
in the bootloader this is what comes up:
hboot 1.44
m7ul pvt ship s-on rh
radio 4A.12.3750.20
open dsp v31.120.274.0617
eMMC-boot
what are my next steps/options?
damiancds said:
okay,
I've unlocked the bootloader, rooted it, it's s-on and installed cm11. After less than a day, I've decided to go back to stock. Unfortunately, because cm11 is kitkat 4.4 it seems I can't even use an ruu, as they'll only go to 4.3 (which it seems i can't use because with s-on, I can't downgrade firmwares).
I've used Twrp 2.6.3.3 for recovery.
i've tried to use moonshine and rum runner, but they both fail, presumably because i've got cm11 installed. Also, when I connect to the pc, it only comes up as a media player or camera (depending on the settings in cyanogenmod), I've got debugging on and i believe everything else I should have.
In device manager, it calls itself "My HTC", yet in utorrent "HTC Aria"
When running (in cmd) "adb devices" it shows my phone, but when I do "fastboot devices" nothing comes up.
i've tried installing htc drivers, but nothing seems to change it. Some have mentioned forcing drivers but I don't know where to get the specific htc one driver.
in the bootloader this is what comes up:
hboot 1.44
m7ul pvt ship s-on rh
radio 4A.12.3750.20
open dsp v31.120.274.0617
eMMC-boot
what are my next steps/options?
Click to expand...
Click to collapse
cm 11 did'nt update your firmware
what's your results for fastboot getvar all
run it from the bootloader screen / fastboot usb (remove your serial no and iemi)
all it says is "< waiting for device >"
this leads me to believe there's a driver error?
Sorry, I'm an idiot
C:\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(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.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(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: 4315mV
(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.056s
damiancds said:
all it says is "< waiting for device >"
this leads me to believe there's a driver error?
Sorry, I'm an idiot
C:\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(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.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(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: 4315mV
(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.056s
Click to expand...
Click to collapse
this is the last AT&T RUU it will update you to android 4.3 >>
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
if that link is slow you can get it directly from HTC here >>
http://www.htc.com/us/support/htc-one-att/news/
you'll have to relock your bootloader
fastboot oem lock
then run the RUU with your phone sitting at the fastboot usb screen
Worked beautifully. Thank You.
there's only two niggling things. when you pull down for your notifications, in the top right used to be settings, now it's quick tiles like cm11.
Also, in my computer, the device shows up as portable media player, where it used to just show up as htc one and an icon that looked like it. (from quick reading, it seems this is normal.)
Thanks again for all your help
damiancds said:
Worked beautifully. Thank You.
there's only two niggling things. when you pull down for your notifications, in the top right used to be settings, now it's quick tiles like cm11.
Also, in my computer, the device shows up as portable media player, where it used to just show up as htc one and an icon that looked like it. (from quick reading, it seems this is normal.)
Thanks again for all your help
Click to expand...
Click to collapse
yeah welcome to android 4.3 .. it's different, wait till you get sense 5.5 in the kitkat update
clsA said:
yeah welcome to android 4.3 .. it's different, wait till you get sense 5.5 in the kitkat update
Click to expand...
Click to collapse
I know now, a rough search turned up the same....
One last question,
I'm sticking with stock, but i want to root it, everything i've done has been unsuccessful, where before first time and it was done, I was reading the guide over here, http://forum.xda-developers.com/showthread.php?t=2273376&page=2 , and it mentions that I can't root a stock rom? that means I would need to grab one of the rooted ones then, correct? I know I've seen a link to them around here, but can't seem to find it, let alone which one I should use.
damiancds said:
I know now, a rough search turned up the same....
One last question,
I'm sticking with stock, but i want to root it, everything i've done has been unsuccessful, where before first time and it was done, I was reading the guide over here, http://forum.xda-developers.com/showthread.php?t=2273376&page=2 , and it mentions that I can't root a stock rom? that means I would need to grab one of the rooted ones then, correct? I know I've seen a link to them around here, but can't seem to find it, let alone which one I should use.
Click to expand...
Click to collapse
after running the RUU your starting from scratch
1.unlock bootloader at HTCDEV.com
2. Flash custom recovery I recommend TWRP 2.6.3.3
How to flash?
1) Download your recovery
2) Put it on your adb/fastboot folder
3) Rename it to recovery.img
4) Open a CMD/Teminal windows on adb folder
5) Put your phone in fastboot
6) Flash the recovery with the command:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
3. flash custom rom 3.17.502.3 Stock Rooted
That should do it if your Root needs updated
download and flash this same as a rom
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
i'd installed cm11 via installer but now i wanna go back to sense
i'd installed cm11 via cm installer but now i wanna go back to stock sense,sadly i couldnt find the suitable RUU for my device.Since im really new to this android system i dont have any ideas bout flashing or locking the devices,could u guys please help me out?
i'd tried turning S off with rumrunner but at the end i was struck on an error.
here are my devices details.
m7_U S on
Hboot 1.56
CID : htc__038
version : 4.20.707.7
THANKS.
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?
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.058s
I am stuck, I can't see to get my phone to boot. You would think that I would be able to do something to fix this if I can get into recovery and bootload, but I can't get a proper system boot. I am hoping that buying a new phone isn't my only option at this point. If anyone can help me I am willing to pay if you can help me get a working phone again.
@Jameskhunter
You should edit your IMEI number out of your getvar
What exactly happened when you flashed the firmware ,any specific message that came across that you can remember
According to the getvar it looks like you flashed the GPE lollipop firmware/ruu without
S-OFF.
---------- Post added at 03:47 AM ---------- Previous post was at 03:37 AM ----------
Try this .exe of the stock ruu sense your At&t
http://forum.xda-developers.com/showthread.php?t=2860423
GPE firmware
jball said:
@Jameskhunter
You should edit your IMEI number out of your getvar
What exactly happened when you flashed the firmware ,any specific message that came across that you can remember
According to the getvar it looks like you flashed the GPE lollipop firmware/ruu without
S-OFF.
---------- Post added at 03:47 AM ---------- Previous post was at 03:37 AM ----------
Try this .exe of the stock ruu sense your At&t
http://forum.xda-developers.com/showthread.php?t=2860423
Click to expand...
Click to collapse
That is what I have been told although I didn't realize that it was GPE and I don't really understand why it let me get my phone in an usable/unrecoverable state if I had s-on. I thought that was a safety net, but the more I read I wish it was s-off. I think it would be fixable then, but in the current state I don't know how to get s-off. I did the firmware command twice and it seemed to work after the second attempt as the article noted that it would. I have never flashed a rom, before so other than reading the article and attempting to follow along didn't really know what to expect. The article had me do a fastboot oem lock and then a fastboot oem ruu as I recall. then it was something like fastboot flash zip .....zip. The problem is the roms that I have attempted to install now don't seem to install maybe if I could find the right one it would install and work good enough to allow me to become s-off and get back to more of a working state. I should of done a lot more reading before attempting this... I made some invalid assumptions about being able to recover which is my fault. I would think something is possible in this state.
I think part of the problem is that I am s-on and my main ver is higher than the RUU for my carrier version and my cid. I think I could edit those if I was s-off or do something, but I can't do that since I am s-on.
Hi
Jameskhunter said:
That is what I have been told although I didn't realize that it was GPE and I don't really understand why it let me get my phone in an usable/unrecoverable state if I had s-on. I thought that was a safety net, but the more I read I wish it was s-off. I think it would be fixable then, but in the current state I don't know how to get s-off. I did the firmware command twice and it seemed to work after the second attempt as the article noted that it would. I have never flashed a rom, before so other than reading the article and attempting to follow along didn't really know what to expect. The article had me do a fastboot oem lock and then a fastboot oem ruu as I recall. then it was something like fastboot flash zip .....zip. The problem is the roms that I have attempted to install now don't seem to install maybe if I could find the right one it would install and work good enough to allow me to become s-off and get back to more of a working state. I should of done a lot more reading before attempting this... I made some invalid assumptions about being able to recover which is my fault. I would think something is possible in this state.
I think part of the problem is that I am s-on and my main ver is higher than the RUU for my carrier version and my cid. I think I could edit those if I was s-off or do something, but I can't do that since I am s-on.
Click to expand...
Click to collapse
I have tried that RUU and it fails, I think because its main version number is lower than mine now... Which I also didn't realize was a limitation. I think the lesson here is to never flash firmware that isn't directly from the htc site although its suppose to be signed, that's a little confusing to me.
I to thought S-ON was supposed to be a safety net
What Roms have you tried sense then
If you hold power+up your phone hard restarts. then quickly hold power+down. then go to recovery. If have TWRP and this way you accessed it. you got some chance. go to https://download.cyanogenmod.org/?device=m8 and download latest nightly and see if you can flash it. That worked for me. Until I find a signed firmware/radio that is version 4.+ I am stuck with cm12.
Hi all,
I have refrained from posting because I thought I would just read, but now I'm at the end of my rope. I just got my ATT htc one m8. I am on T-Mobile, but the price was right for this one.
Anyway I converted my phone right out of the box literally to GPE. I also used sunshine to unlock, and s-off. Both of these seemed to go off with little trouble.
BTW: ADB fastboot, drivers and such are installed correctly.
Things were fine, so I decided to play around some more. I preceded to revert back to sense so, I could play with more roms.
Needless to say I have done a lot of trial and error, so I will tell you what's going on now. Hopefully I didn't brick anything, and hopefully it's an easy fix.
I am s-off
Here is a Getvar all. My phone is no longer seen by adb, so commands do nothing I got this read out by using the toolkit, but prefer manual.
Also I have absolutely no ROM installed so I can not enable debugging mode, I cant do anything. Is there an easy way to re-unlock the boot loader? I don't want to go through htcdev seeing as I went with sunshine.
Sorry if this is noob, but I have struggled for like the last 20 hours trying to figure this out on my own.
Bootloader says relocked (relocked due to trying to go back)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43SWM04814
(bootloader) imei: 358718050247696
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.015s
>
This should be in Q&A thread....
TireIron431 said:
Here is a Getvar all. My phone is no longer seen by adb, so commands do nothing I got this read out by using the toolkit, but prefer manual.
Also I have absolutely no ROM installed so I can not enable debugging mode, I cant do anything. Is there an easy way to re-unlock the boot loader? I don't want to go through htcdev seeing as I went with sunshine.
>
Click to expand...
Click to collapse
fastboot oem unlock
Sorry I messed up. If you just updated your firmware, then you will need to get new token from HTCdev. The /fastboot oem unlock/ only works with GPE hboot. My guess is that each hboot version comes with different unlocktoken. I just updated my firmware and had to grab a new unlock token as well (coming back from GPE).
:fingers-crossed:
TireIron431 said:
Hi all,
I have refrained from posting because I thought I would just read, but now I'm at the end of my rope. I just got my ATT htc one m8. I am on T-Mobile, but the price was right for this one.
Anyway I converted my phone right out of the box literally to GPE. I also used sunshine to unlock, and s-off. Both of these seemed to go off with little trouble.
BTW: ADB fastboot, drivers and such are installed correctly.
Things were fine, so I decided to play around some more. I preceded to revert back to sense so, I could play with more roms.
Needless to say I have done a lot of trial and error, so I will tell you what's going on now. Hopefully I didn't brick anything, and hopefully it's an easy fix.
I am s-off
Here is a Getvar all. My phone is no longer seen by adb, so commands do nothing I got this read out by using the toolkit, but prefer manual.
Also I have absolutely no ROM installed so I can not enable debugging mode, I cant do anything. Is there an easy way to re-unlock the boot loader? I don't want to go through htcdev seeing as I went with sunshine.
Sorry if this is noob, but I have struggled for like the last 20 hours trying to figure this out on my own.
Bootloader says relocked (relocked due to trying to go back)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43SWM04814
(bootloader) imei: 358718050247696
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.015s
>
Click to expand...
Click to collapse
I can help you with this...don't try anything else to your phone you will just make it harder to fix. question how did you try to convert back I need to know what all u did?
I don't remember everything I don't think.. All I did was chamge the cid a few times. I tried to install stock recoveries, I tried install anything I could. Everything seemed to fail. After I changed the cid to stock the pc stopped seeing it from what I remember. Right now all I know is that these is no recovery on it, so no twrp, and no os...and I cant get the pc to see it. I will try to get it recognized by the pc but that's all til I hear back.
abd will not work in fastboot environment. As long as your phone says "Fastboot USB connected," you are still good to go. You must grab a new unlock token from htcdev and then proceed, because it seems that each new hboot has new unlock token. Otherwise you could unlock bootloader the S-off way, which I am not aware of (my phone is S-on) :fingers-crossed:
TireIron431 said:
I don't remember everything I don't think.. All I did was chamge the cid a few times. I tried to install stock recoveries, I tried install anything I could. Everything seemed to fail. After I changed the cid to stock the pc stopped seeing it from what I remember. Right now all I know is that these is no recovery on it, so no twrp, and no os...and I cant get the pc to see it. I will try to get it recognized by the pc but that's all til I hear back.
Click to expand...
Click to collapse
I have s-off through sunshine, do I have to go through htc, or is there a way to do it again with sunshine? My phone still says fastboot usb, but commands don't work.
TireIron431 said:
I have s-off through sunshine, do I have to go through htc, or is there a way to do it again with sunshine? My phone still says fastboot usb, but commands don't work.
Click to expand...
Click to collapse
You got sdcard an can boot to bootloader rt ? If so we will install twrp like that first off
Yes I have sd card, and am at the fastboot usb screen
TireIron431 said:
Yes I have sd card, and am at the fastboot usb screen
Click to expand...
Click to collapse
Perfect. Hit me up on hangouts I should be able to get u up an running might be a very a long process. Did one last night took 4 hours. But dude is up an running. I'm going to pm you my hangouts email now.
Got it all sorted out thanks to Tigerstown. Man that was a mess lol. I appreciate the assist.
Now to try some not so stupid things. lol
TireIron431 said:
Got it all sorted out thanks to Tigerstown. Man that was a mess lol. I appreciate the assist.
Now to try some not so stupid things. lol
Click to expand...
Click to collapse
Just glad to help an glad your phone is backing in working order