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.
Related
Ok, I've read through several other boot loop scenarios. I need to get this taken care of, one way or another, pretty quickly, as I've been without a phone for nearly a week screwing with it
The battery went completely dead while I was surfing the net. Upon plugging it in and trying to boot it up, it started looping... It comes up pretty quick with the white screen with HTC Incredible. Then after a few seconds, shuts off, and starts all over. I can get into hboot, and even though it's an SLCD model, I have been able to flash it with the .77 hboot image and access the phone via fastboot. However, I tried flashing with a few of my backups, and none of that seems to help.
I'm getting pretty desperate.
Maybe your backups don't work because you're not on the newest hboot, .92
Sent from my HTC Incredible
Do you have amon ra?..if you do then use the usb toggle and upload a new rom to the usb drive with that. If you dont then download the pc6img file for it so you can flash it in hboot.
Ok, I have tried flashing every recovery image I could find.. they all seem to flash, then when I select recovery, it comes up with the white screen a starts looping.
As to the backups not working, I flashed them, then flashed the .92 hboot.
Unroot and reload a stock ruu via exe from a computer. That should work 100%.
Jason Black said:
Unroot and reload a stock ruu via exe from a computer. That should work 100%.
Click to expand...
Click to collapse
The issue with that, if I understand the procedure correctly, is that I have to be able to talk via adb or recovery, which I cannot. I am very limited in what I can do with the phone, because I can only use fastboot, or flash PB31IMG files through hboot.
bradinc said:
The issue with that, if I understand the procedure correctly, is that I have to be able to talk via adb or recovery, which I cannot. I am very limited in what I can do with the phone, because I can only use fastboot, or flash PB31IMG files through hboot.
Click to expand...
Click to collapse
No. You dont have to use recovery at all. Find the stock rom. Look at what its called then type "name of stock rom.exe" into google. Download the exe file. Pretty much, you run it. Hold volume down and power on your phone. Go into hboot, plus usb to phone and computer when prompted. Click fastboot and wait till you see fastboot usb. Then start the exe process.
bradinc said:
The issue with that, if I understand the procedure correctly, is that I have to be able to talk via adb or recovery, which I cannot. I am very limited in what I can do with the phone, because I can only use fastboot, or flash PB31IMG files through hboot.
Click to expand...
Click to collapse
If you have s-off all you have to do is down load the RUU to your sdcard and rename it PB31IMG.zip and it will automatically load when you boot into hboot. That is how I unrooted my phone.
If you have s-on that is another thing and I'm not sure how to do it.
kzoodroid said:
If you have s-off all you have to do is down load the RUU to your sdcard and rename it PB31IMG.zip and it will automatically load when you boot into hboot. That is how I unrooted my phone.
If you have s-on that is another thing and I'm not sure how to do it.
Click to expand...
Click to collapse
If he has either s off or s on, the step i gave him up there should work either way. Considering that he cant go into recovery. Meaning he wont be able to load what you're saying into his sd card...
Jason Black said:
If he has either s off or s on, the step i gave him up there should work either way. Considering that he cant go into recovery. Meaning he wont be able to load what you're saying into his sd card...
Click to expand...
Click to collapse
You don't go into recovery to run the PB31IMG.zip file as it loads from hboot automatically. If it needs a workiing recovery image to run thats something I never ran into.
Here's the stock ROMs:
http://forum.xda-developers.com/showthread.php?t=969973
kzoodroid said:
You don't go into recovery to run the PB31IMG.zip file as it loads from hboot automatically. If it needs a workiing recovery image to run thats something I never ran into.
Click to expand...
Click to collapse
His phone doesn't work,as in,it doesnt boot properly or go into recovery, so that means he would have to take out the sd card. Its aloy easier to use the pb*****.exe file while in fastboot usb.
carngeX said:
Here's the stock ROMs:
http://forum.xda-developers.com/showthread.php?t=969973
Click to expand...
Click to collapse
Can you link him to a stock exe file instead?
The RUU .exe that you run from HTC Sync is in there as well. Its listed as 'option 1'.
But if he can get into Hboot, it would be easier to just run the PB31IMG stock image. And since he said he can flash from Hboot still in one of his previous posts... I'd say he try this option first (it's listed as option 2 in the thread I posted).
carngeX said:
The RUU .exe that you run from HTC Sync is in there as well. Its listed as 'option 1'.
But if he can get into Hboot, it would be easier to just run the PB31IMG stock image. And since he said he can flash from Hboot still in one of his previous posts... I'd say he try this option first (it's listed as option 2 in the thread I posted).
Click to expand...
Click to collapse
Sounds like a good idea!
For future reference, almost all radios/recoveries/stock images and such can be found over at this site: www.dougpiston.com
I also have saved copies of both the executable RUU and image file (PB31IMG_3.26.605.1_RUU) saved on my computer and could upload them if needed.
I just used the same image file a couple weeks ago to unroot my slcd phone.
kzoodroid said:
I also have saved copies of both the executable RUU and image file (PB31IMG_3.26.605.1_RUU) saved on my computer and could upload them if needed.
I just used the same image file a couple weeks ago to unroot my slcd phone.
Click to expand...
Click to collapse
An upload might be handy, since the ones I've downloaded from DP's site appear to be corrupt - I cannot open the zip files.
What do you mean you can't open the zips?
Check the MD5 sums of the ones you downloaded compared to the ones on his site.
bradinc said:
An upload might be handy, since the ones I've downloaded from DP's site appear to be corrupt - I cannot open the zip files.
Click to expand...
Click to collapse
http://www.megaupload.com/?d=87LDBNTD
You don't open the zip file just rename it PB31IMG.zip and put it on the root of the sdcard, reboot into hboot and it will find the file, check it, then run it all on its own.
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 have searched to find the answer to this but the going from 1.29 to 1.28 bit is confusing me.
I have an HTC One X that was on T-Mobile UK 1.26. I usedthe HTC Dev and clockwork and ended up with the LeeDroid Rom with 1.29 firmware.
I have the phone for sale and have someone local who wants it, but he says he wants the standard rom on it or a stock HTC one. Don't ask why, I don't know.
What exactly can I do to get it back...I have some backups I made via the option in Recovery all the way back to the T-Mobile rom...with options to restore boot.img
Or can't I go back because I am on 1.29 ?
monkeyphonix said:
I have searched to find the answer to this but the going from 1.29 to 1.28 bit is confusing me.
I have an HTC One X that was on T-Mobile UK 1.26. I usedthe HTC Dev and clockwork and ended up with the LeeDroid Rom with 1.29 firmware.
I have the phone for sale and have someone local who wants it, but he says he wants the standard rom on it or a stock HTC one. Don't ask why, I don't know.
What exactly can I do to get it back...I have some backups I made via the option in Recovery all the way back to the T-Mobile rom...with options to restore boot.img
Or can't I go back because I am on 1.29 ?
Click to expand...
Click to collapse
You can go back; it's only if you'd done an official update (OTA or RUU) that you'd be stuck, because they also update the bootloader and you can't downgrade that.
Since you've got backups I would just restore the backup of the T-Mobile ROM, flash the boot.img which is in the nandroid backup folder, then (if he's wanting it completely stock), flash the stock recovery and lock the bootloader again.
Alternatively, if you can find a T-Mobile RUU you can just lock the bootloader then run the RUU to write everything back to stock, but it seems a waste of time downloading a full RUU when you've got a backup of the software you want already sitting there.
Hey thanks, will give that a try..cheers
I flashed the original backup from April in recovery and it just hangs at a white screen on reboot.
monkeyphonix said:
I flashed the original backup from April in recovery and it just hangs at a white screen on reboot.
Click to expand...
Click to collapse
Did you flash the boot.img via fastboot as well?
Does that have to be done on my pc ? I just flashed the boot.img then the actual backup. Via the phone
Unless you're s-off you can't write to the boot partition from recovery, so you need to do it from your computer using fastboot. Exactly the same as when you're flashing a ROM.
I never used a pc for anything to get it to the Leedroid...I'll have to look for a guide to do what you said. Apart from when I did the HTC Dev unlock thing.
Thanks for your help.
monkeyphonix said:
I never used a pc for anything to get it to the Leedroid...I'll have to look for a guide to do what you said. Apart from when I did the HTC Dev unlock thing.
Thanks for your help.
Click to expand...
Click to collapse
Interesting; I'm impressed your ROM's been working, seeing as you've seemingly been using the stock 1.26 boot.img with the 1.29 ROM.
Anyway, it's a similar (red identical) process to the one you used to unlock the bootloader. Assuming you've still got the fastboot executable on your PC from when you unlocked, and a copy of the boot.img from the backup you're trying to restore:
1) copy boot.img into the same folder as the fastboot binary
2) turn your phone on in fastboot mode (turn it off, hold vol-down and power on and it should boot into bootloader; select 'fastboot' from the menu if it doesn't automatically load into fastboot mode)
3) connect the phone to the PC via USB (the text on the phone should now say "fastboot USB")
4) on your PC open a command prompt and navigte to the folder containing your boot.img and the fastboot binary
5) run the following command: fastboot flash boot boot.img
6) run the following command: fastboot erase cache
7) run the following command: fastboot reboot
I've just reverted back to stock recovery instead of the original boot for some reason, been at a wedding and am a bit very drunk still, so I really need to get the stock boot.img file from somewhere don't I.
Edit, I found it in clockwork folder by connecting to pc and it is 8mb from April.
I did what you said and it all worked, great thanks. I am now back on stock boot.img abd back to tmobile 1.26....but still with the clockwork recovery and still rooted.
I know how to revert back to the stock recovery as I just did it by mistake...should I be d-rooting it or whatever you call it...and will I have wiped out my sim unlock I paid for ?
Also it is offering me an update of 28 or so mb, is this safe to install ? I am on 1.26 right now. Or do I want to get rid of clockworkd and revert to stock recovery first ?
The 28mb update will be the 1.28 update; you would need to restore the stock recovery and lock the bootloader again to install that (it will just download and fail if you try to install it now).
If the person you're selling it to wants it completely back to stock, then flash your stock recovery, then go back into fastboot (same process as before) and use the command fastboot oem lock to lock the bootloader again. Then accept the update and it'll be back to stock and updated to 1.28.
No idea about SIM-unlocks, sorry. I imagine it would still hold (otherwise everyone who's flashing ROMs, updates or backups would need to keep re-doing it), but I'm honestly just guessing at this point so don't take any of that as anything conclusive.
Ok I did all that and relocked it just about to do the update. Thanks very much for your help.
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?
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!