Related
Couldn't find a similar thread so I thought i'd post my problem.
Beginning last night, after watching a video using Pulse I realized the sound wasn't working. I restarted the Nexus 7, had the sound working again, but the device froze during the video (in pulse), and then reset on its own.
Since then, the Nexus 7 will reboot, then once on, will freeze after 30 seconds - 2 minutes, reboot again, and just loop in that pattern. Sometimes when it turns out, I'm not even able to unlock it before it reboots again.
Even if I turn off the Nexus 7 when I get the chance, it will turn on itself and continue the freeze -> reboot loop.
Right now I've been letting the loop continue until the battery runs out to see if it fixes the problem. Until then, has anyone else faced this issue? Any solution?
Details: An unrooted Nexus 7, few apps, only thing off market was to enable flash, got the device 2 weeks ago
Bump to see if anyone has a solution.
Will post a video of what happens when I get home from work.
Haven't heard of this before.... what happens if you boot into bootloader? Perhaps you just need to do a full wipe and re-install.
It actually freezes on bootload.
When I do a force turn off (power and volume down), it will turn off, then turn on by itself and continue the bootloop
Will try to upload a video of what is happening soon.
I have the exact same issue.
Can't restore or reflash because it won't go into bootloader\recovery.
What it WILL do is reboot incessantly. SUffice it to say I'm pretty pissed. This just happened suddenly.
I had not rebooted in a few days so I rebooted, and now it won't stop.
The only change I have made is I disable the magazine app because I read that it's a battery hog and I just do not use it. I can;t imagine disabling the magazine app would result in a full on boot loop where even recovery fails...
-M
I would reflash recovery while in the boot loader through adb. That is what fixed my similar problem
kevlars9 said:
I would reflash recovery while in the boot loader through adb. That is what fixed my similar problem
Click to expand...
Click to collapse
I have the same kind of issue. Left to itself the device reboots until the 'Google' display every 1 minute or so. When trying to get into bootloader it freezes when the Android on its back shows up....
So it seems no flashing is possible. BTW this happened when I tried to uninstall an app, similar scenario to some others reporting this type of problem.
I guess the next stop is the Chocolate Factory helpline :/
I contacted the Googleplex helpline at 6 am Pacific time and Anthony kindly promised a replacement unit for next week... No tech explanation or other info was revealed. Purchase from Google Play in the UK.
Finally given a solution, though a very annoying one.
Basically, since you have about 30 seconds - 2 minutes everytime it loads up, I was just told to try and see if I can factory reset from settings within that time frame. Took a 3 attempts (sometimes it would reboot while loading), but eventually got the factory reset going. Luckily I've only had this thing for less than 2 weeks and didn't have much stuff needed to back up.
Right on, glad to hear you got it sorted - in my case. though, this solution would not have worked, as mine never booted all the way through but got stuck at the boot logo (just in case others are reading this with similar problems). So it sems there are at least 2, possibly more, problem scenarios of this type.
My replacement unit from Google Play just arrived - impressed by the speed of proceedings (inside 2 working days from reporting to receiving in Scottish Highlands). Let's see how this one pans out...
HEy problem plss help Boot loop on N7
Hey my nxus wint get out of a boot loop and i cant get in to recovery mode by bootloader this have ben going on for some time and it started when i flashed a new rom ( Paranoide android )on my Nexus 7:fingers-crossed:
Eternal 2013 Nexus 7 reboot loop
Last night my Nexus 7 2013 started going into a reboot loop and would not stop no matter what efforts I made to stop it.
It started when the Billguard application tried to apply an update. The update gets halfway and then forces the tablet to reboot every 30 seconds. I tried disabling the Wi-Fi to stop the update from happening. I even disabled automatic updates and the reboot still happens restoring the tablet to its previous state. I even tried uninstalling the application which appeared to be successful but then immediately rebooted the tablet to the previous state.
After calling Google tech support and only receiving minimal efforts to stop the tablet from rebooting. All efforts were unsuccessful. I even tried uninstalling the application which then instantly rebooted the Nexus seven and attempted the update agaian forcing it back into the reboot loop.
I then tried to do an android device manager erase which was not acknowledged or completed even when my Nexus 7 goes online.
Any help would be appreciated.
Thanks,
I have a very similar problem. However, it began from no changes to my system. I am on Legolas' All-F2FS Recovery and the SlimKat F2FS system. At first I got stuck in a boot loop, and could get into fastboot, but cannot boot back to the custom recovery. Now, I get past the bootloop but cannot get past the loading screen, and still cannot get into recovery. I've tried wiping cache, I've tried reloading the recovery via fastboot -- but since all I have is fastboot access, I don't know what else to do. All my partitions are F2FS, so I am afraid to try moving back to any standard ext4 recovery. I am very interested in this thread, as I feel our issues are related. Keep me updated, and I will do the same if I find anything useful.
Any help I suspect is appreciated by more than just myself.
BTW, removing back and leaving battery unplugged for a while (which had helped with other bootloop issues) did not fix this one, nor did the cold boot from fastboot with usb plugged in to boot recovery.
superdave132 said:
Last night my Nexus 7 2013 started going into a reboot loop and would not stop no matter what efforts I made to stop it.
It started when the Billguard application tried to apply an update. The update gets halfway and then forces the tablet to reboot every 30 seconds. I tried disabling the Wi-Fi to stop the update from happening. I even disabled automatic updates and the reboot still happens restoring the tablet to its previous state. I even tried uninstalling the application which appeared to be successful but then immediately rebooted the tablet to the previous state.
After calling Google tech support and only receiving minimal efforts to stop the tablet from rebooting. All efforts were unsuccessful. I even tried uninstalling the application which then instantly rebooted the Nexus seven and attempted the update agaian forcing it back into the reboot loop.
I then tried to do an android device manager erase which was not acknowledged or completed even when my Nexus 7 goes online.
Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
I found a fix that worked for me!
I have Minimal ADB & Fastboot installed on my computer. If you're comfortable with the idea of connecting to your Nexus when it is in bootloader download (Fastboot mode), you can try this.
First, I downloaded a full reset file from https://developers.google.com/android/nexus/images:
The ones you'll want are either:
this one for 4.4.2
this one for 4.4.4
I unzipped the appropriate one directly into my ADB directory, and then executed the "flash-all" script by literally typing in "flash all" into the prompt.
This installed all of the default bootloader, recovery and system back onto my Nexus 7 (btw two names for the nexus are "Grouper" and "nakasi"). Then, I was able to clean boot into a reset Nexus 7 system. It was still unlocked. From there, I was able to reinstall a custom recovery (I went with TMW), and even reinstalled a custom ROM (I always stick with SlimKat, personally).
Note: You should also wipe data from the custom recovery once you've installed it.
Second note: In order to be able to load this stuff, I believe you have to unlock your system
To unlock your system in fastboot: fastboot oem unlock
I sincerely hope this helps you (and anyone else stuck in a similar situation to where I found myself). I had completely set my system up with F2FS, and now I'm back to EXT4. BUT, I have a custom recovery, custom rom and root access. Can't complain.:highfive:
Hello XDAers,
I am a real noob at rooting or android-related, and a true one voided of any knowledge regarding anything IT- related.
So dear veterans, please go easy on me.
Due to my prior success of rooting and flashing my Nexus 4 successfully a few months back with no issues, I decided to give it a try to flash a custom ROM for my dad's LG Optimus L7 - which seemed an easy task compared to configuring my Nexus 4 - since there was no need for inputting any command lines or any dealing with the abd (using the easy shortcut, that is).
So, I followed the guide here: http://forum.xda-developers.com/showthread.php?t=1906133 ...
I first factory resettled the phone because it was bloated, then applied the "RunMe.bat" from the "What you desire!" folder. (Everything was already backed-up beforehand.) But the process didn't success until I've retried again and again by re-plugging the USB in because the application/PC couldn't detect the phone. In the same time, I was running KDZ_FW_UPD.exe in the background, so unexpectedly for me the phone shut itself and pushed itself to a vividly green emergency screen, then in a few seconds switched back to a screen of purple-white-blue glitches. I had to close KDZ_FW_UPD.exe without knowing what quite happened since it seemed to be the cause and restarted the process with RunMe.bat.
I didn't manage to "Restore" it first due to the fact that the phone stopped responding due to a lag asking for an encryption key. It was lagging so hard and I had to close the cmd around 5 tries while it was processing, but succeeded later on.
And then, to verify whether I've actually suceeded in rooting L7, I installed Root Checker from the Play Store. And again, for the first few tries the program froze on screen for a long period of time due to "system performance", but after rebooting and restarting the app a few times again, the ROOTING proves to be a success. Just to be sure, around this time I've reloaded KDZ_FW_UPD.exe and it suceeded.
So I went to install CWM and ES. CWM for recovery boot and ES for removing pre-installed system apps as the phone was lagging so badly. I've downloaded the CWM restoring(something like ~6.0.28?) first and tried fastbooting immediately right after, but instead of getting the fastboot menu I got a screen emptied in black with these words:
[5020] "Secure booting error"
[5020] "Cause: boot certification verify"
No hard keys could do anything on the presumed "fastboot", and so I had to hard boot again. I thought that it might be due to the lack of memory(checked on ES later on that it was 310~MB/2GB), and so I've used ES to uninstall a lot of system apps which I deemed uneccessary. So I've Googled a bit and it became apparent to me that that I've didn't unlock the device properly, so lurked around and found a file called L7CWM that is supposedly to resolve my problem, but I presume that it's the CWM recovery image that I've installed. So in the end, I didn't bother with it but kept it on tab just in case.
I repeated the same process with CWM again, but this time, the screen was joined with all kinds of flowery glitches. Restarted the device, and it went only downhill: now the Home launcher stayed all pitch black and nothing appeared. I waited a few minutes, but nothing there until the notification bar appeared. The home screen is apparently dead, and so are the menu keys. Switched to Nova Launcher(installed it just in case Home Launcher fails), and still dead. I couldn't access using any of the menu keys and had unusable launchers.
Hopefully I could still access to the settings from my status bar, but when I did, it started crashing immediately.
I've repeated the attempt a few times after restarting the device a few times, but nothing helped. It only got worse that the when the launcher did SEEM to work. It only showed the wallpaper without showing any of the icons/apps. And crashes again.
I could still access to the App menu via the settings, but couldn't open any of them and when I tried to uninstall them, the screen frozes immediately right after I gain access to the page (white page though) and gain this message: "Unfortunately Package Uninstaller Stopped!"
Then I convinced myself that the only thing I could do at the time was to factory reset the phone and then everything would go alright since I've just had to restore the system apps.
But then the black screen of death came right along with it:
"Secure booting error"
It seems that I'm out of luck... ... But just to check if I'm still left with resorts, I've downloaded the L7CWM file online...
... ...but it still didn't help.
So now I'm being left with no other choices other than asking for help. I never really understand what KDZ_FW_UPD.exe does since I had the LG Driver already before installing it, which I presume was for updating the phone to a newer or older version. And too complex tech articles are kind of alien for me.
EDIT(1 hour later): Okay, now I figured out the reason why L7CWM didn't work was because I didn't extract it to the right folder (after double checked via notepad that I was supposed to directly put it into the C:\ drive). Now it worked(?), but then it didn't.
After launching Flash_Bootloader.bat:
This message now appeared on the L7:
"Sorry!"
"SuperSU is not responding.
Would you like to close it?"
"Wait - Report - Close"
and a few minutes later
"Sorry!"
"Unfortunately, SuperSU has stopped."
"Report - OK"
Now I think the bugs till now happened was due to the fact that I've deleted a file that was required for me to launch apps... Now I just need the right fix.
After 5 minutes of screen inactivity the phone restarted by itself, kind of creepy... ...
Flash_Recovery.bat did nothing.
Reboot2Recovery.bat made it reboot but still struck on the same menu.
Nothing seems to be effective via the phone anymore, seems like I have to rely on abd but then again I don't know how... ... My dad is also f*cking pissed off ^ ^;...
__________________________________
I think that I explained the logs pretty precisely in case I missed something... I'll be very very very very very very thankful if someone could tell me what has caused my phone to fail though.
For references, here are the phone's specifications:
Model Number: LG-P705g
Android version: 4.0.3 (Stock)
Rooted:Yes (root checker)
Baseband version: MSM7227A-1-AA
Kernel version: 3.0.8-perf
Build number: IML74K
Software version: V10e-AUG-10-2012
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
remove the battery for 10 seconds,put it back pres VOL+ and VOL - same time and than press the power button.when you feel a vibration press for many times the button wich is down in right,try for many times and maybe it will working :}
Cydes said:
Hello XDAers,
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
Click to expand...
Click to collapse
simple answer for your
just download your stock rom
go to emergency mode
and flash that stock rom
Hi everyone!
From about 2 weeks i have the weirdest issue i have ever encountered with my mb525 defy in 3 and a half years that i have it. Since I have always managed to solve bigger problems without too many problems or questions, this time I came to a dead end, so I need your help.
About 2 weeks ago I flashed the new nightly (one of the first of november, unified mb52x version) using the usual installation procedure. Upon restart, the device remains stuck on bootanimation (battery can charge after a while). After a bit of unsuccessful hacking I decide to do the factory reset and wipe system and decide to do a clean install of the rom, but the problem still here. At first I blamed the launcher the cause of the problem, so I flashed another launcher, rebooted the device i came stuck on "Android is upgrading... - Starting apps." message (the same of "Optimizing apps"). Remade all wipes and tried 2 older builds (mb52x always), with no luck again. I tried the hints from the user hendrikmerkel, flashing an mb526 version of the rom (the only i founded on external sources is cm-11-20141004-NIGHTLY-mb526 build). This time instead of getting stuck on bootlogo, the message "Android is upgrading... - Starting apps." reappears, but this time with consequent restart of the device.
Also tried to flash again new bootstrap and resize script, first by recovery (flashed new_bootstrap.zip, rebooted, flashed resize.zip, rebooted and flashed the rom) and after by twrp internal terminal emulator and by adb shell (i don't have a certain confirm of his success, no message achieved at all after executing the commands from quarx's recovery installation guide).
During my attempts to exhume it I tried several times to enter the bootloader, but the screen remained black and rsdlite didn't detect it as it should (friend's defy+ on new bootstrap instead can be detected), and after a minute the device reboots by itself, but this time bypassing the bootstrap screen. I tried also the MacGyver method to bomb him a few additional volts on it (without keeping it set too long), and charged the battery to 100% to be sure that it wasn't a problem related to the charge (the battery is 3 months old) and once again no way to recover it. Finally i tried to use them both (macgyver + usb connected) and try to imagine it...
I have an hard-bricked device...I have exhausted all possible ideas. What I ask is to give me some more suggestions to revive it. I strongly believe that it is a software issue, most likely related to the new bootstrap. Maybe reverting the new partition sizes could be a solution. Any suggestion will be very valuable for me and for my long-lived experience with this immortal milestone
Thanks in advance all those who will give me a big hand.
McGyver method wasn't really that necessary... anyway, there're ways your phone can be detected by RSDLite, I don't think it's hard bricked. Next time flash 9-23 nightly until there's a reasonable stable one with new table partition. If you can't enter bootloader try pulling out the battery then reinsert it while holding volume up key.
DiegoxG said:
McGyver method wasn't really that necessary... anyway, there're ways your phone can be detected by RSDLite, I don't think it's hard bricked. Next time flash 9-23 nightly until there's a reasonable stable one with new table partition. If you can't enter bootloader try pulling out the battery then reinsert it while holding volume up key.
Click to expand...
Click to collapse
In fact, this is precisely the problem...once entered the bootloader I just get a backlighted black screen, without the usual writings that appears once you release the keys. Once happened a similar thing, but the bootloader worked and rsdlite detected it. This time instead just looks dead...
Anyway, if i install an original bootstrap rom (cm-11-20140923-NIGHTLY-mb526.zip according to your suggestion) the prompt give me an error :
Code:
set_metadata_recursive: some changes failed
[COLOR="Red"]E:Error executing updater binary in zip '/sdcard/AAA/CM11/cm-11-20140923-NIGHTLY-mb526.zip'[/COLOR]
Error flashing zip '/sdcard/AAA/CM11/cm-11-20140923-NIGHTLY-mb526.zip'
I begin to think that the cause of the problem is due to a conflict with the partitions...but how could it have happened
UP...
So, I installed this new rom: Commotio Android 6.0.1 and with it the latest open gapps for Android 6.0.
I rebooted the device and everything was fine and I got to the setup wizard, chose the language, chose the wifi, but after chosing "No thanks" when asked if I got another device, it just says that "Google play services has stopped working".
The thing is, that I can't get to recovery, or I would've flashed another gapps package. I mean I can fix it all by going to download mode and flash stock rom then go back to my custom rom. But that just takes longer and I don't have the time right now.
Edit: By experience I know this problem is caused by the Gapps package. Because I've solved it many times before by flashing other Gapps packages
Is there a way I can just bypass the setup wizard??
OK, I figured this by (accidently) rebooting into safe mode. I did this by turning the phone off, holding power, volume up and down buttons and releaasing only the power button when logo shows up. Then I continued normally with the setup wizard but it didn't ask me a couple of things, witch actually made it work!
Remove sim card and reboot without connect to WiFi and when to choose mouthed of internet connection do not choose ethir WiFi or mobile data that work on miui ROM and all lp stock ROM (normally I do not install gapps with aosp because I love to try fast experience of android)
I saw it pop up on the stable channel. I waited a few days, checked here and saw nobody complaining so I went for it. Recovery saved it, so no big deal, but still killed about 20 min. 20.4 has been working fine for me.
similar result, updated and just made the phone crash at boot; restored and I guess no more updating for the meanwhile
21.3 still has the same crash.
tdusen said:
21.3 still has the same crash.
Click to expand...
Click to collapse
I confirm - crashed on boot. But I am not sure that the reason is Magisk itself, may be the Magisk Manager is the reason ....
21.0 works all after do not.
Bricked my V20 VS995 this morning trying to update to 21.4. Notification had been nagging me for a week and I finally gave in, now my device has a gray screen with very small text, and at the top it says "LGE Crash Handler: Crash on the LK!". I cannot get into TWRP, and a factory reset has no effect. Still no boot into Android.
I was just talking to my girlfriend yesterday about how it was getting time to upgrade. Careful what you wish for, I guess.
that's why I finally turned off the update notification.
Have you tried booting into recovery by the holding keys method?
Assuming you have TWRP installed
hold vol down and power.
when the LG appears, release power the press and release power (one time) while still holding vol down.
you boot to the factory reset screen. select Yes twice
that will boot into twrp
Same here, updated Magisk and bricked my V20 H910.
Then I've used TWRP to try to queue install the following zip :
1 - H910_20h_Oreo_full_rooted
2 - H910_v2.2-mk2000
3 - Magisk-v19.3
4 - Hide_warning-att
Back to Oreo setup, all good even if datas are lost. Then again I've updated Magisk (was not really sure it was because of that, should have read here first!) and same problem, the unfamous "Crash on the LK!". Magisk killed my phone, again.
So I was ready for another run (but the magisk update of course). Stupid me.
I know can't even acess the recovery tool, ok for the Down/Power then Power to get the first recovery prompt and then the confirmation but no TWRP but the crashed multi-colored messy pixel screen and boot again to Crash LK screen.
I have no clue of how to get out of here, guys any help is more than welcome!
Anyone install 23 yet?
I don't see 23 on the Beta channel, nor on the stable channel.
I have 22.0 installed and running fine.
Does anyone have 22.1 installed? Is it fine?
i had an app update waiting for me 23 installed fine on note 3 and on my v20