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?
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?
Hey there,
C:\adb\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(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: HTC__102
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
http://forum.xda-developers.com/showthread.php?t=2701376
several months ago I have unlocked my phone, reset it to factory several times and in general just tried out installing custom recoveries to ultimately install a custom rom.
I eventually stopped before flashing a custom rom.
A few days ago I started really trying again and I have noticed that i can not install any custom roms without updating my firmware first.
My current version is 1.41.5 and i run android 4.4.2, way too outdated to do anything.
The real problem is that even relocking the bootloader, resetting to factory settings and trying to manually flash a firmware update it will not work.
I am stuck. There is no stock rom available for my third party german carrier anywhere on the internet. (Mobilcom Debitel)
It appears it is impossible to get back the bloatware that came with the phone which is required to update, right?
I don't know how to proceed at this point.
Is there any thing I can do?
Would going s-off help?
I would be very appreciative of any help you guys can give me.
I read in the following thread: http://forum.xda-developers.com/showthread.php?t=2701376
Q : Can i apply an official HTC OTA on my stock rooted rom?
A : Yes but the system apps (carrier branded apps included) has to be 100% intact.
There seems to be no way to get the carrier brand apps for me. Is there a different way?
Edit: If I achieve s-off, would that be a way around my issue?
With your current knowledge base S-OFF would surely lead to a brick. I would wait on that. You need to return to stock recovery, take your carriers OTA's of which there will be at least three or four, then you will be able to install any current ROM. Search return to stock thread for a 1.54.xxx recovery for your CID.
crovean11 said:
Hey there,
C:\adb\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(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: HTC__102
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
http://forum.xda-developers.com/showthread.php?t=2701376
several months ago I have unlocked my phone, reset it to factory several times and in general just tried out installing custom recoveries to ultimately install a custom rom.
I eventually stopped before flashing a custom rom.
A few days ago I started really trying again and I have noticed that i can not install any custom roms without updating my firmware first.
My current version is 1.41.5 and i run android 4.4.2, way too outdated to do anything.
The real problem is that even relocking the bootloader, resetting to factory settings and trying to manually flash a firmware update it will not work.
I am stuck. There is no stock rom available for my third party german carrier anywhere on the internet. (Mobilcom Debitel)
It appears it is impossible to get back the bloatware that came with the phone which is required to update, right?
I don't know how to proceed at this point.
Is there any thing I can do?
Would going s-off help?
I would be very appreciative of any help you guys can give me.
I read in the following thread: http://forum.xda-developers.com/showthread.php?t=2701376
Q : Can i apply an official HTC OTA on my stock rooted rom?
A : Yes but the system apps (carrier branded apps included) has to be 100% intact.
There seems to be no way to get the carrier brand apps for me. Is there a different way?
Edit: If I achieve s-off, would that be a way around my issue?
Click to expand...
Click to collapse
First of all, delete the IMEI from your post. Never put that on a public forum.
Yes, S-Off would be a way, but the safest would be to run an RUU to update. Hook your phone up to your PC, and get into fastboot.
Download the 4.16.401.10 WWE RUU from here.
When the download if finished, double click it, and follow the prompts.
When it's finished, turn on your phone, go through the setup, and enjoy Lollipop.
Make sure to back up anything that is important to you, because this will wipe your phone.
Thank you for the replies, I will report on my success once I have tried what you have proposed, thanks!
Hi Guys
This is a n00bish post so please excuse if in wrong forum section. If so please redirect.
I was having really bad battery issues after the last O2 OTA update and my micro USB is borked. Requires me to wiggle and prop USB cable up to get the charger to work. Such a pain. I thought this may due to firmware / OS as it may have been linked to other battery issues. I think this may be due to hardware damage. and a separate issue. I am going to return to HTC but have installed a custom ROM Viper 3.2.
The battery issues have been resolved (still having charging issues possible hardware damage / fault).
After I installed Viper I realised my WiFi no longer worked.
Basically I would like the correct firmware and possibly stock OS ( Any OS that makes WiFi work is good for now)
I have been through quite a bit of searching and trial and error but cant seem to find the right firmware and stock image to to run on my M8.
This is o2 UK specific. A O2 UK RUU would be super.
Phone details
...
(bootloader) cid: O2___001
OKAY [ 0.001s]
finished. total time: 0.002s
(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.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45BWM02810
(bootloader) imei: Mod edit: IMEI removed
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
odeatomas said:
Hi Guys
This is a n00bish post so please excuse if in wrong forum section. If so please redirect.
I was having really bad battery issues after the last O2 OTA update and my micro USB is borked. Requires me to wiggle and prop USB cable up to get the charger to work. Such a pain. I thought this may due to firmware / OS as it may have been linked to other battery issues. I think this may be due to hardware damage. and a separate issue. I am going to return to HTC but have installed a custom ROM Viper 3.2.
The battery issues have been resolved (still having charging issues possible hardware damage / fault).
After I installed Viper I realised my WiFi no longer worked.
Basically I would like the correct firmware and possibly stock OS ( Any OS that makes WiFi work is good for now)
I have been through quite a bit of searching and trial and error but cant seem to find the right firmware and stock image to to run on my M8.
This is o2 UK specific. A O2 UK RUU would be super.
Phone details
...
(bootloader) cid: O2___001
OKAY [ 0.001s]
finished. total time: 0.002s
(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.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45BWM02810
(bootloader) imei: Mod edit: IMEI removed
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Hi there. I can't really help with your problem, I'm only posting here because I was assigned to move your thread from the general section to the q&a section. I did notice that you included your IMEI number in your post, I've removed it for you, don't ever post your IMEI publicly, or tell anyone what it is. Your IMEI is a unique device identifier, if it falls into the hands of the wrong people they can cause all sorts of problems for you. Anyway, good luck with your problem, just wanted to give you that advice.
odeatomas said:
Basically I would like the correct firmware and possibly stock OS ( Any OS that makes WiFi work is good for now)
I have been through quite a bit of searching and trial and error but cant seem to find the right firmware and stock image to to run on my M8.
This is o2 UK specific. A O2 UK RUU would be super.
Click to expand...
Click to collapse
You can update the firmware or a stock ROM (that matches your current firmware) but you don't need to do both.
I don't think your version has an RUU (many don't).
The stock ROM that matches your current firmware is 1.54.206.5, as determined by main version on your getvar output. The stock nandroid for 1.54.206.5 can be found on the following thread (with instructions to restore found in Post #3 of that thread, under Questions & Answers):
http://forum.xda-developers.com/showthread.php?t=2701376
Also, trial and error while flashing firmware is mostly going to fail, since with s-on you can only flash a firmware with "206" in the third number position (x.xx.206). Also, you need to have the bootloader relocked.
Additionally, I'm not sure how warranty is handled where you are. But in many places, its best practice when returning phone for warranty to s-off (by sunshine) and change the bootloader to LOCKED. UNLOCKED or RELOCKED bootloader in many places will void the warranty. The only way to make it back to LOCKED is with s-off.
odeatomas said:
Hi Guys
This is a n00bish post so please excuse if in wrong forum section. If so please redirect.
I was having really bad battery issues after the last O2 OTA update and my micro USB is borked. Requires me to wiggle and prop USB cable up to get the charger to work. Such a pain. I thought this may due to firmware / OS as it may have been linked to other battery issues. I think this may be due to hardware damage. and a separate issue. I am going to return to HTC but have installed a custom ROM Viper 3.2.
The battery issues have been resolved (still having charging issues possible hardware damage / fault).
After I installed Viper I realised my WiFi no longer worked.
Basically I would like the correct firmware and possibly stock OS ( Any OS that makes WiFi work is good for now)
I have been through quite a bit of searching and trial and error but cant seem to find the right firmware and stock image to to run on my M8.
This is o2 UK specific. A O2 UK RUU would be super.
Phone details
...
(bootloader) cid: O2___001
OKAY [ 0.001s]
finished. total time: 0.002s
(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.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: Mod edit: IMEI removed
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
First things first, since I represent Venom ROMs. Your wifi didn't work because you firmware is super old.
Secondly, you extSD is probably borked because you skimped and bought a cheap one. They don't last long.
You USB charging issues are either bad cable, charger, or charging port. The first two are easy fixes, the last is something you'll have to get repaired by a shop or HTC.
You'll have to go back to stock to update being S-On. If you can find a stock backup (or if you have one yourself ~ you should just sayin....) Yo can restore that and get the OTA.
After the OTA is downloaded, copy it from your phone to your PC (it's in the sdcard/download folder probably) and open it with 7zip.
Find the firmware.zip and unzip it. The recovery.img is in there.
Place the .img into your fastboot folder.
Hook up you phone to your PC and get into fastboot (obviously), and enter fastboot flash recovery recovery.img
Then fastboot reboot and disconnect your phone.
Now that you have the stock ROM and recovery, you should be able to flash the stock OTA.
thanks guys all sorted
had the recovery in slightly wrong folder needed to have device serial as the parent folder.
All back to stock and ticking over nicely
Heisenberg said:
Hi there. I can't really help with your problem, I'm only posting here because I was assigned to move your thread from the general section to the q&a section. I did notice that you included your IMEI number in your post, I've removed it for you, don't ever post your IMEI publicly, or tell anyone what it is. Your IMEI is a unique device identifier, if it falls into the hands of the wrong people they can cause all sorts of problems for you. Anyway, good luck with your problem, just wanted to give you that advice.
Click to expand...
Click to collapse
Removing the serial# would also be a good idea.
xunholyx said:
Removing the serial# would also be a good idea.
Click to expand...
Click to collapse
The serial number isn't really a big issue like the IMEI is, the shady types can't really do anything with that.
Prologue:
So there I was, caressing my shiny and smooth M8.
At the beginning of the year I S-Offed, and added DigitalHigh's awesome Beyond Stock...
Later on, I used a standard RUU GPE Rom.
After repeated Wi-Fi password amnesia, I wanted Beyond Stock Back.
Flashing "GPE_5.1_M8_DH_080215.zip" gives me an "Error 7" even with repeated wipes... hehe... wipes
Searching didn't give me a coherent answer.
So I though, let's update TWRP... and...
Now
The thing's only usable in Bootloader.
If I go to recovery or ANYTHING, the "Google" logo stares at me in disgust.
Odd detail: I'm using fastboot and when it's stuck on the "Google" logo, entering "adb devices" detects the phone in recovery mode.
I flashed TWRP 2.8.7.0, but all I see is the "Google" logo. (I can still feel vibrations on the screen as if I'm hitting a menu button)
I also tried to "fastboot -w" and it gave me the "remote: not allowed" result.
Actually, I tried to fastboot a lot of things and the result came the same.
Anyways, I'll give a detailed log as soon as I remember how, but the reason I post this is 'cause searching for this doesn't give an understandable or reliable result.
Thanks
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s
Give the output of :
Fastboot getvar all
But delete the serial and imei before posting ! If you have an old bootloader you have to use the 2.7 series of TWRP. if you have the latest bootloader (3.18-3.19) you have to use 2.8 series of TWRP !
OOOOOOOOOHHHH, Where I get new M8 bootloader?
Hold Up, going to work, will post 'getvar' later today.
It's there, brah.
Take a look if you can.
It's an AT&T device, you are using it with AT&T ? And you fully converted it from sense to GPE ? You could also :
1: run the GPE ruu again. It will get you on GPE stock again and since you are s-off that should not be a problem of any kind.
2: convert back to sense (original AT&T with software number x.xx.502.x)
i am not sure if the AT&T RUU will cover the "back to sense conversion" so this might be interesting too as it involves the standalone flashing of the firmware first (you need a AT&T firmware, NOT the one posted there !!!)
here is more conversion info :http://forum.xda-developers.com/showthread.php?t=2733523
and here you can get firmwares : http://forum.xda-developers.com/showthread.php?t=2701376
if you want number 2 here is more info with a download link to the latest android L RUU : http://www.theandroidsoul.com/download-att-htc-one-m8-lollipop-ruu-4-28-502-1-75822/
Didnt want to start my own thread due to the shame..
Hi,,
I have managed to remove my OS, without making a backup. All i have running is TWRP. Was going to install CM12.1, but didnt update the M8 to the latest software that contains relevant bootloader. From here it went downhill - fast.
Ended up with no OS, no backkups, and no ability to flash other ROMS i think.
If someone could give me a few ideas, i would really appreciate it.
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Mike
Sheriff1972 said:
Hi,,
I have managed to remove my OS, without making a backup. All i have running is TWRP. Was going to install CM12.1, but didnt update the M8 to the latest software that contains relevant bootloader. From here it went downhill - fast.
Ended up with no OS, no backkups, and no ability to flash other ROMS i think.
If someone could give me a few ideas, i would really appreciate it.
Click to expand...
Click to collapse
Your case is different and you should start your own thread but there are many same case as yours.
Here is one and the solution is in there.. run RUU - http://forum.xda-developers.com/htc-one-m8/help/os-sos-t3192177
Anything you're not sure, ask there. Don't hijack this thread.
UPDATE: Thanks to ckpv5 and the links that were provided i was able to complete the reinstall - thank you so much!!
Opps - sorry - didnt mean to offend!
Will take a look.
Thanks
Mike
The RUU got me an OS and, right now, that is all I need.
Thank you!!
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.