Related
Hi guys, i'm very new in custom ROMs and all this exciting stuff - exactly i'm a noob.
so, i got my HTC Desire HD from the repair back and want to have MIUI on it.
first, i had to unlocked my bootloader via htcdev, which worked perfectly without any problems.
then i put ClockworkMod as recovery on it, and tried to upload the MIUI image via adb on the SD Card.
but when i try to select one point in cwmod it does nothing.
i know that i have to navigate with the volume buttons and have to select with power button, but that doesn't work, and i don't know why...
maybe anyone has an idea... i have none.
Phone: HTC Desire HD
OS: Android 2.3.5 with Sense 3.0 (already unlocked the bootloader)
ps. excuse my bad english
I'm not sure why that isn't working, but you can also control CWM with the hardware touch buttons at the bottom of your screen. I think it's "Home" for up, "Menu" for down, "Back" for back, and "Search" for select.
preacher65 said:
I'm not sure why that isn't working, but you can also control CWM with the hardware touch buttons at the bottom of your screen. I think it's "Home" for up, "Menu" for down, "Back" for back, and "Search" for select.
Click to expand...
Click to collapse
Thank you.
But i tried them also, and the CWMod logo just gets more opacity and the menu fades out.. nothin more happens.
can i also install MIUI via adb? without navigating through CWMod?
Hmm, sounds odd, I'm not sure why CWM isn't working. How did you install it?
I've never tried flashing a ROM via adb, it depends on whether you can issue CWM commands via adb shell. A quick Google suggests that works for some recoveries, but I wouldn't know for sure.
I've seen a few posts about people having trouble after unlocking with the official HTC tool. It doesn't unlock security to the same extent as the S-OFF methods. I've not tried it myself, did it say anything about allowing you to re-lock the phone? If you can, it might be better to re-lock then try the Advanced Hack Kit method... although again, I'm not 100% sure how that would work and it might be worth asking for advice in the AAHK IRC channel before starting.
again, thank you!
i tried some older versions of cwmod, but they don't even start... the htc logo just fades out, and the display light is on, but nothin else.
is it the right way to just flash a recovery or do i have to uninstall it correctly?
oh and btw.. i installed it via fastboot flash recovery xyz.img
oh i got it
//edit http://forum.xda-developers.com/showthread.php?t=1118865
this one works!
I can assume you have done it but it doesnt cost asking:
Cant you use the power(select) button in any options on Clockwork or just the option to flash it from SD?
My suggestion is to try to take it back to stock recovery and then rooting it in the old fashion way. As preacher said many people coming from the HTC unlocked bootloader are having problems.
I will comeback here as soon as I have a better answer for your problem but for now try to go all the way back to stock!
oh i guess i made obviously a dumb mistake.
i flashed with miui and miui doesn't start and guess what i forgot?...
the backup. will it work, if i try to flash with an 2.2.1 stock rom?
Yes, should be able to flash a stock ROM. I would try to get a stock ROM back on there and re-lock the bootloader - apparently you can do that from the command line. Then use the Advanced Ace Hack Kit from the Dev forum to unlock it, instead of the HTC method.
The AAHK is at http://forum.xda-developers.com/showthread.php?t=1259821 and if you read the last few pages of the thread, it talks about re-locking the bootloader. The AAHK now detects if your bootloader has been re-locked and will work - but you must re-lock before you use it.
Then you should be able to flash any custom ROM just fine.
Ok here is an update about my problem...
Yesterday i installed cwm and opened the bootloader via HTCDev, HTC SuperTool V3 also said that my device is rooted as i did their rooting-method. So i tried to flash a lightly old version of MIUI because it has shipped languagepacks within.
then i rebooted, and my phone freezes at HTC Logo. Now i tried so much ROMs and even tried to go back to a STOCK Rom, i also tried Super Wipe + Rev HD, which worked neither. now i relocked my bootloader and wanna ask if AAHK is a possibility to rescue my phone?
i don't get any ROM to work... so is it even possible to run aahk?
I started a thread in General here about problems with the HTC unlock:
http://forum.xda-developers.com/showthread.php?t=1456749
There might be some help there.
How did you try to get the stock ROM back on? I would first try flashing an RUU as explained here:
http://forum.xda-developers.com/showpost.php?p=20068991&postcount=5
This will hopefully get a working ROM back on your phone. Then if your bootloader has been re-locked, you should be able to use the AAHK - but remember that you'll need to follow the manual carefully. If the AAHK is successful you're good to go.
i have no real solution for everyone...
but attn1 from aahk rescued my phone like a boss.
he flashed a new recovery, flashed piece of cyanogenmod via cwm, and flashed the boot.img via fastboot - cyanogenmod was running!
then he flashed with RUU and made my phone completely free with aahk.
Hello everyone,
I accidentally flashed using CWM recovery the stock rom and over it the Flexreaper ROM.
Now the problem:
Booting normally: Boot verified failed
Booting recovery: Recovery verified failed
Fastboot: Yes it works, but it's locked, can't flash anything.
ADB is not available.
Any suggestions how to fix this or get a unlocked bootloader again ?
Greetings, sniperfield
sniperfield said:
Hello everyone,
I accidentally flashed using CWM recovery the stock rom and over it the Flexreaper ROM.
Now the problem:
Booting normally: Boot verified failed
Booting recovery: Recovery verified failed
Fastboot: Yes it works, but it's locked, can't flash anything.
ADB is not available.
Any suggestions how to fix this or get a unlocked bootloader again ?
Greetings, sniperfield
Click to expand...
Click to collapse
Sounds like you locked your bootloader while on a modded rom? If that is the case you hosed it, sorry to say. You need access to fast boot or adb to fix it, if you have neither its locked for good.
OK one thing, did you try booting with update.zip and holding volume down + power?
With luck it will install the stock rom so you can start over.
Tapatalked from my Galaxy S II.
pio_masaki said:
Sounds like you locked your bootloader while on a modded rom? If that is the case you hosed it, sorry to say. You need access to fast boot or adb to fix it, if you have neither its locked for good.
OK one thing, did you try booting with update.zip and holding volume down + power?
With luck it will install the stock rom so you can start over.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Yes locked bootloader + modded rom
update.zip doesn't work (how should it with a broken recovery ?)
but i which update.zip you mean exactly ?
Is there any hope with APX-Mode maybe ?
sniperfield said:
Yes locked bootloader + modded rom
update.zip doesn't work (how should it with a broken recovery ?)
but i which update.zip you mean exactly ?
Is there any hope with APX-Mode maybe ?
Click to expand...
Click to collapse
APX mode has so far proven completely useless for us, we don't have the SBK keys for our device.
The update.zip method is, partly, activated BEFORE recovery is, if you watch the bootloader text while booting up holding volume down, you'll see it look for update.zip before moving on to recovery, and TWRP and CWM don't look for it on their own, unless its something extra just on our versions of the those recoveries.
If fastboot DOES work, the only thing I can really suggest is attempt flashing CWM recovery.img, but of course, the bootloader will likely block it. You could also attempt to flash the bootloader blob again, which will accept fastboot oem unlock, but the normal method is through android's system, not fasboot.
...or hell just throw fastboot oem unlock at it anyways. If the bootloader is still the same, just locked, they may just unlock it. If the bootloader was replaced, it won't work either.
Good days;
I also have a tablet brick from yesterday. And I am very angry. Tape-worm the tablet with CWM and for supues the unblocked bootloader. Tape-worm installed this room http: // forum.xda-developers.com/showthread.php? T=1574897 and empece to having problem with CWM, since not me leia the external card SD for what not podia to do backup, or to load a new rom. at the time I put to look and lei, that was a problem probably of compatibility of the card SD or that was returning to realize again everything the process of unfreezing of bootloader. and this way I did it. again this process, which was the same that it uses previously and I me work. Http: // forum.xda-developers.com/showthread.php? T=1557445.
I restart the tablet, and from this moment, have the logo of green maple tree, and a phrase of red color that he says: " recovery verified failed .... " it does not start the tablet, and it does not also leave me to enter the recovery. if I try to enter the recovery this message goes out for me.
Erasing cache before SD update...
SD update cmd: recovery -
update_package=SDCARD:update.zip
Booting kernel recovery image
please, I am driven to despair, have tried flashear with different roms, with distitnas cards mike SD, with formats in fat, fat32 and ntfs. and do not manage to do anything. I have tried to install again everything across the PC, but the PC neither recognizes me the tablet, when I connect it to the PC, even the connection of the usb nor is heard, since this one does not manage to be ignited completely. And I am not going to take her to the SAT to whom receive from me 100 €, , Since for other 100 € mas I buy myself the new nexus. but it gives me great anger, because really I like a heap this tablet and it was going less than two weeks with her. Please, to say to me what should be, if necesitais mas information, to say it to me. Thank you very much
pio_masaki said:
APX mode has so far proven completely useless for us, we don't have the SBK keys for our device.
The update.zip method is, partly, activated BEFORE recovery is, if you watch the bootloader text while booting up holding volume down, you'll see it look for update.zip before moving on to recovery, and TWRP and CWM don't look for it on their own, unless its something extra just on our versions of the those recoveries.
If fastboot DOES work, the only thing I can really suggest is attempt flashing CWM recovery.img, but of course, the bootloader will likely block it. You could also attempt to flash the bootloader blob again, which will accept fastboot oem unlock, but the normal method is through android's system, not fasboot.
...or hell just throw fastboot oem unlock at it anyways. If the bootloader is still the same, just locked, they may just unlock it. If the bootloader was replaced, it won't work either.
Click to expand...
Click to collapse
can you please give me a exact link for a update.zip ? there are so many different versions -.-
yes bootloader blocks recovery.img flash ...
how can i to flash a bootloader blob with locked fastboot ? ;o
tried already fastboot oem unlock, does not work, bootloader seems replaced
and thank you for trying to help me, if it's really bricked, i'm going to buy a nexus tablet 7 ;D
Hi all
Interesting issue that I've searched here and Google for and not getting far, my searching skills may not be the best though as I'm fairly new to this.
My Nexus 7 was working fine, put it on the side, came back and it's turned off. Thinking it's flat I charge it and try to boot it with no success. Pressing the power for a while does get it to turn on but it gets as far as the Google logo and stays there.
I've factory reset it in the recovery and nothing
I've tried to flash the stock image from Google but when unlocking the bootloader it just sticks on "yes" forever and nothing happens.
What can I do at this point?
Cheers
Acksaw said:
Hi all
Interesting issue that I've searched here and Google for and not getting far, my searching skills may not be the best though as I'm fairly new to this.
My Nexus 7 was working fine, put it on the side, came back and it's turned off. Thinking it's flat I charge it and try to boot it with no success. Pressing the power for a while does get it to turn on but it gets as far as the Google logo and stays there.
I've factory reset it in the recovery and nothing
I've tried to flash the stock image from Google but when unlocking the bootloader it just sticks on "yes" forever and nothing happens.
What can I do at this point?
Cheers
Click to expand...
Click to collapse
Have you heard of Wugfresh Tool kit ? (aka Nexus Tool Kit) It is in the development section or you can google it. It is quite famous.
It will do anything actually from drivers to repair a device stuck on google logo. Just make sure you select the correct option.
You will need unlocked bootloader to flash stock images. And to do either of those, you will need drivers!
Install drivers and use it to recover your device. If you still have trouble, quote me back and I will help you to my best of ability.
Look into the forum before posting your questions. There are so many similar problems and you can easily find a solution by reading their questions and their possible solution.
Good Luck!
I'm having issues with my nexus 7 (2013). It will not boot up,it's stuck on Google logo. I am able to put in fastboot mode. I'd like to do a hard reset/wipe but I cannot enter recovery mode; it just goes to the Google logo and doesn't show me the recovery menu. I thought I could try doing it through adb but bootloader is locked. Downloaded WugFresh toolkit but it requires correct build number, which I do not know. I tried different ones but everything fails. AND USB debugging is not enabled, but I cannot do it through my tablet because it won't pass bootloop. I haven't been able to enable it remotely. So, any help with getting this tablet up and awake?! It's not rooted BTW, its running stock 6.0 marshmallow
MGreen1216 said:
... issues with my nexus 7 (2013) ... stuck on Google logo. I am able to put in fastboot mode ... doesn't show me the recovery menu ... bootloader is locked. Downloaded WugFresh toolkit but it requires correct build number, which I do not know. I tried different ones but everything fails. AND USB debugging is not enabled, but I cannot do it through my tablet because it won't pass bootloop. I haven't been able to enable it remotely. So, any help with getting this tablet up and awake?! It's not rooted BTW, its running stock 6.0 marshmallow
Click to expand...
Click to collapse
Interesting, and troubling for you, I'm sure.
-- What do you mean, in fastboot it doesn't show you the recovery menu? If you are into (more properly) bootloader mode, the Recovery option has to be there. Do you mean you just can't select it, or that it won't work when you do select it?
-- Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img".
-- Have you tried unlocking the bootloader via fastboot? Is it possible OEM Unlock is already/still enabled somehow?
-- Also.... Wug's NRT doesn't need the correct verion/build. The last option in the drop-down menu on the NRT is this: << Android *.*.* - Any Build >>
HTH
-- When i go into bootloader/fastboot mode, the option is there for recovery mode along with 'start' and 'power off',etc.. However, when I select it,it just hangs on Google logo and never shows me the Android man and recovery options.
-- Sorry, not sure what you mean by this: "Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img"."
I may need some instructions on how to do this please.
-- I have tried unlocking bootloader via WugFresh and Nexus toolkit and via adb but it hangs on erasing user data and also hangs on 'unlock bootloader's screen (left it for over 12 hrs). I doubt anything is unlocked.
--Yes, I tried the "any build" option and nothing works.
Thank you
I'm open to any suggestions.
MGreen1216 said:
--- not sure what you mean by this: "Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img"."
I may need some instructions on how to do this please.
Click to expand...
Click to collapse
Ah, right. I didn't read closely, and didn't realize you might not have used fastboot tools... and please, I'm no expert, so if I'm saying somthing inaccurate, I very much hope someone will correct me.
I'm never sure how much a poster knows, so I'm not sure if you meant you don't know fastboot commands at all, or just the specific ones I mentioned .. fastboot commands are like ADB commands, but run in the bootloader environment. We know you have fastboot commands installed and fastboot drivers installed on your computer because you have adb installed - which includes fastboot, and you said WugFresh's tool was able to run, which means you also have the right fastboot drivers (the NRT uses the same fastboot commands).
fastboot can be used to flash/install custom recovery packages, among a whole lot of other things. So what I mentioned in that command was a possible way to maybe get into a custom recovery if you have to do things like wipes or whatever, even if you can't actually fully install the custom recovery. You might need to do this stuff, if you can't unlock your bootloader and flash the whole official Google Factory Image from their website (which is what I'd try - simple instructions are right there, too).
Flashing the full factory image will wipe your device, of course, but there are simple ways around that, which you can find on this very forum. Good luck.
Let us know how you get on.
<<< Any device that's bootable at all is recoverable...... usually... >>>
I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?
I had same problem. Follow the steps. Unlock it again and reboot to the system.
There enable developer option, enable debugging, enable unlock bootloader option.
Rebooted to fastboot mode
Install stock recovery
Adb sideload 3.2 full firmware.
After that reboot your phone to fastboot mode.
Unlock bootloader.
This should do it.
Sent from my ONEPLUS A3003 using Tapatalk
It's like you didn't even read what I wrote...
I said it doesn't boot to system, OnePlus logo appears for a split second and phone turns off.
Bootloader is locked and I cannot flash anything.
ADB Sideload won't read files. Gives the 'cannot read' error.
You know that you can load to bootloader by pressing volume up and power button right?
Sent from my ONEPLUS A3003 using Tapatalk
Monskiller said:
I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?
Click to expand...
Click to collapse
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!
ajaysoranam said:
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!
Click to expand...
Click to collapse
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?
I relocked the bootloader. Which wiped to factory reset.
That wipe deactivated the ability to unlock bootloader until reactivated from the system, which I cannot get to because the phone turns off/bootlops before loading it.
This happened quite a few times on this forum, there is really no reason to relock the bootloader on the op3, it is covered through warranty, but u will have to contact oneplus and they should walk u through and send u files to unbrick it if u r lucky
ovidiu1982 said:
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?
Click to expand...
Click to collapse
then you better get in touch with the op customer service. they will, from what i know, fix it thru a remote connection sitting.
I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.
karthikrr said:
I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.
Click to expand...
Click to collapse
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.
Bro don't worry now.
I am gonna guide you out of this.
First install an adb package like this.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Now get a toolkit like this.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Try to connect to fastboot and check for your device in the toolkit.
If failed then kill process adb in your task manager.
Now once connected.
Check OEM status and bootloader status.
Unlock if required.
Now.
Push twrp to your phone .
Then boot into it through the toolkit.
Now load a full ROM.
http://forum.xda-developers.com/oneplus-3/development/rom-op3lite-debloated-tweaked-fast-t3404996
Just copy paste it using your file manager on PC.
Them flash first make it boot and then root.
Hope this helped.
Monskiller said:
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.
Click to expand...
Click to collapse
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out
karthikrr said:
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out
Click to expand...
Click to collapse
Don't test it. I've already done it by mistake.
It replaced recovery with TWRP by allowing the modification of system and even after reflashing stock it'll bootloop on relocking recovery.
So I found something useful then.
Hey, i think i found a solution for you. I don't know if i can post here xda thread links, so search "EDL Mode xda" on Google and the first link it is. Hope i helped
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?