Develop Bugs

[Q] Phone possibly bricked but it might be saveable!

Hi,
My first phone was rooted and I rooted my second too so I am confident rooting them however my second phone which had been rooted for a while had a space issue on SD card so I cleared out a few things which unfourtunatley included all the backup files ....
It worked fine afterwards but didnt let me change rom (using rom manager) so I just left it in working order for a few months until I wanted to reflash a new rom (as I am sure most people do every few months)
When it didnt let me, I tried to unroot and root options using superoneclick and unrevoked3 however, unrevoked 3 just stayed on "running root" and superoneclick got so far and crashed. When I go into the bootloader, it says something about some filed missing (think might be some nbh files).
At the moment, when normally turning the phone on, it stays on the screen with the pink circle, the first boot screen.
I have tried updating it using the RUU but it takes a long time and then says "use the correct rom for your device" which I am, this method just boots my phone and goes to a htc logo.
I can also get into the bootloader but when I apply update.zip, it says it has failed and something about files not existing/step 7 failure.
The thing is, I can get to fast boot and I am sure there is a way via ADB to force a new image (such as a cyanogen recovery image) on to the device.
Can anyone tell me how to push an image to the phone without using the RUU (as this didnt work for me)??
Maybe my phone is just bricked
Thank you very much!!

It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)

Thanks but I do not have another Desire...

Any card reader

yeah, I got a card reader laying around somewhere, if not ill go get one in Tesco, what where you thinking?

bortak said:
It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)
Click to expand...
Click to collapse
Hi Bortak, I am having similair problems with my phone sticking on the pink circle screen. I cant seem to load a recovery file from Bootloader. Will I need to make a Gold Card, my phone is s-off.
thanks mate

if phone is S-OFF go to my guide, look at advanced boot problems S-OFF.

SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!

Mugube said:
SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!
Click to expand...
Click to collapse
#facepalm#
Translation: I flashed another ROM because my other one didn't boot.

[Q] Recovery is corrupt and stalls at 'waiting' - Can't flash

I have been trying to root my incredible 2 ver 2.3.4 and managed to get it unlocked so I could change carriers. However, in the process of trying to also root the phone using adb I seem to have flashed improperly somehow and corrupted the recovery image instead of replacing it. Maybe I got hold of a corrupt TWC_recovery image and that is the problem. I was trying to flash TWC and it claimed to work but upon trying to reboot into recovery it simply sits at the white HTC screen and stalls.
When I use the cable and ADB to tryi and flash clockwork instead of TWC it apparently is not communicating with the phone. I used adb devices and the list is empty.
Incidentally the phone still boots up good and works fine as a phone but recovery mode using the phone menu is also history. Is there anyway to fix this. It seems like a catch 22 and I am stumped. At any rate, not being able to flash eithere using the phone itself or adb and the laptop has me stymied. Anyone have any ideas. I want to root also and it seems I have to get back to 2.3.3 in order to do that.
My experience is limited. I have successfully rooted my Hero (previous phone) and my Toshiba Thrive in the past though. All went well with them.
Any and all help will be greatly appreciated with proper thanks.

bushpilot444 said:
I have been trying to root my incredible 2 ver 2.3.4 and managed to get it unlocked so I could change carriers. However, in the process of trying to also root the phone using adb I seem to have flashed improperly somehow and corrupted the recovery image instead of replacing it. Maybe I got hold of a corrupt TWC_recovery image and that is the problem. I was trying to flash TWC and it claimed to work but upon trying to reboot into recovery it simply sits at the white HTC screen and stalls.
When I use the cable and ADB to tryi and flash clockwork instead of TWC it apparently is not communicating with the phone. I used adb devices and the list is empty.
Incidentally the phone still boots up good and works fine as a phone but recovery mode using the phone menu is also history. Is there anyway to fix this. It seems like a catch 22 and I am stumped. At any rate, not being able to flash eithere using the phone itself or adb and the laptop has me stymied. Anyone have any ideas. I want to root also and it seems I have to get back to 2.3.3 in order to do that.
My experience is limited. I have successfully rooted my Hero (previous phone) and my Toshiba Thrive in the past though. All went well with them.
Any and all help will be greatly appreciated with proper thanks.
Click to expand...
Click to collapse
download a recovery then rename it to recovery.img then boot your phone to fastboot and connect it to pc put the recovery into your fastboot folder then run this command
fastboot flash recovery recovery.img
this should fix your recovery NOTE ADB commands doesn't work until your phone boots up completely hence recovery is always flashed using fastboot commands

Or better yet, install rom manager and click install recovery
Sent from my ADR6350 using Tapatalk

An error occurred while flashing your recovery
weldawadyathink said:
Or better yet, install rom manager and click install recovery
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
When I try to install clockworkMod Recovery via Rom Mgr it downloads ok and then as it tries to install it dies with the error 'An error occurred while flashing your recovery.'
As I said earlier, when I try using the pc and cable it stalls on 'waiting' because it can't communicate with the phone.
The phone no longer goes into USB Boot like it did earlier..... it did though prior to the corruption.
Any other ideas? Thanks for the help.

Soft Bricked Help?
First of all, my inc2 is unlocked but is NOT rooted.
It has hboot-0.98.0000
radio-1.09.01.0312
rMMC-boot
July 18 2011, 12:39:36
Ver 2.3.4
I tried each of the methods in the earlier posts in the thread and neither worked for me. In the process, I have screwed something and now my phone will not boot into normal phone mode either.
Somehow I have corrupted something that is preventing my flashing a new recovery. Since it is not rooted, I am not sure what I can adb flash and what I can't. I have tried flashing both Clockwork recovery and TWP and although adb reports success the phone will not go into recovery. It simply displays stuck on the white screen with the HTC logo. I also tried flashing by zipping up a rom and clockwork recovery and renaming the zip PG32IMG.zip, loading it onto the sdcard, and loading it at bootup of hboot. It shows loading, then I select reboot bootloader, then try loading recovery and the same thing. Stuck on the HTC white screen. Now, the phone will not boot into normal phone mode either but just sticks on the white screen. I am wondering..... do I need to do a wipe or anything else prior to flashing the recovery? Maybe partition is bad. I don't know the procedure for any of that. I appreciate any help I can get.

Use revolutionary if its unlocked already it'll flash su n cwm
Sent from my ADR6350 using xda app-developers app

Anyone I can mail this phone to that will fix it and root it for $$?
chillybean said:
Use revolutionary if its unlocked already it'll flash su n cwm
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
I have tried that but it won't work because my phone is has hboot-0.98.0000 and when I follow the exact described procedure to change back to 97 it fails.
Is there some guru that fixes these for a living I can send the phone to? Anyone know? :crying:

What carrier are you planning to switch to? On the GSM side, you will most likely get no faster than 2G or 2.5G / Edge speed on data, depending on the radio band used by your provider. It is reliable & dependable for voice and/or WiFi calling with excellent battery life.
SInce you've tried to fixed it a number of ways with limited luck, you should consider flashing one of the factory/VZW's RUU file to restore it back to stock condition, unrooted - then, start the process over. The tacoroot method is what I've used last year to fixed one that appeared to be 100% brick.
PM me if you have trouble locating and want to use the RUU files as I believed that are no longer on the server - see what I can come up with from offline storage.

Letitride said:
What carrier are you planning to switch to? On the GSM side, you will most likely get no faster than 2G or 2.5G / Edge speed on data, depending on the radio band used by your provider. It is reliable & dependable for voice and/or WiFi calling with excellent battery life.
SInce you've tried to fixed it a number of ways with limited luck, you should consider flashing one of the factory/VZW's RUU file to restore it back to stock condition, unrooted - then, start the process over. The tacoroot method is what I've used last year to fixed one that appeared to be 100% brick.
PM me if you have trouble locating and want to use the RUU files as I believed that are no longer on the server - see what I can come up with from offline storage.
Click to expand...
Click to collapse
I have droid Incredible 2 by verizone. I got it unlocked and S-OFF to use custom rom.
During the process, SD card is not detecting any more. Also, USB debugging is not functioning. Therefore, I cannot use any custom ROM now.
I have flashed Chinese 3.07.1401.3 as S710D. Because any of original Vrizone rom are not loading. The current situation is that all functions
are working except which are related to SD CARD, like photo/video, music, software download etc.
USB HOST CONTROLLER shown that S3C usb driver is missing. Please help.

farooq4u said:
I have droid Incredible 2 by verizone. I got it unlocked and S-OFF to use custom rom.
During the process, SD card is not detecting any more. Also, USB debugging is not functioning. Therefore, I cannot use any custom ROM now.
I have flashed Chinese 3.07.1401.3 as S710D. Because any of original Vrizone rom are not loading. The current situation is that all functions
are working except which are related to SD CARD, like photo/video, music, software download etc.
USB HOST CONTROLLER shown that S3C usb driver is missing. Please help.
Click to expand...
Click to collapse
Can you confirm that you can boot into your bootloader - what are the statistics?
S-OFF ??
HBOOT-
Radio-
eMMC-boot
Apr 1 2001, 18:34:30 (or something similiar)
You are most likely missing the correct HTC drivers or have corrupted ones installed. Uninstall & clean it off your PC first, reboot & start over (or, use/borrow another computer to do this - look into the Control Panel ...)
Unless you are planning or using the DI2 on a Chinese carrier that support CDMA and/or GSM, you could run into issues - and, getting it to reset & work properly back on CDMA with VZW could be problematic too.
As for the SD card read error, have you checked its usability on the PC or another device directly, do you have another mSD card to check & verify that the slot ont the device isn't broken/damaged/dirty, etc. ?? Format it on a PC to FAT32 and copy a dummy file, re-insert to DI2 and see what happened ...

[Q] HELP!! Deleted OS!!

Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.

Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
clown6198 said:
Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.
Click to expand...
Click to collapse

stathis95194 said:
Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
Click to expand...
Click to collapse
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.

clown6198 said:
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.
Click to expand...
Click to collapse
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices

Yet another user stuck because they followed a tutorial or video guide, instead of taking the time to learn, read, and really understand the steps and concepts. This is exactly why I discourage such tutorials or YouTube guides (and Toolkits as well), as they leave you completely unequipped to recover if you have a problem, leaving your buddies at XDA to clean up the mess.
YouTube video or not, you shouldn't be doing anything you don't understand, and you shouldn't be wiping anything if you don't understand what the result will be.
You will need to troubleshoot the USB connectivity issue first. From there, unlock the bootloader again, install custom recovery and flash a ROM (as stathis95194 has already stated).

stathis95194 said:
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices
Click to expand...
Click to collapse
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept

clown6198 said:
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept
Click to expand...
Click to collapse
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.

redpoint73 said:
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.
Click to expand...
Click to collapse
will this work even with the S-ON?

clown6198 said:
will this work even with the S-ON?
Click to expand...
Click to collapse
Of course. I wouldn't be telling you to do it, otherwise.

redpoint73 said:
Of course. I wouldn't be telling you to do it, otherwise.
Click to expand...
Click to collapse
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!

Honestly, I would just install Philz recovery instead of TWRP and try to either install the ROM zip directly (after a full wipe), or sideload the ROM zip from your PC.

clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time. Find a ROM for your device that is based off of the 1.x firmware and download that. To get your device out of the bootloop and back into boot loader/recovery, hold power and volume up for quite some time until the screen shuts off. Then, hold power down while the screen is black and you'll be in the boot loader. From there you can use the arrow keys to select recovery. Of it isn't there, first select fastboot or hboot and look for it there. You should be in recovery, now you can go ahead and push the file to your phone. Ensuring it is a sense ROM based off of the 1.x firmware, go to wipe and do the standard swipe to wipe (will erase app data not pictures or downloads), then go into install and select your ROM and swipe. Be patient while your device turns on for the initial boot, it might take a while but your phone should be functional after that.

wtoj34 said:
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time.
Click to expand...
Click to collapse
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.

redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
Hi so Im in TWRP. I pushed a ROM called Android_Revolution_HD-One_M8_11.1 which is supposedly the closest rom to a stock one. I tried flashing the ROM many times, Im in the process of flashing it again after whiping like you said. The result is the same. After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Thanks,
clown6198

clown6198 said:
After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Click to expand...
Click to collapse
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.

redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
redpoint73 said:
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.
Click to expand...
Click to collapse
ahahaha THANK you so much!!!! I got the phone to work but now the problem is, I cant get the sound to work when Im playing music. I installed the harman kardon software and I cant get the music to work at all

clown6198 said:
I installed the harman kardon software and I cant get the music to work at all
Click to expand...
Click to collapse
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?

redpoint73 said:
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?
Click to expand...
Click to collapse
Damn. Apparently I need to get s-off in order for the harman kardon to work. Just need to uninstall harman kardon now... But yea sorry all I needed was to flash the rom. I didn't know the booting was going to take 5 mins and over. I thought that I was just stuck on the HTC logo. all I needed was to be patient ahaha Thanks a lot guys

I just want to unroot!!!

Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?

iSike said:
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
Click to expand...
Click to collapse
Open SuperSU->Settings->Unroot?

j to the 4n said:
Open SuperSU->Settings->Unroot?
Click to expand...
Click to collapse
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me

iSike said:
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
Click to expand...
Click to collapse
When I unrooted using SuperSu it ruined my installation also. I was stuck in a bootloop until I installed TWRP and reinstalled SuperSu, terrible!!! It eventually unrooted and I relocked bootloader but nothing worked so I was forced to root and unlock bootloader again.
I am wondering though, how did you return to stock? I really want the latest AT&T stock but when I install that RUU .exe it gives me error 155 so I can't install it. I was using 1.32 stock AT&T and wanted to install 2.6 (I think that's what it is, it's Android 5.1).
I am S-On, and not S-off, could that be an issue? Bootloader is unlocked and I am rooted now.

You know how u r supposed to rename the ruu u want to flash (assuming you downloaded the stock ruu for your carrier and device). The problem for me was, I could never connect my device thought adb after I rooted it (fast boot worked when I put it in fastboot). Even when I could give a command , it could never load the ruu. So what I did, was right click the ruu and click run as admin. It should open up a page on the top saying something about a ruu/rom utility. Make sure you device is connected and had usb debugging( before you got stuck in the loop hopefully). Now click accept and all that good stuff on the utility, it should scan your phone and show u your current rom image, and then show you the latest rom image. Click update and it will boot your phone to boot loader and begin sending it to your phone. IMPORTANT: DO NOT TOUCH YOUR PHONE. Now here's the catch, if it said it failed or something about a USB error, close the program and start it up again. If your phone is stuck without the download bar moving(displayed on your phone), you are going to have to hard reset it. Google how to do it for your device (just a button holding combination). And start the program again. It will take a couple times for the program to work (mine took about 5-6 times). But it will work sooner or later. I am not home atm, but when I get home, I will find the link to the page where this info is displayed in a more orderly fashion and with pictures. It will be tonight, probably about 9 hours. Try this though, if it is too confusing, wait till I post the link. Good Luck!!
EDIT: Sorry just got back home from a long day haha, I'll be sure to look for the link tomorrow. But my directions above should be good, give it a try.

HTC One M8 - Stuck at Boot Screen after Stagefright OTA [FIXED with RUU]

Hi all,
This is my M8 - Stock, Rooted & S-OFF. It's an unlocked O2 one which I use on EE in the UK
M8_UL PVT SHIP S-OFF
CID-02___001
HBOOT-3.19.0.0000
RADIO-1.25.21331147A1.06G
OpenSDP-v48.2.2-00564-M8974_FO.1211
OS-4.20.206.1 <--- after the OTA, this now reads OS-4.20.206.2
eMMC-boot 2048MB
The Stagefright OTA for my M8 just downloaded, so I re-flashed recovery with one that I extracted from the last 5.0.1 OTA (it usually has the latest TWRP) & let it install the OTA. Everything went fine, it rebooted afterwards to recovery, then automatically rebooted again... & then it sticks at the boot screen after showing the O2 logo & chiming.
From the stuck boot screen, I can reboot it into the boot loader or recovery fine, but now when I boot it into recovery I get this:
Android system recovery <3e>
LRX22C release-keys
Volume up/down to move highlight;
enter button to select.
reboot system now
apply from sd card
wipe data/factory reset
wipe cache partition
reboot into bootloader
power down
view recovery logs
apply from phone storage
_____________________
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code -1)
E:missing bitmap oem_unlock_bg_no
(Code -1)
Write host_mode success
handle_cota_install: No CW files. Skip cw installation.
What do you advise?
I haven't tried to factor reset it yet, but there is nothing on the phone that isn't backed up, so I can reset, re-flash or do anything required to get it back. As it's S-OFF, at a pinch I could change the SID & flash an entirely different ROM, although I have tended to stay Stock up until now...

If everything else fails, is it worth downloading the 5.0.1 RUU from http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 resetting my CID to HTC__001 & then letting it re-download & re-install the OTA before I re-root it & install TWRP again?
Nope... that didn't work! I just get
(bootloader) shift_signature size for header checking...
FAILED (remote: 32 header error)
regardless of whether I have a CID of HTC__001 or 11111111
& a factory reset doesn't seem to have made any difference either, as it is still stuck on the boot screen.
Any ideas of what to try next please?

Hey i Have the same Problem, but i doesnt have S-off (Still on S-ON) so i cant get RUU, or ?
Problemts solving hints ?!?!

I got the same problem, stuck on the boot screen.
S off, supercid, rooted, stock recovery and rom.
Hope we ll havé a solution quickly...

Hi,
maybe install TWRP recovery, restore everything to the state before applying the OTA and then trying once more?
But the newer TWRP versions might not even work any more, at least I have this problem, see http://forum.xda-developers.com/htc-one-m8/help/help-longer-enter-twrp-recovery-one-m8-t3186208.
HTC really seems to have done something nasty with this update. And it actually does not even fix all StageFright vulnerabilitis, the latest one stays open.
Cheers,
Tim

OK, I managed to get my phone back... I left the CID as HTC__001 but the trick was to rename the RUU to 0P6BIMG.zip & copy it to the root of the SD card using an adapter plugged into my PC. Then, I just rebooted it with Power & Vol Down, whereupon it automatically found it & started the update. I did note the prominent warning of "Do not power off your phone", so I left it to do its thing which took quite a while). Now, it's busy "optimizing apps", so I know that we are back up & running. OK, now, it's found the OTA & is busy downloading it again as well, so it appears that I now have a nice, stock, unrooted WWE install instead of my old O2 one. I must do a nandroid backup as soon as I replace the recovery with whatever version of TWRP works, but happy happy, I have my phone back again. I do hope the OTA doesn't kill it again when I run it, but as it is now 100% stock, I am full of hope.
Peter13337 - I don't know how to fix yours, seeing as you aren't S-OFF & the trick that I just pulled needed it, but I think that you might be able to flash an RUU that matches your own installation exactly. I would double check that though. However, if you know your CID & your modelid is 0P6B10000, then maybe your CID is in the list here http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 & if it is, then the RUU will work anyway & you'll be laughing.

JustinSB said:
OK, I managed to get my phone back...
Click to expand...
Click to collapse
Glad you got it running again. It would be very interesting for me to know whether you also have problems with twrp-2.8.7.0 not booting.

tim_h said:
It would be very interesting for me to know whether you also have problems with twrp-2.8.7.0 not booting.
Click to expand...
Click to collapse
I live right out in the sticks here in England, so my Internet connection is filthy - I'll have to leave it overnight to download all the apps that it needs to reinstall before I'll even try the OTA again. Then I'll see if the latest TWRP works, or it we have to go way back to get a version that plays nice. I also wonder where we stand on rooting this version too, but I guess that I just need to flash a current supersu from TWRP, when I finally get it working...
It looks like tomorrow will be just as much of a learning curve as today

JustinSB said:
I also wonder where we stand on rooting this version too, but I guess that I just need to flash a current supersu from TWRP, when I finally get it working...
Click to expand...
Click to collapse
Yep, flashing super-su 2.46 worked just fine for me. No problem there ...

JustinSB said:
Peter13337 - I don't know how to fix yours, seeing as you aren't S-OFF & the trick that I just pulled needed it, but I think that you might be able to flash an RUU that matches your own installation exactly. I would double check that though. However, if you know your CID & your modelid is 0P6B10000, then maybe your CID is in the list here http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 & if it is, then the RUU will work anyway & you'll be laughing.
Click to expand...
Click to collapse
Hmm
Found out, that i doesnt have stock OS. I Have CID VODAP102.
And Now ? Nandroid Backups which i Found for that need again S-OFF

peter13337 said:
Hmm
Found out, that i doesnt have stock OS. I Have CID VODAP102.
And Now ? Nandroid Backups which i Found for that need again S-OFF
Click to expand...
Click to collapse
crap
I've got exactly the same problem after running OTA I'm on s-on
I would be greatful for the solution
Edit: TWRP restore saved my phone
BTW it would be good to know how to apply this bloody update. I've stock rom so no sure why it bricked my phone

I had the same issue on my O2 M8 and managed to resolve by using RUU_M8_UL_L50_SENSE60_MR_O2_UK_4.20.206.1_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414450_signed.exe
I extracted rom.zip (by opening the exe to let it extract and then finding it within %temp%), renamed it to 0P6BIMG.zip and put it on my sdcard. I then booted up the phone with power and volume down and it applied the RUU. Once booted into Android I re-applied the stagefright update and all is working again.
Note: It will wipe the device.
o2 RUU can be found here:
https://www.androidfilehost.com/?fid=95916177934555499

Peter13337 - There's a Stock Nandroid backup for your CID here, which would give you (hopefully) a way out: http://forum.xda-developers.com/showthread.php?t=2701376
It may also give you the chance to run the update, then factory reset it to Google will restore everything for you from its automatic backups. Good luck

ritdaw said:
I had the same issue on my O2 M8 and managed to resolve by using RUU_M8_UL_L50_SENSE60_MR_O2_UK_4.20.206.1_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414450_signed.exe
I extracted rom.zip (by opening the exe to let it extract and then finding it within %temp%), renamed it to 0P6BIMG.zip and put it on my sdcard. I then booted up the phone with power and volume down and it applied the RUU. Once booted into Android I re-applied the stagefright update and all is working again.
Note: It will wipe the device.
o2 RUU can be found here:
https://www.androidfilehost.com/?fid=95916177934555499
Click to expand...
Click to collapse
:sly: You are a legend :thumbup:
Sent from my Nexus 6 using XDA Free mobile app

After restoring TWRP I tried running OTA again
it screwed the device up again
I've got a feeling there will be wave of similar posts soon
thanks HTC for faulty OTA

Are you all trying to install this update while having TWRP as your recovery? Cause that's where your problem is.
I've put 3 HTC M8's back to full stock and accepted the updates with no problems.
Sent from my HTC One_M8 using Tapatalk

tony_5309 said:
Are you all trying to install this update while having TWRP as your recovery? Cause that's where your problem is.
I've put 3 HTC M8's back to full stock and accepted the updates with no problems.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
no, I flashed recovery from the OTA file, otherwise i would get only red triangle.
I restored the backup by booting to TWRP.

tim_h said:
Yep, flashing super-su 2.46 worked just fine for me. No problem there ...
Click to expand...
Click to collapse
tim_h, I flashed TWRP 2.8.7.0 without any problems, rebooted it & used it to flash super-su 2.46 fine. It doesn't give me any problems at all & everything works & boots exactly as it should.

m112 said:
no, I flashed recovery from the OTA file, otherwise i would get only red triangle.
I restored the backup by booting to TWRP.
Click to expand...
Click to collapse
Oh ok. Good.
Sent from my HTC One_M8 using Tapatalk

JustinSB said:
I guess that I just need to flash a current supersu from TWRP, when I finally get it working...
Click to expand...
Click to collapse
OK, after flashing the RUU yesterday, as I mentioned above, I left it downloading all my apps overnight, along with the Stagefright OTA (on my reeeaaaly sloooooow Internet connection), rebooted it to load various HTC updates, then installed the OTA. WARNING! The OTA reboots it twice, & the second time it just sits there on the Boot Screen for well over a minute before it boots & goes into the whole "optimizing apps" routine. I was getting really worried that it had all gone wrong again, but thankfully I stepped away from the phone & let it be, & it came good just before I gave up hope. But compare this with what originally happened yesterday (on a rooted, slightly elderly stock ROM), when I also left it alone & it just sat there for an hour, doing nothing... I don't know the answer, but this OTA seems to be really very picky!
One it had installed & rebooted & I was 100% certain that I was in the clear on the OTA, I flashed in the latest TWRP, which worked fine & gave me no problems at all (Note, there have been reports of people having problems with recent versions of TWRP after this OTA, but I didn't replicate those problems). I used TWRP to install UPDATE-SuperSU-v2.46.zip so I am now back up & running rooted again. But because of this I now have a brand new, shiny WWE Stock ROM (as opposed to my elderly, & heavily patched O2 Stock) with the latest firmware, TWRP & SuperSU. I'm happy that it all works, but I have the greatest of sympathy for everyone out there who didn't have S-OFF, as without it I'd have had very serious problems.
Good luck everyone