[Q] Stuck in "Safe Mode" since 4.3 update - Nexus 7 Q&A, Help & Troubleshooting

Hi everyone,
I have an original N7 (Tilapia) and ever since updating to the 4.3 update, my Nexus has been stuck in safe mode.
I've tried shutting down and restarting the device several times. In the end I gave up and did a full stock image install, erasing everything (I have a Nandroid backup, so not too worried). Literally, the Nexus is back to full factory conditions (no root, no unlock, no custom recovery).
However, even that does not seem to have achieved anything. I am still stuck in safe mode. Is there any way of getting out of this or working out what is causing the problem?
Any help would be greatly appreciated!
Thanks

Well, safe mode is caused by holding both volume buttons while starting, so I'd try to boot in to safe mode again to possibly get out of it.
Sent from my Nexus 7 using xda app-developers app

Here are the instructions right from google not a google search but NEXUS 7 help.
Safe mode access
Reboot to safe mode
If you’re experiencing issues - such as apps crashing, reboots, or fast battery drain - on your device, they could be caused by a third-party app. To check if this is the case, you can start up your device in safe mode, which temporarily disables third-party apps that you’ve installed.
Ensure your device's screen is on, then press & hold the Power button.
Touch & hold the Power off option in the dialog box.
Touch OK in the following dialog to start safe mode.
Try using your device in safe mode to see if the problem persists. If it doesn’t, restart your device to get it out of safe mode and uninstall recently installed apps to see if you can pinpoint the one that’s causing the problem.

Related

[Q] Nexus 7 Boots, Loads Some Apps, Reboots...Repeats Forever

Not sure what's going on here.
My Nexus 7 has recently begun a reboot-load OS-load apps-reboot cycle that I'm at wits end to fix.
I've tried uninstalling some apps that I thought might be the cause (AutoShare and Tablified HD Market), but whenever I remove them, the next time the tablet boots up, they are still there.
I've also tried to get into safe boot mode while the tablet is booting. The dialog pops up for the Power Off option, I hold that until it prompts me for a Safe Boot, I tell it OK but still the tablet reboots as normal with the same apps loaded as usual.
Also, I was previously rooted and unlocked, but the last Android update torpedoed that, and because my USB port doesn't work, I have no way to reinstate my root. As a result, I have no Recovery, which eliminates a couple of other options.
Oh, and I also tried to do a Factory Data Reset, but in the same way that it won't recognize the deinstallation of apps, the Factory Data Reset is not working.
Anyone seen anything like this before? Any suggestions?

[Q] Reboot, but not in Safe Mode

Is there anyway to reboot the Nexus 10 without going in Safe Mode? Or if you already rebooted into Safe Mode, can you reboot back to Normal Mode?
So far I've had to Power Down to restart Nexus 10 without going into Safe Mode.
The reason I've had to do this is that I've been having a wake up lag issue. Happens every now and then and I think it has something to do with automatic app updates, but not sure. So maybe this is a two part thread.
There's no reboot option on the N10, I'm guessing you're rooted?

[Q] Did Verizon Security Warning hard brick my phone?

Hey everyone,
Long time XDA forum user, first time poster. I can usually find what I need through searching, it seems people generally get into a soft brick scenario with this Verizon recovery blocker screen. I do now see that I did act a bit brash, and should have searched more about the knox counter before rooting and installing another rom.
Here are the steps that I performed to get into trouble:
Ran Vroot from my PC to obtain root
Installed SuperSU, updated bianaries in that app, uninstalled Chineses root apps
Tried to install CWM from Rom Manager, rebooted, got the Verizon security warning
Realized that recovery would not work, installed safestrap from APK
Installed hyperdrive in Rom slot 2, set to boot to that ROM slot
So I guess I made a few mistakes. I should never tried to install CWM, I should have somehow disabled/reset the knox counter?, and I should have installed Hyperdrive in the stock rom Slot?
I was hiking and using a GPS navigation app (in airplane mode). I look down and my phone is at this Verizon recovery blocker screen, "System software not authorized by Verizon Wireless...". Now, I would be fine if I could get to odin/download mode, but no matter what key combination I use, it always brings me to that same stupid screen. I have tried volume down+home+power, volume up+home+power in combination with removing the battery for 10-15 seconds, and not being plugged in and I am out of ideas. I have not been able to boot to download mode whatever I try. If I can get there I should be able to take care of the issue. Any ideas? Is a usb jib my last hope?
Also
Also, I was still on 4.3. I had not taken the OTA update to 4.4. That is what was prompting me to get another ROM installed.
Any insight would be appreciated! Is a USB jig my only hope to force the phone into download/odin mode?
joefbtg28 said:
Any insight would be appreciated! Is a USB jig my only hope to force the phone into download/odin mode?
Click to expand...
Click to collapse
I presume you did the Vol Down/Home/Power keypress from full off....correct?
Sent from my Note 3 via Tapatalk
Try full power down then pull battery. wait a few and reinsert battery. then try key combination above.
Sent from my SM-N900V using XDA Premium 4 mobile app

Stuck in BootLoop and Factory Wiping doesn't actually wipe anything

Nexus 7 (2012)
4.4.4 Stock
KTU84P
HW Version - ER3
Bootloader Version - 4.23
Locked Bootloader
Not Rooted
I have a Nexus 7 sitting in front of me that was dropped off by my aunt in hopes that I could repair it for her. It doesn't look too promising, but I thought I'd consult the mighty fine people here on XDA before I give her the bad news. Here's what she says happened. Yesterday, while preforming day to day activities on it (browsing internet, Skyping, Facebook, etc), the device completely froze. After holding down the Power Button and forcing it to shutdown, she booted it back up. Everything seemed to functioned properly for about 30s - 1min when, at that time, the device turned off and rebooted on its own. After booting back up, it started to repeat this cycle. Basically getting stuck in a bootloop. I personally have never witnessed a bootloop like this before, where the device successfully boots up completely into the OS before turning off and repeating. I'm more used to dealing with ones where it might go as far as the manufacturer logo and then repeats. So anway, as I stated, I only have a 30s - 1min window where I can make changes in order to troubleshoot. The first thing I figured I should do was to go into "About Device", turn Developer Mode on and get USB Debugging enabled. I was able to do this and used "adb devices" to confirm its connection to my computer before it looped again. After its next bootloop I headed back into settings because I wanted to take note of the Android version she was running. As I was navigating there, I noticed that the Developer Options were no longer active. Basically as if I hadn't enabled them yet. This made me start thinking that changes being made on the device weren't sticking. I decided to make a few visual changes to the home screen and see if they were still there after the next bootloop. I uninstalled an app, rearranged icon placement, and changed the wallpaper. Once it shutdown and booted back up again, everything was back to the way it was before the changes had been made. The app I had uninstalled was still there, the wallpaper reverted back, and the icons were back in their original location. At this point I decided to see if I could reboot into Safe Mode. Unfortunately, this doesn't work. I am able to get the reboot to Safe Mode confirmation box and tap "Ok" but it remains in Normal mode when it boots back up. I eventually tried to boot into recovery and preform a Factory Reset. I was able to get into recovery and reset the Nexus. Or so I thought. Instead of seeing a Device Setup screen after it wiped, like I assumed I would, it booted up and still had all the data on it. There were no errors during the wipe and it was confirmed with "Data wipe complete." afterwards.
I am absolutely lost. I've never dealt with such an unusual issue before. Especially with it not even reacting to a complete data wipe. So, just to recap . . . I only have 30s - 1min available to interact with the OS before it reboots itself, any changes made during that time don't stick, Device is successful booting into Stock Recovery, and I can successfully get a Fastboot connection when booting to the Bootloader.
Luckily she has come to terms that this might not get fixed and has decided to go a head an order a newer 2013 model. I'd still like to try any solutions that you all might have. Just in case there is a slight glimmer of hope.
Oh, and one last thing I should mention. I tried to see if I could get the bootloader unlocked but it didn't work. This is the first Nexus I've ever had in my possesion, so I'm not really familiar with the tools available for it. I found WugFresh's Root Toolkit and attempted to Unlock with it. The process seemed to go as it should and I didn't receive any errors on the tablet or in the software. However, in the end, it didn't make any changes to the bootloader.
same problem
I have the same problem as you.
Did you find a solution?
Can anybody help us?
Thanks.
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
eawooten said:
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
Click to expand...
Click to collapse
I have tried factory reset from recovery, no errors while wiping but when device restarts nothing has happened: I only have a 30s-1min of old system with all my data and apps or directly bootloop.
Also I have tried flash factory images with Nexus Tool Kit and directly from bootloader. No errors while flashing, apparently has flashed new image system. When device restarts nothing has happened: bootloop or my old system with data and apps for 30s before restart.
Myself and a few others are having the same problem... please keep us updated if you find anything out.
http://forum.xda-developers.com/showthread.php?t=2588911

Recovery from bootloop (and other issues)

Ok, so... this is gonna be quite long to tell, but I need to explain the situation as carefully as possible because the problem I have seems to be very specific and potentially solutionless.
So, a week ago my Samung Galaxy Tab S6 Lite (SM-P610, CSC: ITV, which is the Italian Country Code and it's for unbranded devices, since my model is Wi-Fi only), suddenly started to restart itself and it's been stuck for days in a bootloop (i.e. it's stuck on the logo and if I hard restart it with Volume Down + Power, it gets stuck there again). Yesterday I found out that it's most likely a software problem, so re-installing the Android version should fix everything up... right? Well, I did just that but the device is still stuck on the bootloop.
Here I want to be more detailed: firstly, I'm 100% positive that the problem I have is NOT due to a virus, as I've never done ANYTHING that could potentially lead me to taking a virus (such as downloading apps outisde Google Play, visiting risky sites etc.); secondly, I followed a procedure that was supposed to repair my device without losing data. That's because I've stupidly never made a backup and I can't afford to make a factory reset. The procedure I followed consisted in finding the Android update I needed with Frija, and then downloading everything in the tablet with Odin. Also, I'm 100% positive that I made NO mistakes during the installation procedure. The only step that I did differently is HOW I installed the update: I did it with Download Mode, not with fastboot, because when I go into Recovery Mode and reboot the device into bootloader, the PC doesn't recognize my Tab, even if the PC does recognize that it's connected, as it makes the typical sound of when you plug something in a USB port (I have the USB drivers installed in my PC, I think it doesn't work because I never unlocked bootloader). What I get when I reboot into bootloader is "entering fastboot..." stuck screen and the PC and Odin aren't able to recognize it.
My questions are therefore these:
Is there a way to make a backup of the data of my device if I can't boot it (maybe via Download Mode)?
Is there a way to make fastboot work if I can't boot my device?
Is there some other way to repair my tablet that I can try?
Thank you for any help, this is my last hope to find a solution for my problem.
neo4458232 said:
When your device is stuck on an Android boot loop issue then you can fix it by simply doing a soft reset. Turn off your device and the problem will be resolved.
Here are the steps to follow:
First, switch off your device and take out your battery from the phone.
If your battery is non-removable then turn off the phone for 3 to 5 minutes and again turn it on.
This method works effectively to fix the error of the boot loop issue. But if a soft reset does not work for you to fix Android phones stuck in the boot loop issue then you should follow the next method.
Method 3: Reboot System in Recovery Mode​Rebooting a phone in the Recovery Mode is known for fixing several errors and issues on your Android phone. So, if you are unable to start your phone in normal mode or your Android is stuck in a reboot loop, then restart your phone in Recovery Mode.
Method 4: Remove and Reinsert SD Card​You may also try to remove the SD card to fix the boot loop in Android. According to several user reports, this trick worked for them. So, you should try this.
First, turn off your phone > remove the SD card > turn on your phone normally, and check if your phone is out from the boot loop or not.
If it is still stuck in the boot loop, then go for the other solution.
Method 5: Reboot the Phone in Safe Mode​This problem may also occur due to problematic 3rd party apps. If you have recently installed an app on your phone and then you started facing this issue, then remove it from your device.
Or, if you are not sure which app is responsible, then try rebooting your phone in safe mode. Doing this will disable all the third-party apps on your Android phone and then you can easily find out if this is the reason behind this issue or not.
To do this, you need to follow these steps:
Start rebooting your phone.
When the device logo appears on the screen, long-press the volume-down button at the same time.
Now, your phone will automatically switch to Safe mode.
If your phone is no more getting into the boot loop, then it means one of the third-party apps installed on the device was causing this issue.
Now, find out the problematic app and uninstall it to fix the Android boot loop without losing data.
Method 6: Use Custom Recovery Mode​When you find your Android is stuck on the startup screen due to the boot loop issue, then you must try to restart the phone in the Custom Recovery mode. Here is the guide to do so:
To enter into the Custom Recovery mode press the Power + Volume down buttons simultaneously.
Select the “Advanced” option in the Custom Recovery menu.
Next, choose “Wipe Dalvik Cache”. Choose “Yes” when prompted for confirmation.
Move to the “Mounts and Storage” option and choose “format/cache”. It will clear the cache files completely.
Restart your device.
Method 7: Fix Android Bootloop Error Via CWM Recovery [For Rooted Phone]​Maybe you are not aware of this method but it’s a useful way to fix the boot loop issue on Android after the update. Remember that this method is only for rooted phones. Here CWM means ClockworkMod and if your phone is stuck on the Android boot loop then it must be downloaded and installed on phone. Read me
Click to expand...
Click to collapse
Thanks for replying but I already tried every method listed here.
At this point it sounds like you need to bring it in to a local repair shop & see if they have a fix.
The solution is to wait on the turned on screen until the battery dies completely. Then put it to charge and after a bit using the reset combo (pwr+volume down) once the circular battery charging indicator with the green border comes. (It's a matter of luck, this keeps happening to my tablet and even the official samsung store can't fix it even though they took money to do the same)

Categories

Resources