[Q] Rooted HTC One (M8) stuck in odd bootload? - Android Q&A, Help & Troubleshooting

So upon trying to root and install a custom GPE rom, http://forum.xda-developers.com/showthread.php?t=2716306 to be exact, I had succeeded and successfully gotten the rom on, however from the get-go it was stuck in a bootloop on the 4 circles animation. after around 20 minutes of a laggy boot animation (I showered in wait.) I knew something went wrong. I am able to get into the recovery screen, but not into recovery. the device will not turn off (attempts will only lead to the phone powering up by itself and going back into the 4 circles) nor will it go into recovery mode. my computer is still able to pick it up via USB and adb. If I choose the fastboot option will tell me the device is connected when entering the remount command - however I am not able to browse my phone's files via windows. I also do not have a Micro-SD so the rom/root files are stored internally. I did make a Nandroid back up. I used this [http://theunlockr.com/2014/04/19/root-htc-one-m8-all-in-one-toolkit-method-video/ toolkit and tutorial for my rooting, and their adjacent S-Off tutorial to perform that action. This was my first ROM, and I have not flashed any kernels.
Is there any redemption for me, or have I unfortunately bricked my phone? Is there any possibility AT&T will take pity on me and charge me just a smaller-than-new fee for a replacement?
Please help..?

Related

[Q] Recovery & Flashboot issues. help is appreciated [SOLVED]

First off id like to say thanks in advance to any replies and also apologize if this has been posted previously (i searched and could not find anything that was helpful) I lurked around these forums when i had my x1 and im hoping you guys can be as helpful for me as you are for everyone else. anyway onto the issue
I used the superboot method to root my ATT US Streak. My intentions were to update to 2.1 following the steps in the "eclair working on my u.s. unlocked streak!" thread (wont let me put a link since its my first post)
after using fastboot to root the phone will boot up and function fine but recovery and fastboot no longer work. i tried flashing Koush's custom recovery and other things that require fastboot and the terminal just says "sending..." nothing happens no errors or anything, the cmd prompt just sits there and i need to remove the battery to reboot the device.
i then downloaded the Rom Manager apk from the market and flashed the clockwork recovery from there (it said i did anyway). when i load the recovery from boot (volume keys + power and its the stock recovery) and chose option 2 to flash modaco custom rom or even the stock dell rom it just goes to a black screen and i once again need to remove the battery to reboot.
the phone itself is still functioning fine when it boots up and everything works the way it should other than the home, menu, and back button lights flash in random orders, thats just annoying though. again any help is appreciated
so what should i try next?
EDIT: woke up this morning and now the device will not turn on. i tried starting to fastboot and recovery but still nothing. plug it into my pc and i get the "found new hardware wizard" for a Qualcomm CDMA Technologies MSM.
first real brick? ha that would be my luck
EDIT 2: a kid just ran through my work, grabbed my phone and threw it on the ground. it screwed up the 30 pin connector on the phone and the charger. im going to hurt somebody. phone is booting again though... put sd card back in and still boots fine
SOLVED: Dont know the technical reasons behind it but i had to reinstall the drivers and switch usb ports for every fastboot and recovery procedure
removed SD card and its booting up normally. any thoughts?

[Q] EVO 4g LTE Stuck in repeating bootloop FIXED new phone

This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
I took it to Sprint. They thout it was the power button, after replacing it and the same I got a refurbashed phone through TEP insurance at no cost. WIN. Except does anyone have S-off suggestions for Hboot 2.09 and mainver 3.17.651.4 dirtyracun which I am familiar with does not apper to work.
m1gramme said:
This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
Click to expand...
Click to collapse
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
fizbanrapper said:
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
Click to expand...
Click to collapse
My HBOOT is 2.09.4444
I believe my ROM was eiter a rooted sense or BeanStalk 4.3. I honestly don't remember because I haven't changed anything in so long.
I had TWP openrecovery-twrp-2.6.3.0-jewel.img
Again this wasn't a problem that came from trying to change anything. My phone froze I soft-reset it and it was in an unstoppable bootloop. No images were found. Telling it to go to recovery still took it to bootloop. Even after power down from bootloader, after 20 seconds it boots back into bootloop.
The problem I feel most at hand is I can't charge the battery enough to do anything because it appears to not charge in bootloader.
I have had my phone rooted and s-off through Dirty Racun for almost a year now and have been using the same setup without changing for at least 6 months.
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
If you're able to and have the proper equipment, I'd test the internal battery with a voltage meter to see if it is even able to hold a charge, will save a lot of frustration.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
Again the hardest part about this is my phone refuses to turn off. I have gone into the bootloader and selected Power Down. The phone turns off and the charge light blinks. Then 20 seconds later without me touching it, it turns on and starts into the bootloop.
I am currently finding some luck by holding the down button so when it starts itself again I can be in bootloader mode and select power down. I have elevated my battery from 3530mv to 3649mv (as per fastboot getvar battery-voltage)
Any suggestion as to where a good number to reach would be helpful.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
See above about "charging" after getting it up a little (and without SD card) I tried booting to recovery (getvar battery-status good) still went to htc bootloop screen. Tried to flash recovery and boot as per
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
in troubleshooting guide. Still continues in bootloop
So a littel update after spending forever with my charging trick I was able to get a little more charge. I was able to run commands of flash recovery it stated it was complete. Still boots to bootloop. I was able to try to run RUU using RUU 3.15.651.16 - HBOOT 2.09
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip RUU.zip
The whole process worked (said it did)
Still in repeating bootloops at htc screen.
Phone still turns itself on into a bootloop even after selecting power down from bootloader.
I'm beginning to think it's the dreaded brick...
Interesting issue, indeed. There were some problems reported with the 3.15 RUU, but none that should cause the issue you're having. Check out the top link in my sig and go to the bottom of the first post. Hit up the link for VipeRUU. I suggest trying it and returning your phone to stock. If after returning your phone to stock the issue persists, then you most likely have a hardware issue (already sounds like that's likely the case). If you have TEP with Sprint you can take the phone to a Sprint service center and see about getting it replaced.
Sent from my HTC device
My wife had that issue as well but a factory reset fixed
Sent from my EVO LTE using Tapatalk

[Q] Can't get recovery to load, shell won't work and HTC One freezes at Boot...

I have followed a few of the tutorials with some success but did a mis-step somewhere along the way pursuing S-OFF. While not a total noob with modding (Consoles mainly) this is the first time I am truly lost in the process.
Excuse me if I use a wrong term here and there, I probably need to have a sleep as I have been working on this (from start of initial Mod) for about 17 hours straight (Overnight).
So I have a HTC One M7 UL that I have unlocked and has TAMPERED showing on the Boot screen. :good:
When I power it up it freezes at the white HTC powered by ANDROID screen.
I can get to the Boot menu, and I can select Recovery but it shows the screen for loading the which ever tool I have managed to flash (so yes I have the ability to flash and can swap between Clockwork and TWRP versions with flashing)
I can't list devices or start a shell session, as it thinks that USB debugging isn't turned on. Up until I caused the FUBAR USB connection was working fine.
Holding Power Button doesn't shutdown, just reboots, but can achieve shutdown through boot menu.
How do I get a working phone again?
Ok I soleved it myself. Found a boot.img flashed it over and the custom recoveries work again. Now onto getting S-OFF so I can get Google Play Edition.

*URGENT* HELP! File pulling with ADB

To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.

Bricked Umidigi Crystal

I have a Umidigi Crystal (2/16) and it´s not booting anymore.
How that came is a long story.:crying:
I got the phone, wanted to root it and while I was enabling usb debugging in developer options, I noticed you can root it from there as well.
I have no idea whether thats a Umidigi special or if that was seen on other phones too, basically I had a slider option to enable root access.
After a reboot, SuperSU was installed automatically, root checker, file explorer and rom toolbox worked fine with it but I actually rooted to get Xposed Installer.
That worked very well too, only did I want to have a custom recovery to prepare my phone in case of a bootloop.
So I followed these instructions.
I hadn´t unlocked the bootloader by the time and since the instructions said I would have to unlock it I did that first using these instructions.
Everything worked as expected but from this point on, on the pre-bootanimation picture my screen would say
Code:
Orange State
Your device has been unlocked and can't be trusted
Booting in 5 sec...
As everything else was the same as before, I just ignored it.
Then I moved on to installing TWRP by, again, these instructions.
The process seemed to work but after finishing, I was unable to boot into recovery mode, my phone would just boot into the normal OS(which still worked by the time).
I wanted to get around that by using this app but because of the unlocked bootloader my phone was factory reset
and I had to root again.
I was going for the same way I already did it beforehands and I was asked to reboot again.
After that point, my phone was stuck in the pre-bootanimation screen saying it´s orange state thingy again and would just stay there forever.
I tried installing the stock rom from here ((2/16 - V1.0_20171026)) to get rid of the root setting I enabled.
Now I get the pre-bootanimation screen with the orange state text again and after 5 seconds it keeps the background image but the text disappears.
Thats where it´s stuck for like 3 hours now.
When I press the power key a couple of seconds, that loop starts again, I can´t turn the phone off.
Things I can still do:
•Reboot (holding the power button, still get stuck the same way though)
•Access a PC, the internet, an SD Card and electricity
•Charge the phone
•I still have all the drivers on my PC properly installed
Things I can´t do
•Keep the phone turned completely off
•Boot into fastboot, recovery or normal OS
•Get the PC to recognize my phone (not even the adb)
What I want (if possible in that order):
•Boot into literally any OS
•Use the current OS or any custom rom
•Have root access without the developer option method
•Have TWRP
•Unlocked Bootloader
I know, I ask for a lot but this is the only phone I have right now and I badly need it.
Getting it to boot again is really the primary goal here.
Thanks so much to everyone who tries to help me, it really means a lot

Categories

Resources