Develop Bugs

HTC Desire 300 in boot loop

Hello all,
I have problem with my HTC Desire 300. When phone is turned on it vibrates for a second and screen gets white with green htc letters on it. The screen stays that way for few seconds and phone is turned off and then back on and this loop goes on forever. The only way to stop this is to remove battery. At that point phone is as it was from factory - it was not rooted nor anything else was done on the phone.
I have searched on Internet and found solution to try to do factory reset.
So I pressed volume down and power key and entered menu with option for factory reset. I choose factory reset and thought that everything will be fine but.....everything was as same as on the beginning. Phone vibrates for a second, white screen + green htc letters for few seconds and then turns off and back on again and loop goes forever.
My next try was to choose recovery option from menu, but it ended up the same way.
Then I searched for solution and found this article: http://forum.xda-developers.com/showthread.php?t=2602301
I thought that installing recovery image might help so I followed steps as described. First I had to unlock my phone's bootloader and, at my surprise, I managed to do that. Now my phone's bootloader is in unlocked state. Then I run fastboot and managed to flash recovery.img as described. I powered phone down, up again, choosed Recovery option and phone restarted. Again, short vibration, white screen with green htc letters on it, BUT in upper part of screen is written entering recovery! Unfortunately, it stayed that way for few seconds, then turned off, turned back on and endless loop is here again. But only first time there was written entering recovery in upper part of screen.
Then I tried another option. I found on: https://drive.google.com/folderview...WkFRSjRaMjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
ROM for this phone. I changed name to 0P6AIMG.ZIP, save it to an SD card and choose fastboot option. Now I received error Lack of heap!
I found that problem might be that my bootloader is unlocked so I relocked it again but I receive same error.
Seems to me that each time phone tries to start something (portion of software) but it can't so it turns off and then back on.
Could it be that something else need to be flashed or phone memory itself is bad?
I can use fastboot commands but I can't use adb.
Can you advise me what to do next and what to check.
On above site I found 4 more files:
boot_init.img
boot_stock.img
recovery_stock.fstab
recovery_stock.img
What are those files for and how can I try to use them?
Here is output of fastboot getvar all command:
C:\HTC\ADBFAST\ADBFAST>fastboot getvar al
INFOversion: 0.5
INFOversion-bootloader: 1.18.0002
INFOversion-baseband: 14.11.36Q4.21
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.10.401.4
INFOversion-misc: PVT SHIP S-ON
INFOserialno: SH3BEWL01916
INFOimei: 358280055226720
INFOmeid:
INFOproduct: g3u
INFOplatform: HBOOT-8225
INFOmodelid: 0P6A10000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4100mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-e1c32097
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.044s
Please help as I run out of ideas and knowledge......
Best regards,
Ivo

Now, that does not sound promising...
Looks like hboot is unable to start both of your phones ramdisks (boot.img / recovery.img)
You could try my recovery build but I doubt it will change anything since SPSPawns build should
also boot 'fine'... [into a panic state until the hardware resets itself after ~5 minutes]
If you are unlucky somehow hboot (or radio) got corrupted and the phone is now unable to
boot permanently. Since you are still S-ON this should not be possible unless the
hardware is faulty.
I don't see a lot of options here.
It might have been a better idea if you had tried getting a replacement instead of unlocking it.
But honestly I can understand the need to try and fix it yourself. In any case if you ask htc nicely,
and explain the situation to them, they might still be willing to help.
You could try to find a working recovery and flash it (fastboot flash recovery recovery.img)
You could try extracting the boot.img from the stock odex rom and flash it. (fastboot flash boot boot.img)
You could wait and hope that HTC will release an official RUU for this device. (But if yours is branded this would be pointless)
You could wait for S-OFF and try to flash a working radio or hboot
fyi:
The files you found on the google drive look more like data gathering to me.
boot_init.img (no idea, maybe the first build of a bootable ramdisk)
boot_stock.img (could've been used to grab anything essential for a ramdisk)
recovery_stock.fstab (the mount point layout of the stock recovery)
recovery_stock.img (could've been used to grab anything essential for a recovery)
Also, adb only works once adbd gets started. (during boot of system or recovery)

Thank you for your answer.
Is there any way to check hardware or parts of hardware of phone with fastboot or some other tool. If it is hardware failure then nothing can be done Can I check that somehow?
However, if it is software problem, then I would like very much to go on
You have suggested to try to find a working recovery and flash it. I have one working Desire 300 bought at same time in same shop with same mobile provider. Can it be used for necessary files (images) or whole phone ROM - can I take files from that phone?
I can try to flash your recovery image, but as you sad, I successfully flashed SPaWn's recovery. During flashing process on phone screen was visible small vertical green progress bar for loading and then red progress bar for writing and double OK confirmation on prompt window. Is this indication that phone RAM and other hardware is good after all?
I can extract boot.img from the stock odex rom (downloaded from link in my previous post) and flash it to see if regular boot is ok.
If hboot or radio is corrupted, can I use file(s) from working phone to fix? Before that should I try to put it in S-OFF? I saw few pages where this procedure is described. Should working phone also be in S-OFF for getting these file(s)?
What do you suggest to do first?
You sad:
"It might have been a better idea if you had tried getting a replacement instead of unlocking it.
But honestly I can understand the need to try and fix it yourself. In any case if you ask htc nicely,
and explain the situation to them, they might still be willing to help."
Unfortunately, phone is out of warranty and this was not an option since screen is a bit cracked (but it worked for months that way). I repair electronics for years and I am glad that you understand my need to try to fix it myself
Than you very much in advance,
Ivo

I don't know of a way to use fastboot for hw diagnostics, sorry.
I've never seen a progressbar while flashing via fastboot, then again I'm only checking
the output of fastboot. (written x kb in y seconds etc)
But I never had to confirm anything while doing so. Are you sure you did everything correctly?
You mentioned 0P6AIMG.ZIP in your first post. This is not the right way to flash a custom boot or recovery!
You need to use fastboot for this to actually work.
web: grab my recovery and extract it to get recvovery.img
phone: Boot to hboot and select fastboot don't forget to connect USB
pc: in bash or dos prompt > fastboot flash recovery recovery.img
pc: check if everything went ok
phone: select bootloader and then start recovery
fingers: crossed
And yes, your secondary device could be very helpful in order to restore the primary BUT
there is no way to switch this phone S-OFF, at least none that I know of, so you won't have the permissions to modify hboot or radio.
Still it's an excellent source to get system data and boot.
I've never tried restoring a cwm backup of one device on another of the same model, but as long as the partitioning
is the same I can think of no reason (except a cwm sanity check) why this shouldn't work.
You could also use dd if cwm fails but let's try the uncomplicated way first

Hello,
I tried with your file, but crossed fingers didn't help...endless loop is here again, first time with entering recovery written.
About confirmation during flashing, I thought on this confirmation (this is taken with your recovery.img file):
C:\HTC\fastboot-win>fastboot flash recovery recovery.img
sending 'recovery' (6484 KB)...
OKAY [ 1.214s] <----this confirmation
writing 'recovery'...
OKAY [ 2.321s] <----this confirmation
finished. total time: 3.537s
Sure I didn't need to click on anything to confirm. Sorry for my unclear explanation at previous post
About 0P6AIMG.ZIP in my first post - I saw procedure for upgrading here: forum.gsmhosting.com, guide-how-upgrade-your-htc-android-phone-microsd-card (I am not allowed to put external link yet)
In step 2 there is explanation for renaming upgrade file to model number + inf. I found that when SD card is inserted, during fastboot I see on screen following:
SD Checking...
No gift file...
Loading...[0P6ADIAG.zip]
No image!
Loading...[0P6ADIAG.nbh]
No image or wrong image!
Loading...[0P6AIMG.zip]
Loading...[0P6AIMG.nbh]
No image or wrong image!
So I thought that phone expect any of these files for booting. This is why I renamed original ROM that I found and put it on SD card and try to boot. Then I got 'Lack of heap' error.
One more try that you have suggested is to try extracting the boot.img from the stock odex rom and flash it. (fastboot flash boot boot.img). Is this image from zip file which I found on link from my first post, or should boot.img file be taken from working phone (if yes, how to do that)? Zip file name 'HTC_Desire_300(Zara mini)_stock_odex_1.10.401.4_root_updated_v.1.0.1.zip' indicates root updated and my phone is/was not rooted.
You sad:
"And yes, your secondary device could be very helpful in order to restore the primary BUT
there is no way to switch this phone S-OFF, at least none that I know of, so you won't have the permissions to modify hboot or radio.
Still it's an excellent source to get system data and boot."
Can you please tell me how to get needed files from working phone and which files? I assume that I should use commands in ADB tool?
Thank you for your time that you are spending for my problem
Ivo

For now focus on getting the phone to boot again. So far the recovery partition seems to be broken.
Next try flashing the recovery image on the boot partition (flash boot recovery.img) to check if you can boot from there.
If it works you can continue by replacing it with the boot.img from your other device.
If you can't get recovery to boot from either the boot or recovery partition, you can consider this phone a brick.
At least until S-OFF is available so you can try replacing hboot and radio.
To get the boot image from the the other device you will have to install a recovery.
Afterwards you can just make a backup and you'll find the boot.img in the backup folder
You could also grab any files you want from system or data by renaming *.tar.a to *.tar and extracting it with 7z
Alternativly dd can be used from an android terminal to backup any partition to an img file on the sdcard, (requires superuser)
It is true that the files hboot lists while starting are used to start diagnostics and updates depending on the zip file
but I'm pretty sure it requires the contents to be signed by htc in order to work.

I tried to flash boot.img extracted from the stock odex rom (fastboot flash boot boot.img), but endless loop is still present. So obviously phone can't continue in any direction after first initialization.
Since currently there is no way for S-OFF, is there anything else to try or we came at stop point?

Technically it's over. But just to be completly sure try to flash the recovery.img as boot.
We can't be certain that your system partition might be corrupted aswell unless we try a 100% working ramdisk.
if recovery can't start from either the boot or recovery partition you'll have to wait for S-OFF or just use the device for spare parts.
If it actually boots you can still use it to restore your device but remember if you restore a backup or flash a new rom you will
permanently loose recovery until you reflash it to boot again, sacrificing your system in the process.
Still, good luck for your final attempt and my condolences if this last resort also ends as a failure.

I will try that, just tell me can I run 'fastboot flash boot recovery.img' (with your recovery image or SPaWn recovery image) or should I rename recovery.img to boot.img and then run 'fastboot flash boot boot.img'
What I mean does file name during flashing matter or only content of file is important?

the filename is completely irrelevant. The important part is that it is smaller or equal to the partition size of boot.
Since both boot and recovery are roughly 16MB, everything should be fine. Well in your case probably not...
but you know what I mean.
btw:
After a little pondering my guess would be a broken RAM.
For one it is unlikely that your device managed to kill radio (which wouldn't matter for recovery)
or that hboot got damaged, since it would usually end in it not booting whatsoever.
Furthermore it is highly unlikely that two partitions of your internal emmc broke at the same time.
And since ramdisks (like boot and recovery) get loaded into RAM in order to work. (hence the name)
I'd guess, with a rather high certainty, that somehow your RAM got damaged and now your device is toast.
For your sake, I hope I'm completely wrong. :angel:

I have tried, but with same results......
I think that we can conclude that I indeed have hardware failure (most probably) with access to RAM.
What else can I say except thank you so much for time spent and for advices that you gave me.
My next step will be to disassemble the phone and see if there are any obvious cracks on printed circuit board, although I think that chances to repair this are close to nothing since this is double or multiple layer board packed with SMD components.......
I will certainly let you know if I make any progress!
Once again, thank you very much for all. If you come to Zagreb, we can always go for a beer
Best regards,
Ivo

EXTRA! EXTRA! Read all about it...!
It works!!!!!!!!!!! Yes, it works again!!!!!!!!!!!!!!!
A friend of mine has friend who works in repair shop and, as she heard sad story about phone, told me to bring it to see if anything could be done. So I left phone at shop and tomorrow she called me and told me that it works! She explained me that her colleagues put new software and after 40 minutes phone was working!!!
So, after all, it was not hardware failure. It could be that part of software which is protected with s-on was corrupted. However, it works again!!!
I just wanted to share news with you

Glad to hear you got it booting again.
enjoy the working wifi on the stock rom.

i have same problem plz help me...

Friend bricked HTC One

So, long story short, a kid who got himself a HTC one M8 thought he'd be smart and try to install the Google Play Edition of the Lollipop Update. Turns out he managed to brick the device, sort of. He came to me for help, and I was able to find out what he did so far.
1. He unlocked the bootloader using fastboot.
2. Installed CWM PhilZ
3. Downloaded the Google Play Edition of the Lollipop Update.
4. Failed to take a backup of his current ROM.
5. Installation failed of the new ROM because S was on.
6. He has said (can't make out if this is true or not) that he has reverted to stock recovery, so as to *help* me with fixing it. The screen that I am able to get into after I press the volume button and power combinations says the following.
***TAMPERED***
***UNLOCKED***
MB_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.1921331147A1.16G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 12 2014, 23:27:55.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
*****************************************************************************
I've got my ADT and the necessary tools to proceed. I just need to be pointed in the right direction with this. Selecting Recovery takes me to a screen with a Hazard "!" sign screen, after which I have to reboot the phone. Factory Reset also doesn't work with it showing the update/download arrow after which it comes back to the HTC logo powered by Android, as it always does. When connected to the computer, the computer reads it as a CD drive. Note that I don't have the drivers installed for the phone on this computer seeing as this is not my phone. I've got the stock ROM from the HTC dev site ready. Would appreciate the help. Thanks!

I'm thinking you should download latest ruu image from xda forums for the M8, get to fastboot usb, and flash that to get back to usable. Then s-off with firewater / whatever s-off tool is currently out there. Or, I could be misunderstanding your problem.

KinTharEl said:
So, long story short, a kid who got himself a HTC one M8 thought he'd be smart and try to install the Google Play Edition of the Lollipop Update. Turns out he managed to brick the device, sort of. He came to me for help, and I was able to find out what he did so far.
1. He unlocked the bootloader using fastboot.
2. Installed CWM PhilZ
3. Downloaded the Google Play Edition of the Lollipop Update.
4. Failed to take a backup of his current ROM.
5. Installation failed of the new ROM because S was on.
6. He has said (can't make out if this is true or not) that he has reverted to stock recovery, so as to *help* me with fixing it. The screen that I am able to get into after I press the volume button and power combinations says the following.
***TAMPERED***
***UNLOCKED***
MB_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.1921331147A1.16G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 12 2014, 23:27:55.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
*****************************************************************************
I've got my ADT and the necessary tools to proceed. I just need to be pointed in the right direction with this. Selecting Recovery takes me to a screen with a Hazard "!" sign screen, after which I have to reboot the phone. Factory Reset also doesn't work with it showing the update/download arrow after which it comes back to the HTC logo powered by Android, as it always does. When connected to the computer, the computer reads it as a CD drive. Note that I don't have the drivers installed for the phone on this computer seeing as this is not my phone. I've got the stock ROM from the HTC dev site ready. Would appreciate the help. Thanks!
Click to expand...
Click to collapse
First get HTC Sync on your PC, install the drivers, then uninstall HTC Sync.
Download TWRP from their site. I recommend 2.0.8.3, it has less issues than the newest 2.1.0.0.
Rename it to recovery.img and put it into the fastboot folder on your PC.
Enter fastboot on the phone (while the phone is off, hold power + vol. down)
Plug it in to your PC and start ADB and enter this command:
fastboot flash recovery recovery.img
Make sure that Superuser is installed, (it should be already if he was flashing custom ROMs)
After that you can flash a ROM using ADB, or by putting the ROM onto ext SD and flashing using TWRP.

Update. I was able to get TWRP installed and flash SuperSU. Still have S off and I have no idea how to get that done. I tried using the toolkit by Squabbi and unfortunately wasn't able to get the S off. Any ideas?

KinTharEl said:
Update. I was able to get TWRP installed and flash SuperSU. Still have S off and I have no idea how to get that done. I tried using the toolkit by Squabbi and unfortunately wasn't able to get the S off. Any ideas?
Click to expand...
Click to collapse
You mean S-ON? You could try firewater but that's a shoot and miss in which case it'll have to be Sunshine S-OFF(Only alternative) and that costs $25.
Back to troubleshooting:
Boot into recovery mode and sideload a ROM from the PC. You can also do an adb push ROM.zip /storage/ext_sd/ or if you have a SD Card reader on PC, remove the SD card, put it in PC and manually copy/move a ROM to the SD Card.
You don't need S-OFF to flash custom Recoveries. You'll need it in order to do a full conversion to Google Play Edition though, as a result of partition sizes changing. ROMs on the other hand is fine with S-ON.
Of course if you're going to flash custom ROMs make sure it's for the correct firmware that you're currently using. You're device still uses 2.xx.xxx.x firmware so don't download a 3.xx.xxx.x custom ROM for it. This is the case with Sense based ROMs, not sure about AOSP(Apparently it's not an issue with it). Outdated firmware will have the radio not work properly, which means, possibly, no bluetooth, gps, wifi, data.

Sorry. S-ON, that's what I meant. Yep, as you said, I was able to flash a custom recovery just fine with the S-ON. Was also able to flash SuperSU for it. After this, I was able to access the internal memory of the phone. It showed only one folder on my PC, the TWRP folder. But in the recovery, I'm able to see the root directories, which I can't on the PC. Tried flashing the stock ROM from the HTC dev site by pasting it into the phone, which sadly failed. I'll check again for the 2.xx ROMs. Maybe that's the miss I did.

KinTharEl said:
Sorry. S-ON, that's what I meant. Yep, as you said, I was able to flash a custom recovery just fine with the S-ON. Was also able to flash SuperSU for it. After this, I was able to access the internal memory of the phone. It showed only one folder on my PC, the TWRP folder. But in the recovery, I'm able to see the root directories, which I can't on the PC. Tried flashing the stock ROM from the HTC dev site by pasting it into the phone, which sadly failed. I'll check again for the 2.xx ROMs. Maybe that's the miss I did.
Click to expand...
Click to collapse
Don't bother with HTCDev site, those are kernel source codes and not backups.
COLLECTION of Stock backup's <<There's the nandroid backups for plenty of devices just look for the right one in post 1. Also in post 2 the author showed how to do the restore, make sure it's unpacked and placed in the correct path directory.

Update so far.
S-On
TWRP flashed.
Tried all the methods that you guys have mentioned.
Nandroid backup is failing.
When I use an OTG Flash drive to flash SuperSU, it succeeds, but when I hit the option to reboot, TWRP says that SuperSU isn't installed on the device and gives me an option to install it, which fails.
Tried a ROM from CM, which also failed.
Tried a sideload with adb, which also failed.
Haven't been able to use firewater to turn S-Off, where the push command just hangs.
Therefore, I am stumped at the moment. I've been thinking of using RUU to restore the phone to stock, but I haven't been able to find anything worthwhile. Is this a valid idea that I can use? Anyone has any links to this that I can use? Help would be appreciated. Thanks.

In looking for a solution to your problem, everything I have found so far requires S-OFF. I myself used the weaksauce/firewater method to do mine, did that not work for you? And if not, I have to ask if you followed the directions verbatim?
There is also the sunshine method - have you tried that method to S-OFF the phone?
This is gonna require someone to pay 25 bucks, but 1) it is well worth it, at least at this point in your efforts, 2) you don't have to pay until the S-OFF is successful, and 3) your friend should be footing that bill anyway.
Once you've gotten S-OFF achieved, you are one step - prolly the biggest step - closer to getting this thing done.
Look at it this way - after all of your troubles and frustration, wouldn't $25 be small beans to pay for a working phone?

sigshane said:
In looking for a solution to your problem, everything I have found so far requires S-OFF. I myself used the weaksauce/firewater method to do mine, did that not work for you? And if not, I have to ask if you followed the directions verbatim?
There is also the sunshine method - have you tried that method to S-OFF the phone?
This is gonna require someone to pay 25 bucks, but 1) it is well worth it, at least at this point in your efforts, 2) you don't have to pay until the S-OFF is successful, and 3) your friend should be footing that bill anyway.
Once you've gotten S-OFF achieved, you are one step - prolly the biggest step - closer to getting this thing done.
Look at it this way - after all of your troubles and frustration, wouldn't $25 be small beans to pay for a working phone?
Click to expand...
Click to collapse
S off can only be done with a working phone, eg stock sense rom, S-off is not your problem, installing a rom is, get something like ADHD rom, or the correct stock rom for your CID and then flash that. Job done working phone, then s-off if you wish but its not a requirement, but nice to have and well worth $25

Yeah. I've been searching and came to the same result, that I need the S-off. But all the methods that I have seen require that the phone needs to have a working ROM to turn S off. I'd have been able to use weaksauce/firewater for it. I saw a video of a bricked M8, and he seemed to restore it back to total stock using RUU. I'm currently downloading the RUU for the Google Play Edition, seeing as I can't find the RUU for the Sense UI WWE. In the same video, he has S-ON, from what I saw in the bootloader. Wondering if this method could possibly work. Any ideas? Here's the link for that video. The phone is a Sprint M8, but the same logic should apply for the WWE, if I'm not mistaken. Link to Video
The problem with asking the friend (he's a kid friend of my brother), is that he can't foot the bill.

KinTharEl said:
Yeah. I've been searching and came to the same result, that I need the S-off. But all the methods that I have seen require that the phone needs to have a working ROM to turn S off. I'd have been able to use weaksauce/firewater for it. I saw a video of a bricked M8, and he seemed to restore it back to total stock using RUU. I'm currently downloading the RUU for the Google Play Edition, seeing as I can't find the RUU for the Sense UI WWE. In the same video, he has S-ON, from what I saw in the bootloader. Wondering if this method could possibly work. Any ideas? Here's the link for that video. The phone is a Sprint M8, but the same logic should apply for the WWE, if I'm not mistaken. Link to Video
Click to expand...
Click to collapse
Not going to work. In the video, he is flashing the RUU which corresponds to his phone's CID.
You need to have the GPE CID to use the GPE RUU. Otherwise it will fail CID check and fail to install. And you can't change CID with s-on.
And unfortunately, there are no WWE RUUs.
I would try fastboot erase cache and install TWRP again. Then flash a ROM corresponding to your firmware (Sense 2.x). ROMs simply failing to flash is often just a matter of erasing cache and re-installing recovery.

redpoint73 said:
Not going to work. In the video, he is flashing the RUU which corresponds to his phone's CID.
You need to have the GPE CID to use the GPE RUU. Otherwise it will fail CID check and fail to install. And you can't change CID with s-on.
And unfortunately, there are no WWE RUUs.
I would try fastboot erase cache and install TWRP again. Then flash a ROM corresponding to your firmware (Sense 2.x). ROMs simply failing to flash is often just a matter of erasing cache and re-installing recovery.
Click to expand...
Click to collapse
I see. Thanks for the clarification. I didn't try flashing it yet seeing as I wanted to know what I was getting into before I actually did anything. Just for the sake of giving information, the RUU I downloaded is 2.12.1700. Version of Android is 4.4.4. Guessing it probably won't work, but I'll reflash the recovery as you had suggested. I'll try Android Revolution 22.1 for this, hopefully it works. I'll keep you guys posted.

I don't see any info of your device except the hboot version.
With that hboot version 3.18.0.0000 all the latest custom ROM won't properly work on your device.
Why don't you give more detail - run command fastboot getvar all and post here the result (delete the serialno. and imei no.)
From there we can see whether any stock backup for you. Most important now is to have a fully working phone .. then you can start any other thing like S-Off and flashing custom ROM

(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTXXXXXXXXXX
(bootloader) imei: 3XXXXXXXXXXXX
(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
Update: I've checked through the logs that TWRP shows, and I've found that when trying to sideload, or flash SuperSU(Even when it says successful), cache won't mount. I tried manually mounting it through the option in TWRP, but it won't select the cache at all. I also can't copy anything onto the phone memory. My option to try anything just with the phone so far has been to use an OTG USB Drive and mount that.

KinTharEl said:
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-main:
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
Click to expand...
Click to collapse
1. Empty version-main : The TWRP that you have is a very old version.
Use TWRP 2.8.1.0 link in my signature.
2. HTC__038 and hboot 3.18.0.0000 - your correct software/ROM version no. is 2.10.720.1
There's a nandroid backup for this version here : http://forum.xda-developers.com/showthread.php?t=2701376
So try TWRP 2.8.1.0. Try also to enable MTP and see whether the sdcard/internal storage mountable to your PC.
Download the 2.10.720.1 nandroid backup then use the OTG to restore. You can make a backup of boot and select USB as the storage for the backup, you'll see the folder structure in your OTG drive. There is where you need to transfer the nandroid backup (after you extract it on PC)
Note :
1.If this is successful then you can try to S-Off with Sunshine but it is a hit or miss for your device version ... most likely won't work
2. You can follow the right procedure to do OTA update to 3.35.720.1 then you can flash any of the latest custom Sense based ROM and the lollipop ROM too.
3. Just be on stock then wait for OTA for the official lollipop like most of us here.

KinTharEl said:
Just for the sake of giving information, the RUU I downloaded is 2.12.1700. Version of Android is 4.4.4. Guessing it probably won't work
Click to expand...
Click to collapse
If its a GPE RUU, and you don't have the GPE CID (or SuperCID), it won't work. I already said that, so I don't know why you are still "guessing" anything.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
KinTharEl said:
Update: I've checked through the logs that TWRP shows, and I've found that when trying to sideload, or flash SuperSU(Even when it says successful), cache won't mount. I tried manually mounting it through the option in TWRP, but it won't select the cache at all. I also can't copy anything onto the phone memory. My option to try anything just with the phone so far has been to use an OTG USB Drive and mount that.
Click to expand...
Click to collapse
No version number means obsolete TWRP (as ckpv5 mentioned). Flashing a more current TWRP will fix this, and will probably also fix the flashing issues you had with various ROMs, and might fix the mount cache issue.

redpoint73 said:
If its a GPE RUU, and you don't have the GPE CID (or SuperCID), it won't work. I already said that, so I don't know why you are still "guessing" anything.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
No version number means obsolete TWRP (as ckpv5 mentioned). Flashing a more current TWRP will fix this, and will probably also fix the flashing issues you had with various ROMs, and might fix the mount cache issue.
Click to expand...
Click to collapse
Got it. I'll try it out as soon as I'm done with work. I was out of town the past few days, so I wasn't really able to reply. Thanks for the advice though. I'll definitely look into it.

New M9 --- Bootloop/stuck after mods

Got a new M9 yesterday. Coming from a M8 where I went through several flashing sessions of firmware versions (upgrades) and a couple different ROMs (Viper, LeeDroid, GPE) over the past 1.5 years, no major issues.
With the new M9, I went through the following steps:
Unlocked the bootloader.
Used Sunshine for S-OFF.
Installed TWRP v2.8.7.8-hima.img
Did a backup.
Rebooted fine, loads original OS no issues.
Onto.....
Changing CID to 11111111
Flashed M9_2.8.617.4_NoWipe_NoRed (Developers/Unlocked firmware)
Flashed LeeDroid One M9 - V7.7.0 RC2
And this is where I ran into problems.....let the M9 sit and boot, it booted HTC logo screen, LeeDroid Logo screen, and then the updating apps screen, and finished......but it never booted correctly again. Waited 15 minutes, 30 minutes, an hour....nothing. I could always boot back to bootloader screen. It'd never boot LeeDroid. Eventually, I tried going back to recovery mode....and it went into the HTC recovery screen (not the TWRP recovery).
So....I went to download mode, and flashed the original 2.8.617.4 RUU from SneakyGhost (which has the red text warning)......and then did a factory reset......and it has started back to trying to boot LeeDroid, but it bootlooped to where the M9 will give the HTC logo screen, the LeeDroid logo screen, start and finish the updating apps screen.....will flash off the screen, then repeats the LeeDroid logo, and updating apps again...
I then put the TWRP recovery back (as it would only go to the HTC recovery). And then I flashed LeeDroid V7.7.0 RC2 again and waited.....now the M9 will power on....show me the HTC logo screen, then show nothing, but you can see the screen backlight on, then the screen backlight goes off.....and it reboots. A couple times....it's shown me the status bar (but only the right side info), with nothing else at all showing on the screen.
I just never seem to be able to get it to boot the OS completely to show me a screen after flashing....but all the TWRP and Bootloader stuff works....
Current Fastboot 'getvar all' info:
kernel: lk
product: htc_himaulatt
version: 1.0
imei: -----
version-main: 2.8.617.4
boot-mode: download
version-baseband: 01.01_U11440601_76.03.50611G_F
version-bootloader: 1.0.0.0000
mid: 0PJA11000
cid: 11111111
On the HTC download mode screen:
****Unlocked*****
htc_himaulatt PVT S-OFF
CID 11111111
LK-1.0.0.0000
Radio 01.01_U11440601_76.03.5611G_F
OpenDSP-v29.2.6.00492-M8994_0514
OS-2.8.617.4
June 26 2015, 13:47:21 (559710)
What am I missing/doing wrong?
Any ideas and help sincerely appreciated!

You might want to try to: (According to clsA Guide)
1) Change CID to BS_US001 (Since this is the CID included in the Dev edition RUU)
2) Download this version of Dev edition(2.8.617.4 RUU)
3) Rename file to 0PJAIMG.ZIP
4) Place file in external SD Card
5) Go to download mode and it will detect and install.
Hope this helps.
Credits to clsA

sttw1fa said:
Got a new M9 yesterday. Coming from a M8 where I went through several flashing sessions of firmware versions (upgrades) and a couple different ROMs (Viper, LeeDroid, GPE) over the past 1.5 years, no major issues.
With the new M9, I went through the following steps:
Unlocked the bootloader.
Used Sunshine for S-OFF.
Installed TWRP v2.8.7.8-hima.img
Did a backup.
Rebooted fine, loads original OS no issues.
Onto.....
Changing CID to 11111111
Flashed M9_2.8.617.4_NoWipe_NoRed (Developers/Unlocked firmware)
Flashed LeeDroid One M9 - V7.7.0 RC2
And this is where I ran into problems.....let the M9 sit and boot, it booted HTC logo screen, LeeDroid Logo screen, and then the updating apps screen, and finished......but it never booted correctly again. Waited 15 minutes, 30 minutes, an hour....nothing. I could always boot back to bootloader screen. It'd never boot LeeDroid. Eventually, I tried going back to recovery mode....and it went into the HTC recovery screen (not the TWRP recovery).
So....I went to download mode, and flashed the original 2.8.617.4 RUU from SneakyGhost (which has the red text warning)......and then did a factory reset......and it has started back to trying to boot LeeDroid, but it bootlooped to where the M9 will give the HTC logo screen, the LeeDroid logo screen, start and finish the updating apps screen.....will flash off the screen, then repeats the LeeDroid logo, and updating apps again...
I then put the TWRP recovery back (as it would only go to the HTC recovery). And then I flashed LeeDroid V7.7.0 RC2 again and waited.....now the M9 will power on....show me the HTC logo screen, then show nothing, but you can see the screen backlight on, then the screen backlight goes off.....and it reboots. A couple times....it's shown me the status bar (but only the right side info), with nothing else at all showing on the screen.
I just never seem to be able to get it to boot the OS completely to show me a screen after flashing....but all the TWRP and Bootloader stuff works....
Current Fastboot 'getvar all' info:
kernel: lk
product: htc_himaulatt
version: 1.0
imei: -----
version-main: 2.8.617.4
boot-mode: download
version-baseband: 01.01_U11440601_76.03.50611G_F
version-bootloader: 1.0.0.0000
mid: 0PJA11000
cid: 11111111
On the HTC download mode screen:
****Unlocked*****
htc_himaulatt PVT S-OFF
CID 11111111
LK-1.0.0.0000
Radio 01.01_U11440601_76.03.5611G_F
OpenDSP-v29.2.6.00492-M8994_0514
OS-2.8.617.4
June 26 2015, 13:47:21 (559710)
What am I missing/doing wrong?
Any ideas and help sincerely appreciated!
Click to expand...
Click to collapse
xunus said:
You might want to try to: (According to clsA Guide)
1) Change CID to BS_US001 (Since this is the CID included in the Dev edition RUU)
2) Download this version of Dev edition(2.8.617.4 RUU)
3) Rename file to 0PJAIMG.ZIP
4) Place file in external SD Card
5) Go to download mode and it will detect and install.
Hope this helps.
Credits to clsA
Click to expand...
Click to collapse
The above will defiantly get your phone back to stock and working. (make sure your SDCARD is Formatted FAT32)
I'm not sure where you went wrong with LeeDroid all versions have worked fine on my DE firmware and phone. I can tell you the first boot after the LeeDroid install will take almost 30 min, did you wait long enough ?
I also only use twrp-2.8.7.1_CPTB-B1-hima.img
And try the LeeDroid R15 here >> http://www.leedroid.co.uk/

Thank you both for the replies and help.
Yes, I've not ever run into any major issues with firmware and ROM flashing up til this.
Now....something seems to have happened to my Sandisk 64gb micro SD card. The M9 won't mount it during boot. So....I backed it up, then tried reformatting in my M8. But it re-mounts with all the data/folders still showing. Tried formatting on my Mac (disk utility).....it errors out during the erase/partition stage. So....I tried it on my Windows 7 PC....same thing. But...it mounts on my PC, Mac, and M8 showing all the original files/directories.... FWIW.....I did check the 'lock switch' on the micro SD adapter, it was in the unlocked position.
UGH....
I'll have to wait until some stores open to see if I can get a new micro SD card go further....
Will report back....thanks again!

Oh....on the LeeDroid first boot. Yes, I waited....each time I was able to go through the TWRP install of Leedroid (everything normal and finished), it was over an hour before forcing the reboot (vol/power button combo). It would reboot HTC logo, LeeDroid logo, then screen would go blank....and then it appears as if the display drivers were hosed. It would then (after LD logo) show a blank screen (but backlit), then the backlight would go off. A couple times, it'd show me the status bar right side upon pressing the power button. The M9 would show battery levels, wifi icon, cell icon, but nothing else at all on the screen. Holding power off, would show the normal reboot sequence....
Had been running the the processes almost 5 hours before the OP, when I was out of ideas to work with.

sttw1fa said:
Oh....on the LeeDroid first boot. Yes, I waited....each time I was able to go through the TWRP install of Leedroid (everything normal and finished), it was over an hour before forcing the reboot (vol/power button combo). It would reboot HTC logo, LeeDroid logo, then screen would go blank....and then it appears as if the display drivers were hosed. It would then (after LD logo) show a blank screen (but backlit), then the backlight would go off. A couple times, it'd show me the status bar right side upon pressing the power button. The M9 would show battery levels, wifi icon, cell icon, but nothing else at all on the screen. Holding power off, would show the normal reboot sequence....
Had been running the the processes almost 5 hours before the OP, when I was out of ideas to work with.
Click to expand...
Click to collapse
An old 8 - 16 or 32GB SDCARD work best
you can also use the RUU.exe from HTC themselves
http://www.htc.com/us/support/htc-one-m9/news/

Quick update....still waiting on the micro SD card (come on Sunday Amazon delivery...haha).
But, I've been able to run the HTC RUU program on my Windows 7 laptop, and can now boot the M9 like it's a new phone again. Yay. THANK YOU!
Booting recovery goes into the HTC recovery, and not TWRP. I'll have to start over.....flash twrp, backup, flash a ROM, reboot, etc.
fastboot getvar all shows all the same info, save for the CID change to BS_US001.
So....I've kind of leaned towards LeeDroid the past 5 months, but before that was running Viper. Both with minimal (if any noticed) issues.
Should I retry with LeeDroid or ???

sttw1fa said:
Quick update....still waiting on the micro SD card (come on Sunday Amazon delivery...haha).
But, I've been able to run the HTC RUU program on my Windows 7 laptop, and can now boot the M9 like it's a new phone again. Yay. THANK YOU!
Booting recovery goes into the HTC recovery, and not TWRP. I'll have to start over.....flash twrp, backup, flash a ROM, reboot, etc.
fastboot getvar all shows all the same info, save for the CID change to BS_US001.
So....I've kind of leaned towards LeeDroid the past 5 months, but before that was running Viper. Both with minimal (if any noticed) issues.
Should I retry with LeeDroid or ???
Click to expand...
Click to collapse
Sure I've been using R15 for a couple weeks. It's great
Sent from my HTC One M9 using Tapatalk

Another update....my M9 is now LeeDroid'd on R15.....THANK YOU for the help. Now onto the UI setup I like to tweak.

LeeDroid stuck on M9
This thread is old, but it's the closest thing to my problem. I unlocked my M9 with sunshine, got s-off, installed TWRP. I tried VIPER a while ago, but had overheating problems and went back to stock. Verizon is bugging me about updating the stock OS, which fails. I thought I'd try LeeDroid. Intallation seemed to go ok, but on first boot after an hour all I have is the LeeDroid startup screen. Nothing happens with power + vol dwn. Power plus vol up goes to white screen HTC boot and then the same stalled LeeDroid screen. I can't seem to get back to TWRP. Someone above mentioned "download mode"? At this point I'd be happy to get back to stock if someone could explain how to do it. Is there some way I can control it through my pc? Thanks.
Update: In case someone needs this info, I tried a last ditch idea. I let the phone go dead, completely run down the battery. Then I booted to recovery and installed the backup. Back on stock. Whew! I still have the problem of Verizon trying to force an update every day which fails.

Stuck - can't get pass the htc logo screen

Hello guys,
I'm newbie here. I'm not a tech guy, to be honest. My problem is that I'm stuck on the HTC Logo Screen. My phone is HTC One M8 Eye.
So this morning, I was trying to root my phone. I unlocked my phone already ( now my phone said "Software Status: Modified" and "***Unlocked***" ). Everything was good until I was installing SuperSU.zip file. It didn't work. So I tried to search for a newer version of SuperSU, I think it's 2.56 or 2.76. I copied that to my phone, trying to install via TWRP 2.7.0.2. Everything was good, I though. It said "successful" and "all done". But when it rebooted, it got stuck on HTC Logo Screen.
I tried to turn it back on and off by holding the lock botton, volume up and volume botton at the same time. Then I tried to force it to go into the fastboot mode ( I don't know what to do call that ) where it showed me some options like fastboot, hboot, recovery and stuffs...I'm freaked out from this point and tried to relock my phone via the toolkit by Hasoon. Then I also returned my phone to S-on.
Now the problem is that I can get into the recovery screen with options like fastboot, hboot, but I don't have access to my internal storage anymore. And I'm stuck with HTC Logo Screen. The closest time was that it said "HTC One tm" but not "HTC". Then nothing happens next.
I'm pretty sure I messed up...A LOT.
Please, if anyone knows how to solve this, help me? I'm like, here, begging you since this phone is really important to me.
Thank you in advance.

1. Your main mistake is using an outdated tool
2. Bigger mistake you used tool meant for M8 not M8 eye (they are different device)
3. Biggest mistake you used an outdated TWRP and not meant to be used on M8 eye.
You can try :
1. Install correct TWRP for M8 eye - http://forum.xda-developers.com/showpost.php?p=62030698&postcount=144
2. Install SuperSU 2.76
and see your device will boot or not.
If not, you need to restore nandroid backup or RUU

khanhnn said:
I'm freaked out from this point and tried to relock my phone via the toolkit by Hasoon. Then I also returned my phone to S-on.
And I'm stuck with HTC Logo Screen. The closest time was that it said "HTC One tm" but not "HTC". Then nothing happens next.
Click to expand...
Click to collapse
This is exactly what is supposed to happen when you relock the bootloader, it renders the phone unable to boot into OS. This should never be done, unless you are going to flash an RUU.
Along with the other mistakes already pointed out, it seems you are trying things without properly understanding what the result will be, and without researching properly beforehand.
Also, you say you went back to s-on, but were you ever actually s-off? The only working s-off method is sunshine, which requires root. Therefore, I don't see how the phone could have been s-off (unless you received it that way) and it doesn't actually make sense when you say you returned to s-off.
---------- Post added at 10:21 AM ---------- Previous post was at 10:19 AM ----------
khanhnn said:
Then I tried to force it to go into the fastboot mode ( I don't know what to do call that ) where it showed me some options like fastboot, hboot, recovery and stuffs...I'm freaked out from this point
Click to expand...
Click to collapse
That is called the bootloader screen. You were trying to get into fastboot mode, and you got the bootloader screen, which then allow you to select fastboot (use vol keys to move between options, power button to confirm, if fastboot is not already selected) so I don't see what the issue is here?

Hello,
Thank you for your reply. I successfully installed the TWRP version you mentioned. But I don't know how to push the supersu zip file into my phone now since I don't have access to the internal storage.
Can you help me please?
Thank you very much!

khanhnn said:
I successfully installed the TWRP version you mentioned. But I don't know how to push the supersu zip file into my phone now since I don't have access to the internal storage.
Click to expand...
Click to collapse
Boot into TWRP, and your phone's internal storage should show up if you connect to your PC.

Hello redpoint73,
Thank you for your help.
But I'm now stuck in a new problem. I'm stuck at the bootloader screen.
I guess I'm somehow closer to finishing fixing my phone ( or I hope so since this is really important to me ).
I tried to install ROM ( which I downloaded from the HTC website I think ) but it didn't work out well. It said it was about to reboot but when it did, it returned to the bootloader screen. I tried to reboot a 2 times already but it always returned to the same screen.
What should I do now?
Thank you again.

khanhnn said:
But I'm now stuck in a new problem. I'm stuck at the bootloader screen.
Click to expand...
Click to collapse
I can't tell from the (lack of) information provided, what you have done to this point.
You said you installed TWRP 3.0? Were you ever able to boot into TWRP (or it just went to bootloader)?
If you were able to boot TWRP, were you able to use it access internal storage, as I suggested? Then what happened next?
khanhnn said:
I tried to install ROM ( which I downloaded from the HTC website I think ) but it didn't work out well. It said it was about to reboot but when it did, it returned to the bootloader screen. I tried to reboot a 2 times already but it always returned to the same screen.
Click to expand...
Click to collapse
What you downloaded is likely an RUU (ROM Update Utility) not just a ROM, there are distinct and critical differences, and you should take care not the mix up the terminology.
What is the (full and exact) file name of the RUU? You need to make sure its the right one for your device, before proceeding. And to make sure which path you want to take: TWRP to flash SuperSU or restore stock backup, or RUU. As the process is very different for each. RUU required you relocking the bootloader, which in turn prevents the installation of TWRP. So you need to be sure of which way you want to proceed the path forward, otherwise you will be wasting time going around in circles.
Also, you should do fastboot getvar all, and post the output (delete IMEI and serial number before posting) so we can see more info about the phone; in order to proceed properly.

Dear redpoint73,
Thank you for all the help you have provided until now.
Yes, I can get into the TWRP ( after I selected HBOOT, I selected RECOVERY and there I was, in the TWRP ). I can get to the internal storage but I'm not sure that is what you mentioned before. Which I can access is that I can select the zip file to install ( in the TWRP screen ) , nothing else I guesss. ( I asked yesterday that how could I access the internal storage because I wanted to copy the ROM file into my phone and install it in the TWRP )
I think I downloaded both the RUU and the ROM.
Case 1: WITH THE RUU:
Everything was okay and I'm pretty sure that I downloaded the correct version ( the other two versions said that I had to use the correct one for my phone ). The file name was RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined. However, I encountered the error 171 although I downloaded the HTC One Drivers already ( which is HTC Sync ). I couldn't get through this error so I gave up and tried something with the ROM.
Case 2: WITH THE ROM:
So I downloaded the ROM first from someone in xda forum. I installed it via TWRP and it said "Successful" on the screen. It said that I just gotta tap "reboot". But when my phone rebooted, it went back the bootloader screen. I rebooted 2 more times and the results were still the same. So I searched for some ROMs from other sources and all the times, it said "Successful" on the screen. It just always went back to the bootloader screen however.
Anyway, this is my phone info ( I think ) from the command getvar all:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.213311711.15G
version-cpld: None
version-microp: None
version-main: 5.07.425.1
version-misc: PVT SHIP S-ON
serialno: REMOVED
imei: REMOVED
imei2: Not Support
meid: 00000000000000
product: mels_tuhl
platform: hTCBmsm8974
modelid: 0P6B90000
cidnum: HTC__059
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 5c9466dd
hbootpreupdate: 11
gencheckpt: 0
I hope this works out well

Case 1 : wrong RUU for your device
Case 2 : wrong ROM for your device
Do you really read what I posted above ? Your device is M8 eye not M8.
Case 1 : there is no RUU available for M8 eye 5.07.425.1
Case 2 : there is almost no flashable ROM for M8 eye
Using M8 RUU you'll get error, using ROM meant for M8 it won't boot, you'll get stuck on bootloader
Until you can find 5.07.425.1 RUU or backup, temporarily fix your device by restoring 5.07.401.1 backup that you can find in my backup thread.

Thank you for all of your help guys!
All sorted and my phone is back, alive!
I really appreciate what you did for me!

khanhnn said:
Yes, I can get into the TWRP ( after I selected HBOOT, I selected RECOVERY and there I was, in the TWRP ). I can get to the internal storage but I'm not sure that is what you mentioned before. Which I can access is that I can select the zip file to install ( in the TWRP screen ) , nothing else I guesss. ( I asked yesterday that how could I access the internal storage because I wanted to copy the ROM file into my phone and install it in the TWRP )
Click to expand...
Click to collapse
When booted into TWRP, you can connect to PC, and the phone's internal storage (as well as SD, if you have one inserted) will show up as a drive on your PC, that you can freely drag and drop files, etc.
If not, go to the MOUNT button in TWRP; and check the "Data" box (and "Micro SDcard" if desired). But these should be checked by default (at least on the TWRP build I'm on).
khanhnn said:
Case 1: WITH THE RUU:
Everything was okay and I'm pretty sure that I downloaded the correct version ( the other two versions said that I had to use the correct one for my phone ). The file name was RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.
Click to expand...
Click to collapse
Not sure how you can be "pretty sure" this is the right RUU, and how you came to think it was. This is the RUU for the US AT&T version. Also, the RUU would need to match the version number in the RUU name (at least have "425" in the position x.xx.425.x as that number is the carrier version identifier).

sir same problem is with me,
i need correct ROM for htc one m8 eye,please help me ,
my email is
[email protected]

HTC one M8 Bricked in a confusing way...

(downloads were from this guide: https://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727)
I was trying to unlock/root the phone through the official way, I successfully unlocked it and installed TWRP 2.8.5.0 and booted the device, everything is working fine so I decided to flash the SU. I booted to the recovery but the UI was flashing, I assumed it was just a visual bug and went on, flashed the zip and afterward every click was lagging. I tried to reboot but now It's stuck on the HTC logo, it doesn't go anywhere, I can't even hold the power to shut it down (Had to freeze it to empty the battery) while it's off I can go to the bootloader and all the options in it like the fastboot and recovery which is still laggy and has a flashing UI (I made a backup to check if it's working). I considered loading a different ROM on an SD and try to flash it and see if that fixes it but I can't risk this getting worse.
any ideas what to do in the situation? I've been doing this since the GNexus so no need for an ELI5
what Info I currently know:
bootloader info:
software: official
M8_UL PVT SHIP S-Off (was already that I didn't unlock it )
HBOOT 3.19.0.000
OS 6.12.401.4
openDSP 51.2.2-00593-m8974_f0.1015
CID-HTC__A07
Dec 17 2015,14:15:48.90021118
fastboot info:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-main: 6.12.401.4
(bootloader) product: m8_ul
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__A07
stock HTC Android Rom last Marshmallow update
TWRP 2.8.5.0

That's is not stock lollipop, that's the latest stock Marshmallow.
TWRP 2.8.5.0 won't properly work on it. You need TWRP 3.x.x.x and make sure to install SuperSU 2.79 the lowest version or use the current one 2.81 or 2.82

ckpv5 said:
That's is not stock lollipop, that's the latest stock Marshmallow.
TWRP 2.8.5.0 won't properly work on it. You need TWRP 3.x.x.x and make sure to install SuperSU 2.79 the lowest version or use the current one 2.81 or 2.82
Click to expand...
Click to collapse
sorry I meant Andriod 6, 'Lollipop' was a mistype (names are changing too fast recently)
I borrowed an SD card and loaded an SU removal script on it and installed the one TWRP had in it, will see if I boots, currently it's displaying the red DEV text in addition to the HTC logo instead of only the logo
if It booted; I should flash a newer TWRP then I clear right?

Abd121 said:
sorry I meant Andriod 6, 'Lollipop' was a mistype (names are changing too fast recently)
I borrowed an SD card and loaded an SU removal script on it and installed the one TWRP had in it, will see if I boots, currently it's displaying the red DEV text in addition to the HTC logo instead of only the logo
if It booted; I should flash a newer TWRP then I clear right?
Click to expand...
Click to collapse
The TWRP version 2.8.5 is really old (over 2 years) and sure to cause problem. Just flash the TWRP version as directed by ckpv5, that guy knows what he is talking about.
---------- Post added at 10:47 AM ---------- Previous post was at 10:44 AM ----------
Abd121 said:
I tried to reboot but now It's stuck on the HTC logo, it doesn't go anywhere, I can't even hold the power to shut it down (Had to freeze it to empty the battery) while it's off I can go to the bootloader
Click to expand...
Click to collapse
To force a reboot, hold vol up + power, may need to hold the buttons for a minute or so in the "stuck condition". Once the screen goes black to reboot, let go of the buttons, and only hold vol down, and don't let go until you see the bootloader screen. If this fails to work (just reboots to HTC logo screen), you just got the timing wrong; either started pressing vol down too late, or let go too early. Just repeat the process, until you get the timing right.