tried to get OTA 5.0.1 today. woudn't take. I have (had)rooted,s-off,bootloader unlocked. Now i somehow wiped everything off.No OS, no recovery. No idea how to begin again. Screen is on white with HTC logo and Powered by android showing. won't power down. Any ideas?
Try holding volume up with power button down for ten seconds.
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
Are you sure you wiped everything, or are you just assuming this based on the screen you are seeing?
update
ok, i held power up/power for 20 seconds, then power down/power and got into twrp recovery. there is NOTHING else on the phone. No OS at all. what's the best way to proceed? PC wont pickup device,so adb cmd prompt isn't working. thanks
stlsports said:
ok, i held power up/power for 20 seconds, then power down/power and got into twrp recovery. there is NOTHING else on the phone. No OS at all. what's the best way to proceed? PC wont pickup device,so adb cmd prompt isn't working. thanks
Click to expand...
Click to collapse
What I would do is pop out my MicsoSD card, back everything up on it then download my original OS I WAS running before I blew it up onto the SD card and attempt to flash it. From there I'd hit up this thread http://forum.xda-developers.com/showthread.php?t=2714456 to see if I could glean how to return back to stock. I'm sure someone will yell at me if you shouldn't do it, not that am I saying you should do that, I'm just saying what I'd do.
i was able to get lollipop dream on my sd card and flash it. WHEW! but, i really want stock rooted lollipop. i actually enjoy sense 6.0 a little bit. gonna keep at it..
thanks.
Theoriginalgiga said:
What I would do is pop out my MicsoSD card, back everything up on it then download my original OS I WAS running before I blew it up onto the SD card and attempt to flash it. From there I'd hit up this thread http://forum.xda-developers.com/showthread.php?t=2714456 to see if I could glean how to return back to stock. I'm sure someone will yell at me if you shouldn't do it, not that am I saying you should do that, I'm just saying what I'd do.
Click to expand...
Click to collapse
stlsports said:
i was able to get lollipop dream on my sd card and flash it. WHEW! but, i really want stock rooted lollipop. i actually enjoy sense 6.0 a little bit. gonna keep at it..
thanks.
Click to expand...
Click to collapse
Well now that you're up and running, you can go through the process of flashing the old stock rom (not the lollipop rom), unroot and restore the stock BL, then take the OTA update and I believe you should be able to reroot if you wanted to.
Theoriginalgiga said:
Well now that you're up and running, you can go through the process of flashing the old stock rom (not the lollipop rom), unroot and restore the stock BL, then take the OTA update and I believe you should be able to reroot if you wanted to.
Click to expand...
Click to collapse
couldn't he just flash the most current RUU?
deepsouth06 said:
couldn't he just flash the most current RUU?
Click to expand...
Click to collapse
Maybe, I'm not sure. I was able to because I was coming from just the stock rom rooted with xposed on it I know that at the least BL needs to be stock and match the version of stock ROM you nandroided back on. If you're using RUU I don't think unrooting is important. Whether or not you have to lock the BL I'm not aware of myself but it's an easy process. Below is what I did.
Being on a rooted stock ROM running xposed I downloaded drivers, BL that matched my ROM, ADB/fastboot current RUU I was on and latest RUU.
I was on 4.4.4, I verified the version of my ROM and got the matching BL. I've heard rumors that mismatching BL/ROM will cause an error.
FIRST I booted into my custom recovery and did a back up. Better safe than sorry right?
booted into fastboot and installed the recovery using fastboot flash recovery {recoveryname}.img
locked BL using "fastboot oem lock" rebooted my phone into the OS then fired up the latest[/B ]RUU and let it run and it ran just fine.
I then unlocked my BL again and installed the latest version of TWRP, reinstalled root and my apps. phone runs really well. I need to start going through and freezing apps but hey we skip those things at 2am don't we?
Mind you I have S-off on my phone and I didn't mess with S-off at all.
I would surmise that if you're experiencing getting the latest RUU to install that you might want to make sure your BL and rom number match and if that doesn't work try flashing the RUU that you're currently running and then the latest RUU.
I consulted this list to verify my version I was running, I happened to be running at the time 3.32.531.2 so I hunted for that BL.
https://support.t-mobile.com/docs/DOC-10366
Related
Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.
Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
clown6198 said:
Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.
Click to expand...
Click to collapse
stathis95194 said:
Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
Click to expand...
Click to collapse
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.
clown6198 said:
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.
Click to expand...
Click to collapse
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices
Yet another user stuck because they followed a tutorial or video guide, instead of taking the time to learn, read, and really understand the steps and concepts. This is exactly why I discourage such tutorials or YouTube guides (and Toolkits as well), as they leave you completely unequipped to recover if you have a problem, leaving your buddies at XDA to clean up the mess.
YouTube video or not, you shouldn't be doing anything you don't understand, and you shouldn't be wiping anything if you don't understand what the result will be.
You will need to troubleshoot the USB connectivity issue first. From there, unlock the bootloader again, install custom recovery and flash a ROM (as stathis95194 has already stated).
stathis95194 said:
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices
Click to expand...
Click to collapse
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept
clown6198 said:
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept
Click to expand...
Click to collapse
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.
redpoint73 said:
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.
Click to expand...
Click to collapse
will this work even with the S-ON?
clown6198 said:
will this work even with the S-ON?
Click to expand...
Click to collapse
Of course. I wouldn't be telling you to do it, otherwise.
redpoint73 said:
Of course. I wouldn't be telling you to do it, otherwise.
Click to expand...
Click to collapse
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Honestly, I would just install Philz recovery instead of TWRP and try to either install the ROM zip directly (after a full wipe), or sideload the ROM zip from your PC.
clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time. Find a ROM for your device that is based off of the 1.x firmware and download that. To get your device out of the bootloop and back into boot loader/recovery, hold power and volume up for quite some time until the screen shuts off. Then, hold power down while the screen is black and you'll be in the boot loader. From there you can use the arrow keys to select recovery. Of it isn't there, first select fastboot or hboot and look for it there. You should be in recovery, now you can go ahead and push the file to your phone. Ensuring it is a sense ROM based off of the 1.x firmware, go to wipe and do the standard swipe to wipe (will erase app data not pictures or downloads), then go into install and select your ROM and swipe. Be patient while your device turns on for the initial boot, it might take a while but your phone should be functional after that.
wtoj34 said:
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time.
Click to expand...
Click to collapse
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
Hi so Im in TWRP. I pushed a ROM called Android_Revolution_HD-One_M8_11.1 which is supposedly the closest rom to a stock one. I tried flashing the ROM many times, Im in the process of flashing it again after whiping like you said. The result is the same. After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Thanks,
clown6198
clown6198 said:
After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Click to expand...
Click to collapse
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.
redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
redpoint73 said:
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.
Click to expand...
Click to collapse
ahahaha THANK you so much!!!! I got the phone to work but now the problem is, I cant get the sound to work when Im playing music. I installed the harman kardon software and I cant get the music to work at all
clown6198 said:
I installed the harman kardon software and I cant get the music to work at all
Click to expand...
Click to collapse
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?
redpoint73 said:
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?
Click to expand...
Click to collapse
Damn. Apparently I need to get s-off in order for the harman kardon to work. Just need to uninstall harman kardon now... But yea sorry all I needed was to flash the rom. I didn't know the booting was going to take 5 mins and over. I thought that I was just stuck on the HTC logo. all I needed was to be patient ahaha Thanks a lot guys
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
MrDelicious said:
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
Click to expand...
Click to collapse
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
Click to expand...
Click to collapse
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
Click to expand...
Click to collapse
Thanks! I shall look into this.
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
iSike said:
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
Click to expand...
Click to collapse
Open SuperSU->Settings->Unroot?
j to the 4n said:
Open SuperSU->Settings->Unroot?
Click to expand...
Click to collapse
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
iSike said:
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
Click to expand...
Click to collapse
When I unrooted using SuperSu it ruined my installation also. I was stuck in a bootloop until I installed TWRP and reinstalled SuperSu, terrible!!! It eventually unrooted and I relocked bootloader but nothing worked so I was forced to root and unlock bootloader again.
I am wondering though, how did you return to stock? I really want the latest AT&T stock but when I install that RUU .exe it gives me error 155 so I can't install it. I was using 1.32 stock AT&T and wanted to install 2.6 (I think that's what it is, it's Android 5.1).
I am S-On, and not S-off, could that be an issue? Bootloader is unlocked and I am rooted now.
You know how u r supposed to rename the ruu u want to flash (assuming you downloaded the stock ruu for your carrier and device). The problem for me was, I could never connect my device thought adb after I rooted it (fast boot worked when I put it in fastboot). Even when I could give a command , it could never load the ruu. So what I did, was right click the ruu and click run as admin. It should open up a page on the top saying something about a ruu/rom utility. Make sure you device is connected and had usb debugging( before you got stuck in the loop hopefully). Now click accept and all that good stuff on the utility, it should scan your phone and show u your current rom image, and then show you the latest rom image. Click update and it will boot your phone to boot loader and begin sending it to your phone. IMPORTANT: DO NOT TOUCH YOUR PHONE. Now here's the catch, if it said it failed or something about a USB error, close the program and start it up again. If your phone is stuck without the download bar moving(displayed on your phone), you are going to have to hard reset it. Google how to do it for your device (just a button holding combination). And start the program again. It will take a couple times for the program to work (mine took about 5-6 times). But it will work sooner or later. I am not home atm, but when I get home, I will find the link to the page where this info is displayed in a more orderly fashion and with pictures. It will be tonight, probably about 9 hours. Try this though, if it is too confusing, wait till I post the link. Good Luck!!
EDIT: Sorry just got back home from a long day haha, I'll be sure to look for the link tomorrow. But my directions above should be good, give it a try.
Hi all,
My m8 is rooted, with CWM. I was having issues with it, so I decided to wipe it and flash the marshmallow GPE update to see if that would help (since my OTA alert was there). However, it's now stuck in a bootloop, and I can't get into recovery, or get a computer to recognize it.
If I hold the power and volume buttons down, it will restart, I can get the white screen with HTC logo and red writing stating the build is for development purposes only, but after that it goes right to the loading screen again, instead of going into recovery like it normally would (and like it's done a thousand times for me in the past). I'm not the techiest person, but I thought I'd done enough research on this to do it properly.. apparently not I've tried everything I (and google) can think of, but everything seems to rely on getting to recovery to flash a new rom/wipe the cache/etc or hooking it up to a computer, neither of which I can do. Do I have any other options? This is a "new" phone (bought it refurbished from tmobile to replace my old m8 which I also had issues with... obviously a bad choice), and the thought of buying a new phone again just really kills me. Any help would be SO greatly appreciated. Thanks!
butneveragain said:
Hi all,
My m8 is rooted, with CWM. I was having issues with it, so I decided to wipe it and flash the marshmallow GPE update to see if that would help (since my OTA alert was there). However, it's now stuck in a bootloop, and I can't get into recovery, or get a computer to recognize it.
If I hold the power and volume buttons down, it will restart, I can get the white screen with HTC logo and red writing stating the build is for development purposes only, but after that it goes right to the loading screen again, instead of going into recovery like it normally would (and like it's done a thousand times for me in the past). I'm not the techiest person, but I thought I'd done enough research on this to do it properly.. apparently not I've tried everything I (and google) can think of, but everything seems to rely on getting to recovery to flash a new rom/wipe the cache/etc or hooking it up to a computer, neither of which I can do. Do I have any other options? This is a "new" phone (bought it refurbished from tmobile to replace my old m8 which I also had issues with... obviously a bad choice), and the thought of buying a new phone again just really kills me. Any help would be SO greatly appreciated. Thanks!
Click to expand...
Click to collapse
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!
xunholyx said:
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!
Click to expand...
Click to collapse
You are a lifesaver! Didn't even think about trying to switch from volume up to down, but that did it.
Ok, so now I have TWRP, but my OS was definitely NOT 6 (it was 4.something). I assume that was one of my issues? Honestly, at this point, I just want to go back to stock lollipop, like I had before.. I bounced around a few stock marshmallow roms before my bootloop (realized I hated GPE, that HTC transfer didn't support my device on those versions, CWM wouldn't restore any of my backups--which now makes sense, etc), so I think I just want to quit messing with it at this point and count my blessings. I've had issues finding stock roms though, obviously. Could you point me in the right direction? I just want stock tmobile lollipop, with sense. I didn't think it'd be so difficult, but I'm clearly not very up-to-date on this stuff. Thanks SO much again!
butneveragain said:
You are a lifesaver! Didn't even think about trying to switch from volume up to down, but that did it.
Ok, so now I have TWRP, but my OS was definitely NOT 6 (it was 4.something). I assume that was one of my issues? Honestly, at this point, I just want to go back to stock lollipop, like I had before.. I bounced around a few stock marshmallow roms before my bootloop (realized I hated GPE, that HTC transfer didn't support my device on those versions, CWM wouldn't restore any of my backups--which now makes sense, etc), so I think I just want to quit messing with it at this point and count my blessings. I've had issues finding stock roms though, obviously. Could you point me in the right direction? I just want stock tmobile lollipop, with sense. I didn't think it'd be so difficult, but I'm clearly not very up-to-date on this stuff. Thanks SO much again!
Click to expand...
Click to collapse
Okay. 4.xx firmware will actually work with 6.xx ROMs, but I'll instruct you on getting back to stock lollipop.
Backup anything important to you, such as photos and stuff, because this is going to wipe your phone. Don't worry about the apps. Google takes care of that for you. You might lose a little data from the apps, but if you want to be completely stock, this will do it. (you will probably get a prompt to update to Marshmallow via OTA eventually afterwards, but it will be the official stock version of it)
Also, this is assuming that you are T-Mo US, not a European T-Mo version.
Download this RUU onto your PC.
When the download if finished, hook up your phone and get into fastboot. You'll have to re-lock your bootloader first. The command is fastboot oem lock, then fastboot reboot
After you have re-locked your bootloader, double click on the RUU download and follow the prompts.
If there are problems with the RUU flash, try again while booted to bootloader. Sometimes that is needed for some reason.
That's it. You are now on stock T-MoUS 4.20.531.4
Good luck!
xunholyx said:
Okay. 4.xx firmware will actually work with 6.xx ROMs, but I'll instruct you on getting back to stock lollipop.
Backup anything important to you, such as photos and stuff, because this is going to wipe your phone. Don't worry about the apps. Google takes care of that for you. You might lose a little data from the apps, but if you want to be completely stock, this will do it. (you will probably get a prompt to update to Marshmallow via OTA eventually afterwards, but it will be the official stock version of it)
Also, this is assuming that you are T-Mo US, not a European T-Mo version.
Download this RUU onto your PC.
When the download if finished, hook up your phone and get into fastboot. You'll have to re-lock your bootloader first. The command is fastboot oem lock, then fastboot reboot
After you have re-locked your bootloader, double click on the RUU download and follow the prompts.
If there are problems with the RUU flash, try again while booted to bootloader. Sometimes that is needed for some reason.
That's it. You are now on stock T-MoUS 4.20.531.4
Good luck!
Click to expand...
Click to collapse
Thanks so much. I still have everything backed up from before (well, my CWM nandroid is useless now, but I'll live). I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them. I'm S-ON--is that a problem?
butneveragain said:
Thanks so much. I still have everything backed up from before (well, my CWM nandroid is useless now, but I'll live). I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them. I'm S-ON--is that a problem?
Click to expand...
Click to collapse
No it's not a problem, and something that I have already assumed.
If you were S-Off, you wouldn't need to re-lock your bootloader before running the RUU.exe
Those "some people who were saying" are incorrect.
butneveragain said:
I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them.
Click to expand...
Click to collapse
Yeah, people need to stop saying that. Its completely false. RUU is an official HTC recovery tool, and its intended to work on stock (s-on) devices.
You only need s-off to flash RUU as unintended by HTC, such as:
- flash an older version RUU than what is on the phone ("downgrade")
- Change CID/MID to flash another version's RUU
- Flash RUU with unlocked bootloader
- Flash a hacked/unsigned RUU
xunholyx said:
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!
Click to expand...
Click to collapse
My phone is stuck on boot screen... How can I turn off the device if my vol+ button does not work?
Hello,
just like i wrote in the title. My HTC 10 stucks on htc logo and repeats trying to boot. But i cant do nothing like to go in download mode or recovery so im unable to flash or give adb commands. Are they any workarounds with or without jtag or something else. Vol down+ Power button combination makes no difference.
I dont know why but it happened when i tried to lock the bootloader with fastboot.
here i upload a video to show you whats going on
youtu.be /CmyQiQpdHco
My device is S-on cid 034
When it boots... Hold volume down and power button at same time,may take you a couple tries,will get you into download mode...bricked isn't term for that... Stuck in bootloop...
Sephiroth43 said:
Hello,
just like i wrote in the title. My HTC 10 stucks on htc logo and repeats trying to boot. But i cant do nothing like to go in download mode or recovery so im unable to flash or give adb commands. Are they any workarounds with or without jtag or something else. Vol down+ Power button combination makes no difference.
I dont know why but it happened when i tried to lock the bootloader with fastboot.
here i upload a video to show you whats going on
youtu.be /CmyQiQpdHco
My device is S-on cid 034
Click to expand...
Click to collapse
Try holding just the volume down button while it's rebooting like that and see if you can get to bootloader.
If not, you may have to wait until it drains itself.
Then once it's dead and done looping, plug into a wall charger.
After its been plugged in for 10-15 minutes, charging in off mode hopefully:
Press and firmly hold down on the volume down key, while holding it down, push one time on the power button.
Do not hold the Power button, but continue holding volume down while device powers on, it should hopefully then go to bootloader.
If you get to that point, you should be able to recover the device.
You can come ask for further help, unless you already know what to do from there...
edit: looks like Wonders beat me to it [emoji14]
Sent from my HTC6545LVW using Tapatalk
Thank you both for the fast reply.
Im now on download mode and trying to flash ruu.
Welcome...??
Hello again,
i did a mistake and cant find a solution for it. Somehow a managed to flash the recovery 3.617xxx but i then realised that i needed a stock recovery of 3.6xx401 because of my Phone CID 034. If i want to start the ota oreo update from stock rec. i get that my phone is pmewl but the ota data pmeuhl so therefore it refuses to flash the ota update. Now can i just flash an older correct stock rec over my currently stock rec which have a higher number ( 3x617xxx) and is obviously not for my cid?
Sephiroth43 said:
Hello again,
i did a mistake and cant find a solution for it. Somehow a managed to flash the recovery 3.617xxx but i then realised that i needed a stock recovery of 3.6xx401 because of my Phone CID 034. If i want to start the ota oreo update from stock rec. i get that my phone is pmewl but the ota data pmeuhl so therefore it refuses to flash the ota update. Now can i just flash an older correct stock rec over my currently stock rec which have a higher number ( 3x617xxx) and is obviously not for my cid?
Click to expand...
Click to collapse
I thought you were going to flash an RUU?
Why didn't that happen?
RUU will place the proper recovery on your phone...and then you're all set for updating.
santod040 said:
I thought you were going to flash an RUU?
Why didn't that happen?
RUU will place the proper recovery on your phone...and then you're all set for updating.
Click to expand...
Click to collapse
Yes, i have but then i wanted to restore my old build with Viper10 5.11 it was successfull too, but every time after the phone boots i received a message in dark blue font that my encrypted files are corrupt i need to factory reset my phone. So of course i did it withut thinking after that i loose the rom so i decided to make RUU again. But i couldnt because i was on a higher firmware 3.16x401x to 2.41.401xx but i managed to flash the right stock recovery but im unable to boot up the phone cuz i cant flash or install any RUU under 3.16xxx401 and this came with the eu ota oreo update. So now i cant install RUU 2.41.401 cuz im on 3.16.401 but there are no RUU with version 3.16.401. Im only booting with PureFusion but there i have no radio and i cant s-off while im still on purefusion because the sunshine app refuses it.
Sephiroth43 said:
Yes, i have but then i wanted to restore my old build with Viper10 5.11 it was successfull too, but every time after the phone boots i received a message in dark blue font that my encrypted files are corrupt i need to factory reset my phone. So of course i did it withut thinking after that i loose the rom so i decided to make RUU again. But i couldnt because i was on a higher firmware 3.16x401x to 2.41.401xx but i managed to flash the right stock recovery but im unable to boot up the phone cuz i cant flash or install any RUU under 3.16xxx401 and this came with the eu ota oreo update. So now i cant install RUU 2.41.401 cuz im on 3.16.401 but there are no RUU with version 3.16.401. Im only booting with PureFusion but there i have no radio and i cant s-off while im still on purefusion because the sunshine app refuses it.
Click to expand...
Click to collapse
So what you are saying, is you are s-on and decided it would be a good idea to update to Oreo firmware, but not Oreo software?
Even though there is an entire thread about how downgrading from Oreo back to Nougat causes loss of radio/baseband...
Not sure I follow the logic here, but that sounds like a whole lot of unnecessary fun that you went through.
If you ARE s-on, you basically have three options at the moment.
One is to go and flash LeeDr0id's Oreo rom.
-OR-
You find and apply a stock system.img and boot.img using Twrp.
-OR-
You use SunShine to gain S-off so that you can revert to Nougat and then apply Oreo or whatever other games you should choose to play.
Best of luck! :good:
Thank you, lately im only making questionable choice , but i didnt see Leedroids Update so im loading it now.
But this was a stressful adventure xD
Have a nice day