Hello all,
So here's why I'm posting:
I'm having an issue with my M8 phone. The phone was working great until I tried to install a new third-party TWRP. I don't know if it was miscommunication or what, but in the process of installing it (https://www.dropbox.com/s/ocvavpttfo...ersion_Fix.img), the phone started having issues.
The initial issue was that the phone would get stuck during boot up. The phone was at the current 2.22 build # but in order to make it at least usable again, I flashed an RUU (1.57 build #) and that seemed to fix everything. But then when I went back from stock recovery to my original TWRP, and flashed a recent backup, the phone froze again during boot up. This process worked many times and as recently as yesterday, but now since trying to install that third-party TWRP, it doesn't. I've tried various things but nothing is working. I know that since I can still reach HBOOT and TWRP that there is hope, but I'm at my wits end as to what to do.
I should also mention that I was using the ViperOne M8 ROM (2.1.0). My phone is unlocked/rooted & S-OFF. There were no issues with it again until I tried to install that new TWRP.
I really love my phone, and hope someone on here can help me. After re-RUUing my phone, I'm going to leave it at 1.57 build # and stock recovery (1.12 #) (and USB Debugging on) until I hear from someone. Basically, I just want my phone to be normal again so I can upgrade back to build # 2.22, flash my custom TWRP recovery, and then flash my most recent backup which included the most recent ViperOne M8 update.
Other info you might want:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.531.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Thank You,
RockStar2005
RockStar2005 said:
Hello all,
So here's why I'm posting:
I'm having an issue with my M8 phone. The phone was working great until I tried to install a new third-party TWRP. I don't know if it was miscommunication or what, but in the process of installing it (https://www.dropbox.com/s/ocvavpttfo...ersion_Fix.img), the phone started having issues.
The initial issue was that the phone would get stuck during boot up. The phone was at the current 2.22 build # but in order to make it at least usable again, I flashed an RUU (1.57 build #) and that seemed to fix everything. But then when I went back from stock recovery to my original TWRP, and flashed a recent backup, the phone froze again during boot up. This process worked many times and as recently as yesterday, but now since trying to install that third-party TWRP, it doesn't. I've tried various things but nothing is working. I know that since I can still reach HBOOT and TWRP that there is hope, but I'm at my wits end as to what to do.
I should also mention that I was using the ViperOne M8 ROM (2.1.0). My phone is unlocked/rooted & S-OFF. There were no issues with it again until I tried to install that new TWRP.
I really love my phone, and hope someone on here can help me. After re-RUUing my phone, I'm going to leave it at 1.57 build # and stock recovery (1.12 #) (and USB Debugging on) until I hear from someone. Basically, I just want my phone to be normal again so I can upgrade back to build # 2.22, flash my custom TWRP recovery, and then flash my most recent backup which included the most recent ViperOne M8 update.
Other info you might want:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.531.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Thank You,
RockStar2005
Click to expand...
Click to collapse
You will get better information in the HTC One M8 forum!
majmoz said:
You will get better information in the HTC One M8 forum!
Click to expand...
Click to collapse
Ok thanks! As long as they can help a T-Mobile guy like me!
Thanks,
RockStar2005
Related
I recently acquired an HTC One SV from Boost mobile to try to fix. The previous owner ran a tool meant for a different phone to try to root the device. When I received it, it was stuck at the HTC splash boot screen with a message on the bottom saying that this is for development purposes only. I have tried going into the bootloader and flashing every image that I could find of boot, recovery, and radio. I found images that were supposedly stock and it still does not boot.
Suggestions say to take and flash a RUU to the device. The only official RUU for the region (OTA_K2_CL_JB_45_S_Sprint_WWE_Boost_2.06.653.5-1.11.653.1_release_3244713ijuyqp8g1s0xuaw.zip) I could find does not flash with an error #12. I then tried to find a method to turn the device to S-off but cannot find anything that can be done when not booted into ICS. Does anyone know a way to turn the phone to S-Off within just the fastboot OR does anyone have a backup that will fit my phone using CWM or TWRP as I can boot into them. I also ran into issues with links not working such as the system.img file located in http://forum.xda-developers.com/showthread.php?t=2292432
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.01.0000
(bootloader) version-baseband: 1.12.50.0115
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *********
(bootloader) imei: **********
(bootloader) product: k2_cl
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8011000
(bootloader) cidnum: SPCS_003
(bootloader) battery-status: good
(bootloader) battery-voltage: 4281mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
Thank you for the help!!!
So flashing a rom went wrong somewhere, and I've probably dug myself a deeper hole trying to fix it of course. I can get to bootloader, and I can also get to CWM and/or twrp recovery, however sideloading always fails. Here's a snapshot of where I am now after mucking around too much.
Looking for some help on what steps I need to take to get my baby working again.
boot 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: 1.00.000.0
(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: 4202mV
(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!
simplydroid said:
Looking for some help on what steps I need to take to get my baby working again.
Click to expand...
Click to collapse
Not sure if this will work for you or not, with the S-ON thing, but try this:
http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
This is the RUU for the latest (current) T-Mobile update. It should wipe and return your device to 100% stock.
Normally RUU's will not work with S-ON, but I believe that's only for "downgrading"and not for flashing the current version. Should work. Can't hurt to try.
Download it, reboot into fastboot, and run the RUU. It'll take a while, but should work.
PhoenixPath said:
Download it, reboot into fastboot, and run the RUU. It'll take a while, but should work.
Click to expand...
Click to collapse
That got me going, thanked.
Hi, as title states, i purchased a HOX+ 64gb which did not boot, tried factory settings etc etc and always got stuck, tried finding an RUU and could not find for my version....
Anyway, been reading for 2 weeks on here and tried a few various things to get it to boot.
All failed until Android Revolution.
I put a custom recovery on, think its Team Venom Mod of TWRP
Unlocked The bootloader following instructions on here HTC Dev.
flashed boot.img extracted from AndroidRev8.0 zip (did not flash in fastboot so used a script that allows to flash from recovery on this forum)
Flashed the rom from recovery, and brilliant, the phone loads up, wifi bluetooth all work, just IMEI is unknown.
I've tried a few other roms from here, and they all do the same, only thing i have not tried is nandroid backup, but ive not read about them enough yet to trust myself in what im looking for.
I will post fastboot getvar all shortly, but at present im trying a locked bootloader with an RUU i just found while writing this....
Any suggestions for me to try??
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.40.0000
(bootloader) version-baseband: 3.1204.168A.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.17.401.3
(bootloader) serialno: FA2B6W102293
(bootloader) imei: IMEI does show correctly here.....
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3840mV
(bootloader) devpower: 58
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.532s
anyone can help me with this? or a link to an RUU that would restore to stock??
I have a bone stock M8 on Marshmallow. It suddenly started having com.htc.contacts errors and the phone becomes unavailable. I've done multiple recoveries, resets and cache clearing. Sometimes it comes back for awhile but soon eras out. I chatted with HTC support and they suggested reloading the rom so I downloaded the AT&T version and did all the steps per the instructions and started the update. It gets stuck on the "sending" stage and never completes. Reading the forum I saw Sync Manager can be a blocker so I didn't do it through that but no go. Am I missing something? Thanks I searched but didn't find this.
I assume you actually have the AT&T version M8?
If so, RUU stuck "sending" is common. You may need to find a Win7 PC with USB 2.0, which has the best chance of compatibility.
Back to Stock
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?
Hi, I was trying to revert back to the stock AT&T 6.0 rom using the RUU. I have "Android Revolution HD 53.1" currently installed which is Android 6.0 and Sense 7.0. It is unlocked and S-on, so I re-locked the phone using the fastboot method. After that the fastboot screen had "***RE-LOCKED*** and ***SECURITY WARNING***" on it. The phone would not reboot normally anymore, it would only go to the fastboot/hboot screen. I tried using the RUU anyway, and while it would detect the phone during the setup stages, as soon as it started the update and the phone switched to the htc screen, it would stop and give "error 171 - lost communication with the device."
So I've unlocked it again and it's working fine again. How can I revert it to the stock rom without making it S-off? Thanks!
Oh and if it matters, on the fastboot/hboot screen, it does show an OS version. It just has "OS-"
Edit: Looked at my previous posts as it's been a while since I've came here. Saw that I made a post last year with a similar problem and that switching USB ports on my computer fixed it. Well, switching USB ports fixed this problem too.
rockr09 said:
Saw that I made a post last year with a similar problem and that switching USB ports on my computer fixed it. Well, switching USB ports fixed this problem too.
Click to expand...
Click to collapse
Nice work figuring it out yourself!
rockr09 said:
After that the fastboot screen had "***RE-LOCKED*** and ***SECURITY WARNING***" on it. The phone would not reboot normally anymore, it would only go to the fastboot/hboot screen.
Click to expand...
Click to collapse
FYI, this is normal and expected. Relocking the bootloader renders the phone unable to boot, as it expects RUU to be run immediately thereafter.
Back to Stock
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?