I have had my HTC One M7 shortly after it was release. I got it from ATT. I immediately found a guide here and rooted it. I had TWRP and every time ATT tried to push an OTA I would refuse. I haven't bothered with it until a couple weeks ago when I wanted to put in KIT KAT. so I found m7_Stock_Rooted_4.18.502.7_odex.zip. I did a dirty upgrade, as the thread said it was okay. And it was. I am going on a trip so I purchased a sim unlock code in between upgrading to kitkat and today.
I got another OTA. I must not have read the bootloader correctly to refuse the install. I was no longer rooted. I come back to XDA and thought what the heck, I'll try out this ROM, it looks nice: Android_Revolution_HD-One_83.1.zip. I use TWRP to put the ROM in and now I am full of fail. After a little bit of Google I decided to try to do a factory reset. And now I am stuck in a boot loop. I have went back to Google but so far all I have seen is use adb or some other method to put things on the "sd card". But how would I do that when this phone doesn't have a sim card and I can't hook it up to my computer anymore? FWIW at some point in the boot loop my computer will recognize the phone, but it won't stay in that state long before it goes away. What happens is my phone starts too boot. Boot screen comes up. After about 10-15 seconds it restarts. This time saying entering recovery.... at the top. That lasts for about 2 seconds, phone goes black and reboots like normal. Over and over.
Best I can do is get to the android hard reset screen by holding power and reset screen. But that is saying "tampered" and "unlocked" at top. I chose the factory setting option and that doesn't do anything to alter the current state.
Edit:
When I went to flash Android Revolution ROM I chose wipe data. It gave some error that some files were not copied. So I ran it again, straight from TWRP. But that never installed right and I was stuck in a boot loop. I don't have many options with the android hard reset menu. But if choose restore, I will get to see the screen from TWRP flash for just a moment before it goes away and reboots.
Also I do see my phone when I have it plugged in the control panel (windows). Under devices and printers, it is listed as Android 1.0 under unspecified devices.
Budee80 said:
I have had my HTC One M7 shortly after it was release. I got it from ATT. I immediately found a guide here and rooted it. I had TWRP and every time ATT tried to push an OTA I would refuse. I haven't bothered with it until a couple weeks ago when I wanted to put in KIT KAT. so I found m7_Stock_Rooted_4.18.502.7_odex.zip. I did a dirty upgrade, as the thread said it was okay. And it was. I am going on a trip so I purchased a sim unlock code in between upgrading to kitkat and today.
I got another OTA. I must not have read the bootloader correctly to refuse the install. I was no longer rooted. I come back to XDA and thought what the heck, I'll try out this ROM, it looks nice: Android_Revolution_HD-One_83.1.zip. I use TWRP to put the ROM in and now I am full of fail. After a little bit of Google I decided to try to do a factory reset. And now I am stuck in a boot loop. I have went back to Google but so far all I have seen is use adb or some other method to put things on the "sd card". But how would I do that when this phone doesn't have a sim card and I can't hook it up to my computer anymore? FWIW at some point in the boot loop my computer will recognize the phone, but it won't stay in that state long before it goes away. What happens is my phone starts too boot. Boot screen comes up. After about 10-15 seconds it restarts. This time saying entering recovery.... at the top. That lasts for about 2 seconds, phone goes black and reboots like normal. Over and over.
Best I can do is get to the android hard reset screen by holding power and reset screen. But that is saying "tampered" and "unlocked" at top. I chose the factory setting option and that doesn't do anything to alter the current state.
Edit:
When I went to flash Android Revolution ROM I chose wipe data. It gave some error that some files were not copied. So I ran it again, straight from TWRP. But that never installed right and I was stuck in a boot loop. I don't have many options with the android hard reset menu. But if choose restore, I will get to see the screen from TWRP flash for just a moment before it goes away and reboots.
Also I do see my phone when I have it plugged in the control panel (windows). Under devices and printers, it is listed as Android 1.0 under unspecified devices.
Click to expand...
Click to collapse
which twrp version do you have installed?
little123 said:
which twrp version do you have installed?
Click to expand...
Click to collapse
Thanks dude. I had an older version, since I originally rooted this phone around 18 months ago and used a version from back then. I watched a youtube video how to push TWRP onto a soft bricked device using ADB. After that, I was able to install the ROM.
Budee80 said:
Thanks dude. I had an older version, since I originally rooted this phone around 18 months ago and used a version from back then. I watched a youtube video how to push TWRP onto a soft bricked device using ADB. After that, I was able to install the ROM.
Click to expand...
Click to collapse
glad i could help with just a question
Related
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
brasstongue said:
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
Click to expand...
Click to collapse
Can u get into bootloader?? Press power + vol down??
brasstongue said:
After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols.
Click to expand...
Click to collapse
that means your firmware is either in a state of limbo, or you corrupted one of your partitions.
so I decided to try to reflash the stock ROM, using the RUU zip found here. Due to some problem
Click to expand...
Click to collapse
which ruu, and what was the problem
But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM.
Click to expand...
Click to collapse
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Thanks for the reply.
nkk71 said:
which ruu, and what was the problem
Click to expand...
Click to collapse
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
nkk71 said:
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
Click to expand...
Click to collapse
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
nkk71 said:
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
Click to expand...
Click to collapse
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
nkk71 said:
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
Click to expand...
Click to collapse
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
nkk71 said:
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Click to expand...
Click to collapse
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
brasstongue said:
Thanks for the reply.
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
Click to expand...
Click to collapse
my bad, thought I read Sprint, not sure if Sprint and Verizon use same recovery, but that doesn't really matter now
unless you can get to bootloader, you're stuck, sorry.
If your pc does see "fastboot devices" then it must be in bootloader and flashing a ruu.zip (if available) could (that's a very big could) get the device working again.
Hey guys, Im fairly new to this stuff, but I got a question or two, it may take me a day to reply so i'll try to put as much info as posible.
Now recently I received the OTA 4.20 (Lolipop) on my phone, so I flashed my stock recovery to download the OTA, making me reroot my phone.
So my phone is re-rooted (after 2 tries) but now it seems like I cant write to my SD card, so I got fed up and went into TWRP recovery and selected wipe data and restore. (Restore point was before I got lolipop) I try to reboot but it takes me as far as HTC One screen. Next I go to recovery and try a factory reset, says its successful, but it lied to me! Still stuck at HTC One screen. So I flash back to stock recovery to try the factory reset with that, it went for a moment, then tried to boot, getting stuck at HTC one screen again, so once more, I flash TWRP to my phone in attempt to get the recovery back, but now I can't load recovery, or boot. So Im stuck there. Is there any advice to what to do from here? I tried command 'fastboot erase cache' thinking that would do something and reflashing the recovery.img but it's still not working. I hope someone can help me.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
The reason you can't write to your SD card isn't because of lollipop, that was actually added but on kit Kat, but the devs went and added a line of code to a file to allow it again. I am currently running my stock rooted, built from decrypted ruu, originally I wasn't able to but I added that one line of code. I believe all you have to do is flash a stock rooted and SD card write should be enabled. As for not being able to get into recovery or boot at all, boot to bootloader and ruu then flash twrp.
Ok so correct me if im doing something wrong, but I flashed the stock recovery in attempt to factory reset it, it wont work, so I flash TWRP with command line (Fastboot flash recovery twrp.img) And it's 'successful' but it wont load, it will attempt to load but one second in and it goes back to fastboot, how to I move forward from here?
Edit: so idiot me did it again, I was trying to install M7 version into a m8. Resolved, Now I can enter recovery again.
Alright, so now my only problem is now that it wont boot normally, it freezes at HTC one screen. I have access to TWRP recovery, just not sure what to do next from here.
ArthAngel said:
Alright, so now my only problem is now that it wont boot normally, it freezes at HTC one screen. I have access to TWRP recovery, just not sure what to do next from here.
Click to expand...
Click to collapse
I actually just unlocked my bootloader yesterday, installed TWRP today, and had what I thought was the same. The thing is, let it sit. Mine sat at the HTC ONE screen for what seemed to be between 5 and 10 minutes. I read that it happens in one of these threads.
But I let it sit and it eventually went to "Android is Upgrading" and was loading the apps.
dopy25 said:
I actually just unlocked my bootloader yesterday, installed TWRP today, and had what I thought was the same. The thing is, let it sit. Mine sat at the HTC ONE screen for what seemed to be between 5 and 10 minutes. I read that it happens in one of these threads.
But I let it sit and it eventually went to "Android is Upgrading" and was loading the apps.
Click to expand...
Click to collapse
Ok thanks, I'll post back in 20 minutes with an update.
So i've waited about 20 minutes on the HTC one screen, (Still on it as I post this) It is still stuck on it. I dont know if this helps but im able to view my internal and external card via computer cable, but I only see folders, no files of any kind in any of them..
Edit* I WAS able to read it, now I can't.
I GOT IT! I was able to revert to a backup I made. Even though I gotta flash stock again for OTA but F it! I got it working again. Thanks for all your help!
I have a Moto G XT1072. I had unlocked the bootloader, installed TWRP and rooted it a while ago. I did not install any custom rom.
I was completely unaware of TWRP's lack of support for OTA upgrades, so when my phone notified me that there was an update available, I was like "oh, cool, okay" and downloaded it.
a) The download finished, the phone rebooted and TWRP recovery popped up.
b)"Mh, I guess I have to find the update file and flash it, probably"
c) Of course I didn't find it, so I googled and found out that if I want to install an OTA update I have to flash back the stock recovery and I might lose root. "Not worth it, thanks, maybe when 6.0 comes out"
d) So I rebooted the phone. Boot screen with motorola logo shows up, phone boots normally, I insert my sim card pin, set the alarm for tomorrow morning (6:00 am, fml) and *poof*, phone shuts down and reboots in TWRP.
e) back to point d.
Recap: I downloaded the update but I didn't install it, phone boots normally (I can even go in settings), but after 30 seconds it shuts down and reboots in TWRP. I do not care about the update, I just hope I can avoid re-rooting or even wiping.
I've got the exact same problem as you. Stupid to not have thought this could've happened with TWRP installed. Additional problem is, I have removed everything ''root-related'' (adb, fastboot), because I thought I wouldn't need it anymore. TWRP is obviously still on my mobile, but that's about it. I have already made a backup in TWRP (don't think it will help, because I'm afraid it will backup as boot trap), but who knows if it may help.
Back to the point, I'm a noob with rooting, I don't even know how I've managed to root it in the first place, but I'm stuck with the same problem as you are but without the required tools (at least, that's what I think)...
UPDATE: So my phone finished the backup, I turned it off to charge my battery, I fired it back up after an hour (normal way, not TWRP way), and it all of the sudden works again. It doesn't boot trap anymore and it seems like I'm able to use every function properly again. After those 30 seconds (where it usually rebooted), I now got the message that the installation had failed and that I should try again later. I don't know if there's any logical explanation for this or if this is pure luck, but I'm glad it's working again! I don't know if this will help for you as well ricvail, but I think it's at least worth a shot!
Hello,
I fear my daughters european HTC Desire 510 is bricked. First of all, we have already given up on what is on the phone. So no worries if a solution means wiping EVERYTHING from the phone, as long as we can get it to start again.
For some unknown reason, possibly an update the phone went into an almost constant bootloop a month or so before christmas. It could eventually get to the login screen, after going in circles for anything between 20 mins and hours. So I thought I would try to tamper with it. I know how to get into the bootloader from rooting other phones, so I went there to try to reset the phone to the factory settings. The result was that the phone now wouldn't go there again. If I tried to do a second reset it went straight to boot, without any way to interrupt, same thing when trying to go into recovery, instant reboot in the blink of an eye.
What then happens when the phone reboots? It gets to the first screen, green HTC logo and "Powered by Android", it sits there for maybe 30 seconds, then it goes black, buzz and back to the previous HTC logo. And this goes on until the battery dies, I pull the battery or I quickly push the vol down and power buttons to go into HBOOT.
I usually don't give up this easily. I found another thread here on some european guy having trouble with his Desire 510, and one of the answers linked to a RUU for a european 510. So I thought, why not, I hadn't unlocked the bootloader yet. So I downloaded the RUU and tried to install it. It messed with me a little, aparently as expected, and then ran through the whole installation. Before the upgrade, well downgrade to be specific the OS was ver. 1.51.401.4 but now claims to be 1.51.401.1. Problem though is, absolutely no change in behaviour. I have restarted the phone after pulled the battery and waited for anything between seconds and an hour, and the phone does exactly the same thing. It happily goes into HBOOT but won't allow me to do a factory reset, nor will it allow me to access recovery.
It will allow me to access Fastboot though, so I thought, hmmm if I install ClockWorkMod or TWRP, maybe something will change. Since I'm more used to working with CWM I went down that road, went to htcdev.com, got the unlock code and unlocked the phone. It now says <<< UNLOCKED >>> and I ran the fastboot devices command, that happily returned some "CC4********7 fastboot". So I went ahead and installed CWM, the installation went all the way and in the end it happily stated that CWM was installed. But did that mean any difference, noooo. If I try to access either Recovery, that should start CWM or Factory reset and also Check smartsd, instant reboot. And I mean INSTANT. Fastboot works, as already stated. I can also get into Image CRC and Show barcode, but what good is that.
Any ideas. I'm beginning to think that something is physically broken inside the phone.
This is my first post, but I've had my phone rooted for a few months now with no problems until today out of the blue. What I've done to root my phone in the first place was flash to 4.4.2 NE3, root it, then upgrade to 5.0.1 OC 7 DeOdexed while keeping the root according to the link below. And then I put Xposed framework on it.
https://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
And this has worked well for me for a few months since that was back at the end of December. Flash forward to today when my phone was being rather slow to respond to my actions so I decided to restart it. And upon restarting it, it's been stuck on the AT&T logo screen for a very long time. I can power it down with the power button, but think it actually just restarts it because then it boot ups again on its own. I cannot enter recovery mode with power+home+volume up, but I can get to the custom OS screen with power+volume down. My computer cannot see it as an adb device either. I've also tried removing the SIM card and the SD card and it's still gets stuck at the AT&T logo.
I've done nothing different with the OS or Xposed recently. The only new thing was about 2 hours prior to restarting it, I connected it to my computer to transfer some video files to the sd card. While I had it connecting to the computer and looking at the files on it through the phone's My Apps, it was sluggish to respond to my actions. But after disconnecting it, it was fine. I don't know if this is related, but I haven't done anything else different with it. Is there anyway to get my phone to boot up correctly? Or am I going to have to reflash it all over again? Thank you for any help.
Edit: I can enter recovery mode and I tried wiping the cache. It still gets stuck at the AT&T logo screen. I should also note that it no longer shows the Samsung "custom" boot screen anymore like it used to after rooting, now it just has the default Samsung boot screen, so it would certainly seem like my OS has been corrupted.