Database Users

[Q] Stuck in safe mode

Hi everybody.
I don't know how it happened (I just wanted to do a reboot in the recovery mode), but now I've got the blue led when normally turn my phone on. I can't even access to the fastboot (blue led too).
The only thing I can do, is boot in the safe mode, by booting my phone (connected to the charger) after removing the battery... I tried "reboot to bootloader", without success...
I think it's because of the recovery, because I had some problems during the installation of my last ROM, a few months ago. So I'd think I must flash a new recovery.
ow can I get out???? ADB? Special "trick"? Factory reset from the ROM? Flashing a new recovery (I don't know how...)?
Thank you, Roumaru

I tried to flash a new recovery with ADB, and then reboot to the bootloader, but it didn't work.... I'm really stuck!

Try RUU method if you are able to acces bootloader mode ,or try to search the forum or look into FAQ,for the answer of your problem.
Sent from my HTC Magic using xda app-developers app

george.wgx said:
Try RUU method if you are able to acces bootloader mode ,or try to search the forum or look into FAQ,for the answer of your problem.
Sent from my HTC Magic using xda app-developers app
Click to expand...
Click to collapse
I can't access to the bootloader... I can just access to the safe mode! It's really strange. I'll search in other forums, but I haven't found any answer yet

Roumaru said:
I can't access to the bootloader... I can just access to the safe mode! It's really strange. I'll search in other forums, but I haven't found any answer yet
Click to expand...
Click to collapse
Install mumilover's Fastboot Commander. Connect it to your PC with a USB cable, turn it on, and run Fastboot Commander. It will display a bunch of information about your phone that will help us diagnose the problem.
Just cut and paste the info it gives you. If it doesn't work, just tell us what information you see on the phone's screen.
You should see something like:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0007 (SAPP10000)
CPLD-10
RADIO-6.35.07.29
Aug 4 2009, 19:43:30
Later.

DasBub, he cannot acces bootloader,so he 's not able to see that info

george.wgx said:
DasBub, he cannot acces bootloader,so he 's not able to see that info
Click to expand...
Click to collapse
Yes, I understand that he can't get into HBOOT, FASTBOOT, or Recovery using physical buttons. But there are other possibilities we can check. I don't know his skill level, knowledge about the device, or the complete state of his device, so I'm trying to build a clearer picture.
If fastboot reports nothing, what about adb? If adb reports nothing, check device manager to see if it's even noticed by the PC.
When I said "just tell us what information you see on the screen" what I meant was "tell us what the screen is showing, even if it is nothing at all and the blue LED is on". My fault.
I'm curious about the whole "safe mode" business. Is it truly booting into safe mode, where you can see the words "safe mode" on the screen, or is it something else?

DasBub said:
Yes, I understand that he can't get into HBOOT, FASTBOOT, or Recovery using physical buttons. But there are other possibilities we can check. I don't know his skill level, knowledge about the device, or the complete state of his device, so I'm trying to build a clearer picture.
If fastboot reports nothing, what about adb? If adb reports nothing, check device manager to see if it's even noticed by the PC.
When I said "just tell us what information you see on the screen" what I meant was "tell us what the screen is showing, even if it is nothing at all and the blue LED is on". My fault.
I'm curious about the whole "safe mode" business. Is it truly booting into safe mode, where you can see the words "safe mode" on the screen, or is it something else?
Click to expand...
Click to collapse
I took a look at "fastboot commander", but naturally I need to be in the fastboot to make it work, and I can't access fastboot...
I can NOT boot in HBOOT, FASTBOOT, and Recovery, but when I remove the battery, put it in the phone, plug my charger, and then press the power button, the phone boot normally, except he's in the "safe mode" (can't access some applications, no network). I can control my phone with ADB, but when I tried "adb reboot bootloader", the blue led was here again...
I also tried the RUU method, but the RUU doesn't recognize my phone.
I think it would be good if I could do a "total reset" of my phone, like flashing it or something that can reset the bootloader.
Thank you for your interest

Yeah dude there is fix for you its named JTAG Google it and you will find out what is it.
In my country its cost me 40 Euro to fix i hope in your is cheaper or even better - you can make your own

Roumaru said:
I took a look at "fastboot commander", but naturally I need to be in the fastboot to make it work, and I can't access fastboot...
I can NOT boot in HBOOT, FASTBOOT, and Recovery, but when I remove the battery, put it in the phone, plug my charger, and then press the power button, the phone boot normally, except he's in the "safe mode" (can't access some applications, no network). I can control my phone with ADB, but when I tried "adb reboot bootloader", the blue led was here again...
I also tried the RUU method, but the RUU doesn't recognize my phone.
I think it would be good if I could do a "total reset" of my phone, like flashing it or something that can reset the bootloader.
Thank you for your interest
Click to expand...
Click to collapse
Could you try something? Make sure your phone is accessible using adb, then do this:
adb -s [serial number for phone, without brackets] reboot oem-78
The serial number can be found using "adb devices".
That should reboot you into RUU mode. If it doesn't work, safe mode should still be accessible.

Please don't post Q&A in the development section.
Thread Moved
Moderating from my One Xl

DasBub said:
Could you try something? Make sure your phone is accessible using adb, then do this:
adb -s [serial number for phone, without brackets] reboot oem-78
The serial number can be found using "adb devices".
That should reboot you into RUU mode. If it doesn't work, safe mode should still be accessible.
Click to expand...
Click to collapse
Doesn't work, the blue led is coming again...
Another idea, except Jtag? Because I don't want to spend money on my Magic, and I don't think I've got the material to do the Jtag...
However, thank you everybody!

Roumaru said:
Doesn't work, the blue led is coming again...
Another idea, except Jtag? Because I don't want to spend money on my Magic, and I don't think I've got the material to do the Jtag...
However, thank you everybody!
Click to expand...
Click to collapse
Hey, we're not giving up yet
You can access ADB, so it may be possible to push a recovery image onto the device and flash it.
For the original instructions, click this link and focus on Step 9.
Here's a shortened version:
Download roottools and unzip it somewhere on your PC.
With your phone in Safe Mode and connected to your PC, open a command prompt.
If you know which radio you were on (3.X or less, or 6.X), cd to that directory in roottools and push the recovery image.
Example: If you have 6.X, you would
cd c:\roottools\6.35Radio\​adb push Recovery-RA-hero-v1.6.2.img /sdcard​
Next:
cd to the "App" directory of roottools, then
adb push flash_image /data/local/tmp
adb shell
su
cd /data/local/tmp
chmod 777 flash_image (you might have to use /data/local/tmp/flash_image or ./flash_image)
flash_image recovery /sdcard/Recovery-RA-hero-v1.6.2.img​
If you get through that with no errors, we should be good. If it throws an error at "su" then you should try using SuperOneClick to get temporary root.
If it flashes without errors, you can try "adb reboot recovery" and see what happens.

Resolved
A few days ago, the "safe mode" logo disappeared. Really didn't understand why, but now my problem is solved!
Thank you for all, Roumaru

Roumaru said:
A few days ago, the "safe mode" logo disappeared. Really didn't understand why, but now my problem is solved!
Thank you for all, Roumaru
Click to expand...
Click to collapse
That's great news! Everything works normally now?
I have heard that a stuck button or trackball is a possible cause. Maybe that was the problem with your phone, but it became unstuck?
Cheers!

[Q] Stuck at Google logo AND system recovery AND oem locked

Please tell me there's a solution to this..!
My N7 2013 had always been fine, and I liked stock android very much, thus saw no need to unlock the bootloader. When the 5.1 OTA came, I updated my N7 and it started crashing and restarting on its own. One day, it restarted again and got stuck at the Google screen.
Of course the first thing I did was to get the Nexus Root Toolkit, and tried flashing stock rom. Of course it didn't work since it was oem locked. When I tried to unlock the bootloader, I was prompted with the screen asking if I want to unlock and wipe all data. I selected unlock and pressed the power button. Then it froze (I left it for 8 hours, plugged in to a power outlet).
The next logical thing to do was to start recovery mode in the fastboot to do a factory reset, except it simply switched to the Google screen and was stuck there.
TL;DR
Normal startup: Stuck at google screen.
Unlock bootloader: Stuck at selection.
Recovery mode: Stuck at google screen.
I'm pretty desperate now, that's why I'm posting here. Sorry if it's the wrong category or something. I've read many articles, but it's always ONE of the THREE issues I have. They often refer to using a method that involves an area where it's affected by the other problems.
Please help me, I don't want to see $250 down the drain

Have you tried using Nexus Root Toolkit to unbrick the tablet? There is an unbrick section and one of the options says something like "Soft brick/bootloop". Try that option.

Fobos531 said:
Have you tried using Nexus Root Toolkit to unbrick the tablet? There is an unbrick section and one of the options says something like "Soft brick/bootloop". Try that option.
Click to expand...
Click to collapse
I have! I saw the option when I opened NRT, and went straight for it. Here's what I did:
Checked "soft-bricked/Bootloop" option under "flash stock + unroot"
Downloaded the correct factory image
Checked "Force flash mode" (unchecked doesn't work either)
The command box came up (please see attachment)
It kept saying that the operation failed because the bootloader was locked. When I tried to unlock the bootloader, it was stuck at the selection screen after I press the power button to select "unlock bootloader".
Note: It's stuck at "erasing cache". Left it on for 2 hours.

Panpaper said:
I have! I saw the option when I opened NRT, and went straight for it. Here's what I did:
Checked "soft-bricked/Bootloop" option under "flash stock + unroot"
Downloaded the correct factory image
Checked "Force flash mode" (unchecked doesn't work either)
The command box came up (please see attachment)
It kept saying that the operation failed because the bootloader was locked. When I tried to unlock the bootloader, it was stuck at the selection screen after I press the power button to select "unlock bootloader".
Note: It's stuck at "erasing cache". Left it on for 2 hours.
Click to expand...
Click to collapse
Hook it up to your PC, open a command line to wherever you have fastboot.exe at, plug in your device to the pc, boot your device into fastboot by hand (with device off, hold down power+volume down), once it's in fastboot mode, do a: fastboot devices, what comes up?

mdamaged said:
Hook it up to your PC, open a command line to wherever you have fastboot.exe at, plug in your device to the pc, boot your device into fastboot by hand (with device off, hold down power+volume down), once it's in fastboot mode, do a: fastboot devices, what comes up?
Click to expand...
Click to collapse
Thanks for the reply!
It says 07c17e46 fastboot
(image attached)

Panpaper said:
Thanks for the reply!
It says 07c17e46 fastboot
(image attached)
Click to expand...
Click to collapse
From that point, do a: fastboot oem unlock (it will wipe the entire device (i.e. user data), if it works)
Then look at the tablet and you should see a confirmation screen, do you? If so follow it and wait some time, took mine about 12 minutes IIRC, but mine was a nexus 7 2013 not a 2012, so YMMV.
If nothing happens post a screenshot of errors, etc from cmd prompt.

mdamaged said:
From that point, do a: fastboot oem unlock (it will wipe the entire device (i.e. user data), if it works)
Then look at the tablet and you should see a confirmation screen, do you? If so follow it and wait some time, took mine about 12 minutes IIRC, but mine was a nexus 7 2013 not a 2012, so YMMV.
If nothing happens post a screenshot of errors, etc from cmd prompt.
Click to expand...
Click to collapse
It's been an hour and a half, and it's still at "erasing userdata". Mine is a nexus 7 2013 too, is it supposed to take that long?

Panpaper said:
It's been an hour and a half, and it's still at "erasing userdata". Mine is a nexus 7 2013 too, is it supposed to take that long?
Click to expand...
Click to collapse
How long it takes differs, but it certainly should be done within 20-30 mins. Not sure where to go from here, will do a little looking around and get back to this thread.
FYI, you might want to know you are in the Nexus 7 2012 forum. You may want to self-report your OP as a maintenance request and have it moved to the Nexus 7 2013 forum.
And with that thought, make sure in future, that within wugfresh tool, you are selecting the right image, as if you try and use the N7 2012 one you may have issues.

mdamaged said:
Oh well, then you might want to know you are in the Nexus 7 2012 forum. Anyhow, how long it takes differs, but it certainly should be done within 20-30 mins.
Click to expand...
Click to collapse
Oh, sorry I didn't know that! First post.
I'll leave it running for the day and see what happens then. Thank you!

mdamaged said:
How long it takes differs, but it certainly should be done within 20-30 mins. Not sure where to go from here, will do a little looking around and get back to this thread.
FYI, you might want to know you are in the Nexus 7 2012 forum. You may want to self-report your OP as a maintenance request and have it moved to the Nexus 7 2013 forum.
And with that thought, make sure in future, that within wugfresh tool, you are selecting the right image, as if you try and use the N7 2012 one you may have issues.
Click to expand...
Click to collapse
Sorry to trouble you again. I don't know if the userdata erasing is done, but I got this (screenshot). The tablet is still frozen in the selection screen (highlighted "Yes, unlock bootloader").
I shut it down and started it into fastboot again. Under LOCK STATE it's still locked.

Panpaper said:
Sorry to trouble you again. I don't know if the userdata erasing is done, but I got this (screenshot). The tablet is still frozen in the selection screen (highlighted "Yes, unlock bootloader").
I shut it down and started it into fastboot again. Under LOCK STATE it's still locked.
Click to expand...
Click to collapse
I'm suspecting it could be a bad usb port or bad usb cable. i.e. try a different pc, or a different usb cable and different usb port, also never use a USB hubs port. It also could be a dirty usb port on the device too.

mdamaged said:
I'm suspecting it could be a bad usb port or bad usb cable. i.e. try a different pc, or a different usb cable and different usb port, also never use a USB hubs port. It also could be a dirty usb port on the device too.
Click to expand...
Click to collapse
I tried a different USB port, and also on a different laptop, but nothing seems to work. It seems to be stuck at "erasing userdata". I tried fastboot -w too, but it just stayed at "erasing userdata" for over an hour.
I'll get a new USB cable whenever I can, and try this again. Thanks for all the help so far!
I can't believe an official OTA update would cause so much damage. SIgh.

mdamaged said:
I'm suspecting it could be a bad usb port or bad usb cable. i.e. try a different pc, or a different usb cable and different usb port, also never use a USB hubs port. It also could be a dirty usb port on the device too.
Click to expand...
Click to collapse
So apparently I'm not the only one with this problem.
http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/
I used my Nexus 5 original USB cable to do it, and the same problem has occurred.
I feel like I'm running out of options and seriously losing hope. I know it'll probably be better to leave the device on its own and wait for some kind of fix in the future, but I'd also like to know if there are any other way other than sending it in for repair (I rather buy a new tablet).

Broken LCD display, trying to dump data

Hi all!
I've been researching this for the past few days. I recently dropped my Nexus 6P and it broke the LCD display. Google voice commands still work and I was able to unlock it with a USB OTG cable, so it appears that the only thing that's broken is the display. Of course, I didn't have USB debugging, Developer Mode, or it set up as an MTP device. I've only had the phone for a couple months so it's not a big deal but I would like to get my pictures back if at all possible. I know almost 0 things about android development, but am fairly tech savvy so I'm trying, here.
I have Android Development Studio with the Google USB Driver installed. Plugging the phone in via USB shows a "Nexus 6p" device with no files on it. I've gone through some tutorials but always get stuck at the "adb device" part.
I get the following from running commands:
Code:
C:\Android\Sdk\platform-tools>adb.exe devices
List of devices attached
C:\Android\Sdk\platform-tools>fastboot devices
XXXXXXXXXXXXXX fastboot
C:\Android\Sdk\platform-tools>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.031s
I think I am able to boot my device into recovery mode, but that hasn't helped as of yet.
Would appreciate any and all advice. Thanks for taking a look. Don't worry, I immediately set up my new phone in case I'm ever in this situation again. Take it from me... set it up now

OK so fastboot is for the bootloader and adb is for either recovery or the system itself.
You also won't type .exe after it either. Boot up your phone and unlock it then type "adb devices" into the command prompt. If that doesn't work (since you mentioned USB debugging is off) try from stock recovery. I'm honestly not 100% sure this will work TWRP is the 1st thing on my phone's. I don't mess with stock, but it's worth a shot. Reboot while holding volume up and it should bring you to stock recovery. Wait a few seconds and then hold the power button and quickly press and release volume up and then let go of both buttons. Do this plugged into a PC since when you enter the bootloader you get the little noise that plays. That way you know when it actually reboots and when to try the button combos. Now run "adb devices" again and it should show "XXXXXXXXXXXXXXXXX recovery"
From there just try adb pull.
"adb pull /storage/emulated/0 c:/Users/YourUserNameHere/Downloads"
Obviously in the path above, you'd enter your own username and entirely change the path to wherever you want your data saved. The above pull command will take your entire internal storage, all files if it works.

Hey Roy,
Thanks for posting. Still no luck getting it to show up on the device list. Followed your instructions and got a connected noise for the boot screen, then unconnected noise and connected noise again when I held the power button and pushed the volume up button, then released. So I think I got it into recovery mode but still no dice. Any other ideas on things I could try?

ahalbert said:
Hey Roy,
Thanks for posting. Still no luck getting it to show up on the device list. Followed your instructions and got a connected noise for the boot screen, then unconnected noise and connected noise again when I held the power button and pushed the volume up button, then released. So I think I got it into recovery mode but still no dice. Any other ideas on things I could try?
Click to expand...
Click to collapse
Sadly if you fully booted into stock recovery and adb still isn't working, I'm not sure there's a way to enable Android debugging at this point. Maybe someone else could chime in, but I think you'd need to get your screen replaced at a local repair shop.

RoyJ said:
Sadly if you fully booted into stock recovery and adb still isn't working, I'm not sure there's a way to enable Android debugging at this point. Maybe someone else could chime in, but I think you'd need to get your screen replaced at a local repair shop.
Click to expand...
Click to collapse
That's too bad. Thank you for the advice though!

Bricked Chinese version, only ADB sideload is working. Appreciate any help.

Hi,
Messed up badly Furious that ZTE made the phone incompatible with Daydream, decided to root the device. Tried various ROMs, but could never get the modem to work in the UK. Eventually tried to reinstall Chinese stock ROM and, to my surprise, the modem still didn't work. Attempted to restore the modem files from TWRP backup and bricked the phone completely. Can only boot into Chinese recovery where only ADB sideload enables the phone to be seen by Windows as Android ADB Interface. EDL mode cannot be seen and Axon7toolkit cannot see the phone even in ADB sideload mode. Attempts to update software result in this message: Package expects build fingerprint of ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys or ZTE/P996A03/ailsa_ii:7.1.1/NMF26F/20170224.135053:user/release-keys ; this device has ZTE/P996A03/ailsa_ii:7.1.1/NMF26V/20170912.013327:user/release-keys. Most likely, updates won't work anyway, because when the phone was running, updates resulted in a mismatch. Any feedback would be much appreciated.

tretayuga said:
Hi,
Messed up badly Furious that ZTE made the phone incompatible with Daydream, decided to root the device. Tried various ROMs, but could never get the modem to work in the UK. Eventually tried to reinstall Chinese stock ROM and, to my surprise, the modem still didn't work. Attempted to restore the modem files from TWRP backup and bricked the phone completely. Can only boot into Chinese recovery where only ADB sideload enables the phone to be seen by Windows as Android ADB Interface. EDL mode cannot be seen and Axon7toolkit cannot see the phone even in ADB sideload mode. Attempts to update software result in this message: Package expects build fingerprint of ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys or ZTE/P996A03/ailsa_ii:7.1.1/NMF26F/20170224.135053:user/release-keys ; this device has ZTE/P996A03/ailsa_ii:7.1.1/NMF26V/20170912.013327:user/release-keys. Most likely, updates won't work anyway, because when the phone was running, updates resulted in a mismatch. Any feedback would be much appreciated.
Click to expand...
Click to collapse
You messed up real bad. I assume you forgot to flash the modem files when you flashed the custom ROMs?
EDL mode cannot be seen? What do you mean by that? Keep the Device Manager open, phone disconnected; then hold both volume buttons, wait 5 seconds, connect the USB cable while you are holding them, and wait 3 seconds more before releasing them. The device manager should refresh.
The phone should appear under Ports (COM & LPT) or under USB devices as QUSB_BULK. If it is under USB devices you have to right click on it, Uninstall -> Delete driver software. After that hold all 3 buttons for a long time (both volume buttons and power) and device manager should refresh itself. It should install the Qualcomm driver then. If the driver is ZTE handset diagnostic interface, you'll have to disassemble the phone

Choose an username... said:
You messed up real bad. I assume you forgot to flash the modem files when you flashed the custom ROMs?
EDL mode cannot be seen? What do you mean by that? Keep the Device Manager open, phone disconnected; then hold both volume buttons, wait 5 seconds, connect the USB cable while you are holding them, and wait 3 seconds more before releasing them. The device manager should refresh.
The phone should appear under Ports (COM & LPT) or under USB devices as QUSB_BULK. If it is under USB devices you have to right click on it, Uninstall -> Delete driver software. After that hold all 3 buttons for a long time (both volume buttons and power) and device manager should refresh itself. It should install the Qualcomm driver then. If the driver is ZTE handset diagnostic interface, you'll have to disassemble the phone
Click to expand...
Click to collapse
Thanks. The phone is listed as ZTE Handset Diagnostic Interface(DFU) (COM10) in Ports. It is listed as Unknown USB Device in USB Controllers and following the procedure you described doesn't install the Qualcomm driver. I take it, then, that an engineer would have to disassemble the phone.

tretayuga said:
Thanks. The phone is listed as ZTE Handset Diagnostic Interface(DFU) (COM10) in Ports. It is listed as Unknown USB Device in USB Controllers and following the procedure you described doesn't install the Qualcomm driver. I take it, then, that an engineer would have to disassemble the phone.
Click to expand...
Click to collapse
Or you. Follow the 4th category brick repair manual. I'm just rewriting it but it'll take time
Where are you getting adb sideload from?

Choose an username... said:
Or you. Follow the 4th category brick repair manual. I'm just rewriting it but it'll take time
Where are you getting adb sideload from?
Click to expand...
Click to collapse
Well, with your help I may snatch victory from the jaws of defeat. I'll ask one of the local engineers to dismantle the phone according to your guide and we'll see what we can do. The adb sideload screen is in this photo.
Thanks again.

tretayuga said:
Well, with your help I may snatch victory from the jaws of defeat. I'll ask one of the local engineers to dismantle the phone according to your guide and we'll see what we can do. The adb sideload screen is in this photo.
Thanks again.
Click to expand...
Click to collapse
You still have one other option though. May save you.
Do you have an SD card? If not, get at least a 4 GB one (or one with 3gb free), download an official A2017 update package, unzip it and put the update.zip in the sd card. (If you get a bunch of folders instead of a file called update.zip just take the original zip and put it in the SD).
after that, put it in the sd card and select the option that says 'sd'.
It may work. Right now it's your best shot at not taking it apart

Choose an username... said:
You still have one other option though. May save you.
Do you have an SD card? If not, get at least a 4 GB one (or one with 3gb free), download an official A2017 update package, unzip it and put the update.zip in the sd card. (If you get a bunch of folders instead of a file called update.zip just take the original zip and put it in the SD).
after that, put it in the sd card and select the option that says 'sd'.
It may work. Right now it's your best shot at not taking it apart
Click to expand...
Click to collapse
That's forbidden. When I've tried to update from the SD card using that option, I get a message saying I don't have permission to update from the SD card. I will, however, try again because you've mentioned some things that are slight variations on what I've done before.

tretayuga said:
That's forbidden. When I've tried to update from the SD card using that option, I get a message saying I don't have permission to update from the SD card. I will, however, try again because you've mentioned some things that are slight variations on what I've done before.
Click to expand...
Click to collapse
Yeah, it's possible. But I have one more idea. Can you try one other thing?
There's a way to get to EDL if you have only DFU mode, which is by getting adb (not adb sideload, just normal adb) and issuing "adb reboot edl". If you can get adb (i think you may have adb from the main recovery screen) then you can get to EDL and flash stuff with MiFlash. Try to issue 'adb reboot edl' when you are on the main screen of the recovery mode.
The other way, which might work on your state, is turning the phone off and holding volume down + power. It might open FTM mode (it's a white rectangle in the middle of the screen with the words FTM written on it, can't miss it). If you get there just issue 'adb reboot edl' and flash with MiFlash

Choose an username... said:
Yeah, it's possible. But I have one more idea. Can you try one other thing?
There's a way to get to EDL if you have only DFU mode, which is by getting adb (not adb sideload, just normal adb) and issuing "adb reboot edl". If you can get adb (i think you may have adb from the main recovery screen) then you can get to EDL and flash stuff with MiFlash. Try to issue 'adb reboot edl' when you are on the main screen of the recovery mode.
The other way, which might work on your state, is turning the phone off and holding volume down + power. It might open FTM mode (it's a white rectangle in the middle of the screen with the words FTM written on it, can't miss it). If you get there just issue 'adb reboot edl' and flash with MiFlash
Click to expand...
Click to collapse
Thanks, but I've already tried it. The phone only communicates with the computer in adb sideload mode, so trying adb reboot edl results in an "error:closed" message. If not in sideload mode, adb cannot even register a device. Occasionally, I've seen a small Linux penguin in the middle of the screen and today it hung on the MiFavor logo for some time. If those are significant, I don't know how to get them back. The ZTE engineers have been very thorough. It's frustratiing because the adb sideload thing might work with the right software package, and I can clear the cache and wipe the system; but then I'm back to square one. Your suggestion about dismantling the phone sounds like the most promising path forward and I will have a go tomorrow.

tretayuga said:
Thanks, but I've already tried it. The phone only communicates with the computer in adb sideload mode, so trying adb reboot edl results in an "error:closed" message. If not in sideload mode, adb cannot even register a device. Occasionally, I've seen a small Linux penguin in the middle of the screen and today it hung on the MiFavor logo for some time. If those are significant, I don't know how to get them back. The ZTE engineers have been very thorough. It's frustratiing because the adb sideload thing might work with the right software package, and I can clear the cache and wipe the system; but then I'm back to square one. Your suggestion about dismantling the phone sounds like the most promising path forward and I will have a go tomorrow.
Click to expand...
Click to collapse
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.

Choose an username... said:
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Click to expand...
Click to collapse
I do indeed get the 5 seconds screen, but the reason I didn't mention it is that it does nothing from what I can see. The phone "boots" after five seconds, but if I press the volume buttons to enter options, Bootloader is not one of them. The Fastboot option just makes the phone reboot and the Recovery option sends me to the screen in the photo upthread. Like I say, they've been very thorough.

Choose an username... said:
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Click to expand...
Click to collapse
Curioser and curioser. I went through the steps to short circuit the test point on the motherboard and MiFlash successfully flashed the Unbrick ROM which you advised. Obviously, the Qualcomm drivers were recognised e.t.c. The state of the phone now is that it is caught in a boot loop. It shows the ZTE screen and the 5-second screen. Going into recovery on the 5-second screen causes the ZTE logo to appear again, then the battery icon keeps showing, switching off and showing again. The Fastboot mode on the 5-second screen now takes me to the Fastboot screen, but entering recovery causes the same battery loop. Did I make a mistake reassembling the phone perhaps? Should I try to flash a different ROM from the test point?

tretayuga said:
Curioser and curioser. I went through the steps to short circuit the test point on the motherboard and MiFlash successfully flashed the Unbrick ROM which you advised. Obviously, the Qualcomm drivers were recognised e.t.c. The state of the phone now is that it is caught in a boot loop. It shows the ZTE screen and the 5-second screen. Going into recovery on the 5-second screen causes the ZTE logo to appear again, then the battery icon keeps showing, switching off and showing again. The Fastboot mode on the 5-second screen now takes me to the Fastboot screen, but entering recovery causes the same battery loop. Did I make a mistake reassembling the phone perhaps? Should I try to flash a different ROM from the test point?
Click to expand...
Click to collapse
So now you have fastboot? Put the TWRP-3.2.1-0.img on the adb folder, then open CMD, navigate to that folder, write 'fastboot boot TW" and press Tab, the filename should appear, if it does hit Enter
If you get to TWRP don't turn the phone off, and flash the universal bootloader, Lineage, the A2017 modem, and Magisk 15.2

Choose an username... said:
So now you have fastboot? Put the TWRP-3.2.1-0.img on the adb folder, then open CMD, navigate to that folder, write 'fastboot boot TW" and press Tab, the filename should appear, if it does hit Enter
If you get to TWRP don't turn the phone off, and flash the universal bootloader, Lineage, the A2017 modem, and Magisk 15.2
Click to expand...
Click to collapse
Sorry, I didn't make that clear. The 5-second screen directs me to Fastboot, but there are only four options there: Start (doesn't work, obviously), Restart Bootloader (brings you back to the same place), Shut down and Recovery (goes to battery icon). Don't know what went wrong--maybe a connection got damaged when the phone was dismantled--but I discover I can't repeat the short circuiting thing and, even though the phone is seen on the system as Qualcomm 90.., MiFlash cannot flash anything different. I despair. I'll send the phone for recycling. Making the Axon 7 incompatible with Daydream was the last straw. I very much appreciate your help just the same.

tretayuga said:
Sorry, I didn't make that clear. The 5-second screen directs me to Fastboot, but there are only four options there: Start (doesn't work, obviously), Restart Bootloader (brings you back to the same place), Shut down and Recovery (goes to battery icon). Don't know what went wrong--maybe a connection got damaged when the phone was dismantled--but I discover I can't repeat the short circuiting thing and, even though the phone is seen on the system as Qualcomm 90.., MiFlash cannot flash anything different. I despair. I'll send the phone for recycling. Making the Axon 7 incompatible with Daydream was the last straw. I very much appreciate your help just the same.
Click to expand...
Click to collapse
No, when you are on the screen with the 4 options you have Fastboot. That is the bootloader mode. Get there and issue 'fastboot devices' and you'll see that you got fastboot from there.
Don't repeat the 4th category manual, just turn the phone off and hold volume up and down, then connect the USB. If it appears as Qualcomm HS-USB QDLoader 9008 you're in EDL.
What's the name of the package that you flashed?

Choose an username... said:
No, when you are on the screen with the 4 options you have Fastboot. That is the bootloader mode. Get there and issue 'fastboot devices' and you'll see that you got fastboot from there.
Don't repeat the 4th category manual, just turn the phone off and hold volume up and down, then connect the USB. If it appears as Qualcomm HS-USB QDLoader 9008 you're in EDL.
What's the name of the package that you flashed?
Click to expand...
Click to collapse
You star! I've followed your advice and now it is exactly the phone I was looking for. (I had made a mistake and forgotten to reconnect something in the internals, but the ROM worked just fine once that was sorted and I've flashed all the things you recommended.) Your name will be sung down the ages in my household, Choose an username. Many thanks

Nexus 7 stuck in APX mode, Won´t turn ON, No Backlight.

Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)

Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Take a look at this comprehensive listing of Nexus 7 button presses/interrupts. They may be of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
Hi, Gabu1405...
APX mode is never a good sign with the Nexus 7. It usually indicates that the bootloader has become corrupted, erased or overwritten (by something that is not a valid bootloader). When this occurs, the device is hardbricked and usually requires a motherboard replacement to resurrect the device, although there is a procedure called 'flatline', but this requires previously generated device unique 'blob' files, which you mention in your post.
Having said all of that though, nothing in your description should have caused the bootloader to have become 'damaged'. In order to erase, corrupt or overwrite the bootloader, your device would need to be bootloader unlocked in the first place, because a locked bootloader prohibits any unauthorised write access - bootloader locked devices can only be system 'modified' by official digitally signed updates from Google, which are flashed via the stock recovery.
Are you certain the Nexus 7 is showing as an APX device in Windows device manager?
What was the battery status/percentage when you attempted to unlock the bootloader? Maybe the tablet just needs a good charge, maybe for several hours!
You don't unlock the bootloader with ADB. Android Debug Bridge only works in fully booted Android and with the stock factory recovery. You need to use fastboot to unlock the bootloader, the command being fastboot oem unlock, whilst the device is in fastboot mode, which you boot into via the Volume Down+Power Button key press combo, as you mention in your post.
How it (may have) got into APX mode is certainly strange, because as I've said, this isn't something that normally happens spontaneously - when it happens, it's often due to people mistakenly flashing an incorrect .IMG file to the bootloader partition, causing the bootloader to be overwritten. A possible explanation is hardware failure, and that the emmc/NAND chip storage has developed a fault, and caused the bootloader to become corrupted. It's worth bearing in mind that the Nexus 7 is now seven years old, and with the best will in the world, these things don't last forever, unfortunately. Components fail and data corruptions occur.
If your Nexus 7 is truly in APX mode, for whatever reason, then I'm afraid it's likely hardbricked, and a motherboard replacement is the only realistic way of resurrecting it.
I can only suggest you try charging your Nexus 7, maybe overnight, or for several hours at least, and maybe try the button presses referenced via the link at the top of this post, and see if you can coax life back into your Nexus 7. It does happen sometimes; a seemingly dead device will suddenly spring back to life, through a combination of serendipity and hitting on doing the right things, in the right order, and at the right time
Good luck, Gabu1405...
Rgrds,
Ged.

GedBlake said:
Take a look at this comprehensive listing of Nexus 7 button presses/interrupts. They may be of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
Hi, Gabu1405...
APX mode is never a good sign with the Nexus 7. It usually indicates that the bootloader has become corrupted, erased or overwritten (by something that is not a valid bootloader). When this occurs, the device is hardbricked and usually requires a motherboard replacement to resurrect the device, although there is a procedure called 'flatline', but this requires previously generated device unique 'blob' files, which you mention in your post.
Having said all of that though, nothing in your description should have caused the bootloader to have become 'damaged'. In order to erase, corrupt or overwrite the bootloader, your device would need to be bootloader unlocked in the first place, because a locked bootloader prohibits any unauthorised write access - bootloader locked devices can only be system 'modified' by official digitally signed updates from Google, which are flashed via the stock recovery.
Are you certain the Nexus 7 is showing as an APX device in Windows device manager?
What was the battery status/percentage when you attempted to unlock the bootloader? Maybe the tablet just needs a good charge, maybe for several hours!
You don't unlock the bootloader with ADB. Android Debug Bridge only works in fully booted Android and with the stock factory recovery. You need to use fastboot to unlock the bootloader, the command being fastboot oem unlock, whilst the device is in fastboot mode, which you boot into via the Volume Down+Power Button key press combo, as you mention in your post.
How it (may have) got into APX mode is certainly strange, because as I've said, this isn't something that normally happens spontaneously - when it happens, it's often due to people mistakenly flashing an incorrect .IMG file to the bootloader partition, causing the bootloader to be overwritten. A possible explanation is hardware failure, and that the emmc/NAND chip storage has developed a fault, and caused the bootloader to become corrupted. It's worth bearing in mind that the Nexus 7 is now seven years old, and with the best will in the world, these things don't last forever, unfortunately. Components fail and data corruptions occur.
If your Nexus 7 is truly in APX mode, for whatever reason, then I'm afraid it's likely hardbricked, and a motherboard replacement is the only realistic way of resurrecting it.
I can only suggest you try charging your Nexus 7, maybe overnight, or for several hours at least, and maybe try the button presses referenced via the link at the top of this post, and see if you can coax life back into your Nexus 7. It does happen sometimes; a seemingly dead device will suddenly spring back to life, through a combination of serendipity and hitting on doing the right things, in the right order, and at the right time
Good luck, Gabu1405...
Rgrds,
Ged.
Click to expand...
Click to collapse
Sorry, I expressed myself wrongly, I ran the same command as you said, it was fastboot oem unlock and it just said, "waiting for device..." then I tried fastboot oem unlock-go, also the same thing "waiting for device" so I just disconnected the tablet and restarted it and it was working pretty fine, then I connected to the PC and tried to enter fastboot mode manually, and this is when it shut down and never turned back on.
Also, my battery was at 70% at that time and yes, It's clearly on APX mode.
Well, thank you for your reply, now the only thing I got to do is recharge it and hope for the best.
Regards.

Gabu1405 said:
Sorry, I expressed myself wrongly, I ran the same command as you said, it was fastboot oem unlock and it just said, "waiting for device..." then I tried fastboot oem unlock-go, also the same thing "waiting for device" so I just disconnected the tablet and restarted it and it was working pretty fine, then I connected to the PC and tried to enter fastboot mode manually, and this is when it shut down and never turned back on.
Also, my battery was at 70% at that time and yes, It's clearly on APX mode.
Well, thank you for your reply, now the only thing I got to do is recharge it and hope for the best.
Regards.
Click to expand...
Click to collapse
Probably not much use until, or indeed if, you can get out of APX Mode... But the 'waiting for device' message is usually an indicator of a Windows driver problem - Windows is not able to communicate with the Nexus 7.
The way you'd normally do things is by first running the command fastboot devices
This command does nothing, except to confirm you have a viable fastboot connection, by displaying your Nexus 7's unique serial number in your Windows Command/DOS box. If this serial number fails to appear, you have a driver/connectivity problem and proceeding on to fastboot oem unlock would be pointless until the driver/connectivity problem is resolved.
Anyway, I hope charging the device helps. I'm still inclined to think that your device is recoverable - it would certainly be very unusual for the bootloader to be borked when it hasn't even been unlocked yet. In the seven years I've been a Nexus 7 owner, and being active on these forums for many of those years, I haven't encountered any reports by other XDA members where a locked bootloader has simply quit working... As I say, it'd be very unusual, but I suppose not wholly impossible.
Rgrds,
GB.

GedBlake said:
Probably not much use until, or indeed if, you can get out of APX Mode... But the 'waiting for device' message is usually an indicator of a Windows driver problem - Windows is not able to communicate with the Nexus 7.
The way you'd normally do things is by first running the command fastboot devices
This command does nothing, except to confirm you have a viable fastboot connection, by displaying your Nexus 7's unique serial number in your Windows Command/DOS box. If this serial number fails to appear, you have a driver/connectivity problem and proceeding on to fastboot oem unlock would be pointless until the driver/connectivity problem is resolved.
Anyway, I hope charging the device helps. I'm still inclined to think that your device is recoverable - it would certainly be very unusual for the bootloader to be borked when it hasn't even been unlocked yet. In the seven years I've been a Nexus 7 owner, and being active on these forums for many of those years, I haven't encountered any reports by other XDA members where a locked bootloader has simply quit working... As I say, it'd be very unusual, but I suppose not wholly impossible.
Rgrds,
GB.
Click to expand...
Click to collapse
Well, charged my device for a whole day, and now I tried to do the button combinations which you sent the link, nothing happened.
I thought that my battery could be unplugged or the cable was loose or something, so I opened the tablet and it was fine.
So, I just decided to do the button combinations while plugged into my PC, and I noticed that doesn´t matter which combination I try, the tablet disconnects from the PC and instantly reconnects, but still in APX mode.
I guess it is Game Over for me, gonna recharge it again, and try again tomorrow.
Thanks again.

Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Hi!
I had a Nexus 7 stuck in APX mode as well. Without the blobs saved you can't do anything. I tried a lot of thigs but nothing really helped. I ended up searching for an another N7 with a broken screen but with a working motherboard online. I was lucky and find one around $15. I swapped the boards and it was good to go.
Zsolti

Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Check out my guide.