Related
Hi Gentlemen,
I am new to rooting Androind phones since been using iphone all this years. Right now, I think my HTC One X is bricked. This is what I've done to cause it in this situation:
1) After installing Clockwork Recovery and Super SU. I installed the super wipe.
2) Run super wipe and proceeded to install Android Revolution ROM but the installation was unsuccessful. Not much reason was stated. So I proceeded to reboot the phone and now it just hang at the splash screen.
I've done alot of read up and research the forum how to unbrick my phone but I'm clueless and don't know what to do anymore. I can still get to bootloader screen and that's the furthest I can go.
Pleasse help me.
try to install a stock rom: http://forum.xda-developers.com/showthread.php?t=1546970
Did u do a backup first? Iff not
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Mod or Die
snowwhite007 said:
Did u do a backup first? Iff not
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Mod or Die
Click to expand...
Click to collapse
After doing step 2, I receive this respond:
... INFOLock successfully...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Is it something wrong?
amigo_s said:
try to install a stock rom: http://forum.xda-developers.com/showthread.php?t=1546970
Click to expand...
Click to collapse
I did try doing that but this error pops out:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Pls help me
I take it you did the right thing and made sure you have the right RUU for your phone before you attempted to root?
Hmmm managed to get myself stuck in the same situation here a well as wouldnt go back into recovery. Have relocked bootloader but whn I try to reflash RUU it wont recognise the phone even though it shows in device manager correctly and I can control via fastboot commands but doesnt show when using adb devices.
Any ideas whey RUU cant see the phone?
it defo the correct Ruu?
Mod or Die
Hi.My problem is when I want flash stock terminal give something like that sending 'recovery' (5786 KB)... FAILED (remote: (00120000))
whats the problem?
ps1
right now its
sending 'recovery' (5786 KB)... OKAY
writing 'recovery'... FAILED (remote: battery low)
MacBook-Pro-xxx:fastboot xxx$
when i try to charge phone automaticlly starts
snowwhite007 said:
it defo the correct Ruu?
Mod or Die
Click to expand...
Click to collapse
I presume so as is EUROPE RUU of which I can only find 2, hav the other one downloading currently, but the dialogue it comes up with says about no connection via USB and surely even the incorrect RUU would dectect the phone but fail on authentication wouldn't it?
snowwhite007 said:
Did u do a backup first? Iff not
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Mod or Die
Click to expand...
Click to collapse
sounds awfully familiar... http://forum.xda-developers.com/showpost.php?p=24775692&postcount=3 lol
Remember to Flash Stock Recovery before relocking your bootloader.
wen you are done whit that enter bootloader and press Fastboot then run the RUU file...
DaDoctor!
ya i was one of the first to say that lol but i dont care anymore hehe im just trying to help ppl but sometimes ill get wen seeing ppl posting that exact same thing you have done to alot of pll
Managed to get the RUU to recognise my phone, needed HTC Sync installed even though everything else was working ok without, but although I can now flash RUU's I get a customer number error which I guess Im getting as my phone was a branded T-Mobile one.
Therefore am I correct in saying that unless I can get RUU 1.26.110.5, which is the RUU I need, or get recovery working again by some mircale then Im screwed and now have a rather expensive paper weight?
I manage to boot to cwm recovery. And now the question is, how can I transfer the stock rom or the android revo hd rom to my sdcard from fastboot since i cant boot up my phone cos it stuck at the flash screen. Since I had done the superwipe before all this and now its empty.
Thanks for all the tips given so far.
I FOUND THE SOLUTION !!!!!!!!!!!!!
First Sorry for my French !
So, flash stock recovery first, lock the recovery.
Go to fastboot, and click on the Power Off, screen goes black and the phone is OFF.
Put the charger and the usb on the phone, WAIT 1 or 2hours, led still red, DON'T POWER ON !
When is done, go fastboot, launch RUU, IT'S DONE, battery is good !
Works for me
Swannsin said:
I manage to boot to cwm recovery. And now the question is, how can I transfer the stock rom or the android revo hd rom to my sdcard from fastboot since i cant boot up my phone cos it stuck at the flash screen. Since I had done the superwipe before all this and now its empty.
Thanks for all the tips given so far.
Click to expand...
Click to collapse
Cool well done for getting back into recovery....how did you manage it? As for getting rom back did you not do a backup of the previous rom before wiping? If not you may be stumped for the time being as USB mount does not work on any of the custom recoveries so far.
I fastboot the boot.img and also flash the CWM recovery. This steps enable me to get back to recovery.
But my mistake was i did not any back up on the previous rom and now i cant do a normal boot up as it will stuck at the htc white screen. So i believe the reason it cant boot up is because there is no rom at all.
So now, the only way i can flash rom from recovery is to send file to my sdcard via fastboot. but i don't know the command needed for it, so I need help with the command. i have with me now is the stock rom and also ARHD rom. but i cant access my sdcard to transfer the file.
I have tried to download the stock RUU but unfortunately it says that my CID is imcompatible. My set is from Singapore and now I will try to download this RUU RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed.exe.
If all else fails, final option is to send back my set to HTC service center and have it repaired and pay the charges
Swannsin said:
I fastboot the boot.img and also flash the CWM recovery. This steps enable me to get back to recovery.
But my mistake was i did not any back up on the previous rom and now i cant do a normal boot up as it will stuck at the htc white screen. So i believe the reason it cant boot up is because there is no rom at all.
So now, the only way i can flash rom from recovery is to send file to my sdcard via fastboot. but i don't know the command needed for it, so I need help with the command. i have with me now is the stock rom and also ARHD rom. but i cant access my sdcard to transfer the file.
I have tried to download the stock RUU but unfortunately it says that my CID is imcompatible. My set is from Singapore and now I will try to download this RUU RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed.exe.
If all else fails, final option is to send back my set to HTC service center and have it repaired and pay the charges
Click to expand...
Click to collapse
Ok managed to get mine booting back into CWM Recovery as well now but dont think about sending back to HTC as the CWM guys are working on USB Mount & ADB as we speak so dont think it will be to long. Ill look into fatboot commands now and see if there isnt soemthing we can use.
There's always a way..........
DaDoctor said:
sounds awfully familiar... http://forum.xda-developers.com/showpost.php?p=24775692&postcount=3 lol
Click to expand...
Click to collapse
Yeah shud have a sticky ull notice the other 6 ppl that i copy pasted for i quoted ure username aha i really wonder why ppl want to flash stuff without fuly charging and then having audacity to not backup ahha
Mod or Die
snowwhite007 said:
Yeah shud have a sticky ull notice the other 6 ppl that i copy pasted for i quoted ure username aha i really wonder why ppl want to flash stuff without fuly charging and then having audacity to not backup ahha
Mod or Die
Click to expand...
Click to collapse
Backups are only half of the story. When you cant get into recovery to restore the backups that you HAD made and then when trying to reflash the RUU to resotre your phone it then wipes the backups but then allows you back into recovery where you now have no backups nor the ability to mount USB or push anything to the SD so and still in the same siutation just with nice blue writing now thats just plain sods law......LOL!
---------- Post added at 09:24 PM ---------- Previous post was at 09:16 PM ----------
Swannsin said:
I fastboot the boot.img and also flash the CWM recovery. This steps enable me to get back to recovery.
But my mistake was i did not any back up on the previous rom and now i cant do a normal boot up as it will stuck at the htc white screen. So i believe the reason it cant boot up is because there is no rom at all.
So now, the only way i can flash rom from recovery is to send file to my sdcard via fastboot. but i don't know the command needed for it, so I need help with the command. i have with me now is the stock rom and also ARHD rom. but i cant access my sdcard to transfer the file.
I have tried to download the stock RUU but unfortunately it says that my CID is imcompatible. My set is from Singapore and now I will try to download this RUU RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed.exe.
If all else fails, final option is to send back my set to HTC service center and have it repaired and pay the charges
Click to expand...
Click to collapse
Think we are fairly screwed until either USB/ADB is working in recovery or S-Off is available in which case any RUU should work I believe. Worth hanging on rather than paying HTC in my opinion.
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.
Hi
I recently tried to update a stock handset from 3 to the Android Revolution HD 18.2 ROM, but have failed and now cant get it to boot at all.
I have CID: H3G__001 and HBOOT 1.12, i think i may have jumped the gun and not updated my hboot but could be wrong.
I am using a mixture of Hasoon2000 v2.3 tools and some adb commands found while searching for solutions, but nothing i try seems to restore it.
When i first rooted / unlocked it, i installed TWRP 2.4.1.0 from Hasoon's tool, and did a backup.
I have tried restoring from this backup but all i get is stuck at the 3 logo, rather than the HTC one.
I tried to re-lock the bootloader and reboot, clear all the cache but still nothing....
I have spent hours now searching for possible solutions before finally calling out for help, as i think i am now likely to do more damage than good.
I even tried to download a full backup from Matt's collection http://forum.xda-developers.com/showthread.php?t=1975140 but this failed to install
HELP !!!! Phone is now dead
Hi.
You need to update your hboot in order to flash ARHD 18.x.
Your backup failed to boot because you didn't flash the boot.img of it. Get the boot.img at /sdcard/TWRP/ and flash it.
TToivanen,
Thanks for such a fast response.
I have tried searching for the correct files to use to update my hboot, but the list from http://forum.xda-developers.com/showthread.php?t=2153777&highlight=hboot just confuses me as i cant seem to work out the correct one to use (if any).
Do you know where i could get the right hboot for my cid ?
If i update the hboot and re-flash the ARHD 18.x. - if this fails again, will i still be able to recover to stock using TWRP recovery and your method of locating the boot.img from the sdcard/TWRP ?
Many thanks, its just i have been going round in circles for ages and gave my other phone to a friend so now desperate to get back up and running again.
I think you have more succes in this thread
http://forum.xda-developers.com/showthread.php?t=1927048
And yes you can always return to a backup or another rom ....
Oké so download the firmware.zip from the link above and do these fastboot commands. Note that you will need the original Unlock_code.bin because this method involves locking and reunlocking the bootloader. Search for it in your email inbox.
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip (do two or three times if it fails)
fastboot flash unlocktoken Unlock_code.bin
fastboot flash recovery openrecovery-twrp-xxxx.img
Thanks all, managed to un-brick it, now time to play and see what it can do.
Updated hboot by following the instructions http://forum.xda-developers.com/showthread.php?t=1927048
Then went back to install the Android Revolution HD 18.2 ROM and boot.img and all working again.
Not sure if its the best ROM for this device but i thought its a reasonable place to start. Going to install Titanium backup first and also do a full nand backup just in case something goes wrong, or i feel brave enough to try a different ROM.
Thanks again.
You're welcome!
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!