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...

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:

[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]

[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
Reboot to EDL mode from FASTBOOT!
No more Test Point Method needed ​
Technical Details:
Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the command line and refuses to sent the command to the device. Since FastBoot command protocol is simple and text-based, it is enough to send a packet containing "reboot-edl" text over USB. The simplest way to do that is to patch Windows fastboot.exe file, replacing "reboot-bootloader" text with "reboot-edl". As "reboot-bootloader" string is found in the command line, fastboot.exe sends the same constant string to the device. So if "reboot-bootloader" is replaced with "reboot-edl", you can specify "reboot-edl" in the command line and the same text will be sent to the device.
New Update: Fastboot updated to latest version.
Tutorial:
1. Download the Fastboot_edl-v2.zip from Here.
2. Extract the zip in your desktop
3. Open the folder and double Click on Reboot.bat
{
"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"
}
4. Reboot your device to Fastboot Mode by pressing
Vol Down + Power button and connect your device with PC and Press Enter.
5. Your Device will be rebooted to EDL!
6. Now flash your Fastboot Rom with Mi Flash Tool to Unbrick your Mi Note 3. ​
Proof:
Thanks to @emuzychenko for the Idea!

This is AWESOME!! Just tested and worked amazingly.
Thank you!
Edit: the included command prompt didn't work for me though, launched standard and traversed to this folder

It would've been better if the source of this guide is also mentioned, just my thoughts
Sent from my Redmi Note 3 using XDA-Developers mobile app

Harish_Kumar said:
It would've been better if the source of this guide is also mentioned
Click to expand...
Click to collapse
Especially since most of text had been copied "as is".

Please add this to op
=> https://youtu.be/-6uErg52nKs

kaushal64 said:
Please add this to op
=> https://youtu.be/-6uErg52nKs
Click to expand...
Click to collapse
I have updated the fastboot.exe and the method also. Update your video with this and I will add it to OP.

I had replaced link for modified fastboot file please add it to op.

Harish_Kumar said:
It would've been better if the source of this guide is also mentioned, just my thoughts
Click to expand...
Click to collapse
emuzychenko said:
Especially since most of text had been copied "as is".
Click to expand...
Click to collapse
Thumbs up!

This is great
My problem solved
Many thanks

not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...

Zarko007 said:
not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...
Click to expand...
Click to collapse
Send me your current emmc_appsboot.mbn and I will check what is happening wrong there.

BRoy_98 said:
Send me your current emmc_appsboot.mbn and I will check what is happening wrong there.
Click to expand...
Click to collapse
Where to find it?

Zarko007 said:
Where to find it?
Click to expand...
Click to collapse
You can find it in the fastboot rom. Or if you have recovery rom, then go to the firmware-update folder in the zip there you will find it.

BRoy_98 said:
You can find it in the fastboot rom. Or if you have recovery rom, then go to the firmware-update folder in the zip there you will find it.
Click to expand...
Click to collapse
Maybe stupid question, but wouldn't phone go to edl mode (with red led flashing) before flashing rom and what then mbn file has to do? According to your manual it is the last step?
thanks

Zarko007 said:
not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...
Click to expand...
Click to collapse
Is your device bricked or you want to flash an official miui rom? Since your rom looks like a distributor rom not an official rom.
Sent from my kenzo using Tapatalk

sator02 said:
Is your device bricked or you want to flash an official miui rom? Since your rom looks like a distributor rom not an official rom.
Sent from my kenzo using Tapatalk
Click to expand...
Click to collapse
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....

Zarko007 said:
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....
Click to expand...
Click to collapse
Don't use this tool if your device is not bricked, your rom is a distributor rom that's why you cannot unlock your device, you have to flash miui rom prior to unlocking, you can do it thru edl mode using adb, search on miui forums and you'll find it.
Edit: check this out: http://en.miui.com/thread-235865-1-1.html
Sent from my kenzo using Tapatalk

Zarko007 said:
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....
Click to expand...
Click to collapse
If your device is not bricked, then you can reboot to EDL mode from adb. Do this to reboot to edl from adb:
1. Connect your device to PC.
2. Open adb and type: adb devices and press enter to see your device if it is connected properly.
3. When you can see your device ID, type: adb reboot edl and press enter. It will reboot your device to EDL mode.
4. Now flash your rom with Mi Flash.

BRoy_98 said:
If your device is not bricked, then you can reboot to EDL mode from adb. Do this to reboot to edl from adb:
1. Connect your device to PC.
2. Open adb and type: adb devices and press enter to see your device if it is connected properly.
3. When you can see your device ID, type: adb reboot edl and press enter. It will reboot your device to EDL mode.
4. Now flash your rom with Mi Flash.
Click to expand...
Click to collapse
I have tried it already many Times but no success...

Zarko007 said:
I have tried it already many Times but no success...
Click to expand...
Click to collapse
This must be driver problem. Install MI PC suite and it will install all necessary drivers. Then try it again.

[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.

Can't unlock bootloader zuk z1

[SOLVE]
Hi, I have a Zuk Z1 with ZUI 2.5.330 installed. So, I want to try some custom ROMs for fun, but ZUI version haven't an OEM unlock option, only have an usb debugging option. I already install adb and fastboot tools for Android, and I can reboot to bootloader through command adb reboot bootloader, but when I type fastboot devices nothing appears. When fastboot is active, in the ZUK z1 appears a black screen with the linux penguin and a status that say locked. So, if someone can give me a solution I would appreciated.
Thanks.

zsbq82 said:
Hi, I have a Zuk Z1 with ZUI 2.5.330 installed. So, I want to try some custom ROMs for fun, but ZUI version haven't an OEM unlock option, only have an usb debugging option. I already install adb and fastboot tools for Android, and I can reboot to bootloader through command adb reboot bootloader, but when I type fastboot devices nothing appears. When fastboot is active, in the ZUK z1 appears a black screen with the linux penguin and a status that say locked. So, if someone can give me a solution I would appreciated.
Thanks.
Click to expand...
Click to collapse
Check your PC, drivers, Firewall, cable etc. That are most common problems you'll find

zsbq82 said:
Hi, I have a Zuk Z1 with ZUI 2.5.330 installed. So, I want to try some custom ROMs for fun, but ZUI version haven't an OEM unlock option, only have an usb debugging option. I already install adb and fastboot tools for Android, and I can reboot to bootloader through command adb reboot bootloader, but when I type fastboot devices nothing appears. When fastboot is active, in the ZUK z1 appears a black screen with the linux penguin and a status that say locked. So, if someone can give me a solution I would appreciated.
Thanks.
Click to expand...
Click to collapse
Hi, do you find any way to solve problem? My is similar, just flash ZUI over 7.1.2 and boolader is locked....

strongst said:
Check your PC, drivers, Firewall, cable etc. That are most common problems you'll find
Click to expand...
Click to collapse
Hi, it happens the same thing. I've change the USB cable and I also try it with allinone tool, but the state of the oem does not change. If someone have another way, I'll give it a chance.
Thanks.
{
"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 this might be useful-
http://developer.zuk.com/bootloader

zsbq82 said:
Hi, it happens the same thing. I've change the USB cable and I also try it with allinone tool, but the state of the oem does not change. If someone have another way, I'll give it a chance.
Thanks.
Click to expand...
Click to collapse
Please post a log of your commands you typed so we can check this.

strongst said:
Please post a log of your commands you typed so we can check this.
Click to expand...
Click to collapse
1- adb devices ( returns my device ZUK z1).
2- adb reboot bootloader ( enters un fastboot Mode).
3- sudo fastboot devices ( same that in first step).
4- sudo fastboot oem unlock-go ( print three dots and in this step I get stuck).
That's all,
Thanks.

zsbq82 said:
1- adb devices ( returns my device ZUK z1).
2- adb reboot bootloader ( enters un fastboot Mode).
3- sudo fastboot devices ( same that in first step).
4- sudo fastboot oem unlock-go ( print three dots and in this step I get stuck).
That's all,
Thanks.
Click to expand...
Click to collapse
Sorry, but I that's not a log file. Please upload /link /screenshot whatever... The full commands and output you enter on your PC.

[SOLVE]
strongst said:
Sorry, but I that's not a log file. Please upload /link /screenshot whatever... The full commands and output you enter on your PC.
Click to expand...
Click to collapse
Well, there is no need: I already solve it. For same future issues you must go to http://developer.zuk.com/bootloader and ZUK team will send you an unlockerbootloader image. They explain with detail all the process to follow.
Thanks for the support.

Hi, could you please you used email address that they answered you?
Because i already have such problem and with some email address sent serial number to them, but unfortunately i did not receive any image or reaction, if i send for you my serial number could you give it for me?

unlock site doesn't seem to work anymore