Develop Bugs

[Q] Accidentally flashed a GSM RUU onto my CDMA One M8.

Now rebooting the phone only takes me in to the bootloader. I cannot load into the stock recovery or TWRP, and I error out every time I try and flash an RUU.
I have contacted HTC support and they said to run the .exe version of the RUU for my phone, which gives me error 155 unknown error (I know it has to do with the partitioning).
Is there anything I can do to fix this or is my phone basically bricked/dead.

See if you can find the firmware.zip that corresponds to the RUU for your device. If so, then flash the firmware, then try the RUU again.
I'm not sure if this will work in this specific case. But its how other folks were able to resolve the partition issue going from GPE to Sense (GSM M8).
I assume you have s-off, since otherwise the "incorrect" RUU never would have run in the first place?

redpoint73 said:
See if you can find the firmware.zip that corresponds to the RUU for your device. If so, then flash the firmware, then try the RUU again.
I'm not sure if this will work in this specific case. But its how other folks were able to resolve the partition issue going from GPE to Sense (GSM M8).
I assume you have s-off, since otherwise the "incorrect" RUU never would have run in the first place?
Click to expand...
Click to collapse
Yes, I'm s-off. It was a total accident. Never meant to run it.
I've tried every combination of flashing I can think of.
I have downloaded the firmware and RUU from this thread: http://forum.xda-developers.com/showthread.php?t=2729173 but they did not work.
I can use my old m7 for now but its got a cracked screen
I'm so mad at myself for this.
EDIT: Now I'm looking I notice a combination of stuff on that thread I haven't tried. Guess I'll keep dicking around with it. Not much worse I can do to the thing now anyway.

[Q] Bootloop on GPE converted M8 after update (help!)

I recently tried updating my (previously functional) HTC One M8 I converted to a Google Play Edition phone. I hadn't realized the version of the GPE RUU was rooted, so after using Android's stock updater, the phone is busted. I've been tearing my hair out for the last six hours trying to flash something or get it to work in a way that's acceptable, but I can't seem to get access to it.
I should note that once the RUU was updated to GPE, I didn't bother reinstalling TWRP, so I'm also stuck on a stock recovery.
There are a couple of significant issues beyond the phone just not starting up. When I go into the bootloader, it states that it's missing OP6BDIAG.zip, and that no images were found. It then says a few more things in separate lines so quickly I can't really read them. I think they're either .exe or .zip files.
MTP is not currently working, I can't access the file structure. ADB and Fastboot are giving me errors, saying they can't find the device. I've pushed FACTORY RESET in the bootloader with no difference at all. I've gone into the recovery and wiped data, cache, everything. My NANDroid backups are all of Sense, because I have only converted this phone to GPE a week ago.
I'm not a software developer, I'm not an Android systems expert, and in all honesty when it comes down to it I'm skilled enough to read a manual and know usually what I'm saying when I type in command prompts. I need some help. I've officially spent more time trying to figure out how to fix this than converting the phone in the first place.
Some more info: For those of you who don't know, to do the conversion I've done, my phone is unlocked, has s-off, I've changed the CID to google's, and I changed the RUU to the stock android from a member of this forum's instructions. The bootloader is still HTC, and it is running the HTC GPE RUU, not a Nexus or other RUU.

Update: I got TWRP on my phone! ADB wasn't communicating with my device so I looked up how to do it all through fastboot. It's turned my phone into an MTP device and I can access everything. My NANdroid backups to Sense were deleted when my RUU updated it to a Play Edition phone, so I'm out of luck there, but I assume I can just use TWRP tools to get my phone working again? What's my next step?

DiscoKing said:
Update: I got TWRP on my phone! ADB wasn't communicating with my device so I looked up how to do it all through fastboot. It's turned my phone into an MTP device and I can access everything. My NANdroid backups to Sense were deleted when my RUU updated it to a Play Edition phone, so I'm out of luck there, but I assume I can just use TWRP tools to get my phone working again? What's my next step?
Click to expand...
Click to collapse
No official RUU is pre-rooted, and unfortunately Lollipop has been very rough on root users. It isn't like the old days when it would just blow away your root files and move on.
If you want to run GPE, get the official RUU and try it again. Just keep in mind that OTAs will break if you root it.

That worked, after a few failures. Thank you.

Please help me I have the exact same problem. How did you manage to install TWRP?

Returning to stock issues.

I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!

Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.

I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?

Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.

Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?

Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...

Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.

Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?

Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?

Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!

Full stock Dev Ed M8 won't take OTA or RUU for MM

I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?

fyarf said:
I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?
Click to expand...
Click to collapse
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...

Sneakyghost said:
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...
Click to expand...
Click to collapse
heres my recovery message, just to maybe help troubleshoot it. it mentions userdata being busy (i got an error in the zip ruu flash for userdata, had to flash the ruu zip twice to get an okay), then kidmode missing. not sure what to do besides flash the firmware from http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894

Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.

Sneakyghost said:
Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.
Click to expand...
Click to collapse
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset

fyarf said:
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset
Click to expand...
Click to collapse
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.

Sneakyghost said:
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.
Click to expand...
Click to collapse
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.

fyarf said:
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.
Click to expand...
Click to collapse
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...

Sneakyghost said:
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...
Click to expand...
Click to collapse
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.

fyarf said:
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.
Click to expand...
Click to collapse
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.

Sneakyghost said:
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.
Click to expand...
Click to collapse
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?

Double_a2013 said:
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?
Click to expand...
Click to collapse
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.

Sneakyghost said:
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.
Click to expand...
Click to collapse
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:

Double_a2013 said:
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:
Click to expand...
Click to collapse
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?

fyarf said:
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?
Click to expand...
Click to collapse
I've never had to reconfigure them before, regardless of if I'm using GPE or Sense RUUs. I'll give it another shot, and get back in a more timely manner
Edit: Apn settings seem fine. It's using the Nextgenphone one from ATT
Edit #2:
http://forum.xda-developers.com/att...ming-calls-lte-mode-m8-att-arhd-34-0-t3026710
Found this thread about a similar issue. I guess I'll disable HD Voice (Honestly, its borderline useless anyway) and see if that solves anything

Phone stock in bootloop after flashing custom rom

So I installed ViperOne M9, the latest version, everything went fine, the download didn't fail, but after rebooting the phone just boots to the bootloader. I can access recovery mode, and download mode but I can't do anything else. I'm not sure what went wrong, though I suspect it might have been that my phone wasn't updated to the latest firmware, I thought it was but I think it wasn't. I made a TWRP backup and placed it on my SD Card but it doesn't seem to be reading it since nothing shows up in there.
In summary I switched to ViperOne M9 from stock, my bootloader is unlocked and my phone is rooted. Its S-On, and it seems to be rebooting every so often. Can anyone help me, this is my first time flashing a custom ROM and everything seemed to be going well until this step.

ArgusPMC said:
[...]
ViperOne M9, the latest version
[...]
S-On
[...]
Click to expand...
Click to collapse
You need the Android M firmware for the latest Viper version. Not every SKU got that update already. What's your current firmware version (stated in Download Mode in the line with "OS" at the beginning)?
Edit: Pressing and holding the power button and both volume buttons at the same time (for a certain amount of seconds I always forget - was it something around 30?) should end the bootloop and make your phone return to Bootloader Mode.

My current firmware is 2.10.709.180. I looked into the Backup and RUU collection too, though I wasn't sure about what to do with that. I did see a TWRP backup for version 2.10.709.1, but I'm not sure if that's the same as the firmware version I have, give those two digits at the end with my phone. Otherwise I guess I could use an RUU if I understood correctly, but I got that I should look for a specific one for my phone.
My CID is also HTC__621 if that helps anything. I'm also not sure about S-ON, should I go S-OFF, I know there's an app that does it for $25, and if it is better for custom ROMs then I have no issue paying that.

If I'm not mistaking your firmware version belongs to the first of the two updates that install Android M on the Taiwanese version (SKU 709) of the M9. So you probably only installed the preparing one and not the Android M one itself. Unfortunately no one contributed a backup for that version and I don't have enough time at the moment to create one. Since you're S-ON you can't use any of the RUUs either because S-ON prevents you from downgrading or changing to a different SKU. And there is no RUU for your firmware version which is accessible for free.
I would recommend installing one of the Android L custom roms (e.g. Viper One M9 3.5). After that you have four options:
Wait and hope that someone creates and uploads a backup you could use. (Can be combined with option 2)
Wait for an Android M RUU for your SKU. (There's no guarantee that there ever will be one.)
Get S-OFF via Sunshine so that you could use one of the older RUUs for the SKU 709. (They can be found in my google sheet.)
Use this RUU service.
If I were you I would choose option three since S-OFF makes getting back to stock so much easier and you're independent from others uploading a backup that corresponds to your current firmware since you can use any RUU you want with S-OFF. But don't feel pushed by me to choose option 3 (since that's not my intention). It's completely your choice.

I'll just go S-OFF, seems like the easiest solution. I was going to do it anyway, so I might as well do it now.
EDIT: Thanks, your solution worked out for me, now I've just got to use the RUU I downloaded and with that I can go ahead and get the Android M firmware I need.