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:
Related
Hello Forums,
I went on vacation like 2 months ago, and i brought my Nexus with me, and I thought i had lost it. My relatives found it and it was handed to me. With this being said, my nexus was uncharged for the duration of the time, and when i tried to recharge it, it flickered several times and nothing happened. I found that i should hard reset and and put it into recovery mode, but it would always say booting failed.
I searched everywhere and found that i should try and flash the stock image so i looked up several guides on how to do so. On this site i found to use a Wugfresh toolkit. When i tried flashing on both occasions, each time the cmd prompt would come up it would say
sending 'bootloader' <2096KB>....
FAILED <remote: Bootloader is locked.>
finished. total time: 0.012s
rebooting into bootloader....
OKAY
finished. total time:0.021s
<waiting for device>
BUT, my device won't ever reboot. I would always have to press power vol up and vol down.
I noticed that this is a reacurring pattern. I is unable to reboot on its own.I searched everywhere and cannot find a solution.
I am able to get into the menu
FASBOOT MODE
PRODUCT NAME
VARIANT
ETC ETC
LOCK STATE-LOCKED
I would think to unlock it, but it wont ever reboot when i tried to.
I have also tried opening cover to see if the battery wire was loose, it was slightly out of place but i put it back, but same thing.
Since you can access the bootloader, I would recommend learning how to use fastboot. I had a similar situation, and fastboot saved my N7. I'm not that experienced with fastboot, but learning was pretty simple. Search Google for instructions on how to set up SDK. Let me know if you run into any problems, and I'll do what I can to help.
chrisbo4 said:
Since you can access the bootloader, I would recommend learning how to use fastboot. I had a similar situation, and fastboot saved my N7. I'm not that experienced with fastboot, but learning was pretty simple. Search Google for instructions on how to set up SDK. Let me know if you run into any problems, and I'll do what I can to help.
Click to expand...
Click to collapse
im following a guide, but im stuck where i have to update my drivers. since my Nexus is off, when i go into the device manager, all i see is APX under other devices. Do i turn on my nexus in bootloader, or update the APX drivers?
EDIT: I did get the drivers working when i put it into bootloader , so when i look at the device manager i see "Google Nexus 7 Bootloader Interface". When i put in adb devices in the command prompt, i see
List of devices attached
C:\Users\etc\etc\....
I dont get a serial number, i dont know what im doing wrong ):
Arroma said:
im following a guide, but im stuck where i have to update my drivers. since my Nexus is off, when i go into the device manager, all i see is APX under other devices. Do i turn on my nexus in bootloader, or update the APX drivers?
EDIT: I did get the drivers working when i put it into bootloader , so when i look at the device manager i see "Google Nexus 7 Bootloader Interface". When i put in adb devices in the command prompt, i see
List of devices attached
C:\Users\etc\etc\....
I dont get a serial number, i dont know what im doing wrong ):
Click to expand...
Click to collapse
Okay, and the command prompt is where I had some trouble too. Unfortunately all of the tutorials I read assume that that the user already knows how to use a command prompt, which I didn't. So you'll want to make sure your SDK manager has "platform-tools" & "USB drivers" up to date. Also make sure that your factory image has been extracted and placed in the platform-tools folder. I used 7-zip to extract.
When you're in the command prompt, type "cd android-sdk-windows", then "cd platform-tools". From there you're ready to use fastboot. You can type "fastboot devices", and you should (if everything is installed correctly) see your devices serial number displayed. From there you can type the necessary commands to restore your device.
Arroma said:
Hello Forums,
Click to expand...
Click to collapse
android adb folder (password to zip is jt100)
^ download that and extract the Android folder to the root of your C: harddrive (so it'll be C:/Android) this is the main adb/fastboot/whatever folder you'll ever need, ever.
- hold down shift and then right click within the android folder and select "open a command prompt here" (or something like that)
Arroma said:
i do see the serial, but now im unsure of what commands to use, the guide said to do oem fastboot unlock, but it failed
Click to expand...
Click to collapse
-fyi...the command 'adb devices' is for when your device is booted up to the android homescreen and 'fastboot devices' is obviously when you're in bootloader
-'fastboot oem unlock' is to unlock the bootloader
then, if you have the 4.3 factory image from google on hand...
-extract the initial zip, and you'll get like 5 files
-copy those 5 files to the same C:/Android folder from earlier
-make sure your nexus is in bootloader screen and then just double click the 'flashall' .BAT file (if you're running windows OS) and android will auto wipe and flash everything
-just let it sit and wait for your device to boot to setup screen
chrisbo4 said:
Okay, and the command prompt is where I had some trouble too. Unfortunately all of the tutorials I read assume that that the user already knows how to use a command prompt, which I didn't. So you'll want to make sure your SDK manager has "platform-tools" & "USB drivers" up to date. Also make sure that your factory image has been extracted and placed in the platform-tools folder. I used 7-zip to extract.
When you're in the command prompt, type "cd android-sdk-windows", then "cd platform-tools". From there you're ready to use fastboot. You can type "fastboot devices", and you should (if everything is installed correctly) see your devices serial number displayed. From there you can type the necessary commands to restore your device.
Click to expand...
Click to collapse
i do see the serial, but now im unsure of what commands to use, the guide said to do oem fastboot unlock, but it failed
Arroma said:
i do see the serial, but now im unsure of what commands to use, the guide said to do oem fastboot unlock, but it failed
Click to expand...
Click to collapse
The command you'll want to use if you want your bootloader unlocked is "fastboot oem unlock" Just a hint, every command should begin with "fastboot". If all you want to do is restore the factory image, I can help you with those commands as well.
You're limited to Fastboot commands when your device is booted to the boot loader. ADB commands only work if you can get booted into Android. You'll have to recover your tablet strictly using fastboot commands. Wugfresh's root toolkit should work now that you have the device drivers loaded. First step is to unlock the boot loader. Then proceed with flashing the factory image.
wugfresh doesnt work, it always fails to unlock, even using the commands, says Unknown Error
Arroma said:
wugfresh doesnt work, it always fails to unlock, even using the commands, says Unknown Error
Click to expand...
Click to collapse
read my earlier post, forget using the damn toolkit
@jt.one I agree using a toolkit is a waste of time, especially when the OP has already accessed fastboot. He's practically done.
mandad since
jt.one said:
then, if you have the 4.3 factory image from google on hand...
-extract the initial zip, and you'll get like 5 files
-copy those 5 files to the same C:/Android folder from earlier
-make sure your nexus is in bootloader screen and then just double click the 'flashall' .BAT file (if you're running windows OS) and android will auto wipe and flash everything
-just let it sit and wait for your device to boot to setup screen
Click to expand...
Click to collapse
Right so, i did everything you said, and it was working, until somewhere along the middle it failed cause its still locked, but i cant unlock it cause it always fails to unlock due to an unkown error ):
After sending fastboot devices, and getting a serial number, send fastboot oem unlock. Then flash a factory image. Here's a good tutorial on how to flash Android 4.3..
Arroma said:
Right so, i did everything you said, and it was working, until somewhere along the middle it failed cause its still locked, but i cant unlock it cause it always fails to unlock due to an unkown error ):
Click to expand...
Click to collapse
even though you did 'fastboot oem unlock'..... your bootloader refuses to unlock?
now that is strange...
{
"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"
}
jt.one said:
even though you did 'fastboot oem unlock'..... your bootloader refuses to unlock?
now that is strange...
Click to expand...
Click to collapse
i dont understand either, errors everytime ):
You don't see a fastboot response like this?
Then you'll need to tell us specifically, every error message that pops up.
exglynco said:
You don't see a fastboot response like this?
Then you'll need to tell us specifically, every error message that pops up.
Click to expand...
Click to collapse
i do see that, and i use the power button for yes, here ill copy and paste what i saw on the internet some guy is having the same problem im having, only noone replied to his thread
"My problem is that I cant unlock my bootloader.
This is what I tried:
fastboot oem unlock
This is the result:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
On my device in fastboot it just adds the text "unlocking now......" and nothing happens. If I try to reboot with i.e fastboot reboot-bootloader the device screen is just black, im not sure its even on."
-cant give credit to the guy cause i cant post links yet,
sorry on not being clear enough, i really appreciate your help
Arroma said:
i do see that, and i use the power button for yes, here ill copy and paste what i saw on the internet some guy is having the same problem im having, only noone replied to his thread
"My problem is that I cant unlock my bootloader.
This is what I tried:
fastboot oem unlock
This is the result:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
On my device in fastboot it just adds the text "unlocking now......" and nothing happens. If I try to reboot with i.e fastboot reboot-bootloader the device screen is just black, im not sure its even on."
-cant give credit to the guy cause i cant post links yet,
sorry on not being clear enough, i really appreciate your help
Click to expand...
Click to collapse
You're device wouldn't boot prior to unlocking the bootloader, right? I would try flashing the factory images, then unlocking the bootloader... if that;s possible.
chtfte was
chrisbo4 said:
You're device wouldn't boot prior to unlocking the bootloader, right? I would try flashing the factory images, then unlocking the bootloader... if that;s possible.
Click to expand...
Click to collapse
im not sure i understand, i cant flash anything because its still locked
Arroma said:
im not sure i understand, i cant flash anything because its still locked
Click to expand...
Click to collapse
I apologize, just a crazy idea I had.
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...
Hey guys,
I was hoping you might help me as I was struggling to find an answer through google search.
After using the ZUK Z1 (Cyanogen OS 12.1 with the latest update), a few days ago the phone suddenly restarted and entered an endless restart loop
I've tried wiping the data, the cache and the user files.
I've tried applying the latest CyanogenOS zip for the Z1 either through sideload or locally from the device.
Nothing worked and I'm becoming very frustrated
I thought that maybe if I could wipe the system partition and then apply the COS zip than maybe it would work.
Does anybody have any ideas?
Thanks in advance,
Yoav.
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too too.
Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
{
"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"
}
Does anyone has any idea what that means? Does that mean that it is a hardware failure?
yoavk said:
Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
Does anyone has any idea what that means? Does that mean that it is a hardware failure?
Click to expand...
Click to collapse
Ok, so first, don t panic. If you re able to acces recovery and fastboot mode, there is a strong hope. I have Windows 7 on my PC, btw.
I tried the qpst tool to flash the stock, but i couldn t. That is why i turned to the Zuk Tool Kit, which did the trick for me.
To use this tool, FIRST OF ALL YOU MUST INSTALL ADB AND FASTBOOT. you can find varius tutorials about this on te interent. I provide you some, too:
http://forum.xda-developers.com/showthread.php?t=2588979
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
It was hard for me too to understand what is going on at first, but i did some research on the topic, and i got it.
After you installed adb, you can check if it is instaled by running the command "adb version" in CMD:
You should recieve something like this if it is installed.
After you installed fastboot and adb, install the Zuk Toolkit following the steps provided in the thread of Lenvo Zuk toolkit. Download cygwin, open cygwin terminal and drag start.sh from zuk toolkit folder into terminal window, press Enter, and you will have the menu open like this:
Here, just naviagte by writing the number corresponding to the menu you want to access and hitting enter.
Under "6. Do some basic ADB and Fastboot commands.
" coomands, you will have this menu:
Do note that [fASTBOOT] marked commands will work only when your phone is in fastboot mode. To acces your fast boot mode of your phone, just select "reboot to bootloader" option from recovery menu.
Once you managed to reach this state, you can put your phone in fastboot mode, and try the command "10. [Fastboot] Reflash to stock using a manually downloaded factory image."....
IF this doesn t work, try to flash the stock rom via sideload option from recovery menu of your phone. To do this, you must chose the sideload option from recovery menu. Download the stock signed rom from here https://cyngn.com/support(NOT THE FASTBOOT ONE, JUST THE SIGNED ONE.) Rename your stock rom zip file you just downloaded "sideload" and place it on desktop. Then use THE command "4. [ADB] Sideload a zip file.
" from zuk toolkit to flash the rom. Also you must have the phone connected to pc with the USB-c cable during the whole process, of course. If it works, your phone will show the animation of flashing procees on its screen. Wait until the phone stops, chose wipe dalvik and reboot.
Use the snipping tool or PrtSc to take screen images from where you are stuck or you don t know what to do, and post them here.
Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
C:\ WINDOWS\ system32> fastboot -i 0x2b4c oem device-info
< waiting for device >
Click to expand...
Click to collapse
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg
yoavk said:
Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg
Click to expand...
Click to collapse
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
When you chose the install Update pacakge option, what options are displayed on your phone?
Also, if u installed qpst, you shoudl have in your PC a program callled QFIL, which is the flasher tool for all lenovos including ZUK. You must flash the zui stock rom using qfil. Read this thread for more info and downloads: http://forum.xda-developers.com/zuk...ui-version-t3265741/post64865607#post64865607
Also, here is a thread of a guy who had pretty much the same problem as you and managed to flash the stoc using QFIL : http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257
Extentho said:
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
Click to expand...
Click to collapse
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.
yoavk said:
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.
Click to expand...
Click to collapse
I think you could try un-bricking it by yourself. It is not that hard. But if those guys from coolicool will change your phone, that s ok too. Blease be advised that rooting voids warranty...soo
Lucky me I didn't have the chance to do it
I didn't even have the chance to unlock the bootloader
Does anyone here have any experience with the guys over at coolicool?
i flashed coldbird's zip for capacitive touch on the fingerprint sensor. got into an endless restart loop after that. to every option, the toolkit replies command not found.
eg: ./xposeduninstallbootloop.sh: line 128: adb: command not found
followed by whatever option was ordered, that has been done successfully but can see no change.
Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056
Easy bro easy, the steps that you are following are a bit confusing, aren't they?
Please tell me the current status of your phone. I might be able to help.
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"
}
Hi, I am wanting to root my shield tv box but I have already flashed a full android version onto it, which works ok, but i want to root it and cannot because
I can't root without a custom recovery.
I cannot get custom recovery without being able to do a fastboot
I cannot do fastboot because I cannot say OK to the pop-up to permit this computer to always be accepted for debugging
I cannot say OK because my mouse/keyboard stops working when the pop-up appears (debug connected to this computer OK? notice)
I thought of using droidmote but I cannot because I am not rooted!!!
How to get past this? Is it possible?
tx
Mark.
fredphoesh said:
Hi, I am wanting to root my shield tv box but I have already flashed a full android version onto it, which works ok, but i want to root it and cannot because
I can't root without a custom recovery.
I cannot get custom recovery without being able to do a fastboot
I cannot do fastboot because I cannot say OK to the pop-up to permit this computer to always be accepted for debugging
I cannot say OK because my mouse/keyboard stops working when the pop-up appears (debug connected to this computer OK? notice)
I thought of using droidmote but I cannot because I am not rooted!!!
How to get past this? Is it possible?
tx
Mark.
Click to expand...
Click to collapse
In this case you need to enter fastboot via hw method. Read root thead for how since it's different for models.
oldpoem said:
In this case you need to enter fastboot via hw method. Read root thead for how since it's different for models.
Click to expand...
Click to collapse
Hi,
I can get into Fastboot mode by pulling out the AC cable, pressing and holding the on button while plugging in the ac cable, then waiting a few seconds, and Fastboot pops up, BUT because I did not say OK to the message that comes up in Android when I plug the computer into the Shield TV device, the device is not found in Fastboot mode. I have tried this many many times, using usb cables that work, and usb ports that work... that HAVE worked with this exact same device on previous flashes over the years.... it seems I have catch 22, cannot be seen and cannot change unless I'm seen.
fredphoesh said:
Hi,
I can get into Fastboot mode by pulling out the AC cable, pressing and holding the on button while plugging in the ac cable, then waiting a few seconds, and Fastboot pops up, BUT because I did not say OK to the message that comes up in Android when I plug the computer into the Shield TV device, the device is not found in Fastboot mode. I have tried this many many times, using usb cables that work, and usb ports that work... that HAVE worked with this exact same device on previous flashes over the years.... it seems I have catch 22, cannot be seen and cannot change unless I'm seen.
Click to expand...
Click to collapse
Don't confuse fadtboot with adb. The popup dialogue relates to adb. When you enter fastboot the reason your computer doesn't see probably because your shield fastboot drivers is incorectly installed. The drivers in fastboot is different from adb drivers.
When you put shield in fastboot connect to pc and look in device manager. If there is exclamation mark on Shield or unknown device. That means drivers is not properly installed. Try fix the dtivers and you can run fastboot command.
EDIT:
I cannot do ADB commands but can do fastboot ones... so for the moment, all is good, busy flashing, no problem...
NOTE:
I could not do fastboot commands either, so I rebooted my box to android and went to settings and enabled debugging and switched on the OEM unlocking. Went back to recovery/fastboot mode and suddenly the fastboot commands did work... so one does have to turn debugging on.
oldpoem said:
Don't confuse fadtboot with adb. The popup dialogue relates to adb. When you enter fastboot the reason your computer doesn't see probably because your shield fastboot drivers is incorectly installed. The drivers in fastboot is different from adb drivers.
When you put shield in fastboot connect to pc and look in device manager. If there is exclamation mark on Shield or unknown device. That means drivers is not properly installed. Try fix the dtivers and you can run fastboot command.
Click to expand...
Click to collapse
Hi, thanks for the input @oldpoem
{
"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"
}
See the image, in my win device manager, the device is seen ( I am in fastboot /recovery mode on the box) but when I type
D:\Android\stock\723>adb reboot bootloader
I get:
error: no devices/emulators found
if I type D:\Android\stock\723>fastboot flash staging blob
I get
Sending 'staging' (5277 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
I have tried other USB sockets and cables, but they all show, as seen in the image, my shield (android bootloader device) is visible. On the taskbar, I get this,
Or am I still confused!?
Tx
Mark.
fredphoesh said:
EDIT:
I cannot do ADB commands but can do fastboot ones... so for the moment, all is good, busy flashing, no problem...
NOTE:
I could not do fastboot commands either, so I rebooted my box to android and went to settings and enabled debugging and switched on the OEM unlocking. Went back to recovery/fastboot mode and suddenly the fastboot commands did work... so one does have to turn debugging on.
Hi, thanks for the input @oldpoem
See the image, in my win device manager, the device is seen ( I am in fastboot /recovery mode on the box) but when I type
D:\Android\stock\723>adb reboot bootloader
I get:
error: no devices/emulators found
if I type D:\Android\stock\723>fastboot flash staging blob
I get
Sending 'staging' (5277 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
I have tried other USB sockets and cables, but they all show, as seen in the image, my shield (android bootloader device) is visible. On the taskbar, I get this,
Or am I still confused!?
Tx
Mark.
Click to expand...
Click to collapse
This is normal. When box is in fastboot mode it won't responsed to adb command, thus no devices found. ADB command is only usable when box is in android and usb debugging turned on. Your confirmation popup related to this.
You are confused when sending adb command when your box is in fastboot mode.
In fastboot mode you can send only fastboot command. Also it is also normal that you needed oem unlock before you can use fastboot flash command. It is required step.
oldpoem said:
Also it is also normal that you needed oem unlock before you can use fastboot flash command. It is required step.
Click to expand...
Click to collapse
AH ok, so that is why Fastboot commands were was not working!
Thanks for the help.
Mark.