I have a wifi Nexus 7, unlocked and stock.
Recently, my tablet got stuck in a boot loop. After reading previous threads and replies, I tried to wipe and do a factory reset.
However, I can't get to the menu in the recovery mode.
I am able to get to the menu where I chose recovery,
My screen shows the dead Android with a red triangle and exclamation point...but I can't get past that.
Prior threads have alternately suggested power button and volume up button simultaneously, or volume up button alone...
But my tablet won't respond to either.
After the dead robot appears, the tablet appears to reboot and is stuck in boot loop again.
Any ideas?
Try this
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
goofball2k said:
Try this
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Click to expand...
Click to collapse
Show GoofBall some thanks. This is not the end of the world. Totally fixable!
Almost 99% of these issues have been addressed. I know how the pucker factor can set in when a device WILL NOT work right. Wrong time to panic. In fact, and no offense to you, the fixes for these issues are available. I understand that it can be a bit tricky navigating for the exact solution to your problem, but they are out there.
If you get in a hurry to "fix it" you might end up "fuxing it".
That is why research is so important when doing these modifications. Read ALL of the installation steps. Forwards and backwards. Memorize them. Keep reading past page 1. There are usually hiccups that get reported and fixed. I will read the entire thread, but most of the times if you read the 1st 5 pages and the last 5 pages of any thread, you will be fine. Bugs get worked out pretty darn quick around here.
For the extra paranoid, do not upgrade to the latest nightlie. Give it a few nights. AND CHECK THE THREAD FOR ISSUES. :good:
All of us are striving for a better experience, even when we don't need it. These Nexus 7 2013 tablets are so damn kick as out of the gate, the only mods really needed are Root, and Custom Recovery. I won't even mention how I feel that TWRP or CWM SHOULD be partnered with Google. Oops, I just did ..
Thanks
goofball2k said:
Try this
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Click to expand...
Click to collapse
Thanks for the suggestion.
Since I couldn't get the unit to boot, I was unable to try your suggestion.
And since my tablet was under warranty, I returned it to the store and swapped it out for a new one.
Badger51 said:
Thanks for the suggestion.
Since I couldn't get the unit to boot, I was unable to try your suggestion.
And since my tablet was under warranty, I returned it to the store and swapped it out for a new one.
Click to expand...
Click to collapse
Would you be willing to describe what went wrong when you followed those steps? Any errors, bootloops...etc.
Feedback is quite helpful.
Boot loop
ldmeeds said:
Would you be willing to describe what went wrong when you followed those steps? Any errors, bootloops...etc.
Feedback is quite helpful.
Click to expand...
Click to collapse
I'm not sure what happened with my tablet. It had been working fine...I was using it yesterday when it locked up....I went to reboot it and discovered it was in a boot loop.
I was able to get it into recovery mode, but had difficulty getting to the recovery menu where I planned to factory reset the unit.
I later was able to do that, but the tablet continued to get stuck in the boot loop mode.
As mentioned earlier, since it was under warranty, I swapped it out at the store and have been busy today, downloading all my apps on the new tablet.
Have there been problems with the volume up and down keys? Those keys did not seem to be performing as they should during this mis-adventure.
You probably were pressing the wrong sequence of buttons.
The Android fallen down screen is an overlay over the recovery menu. To bring the menu to the foreground, you need to press in this exact order:
Press/Hold Power, Press/Release VolUp, Release Power
This post has all the info on how to enter bootloader, recovery, etc.
http://forum.xda-developers.com/showthread.php?t=2397282
Even if you know from other platforms, I suggest reading it because Nexus is slightly different, enough that it can be frustrating. Often people think they should be pressing Power and VolUp at the same time when it needs to be one before the other. Other times, people think they should be pressing VolUp&VolDown, when it is really one or the other.
Great Summary
Great Summary, I have a Galaxy Nexus and you're right...it is confusing to remember the sequence from one installation to another.
As I recall, and my index finger is still sore from pressing the volume buttons....I was used Power and Volume Down to get into the Fastboot, Restart and Recovery Mode...I would select Recovery and the unit would reboot
From there however, I kept getting the dead robot...
sfhub said:
You probably were pressing the wrong sequence of buttons.
The Android fallen down screen is an overlay over the recovery menu. To bring the menu to the foreground, you need to press in this exact order:
Press/Hold Power, Press/Release VolUp, Release Power
This post has all the info on how to enter bootloader, recovery, etc.
http://forum.xda-developers.com/showthread.php?t=2397282
Even if you know from other platforms, I suggest reading it because Nexus is slightly different, enough that it can be frustrating. Often people think they should be pressing Power and VolUp at the same time when it needs to be one before the other. Other times, people think they should be pressing VolUp&VolDown, when it is really one or the other.
Click to expand...
Click to collapse
Related
This is my first post on the XDA forum. I registered only 2 try 2 have a reply 2 a problem that in my language (italian) is impossible to find out.
This is the best place for everything concerning android world so I hope to be lucky.
This morning my galaxy nexus, while I was playing @ paradise island, freezed and started to play several times a sound that was like an emergency (almost like the overheat processor beep in the computer cases - never heard that before). After this emergency beep the phone shutted off.
When I turned it on the Google logo appears but it start having gliches and reboot. This infinite times until the battery is removed. Sometimes it arrives to the colorful background but that times also it freeze (without gliches) and reboot.
Tryin 2 find out the problem I had a soft reset (battery off for 10 mins) but nothing.
I tried also an hard reset. The phone anyway after having selected RECOVERY MODE from the apposite menu start the google logo and when reaches the "red alert signal droid" the droid is gliched and the phone freeze and reboot. And start another time infinite reboots.
Someone know what kind of problem the phone have? It enters without problems in odin mode and the (I kind is called) bootload mode but don't start the recovery mode. I'm totally n00b, the phone is in fact stock, and I don't want 2 wait 1 month of assistance time if is a problem that can be resolved also @ home.
Please help me if you can and thanks for gifting me with your time.
- NeX - said:
.... The phone anyway after having selected RECOVERY MODE from the apposite menu start the google logo and when reaches the "red alert signal droid" the droid is gliched and the phone freeze and reboot. And start another time infinite reboots.
....
Click to expand...
Click to collapse
Sorry to ask but I don't understand gliched, can you get in Stock Recovery (the "red alert signal droid" as you call it), push volume up and power at the same time and enter the recovery menu? Or not?
Diger36 said:
Sorry to ask but I don't understand gliched, can you get in Stock Recovery (the "red alert signal droid" as you call it), push volume up and power at the same time and enter the recovery menu? Or not?
Click to expand...
Click to collapse
no I can't. The droid is gliched so the volume up + power combo doesn't work. The phone reboot some times. Some others times (like the trying I had now) the phone freezes.
Try flash the google stock images through fastboot, there are threads with instructions and links to everything you will need.
You should be able to fix whatever is wrong.
nodstuff said:
Try flash the google stock images through fastboot, there are threads with instructions and links to everything you will need.
You should be able to fix whatever is wrong.
Click to expand...
Click to collapse
If doing it I can loose warranty?
No, you can re-lock your bootloader when you are done.
matt2053 said:
No, you can re-lock your bootloader when you are done.
Click to expand...
Click to collapse
And the problem for sure is going 2 be solved? Seems super!
It MAY solve your problems, if they are software related.
If its a hardware problem it won't.
Give it a try anyway.
nodstuff said:
It MAY solve your problems, if they are software related.
If its a hardware problem it won't.
Give it a try anyway.
Click to expand...
Click to collapse
ok i'll search and try it.
to me, sounds like hardware problem.
this is the toolkit you should try - http://forum.xda-developers.com/showthread.php?t=1392310
joshtb86 said:
to me, sounds like hardware problem.
this is the toolkit you should try - http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
He is better off using fastboot and learning something.
Tool kits are the wrong way to do things, it is better to know what is actually happening when you pick an option in a toolkit.
nodstuff said:
He is better off using fastboot and learning something.
Tool kits are the wrong way to do things, it is better to know what is actually happening when you pick an option in a toolkit.
Click to expand...
Click to collapse
the problem is that I don't know anything of this stuff. I don't know how to start.
The toolkit guide is huge and I think i should do only 2 or 3 of the all listed operation...
For now i took only the kit, the pdanet for win 64 and the yakju 4.0.4 from the google page. I don't know how 2 put them on and in which order.
.....
Oh, phone of my colleague has the same issue. We don't know what to do cause we can't connect Nexus to computer. When trying to do this Fastboot 2147483647 error occurs. Adb devices gives empty list.
Sounds like a hardware problem to me
- NeX - said:
the problem is that I don't know anything of this stuff. I don't know how to start.
The toolkit guide is huge and I think i should do only 2 or 3 of the all listed operation...
For now i took only the kit, the pdanet for win 64 and the yakju 4.0.4 from the google page. I don't know how 2 put them on and in which order.
Click to expand...
Click to collapse
Learn.
It looks like rocket science to me at first(Gnex is my first smartphone), do it slowly.
- NeX - said:
no I can't. The droid is gliched so the volume up + power combo doesn't work. The phone reboot some times. Some others times (like the trying I had now) the phone freezes.
Click to expand...
Click to collapse
Not sure if this is different on other phones but for me to get to recovery its not Volume up + Power. Its Volume up + volume down + power (i.e. hold both volume buttons then hold power button until it vibrates or the google logo shows up)
WoodroweBones said:
Not sure if this is different on other phones but for me to get to recovery its not Volume up + Power. Its Volume up + volume down + power (i.e. hold both volume buttons then hold power button until it vibrates or the google logo shows up)
Click to expand...
Click to collapse
This gets you to bootloader, not recovery
Sent from my i9250
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
JasePK said:
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
Click to expand...
Click to collapse
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from (TWRP or CWM) (how to: https://sites.google.com/site/tomsgt123//adb-fastboot)
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: http://www.reddit.com/r/htcone/comments/1rkvy0/help_stuck_in_bootloop_without_access_to_recovery/
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Techngro said:
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from -snip-
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: -snip-
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Click to expand...
Click to collapse
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
JasePK said:
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
Click to expand...
Click to collapse
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
Click to expand...
Click to collapse
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
JasePK said:
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
Click to expand...
Click to collapse
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
cdresor said:
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
Click to expand...
Click to collapse
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
JasePK said:
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
Click to expand...
Click to collapse
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
cdresor said:
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
Click to expand...
Click to collapse
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
JasePK said:
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
Click to expand...
Click to collapse
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
cdresor said:
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
Click to expand...
Click to collapse
No that's alright, I just wanted to know if it was something I should avoid. :laugh: I'll use Odin to flash the official firmware back on regardless.
I had this happen to me, what had occurred was that the efs was corrupt. Here's the fix:
http://forum.xda-developers.com/showthread.php?t=2507403
Now to implement this fix, you must first be able to get into download mode. To do so:
1. Pull the battery
2. Wait 10-20 secs
3. Reinsert battery WHILE holding power button and (volume down + home???, whatever the key combination is)
5. Phone will boot directly to download mode, no logo
6. Flash twrp via odin
7. Phone will reboot into bootloop again
8. Repeat steps 1-4 except this time use the key combination for recovery
9. You must now use adb and push the file I linked to earlier
10. Then without rebooting you must flash it
11. Reboot and problem solved
Fixed issue with continuous recovery boot
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
This is exactly what I posted above lol
LOL Sorry. When I flash the TWRP file it just rebooted the phone back into the Hyper Drive Rom I'm using, did it do the same for you?
Thanks to everyone who has provided information and tried to help me! Thankfully, T-Mobile simply sent me a new phone. However, I'm definitely going to keep this topic bookmarked for future reference. This seems to be a rather uncommon problem, considering I had to make a topic to find a solution since all of my searches didn't give me any results.
Thanks again to everyone!
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
I'm having the same problem with my TMobile Note3 after using Kingo after upgrading via Kies to the latest Firmware. The only difference is my phone immediately starts rebooting as soon as I put the battery back in. It doesn't appear that any keys stop this and the USB isn't recognized by my computer in time before the reboot cycle starts.
Is there anything else to try other than sending the phone back for warranty replacement?
tim
Yeah Kingo has given me nothing but trouble, I'd steer clear of that software. I'm assuming you have no access to recovery mode? I have had that issue before on an S3 and was able to finally get it into download mode, but the battery being inserted immediately boots the phone up. So what you have to do is 1. Take battery out and unplug usb cable. 2. Plug USB cable in and Hold download mode buttons with BATTERY OUT (vol+, home and power) 3. insert battery simultaneously while holding buttons down, phone will boot up.. After holding down for about 10 seconds phone will manually reboot, 4. When screen shuts off (potentially vibrates) release download mode buttons, then IMMEDIATELY press and hold download mode buttons again (must perform this step FAST, the key is to do it right before the screen turns on if you can.) 5. The manual boot you've performed should allow you to trigger download mode. I was eventually able to get this to work (about 3 tries. ) I believe your download mode is still intact, you just have to use this method to access it. Remember that because your phone atuo boots with battery inserted download mode will only be available by manual reboot not battery insert.
Give thanks if I assisted you.. Your phone isn't a hard brick so Jtag service should be unnecessary at this juncture.
---------- Post added at 05:09 AM ---------- Previous post was at 05:01 AM ----------
Awesome!! Glad I could be of such assistance
---------- Post added at 05:13 AM ---------- Previous post was at 05:09 AM ----------
R187J said:
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
Click to expand...
Click to collapse
Awesome man!! Glad I could be of assistance!!
Give thanks/thumbs up!
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks
I've dug around trying to find a similar problem here and on google, so my apologies if this has already been addressed.
The problem originally began when the game pad stopped being responsive (or at times took multiple presses to get a response) and after no luck troubleshooting it, I tried to reset from clockwork recovery.
Ever since my phone no longer boots. It just sits on the LUPUS wolf logo (I do not recall exactly which rom I am running, but I hope this helps) and at first I thought it was your normal "this can take a bit" first boot, but I've let it eat the whole battery and it never gets anywhere. I've tried to prompt the phone to boot into both custom recovery and d/l mode and neither get me anywhere. Any suggestions?
Sacrifusion said:
I've dug around trying to find a similar problem here and on google, so my apologies if this has already been addressed.
The problem originally began when the game pad stopped being responsive (or at times took multiple presses to get a response) and after no luck troubleshooting it, I tried to reset from clockwork recovery.
Ever since my phone no longer boots. It just sits on the LUPUS wolf logo (I do not recall exactly which rom I am running, but I hope this helps) and at first I thought it was your normal "this can take a bit" first boot, but I've let it eat the whole battery and it never gets anywhere. I've tried to prompt the phone to boot into both custom recovery and d/l mode and neither get me anywhere. Any suggestions?
Click to expand...
Click to collapse
IMHO, it looks like faulty slider flex cable (exact same situation i had, but i was able to enter recovery after 2 minutes of logo on screen)
Try to power on phone with slider open.
If you can enter in recovery mode with "volume -" (if it light blue led or vibrate) and see is d-pad is working.
Sorry for the delayed reply. The notification went into my spam folder :/
Alright, I followed your steps in two ways. I opened the slider and held both the power and the volume down till I got the buzz buzz and the LED blinked green once and continued to hold volume down till I got the LUPUS logo. No luck. I did mostly the same thing the second time but I held the volume down for 3 minutes with the same result. I still have yet to make it back into recovery.
Sacrifusion said:
Sorry for the delayed reply. The notification went into my spam folder :/
Alright, I followed your steps in two ways. I opened the slider and held both the power and the volume down till I got the buzz buzz and the LED blinked green once and continued to hold volume down till I got the LUPUS logo. No luck. I did mostly the same thing the second time but I held the volume down for 3 minutes with the same result. I still have yet to make it back into recovery.
Click to expand...
Click to collapse
To be able to enter recovery, it is not "holding volume-" while powering on phone or keeping it pressed.
Press power button (and it should vibrate), and release it.
When blue led is on press and release vol- button many times untill you enter recovery (don't keep it pressed all time)
Ah, you are absolutely right. I've never entered recovery like that on another Android before. I loaded up the "near perfect" rom and my game pad seems to be working for now, so it appears I am back in business.
How problematic is it if my slider flex cable is going bad? Will it permanently fail eventually?
Hi,
I have a bootloop issue (I was using LOS official and it crashed when I answered a call) and when I try booting in recovery mode it just starts normally.
I do the Power + Vol down until I see the LG logo then release both for a short time and hold them again but it starts the LOS bootanimation..
What I am doing wrong ?
Emin3ms said:
Hi,
I have a bootloop issue (I was using LOS official and it crashed when I answered a call) and when I try booting in recovery mode it just starts normally.
I do the Power + Vol down until I see the LG logo then release both for a short time and hold them again but it starts the LOS bootanimation..
What I am doing wrong ?
Click to expand...
Click to collapse
The G4 has a really stupid way of entering the recovery. I couldn't get in for a while too. Try again making sure you are actually pressing the buttons together at the same time. That means having just one click. They have to be clicked down at the exact same time.
Also, the instructions you've seen (first Google result) may not be the best. This is what I do WITH a custom recovery (TWRP).
1. Power off completely
2. Holding power and volume down at the exact same time until the lg logo appears.
3. Continue holding the volume down button but release the power button for a second.
4. Press and hold power and volume down again.
5. When asked if you want to wipe the device, select yes. This won't wipe the device but will take you to TWRP (if you installed it). Otherwise, it wipes the device.
htr5 said:
The G4 has a really stupid way of entering the recovery. I couldn't get in for a while too. Try again making sure you are actually pressing the buttons together at the same time. That means having just one click. They have to be clicked down at the exact same time.
Also, the instructions you've seen (first Google result) may not be the best. This is what I do WITH a custom recovery (TWRP).
1. Power off completely
2. Holding power and volume down at the exact same time until the lg logo appears.
3. Continue holding the volume down button but release the power button for a second.
4. Press and hold power and volume down again.
5. When asked if you want to wipe the device, select yes. This won't wipe the device but will take you to TWRP (if you installed it). Otherwise, it wipes the device.
Click to expand...
Click to collapse
Same Issue here, I was on Genisys opened whatsapp cuause I had a new message and phone rebooted.
after that it just stay on LG logo.
I followed your steps and got to the option of factory reset but after I hit ok with the power button phone just reboots back to the LG logo.
I think mine is the genuine bootloop issue.
htr5 said:
The G4 has a really stupid way of entering the recovery. I couldn't get in for a while too. Try again making sure you are actually pressing the buttons together at the same time. That means having just one click. They have to be clicked down at the exact same time.
Also, the instructions you've seen (first Google result) may not be the best. This is what I do WITH a custom recovery (TWRP).
1. Power off completely
2. Holding power and volume down at the exact same time until the lg logo appears.
3. Continue holding the volume down button but release the power button for a second.
4. Press and hold power and volume down again.
5. When asked if you want to wipe the device, select yes. This won't wipe the device but will take you to TWRP (if you installed it). Otherwise, it wipes the device.
Click to expand...
Click to collapse
Ok after a few tries I managed to do it this way
Hi guys, today I've managed to brick my G4 so it doesnt boot neither to recovery nor fastboot nor download mode. It just loops the LG logo as you can see here https://www.youtube.com/watch?v=9gm0dh6bLp4
Any ideas how to recover?
Thank you
Jirrick said:
Hi guys, today I've managed to brick my G4 so it doesnt boot neither to recovery nor fastboot nor download mode. It just loops the LG logo as you can see here https://www.youtube.com/watch?v=9gm0dh6bLp4
Any ideas how to recover?
Thank you
Click to expand...
Click to collapse
If you don't remember doing anything that might have caused this, then it may be the LG G4 bootloop bug.
I'd put the phone in a zip lock back, in the freezer overnight and then back up all my data as quickly as possible. You're phone may be dead.
htr5 said:
If you don't remember doing anything that might have caused this, then it may be the LG G4 bootloop bug.
I'd put the phone in a zip lock back, in the freezer overnight and then back up all my data as quickly as possible. You're phone may be dead.
Click to expand...
Click to collapse
I'm sure I've bricked it while flashing LOS (regular dirty flash of new weekly like i do nearly every week), this time just went something wrong...
As far as I can tell from some YT videos my reboot pattern is different from regular G4 bootloop
Thx for your replies, I managed to revive my phone after whole day of tinkering. Had to overcome some issues so I've posted the solution: https://forum.xda-developers.com/showpost.php?p=73539738&postcount=1
htr5 said:
The G4 has a really stupid way of entering the recovery. I couldn't get in for a while too. Try again making sure you are actually pressing the buttons together at the same time. That means having just one click. They have to be clicked down at the exact same time.
Also, the instructions you've seen (first Google result) may not be the best. This is what I do WITH a custom recovery (TWRP).
1. Power off completely
2. Holding power and volume down at the exact same time until the lg logo appears.
3. Continue holding the volume down button but release the power button for a second.
4. Press and hold power and volume down again.
5. When asked if you want to wipe the device, select yes. This won't wipe the device but will take you to TWRP (if you installed it). Otherwise, it wipes the device.
Click to expand...
Click to collapse
OH MY GOD. It still doesn't work, I am tired and out of my mind, I tried many many times, Idk what else to do. I will try again and again but I am just becoming more mad instead of fixing the problem. DAMMIT
Eldpool said:
OH MY GOD. It still doesn't work, I am tired and out of my mind, I tried many many times, Idk what else to do. I will try again and again but I am just becoming more mad instead of fixing the problem. DAMMIT
Click to expand...
Click to collapse
Hmm, wait, ok. I did it finally, you just need to press them simultaneously and then when LG logo appears just release the power button for literally 1 second and then press and continue to hold both of buttons. That's it.
Eldpool said:
Hmm, wait, ok. I did it finally, you just need to press them simultaneously and then when LG logo appears just release the power button for literally 1 second and then press and continue to hold both of buttons. That's it.
Click to expand...
Click to collapse
This actually worked!!!!....The 1 Second is crucial in the process, I did it on my first try after reading post
I did the procedure but it went to a page that said clear your phone or not! Just it, and there is no option to clean cache partition or any other
First off, I did do a search, but as far as I can tell no one has had this problem so far.
This is all after modding using a tool kit: (i can't include the url but it is the toolkit by neisor on the oneplus forums)
tldr: phone stuck in bootloop, computer wont recognize the phone, maybe because it keeps shutting off and then booting to the 1+ logo, then shutting off again, would drivers help? what can I do about the volume up button?
So for a while my volume up button hasn't been working, and the mega unbrick post shows that I need to hold the volume up button for at least 25 seconds and while holding, plug my phone in. I have also seen some posts that say the volume up button could be a software issue, and the button itself could be working, and it is just not registering, as well as someone saying that you could take the back off and manually press the button, instead of using the bar on the outside of the phone (would this work?). I have gotten the button to work in the past by pressing the volume up button to the side instead of straight in, but I haven't been able to get it to work since my phone got bricked.
Another issue: my phone is stuck in a boot loop, I can't access fastboot, and I'm unsure of recovery because my volume up button is not working. would it be worth it to deal with the constant vibrating to try to get it to recovery?
I have been able to shut the phone off by holding the power button for something like a minute and a half, though.
This is my first post, and if I have broken any rules I am very sorry, but I need help and am tired of not having a phone.
Thank you everyone,
Mark
Edit: this is what I did to root the phone:
1. download the toolkit
2. unlock bootloader (when fastbooting the phone said unlocked at the bottom, and a message about not being secure showed every time I rebooted the phone)
3. flashed twrp (no issues, still booted, recovery went to twrp. for some reason I had to flash multiple times as every now and then recovery would revert to stock op, although I did make a backup through twrp)
4. send supersu zip file to phone, install using twrp (phone would not boot, op logo stayed on phone for 2 hrs + until I rebooted to fastboot and tried to reinstall the backup I made, still nothing)
5. Try magisk (still stuck on op logo)
6. try to go back to stock, accidentally lock bootloader (now the phone is stuck in bootloop, don't know what to do from here as I cant get to fastboot and am unsure of recovery's accessibility.)
If you are sure you have a broken volume button, you need to replace it first in order to get the phone fix.
Correction:
Fastboot/bootloader = Power+Vol Up
Recovery = Power+Vol Down
This happened to me except I didn't even get anything appear on the screen -- the phone just periodically vibrated with the screen not even light up. I tried the reset toolkit which is meant to flash your phone back to normal using Qualcomm drivers or something, but that didn't work either. Eventually I had to send it to OnePlus who fixed it for free in under a week! They said the motherboard had failed.
I hope you get this fixed!
Thanks
150208 said:
If you are sure you have a broken volume button, you need to replace it first in order to get the phone fix.
Correction:
Fastboot/bootloader = Power+Vol Up
Recovery = Power+Vol Down
Click to expand...
Click to collapse
thanks for the correction, I will keep trying the volume buttons, if it doesn't work by the end of today I will search for a new volume button.
Thanks again,
mark
Ouch
badabdba said:
This happened to me except I didn't even get anything appear on the screen -- the phone just periodically vibrated with the screen not even light up. I tried the reset toolkit which is meant to flash your phone back to normal using Qualcomm drivers or something, but that didn't work either. Eventually I had to send it to OnePlus who fixed it for free in under a week! They said the motherboard had failed.
I hope you get this fixed!
Click to expand...
Click to collapse
Damn, that sucks, and besides being unfixable (doubt it), this is my biggest fear. I'm in the US and really don't want to have to ship my phone to china to have it fixed. If you are in the US as well do you know if there is a OnePlus branch I can send it to in the US?
Thank you,
Mark
MarkTheFur said:
Damn, that sucks, and besides being unfixable (doubt it), this is my biggest fear. I'm in the US and really don't want to have to ship my phone to china to have it fixed. If you are in the US as well do you know if there is a OnePlus branch I can send it to in the US?
Thank you,
Mark
Click to expand...
Click to collapse
There seems to be one in Texas. Anyway, contact OnePlus and they may try to solve it over the air.
Apart from that, did you install the Qualcom drivers properly? Even with your faulty power button, try to hold it down for 40+ seconds (for the phone to switch off) and then immediately hold down the volume up button for 10 seconds and then plug in the phone to the PC. I know I am merely repeating the instructions of Naman Bhalla in his Mega Unbrick Guide but it is crucial to do them correctly especially the installation of the drivers. Try these steps repeatedly because for some people, the phone gets recognised after repeated attempts. Or else replace the power button and then try these steps.
I had to use the Guide last month and successfully resurrected my dead phone.
MarkTheFur said:
... what can I do about the volume up button?
Click to expand...
Click to collapse
Can you boot into recovery by pressing power+volume down buttons?
Update: Got phone to show on computer as qualcomm under coms and ports
So last night I went ahead and held volume up for about 20 seconds, then plugged the phone in, keeping the volume up button pressed the entire time. my phone stopped bootlooping and showed up as a qualcom device! So I have downloaded the new driver the stock os, and am going to proceed to try to unbrick my phone.
Wish me luck,
Mark
Yes, I did, and its working so far
tnsmani said:
There seems to be one in Texas. Anyway, contact OnePlus and they may try to solve it over the air.
Apart from that, did you install the Qualcom drivers properly? Even with your faulty power button, try to hold it down for 40+ seconds (for the phone to switch off) and then immediately hold down the volume up button for 10 seconds and then plug in the phone to the PC. I know I am merely repeating the instructions of Naman Bhalla in his Mega Unbrick Guide but it is crucial to do them correctly especially the installation of the drivers. Try these steps repeatedly because for some people, the phone gets recognised after repeated attempts. Or else replace the power button and then try these steps.
I had to use the Guide last month and successfully resurrected my dead phone.
Click to expand...
Click to collapse
I still need to turn off the signed drivers features ( a huge bi*ch, I have to use another computer to contact microsoft or something to get my computer to load when I turn off safe boot or whatever its called), but once I do that I can install the driver and attempt to reinstall the stock os. Hopefully everything will go well.
Thank you,
Mark
Not as far as I know
rk2612 said:
Can you boot into recovery by pressing power+volume down buttons?
Click to expand...
Click to collapse
So far recovery has not been loading, just the bootloop, but I have gotten the phone to power off by pressing the power button for 40 seconds, and the volume up button plus plugging in does make the phone register as qualcom 9008 or something like that. Basically everything is going well so far, and the faulty vol button seems to have been a software bug, as it does work when plugging it in. I will try to get to fast boot, but it did not work last time.
Thank you,
Mark
MarkTheFur said:
So far recovery has not been loading, just the bootloop, but I have gotten the phone to power off by pressing the power button for 40 seconds, and the volume up button plus plugging in does make the phone register as qualcom 9008 or something like that. Basically everything is going well so far, and the faulty vol button seems to have been a software bug, as it does work when plugging it in. I will try to get to fast boot, but it did not work last time.
Thank you,
Mark
Click to expand...
Click to collapse
Glad to hear that there is some progress. Best of luck and keep us informed.