Related
Long shot as this shouldn't be possible, but I figured I'd try asking here anyways. Is there any way to unlock a 6P that's pin-locked by Android's Device Manager?
The goal is to get the pictures off this phone. It was my brother's phone before he passed away and I've been holding on to it for the past few months - just haven't had the energy to try to deal with it...
-I have access to the gmail account.
-I tried changing the pin through Google's device manager, but since the phone was already locked, the new pin did not take. I get the message on the phone about the new pin, but it doesn't unlock it.
-Developer mode is not enabled (i.e. USB debugging).
-Not rooted or anything like that and most likely has the latest updates (t-mobile). As a matter of fact, the lock screen says that a new system update has been downloaded.
Thanks.
Try putting twrp in your adb folder, boot into fastboot and use "fastboot boot twrp.img"
clappe said:
Long shot as this shouldn't be possible, but I figured I'd try asking here anyways. Is there any way to unlock a 6P that's pin-locked by Android's Device Manager?
The goal is to get the pictures off this phone. It was my brother's phone before he passed away and I've been holding on to it for the past few months - just haven't had the energy to try to deal with it...
-I have access to the gmail account.
-I tried changing the pin through Google's device manager, but since the phone was already locked, the new pin did not take. I get the message on the phone about the new pin, but it doesn't unlock it.
-Developer mode is not enabled.
-Not rooted or anything like that and most likely has the latest updates (t-mobile). As a matter of fact, the lock screen says that a new system update has been downloaded.
Thanks.
Click to expand...
Click to collapse
The only way I can think of is by installing twrp on the phone. The only way it wouldn't work would be if he didn't have USB debugging enabled, which if he didn't then you might be out of luck... I'm so sorry.
Ghstudent said:
The only way I can think of is by installing twrp on the phone. The only way it wouldn't work would be if he didn't have USB debugging enabled, which if he didn't then you might be out of luck... I'm so sorry.
Click to expand...
Click to collapse
Unfortunately, I am pretty sure USB debugging is not enabled...sorry that's what I meant when I wrote developer mode (I've tinkered with making apps, so I know what it is).
Thanks.
Same situation here and I try to figure a solution for many days.In my opinia the only way to bypass is a modified google account manager ! Could anybody help?
@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.
RoyJ said:
@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.
Click to expand...
Click to collapse
Connecting the device to a Windows 10 PC, it will recognize the 6P, but using Windows Explorer will show no files.
Running 'adb devices' lists no devices.
When I power on the 6P, first I get the 'Google' text logo, then the colorful 'spinny' android logo, then the 'android' text logo. Then it goes to the usual lock screen (shows the time, background, etc). On this screen are the normal shortcut buttons on the bottom - microphone, padlock, camera. After a few seconds it shows the 'Locked by Android Device Manager' screen, this has a padlock symbol in the middle along with the pin code that I set online through Google's device manager.
Thanks.
Might be worth a shot to try to contact Google. You'll need proof of your identity, and the passing of your brother though. Best of luck. Sorry about your loss.
If you end up not being able to get a rep that can help via email or phone calls; you might have to do a hardmod.
tr4nqui1i7y said:
Might be worth a shot to try to contact Google. You'll need proof of your identity, and the passing of your brother though. Best of luck. Sorry about your loss.
If you end up not being able to get a rep that can help via email or phone calls; you might have to do a hardmod.
Click to expand...
Click to collapse
Hardmod? I did a quick search and the only hardmod I found was to deal with temperature.
Thanks.
RoyJ said:
@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.
Click to expand...
Click to collapse
Did you have a chance to try it?
Thanks.
EDIT: I know a way of getting out of the bootloader but it requires me to unlock it (even though I left it unlocked after initially doing it). Unfortunately, though, I think I'm left with a £150 paperweight since I need an OS on the device to enable OEM unlocking and the device literally has no OS or recovery after the hard brick. Motorola have been very "supportive" about my situation even after sending them a 10 paragraph email explaining everything which obviously, they didn't read because I wrote on the first line that the device has been rooted so they knew beforehand. I wrote 10 paragraphs, they replied with six lines, so... Yeah.
I installed LineageOS 14 on my Moto G4 months ago with TWRP and I've never had any issues until today. Literally, just updated to a new nightly build for LineageOS and my phone screen went black and didn't turn back on. I plugged it into my computer and it showed up as QHSUSB_BULK. Obviously, at this point, my device was hard bricked but I found a way online of using Qualcomm's recovery thing they have to get my phone working again, which I did. But now, I've sorta ended up soft bricking the device now.
The device boots up into the bootloader (or what I think is the bootloader). What comes up is just white text at the bottom which basically just tells me information about my phone (product/variant, serial number, CPU, eMMC, DRAM etc.) The menu for the bootloader is just one string of text that only reads 'Start' and when I press the volume buttons, it will show up with more options but they're all highlighted in red and they all lead to the same error message, as follows:
Bootloader logs
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer
to repair your device.
Connect your device to your computer to get
the Software Repair Assistant.
I've looked around Google for the Software Repair Assistant and it appears to only be for Verizon Wireless and since I'm in the United Kingdom, Verizon Wireless doesn't even exist over here, nor do I even have them as my phone carrier. I'm with O2.
Also, I've tried a few things with Minimal ADB and Fastboot but every time I enter a command, it fails and say's 'FAILED (remote failure). My phone is detected in Fastboot, but not in ADB.
Hopefully, I can get this fixed.
Thanks,
Gabriel.
Guys, i am having the same issue too. I am getting the same issue. Since verizon is not available in india, unable to repair the phone since soft bricked. Kindly help.
did you try to enter fastboot>recovery and get the robot? if you can get that try holding the the power key and tap the up volume. that should give you a drop list with a factory reset option. click it and see what happens?
same problem here.
my phone is rescued.
llaalways said:
same problem here.
Click to expand...
Click to collapse
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
maltydog said:
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
Click to expand...
Click to collapse
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did to flash the stock firmware.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
maltydog said:
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
Click to expand...
Click to collapse
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
kbonnel said:
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
Click to expand...
Click to collapse
Thanks, I understand now. I can't start this tonight, but I will try the again next time I have time at the desktop.
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
damn it, I read somewhere that there are problems while using adb on the current official beta. There was a command for getting connection again. But I can't find it right now.
Just to be clear. when the phone is on, you enabled USB debugging and plugged in the USB cable and checked the tickbox before you granted debugging access, right? If you don't check the box, there is no access granted after a phone reboot.
take care, I had problems getting through the initial phone setup after I did a factory reset. The Oreo beta still has some hickups. I got it to work after a few reboots. Without finishing the intial phone setup you can't enable USB debugging, you know.
emowing said:
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
Click to expand...
Click to collapse
Good point on the driver, I wasn't even thinking about that.
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
maltydog said:
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
Click to expand...
Click to collapse
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes.
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks.
F
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks. Trying to reply and it doesn't appear. Edit: Sorry for the multiple posts,they all appeared at once.
Okay, I am back to this now, I had time today. I installed the windows drivers from the Essential site (I am running Windows 10 64 bit) and the device was recognized in fastboot devices. The phone wiped my data and restarted with a setup screen. So far, so good. So I shut down the phone again, turned it on again in fastboot mode, it was unlocked. I went into a CMD screen and typed fastboot devices, and the phone was still listed there. So I opened windows explorer and got to the folder where I had unpacked the image files and also copied the flashboot file. I right-clicked the flashall.bat file, chose run as administrator. When I did this, I got a bunch of error messages that went by so fast, they were practically impossible to read, though they seem to say something about files not found. I didn't see any log file in the folder, so I guess they are not created. I went back to the Essential site and downloaded the zip file with the correct image files again and tried a second time, with the same results. Anyway I have wiped my phone, but still have not reinstalled the Sprint nougat software I need on this phone. Any other suggestions?
Okay, I tried again, and I was able to read the error message. They all said cannot load "filename" no such file or directory. It sounds like some kind of path error, right? I expanded the file from the Essential download for build Build NMI81C into their own directory, a subdirectory of a library where I have been keeping various android files, and I copied the flashboot file into the same directory from the platform-tools download, but only that file. That seems to be what instructions specify.
Also, I notice on this thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page3 it mentions also using the command "fastboot flashing unlock_critical" but I do not see that elsewhere.
I was able to get flashall to run using the command prompt instead of Windows Explorer. It seemed to run okay, except a couple of items cause me some concern.
I got a message "FAILED (remote: Flashing is not allowed for Critical Partitions)" for the abl.img file.
And the other command "Did you mean to fashboot format this ext4 partition".
Are either of these a problem?
Try running the commands one at a time. Open the flash-all.sh in a text editor and copy the commands.
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
maltydog said:
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
Click to expand...
Click to collapse
Did u not do the flashing unlock_critical?
Airwolf79 said:
Did u not do the flashing unlock_critical?
Click to expand...
Click to collapse
No I didn't. It was not mentioned by anyone but me in this thread until you did.
So far I have received no error messages since I did the reversion to stock. As I said,
I did get an update almost immediately.
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Same problem
Same thing happened to me. Same day as you. I can get fastboot but not adb but since the device is locked I can't flash. I've only had the phone about 6 months so I contacted customer support and they offered to replace the phone.
It might be a known issue because they didn't even try to address the fact that I could get fastboot connected but not adb. They just offered to replace.
Thanks for the info! I am -at least in this case- unfortunately an early adopter. I bought two essentials at the beginning of the pre-release.
Essential support checked my serial number and said the phone was out of warranty.
Has anyone been able to force the Essential into EDL mode to recover that way? It looks like you have to latch one of the USB pins to ground, or 5V, but I haven't found any detailed instructions on how to make this work on the essential...
Thanks again
Justin
I'm sure things have changed and I'm wrong, but if you can get into the fastboot menu can't you just cycle through the options until you get to recovery and then flash an official release from Essential?
I may be thinking of LG or something but this should be possible as long as it's newer than the current software installed because it will see it as an official update and allow the flash.
Thanks but unfortunately, when I try and do that, the phone just does the same thing, it hangs forever on the initial boot screen white Android text with the circle/square logo...
That's why I've been looking into the more direct hardware version of forcing the phone into EDL mode, which is supposed to be possible with all Qualcomm based phones.
I've just not found the time yet to find a USB-C cable I'd be happy to cut in half and short the pins on! Which is why I was hoping someone might have tried this with an essential before to know if it was successful before I start trashing good cables
Thanks again for your reply!
JB
justinbaird said:
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Click to expand...
Click to collapse
I have the exact same problem,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cannot flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you
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.