Database Users

[Q] Google nexus 7 (2012) - Unrooting leads to total failure(no recovery, no boot up)

Dear developers and other users!
I have been looking for same issues but I was unable to find answer for my problem.
About a year ago I unlocked and rooted my nexus 7 tablet to use special apps on it.
Today I tried to unroot and lock my device. On my laptop the program(Nexus Root Toolkit) said it was successful so I just needed to reboot the tablet.
After rebooting it stopped on the Google screen with a "Booting failed" text on the top left corner like that:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think I have uninstalled android from the device but I can't Intsall a new one because recovery mode doesn't work and Android is not going to boot.
I can only use Bootloader. Bootloader looks like that:
Once I started my tablet it started in bootloader mode but every other startup fails on Google screen.
Please help me to use my tablet as before without root.
What should I do and how should I do that to get it work again?
Any help would be highly appreciated ​

Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk

Carlyle_f said:
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )

Eurioin said:
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Click to expand...
Click to collapse
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid

Pirateghost said:
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Click to expand...
Click to collapse
Thank you It is still not working :/ in cmd after each command it writes waiting for device

Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Fix your drivers then. Fastboot is the surefire way to fix your issue.
#stayparanoid

Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Its much easier on a Linux machine. All you need to do is open terminal and type "sudo apt-get install android-tools-adb android-tools-fastboot" and hit enter. Then extract the .tar file and double click "flash-all.sh" and choose run in terminal. Absolutely no driver headaches.
If you have access to a Linux machine (mint/ubuntu) or if you can dualboot Linux, this will really help
Sent from my GT-I8190 using Tapatalk

I too have this same issue...
Exception is my Nexus is locked... everytime I try to unlock it, it tries to reboot and never comes back on...
What am I doing wrong?

Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type
fastboot oem unlock
Click to expand...
Click to collapse
(this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
fastboot update image-nakasi-kot49h (this was the firmware that I needed to "update")
Click to expand...
Click to collapse
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
fastboot oem lock
Click to expand...
Click to collapse
And now I am using Android 4.4.4 on my nexus 7 tablet

Eurioin said:
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type (this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
And now I am using Android 4.4.4 on my nexus 7 tablet
Click to expand...
Click to collapse
I was hopeful that this would work for me.... I am using a win 8.1 machine and the downloaded fastboot and adb seemed to work fine.
I go to do a fastboot unlock and I get the following:
(bootloader) erasing userdata...
(bootloader) erasing userdata done...
(bootloader) erasing cache...
(bootloader) erasing cache done...
(bootloader) unlocking....
FAILED (remote: (Unknown error code))
finshed. total time: 7.902s
So..... Anyone ? The tablet does ask if I want to Unlock the Bootloader... I select yes and hit the power button to select... yet the tablet goes back to the android screen... The top of the screen says Unlocking now...... yet it doesn't...
Please help...

[Q] 2012 Nexus 7 stuck in bootloop but recovery not working?

OK, after several weeks of google-ing and trying different solutions I still have not been able to find a fix for this so I'm hoping that a bit more details & illustrated post will help.
Description: I flashed the device with Cyanogen Mod, all worked fine but when I then tried to install G-apps it went through the installation process, rebooted and then stuck on the spinning Cyanogenmod logo.
I've tried rebooting it into recovery mode to find a solution. Going through the factory reset option runs through the whole process and then reboots into the looped boot logo again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I reboot the device in recovery mode I get this screen and options:
This is the text at the bottom of the recovery screen:
The screen after I hold down power & volume up (and release volume up after 3 seconds):
This is the options I get when choosing ADB mode:
Factory restore option menu:
One of the issues I think is that the device is no longer detected by my PC which seems to remove the option of pushing a new ROM to is.
Any ideas would be very much appreciate.

evertb said:
OK, after several weeks of google-ing and trying different solutions I still have not been able to find a fix for this so I'm hoping that a bit more details & illustrated post will help.
One of the issues I think is that the device is no longer detected by my PC which seems to remove the option of pushing a new ROM to is.
Any ideas would be very much appreciate.
Click to expand...
Click to collapse
Edit: The screens you're calling recovery are actually the bootloader, use the volume keys to select recovery mode, and power key to confirm. If you have a working recovery it should boot into it, just go from there to clean flash your rom again (or an alternate one if desired). If gapps gave you issues, you might try redownloading gapps (may as well check the ROM file too). If you don't have a working recovery, then follow the other instructions below.
Your device should be recoverable, you're booting into fastboot mode on the bootloader screen and are unlocked, so you should be able to use this to restore a factory image of your choice.
Use the steps in this thread (it's stickied at the top of this section) http://forum.xda-developers.com/showthread.php?t=1907796
First type the command "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode, if it returns your device's serial number, you should be good to go and won't need to follow the steps to install drivers. If it doesn't return the devices serial number, you have driver issues with adb/fastboot and will need to resolve this first (there are tips and links for installing or updating drivers in the guide).
Also, you can skip the "fastboot erase boot" and "fastboot flash bootloader" commands, as your bootloader is fine. There are also corrupt versions included in several of the google factory images, so i would recommend to just not do this if it's not needed.
Hope that helps and good luck!

Thanks for those instructions, yes have gone into recovery from the bootloader but that leads back to the bootscreen.
Will try your instructions in the morning!

PrizmaticSmoke said:
Edit: The screens you're calling recovery are actually the bootloader, use the volume keys to select recovery mode, and power key to confirm. If you have a working recovery it should boot into it, just go from there to clean flash your rom again (or an alternate one if desired). If gapps gave you issues, you might try redownloading gapps (may as well check the ROM file too). If you don't have a working recovery, then follow the other instructions below.
Your device should be recoverable, you're booting into fastboot mode on the bootloader screen and are unlocked, so you should be able to use this to restore a factory image of your choice.
Use the steps in this thread (it's stickied at the top of this section) http://forum.xda-developers.com/showthread.php?t=1907796
First type the command "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode, if it returns your device's serial number, you should be good to go and won't need to follow the steps to install drivers. If it doesn't return the devices serial number, you have driver issues with adb/fastboot and will need to resolve this first (there are tips and links for installing or updating drivers in the guide).
Also, you can skip the "fastboot erase boot" and "fastboot flash bootloader" commands, as your bootloader is fine. There are also corrupt versions included in several of the google factory images, so i would recommend to just not do this if it's not needed.
Hope that helps and good luck!
Click to expand...
Click to collapse
Where/when exactly do I type in "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode?

evertb said:
Where/when exactly do I type in "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode?
Click to expand...
Click to collapse
With the device in Fastboot mode (like your second screenshot, you'll see "Fastboot Mode" in the lower left at the top of the block of text) and connected to your PC, open a command prompt on the PC, and just type the command "fastboot devices" then hit enter.

PrizmaticSmoke said:
With the device in Fastboot mode (like your second screenshot, you'll see "Fastboot Mode" in the lower left at the top of the block of text) and connected to your PC, open a command prompt on the PC, and just type the command "fastboot devices" then hit enter.
Click to expand...
Click to collapse
At the c: prompt?
I did this and get the following error: "fastboot' is not recognised as an internal or external command, operable program or batch file...

evertb said:
At the c: prompt?
I did this and get the following error: "fastboot' is not recognised as an internal or external command, operable program or batch file...
Click to expand...
Click to collapse
Okay, then you need to install the Android SDK and Java development kit, there are links and instructions on how to do this in the guide i linked to above in the "Software Requirements" section.

PrizmaticSmoke said:
Okay, then you need to install the Android SDK and Java development kit, there are links and instructions on how to do this in the guide i linked to above in the "Software Requirements" section.
Click to expand...
Click to collapse
I did that prior to trying this.
Will uninstall everything and start from scratch.

I think you just had to be in the folder where fastboot.exe is installed. I went to the C:\Users\myname\Downloads\Android SDK\sdk\platform-tools (where I installed the sdk files). From that folder I did a shift, rt-click and 'open a command window here'. Then I typed in the fastboot command and it executed properly.

Groid said:
I think you just had to be in the folder where fastboot.exe is installed. I went to the C:\Users\myname\Downloads\Android SDK\sdk\platform-tools (where I installed the sdk files). From that folder I did a shift, rt-click and 'open a command window here'. Then I typed in the fastboot command and it executed properly.
Click to expand...
Click to collapse
I've tried all the options outlined above but am not getting anywhere for the simple reason that the device is not being detected by any computer that I connect it to.
I have deleted all drivers so it would install fresh but that hasn't made any difference either.
I looked at installing a fresh ROM via OTG but even that is not an option on the device it seems.
What I am at is the following:
- I can boot into Fastboot
- booting into recovery puts up the "dead android" screen.
- Holding down "power" and "volume up" and then releasing "volume up brings up a screen with the following options: "reboot system
now", "apply update from adb", "wipe data/factory reset" & "wipe cache partition".
- "apply update from adb" brings me to the adb screen but as the device isn't being detected I cannot do anything there. The "wipe data" & "wipe cache" options complete but then bring me back in the same screen.
There does not seem to be an option to load a ROM via the OTG cable.
Basically at this stage I cannot find *any* option to flash a fresh ROM.
Banging my head of the wall here so would really appreciate some help from people more knowledgable than me.

[solved] Can't unlock bootloader / flash recovery

EDIT:
Soulution
If you stumble upon this thread while searching for your problem...
There is no specific solution for this problem.
Allthough the phone isn't bricked, you still should do the unbreaking Method 3 in Naman Bhalla's thread on the OnePlus forums (LINK)
The phone is working perfectly again.
Also, if this problem appeared when you tried flashing OOS 3.0, check out this guide.
I did a lot of google research, found a lot of stuff and I'm still stuck at my problem.
Some background information:
I wanted to flash the new Oxygen OS 3.0 Community Build, decided to perform a clean install (full wipe with system, cache, dalvik and data).
Went into TWRP, wiped phone, installed OOS 3.0 - worked.
Made my initial setup, then I wanted to boot into recovery - didn't work.
Then I booted into fastboot, tried fastboot oem unlock, it said:
fastboot oem unlock
...
OKAY [ 0.014s]
finished. total time: 0.014s
Click to expand...
Click to collapse
Afterwards I checked fastboot oem device-info:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.080s]
finished. total time: 0.080s
Click to expand...
Click to collapse
That means still locked.
The phone won't boot up by itself.
I had to go in fastboot, and then use "fastboot continue" to get into the OS.
At the beginning, I forgot to enable the 'Allow OEM unlock' option in developer settings, it is now enabled but effect remains the same.
My question:
How do I fix my obviously broken recovery? How can I reflash it with a locked bootloader or how do I even unlock the bootloader.
PLEASE do not link me to the unbrick guides - the device is NOT bricked - it boots up with fastboot continue and also shows up as ONE A2003 when connected to pc.
What works:
+ getting into the OS (via fastboot continue)
+ getting into fastboot
What doesn't work:
- unlocking via fastboot oem unlock
- flashing a recovery (device is locked)
- booting into recovery
Thanks in advance for your help & ideas!

Hi man, what a mess did you did
I have been in that situation. (Stock in fastboot/boot logo with bootloader locked and oem unlocking disabled in seetings).
The only thing that worked for me was the naman bahlla tutorial to unbrick hard bricked devices. (The 3rd method).
The link is this one: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Anyway you can ask naman bhalla help in that thread. He will help you.
TS

Tierri said:
Hi man, what a mess did you did
I have been in that situation. (Stock in fastboot/boot logo with bootloader locked and oem unlocking disabled in seetings).
The only thing that worked for me was the naman bahlla tutorial to unbrick hard bricked devices. (The 3rd method).
The link is this one: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Anyway you can ask naman bhalla help in that thread. He will help you.
TS
Click to expand...
Click to collapse
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003

GerRudi said:
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003
Click to expand...
Click to collapse
hum. Ask Naman Bahlla for help.

GerRudi said:
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003
Click to expand...
Click to collapse
When you try to flash a recovery, what error message do you get? Curiosity question.
But I'm gonna have to echo Tierri to use that unbricking method. I get you're not bricked, but that will work to fix your issue. To get the Qualcomm device thing to show in device manager, power down your phone completely. Then connect the USB cable and press VOL UP (don't press power). You should hear the Windows connection chime. Also make sure you're booted up with Windows Device Driver Signature check turned off.
EDIT: I've followed these directions in the past: http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543

I did the same thing.
Only way is boot to system (fastboot continue) backup all files from internal memory to pc,
Restore device completly as Tierri said using method 3 unbrick guide.
Unlock bootloader in system (oos 2.2.1 or 2.2.0).
and flash oos 3.0 beta with twrp from that thread: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/

Thanks for all your replies!
As you all suggested, I decided to go through the Bhallas unbricking guide on the OnePlus forums.
This seemed to be the quickest solution out there.
I'll update the Original post with the solution, thanks.
If mods see this, thread can be closed, tagge the thread as solved.

The real op oem fix
follow these steps:
1. launch your cmd
2. plug out your phone
3. power it off
4. power into fastboot
5. plug it into the pc
6. type these commands
"adb start-server"
"fastboot devices" (your device should show in fastboot)
"fastboot oem lock" (this will reboot your phone and reset everything make sure you backup if you need to)
7. skip all OP setup steps(skipping these steps saves your time cause this process will have to be done twice also put into DEV mode and allow usb debugging)
8. once you on your homescreen power off your OP
9. plug it out of the pc
10. put it back into fastboot
11. type these commands before plugging back into pc
"adb kill-server"
"adb start-server"
12. plug it back into the pc and type these commands
"fastboot devices"
"fastboot oem unlock" (sometimes it will prompt you in some kind of asian language asking if you want to reset all your data just click the first option this will also reset your phone again)
that should fix the OEM boot unlocker now
i made this solution my self after troubleshooting like crazzy cause i had the same problem like you but didnt have to do all the extra bs with download random crap that does not really help
~xjinx216

is your bootloader unlocked now after following naman's process? please help, i've been having the same problem for ages.

I'm having this issue as well. Tried every driver and just can't seem to unlock bootloader. Adb seems to work, can boot into fastboot but then it always says fastboot cannot be detected when I try anything. Or it gets stuck on waiting for device. I just want to get this thing rooted????

Im having the same issue and my device IS bricked (and im sure i may have somehow deleted my OS) And i can't do anything to fix it, but if i deleted/corrupted my OS can it still be oem locked?

Solution
GerRudi said:
EDIT:
Soulution
If you stumble upon this thread while searching for your problem...
There is no specific solution for this problem.
Allthough the phone isn't bricked, you still should do the unbreaking Method 3 in Naman Bhalla's thread on the OnePlus forums (LINK)
Click to expand...
Click to collapse
I had about the same problems with my phone (oem unlock shows okay but doesn't unlock, directly booted the not working recovery) i was then able to boot to system with "fastboot continue".
Solution i found (root needed): flash stock recovery (from oneplus 2 downloads section) in rom with "dd" command and do a oem unlock, it will then boot to stock recovery, where you have to confirm the unlock (works with all roms but only with stock recovery).
command used to flash recovery (in android terminal emulator, adb should work too): dd if="location of recovery.img to flash" of=/dev/block/bootdevice/by-name/recovery
You can also flash twrp on a locked bootloader like this (just make sure to have a stock recovery ready on the device).
You might want to include this in front page.

GerRudi said:
EDIT:
What works:
+ getting into the OS (via fastboot continue)
+ getting into fastboot
What doesn't work:
- unlocking via fastboot oem unlock
- flashing a recovery (device is locked)
- booting into recovery
Click to expand...
Click to collapse
I got into exactly the same situation now, the problem is that "Method 3 in Naman Bhalla's thread" is not working for me as it break on "sahara error". Actually the message says to restart phone and retry, but I'm always getting into this error again and again. I already tried to reinstall drivers many times and I'm running in testing mode... what else I can try to solve this? (Windows 10 Pro)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

fastboot,unlock wont work

Hi All,
Loving my Nexus 6P but noticed after several of the OTA updates that the battery is getting worse so decided to do a factory reset, The May update hasn't come OTA yet either so thought might as well kill to birds with one stone.
Installed ADB tools on my Ubuntu machine and a quick "abd devices" brings the phone up, OEM Unlock is allowed in the developer options.
In fastboot mode "fastboot devices" also brings up the device.
so I then tried "fastboot flashing unlock" and it does nothing just brings up a list of all the options, I'm on adb 1.0.32 IIRC so the "fastboot OEM unlock" doesn't work either.
Anybody had this before, cant get it to unlock.

I noticed you said you checked oem unlock but didnt mention that you enabled usb debugging. Did you do that as well?

Yes sorry, debugging is enabled.

I used a pc but there is an article for this phone using linux (Debian/Ubuntu). You may have seen it but if not maybe this will help you out.
http://forum.xda-developers.com/nexus-6p/general/guide-unlock-nexus-6p-resorting-to-t3257388

When you initially plug phone in,were you prompted on phone to allow PC to connect to phone?
Sent from my Nexus 6P using XDA-Developers mobile app

Yes it came up and asked me if i wanted to allow fastboot or something similar, I accepted.

Fe Mike said:
I used a pc but there is an article for this phone using linux (Debian/Ubuntu). You may have seen it but if not maybe this will help you out.
http://forum.xda-developers.com/nexus-6p/general/guide-unlock-nexus-6p-resorting-to-t3257388
Click to expand...
Click to collapse
I will give this a go tomorrow! looks like it might resolve the issue.

ur on a ubuntu machine, so i cant help
but i got my wife a Nexus 5X the other day and it threw me on a loop when i couldnt "fastboot flashing unlock" since it will say "waiting on device".... im not new to this, been rooting and flashing since 2010..... and i had eom unlock and adb debug selected.... adb on android would give me serial... but not on fastboot..
came to find out i had to right click on device manager and update driver to "Android ADB Interface".... it worked fine after that
long story.... sounds to me like you may have a driver issue on ur machine connecting to the phone since the only difference between ur problem and mines is the computer used

AndrewJB88 said:
Hi All,
Loving my Nexus 6P but noticed after several of the OTA updates that the battery is getting worse so decided to do a factory reset, The May update hasn't come OTA yet either so thought might as well kill to birds with one stone.
Installed ADB tools on my Ubuntu machine and a quick "abd devices" brings the phone up, OEM Unlock is allowed in the developer options.
In fastboot mode "fastboot devices" also brings up the device.
so I then tried "fastboot flashing unlock" and it does nothing just brings up a list of all the options, I'm on adb 1.0.32 IIRC so the "fastboot OEM unlock" doesn't work either.
Anybody had this before, cant get it to unlock.
Click to expand...
Click to collapse
The problem is that your fastboot is out of date. If you're using the adb/fastboot that's native to your distro it won't work. You need to download the Android SDK and update the platform-tools package, then use that version of fastboot. Navigate to the platform-tools folder, select to open a command prompt in that location, and then issue your fastboot commands locally. This means you need to prefix each command with "./", so the commands would be like this:
Code:
./fastboot devices
./fastboot flashing unlock

chaco81 said:
ur on a ubuntu machine, so i cant help
but i got my wife a Nexus 5X the other day and it threw me on a loop when i couldnt "fastboot flashing unlock" since it will say "waiting on device".... im not new to this, been rooting and flashing since 2010..... and i had eom unlock and adb debug selected.... adb on android would give me serial... but not on fastboot..
came to find out i had to right click on device manager and update driver to "Android ADB Interface".... it worked fine after that
long story.... sounds to me like you may have a driver issue on ur machine connecting to the phone since the only difference between ur problem and mines is the computer used
Click to expand...
Click to collapse
It isn't a driver issue, adb and fastboot are native to Linux so no drivers are required.

Heisenberg said:
The problem is that your fastboot is out of date. If you're using the adb/fastboot that's native to your distro it won't work. You need to download the Android SDK and update the platform-tools package, then use that version of fastboot. Navigate to the platform-tools folder, select to open a command prompt in that location, and then issue your fastboot commands locally. This means you need to prefix each command with "./", so the commands would be like this:
Code:
./fastboot devices
./fastboot flashing unlock
Click to expand...
Click to collapse
I initially had the Ubuntu ADB tools installed but then installed the newer version over the top but that didn't resolve it either. I didn't get round to trying the guide above.

I didn't get round to fixing this, I decided to jump straight to developer preview 3 OTA which I was already running on my Nexus 9.
Battery seems a lot better.

AndrewJB88 said:
I initially had the Ubuntu ADB tools installed but then installed the newer version over the top but that didn't resolve it either. I didn't get round to trying the guide above.
Click to expand...
Click to collapse
Did you actually install the SDK from scratch? And remember to issue the prefixed (./) commands from within the platform-tools folder?

AndrewJB88 said:
I didn't get round to fixing this, I decided to jump straight to developer preview 3 OTA which I was already running on my Nexus 9.
Battery seems a lot better.
Click to expand...
Click to collapse
To update your SDK Platform-Tools package, which has the ADB, open command prompt and type
android update sdk
In the gui option select platform-tools and then OK.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Heisenberg said:
It isn't a driver issue, adb and fastboot are native to Linux so no drivers are required.
Click to expand...
Click to collapse
Thank you sir for the proper correction to my post.

I don't know if you ever resolved this, but I was having the same issue. At first I updated the sdk via manager. No luck. Then I did a complete new install, over the old. No luck. I then did a search for android to find the sdk folder on my computer to make sure there wasn't a duplicate. Turns out, the fresh install created a new location for the sdk. The one I used was still old, despite the update, apparently. I opened the new location, which was shown to have been created at the time of the new install. Ran the command, and it worked flawlessly.
Hope u worked it all out already, but if not, I'm sure urs was the same issue. I've been trying to get this done for hours. Finally got it unlocked!
Good luck

PS C:\> fastboot devices
CVH7N15A14007144 fastboot
PS C:\> fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.037s]
finished. total time: 0.037s
PS C:\> fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
PS C:\> fastboot flashing unlock
usage: fastboot [ <option> ] <command>
any suggestion?
Note: USB Debugging and OEM unlocked before I experienced another bootloop.

Heisenberg said:
The problem is that your fastboot is out of date. If you're using the adb/fastboot that's native to your distro it won't work. You need to download the Android SDK and update the platform-tools package, then use that version of fastboot. Navigate to the platform-tools folder, select to open a command prompt in that location, and then issue your fastboot commands locally. This means you need to prefix each command with "./", so the commands would be like this:
Code:
./fastboot devices
./fastboot flashing unlock
Click to expand...
Click to collapse
Tut Tut-- You the man, thanks it woked, most of all it make sense.-:laugh:

[SOLVED][A2017G]Softbricked with fastboot + TWRP deleted + unlocked

I have the A2017G unlocked + fastboot working and I had TWRP working as well.
I tried to install A2017G B09 by tron1 and now my device is stuck in a bootloop.
When I try booting / booting in recovery i get this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the message switching to recovery doesn't work and fastboot mode does (going to recovery from fastboot doesn't work as well).
I really really need help and I'm absolutely clueless as to what to do.
When I let it boot it's stuck on the last image in the boot animation (this one)
I can't put my phone into edl mode using "adb reboot edl" as it won't start, but I did manage to do it while it was booting before stuck in the loop and it's giving me the device unauthorized error:
Code:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
If I try shutting it down, and plugging it in while clicking both volume buttons it shows as QUSB__BULK but "adb devices" doesn't show anything and obviously axon7tool doesn't work.
What do I do?? Is this a hardbrick? How can I install TWRP back?
EDIT: Read my third reply:
I switched the driver to Marshall London Bootloader. Now the device doesn't show in devices but flashing with fastboot shows it's ok! I tried flashing recovery.img but it doesn't do anything. What do I do?
Click to expand...
Click to collapse

I did some testing in fastboot mode while switching drivers in ZADIG and trying adb devices/adb reboot edl. My results:
I also tried it in LeAndroid driver (Whatever that is) and it didn't work.
Driver: WinUSB
adb not working (Not found)
Shows under: usb controllers -> android
Driver: libusb-win32
adb not working (Not found)
Shows under: libusb-win32 usb devices -> android
Driver: USB serial (CDC)
adb not working (Not found)
Shows under: Ports -> Android (COM7)
Driver: libusbK
adb not working(Not found)
Shows under: libusbK usb devices -> android
I'm really lost. What can I do other than bruteforcing drivers? Please help, I fear that I hardbricked the phone... Thanks in advance

Try tenfar tool axon7root while in qusb bulk/edl mode.

If your phone is in fastboot mode you don't have to play with the command "adb", instead you need the command "fastboot".

nonamesl said:
...
I'm really lost. What can I do other than bruteforcing drivers? Please help, I fear that I hardbricked the phone... Thanks in advance
Click to expand...
Click to collapse
-Boot to FTM (shutdown and after: press and hold Volume down + Power till you see FTM screen)
-adb devices (check if your device is seen)
-adb reboot edl
-Use axon7tool to flash correct TWRP
-Revover Phone

Boot into fastboot, connect to your computer, "fastboot flash recovery twrp.img", boot into recovery, flash ROM.

Dust2Dust said:
-Boot to FTM (shutdown and after: press and hold Volume down + Power till you see FTM screen)
-adb devices (check if your device is seen)
-adb reboot edl
-Use axon7tool to flash correct TWRP
-Revover Phone
Click to expand...
Click to collapse
Read the OP + first reply, it doesn't show in adb devices
xtermmin said:
Boot into fastboot, connect to your computer, "fastboot flash recovery twrp.img", boot into recovery, flash ROM.
Click to expand...
Click to collapse
tron1 said:
If your phone is in fastboot mode you don't have to play with the command "adb", instead you need the command "fastboot".
Click to expand...
Click to collapse
Huh. I'll try that and post whatever
lafester said:
Try tenfar tool axon7root while in qusb bulk/edl mode.
Click to expand...
Click to collapse
Isn't that just for A2017/A2017U? Also I can't get it into qusb bulk, see my first reply.

xtermmin said:
Boot into fastboot, connect to your computer, "fastboot flash recovery twrp.img", boot into recovery, flash ROM.
Click to expand...
Click to collapse
tron1 said:
If your phone is in fastboot mode you don't have to play with the command "adb", instead you need the command "fastboot".
Click to expand...
Click to collapse
My phone doesn't show under "fastboot devices" when in fastboot mode... Also in device manager it shows as "Android" under "USB Devices", I changed the driver using Zadig to WinUSB, also tried with USB serial (CDC) driver, still didn't show in "fastboot devices".
EDIT:
I switched the driver to Marshall London Bootloader. Now the device doesn't show in devices but flashing with fastboot shows it's ok! I tried flashing recovery.img but it doesn't do anything. What do I do?
EDIT: Apperantly after flashing it with fastboot entering recovery mode works! I just had to wait for the message to disappear (which is odd because before the message was only when doing a system boot). Thanks for all the help!

nonamesl said:
Read the OP + first reply, it doesn't show in adb devices
Click to expand...
Click to collapse
Have you given it a try at all or is this just a big mouth ?!
I was trying to help you out after reading the post, FTM will help you to make the device show up.

Dust2Dust said:
Have you given it a try at all or is this just a big mouth ?!
I was trying to help you out after reading the post, FTM will help you to make the device show up.
Click to expand...
Click to collapse
Yes, I did try it, not just saying this because "I have a big mouth". I already solved this tho. Appreciate the help but it didn't work so I was just pointing that out.