Database Users

[Q] NFC error puzzle. USB debug not an option

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.

Nexus 6P black screen will not boot into OS

Okay, so there is no screen protector or anything. Not rooted or unlocked or tampered in any way. I've had the phone for 26 hours and then the following happened:
EDIT: YouTube video added https://youtu.be/yAVmTz7MQbQ
I pulled the phone out of my pocket to unlock it. I see the lock screen and put in my pin (yes, I see the actual screen and stuff on it. Let me make that clear.) after I enter my pin successfully the screen locks itself. I contacted Google support and they said to factory reset it. I did the full factory data reset in the recovery mode (again, the screen works. I can see everything to do a FDR and I can see the boot animation) and it starts to boot up. Once I see the "welcome" screen it instantly locks itself. I can hear the audible "latch" locking sound that it makes when you press the power button. I know the buttons are not malfunctioning because they work perfectly fine in bootloader / recovery mode to scroll up and down and select things. I've tried multiple things but nothing seems to work. The problem here is that I want to try and do a factory image but my computer will NOT recognize my Nexus 6P when in recovery mode / bootloader mode. I have all the drivers installed but since I can't access the OS and enable OEM UNLOCKING there is no way to factory flash a factory image is there? Can someone maybe help point me in the right direction? Again, I can NOT access the OS at all whatsoever.

You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !

hutzdani said:
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
Click to expand...
Click to collapse
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S

xandr00 said:
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
Click to expand...
Click to collapse
Can you run fastboot format cache and format user data? Then will anything happen ?
Sounds like you need to edit the partition that holds the data change for allow OEM unlock - there's a few threads about this on XDA for the N9 and N6 as far as I can remember.
It would seem the ability to flash a fresh system.img would solve this

Powering down, and re-powering problem

So let me begin with what I'm running.
Stock bootloader-locked.
Nougat 7.1.2 Beta from Google (On the beta program)
No root. Completely stock.
When I updated to 7.1.2 I started having this problem, the phone did not start up right after the update. It took a few hours to finally get the phone to come on, when I did I opted out of the beta and went back to 7.1.1, flashed back, phone started, yay!
Except.....
Now if I shut the phone down now I cannot get it to power on at all, doesn't respond to anything, no stock bootloader by pressing power+vol down, nothing.
The only way to get this phone to load up is I have to wait until the battery fully dies, charge to full and then power on the phone and it will start. Even after all this I still can't power down and enter stock recovery/bootloader.
Any idea on what's going on?

Chewmasey said:
So let me begin with what I'm running.
Stock bootloader-locked.
Nougat 7.1.2 Beta from Google (On the beta program)
No root. Completely stock.
When I updated to 7.1.2 I started having this problem, the phone did not start up right after the update. It took a few hours to finally get the phone to come on, when I did I opted out of the beta and went back to 7.1.1, flashed back, phone started, yay!
Except.....
Now if I shut the phone down now I cannot get it to power on at all, doesn't respond to anything, no stock bootloader by pressing power+vol down, nothing.
The only way to get this phone to load up is I have to wait until the battery fully dies, charge to full and then power on the phone and it will start. Even after all this I still can't power down and enter stock recovery/bootloader. Any idea on what's going on?
Click to expand...
Click to collapse
Interesting. You can't button press and get into bootloader? That's hard wired. Maybe a bad power button? I was going to suggest wiping cache from recovery as a first step, but you NEED recovery mode to do anything. At a minimum I would go into Dev Settings and allow both OEM unlocking and USB debug straight away. This way you can use ADB, and if you end up in a bootloop you can still unlock the bootloader and flash images and maybe a recovery . Do you know which 7.1.1 build you are on? Set up ADB/fastboot and try adb reboot recovery from within the OS. Maybe get you into recovery so you can at least wipe cache to start. Later, you may also be able to sideload an OTA from stock recovery (if adb reboot works). If the OTA doesn't fix it, you may need to do a factory reset. ADB will also allow you to pull any valuable files off the device.

I've actually signed up again and am running the beta 7.1.2 OTA Google beta program.
Security patch: January 5/2017
Baseband version: angler-03.79
Kernel version: 3.10.73-geac7D674
[email protected] #1
Tue Dec 13 10:11:12 UTC 2016
Build Number: NPG05F
I've been back and forth with 7.1.1 and 7.1.2 and it does the same thing with each build.
I tried unlocking with Wugs toolkit but as soon as I get to power off device and go into bootloader I can't get the bootloader screen to show up and I need to wait until the phone dies and charge to 100% and then start the phone regularly.
I do have ADB installed on my PC but anytime I need to get into bootloader I'm screwed.

Chewmasey said:
....I do have ADB installed on my PC but anytime I need to get into bootloader I'm screwed.
Click to expand...
Click to collapse
Thanks for providing lots of good info on where you are at.... most ppl dont. I'm also on 7.1.2 but with zero issues. OK gotcha, so using NRT, under advanced tools you have tried rebooting to both bootloader and recovery, and it failed. You didn't say YES, I enabled USB Debug/ OEM Unlock in developer options. By any means possible get into your OS and enable OEM Unlocking and USB Debugging now before it's too late. You've got to get into your bootloader/recovery and you are still locked with no access to ADB. There is a great driver install/ diagnostic tool in NRT to help you confirm all drivers are there and working. Sounds like you are ready to unlock/wipe in an effort to recover your phone. I think you can recover from this, but you'll probably lose your userdata.

I have the phone up and running right now. I have already went into developer options and checked OEM unlock and have debugging enabled.
When I go into NRT and go to unlock, it connects etc but when it comes to the point of power off device and boot into bootloader the screen is blank. My PC only recognizes the phone as an Android Interface after this and then I have to wait until the phone completely dies and a recharge to power up the phone.
I would try NRT again right now but I'm scared I will be without my phone all day tomorrow.
Damned if I Do, Damned if I don't.

Chewmasey said:
I have the phone up and running right now. I have already went into developer options and checked OEM unlock and have debugging enabled. When I go into NRT and go to unlock, it connects etc but when it comes to the point of power off device and boot into bootloader the screen is blank. My PC only recognizes the phone as an Android Interface after this and then I have to wait until the phone completely dies and a recharge to power up the phone.
I would try NRT again right now but I'm scared I will be without my phone all day tomorrow.
Damned if I Do, Damned if I don't.
Click to expand...
Click to collapse
When the phone is not responsive and you have been discharging it, have you tried holding the power button down for at least 2 minutes? In many cases this forces the phone to restart, but it takes a long time. That may shorten the wait between getting the phone back up.
Did you only start using NRT after the problem, or it was working fine beforehand in bootloader mode (fastboot). There is a separate driver for fastboot, I'm trying to see if that was working before. Since you are trying to unlock, it sounds as if you are past trying to save any data on the phone. NRT uses both ADB and fastboot, but you may have better luck using the command line from your PC. In my previous post I linked to Google's ADB/Fastboot binaries. Instructions are pretty basic. If you can get that setup you can try communicating with the device from the command line. Even if the is screen off, try sending fastboot devices.

Tried everything, gave up bought a used 64gb Nexus 6p.
Last time fiddling with the phone Everytime I touched the power button the red LED blinked.
I'm thinking either the motherboard or the battery.

Phone stuck on Bootloader [soft brick]

Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.

GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....

slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:

GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.

tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?

Factory Reset my Magisk root device now its bricked

i factory reset my device and now it says "official released binaries only " in red and it wont boot at all. idk what to do.. i dont know how to force it to go into download mode i tried plugging it into the computer but it doesn't help. it just keeps restarting over and over again i only see the Samsung S10+ with the Yellow Triangle logo with that message at the top then it reboots. " anyone got any ideas how i can fix this there isn't a samsung store near me. if i plug-in the device into the computer it just keeps rebooting to the samsung s10 screen with the yellow triangle saying at the top in red "Only Official released binaries are allowed to be flashed" my issue is that i can't get the phone into download mode i tried holding down Bixby volume down power then plugin the usb cable. and even bixby volume up and power . it just keeps rebooting itself (sm-G975F)

have a quick look at this thread..... you should be able to boot into download mode, make sure u have the drivers for your phone installed on your pc. you will need to flash another firmware via odin (id recommend stock firmware to get you back on track )
https://forum.xda-developers.com/galaxy-note-9/help/official-released-binaries-allowed-to-t3893592

100000x likes.. you saved me bro.
volume down + bixby that was the magic key's to get back into download mode. i am flashing the firmware now. thank you again. i couldn't figure it out and i was going nuts .

? glad to help

meddylad said:
? glad to help
Click to expand...
Click to collapse
i lost oem unlock so i changed the date to may 1st and it showed up. but now how do i get it back to grayed out.. because when it needs internet it changes the date back to. todays date. got any ideas.
edit: when i reset up the phone after i checked oem unlock i put the the date for 10 days ago. so that the unlock stayed. anyways thanks again @meddylad

I think you have no choice but to wait the 7 days (think its a knox issue)... you could turn off auto time sync but that messes up other apps.
maybe someone else might have a workaround so hold tight

meddylad said:
I think you have no choice but to wait the 7 days (think its a knox issue)... you could turn off auto time sync but that messes up other apps.
maybe someone else might have a workaround so hold tight
Click to expand...
Click to collapse
I turned off auto time . And got OEM unlock then unlocked it and re installed magisk then for the final setup I put the auto time.
Question are you on asd6 or asd4 firmware?

rp4k said:
I turned off auto time . And got OEM unlock then unlocked it and re installed magisk then for the final setup I put the auto time.
Question are you on asd6 or asd4 firmware?
Click to expand...
Click to collapse
Personally I don't known an S10. However, from what I know, Samsung incorporated a fastboot-like feature. In Download Mode, when you press Up, it asks you to factory reset to unlock your bootloader. You might need to relock it (if you come from pure stock), wait the 7 days, and unlock it again.
"Only official binaries can be flashed" is due to RMM state changing to Prenormal. It happens on a factory reset. To prevent it, you need to patch it through TWRP. If you can on the S10 I don't know, but patching RMM will prevent this warning. It's basically meaning OEM Unlock is back on.

Visera said:
Personally I don't known an S10. However, from what I know, Samsung incorporated a fastboot-like feature. In Download Mode, when you press Up, it asks you to factory reset to unlock your bootloader. You might need to relock it (if you come from pure stock), wait the 7 days, and unlock it again.
"Only official binaries can be flashed" is due to RMM state changing to Prenormal. It happens on a factory reset. To prevent it, you need to patch it through TWRP. If you can on the S10 I don't know, but patching RMM will prevent this warning. It's basically meaning OEM Unlock is back on.
Click to expand...
Click to collapse
There isn't a patch for it yet on s10 because it's not possible because of how the partitions are setup. I already fixed my device already and like I stated in the lost before
You can bypass the 7 day wait.
First boot of new firmware have no internet or sim and set the date to 7 or 10 days before. Then once in the os do the developer mode unlock and click OEM unlock. Then go into download to unlock it fully then When the phone reboots to erase all data set it again to the same date . But this time once your In the OS you enable wifi but disable automatically time and date and set it to the same date as before. And OEM unlock will be grayed out. Then reboot to Download mode and flash the patched .tar from magisk. Once that finishes reboot to stock recovery do a factory wipe. Then reboot with volume+ Bixby, power to get into magisk image of os. And you will have the unlocked bootloader . But the OEM won't be grayed but it will be active.

rp4k said:
There isn't a patch for it yet on s10 because it's not possible because of how the partitions are setup. I already fixed my device already and like I stated in the lost before
You can bypass the 7 day wait.
First boot of new firmware have no internet or sim and set the date to 7 or 10 days before. Then once in the os do the developer mode unlock and click OEM unlock. Then go into download to unlock it fully then When the phone reboots to erase all data set it again to the same date . But this time once your In the OS you enable wifi but disable automatically time and date and set it to the same date as before. And OEM unlock will be grayed out. Then reboot to Download mode and flash the patched .tar from magisk. Once that finishes reboot to stock recovery do a factory wipe. Then reboot with volume+ Bixby, power to get into magisk image of os. And you will have the unlocked bootloader . But the OEM won't be grayed but it will be active.
Click to expand...
Click to collapse
Yeah, the same trick used to work on the older phones with the OEM unlock bug. No longer works, however RMM patching fixes it. I'm sure it'll be the same as S9. S10 has the same partitions, same OneUI, simular pie vendor, all that magic. Won't take long hopefully, S9/S10 are both Treble enabled and A - only.
edit: Read S10 isn't as simular. I'm tired.

Visera said:
Yeah, the same trick used to work on the older phones with the OEM unlock bug. No longer works, however RMM patching fixes it. I'm sure it'll be the same as S9. S10 has the same partitions, same OneUI, simular pie vendor, all that magic. Won't take long hopefully, S9/S10 are both Treble enabled and A - only.
edit: Read S10 isn't as simular. I'm tired.
Click to expand...
Click to collapse
Well this trick works fine on the s10.