Related
Ok... So a couple of days ago, I was having bootloop issues on Ineffabilis 1.3 using the Anthrax kernel. After doing a battery pull, I booted into the bootloader and then to recovery and found that my roommate, while playing with my phone, had flashed the ClockworkMod Recovery, I suppose through the Rom Manager app.
I figured it would be ok to do a full wipe and re-flash the rom since flashing the stock kernel didn't stop the bootlooping and I would just flash AmonRa back when I was done to do a backup.
Well, after doing a factory reset from CWM and getting errors thereafter trying to flash the superwipe and Ineffabilis, I rebooted the phone and skipped through the setup to get to the restart menu to get into the bootloader again to flash AmonRa. I was able to flash it, but now every time I try to get into the recovery whether from the restart menu, ADB, or through the fastboot menu, it automatically restarts the phone as soon as the recovery is loaded and goes back to the OS.
Has anyone experienced this and is there any way to fix it to get back into it?
Sounds like you have a ph image on your sd card. Just delete it and you should be fine
sent from ics land
I've long since removed all PH files from my phone, internal and external sdcard included, and even if there were that's never stopped my from booting directly into recovery from the restart menu or through ADB.
I've even gone as far as removing the external sdcard with the same result. It just boots into recovery and as soon as it loads for that split second, it automatically reboots to the HTC screen and back to Android.
I still have root and my phone isn't bricked. I just can't flash any roms or kernels in the future when we get our official ics update. WTB my EVO 3D's hboot 1.4 back...
Sent from my ADR6425LVW using XDA
ojdidit84 said:
I've long since removed all PH files from my phone, internal and external sdcard included, and even if there were that's never stopped my from booting directly into recovery from the restart menu or through ADB.
I've even gone as far as removing the external sdcard with the same result. It just boots into recovery and as soon as it loads for that split second, it automatically reboots to the HTC screen and back to Android.
I still have root and my phone isn't bricked. I just can't flash any roms or kernels in the future when we get our official ics update. WTB my EVO 3D's hboot 1.4 back...
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
what happens when you try to go to recovery...
i would just reflash a recoveyr in fastboot. cant hurt.
What it does is as soon as it boots to recovery, I see it load the recovery and then as soon as it loads, it's as if the phone automatically selects the reboot option and goes back through the normal boot no matter which method I use to boot into recovery.
I've done the fastboot method which flashed successfully, tried to re-flash clockwork using rom manager, scott's tool, adb & fastboot, also used scott's flash tool which was also successful and it just seems as if recovery mode is borked somehow and using these methods to go back to AmonRa produce the same result. I'm usually good at figuring these things out myself since I've been rooting and flashing since my first Sprint HTC Hero, EVO 4G, 3D, Epic 4G/Touch and I've never had anything like this happen before. Completely stumped .
Have done a search and haven't found anyone with the same issue so I have nothing prior to go off of. The phone works fine for now so I'm in no hurry since I still have root and thankfully Titanium Backup for my apps. Not sure what to try next at this point.
ojdidit84 said:
What it does is as soon as it boots to recovery, I see it load the recovery and then as soon as it loads, it's as if the phone automatically selects the reboot option and goes back through the normal boot no matter which method I use to boot into recovery.
I've done the fastboot method which flashed successfully, tried to re-flash clockwork, also used scott's flash tool which was also successful and it just seems as if recovery mode is borked somehow. I'm usually good at figuring these things out myself since I've been rooting and flashing since my first Sprint HTC Hero, EVO 4G, 3D, Epic 4G/Touch and I've never had anything like this happen before. Completely stumped .
Have done a search and haven't found anyone with the same issue so I have nothing prior to go off of. The phone works fine for now so I'm in no hurry since I still have root and thankfully Titanium Backup for my apps. Not sure what to try next at this point.
Click to expand...
Click to collapse
From hboot, choose factory reset and see if it boots you into recovery. I had a similar issue after running the new RUU, once I chose that it booted into custom recovery and i was able to reboot and then afterwards had no trouble accessing recovery.
mjh68 said:
From hboot, choose factory reset and see if it boots you into recovery. I had a similar issue after running the new RUU, once I chose that it booted into custom recovery and i was able to reboot and then afterwards had no trouble accessing recovery.
Click to expand...
Click to collapse
Ok. I'll give that a whirl in the morning and see if it solves the problem.
Bump... I'm stuck with this issue...
Hi,
Spent the last two days trying everything I could think of to get a custom recovery loaded on my rezound with no luck. Have searched everywhere and short of trying to hex edit some code nothing has worked.
I was on a custom ICS rom and applied the 4.03.605.2 RUU (hboot 2.27). Was S-ON with unlocked bootloader. I locked the bootloader, installed RUU successfully, unlocked the bootloader with my token. I tried flashing amon-ra, CWM, TWRP many versions of each by fastboot and hboot (PH98IMG). The custom recovery is successfully written in each case, but i can't successfully boot into the recovery partition either from fastboot or hboot menu option. I can write the recovery.img file from the RUU zip, and all is good. Ultimately, I am just trying to install a custom ROM/root my device.
I tried the above advice about performing a factory reset. No Dice. So for now, I am stuck in Verizon bloatware land, and very unhappy about it.
Suggestions welcome. Thanks everyone.
phaedrus43 said:
Hi,
Spent the last two days trying everything I could think of to get a custom recovery loaded on my rezound with no luck. Have searched everywhere and short of trying to hex edit some code nothing has worked.
I was on a custom ICS rom and applied the 4.03.605.2 RUU (hboot 2.27). Was S-ON with unlocked bootloader. I locked the bootloader, installed RUU successfully, unlocked the bootloader with my token. I tried flashing amon-ra, CWM, TWRP many versions of each by fastboot and hboot (PH98IMG). The custom recovery is successfully written in each case, but i can't successfully boot into the recovery partition either from fastboot or hboot menu option. I can write the recovery.img file from the RUU zip, and all is good. Ultimately, I am just trying to install a custom ROM/root my device.
I tried the above advice about performing a factory reset. No Dice. So for now, I am stuck in Verizon bloatware land, and very unhappy about it.
Suggestions welcome. Thanks everyone.
Click to expand...
Click to collapse
Hook up to PC. the phone can actually adb when turned off. or make sure ROM is booted with ADB turned on. It should connect to adb. Does it? Then your command would be "adb reboot recovery" after you have flashed a custom recovery. So what does it do when you try to enter recovery?
Thanks. Did try that, but not with phone off. I'll try both for good measure and let you know. Thank you fly...
Sent from my ADR6425LVW using xda app-developers app
Flyhalf205 said:
Hook up to PC. the phone can actually adb when turned off. or make sure ROM is booted with ADB turned on. It should connect to adb. Does it? Then your command would be "adb reboot recovery" after you have flashed a custom recovery. So what does it do when you try to enter recovery?
Click to expand...
Click to collapse
Hi Fly,
I was unable to get adb to see the phone when it was off with either a custom recovery or the stock recovery. When I rebooted to recovery from adb with a custom recovery installed, it attempts to boot to the recovery partition but fails and boots back to the OS (this is true when using adb, fastboot, and hboot to boot to recovery). When i reinstalled the stock recovery, it successfully boots to recovery using all methods.
i have tried other custom recovery versions, TWRP (preferred), AMON-RA, CWM Recovery...
annoyed.
Thanks Fly. Any other ideas?
phaedrus43 said:
Hi Fly,
I was unable to get adb to see the phone when it was off with either a custom recovery or the stock recovery. When I rebooted to recovery from adb with a custom recovery installed, it attempts to boot to the recovery partition but fails and boots back to the OS (this is true when using adb, fastboot, and hboot to boot to recovery). When i reinstalled the stock recovery, it successfully boots to recovery using all methods.
i have tried other custom recovery versions, TWRP (preferred), AMON-RA, CWM Recovery...
annoyed.
Thanks Fly. Any other ideas?
Click to expand...
Click to collapse
I'm out of ideas. Since your s-on you can't go down to the OTA RUU and try there. Maybe someone else can spread some light.
Well one more idea. Boot your phone into Fastboot. Plug into computer and download a custom recovery to your computer. The command to use is "fastboot boot recovery.img"
If that does work then download http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and flash it inside of recovery. That will give you root inside your stock rom at least.
Flyhalf205 said:
I'm out of ideas. Since your s-on you can't go down to the OTA RUU and try there. Maybe someone else can spread some light.
Well one more idea. Boot your phone into Fastboot. Plug into computer and download a custom recovery to your computer. The command to use is "fastboot boot recovery.img"
If that does work then download http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and flash it inside of recovery. That will give you root inside your stock rom at least.
Click to expand...
Click to collapse
Hi Fly,
Nothing doing. Can't flash the attached in stock recovery, can't boot into any recoveries with stock flashed or with custom recovery flashed. Seems there must be some new security built into the new RUU? I did note one thing. When I first flash the RUU the hboot banner says relocked (as i have to relock to install an RUU). However, as soon as I flash anything to the recovery partition it adds a new white on black banner that says tampered. Now, i have seen that before when I s-off'd my rezound previously (returned to verizon for audio problems). I never did s-off this particular phone. I don't recall my first phone flagging a new recovery or this phone flagging a new recovery on the old firmware (i could be wrong though as i don't spend a lot of time in hboot).
Still hoping to put a custom recovery on this. Any other way to load a custom rom? i really want to run Neo's AOKP, as I had that on here before I RUU'd. In fact, i got into this position because I was going to s-off the phone, but I had a custom rom. I started looking for RUU's to restore to stock because controlbear wouldn't work with custom rom. Instead of installing an early ICS again, i opted to install the latest RUU.
I searched the forums high and low and wasn't really able to find anyone with this problem. I wonder if there is something wrong with the RUU? I checked the MD5sum and it matched. When flashing recovery i checked the mainver too, so it isn't that... I'm stumped.
This phone wasn't real popular and is gettting old now (man, the lifecycle on phones suck, I had my N1 through many roms and AOSP releases! These new phones are gone in 6 months, a year tops). I doubt anyone is going to trouble themselves to crack a new HBOOT on this phone (this is 2.27).
Only other things i can think (and I haven't tried yet) is trying zergRushing it for temp root to at least remove/freeze the bloat like I did with this phone when I first got it. Or if I can just get a rom installed without a custom recovery I don't flash as often as I used to and figure an upgrade isn't long off. Or if i could downgrade the hboot or install jb hboot...
Would love it if someone had something new to try.
Thanks so much again Fly and happy holidays.
Success! (but how?)
Ok Fly,
I don't get it... not at all. I tried, just for the hell of it, a little more tonight and my phone was happy to flashboot boot TWRP 2.2.2.1 SPECIFICALLY. I was unable to get other versions working or other custom recoveries. I have no IDEA why. I can only think that the recovery partition is too small for some recovery.imgs? but 2.2.2.1 is actually bigger than 2.3.3.0 that you compiled for the rezound. Anyway, i have ROOT! now, my first step before I dork with anything is to S-Off this bad boy so i can move around a little more. I will probably still leave the locked bootloader after that, just to keep me from n00bing up. Haven't tried flashing the twrp recovery yet, don't want to goof up my S-off chances or not give you a chance to ask a question.
If you want some forensics to help others out, please let me know. I am gonna leave this phone alone for a day in case you have questions. There HAS to be some lesson in here. Totally random to me. (last thought) i was running 2.2.2.1 before I ran the RUU... wonder if that has something to do with it?
Thanks again Fly.
phaedrus43 said:
Ok Fly,
I don't get it... not at all. I tried, just for the hell of it, a little more tonight and my phone was happy to flashboot boot TWRP 2.2.2.1 SPECIFICALLY. I was unable to get other versions working or other custom recoveries. I have no IDEA why. I can only think that the recovery partition is too small for some recovery.imgs? but 2.2.2.1 is actually bigger than 2.3.3.0 that you compiled for the rezound. Anyway, i have ROOT! now, my first step before I dork with anything is to S-Off this bad boy so i can move around a little more. I will probably still leave the locked bootloader after that, just to keep me from n00bing up. Haven't tried flashing the twrp recovery yet, don't want to goof up my S-off chances or not give you a chance to ask a question.
If you want some forensics to help others out, please let me know. I am gonna leave this phone alone for a day in case you have questions. There HAS to be some lesson in here. Totally random to me. (last thought) i was running 2.2.2.1 before I ran the RUU... wonder if that has something to do with it?
Thanks again Fly.
Click to expand...
Click to collapse
Anytime :fingers-crossed:
Crazy how things work like this. But the recovery partition shouldn't be to small to flash a custom recovery. Good luck. Just sounds like one of those rare things that happens.
I'm starting off this thread by listing what I did first, and then what is wrong.
I wanted to unlock my new Evo so I used the r regaw_leinad HTCDEV unlock method and installed TWRP. It was only AFTER this was done that I realized I couldn't get SU with the SW version I had on my phone. So I'm S-ON but have TWRP installed only. So basically Stock.
Anyhow, I went to upgrade with the latest OTA and it kept putting me into TWRP and not updating it. Now, I'm sitting with a phone that will only boot to the HTC image and won't fully start up. I can get into TWRP but every rom I flash doesn't work even though it says it flashed correctly. I'm at a loss and really need help here.
You cant take an OTA with a custom recovery. Thats your problem. The heart of the problem though is that you should never take an OTA at all.
Now for your solution, you have to flash a ROM based on 1.22 otherwise your going to have kernel issues.
For the future, know your h-boots limitations:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-wip.html
Any ROM you flash that has a different kernel than the one you are currently on will need to have the kernel installed this way
Good information, I never knew that...
I've downloaded a ROM Fresh Evo LTE 5.2.1 based on 1.22 like you said - flashed the boot.img using fastboot but it still loops the ROM. Should I be doing this in a specific order? My order was this:
Wipe Cache/Davlik
Flash Fresh Evo ROM
Fastboot boot.img using the method you linked to
Reboot my phone.
Several months ago I started the RegawMOD root process before HTC blocked the tokens. Thing is, it didn't complete. My bootloader screen shows Unlocked. But it didn't go beyond this point. Which may have been the result of my previously malfunctioning computer. I have software version: 1.22.651.3.
Presently, I'm running into a situation because I want to finish rooting this so I can proceed to installing a custom ROM. Obviously I can't just run RegawMOD's .exe again because of the HTC token issue, and from what I've been reading on XDA, this software version (1.22.651.3) doesn't have an un-root process.
I really don't know what to do at this point, I'm not very experienced with rooting/rom'ing and as near as I can tell, there's nothing I can do. Does anyone have any ideas about how to correct this?
MaL.euroniC said:
Several months ago I started the RegawMOD root process before HTC blocked the tokens. Thing is, it didn't complete. My bootloader screen shows Unlocked. But it didn't go beyond this point. Which may have been the result of my previously malfunctioning computer. I have software version: 1.22.651.3.
Presently, I'm running into a situation because I want to finish rooting this so I can proceed to installing a custom ROM. Obviously I can't just run RegawMOD's .exe again because of the HTC token issue, and from what I've been reading on XDA, this software version (1.22.651.3) doesn't have an un-root process.
I really don't know what to do at this point, I'm not very experienced with rooting/rom'ing and as near as I can tell, there's nothing I can do. Does anyone have any ideas about how to correct this?
Click to expand...
Click to collapse
If it says unlocked then u need to flash a recovery.. Then from recovery u flash whatever custom rom u want.. Most all custom roms are rooted with busybox.. So just flash recovery then flash rom and u will be golden!:good:
Nooblube said:
If it says unlocked then u need to flash a recovery.. Then from recovery u flash whatever custom rom u want.. Most all custom roms are rooted with busybox.. So just flash recovery then flash rom and u will be golden!:good:
Click to expand...
Click to collapse
Thank you. As I mentioned, I'm relatively new to this, so not entirely sure what to search for on XDA to flash recovery. I'm not asking for the answers, but, do you have any recommended search terms that I should use?
Look up team unlimited on the web, download twrp for your phone, enable usb debugging in dev options and push the recovery to your phone with adb.
Sent from my EVO using xda premium
Stuck more than ever
So, here's the deal: I found out that when I went through the Regaw root process, I do actually have a recovery on here. So I attempted to flash a ROM, which promptly wouldn't load. It says "unknown Md5 error".I looked up some information about the MD5, and it's related to some left-over stuff from before I used the root process, which I've lost because I've since formatted my computer.
I tried running RUU; it typically fails saying it can't detect the device. I've downloaded all the HTC drivers and the RUU starts ok sometimes, but not all the time. Right now, the only screens I can get to are the bootloader and recovery.
Download a ROM with a son installer included. Boot into recovery by holding power and volume down. Wipe everything in recovery except your storage. Mount your phone to your PC via USB mount storage. Transfer the rom to your phone and flash.
Sent from my EVO using Xparent Skyblue Tapatalk 2
https://plus.google.com/103583939320326217147/posts/eywrqNeJhdB
Tonight, +Wil Wheaton was trying to root his HTC One and failing miserably. He was able to get recovery installed, but couldn't figure out how to get Superuser installed through recovery (some issue with mounting, blah blah).
https://plus.google.com/108176814619778619437/posts/11MvAVpy98E
Tough bootloaders call for an even tougher recovery. I'm proud to announce the new Wil Wheaton Recovery. Wil Wheaton will offer to root your device if root access is missing.
Will Wheaton Recovery is a limited edition recovery, exclusive to the HTC Ones (AT&T + Tmobile) and Wil Wheatons. Enjoy!
Download Wil Wheaton Recovery and flash it with fastboot:
http://download.clockworkmod.com/test/wHil-wheaton.img
Boot recovery, then just reboot back to Android once in the recovery menu. Before recovery exits, it will automatically prompt you to install root if it is missing.
Once rooted, just install Superuser off Google Play. It will finish off the rooting process:
https://play.google.com/store/apps/details?id=com.koushikdutta.superuser&hl=en
Click to expand...
Click to collapse
ghostdgnn said:
https://plus.google.com/103583939320326217147/posts/eywrqNeJhdB
Click to expand...
Click to collapse
I read about this the other day, and was about to make a thread asking how it worked because I'm about to root my wife's new phone. I got sick of HTC's inconsistent build quality and went to Samsung (I'm regretting that and hopefully getting a One myself soon), but wanted to make sure the process with this was the same as when I last did it. Go to htcdev.com, unlock your bootloader, then flash this through bootloader. That's it! Right? Haha, thanks in advance.
Hopefully this helps others and not just me being unfamiliar with HTC and not reading enough...:laugh:
Yup, it's the same old process.
t-mobile RUU
does anybody know where i can get the stock t mobile RUU from. cus im have the same problem it keeps saying Cache cant mount the Will Wheaton version didnt even work lol. but any help would appreciated
?????
does anybody know WHEN i might be anble to get the stock t mobile RUU.
My HTC One M8 from AT&T got stuck in a boot loop after I unlocked it, put a custom recovery on it, and then tried to put a custom ROM on it.
I tried to put InsertCoin on there and it got stuck in a boot loop for some reason.
I got the SDK kit and tried doing a adb push my NANDroid I did originally (before trying the ROM) and so I have my NANDroid backup.
I just can't push anything to my SDCard because it keeps saying "adb shell ls /mnt/sdcard/" no such file or directory exists
same thing with "adb shell ls /sdcard/" no such file or directory exists.
I have my NANDroid backup (before the soft brick) and, a new ROM (Viper One M8 2.3.0)
so how do I "adb push" a file onto a filesystem that I have no access to?
Thanks!
**EDIT**
adb push viperOne.zip /sdcard says "protocol failure"
It's as if I have no rights to push anything.
When I try to "install from .zip" it says "unable to mount SDCard"
Hope this helps
adb push viperOne.zip /sdcard/. is what it should be @command. make sure rom zip is in same location as adb/fastboot files
Wonders_Never_Cease said:
adb push viperOne.zip /sdcard/. is what it should be @command. make sure rom zip is in same location as adb/fastboot files
Click to expand...
Click to collapse
They are in the same location as the adb/fastboot.
Still same errors.
Are you booted into recovery when running that command?If so and still getting that error... Gonna have to attempt running an ruu then see if it clears it up, try to flash back stock recovery, boot into bootloader connect to computer and run the ruu. s-on or s-off?
It is S-ON
Also I have a nandroid backup. But because I can't adb push anything, I can't even run the nandroid backup to restore.
It won't mount my SD card.
I have to do an RUU? How do I do that?
ok so did you try to flash the kernel [email protected] s-on device? since rom has been flashed... pull the kernel from the rom zip you flashed and copy it to adb/fastboot location,boot into bootloader,connect via fastboot, then run fastboot flash boot boot.img
I didn't do a kernel. It was just default.
That seems too complicated.
I somehow fixed my issue but getting CyanogenMod and flashing that using sideload. For the first time ever sideload worked.
However when I got the Google play services, it kept crashing when I opened it, any reason why? I have the CM nightly 20140830
Thanks!
Cant help you on that,better to ask in the devs thread for that software your running. Good luck.
technocrat7 said:
I didn't do a kernel. It was just default.
That seems too complicated.
I somehow fixed my issue but getting CyanogenMod and flashing that using sideload. For the first time ever sideload worked.
However when I got the Google play services, it kept crashing when I opened it, any reason why? I have the CM nightly 20140830
Thanks!
Click to expand...
Click to collapse
What recovery? If TWRP, try CWM as SD mount issue (while sideload works) is a problem I've seen here several times before on TWRP.
Help help help soft brick no os no baseband
Wonders_Never_Cease said:
adb push viperOne.zip /sdcard/. is what it should be @command. make sure rom zip is in same location as adb/fastboot files
Click to expand...
Click to collapse
I have a sprint htc one M7 I just got my replacement phone today and i rooted it and got every thing restored on it then there was a problem with the speakers on the phone it would play music but only on the right side .....(i forgot to mention i installed renovate rom after i rooted it) so i figured if i installed another kernal it would fix it so i installed kangaroo kernal for SPRINT HTC ONE android version 4.4.2 which was the right kernal for my phone ..so i thought... so when i installed it ..it took a while for it to turn on and i knew something was wrong when it turned on the home screen wouldn't load and it was showing i had no service when i was in a area i clearly new i had service in so i tried to run a RUU and i keep getting a USB error when it tries to send the ruu . I know the cable works and when i ran fastboot getvar all there is no baseband and no os .........HELP SUPER URGENT URGENT MY parents are going to kill me cause i just got my replacment.... my hboot is 1.57 PLEASE HELP QUICK.:crying::crying::crying::crying::crying::crying:
Jac15myers said:
I have a sprint htc one M7
Click to expand...
Click to collapse
This forum is for the M8, not the M7. Not only that, but the AT&T version, not Sprint.
You should post to your device specific forum section. As the devices are completely different hardware, advice given here may not work for your M7 and may even damage it.
HTC One M8 (AT&T) Soft-Brick Bootloop
Hey everyone, I'm new to XDA and am a bit of a noob at flashing so take it easy on me
Here's my problem: As implied by the title, my AT&T One M8 is stuck in a bootloop at the white HTC screen and won't boot me into my rom. Something to note is that there's a little open gray lock icon at the bottom of the white screen. After a moment the screen just takes me to Philz recovery. Also, the phone was previously rooted and is currently S-On (no firewater support for AT&T yet), with my custom recovery (Philz). Unfortunately, I did not make a backup of my phone (I know, bad move) but at this point I just want the thing to work properly!
What happened: With a stock GPE Rom by Graffixnyc, I installed Google's stock recovery in hopes of recieveing the 4.4.4 OTA; the rom I had was 4.4.2. A day later I get the 4.4.4 OTA, accept and install it, and then that's what started the bootloop. I haven't gotten back into the OS since. In addition, my computer does not recognize my device when it's connected, although fastboot and adb commands do work.
What I've tried: Flashing through both TWRP and Philz, trying two different GPE roms. Neither worked, even through adb sideloading I get the same error. To transfer files from my computer to phone I've been using a micro SDcard with an SD adapter. I've also tried doing a factory wipe through Philz and even flashed a 'fix permissions' emulator.
I'd imagine that I need a One M8 factory image just for a fresh clean start, but apparantly HTC only has one for the unlocked developer edition. Would I be able to use this version of the factory image/obtain one for the AT&T model or is there a different route I need to go?
Thanks in advance for the help; this seems like a great community to be involved in!!
Blaise56 said:
Here's my problem: As implied by the title, my AT&T One M8 is stuck in a bootloop at the white HTC screen and won't boot me into my rom. Something to note is that there's a little open gray lock icon at the bottom of the white screen. After a moment the screen just takes me to Philz recovery. Also, the phone was previously rooted and is currently S-On (no firewater support for AT&T yet), with my custom recovery (Philz). Unfortunately, I did not make a backup of my phone (I know, bad move) but at this point I just want the thing to work properly!
What happened: With a stock GPE Rom by Graffixnyc, I installed Google's stock recovery in hopes of recieveing the 4.4.4 OTA; the rom I had was 4.4.2. A day later I get the 4.4.4 OTA, accept and install it, and then that's what started the bootloop. I haven't gotten back into the OS since. In addition, my computer does not recognize my device when it's connected, although fastboot and adb commands do work.
What I've tried: Flashing through both TWRP and Philz, trying two different GPE roms. Neither worked, even through adb sideloading I get the same error. To transfer files from my computer to phone I've been using a micro SDcard with an SD adapter. I've also tried doing a factory wipe through Philz and even flashed a 'fix permissions' emulator.
I'd imagine that I need a One M8 factory image just for a fresh clean start, but apparantly HTC only has one for the unlocked developer edition. Would I be able to use this version of the factory image/obtain one for the AT&T model or is there a different route I need to go?
Click to expand...
Click to collapse
Did you do the full conversion, of just flashed the GPE ROM?
If you didn't do the full conversion, GPE uses a different partition layout, bootloader, and different CID (and MID?) than Sense, so any one or all of those can be your issue.
What happens if you try to boot into bootloader and select recovery?
Blaise56 said:
I'd imagine that I need a One M8 factory image just for a fresh clean start, but apparantly HTC only has one for the unlocked developer edition.
Click to expand...
Click to collapse
Not sure why you think that. RUUs are available here:
http://www.htc.com/us/support/htc-one-m8-att/news/
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Proper CID and relocked bootloader required to run RUU with S-on. And hboot number of the RUU must be equal or greater than what you have installed.
redpoint73 said:
Did you do the full conversion, of just flashed the GPE ROM?
If you didn't do the full conversion, GPE uses a different partition layout, bootloader, and different CID (and MID?) than Sense, so any one or all of those can be your issue.
What happens if you try to boot into bootloader and select recovery?
Not sure why you think that. RUUs are available here:
http://www.htc.com/us/support/htc-one-m8-att/news/
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Proper CID and relocked bootloader required to run RUU with S-on. And hboot number of the RUU must be equal or greater than what you have installed.
Click to expand...
Click to collapse
Thanks man!
I have the almost same problem yesterday when i unlocking the bootloader, flash TWRP recovery after flashing a recovery i want to root device in TWRP i install update SuperSU and i restart phone my M8 is stoped in HTC logo & cannot further i need solution quickly because i need phone i don't have spare for replacing my M8 please help
Fifa91 said:
I have the almost same problem yesterday when i unlocking the bootloader, flash TWRP recovery after flashing a recovery i want to root device in TWRP i install update SuperSU and i restart phone my M8 is stoped in HTC logo & cannot further i need solution quickly because i need phone i don't have spare for replacing my M8 please help
Click to expand...
Click to collapse
Not enough info, please do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
You probably used an obsolete version TWRP, and obsolete SuperSU. But I need to see the getvar data, plus what TWRP version and what SuperSU version, to know for sure or advise any more.