Really hoping I can revive this incredible.
Got the phone in attempt to fix it, it's in a constant state of 'boot-loop syndrome'..
Can't go into recovery.. can't factory data reset.. all I get is the
....*vibrate*, white HTC incredible screen....*vibrate off*, etc. etc. etc.
The only thing that is working is hboot (as well as hboot usb when plugged into a pc).
But that's as far as I can get.. anything else I attempt to load from the hboot/bootloader it goes into a constant boot loop spasm.
The incredible is currently S-ON
Hboot- 0.92.0000
Radio-2.15.10.07.07
I've tried numerous PB31IMG stock files in attempt to recover the system.
The system/sd card detect the files just fine and attempt to load them.
The PB31IMG at pvillcomp ( http://pvillecomp.com/?page_id=22 ) didn't work, too old
This one, however, does work (only one so far I've found that does)
http://dinc.does-it.net/Stock_Images/4.08.605.2/PB31IMG.zip
But while going through the installation process it fails at Radio_**
all other variables within the file (bootloader, system, recovery, etc) complete successfully.
Once all the components of the zip file are installed, it gives the message
partition update fail!
Update fail!
Click to expand...
Click to collapse
Am stuck at this point, hoping for assistance.. if anyone knows any possible solutions or what the issue could be, please help!
Thank you.
echoedge said:
But while going through the installation process it fails at Radio_**
.
Click to expand...
Click to collapse
That sounds scary. I've heard that a failed radio flash is the only way to permenantly brick one of these phones.
Here's what I would try:
1. Update HBOOT to the latest, from here:
http://dinc.does-it.net/Hboots/Hboot_1.07/
2. Unlock the bootloader using htcdev (see cmlusco's or scotty's guides)
3. Flash a custom recovery using fastboot (I've used CWM and TWRP)
IF you can get all that to complete successfully, and can boot into recovery, you should then be able to get root adb access to the system. This will give you some more options, such as flashing an older RUU (again, see cmlusco's and scotty's guides for downgrading), and just maybe you'll be able to find something that works.
musical_chairs said:
That sounds scary. I've heard that a failed radio flash is the only way to permenantly brick one of these phones.
Here's what I would try:
1. Update HBOOT to the latest, from here:
http://dinc.does-it.net/Hboots/Hboot_1.07/
2. Unlock the bootloader using htcdev (see cmlusco's or scotty's guides)
3. Flash a custom recovery using fastboot (I've used CWM and TWRP)
IF you can get all that to complete successfully, and can boot into recovery, you should then be able to get root adb access to the system. This will give you some more options, such as flashing an older RUU (again, see cmlusco's and scotty's guides for downgrading), and just maybe you'll be able to find something that works.
Click to expand...
Click to collapse
Thanks for the website, was looking for something like that
Anywho, tried to flash it in the bootloader, it seems to find it a file for which is proper but does not give me any option to update it.
It just says "looking for PB31IMG... then finds it, says checking PB31IMG...", then the prompt goes away.
I'm quite limited when it comes to knowledge on this stuff, but anyone think if I decompile the stock ruu (~180mb) PB31IMG.zip, and flashboot each part of the update separately it may work?
Related
How can I flash the Stock Recovery ROM for my Desire Z?
Basically, I want to remove what ClockWorkMod did. Even when I turned Fast Boot off, turned off the phone, it wouldn't, and will startup ClockWorkMod instead. That said, I can't boot into HBOOT at all since wanting to go into HBOOT means I'm required to turn the phone off completely first.
I'm also having trouble finding my shipped ROM (1.34.707.5), and from the other threads I read, it seemed like a bad idea to grab other DZ ROMs and try flashing it.
Can anyone help/guide me with this? Thanks!
Edit: Prior to this, I was trying to overclock my DZ using this guide for noobs http: //androidforums.com/desire-z-all-things-root/233729-ultimate-guide-rooting-overclocking-your-bell-desire-z-newb-friendly.html. I followed every step, inclusive of the backup.
Kudos to Blue1k for the guide and gtrab for the amazing overclock script
Code:
adb reboot bootloader
will get you into fastboot usb.
Hm,fastboot at settings menu deactivated.
Turned phone off,then holding trackpad down and turning phone
on works for me!
Thanks keinengel for the tip!
@Ganli I can't turn phone off using the menu (and with Fast Boot turned off). I tried removing the battery and I got into HBOOT successfully.
That said, I didn't like the way ClockWorkMod disabled my turning off phone (I do appreciate the backup features it provided). Is there anyway I could restore the original recovery back?
n3ph said:
That said, I didn't like the way ClockWorkMod disabled my turning off phone (I do appreciate the backup features it provided). Is there anyway I could restore the original recovery back?
Click to expand...
Click to collapse
There's a known issue with ClockworkMod where, when you have your phone turned off and you plug in the charger, it automatically then starts up in Clockwork. Is this what you're seeing ? Because if not, that sounds very odd (Clockwork disabling turning off your phone ).
You can flash a new recovery from fastboot, if you have the eng hboot installed. I presume you can take the recovery.img file from one of the stock ROMs, then do "fastboot flash recovery recovery.img".
steviewevie said:
There's a known issue with ClockworkMod where, when you have your phone turned off and you plug in the charger, it automatically then starts up in Clockwork. Is this what you're seeing ? Because if not, that sounds very odd (Clockwork disabling turning off your phone ).
You can flash a new recovery from fastboot, if you have the eng hboot installed. I presume you can take the recovery.img file from one of the stock ROMs, then do "fastboot flash recovery recovery.img".
Click to expand...
Click to collapse
Bingo. It turned off completely when I non-fast boot powered it down without the charger plugged in!
I would like to flash the original recovery like what you mentioned. I am afraid of hardware incompatibilities as mine has a different software version than the ones I've seen here. I wonder if I could use them. (By the way, I haven't seen any recovery.img around, only PC10IMGs)
n3ph said:
I would like to flash the original recovery like what you mentioned. I am afraid of hardware incompatibilities as mine has a different software version than the ones I've seen here. I wonder if I could use them. (By the way, I haven't seen any recovery.img around, only PC10IMGs)
Click to expand...
Click to collapse
The PC10IMG is a zip file containing various stuff to make up a ROM, mainly these are partition images. One of them is recovery.img. So you can get recovery.img from one of those ROM images.
What ROM are you running exactly ?
Stock ROM. Probably one of the Asian version.
Baseband
12.28b.60.140eU_26.03.02.02_M
Kernel
2.6.32.21-gd2764ed
[email protected] #1
Tue Oct 26 16:04:03 CST 2010
Build number
1.34.707.5 CL273326 release-keys
Software
1.34.707.5
I haven't seen any ROM with this version on XDA yet. I saw about the RUU in other threads. Will I be able to select flashing only the recovery from RUU? Or is it a full flash only?
n3ph said:
I haven't seen any ROM with this version on XDA yet. I saw about the RUU in other threads. Will I be able to select flashing only the recovery from RUU? Or is it a full flash only?
Click to expand...
Click to collapse
I have never tried the RUU. At a complete guess I would think it is only a full flash.
You can run the RUU then leave it at the first screen, then open up another window and find where Windows has put the temp files it has extracted from the RUU. Amongst those will be the ROM image, which you can open up (it's a zip file) and find the "recovery.img" file, which you can flash via fastboot if you have the eng hboot installed.
Understood. One more question, my HBOOT is stock. Not sure if this is different from "eng hboot" By Fastboot, you meant this program http: //forum.xda-developers.com/showthread.php?t=463627 right?
Im confused here and just thinking out loud for myself but maybe to provoke some logic here --
without clockworkmod you are unable to flash any roms. you must have clockworkmod to tinker with your phone. no clockworkmod = unroot, or semi root psuedo root whatever.
the only way people can flash stuff is with clockworkmod. its the only recovery available at this time.
if i am missing something or being redundant, my sincere regards.
??
n3ph said:
Understood. One more question, my HBOOT is stock. Not sure if this is different from "eng hboot" By Fastboot, you meant this program http: //forum.xda-developers.com/showthread.php?t=463627 right?
Click to expand...
Click to collapse
You can tell which hboot you have if you shut down the phone (fully, not HTC's confusingly-named "fast boot" mode, which is a sleep state) and then hold Volume down and then hold Power till it turns on.
If it says "SHIP" on the first line, it is the stock hboot. The engineering hboot says "ENG". The eng hboot gives you more options.
No need to install that program, if you go through the steps in my adb guide to setup adb via the SDK, you will have fastboot too.
androidcues said:
without clockworkmod you are unable to flash any roms. you must have clockworkmod to tinker with your phone. no clockworkmod = unroot, or semi root psuedo root whatever.
the only way people can flash stuff is with clockworkmod. its the only recovery available at this time.
Click to expand...
Click to collapse
Yes, the only recovery options we have at the moment are stock recovery or ClockworkMod recovery (installed from ROM Manager). Maybe we will get some more custom recoveries in the future, who knows ?
But you don't need ClockworkMod to flash a ROM. You can flash stock ROMs on a stock phone, though only ones designed specifically for your sub-model of phone (e.g. European ROMs if it's a European phone, T-Mobile ROMs if it's a G2, etc, etc).
If you get S-OFF then you can flash custom ROMs to your phone, or stock ROMs from a different stock Vision (e.g. flashing a stock European ROM onto an Asian DZ).
ClockworkMod is very very useful for letting you do a full backup (nandroid backup) of your ROM.
You can also flash other ways, e.g. flashing from your SD card via hboot, or if you have the eng hboot installed then you can use the fastboot mode/utility to flash too.
thank you i stand corrected.
Thanks for the help. After researching more on what you said, I have a better idea on the flashing process =)
I'll try to reserch more while waiting for a compatible ROM for my phone before trying anything again (in case I brick it)
n3ph said:
Thanks for the help. After researching more on what you said, I have a better idea on the flashing process =)
I'll try to reserch more while waiting for a compatible ROM for my phone before trying anything again (in case I brick it)
Click to expand...
Click to collapse
I'd like to know if anyone was able to make a copy of the stock ROM or has found the RUU for this specific version.
Guys, please help!! Yesterday I was so hungry for some ice cream sandwich, that I accidentally tried to flash a rom for HTC Incredible S onto my HTC Incredible! Only after the install failed (used Rom Manager, and when it rebooted, it was saying something about missing pb31img.nmh or some weird extension like that) did i realize what i have done. However my phone was pretty much functional at that point. I tried booting into hboot and doing recovery, but whenever i selected any of the hboot options (clear storage, recovery, factory reset), it would just reboot back into hboot. But at this point i was still able to boot into my phone. I tried backing up from saved images using Rom Manager, but when it rebooted, it always gave the pb31img message. Then it just froze. When i pulled the battery and plugged it back in, the phone just got stuck at the HTC Incredible white screen and would not boot. I've been searching the forums long and hard, but it seems all solutions assume i need to be able to boot into the phone, or to be able to simply use hboot to recover. None of these seem to be viable options for me at the moment. Please help with any suggestions as I wanted to wait for the Tegra 3 phones to come out before upgrading!!
fastboot and adb require phone to be able to boot. my phone does not boot into anything besides hboot. and even in hboot, none of the functions work. i was able to format my sd card and copy an img of the proper rom on there, and when i go to hboot->fastboot, it says "loading pb31img.zip" and shows the blue status bar, then says parsing "pb31img.zip" but that takes a second and then it just goes back to the hboot screen without installing anything!! does this mean i'm totally SOL now?
You can use fastboot to flash a stock image. You do not need to be able to boot to use fastboot,fastboot is thru hboot.
http://android-dls.com/wiki/index.php?title=Fastboot#Fastboot_Commands
However if you can get into hboot (the screen with the PB31IMG.zip message), then you can just do an ruu thru hboot. It sounds like your missing or have a corrupt boot image. You need to download the PB31IMG.zip ruu file from here (http://pvillecomp.com/?page_id=22), place it on your sdcard in no folders and then reboot thr phone. Hboot will find the file and prompt you to press vol up to update. Once thats done press vol up to reboot. Your phone should boot now. You will have to reroot if you want.
cmlusco said:
You can use fastboot to flash a stock image. You do not need to be able to boot to use fastboot,fastboot is thru hboot.
However if you can get into hboot (the screen with the PB31IMG.zip message), then you can just do an ruu thru hboot. It sounds like your missing or have a corrupt boot image. You need to download the PB31IMG.zip ruu file from here , place it on your sdcard in no folders and then reboot thr phone. Hboot will find the file and prompt you to press vol up to update. Once thats done press vol up to reboot. Your phone should boot now. You will have to reroot if you want.
Click to expand...
Click to collapse
OMG!!! Thank you soooo much! I can't give you enough thanks, you have no idea! I don't know why this one worked and lots of other cwm img files and rom img files didn't though! And i tried using the fastboot command through the terminal from the computer to flash this same RUU file, but it was giving me problems. But when i put it on the sd card, it worked right away. Now i have a phone to wait out for the Tegra 3!
Glad i could help.
Everything I have read so far says NOT to do any of that through a ROM manager. Could that be why his attempts to install a stock recovery failed?
This really helped me in my situation. I think I had an old version of clockworkmod on my Incredible and it wouldn't let me flash things correctly so it got me stuck in a bootloop but than I flashed the Froyo RUU PB31IMG.zip in hboot and it got my phone working again. Now time to re-root. (I chose Froyo because if you want to re-root with gingerbread you have to downgrade to Froyo which is a hassle)
Your device can not really be bricked. Impossible if you know what you are doing . Revert back to old rom after booting into recovery or choose a simpler from.
Sent from my HTC Incredible S
emaninthenation said:
Now time to re-root. (I chose Froyo because if you want to re-root with gingerbread you have to downgrade to Froyo which is a hassle)
Click to expand...
Click to collapse
If you are s-off it does not matter whether you use the froyo or gingerbread ruu. That is the whole point of getting s-off, so that if an ota or anything else for that matter replaces the custom recovery with the stock recovery, you will still be s-off allowing you to flash the custom recovery right back without having to do all that unrevoked stuff again.
I recently purchase a used Dinc2 with 2.3.4. It worked fine until i tried to root/unlock it. I followed the HTCDev guide for unlocking and after rebooting following accepting the agreement the phone stuck on the HTC splash screen. I've spent several weeks reading and searching trying to find a solution, but without any success. i'm hoping someone might be able to point me in the right direction.
I don't consider myself a noob since I've been flashing my unlocked OG Droid for several years, however I will admit this HTC is a whole different animal.
Here are the details of what I've found so far:
* I can use volume down + power to get into hboot, which tells me the phone is unlocked with S-On.
* If i use fastboot oem lock I get " FAILED (status read failed (Too many links))"
* When I fastboot boot into CWM I get several E: Can't mount cache/ errors
* Formatting the cache fails with CWM and 4ext
* Flashing ROMs with either CWM or 4ext fails as well
Is there anything I should still try before writing this phone off?
thanks
Get s off
Sent from my Incredible 2 using xda app-developers app
You could try the root method in the "comprehensive S-OFF / root methods" thread in development, second post. It involves flashing a RUU in hboot, which you may be able to do. And, I'm not sure, but it could fix any partition error if cache somehow got corrupted.
What does hboot say? Should say unlocked and S-ON if you're HTC unlocked.
Sent from the frozen tundra of Mississippi using xda app-developers app
Thanks for the tips.
When doing this, when I get to the section where 'fastboot flash recovery recovery.img', it hangs at writing 'recovery' and doesn't do anything.
Further update...
If I use 'Fastboot boot recovery.img' instead of 'fastboot flash recovery recovery.img' then 4ext loads, however it tells me:
ATTN: recovery is in safe mode. this is because the following partition is not accessible: "cache". Please enter the wipe menu and wipe cache! If you changes hboot you should choose to format all partitions (except sdcard).
If I follow either of those instructions and fastboot boot into 4ext it gives me the same 'safe mode' error every time.
It seems your Dinc2 is security locked, S-ON, you need a XTC clip to S-OFF your Dinc2
Before I seek out an XTC clip I would like to try using a signed version of PG32IMG.zip, however I haven't been able to locate one for the 2.3.4 firmware. Most resources point back to this link at rootzwiki rootzwiki.com/topic/18873-ruu-htc-incredible-2-signed-ruus-pg32imgzip/ but the link to the downloads is broken.
Can anyone point me to a valid download for a signed version of PG32IMG?
thanks
jwendorf said:
Before I seek out an XTC clip I would like to try using a signed version of PG32IMG.zip, however I haven't been able to locate one for the 2.3.4 firmware. Most resources point back to this link at rootzwiki rootzwiki.com/topic/18873-ruu-htc-incredible-2-signed-ruus-pg32imgzip/ but the link to the downloads is broken.
Can anyone point me to a valid download for a signed version of PG32IMG?
thanks
Click to expand...
Click to collapse
Have you tried running "factory reset" from the hboot menu?
Your phone seems to have partition errors (probably why it hung on the HTC screen after you unlocked, and why cache is giving you errors). I'm not sure if an RUU will wipe/re-write your partitions for you, or if it could error and brick the phone. I know that flashing a RUU is delicate, and errors while doing that can brick the phone. So, the only reason I'd flash a RUU at this point you're at is if you think you're already bricked and want to try something to fix it.
If you remember what Verizon version you had before you unlocked, you could find the stock rom, extract the boot.img into your android directory, and try flashing that in fastboot using "fastboot flash boot boot.img". That might get you booted in your current rom. Try this stock ROM: http://forum.xda-developers.com/showthread.php?t=1599767 In case you didn't know, when you're HTCDev unlocked, you have to flash boot.img every time you flash a ROM.
When I went from HTCDev Unlocked to S-OFF, all I did was flash an RUU and then run revolutionary. RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
Which can be found in the "Comprehensive S-OFF/Root Methods" thread in development.
Download the first link under "Tacoroot" and extract the RUU zip file. It goes on the root of your SD card, and you rename it "PG32IMG.zip". Then, you have to go to fastboot (the bootloader) and type in the adb command "fastboot oem lock". After that, select "bootloader" and it should scan for the PG32IMG.zip and ask if you want to flash. If it runs correctly you should be on hboot version .97 with a stock ROM, and you can run revolutionary.
Did you ever type the command "fastboot oem unlock" at any point in the HTCDev unlock process? If so, you may not be able to run that RUU.
Okay Im going to try to get the whole story in here, so stick with me.
I bought a used ATT m8, that was converted to GPE. It was unlocked and s-off.
I wanted to go back to stock Rom, but twrp recovery wouldnt flash ANYTHING. I tried a bunch of roms and mod files. I would frequently get Status 7 error. Tried different recoveries, same thing.
I tried using http://forum.xda-developers.com/showthread.php?t=2733523 this to get back to stock. Changed my CID to 11111111. Still didnt work. ROM would install, but it kept rebooting to recovery. I reflashed stock recovery and factory wiped. Then I installed TWRP again and nothing changed. Something really jacked up when I tried to flash an RUU zip using the ./fastboot oem rebootRUU command to flash a 1.5 gb RUU zip. Obviously I did something wrong, because now all I see is an HTC logo and four triangles at each corner. I can still enter adb commands, but the bootloader and recovery are both gone.
Any assistance would be SO appreciated. Im without a phone right now.
Yall are the best.
UPDATE: used fastboot to flash stock firmware. Now i have bootloader and twrp recovery but no rom to flash or nandroid to restore. I cant move any nandroid TO the device for some reaodn. Ive tried for about a half hour now. And the one rom that I tried to adb sideload failed to install
bigbuckin said:
Okay Im going to try to get the whole story in here, so stick with me.
I bought a used ATT m8, that was converted to GPE. It was unlocked and s-off.
I wanted to go back to stock Rom, but twrp recovery wouldnt flash ANYTHING. I tried a bunch of roms and mod files. I would frequently get Status 7 error. Tried different recoveries, same thing.
I tried using http://forum.xda-developers.com/showthread.php?t=2733523 this to get back to stock. Changed my CID to 11111111. Still didnt work. ROM would install, but it kept rebooting to recovery. I reflashed stock recovery and factory wiped. Then I installed TWRP again and nothing changed. Something really jacked up when I tried to flash an RUU zip using the ./fastboot oem rebootRUU command to flash a 1.5 gb RUU zip. Obviously I did something wrong, because now all I see is an HTC logo and four triangles at each corner. I can still enter adb commands, but the bootloader and recovery are both gone.
Any assistance would be SO appreciated. Im without a phone right now.
Yall are the best.
Click to expand...
Click to collapse
Did you run a Sense RUU? You'll need to to resize your partitions.
When the previous owner converted to GPE, he ran a GPE RUU that makes the system partition too small for Sense.
You need to run an AT&T RUU to convert back properly.
Here is a link for the official HTC/AT&T RUU download.
The full instructions are there as well for manually updating.
Read them.
The download is at the bottom of the page.
I finally got the phone booted back into gpe FYI.
But yes, I tried two different HTC ruu zip files by using the OEM rebootruu command and then flashing them. They were around 1.5 GB in size and I do recall it failing because the file was too large to complete is there a way to manually change partition size?
Also worth noting I am using a Mac, and can't use the HTC ruu .exe files
bigbuckin said:
I finally got the phone booted back into gpe FYI.
But yes, I tried two different HTC ruu zip files by using the OEM rebootruu command and then flashing them. They were around 1.5 GB in size and I do recall it failing because the file was too large to complete is there a way to manually change partition size?
Click to expand...
Click to collapse
bigbuckin said:
Also worth noting I am using a Mac, and can't use the HTC ruu .exe files
Click to expand...
Click to collapse
This thread has everything you need.
You'll want option 1. When you boot into bootloader, you'll have to select hboot to start the flash. I don't know why he left that out of his instructions.
Just to clarify, there are no prerequisites to doing this? I don't need to bother with firmware or anything? I just put that file on my SD card, rename it, flash hboot, flash file, reboot into sense?
bigbuckin said:
Just to clarify, there are no prerequisites to doing this? I don't need to bother with firmware or anything? I just put that file on my SD card, rename it, flash hboot, flash file, reboot into sense?
Click to expand...
Click to collapse
Petty much.
Boot into bootloader, select hboot, press vol up to flash, press power button to reboot after the flash. Done.
You'll get prompts for the volume up and press power button.
No need to do anything but rename it, put it on extSD, and go to hboot.
You're amazing. I've spent countless hours troubleshooting this and never came across this thread. I'll update when finished to confirm it worked for me
Oh, I forgot to add, when you done with the flash make sure you delete the renamed file from your extSD. If you don't, every time you boot to hboot it'll try to update again.
So, everything was looking good until (11) System - FAILED
...at the bottom it had an error message saying something like "Image size too large" or something like that. I took a picture if it would help.
Basically the same thing ive been seeing with every other thing ive tried to do
bigbuckin said:
So, everything was looking good until (11) System - FAILED
...at the bottom it had an error message saying something like "Image size too large" or something like that. I took a picture if it would help.
Basically the same thing ive been seeing with every other thing ive tried to do
Click to expand...
Click to collapse
http://forum.xda-developers.com/att...u-m8att-4-4-4-s-off-onlynewest-t3015680/page2
Scroll to post #17, and read the next few.
You need to run it twice.
I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.
Gitnerd said:
I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.
Click to expand...
Click to collapse
If you ask me
since i have s-off I would just change my mid and cid to dev edition then flash dev end ruu.
Gitnerd said:
I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.
Click to expand...
Click to collapse
That's not how to flash an RUU.zip
This is how it is done.
Make sure that your extSD is formatted to FAT32 first. It won't work otherwise.
After the format, rename the zip to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your card.
Boot into bootloader (Turn off you phone, then boot it up while holding power + vol down) and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash ~ power to reboot)
That's it. Super easy.
Make sure to delete the renamed file from your extSD, otherwise every time you boot to hboot, it'll try to update again.
xunholyx said:
That's not how to flash an RUU.zip
This is how it is done.
Make sure that your extSD is formatted to FAT32 first. It won't work otherwise.
After the format, rename the zip to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your card.
Boot into bootloader (Turn off you phone, then boot it up while holding power + vol down) and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash ~ power to reboot)
That's it. Super easy.
Make sure to delete the renamed file from your extSD, otherwise every time you boot to hboot, it'll try to update again.
Click to expand...
Click to collapse
Hello, thank you for your reply, I was traveling for holidays and have been working on the phone for the past couple of days and have run into alot of trouble doing what you say here, any help would be greatly appreciated I'm at the end of my rope with this phone. I got the 0P6BIMG.zip RUU and loaded it onto my Fat.32 formatted SD Card , I loaded the card into the phone and followed the fastboot options to flash, it recognized the RUU and attempted to flash it but said the model ID was incorrect. I opened up the zip and sure enough the android-info.txt file in the RUU does not list my model number and I cannot put my model number into it because it is an htc encrypted zip that will not let me change the file properties of the archive. I thought about trying to put the HTC into developer kernel so that my model ID would line up with that of the RUU info file but I did something (don't know what I did) and now fastboot won't even recognize the device (fastboot devices command shows nothing when phone is in fastboot USB mode).
My mid is 0P6B20000
My cid is VZW_001
Gitnerd said:
Hello, thank you for your reply, I was traveling for holidays and have been working on the phone for the past couple of days and have run into alot of trouble doing what you say here, any help would be greatly appreciated I'm at the end of my rope with this phone. I got the 0P6BIMG.zip RUU and loaded it onto my Fat.32 formatted SD Card , I loaded the card into the phone and followed the fastboot options to flash, it recognized the RUU and attempted to flash it but said the model ID was incorrect. I opened up the zip and sure enough the android-info.txt file in the RUU does not list my model number and I cannot put my model number into it because it is an htc encrypted zip that will not let me change the file properties of the archive. I thought about trying to put the HTC into developer kernel so that my model ID would line up with that of the RUU info file but I did something (don't know what I did) and now fastboot won't even recognize the device (fastboot devices command shows nothing when phone is in fastboot USB mode).
My mid is 0P6B20000
My cid is VZW_001
Click to expand...
Click to collapse
You need to use this RUU.zip
It is for the Verizon model
xunholyx said:
You need to use this RUU.zip
It is for the Verizon model
Click to expand...
Click to collapse
My goodness, I looked for this RUU everywhere, I would type in my mid and cid into google, I checked the One m8 archive of RUU's in that XDA thread, I couldn't find it. I don't know how you did, but you just saved my phone! Im booted into Android 4.4.2, receiving texts and everything. I'll figure out if I'm safe to update android later, I'm just so happy to have a working phone again. I gave you a thanks but do you have a contribution link or anything I could give to? You have helped me out tremendously.
Gitnerd said:
My goodness, I looked for this RUU everywhere, I would type in my mid and cid into google, I checked the One m8 archive of RUU's in that XDA thread, I couldn't find it. I don't know how you did, but you just saved my phone! Im booted into Android 4.4.2, receiving texts and everything. I'll figure out if I'm safe to update android later, I'm just so happy to have a working phone again. I gave you a thanks but do you have a contribution link or anything I could give to? You have helped me out tremendously.
Click to expand...
Click to collapse
I gave you an old RUU link. Sorry.
You can get the 5.0.1 RUU.zip from here if you want to update. It would be good to do it now, since running the RUU wipes your device, and yours is already wiped.
I've sent a PM with a donation link.
Thank you!