I've seen already this thread suggested by XDA thread locator.
https://forum.xda-developers.com/htc-one-m8/help/verizon-htc-one-m8-stuck-htc-logo-t3163088
But I'd try to explain as simple as possible the whole situation which happened hours ago.
Don't know what happened but my mothers phone went off and restarted with htc one logo on it and nothing else later.
Power button itself doesnt work and is not responding.
Configuration PWR + VOL UP gives me restart but no recovery mode, giving me sound effect of restarting phone and ONE logo on it without any other reaction whatsoever.
PWR + VOL DWN zero reaction
PWR + VOL UP & DOWN pressed together restarting the phone and then gives me HTC ONE LOGO and nothing else.
when Phone is plugged in to the computer and I'm forcing the phone to restart it shows me new Device on the computer as a CD Driver every time.
So I think there is still hope to get this guy back to life.
It's running on custom rom but unknown version because it was purchased as a refurb from ebay 2 years ago and it was running just fine utill this very day.
I'm absolutely noob with flashing twrping etc so please ELI5 if possible, any type of help will be much appreciated.
Thanks in advance.
Hey, I had this same problem a couple of days ago. Here's what I did to get the phone into fastboot, from where you can install a recovery, factory reset etc.
1. Hold the power button + vol up button for about 10-20 seconds. This should shut down the phone.
2. Hold the power button + vol down button to restart the phone back into fastboot.
If you can get into fastboot, there are plenty of guides which can help you flash a twrp image. If you want me to give you some instructions on that just reply and let me know. Good luck!
Note that this phone doesn't have download mode (as some other Android devices do); nor is there a button combo to go directly to recovery. But you can almost certainly still get to bootloader, and from there boot recovery. In the current condition, you can get to bootloader by:
1) Hold Power+ vol up (as you have been) to restart the phone.
2) Once the screen goes dark (signaling it is about to reboot) let go of the buttons, and only hold vol down
3) Don't let go of vol down until the bootloader screen appears.
4) If the above sequence fails, its virtually always because the user just didn't get the timing right (either started pressing vol down too late, or let go too early). Just repeat steps 1-3 until you get to bootloader.
Once in bootloader, try to reflash the ROM, or restore a TWRP backup (if you have one). Spontaneously stuck on HTC logo screen is often a result of the OS/ROM becoming corrupt or otherwise damaged, and flashing/restoring the ROM will often fix it.
Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
It's my mom's phone so basically reliabilty and robustness over flashing lights and numerous unnecessary functions.
Version of android doesn't really matter.
Thanks again for help so far.
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
TWRP might be extra helpful or the recovery it's functions are just fine?
Shewie said:
Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
Click to expand...
Click to collapse
I'd need to know more about the phone in order to give any suggestions.
With the phone connected to computer, boot into fastboot mode, and (assuming you have fastboot setup on your computer) do the command: fastboot getvar all
Then post the results (delete IMEI and serial number before posting).
Also, what version TWRP (if that is the recovery installed)?
Shewie said:
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
Click to expand...
Click to collapse
You will be able to flash a ROM from the SD card, if using TWRP.
Shewie said:
TWRP might be extra helpful or the recovery it's functions are just fine?
Click to expand...
Click to collapse
Not sure what is being asked here (can't quite understand). Are you saying that another recovery besides TWRP is presently installed?
@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
I wouldn't mind link to the pack with "must have" to complete the process
Shewie said:
@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
Click to expand...
Click to collapse
You have what is called the "stock recovery" or official HTC recovery.
You can't flash anything but OTA updates, or other official (HTC) signed zips with this. You need a "custom" recovery like TWRP in order to flash things like custom ROMs. So I'm curious what you meant before when you posted:
Shewie said:
Thanks [MENTION=660462]Sadly reflashing/factory reset failed few times due corrupted files.
Click to expand...
Click to collapse
What exactly were you trying to "reflash", what were the exact steps, and the results (specific error messages, etc.).
I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.
Shewie said:
I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.
Click to expand...
Click to collapse
Okay, so you're confusing the terms. Factory reset doesn't flash/reflash anything (flash meaning to install some firmware or software to the device). The only thing that factory reset does is wipe user data.
At this point, I'd suggest the best/easiest course of action in the current conditions (stock recovery, locked bootloader) would be to run the RUU intended for your device. Your device is the AT&T version, so the RUU can be found at the bottom of the page (and instructions on how to install): http://www.htc.com/us/support/htc-one-m8-att/news/
RUU is a complete factory image. You download to a PC (PC required, won't work on Mac or Linux) connect the phone (booted into bootloader-fastboot mode) then just run the RUU, and it will do the rest.
I'm confidant this will get the phone up and running. Your mom may not like all the AT&T branding and apps, if it wasn't there before, and AT&T is not her carrier (one of the main reasons for these devices to have custom ROM - to remove carrier branding). But we can cross that bridge (if need be), after we get the phone working.
Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?
Shewie said:
Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?
Click to expand...
Click to collapse
It just gets stuck sometimes. Just kill the process, and start the RUU again. It will probably work fine on the next try. It's a bit scary, as it says not to stop the process or disconnect the phone while it's running. But if it gets stuck like this, there isn't anything else you can do.
Good News, it's working. But it's bloated to the bones. How I can get rid of the carrier unnecessary software?
I was to afraid to kill the process during update to avoid scenario of bricking my phone completely.
But It's working!
Related
So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
a bit more info plz
alemale said:
So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
Click to expand...
Click to collapse
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
rishr4 said:
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
Click to expand...
Click to collapse
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
alemale said:
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
Click to expand...
Click to collapse
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
2. There is a possibility that you could "brick" or bootloop your phone. There are two types of brick: soft (recoverable) and hard (non-recoverable). With a soft brick, the phone will not boot or keeps rebooting ("bootloop"), but it can be started in bootloader mode which allows repair of the ROM. With a hard brick, the phone won't even boot into bootloader after holding the power button for 10 seconds and the phone must be returned to HTC for service.
Click to expand...
Click to collapse
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the
PROCEDURE 1
Click to expand...
Click to collapse
then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
rishr4 said:
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
Click to expand...
Click to collapse
I tried to unlock the bootloader but it wanted 2.3.5 so i tried to install the new version. now it can't do anything. Well this didn't broke my heart because the phone is pretty worthless . now i have to buy new phone sooner than i planned but still all help is still accepted.
Hi, exactly the same for me : I bought the phone 2 years ago and immediately unbranded it with a goldcard, but never tried to unlock it because it was my wife's and I didn't want to risk anything.
Now she got a new phone, I wanted to play a little with the Wildfire S ^^.
In order to unlock the phone on htcdev I had to update it from 2.13.401.2 to 2.13.401.3, with RUU because can't update with OTA (different CID), with goldcard inside.
After the RUU finished, it says "congratulations everything went well", but actually the phone does not boot, stocked in a loop "quick flash / turns off", can't access bootloader, no USB detection for ADB.
Can't send it to HTC because the 2 years warranty is expired, how ironic ! :laugh:
So... if anyone does know or see any trick that could help to boot anything on this "seems to be hard-bricked" kid... huge thanks to you
I have spent the last 3 days searching XDA & trying every possible fix, no luck!
Here's my dilemma.....
I have custom recovery, TWRP 2.6.3.3, don't know what I did after trying to flash something........ I wiped everything except SDcard by accident. Like a darn fool, forgot after backing up everything via computer, to put a spares on my SDcard. Sooooo, I tried restoring by using LG FlashTool..... Here's where my problems began:
1. I can't load into download mode, it sticks at the logo to enter download mode but doesn't connect.
2. I tried ADB Sideload, sticks at "STARTING ADB SIDELOAD FEATURE.........."
3. No matter what mode (including Fastboot) I try, just won't connect to my computer the way I need it to. (*ALL DRIVERS HAVE BEEN REINSTALLED NUMEROUS TIMES, STILL NO LUCK.*) When I look in DEVICE MANAGER, it shows in "OTHER DEVICES" as "LG-LS980" (*Which is a good thing right? *)
At this point i'm at my wits end...... I tried to HARD FACTORY RESET, but didn't go thru. I'm afraid that if I tried it again, I could cause even more damage.
I've been without my phone for days & I'm about to go crazy if I have to pay LG or Sprint again for another phone!!!! I'd rather use my $600 on something else.
PLEASE TELL ME SOMEONE HAS FOUND A WAY TO GET AROUND THIS!
I've searched just about every forum & tried different methods.
Forgot to add that every time I power off from recovery, I get a the message about my device not being rooted, would I like to install..... When I swipe to install, nothing happens. Just powers off.
MsOhSoPhresh said:
I have spent the last 3 days searching XDA & trying every possible fix, no luck!
Here's my dilemma.....
I have custom recovery, TWRP 2.6.3.3, don't know what I did after trying to flash something........ I wiped everything except SDcard by accident. Like a darn fool, forgot after backing up everything via computer, to put a spares on my SDcard. Sooooo, I tried restoring by using LG FlashTool..... Here's where my problems began:
1. I can't load into download mode, it sticks at the logo to enter download mode but doesn't connect.
2. I tried ADB Sideload, sticks at "STARTING ADB SIDELOAD FEATURE.........."
3. No matter what mode (including Fastboot) I try, just won't connect to my computer the way I need it to. (*ALL DRIVERS HAVE BEEN REINSTALLED NUMEROUS TIMES, STILL NO LUCK.*) When I look in DEVICE MANAGER, it shows in "OTHER DEVICES" as "LG-LS980" (*Which is a good thing right? *)
At this point i'm at my wits end...... I tried to HARD FACTORY RESET, but didn't go thru. I'm afraid that if I tried it again, I could cause even more damage.
I've been without my phone for days & I'm about to go crazy if I have to pay LG or Sprint again for another phone!!!! I'd rather use my $600 on something else.
PLEASE TELL ME SOMEONE HAS FOUND A WAY TO GET AROUND THIS!
I've searched just about every forum & tried different methods.
Click to expand...
Click to collapse
So try this...
Push the power button to turn the device on. Let it sit.
After you know that the g2 is on and trying to do its think, Press and hold power buttton, do not let go. It will force turn off the phone, but it will start to turn back on, if you keep holding the power button till it shuts off for the second time, you'll be set and the device will be fully off.
Have Lg Flash Tool open, make sure you have manual mode on and you point to the right dll and right tot file, could be zv7 zv8 or zva.
Click the arrow to have the flash tool biin check the files. when that is ready, do this next part fast. Plug in your phone, and immeditaly press and hold Volume up and Power. Download mode should appear.
and you should be good from there! If you try to enter download mode by using volume and up without the cable plug in, you'll hit the factory reset menu which is tied to the recovery, it'll do nothing, only take you to recovery. I hope this is of some help!
Edit:try new boot loader or system flasher via twrp
proplem i faced is one button which used to enter recovery is damged
Flash stock Ignoring the unmonted ianot able to be mounted then change system partitions u will be able to mount
Enjoy
bmxerkid954 said:
So try this...
Push the power button to turn the device on. Let it sit.
After you know that the g2 is on and trying to do its think, Press and hold power buttton, do not let go. It will force turn off the phone, but it will start to turn back on, if you keep holding the power button till it shuts off for the second time, you'll be set and the device will be fully off.
Have Lg Flash Tool open, make sure you have manual mode on and you point to the right dll and right tot file, could be zv7 zv8 or zva.
Click the arrow to have the flash tool biin check the files. when that is ready, do this next part fast. Plug in your phone, and immeditaly press and hold Volume up and Power. Download mode should appear.
and you should be good from there! If you try to enter download mode by using volume and up without the cable plug in, you'll hit the factory reset menu which is tied to the recovery, it'll do nothing, only take you to recovery. I hope this is of some help!
Click to expand...
Click to collapse
This isn't working. I've tried this numerous times..... No luck.
myaservip said:
Edit:try new boot loader or system flasher via twrp
proplem i faced is one button which used to enter recovery is damged
Flash stock Ignoring the unmonted ianot able to be mounted then change system partitions u will be able to mount
Enjoy
Click to expand...
Click to collapse
I'm now completely lost.....
Ok... So i made a little progress....
I am now able to boot into fastboot mode.... No recovery now tho. If someone can help me with manually pushing everything I need to restore my phone, it would make my day!
I'm having withdrawal symptoms now. LOL! I MISS MY PHONE!
Problem solved!
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!
MsOhSoPhresh said:
This isn't working. I've tried this numerous times..... No luck.
Click to expand...
Click to collapse
MsOhSoPhresh said:
I am now able to boot into fastboot mode.... No recovery now tho. If someone can help me with manually pushing everything I need to restore my phone, it would make my day!
I'm having withdrawal symptoms now. LOL! I MISS MY PHONE!
Click to expand...
Click to collapse
MsOhSoPhresh said:
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!
Click to expand...
Click to collapse
Glad to see you've fixed your problem! I myself haven't been around, had some down time to. My sim reader magically stopped working and then randomly started working days later. Anyway, congrats!!!
MsOhSoPhresh said:
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!
Click to expand...
Click to collapse
Glad you figured it out. I was about to basically explain the steps to do exactly what you did.
Welcome back to the land of the living!
agentfusion said:
Glad you figured it out. I was about to basically explain the steps to do exactly what you did.
Welcome back to the land of the living!
Click to expand...
Click to collapse
After she got it the first time, which we both congratulated her for, something went completely wrong. She dug herself even deeper, but broke download mode. That was extremely fun to fix.
I am in need of some serious help. My AT&T M8 won't boot past the HTC logo screen and won't allow me to go into recovery or the hboot screen. I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen. It was so bad that I just left it plugged in overnight and I don't have a clue as to how long it took to power off because I fell asleep before it did. If there's a video tutorial out there that someone has or simply a link that can show me how to install something via backdoor on this device, that would be great!
alpinesun said:
I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. !
Click to expand...
Click to collapse
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
alpinesun said:
Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen.
Click to expand...
Click to collapse
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.
Thanks already. I didn't realize I had to hold down the volume down button after it goes dark. It got me into twrp. I believe I should be good from here after I download a new rom to sideload. But to give you a run down, I was prepping the phone to sell it by wiping the data and installing the rom the guy said he wanted on it. When I was going thru the normal procedure to install the rom (wipe, flash, etc) that's when the phone started sticking on the logo screen. My assumption was that I downloaded a bad rom, so since then I've been trying to get back into twrp so I can load a new rom and finally was able to after you told me this. I'll report back if a new rom actually didn't help the situation. I only thought I wiped the OS because something similar happened with my Note when I was tinkering and that was the result.
alpinesun said:
I'll report back if a new rom actually didn't help the situation.
Click to expand...
Click to collapse
If you need any further help, please answer all the questions I previously asked.
Good luck.
redpoint73 said:
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.
Click to expand...
Click to collapse
So, it seems I'm still having the problem, even while trying to install cyanogen. Here are the answers to those questions...
1) bootloader unlocked?... YES
2) custom or stock recovery... TWRP
3) custom ROM?... It was a custom AOSP Rom
4) what hboot number?... 3.16.0.0000
5) s-on or s-off... S-OFF
6) did you make a nandroid with custom recovery?... It was erased
Any help you can give from this point would be awesome. Thanks again!
alpinesun said:
So, it seems I'm still having the problem, even while trying to install cyanogen.
Click to expand...
Click to collapse
Failure to flash ROMs can often be solved with fastboot erase cache, then install TWRP by fastboot again. Update TWRP version, if you are using an outdated one.
Also, if you try to flash any ROMs based on Sense software beyond version 1.x (huge majority of them are past 1.x at this point) you will likely experience extremely long boot times (10 minutes or more) and broken WiFi due to outdated firmware. But CM should be okay.
alpinesun said:
6) did you make a nandroid with custom recovery?... It was erased
Click to expand...
Click to collapse
It was erased, or you wiped it?
Okay. Do you suggest trying an older sense rom to see if it works? The last time touched the phone was when I picked up my Note 4, so I will look for something that predates that.
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.
alpinesun said:
Okay. Do you suggest trying an older sense rom to see if it works?
Click to expand...
Click to collapse
Sure, it couldn't hurt. With your current firmware, you will need a ROM based on 1.x software. There aren't a heck of a lot of those left. But there are a few. GoldenEye is one I can personally vouch for, since I was running it for a while back in the day:
http://forum.xda-developers.com/showthread.php?t=2705640
But I would definitely recommend just trying fastboot erase cache and re-install TWRP first. I've lost count how many times suggesting this simple fix has helped other users here on XDA, when ROMs fail to flash.
alpinesun said:
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.
Click to expand...
Click to collapse
Fair enough. Just FYI, don't do a factory reset in bootloader (in the OS settings or recovery is OK). On modded phones this may cause the internal storage to become corrupted. Nandroids have sometimes been lost this way. This may or may not be what happened to you. Just wanted to throw that out there.
Also, there has been the occasional occurrence of internal storage being corrupted, possibly by TWRP. It may not even have been something you caused.
Hi,
it is the second time my Gnex went into endless reboot loop sessions.
It will boot, load crash after few seconds and reboot again.
I had it unlocked in the store i bought it, and had stock rom (Not sure about the version).
Tried to do factory reset from fastboot, from recovery, and from android. Also tried to flash custom boot loader, Nothing works.
Although fastboot writes it successfuly completed the action so does the factory reset. The phone will work for few seconds but no more.
Also tried using WugFresh, for factory reset and for Flash Stock + unroot in soft-break status
I have no ideas what to do next,
Please help.
Mike
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
AvidPhisherman said:
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
Click to expand...
Click to collapse
Hi thanks for the reply, i am a simple user, prior to the bootloop i was using whatsapp, actually the android crashes few seconds after getting a whatsaap message (i recieve notification and it goes down). Previous time also i didn't do anything special. i never installed custom recovery or roms... previous time it was fixed by a lab the phone was on warranty.
And yes the tool recognize the device.
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
AvidPhisherman said:
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
Click to expand...
Click to collapse
Tried to uninstall whatsapp but it crashes before i manage to do so.
even managed to access memory via TWRP and delete whatsaap manually but somehow it appears again after restart.
Something is terribly wrong
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
nthnlee said:
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
Click to expand...
Click to collapse
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
beekay201 said:
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
Click to expand...
Click to collapse
When fastboot didn't work. i had to try something else. But, odin didn't work either.
mishkap said:
When fastboot didn't work. i had to try something else. But, odin didn't work either.
Click to expand...
Click to collapse
Let's see then. Be prepared to spend at least 30min reading, and re-reading, until you actually feel comfortable in what you're doing/typing in. If you're not sure about the technical terms and what lies behind them, read this thread's #1 First Post.
What's your device variant? maguro? toro? toroplus? This will tell which factory image you need to flash.
You need to flash latest factory image, which is (for maguro variant) Android Build 4.3 (JWR66Y). Read #1 First Post on this thread. And I mean, READ IT! Do not do anything else to your device until you do.
After you flash the factory image, that first boot will take a while to reach Android. Chill out. Go get yourself a drink. Take your time. It should have booted into Android already when you get back. It should be fine, but if not, you need to enable USB debugging under Settings > Developer Options, to check the system log.
If after 15min, it still has booted yet, pull the battery out, wait a few secs, put it back in.
Use the 3bc (3-button combo) to reach fastboot mode again. Flash a custom recovery. That's done by downloading the latest TWRP or CWM (i'll leave that choice up to you, be mindful that you might wanna try them both in the future), and running on the host (the PC):
Code:
fastboot flash recovery recovery_filename_here.img
Don't reboot the device. Use the volume keys to "Reboot to recovery" straight from fastboot. After a few seconds, you should be seeing the custom recovery you've flashed with the fastboot command above.
Now comes the part where ADB is required. I hope you've already read the answers to questions "Where do I get the driver for my PC?" and "Why do I need to install the driver twice?". If not, read them now. Also, read "What is ADB?". TIP: When a custom recovery is actually running on the device, ADB mode is already active by default, so when hooking up to the pc the device will show as an ADB interface, so installing the driver (if needed/not done yet) is piece of cake.
After you get ADB to recognize your device (like, you see your device's SN on the output of command `adb devices`).. You need to copy a custom ROM to your device, and flash it. That will get you, most likely than not, Android's USB debugging by default (read answer to "What is an insecure boot image?" on the first link), and that will allow you to see the system log, WHILE Android is booting up. Why do we wanna do this? Cos we want to see if any errors show up, something that may tell us what's failing.
When choosing a ROM from the Android Development section, ask around in the thread if the ROM has USB debugging enabled by default.
Read "What are the ADB commands?" in the thread I first linked to. You'll need to learn at least `adb push` for now.
Once you get the ROM in your /sdcard/ or whatever folder you like, disconnect the USB cable, wipe data/factory reset, then install zip from sdcard (that zip you pushed before).. Forget about gapps for now.
Connect the usb cable, reboot, and once you see padlock screen go away, start trying to run `adb devices`. Do you see your SN in the output? Once you see it, good, it already connected to adb on the device. Run `adb logcat` and try to look out for errors. Logcat is the system log.
To know how to grab that output to a text file so that you can share it with us.. Google it, my fingers hurt.
Thanks beekay201,
As a matter a fact. shortly before you posted this answer i gave up and gave my phone to a local lab.
But unfortunately they were useless and didn't manage to do anything claiming they don't have spares for my phone, tried to explain that it is not a hardware issue, but all in vain .
Anyway, ill go over your instructions and ill update the results soon.
hi everyone,
I am in a quite a pickle here. I tried updating my phone with ARHD43 and after doing it couldn't get the WIFI to turn on. I read a bit and found that this is becuase I do not have the latest firmware. So I tried going back to stock through RUU (flashed stock recovery and boot.img) and in the process flashed new recovery and boot images. Now the my phone keeps booting into stock recovery with the red triangle continuously and I can't boot into the OS. From recovery when I select apply from SD card I throws CID error and reboots into recovery again!
I cannot connect to fastboot so I am stuck bad. :crying:
did I brick my device? can I save it? I am S-ON with unlocked boot loader. region is .707
Appreciate your help.
<I have posted a similar question in the ARHD43 thread but haven't recevied a response so posting in here in the general forum again>
simplyaha said:
I cannot connect to fastboot so I am stuck bad. :crying:
Click to expand...
Click to collapse
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
simplyaha said:
So I tried going back to stock through RUU (flashed stock recovery and boot.img) >
Click to expand...
Click to collapse
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?
redpoint73 said:
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?
Click to expand...
Click to collapse
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.
simplyaha said:
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.
Click to expand...
Click to collapse
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
simplyaha said:
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
Click to expand...
Click to collapse
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.
redpoint73 said:
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.
Click to expand...
Click to collapse
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
I will try again and reply.
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..
simplyaha said:
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
Click to expand...
Click to collapse
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
simplyaha said:
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..
Click to expand...
Click to collapse
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.
redpoint73 said:
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.
Click to expand...
Click to collapse
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning :victory:
yes, no more messing around, promise.. :angel:
simplyaha said:
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning
Click to expand...
Click to collapse
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.
redpoint73 said:
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.
Click to expand...
Click to collapse
ccol thank! I will try this tonight and share the outcome.. :good:
eureka! got my phone up and running now. the ruu was perfect. but got my memory card messed up (showing as raw format on the pc). gotta look for a solution for this now :banghead:
but my phone is back! thank you for all the help. much appreciated. :thumbup:
Sent from my HTC One_M8 using XDA Free mobile app