Two days ago my wifes 1st generation Nexus 7 refurb started giving the "Unfortunately, NFC service has stopped" error. You click OK and the error instantly pops up again. There is a moment to click on something if you're fast and I've been able to click on settings but when settings opens it's nothing but a black screen with no options. This means that I can not enable usb debugging. I have tried quite a few different processes, ADB sideload, going through the bootloader, but they all seem to require usb debugging and the tablet is never recognized. The tablet is stock but I have no way of knowing what version of android it is currently running with the blank settings window (unless you can give me a tip on that). Have done two wipe/factory restores on it and the error comes up right at the first boot screen. I am willing to pursue any option to get this tablet in working order. Rooting, flashing, whatever but I am a novice in the world of android rooting. It was purchased off groupon (won't make that mistake again) and the 14 days are past so If I have to send it in, it's cash money out of our pockets.
Do I have any options? Thank you for your time!
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
notnorm said:
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
Click to expand...
Click to collapse
If the tablet has never been rooted, and the factory reset procedure seemed to complete successfully, then your symptoms suggest that something is wrong with the /system filesystem - which, for stock devices is never modified (always mounted read-only).
So that in turn suggests *perhaps* flaky hardware - probably the flash memory chip - that has gone awry and is the root cause of the problem.
It is conceivable that you could go through the process of unlocking the bootloader and re-flash a Google-provided "factory image", and that the problem will go away. But if the root cause is really a flaky flash memory chip, it will very likely return with a vengeance, and your efforts will be for naught.
There is something missing in your narrative, however - if the appearance of the "NFC Service has stopped" dialog on-screen prevents you from interacting with your (intended) foreground apps, how were you able to perform a factory reset and then follow that up with a tablet configuration? (e.g. to get Google credentials on the tablet so you could push apps to it by using a PC Web browser from the Google Play market).
If you are unfamiliar with rooting but still want to proceed with reloading the factory images, you will have to follow the Stock Recovery tutorial threads. Many users - especially those with Windows machines - seem to get stuck at this step, although truth be told that has nothing to do with Android, and everything to do with Windows Driver Installation Hell.
Note - specific to your situation.. You do not need to enable USB debugging to re-flash factory stock images. You only need to communicate with the device (booted into bootloader mode) with the "fastboot" program. For this you only need working USB hardware - not "adb".
good luck
BTW, note that you can perform a factory reset in the stock recovery without launching it from the O/S. The sequence is:
1) Turn the tablet off (not screen off, but powered completely off)
2) Boot into bootloader mode by holding Power+Vol-Down together (hold them down until android lying on its' back shows up - about 4 seconds)
3) Using the vol-up/vol-down button, select "Recovery Mode" on screen and press the power button
At this point the screen will go black. Wait about 10-13 seconds. The screen will remain black even though the stock recovery is now running. To get the screen to show the (stock) recovery menu,
4) press and release the Power & Vol-Up keys simultaneously.
The stock recovery menu should show now up. If it doesn't, try again. (After 60 seconds if you have done nothing, the tablet will reboot to the "normal" OS).
5) Use the on-screen menu to perform a factory reset (follow the directions on-screen for key usage).
Thank you so much for your response! The unanswered question is that I managed to put in the network info and what not during setup by hitting OK on the error and tapping the letter in the moment before the error popped up again. Not a fun task!
I've been trying to flash and after installing the google usb drivers it's still doing the <waiting for device> for infinity. I think I will have to bite the bullet and send it in. You saying that it might be a flash chip is kind of comforting because I think I might have bashed my skull against this issue forever before giving up!
Chris
flashed the wifi fix for the TMObile us version (from the X Note rom page)and was able to get out of the loop.
Related
So, dumb self made a pattern that I don't remember. So my Vibrant is at the Too Many Pattern Attempts screen. I've tried to wipe the phone using vol up and down plus power but that doesn't remove the too many attempts screen at all. The only gmail account that I hooked up to my phone keeps telling me that something is incorrect yet I can log in to my gmail fine from my computer... What can I do? I tried to do Odin, but vol down plus power does nothing on my phone. It just continuously power cycles... When I boot into the recovery screen I can use Odin but it just hangs at checking files... Any suggestions?
Do you have coverage? Maybe the Google verification can't connect. It always worked on my myTouch and once on the Vibrant.
Sent from my Samsung Vibrant using the XDA app
Tmobile Galaxy S pattern locked out, can't root
I just bought my first Android device, the Samsung Galaxy S from Tmobile from the US (I live in China) last week. I have only used it a few days and my girlfriend thought the pattern lock would be a fun game to play. Result - locked out. I have the same problems as in the below thread:
http://code.google.com/p/android/issues/detail?id=4784
I tried the receive a phone call then hammer the home key; emergency call and go to search and many of these type fixes; however none have gotten me through. It seems they fixed the security problem here but didn't fix the username password problem as I'm sure the credentials I entered are correct and I have data service.
After giving up on these methods I tried doing a hard reset. BTW, on this model you must hold down volume up AND down buttons at the same time, then press the power button to get the reset screen.
I have cleared user data etc, but when I try to reset the phone I get the error message "setup.zip not found".
I understand that I now need to root the phone, so I tried the method explained here but without having access to the phone I need to load this setup.zip file on the SD (not the one with Avatar).
http://samsungvibranthacks.com/samsung-vibrant-hacks/how-to-root-samsung-vibrant-galaxy-s/
I already installed Kies (has Outlook sync functionality!) on my desktop so that I can access the internal memory as an external drive. However the phone's USB mode must be set to (it will prompt whenever I connect) to Kies mode. However since I am locked out of the phone I can't tell the phone to get into Kies mode, therefore cannot access the internal memory, therefore cannot load setup.zip, therefore cannot root, therefore cannot get past the pattern lock screen = useless phone.
I need to root the phone anyway so I can load a few Asian IME's that didn't come with the phone so don't mind playing with this, but since I'm new to Android it may be a while before I can get through since most root instructions either require access to the internal memory via my computer or access to the phone (past the pattern lock).
If I offer to make a paypal donation could I summon the help of one of the more experienced Android gods that frequent this forum that can help me get through this?
To use odin you need to get into download mode not recovery mode (Volume Down+ Power) but since for some reason that wont work for you, you will have to do something involving the android sdk do you know how to use it?
Genesis1791 said:
To use odin you need to get into download mode not recovery mode (Volume Down+ Power) but since for some reason that wont work for you, you will have to do something involving the android sdk do you know how to use it?
Click to expand...
Click to collapse
On one or two tries, when the device was attached to my laptop I got a yellow on black downloading screen but had no idea what it meant. How does this help me root it? In general the volume down+plus power button didn't do anything but reboot it.
I just downloaded the SDK last night for the last time and haven't succeeded in installing it so have still got a bit of learning to go before I can make it useful.
I have the phone back in my hand now so adding some details:
Holding volume up and down and the same time, then pressing powere gets me to the "Android system recover <2e>" screen with four options:
Reboot system now
reinstall packagages
delete all user data
delete cache data
I've tried all and none will get me out of the username/password screen after reboot. If I select "reinstall packages" it says:
E:can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
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
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
Hi, hoping for some advice, I have three shield 2017's, updated 2 of 3 to 8.0.1 without issue, last one went into bootloop after the update.
The problematic one had the update pending for a long time, just never rebooted to install it, until now.
I followed the nvidia KB, and tried the the fast boot menu, recovery kernel, factory reset, still bootloop.
I contacted support over chat, they had me boot without HDMI, press A, reconnect HDMI, no difference, shield keeps rebooting even without HDMI.
Support then had me change power plugs, since I have three shields, I tested using another working shield PSU, same problem.
Support then had me boot, wait 2 mins, press home and left on dpad, wait for blue flashing, no difference, as shield keeps rebooting, waiting for anything is really pointless.
Out of frustration, and not knowing what I'm doing, I did a factory reset directly from fastboot menu, now I get a can't verify firmware, lock firmware, press A message, and then it just sits at the nvidia menu, not good.
(Btw, it took many tries to get the fastboot menu to launch, first time was lucky, but it continued rebooting before I had a chance to move the menu, then it seemed impossible to get again.
Is there a reliable way to get the fastboot menu up using the controller A+B or other method?
Given the state of the shield, can I recover the device, any advice on how, please?
if you are able to access fastboot menu everything is possible if it's not a hardware problem, grab one of the recovery images for your device and use one of the many tutorials available to recovery your device
zecabra said:
if you are able to access fastboot menu everything is possible if it's not a hardware problem, grab one of the recovery images for your device and use one of the many tutorials available to recovery your device
Click to expand...
Click to collapse
Ok, that's good news then, I'll order and A-A cable and try one of the tutorials (I was pointed to one on reddit).
Any advice on how to reliably launch the fastboot menu using the controller, I do the A+B button, power on, and it only occasionally works?
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 ModeRebooting 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 CardYou 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 ModeThis 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 ModeWhen 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)