So my htc is 2 years old and it's starting to have some problems. Right now when I tried to restart it it just got stuck on the android logo. I've read a lot on the internet but since I am entirely new to this I decided to come here so i can get a valid answer on my current options. Do i have to use ruu to make it alive and if yes which version to download? Are there any there any other options? I got adb and fastboot on my windows. Right now the phone is connected to the pc with usb in bootloader mode. Here are some pieces of info about my phone
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__032
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Also , if i install the ruu, is there anything left to do after? or can i just reboot my phone and watch it open finally?
therzvsm said:
Right now when I tried to restart it it just got stuck on the android logo. I've read a lot on the internet but since I am entirely new to this I decided to come here so i can get a valid answer on my current options. Do i have to use ruu to make it alive and if yes which version to download? Are there any there any other options?
Also , if i install the ruu, is there anything left to do after? or can i just reboot my phone and watch it open finally?
Click to expand...
Click to collapse
You can try to do factory reset, wipe cache and Dalvik, all within bootloader/stock recovery. But if that doesn't help, we see a good amount of reports like yours, where it seems like the OS has been damaged or corrupt. In which case, simply doing factory reset or wiping cache, is not going to fix it.
In that case, RUU is certainly an option, and probably the easiest. The correct RUU for your device, plus instructions how to flash, can be found here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Once RUU is installed, nothing else to really do. Just boot up the phone (hopefully will boot to Android OS) and setup the phone again. Note that RUU will wipe all personal data on the phone.
Another option is to unlock the bootloader, flash TWRP, and install a stock TWRP backup (stock ROM) as outlined in the following thread: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But note that unlocking the bootloader also wipes all user data. So you aren't gaining anything with this method, and it is a significantly longer and more complicated process. So again, I think RUU is your best bet.
Related
Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(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.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.
n1234d said:
Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(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.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.
Click to expand...
Click to collapse
The attached image is where it gets stuck. Adb works
E:\m8\>adb devices
List of devices attached
HT45NWM07703 device
@EddyOS, @nkk71 please see this. I think there's something wrong with my /data partition..
Did you recently do the GPE conversion?
May be you should try to flash the stock rom and stock recovery then flash the ruu.
Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
This, the partitions get altered so you can't just simply flash back
According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go
Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
Nope
Jyotirdeb said:
May be you should try to flash the stock rom and stock recovery then flash the ruu.
Click to expand...
Click to collapse
I hadn't touched the firmware, so there shouldn't be any problem related to that. Anyways, a rom and recovery do Not affect an RUU flash.
ashyx said:
This, the partitions get altered so you can't just simply flash back
Click to expand...
Click to collapse
Again, nope, I didn't do gpe
EddyOS said:
According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go
Click to expand...
Click to collapse
I flashed the international fw zip, and ARHD, (I had checked the hash of the file) and it still didn't work. Also, when I would reboot, some random artefacts would appear during the boot animation (different each time, sometimes wouldn't appear), such as there would be a random flash of purple across the screen or the boot animation would leave a trail behind it (like the effect you get web you would drag a stuck window in win98) etc. sometimes TWRP would act extremely sluggish while sometimes it would be fast and snappy. Quite a few times, while flashing any rom, the screen would go black and reboot to TWRP at random (even after disabling the display timeout). I tried formatting all the partitions on the internal storage. Still gave me problems. I tried to repair file system of each partition in TWRP. The data partition could never get repaired. All of these random problems lead me to believe that this was 99% the fault of the phone/hardware. Luckily I was within the 14 day replacement period and so I went out today after flashing the faux locked/s-on bootloader (I know I should not mess with firmware unless required, and I hadn't till now but I didn't care anymore since I was getting it replaced anyway. I also had 2 dead pixels and a scratch on my camera glass. Now I just have to sit back and wait for a new phone
We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!
Sneakyghost said:
We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!
Click to expand...
Click to collapse
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.
Yeah well no idea then. Just know I've seen this happen from wrong recoveries. Also not the time to dig into it any further if you've gotten that resolved already I'll leave it as is. Thanks for asking me though. Just keep in mind I've been out of XDA since months and am only slowly reading my way back in so I'm sure there are way more knowledgeable guys around regarding firmware, softbricks and the like.
mobile post... lazy typing...
n1234d said:
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.
Click to expand...
Click to collapse
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
7mojo said:
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk
n1234d said:
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks
7mojo said:
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks
Click to expand...
Click to collapse
Bump!
Anyone?
Hi guys,
I received my AT&T HTC M8 last week.
I wanted to flash the Android Revolution HD rom so I unrooted the device, installed TWRP, super CID it and S-Off it.
I tried to install the Rom but the WIFI didn't work so I rolled back to the Stock using TWRP.
I did some reaches and realize I need to update the Firmware so I did. The messaged at the end of the process was "completed successfully" but when I rebooted the device it got stuck at the splash screen. I can hear the ATT load chime but the AT&T icon is not displayed and that's it, stuck!!!!
I entered the HBoot and tried to access the recovery. The screen gets black with a red triangle icon in the center and the device reboot after several minutes. I think the Hboot message is no image.
When I connect the device to the computer it is recognized and I can access the files etc. but the ADB doesn't see the device any more.
I'm really lost and frustrated after hours and hours of reading and research without any luck.
Any help will be truly appreciated.
This is the device variables before I updated the firmware:
(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-OFF
(bootloader) serialno: HT453WM01167
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(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!
I look forward to your advice.
Thanks a lot in advance.
ronf0303 said:
Hi guys,
I received my AT&T HTC M8 last week.
I wanted to flash the Android Revolution HD rom so I unrooted the device, installed TWRP, super CID it and S-Off it.
I tried to install the Rom but the WIFI didn't work so I rolled back to the Stock using TWRP.
I did some reaches and realize I need to update the Firmware so I did. The messaged at the end of the process was "completed successfully" but when I rebooted the device it got stuck at the splash screen. I can hear the ATT load chime but the AT&T icon is not displayed and that's it, stuck!!!!
I entered the HBoot and tried to access the recovery. The screen gets black with a red triangle icon in the center and the device reboot after several minutes. I think the Hboot message is no image.
When I connect the device to the computer it is recognized and I can access the files etc. but the ADB doesn't see the device any more.
I'm really lost and frustrated after hours and hours of reading and research without any luck.
Any help will be truly appreciated.
This is the device variables before I updated the firmware:
(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-OFF
(bootloader) serialno: HT453WM01167
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(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!
I look forward to your advice.
Thanks a lot in advance.
Click to expand...
Click to collapse
You have old, 4.4.2 firmware. That is the issue. Get new firmware and instructions on installing it here or here.
Thanks for getting back to me.
The firmware you see in the var. list I placed above is before I changed the Firmware.
As a result the phone is stuck on the splash screen.
I found post Firmware Flashing without the panic attacks... ; (you recommended) and followed the instructions.
The firmware update was complete...
Since that point the phone doesn't boot.
I did a Factory Reset yet still no change.
The most annoing fact is that I can get to the device with ADB.
When I type ADB Devices I get empty list
ronf0303 said:
Thanks for getting back to me.
The firmware you see in the var. list I placed above is before I changed the Firmware.
As a result the phone is stuck on the splash screen.
I found post Firmware Flashing without the panic attacks... ; (you recommended) and followed the instructions.
The firmware update was complete...
Since that point the phone doesn't boot.
I did a Factory Reset yet still no change.
The most annoing fact is that I can get to the device with ADB.
When I type ADB Devices I get empty list
Click to expand...
Click to collapse
ADB only works in custom recovery or when booted into OS
Fastboot will work on fastboot mode.
Do flash a custom recovery using fastboot. And also erase cache position before booting into custom recovery
It's working - I'm so happy
Hi guys,
Thanks for your support.
Bottom line - The phone is up and running ARHD Ver 21.
I repeated the whole process (flashing the firmware and the rom) but this time instead of flashing the FW I downloaded from the Revolution site (3.32.531.2) I flashed 3.32.531.2_Firmware_TMUS.ZIP I downloaded from
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
So thanks so much for your support.
I'm really really happy
Hello, so quite sometime ago I rooted my phone, or unrooted it. I am not sure what the term is, I dont even remember why I done this in the first place. Anyways today I wanted to just put my phone back to like it was when I got it, and in doing so I have actually broke my phone I can't get my phone to boot up anymore, I always get a message saying I have no OS installed. I am really useless with all of this so I would appreciate it if there is a patient person out there who can help me get my phone back on and back to how it was when I recieved it. I am sure I need to add more information but I dont know what so please tell me what you guys need to know and I will try and provide the answers.
This should be the first rule when asking for help.
Post fastboot getvar all result (delete serial & imei no.)
Without this info, no one will be able to offer any help
ckpv5 said:
This should be the first rule when asking for help.
Post fastboot getvar all result (delete serial & imei no.)
Without this info, no one will be able to offer any help
Click to expand...
Click to collapse
Where do I find this?
Do you have fastboot & adb on your PC ? You should have one, if not how can you install a custom recovery and root your device before ?
If you're not sure .. install this : http://forum.xda-developers.com/showthread.php?t=2317790
Put your device in bootloader mode and connect to PC
Open a command prompt and type fasboot getvar all then "enter"
Copy the outcome and paste here
ckpv5 said:
Do you have fastboot & adb on your PC ? You should have one, if not how can you install a custom recovery and root your device before ?
If you're not sure .. install this : http://forum.xda-developers.com/showthread.php?t=2317790
Put your device in bootloader mode and connect to PC
Open a command prompt and type fasboot getvar all then "enter"
Copy the outcome and paste here
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I think thats what you want right?.
Yes .. that's the one.
You have two options :
Option 1:
Install new stock ROM with a RUU - Download : https://www.androidfilehost.com/?fid=95916177934555499
you need to relock bootloader - run command fastboot oem lock
run RUU (right click the RUU and select run as administrator)
you need to use USB2.0 on your PC
RUU will wipe everything on your device including your files on internal storage
Option 2:
Restore a non-rooted TWRP backup 4.20.206.1
No need to relock bootloader
No internal storage wipes
Read how-to and all the needed files are here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Good luck .. I have to sleep now, good night
ckpv5 said:
Yes .. that's the one.
You have two options :
Option 1:
Install new stock ROM with a RUU - Download : https://www.androidfilehost.com/?fid=95916177934555499
you need to relock bootloader - run command fastboot oem lock
run RUU (right click the RUU and select run as administrator)
you need to use USB2.0 on your PC
RUU will wipe everything on your device including your files on internal storage
Option 2:
Restore a non-rooted TWRP backup 4.20.206.1
No need to relock bootloader
No internal storage wipes
Read how-to and all the needed files are here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Good luck .. I have to sleep now, good night
Click to expand...
Click to collapse
Option one just stays on updating 0/6 sending and nothing happens. Option 2 doesnt make sense to me, I really have no idea what most of it means.
Ok so this morning I tried option one again. It went through the first 6 stages fine, then it got stuck on the next set of stages at 1/7. When I restart my phone into the recovery screen type thing I have in red letters OS - (4.20.206.1) but I am still unable to start my phone up. I have disabled firewalls and also using USB2.0 when trying to do this process. Maybe this one that has been linked is not the right one for me? Or maybe I am doing something wrong?. I would really love to get my phone back working so all help is really appreciated.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
You have USB/Device connection problem. First it was 0/6 and now 1/7 ...
Which windows version that you use ? try with a Win7 PC .. I don't know many people cannot run RUU on windows higher version that Win7. I don't have problem on any windows version including my current Win 10.
What do you don't understand about option 2 ? It's very straight forward.
Install latest TWRP 2.8.6.0 or TWRP 2.8.7.0 (you need to reunlock bootloader because you relocked it for option 1)
Extract and copy the backup folder to TWRP backup on your device
Restore backup .. done
Or
Just install any of Sense based ROM that available in Development thread to get your device up & running ... then you can start that option 1 & 2 again
But seeing you mentioned OS - 4.20.206.1 in red, you need to get option 1 done because the firmware installation was incomplete
ckpv5 said:
You have USB/Device connection problem. First it was 0/6 and now 1/7 ...
Which windows version that you use ? try with a Win7 PC .. I don't know many people cannot run RUU on windows higher version that Win7. I don't have problem on any windows version including my current Win 10.
What do you don't understand about option 2 ? It's very straight forward.
Install latest TWRP 2.8.6.0 or TWRP 2.8.7.0 (you need to reunlock bootloader because you relocked it for option 1)
Extract and copy the backup folder to TWRP backup on your device
Restore backup .. done
Or
Just install any of Sense based ROM that available in Development thread to get your device up & running ... then you can start that option 1 & 2 again
But seeing you mentioned OS - 4.20.206.1 in red, you need to get option 1 done because the firmware installation was incomplete
Click to expand...
Click to collapse
Yes maybe I do but I am not sure why, maybe I need to look into seeing if my motherboard needs an update or if any windows updates are needed. I am on Windows 7 but like I said, it goes through the first 6 steps then as it boots the bootloader up again I hear the sound that my computer makes when plugging in a USB cable. However even if I leave it, it will not go past 1/7. But if I take the cable out it reconises I have done that so that makes me wonder if it is a USB problem?.
I dont understand option 2 because I dont know anything about all of this, I shouldnt have done it in the first place and I dont even remember why I did. I also must have deleted my backups as I cant find them. The part I was confused at, was which TWRP to get, then how to get it on my phone as my computer does not reconise my phone in the state it is in so I cant just go into the phone and place it. I also dont have an SD card with my phone either.
I will try updating my PC and try and get option 1 working and report back. Thank you for helping by the way, I really appreciate your patience with me.
Try also to install latest HTC USB driver.
Download HTC Sync Manager and install. Then uninstall the HTC Sync Manager but leave the HTC Driver installed.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
Is there a way to wipe this OS version and try this whole thing again? I have found my 2.0 USB ports, I have tried a different cable and it still gets hung up. Only now it doesnt move past the 0/6 whereas it used to go through all of them then into the 1/7 and get stuck on this part. I also can try a different PC if need be.
KDK11 said:
I also can try a different PC if need be.
Click to expand...
Click to collapse
That is what I would suggest.
Also, does your PC have USB 3.0 on the ports? This has been known to cause problems with the RUU.
Ok so I have done the steps suggested now, when I uninstalled the HTC Sync Manager it let the process complete. It is now on a screen which says Android is upgrading, optimizing app 17-261. Is that my phone fixed? Or is there more I need to do now that it actually has turned on?.
KDK11 said:
It is now on a screen which says Android is upgrading, optimizing app 17-261. Is that my phone fixed?
Click to expand...
Click to collapse
Looks that way. It should boot into OS after its done optimizing all the apps, which is normally pretty slow (with that many, it will take 10 or more) since Android moved from Dalvik to ART.
Well I would like to say a massive thank you for the help I really appreciate the patience and help. So thank you again. I would have been lost without you's.
KDK11 said:
Ok so I have done the steps suggested now, when I uninstalled the HTC Sync Manager it let the process complete. It is now on a screen which says Android is upgrading, optimizing app 17-261. Is that my phone fixed? Or is there more I need to do now that it actually has turned on?.
Click to expand...
Click to collapse
That's it ... nothing else to do .. run the setup wizard and enjoy your device
KDK11 said:
Well I would like to say a massive thank you for the help I really appreciate the patience and help. So thank you again. I would have been lost without you's.
Click to expand...
Click to collapse
No problem .. glad that we could help
O2 RUU Marshmallow CID O2_001 pleaseee
Hi!
I have an HTC One M8 from O2 UK, that i give me a lot of problem after updating to Marshmallow.
After successfully complete the update i have done a factory reset which i guess it soft brick my phone.
It will show optimizing apps, after that starting apps and is stuck there until battery dies. I try many methods, formatting cache partition from recovery menu, made another factory restore from fastboot, I even left it plugged one night and nothing.
The only hope is if i find a RUU for CID O2_001
The phone is S-ON non rooted, i unlock then re lock boot loader thanks to htcdev website.
adb fastboot getvar command show this.
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: .................................................
(bootloader) imei: .......................................
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.126s
Please help me made the phone working again!
Thank you!
cossty said:
Hi!
I have an HTC One M8 from O2 UK, that i give me a lot of problem after updating to Marshmallow.
After successfully complete the update i have done a factory reset which i guess it soft brick my phone.
It will show optimizing apps, after that starting apps and is stuck there until battery dies. I try many methods, formatting cache partition from recovery menu, made another factory restore from fastboot, I even left it plugged one night and nothing.
The only hope is if i find a RUU for CID O2_001
The phone is S-ON non rooted, i unlock then re lock boot loader thanks to htcdev website.
adb fastboot getvar command show this.
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: .................................................
(bootloader) imei: .......................................
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.126s
Please help me made the phone working again!
Thank you!
Click to expand...
Click to collapse
Hello,
In this thread you will find the firmware for your phone. It looks like you know the process of installing your firmware, so if I were you I'd down load the proper firmware and try the whole process all over again.
Jerrel7 said:
Hello,
In this thread you will find the firmware for your phone. It looks like you know the process of installing your firmware, so if I were you I'd down load the proper firmware and try the whole process all over again.
Click to expand...
Click to collapse
Hi!
I didn't find because it is to new. It's an O2 UK, android 6 version, cid O2_001.
I did something else, i flashed TWRP recovery and then i flash latest InsertCoin rom, and now the phone it is working again.
Thank you!
Hi
I have a problem with a UK M8 which originally had a cracked screen and I replaced it. All good except for some issue of which I cant remember what it was as it was a long time ago. I assumed a sw fault so did OTA update to Marshmallow. However I think it failed during install and then got stuck on htc logo. Factory resets etc had no effect.
So after doing extensive searching I decided to try other methods so unlocked the bootloader and tried to install a rom. To cut a long story short, I have tried everything that I can but I cannot get the phone to boot into OS. I can get it to do the optimizing apps and then it changes to starting apps but sticks on the starting apps screen even if I leave it all day. I have tried various methods but always end up with a phone which will not boot to OS. It did briefly boot into os (partly) butapart from the background and the battery info and couple of other top line details nothing else, then it rebooted itself and htc logo stuck again. I have over the course of time wiped everything from the phone so it has nothing original on it.
The last thing I have done is flashed a signed firmware and have tried using ckpv5s nandroid backups on sd card and also the renaming to 0P6BIMG and sd card flash that way. Same result.
I am now fed up and so need some help. I just want the bloody thing to work again.
Huge thanks in advance
Details as follows
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ###########
(bootloader) imei: ############
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I am betting that I have made a schoolboy error. I am also suspecting a hardware fault.
I have twrp 3.0.2.0 installed. Unlocked bootloader.
Hazlo99 said:
The last thing I have done is flashed a signed firmware and have tried using ckpv5s nandroid backups on sd card and also the renaming to 0P6BIMG and sd card flash that way. Same result.
I have twrp 3.0.2.0 installed. Unlocked bootloader.
Click to expand...
Click to collapse
restoring nandroid backup is solve the issue of faulty OS if your device doesn't have an official RUU ( as your device )
so try to restore your devices backup ( again if you do it following OP instruction ) from ckpv5 thread i doubt it will fail if it's software issue
Good luck
Hey guys and gals!
I have a completely stock Sprint HTC M8. Here's my dilemma. I used (unknowingly) a faulty cable to charge my phone after a full battery drain. Once I realized there was a problem with cable, I used an OE cable and fully charged the phone. As the title states, after powering the phone it bootloops until it dies. Sometimes it gets past the boot screen and I can see the phones home page for a short time (which is still the same as when I customized it when the phone was fully functional). But it inevitably bootloops.
I have tried to RUU, Flash an OTA, even hard reset and I end up with the same bootloop and the same version of the OS/ROM on the phone.
As you can see from the previous passage, I have come to a resolve regarding the loss of data on the internal sdcard. But if there is a way to preserve the data based on the information I've shared, please inform me.
For information purposes to help with this situation, here is the getvar information:
fastboot getvar all
ERROR: could not get pipe properties for endpoint 1 (e0004061)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.654.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ______________
(bootloader) imei: _______________
(bootloader) imei2: Not Support
(bootloader) meid: _______________
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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.007s
Any help is appreciated. Thanks in advance.
StillUseMyEvo4G said:
I have tried to RUU, Flash an OTA, even hard reset and I end up with the same bootloop and the same version of the OS/ROM on the phone.
Click to expand...
Click to collapse
Which RUU? It needs to be the specific RUU (6.20.654.3) for the Sprint HK version. Any other RUU will fail by intention, and should give you an error message. If you tried an RUU, and it didn't work, we would need some specific information on what RUU, description of the error message or other failure circumstances.
Flashing an OTA won't work. You can't OTA update a phone which is already up-to-date (which your phone is). And you also can't manually flash an OTA with s-on, anyway.
StillUseMyEvo4G said:
As you can see from the previous passage, I have come to a resolve regarding the loss of data on the internal sdcard. But if there is a way to preserve the data based on the information I've shared, please inform me.
Click to expand...
Click to collapse
If you are trying to run an RUU, you are past the point of preserving your data, as RUU will wipe the phone. Or you are misunderstanding what the RUU does.
Do you have USB debugging enabled, or can boot to OS long enough to toggle it on? Does it stay powered on, in bootloader?