Related
I've tried to flash custom ROMs on my nexus 7, 3 times now, each time has the same result. I flash the ROM, then the Gapps and wipe data/cache. What happens afterwards is an endless boot cycle and a frozen bootloader (after rebooting into bootloader pressing up and down do nothing, neither does power button.) So i pull the battery and reboot into bootloader, now it works. This time it is a little different. Usually I can go into CMD and re flash stock, fallowing the instructions on this forum. This time when I try the command "adb reboot bootloader" I get "Failed to find device",even tho my computer recognizes it as an "Android ADB Interface." So I decided to try and re install my ADB drivers and I get "Failed to handshake device' or something along those lines.
My bootloader also reads a little differently than usual so I'll list the information below, it might be helpful.
"Product name - grouper
Variant - not defined yet
HW version - ER3
Baseband version - N/A
Signed - not defined yet
Lock state - unlocked'"
So I'm stuck with a nexus 7 in bootloader and my computer is not able to connect to it. Any help would be nice. I've already tried fallowing the returning to stock guide 3 times so please don't give me a bunch of **** about that.
Help would be nice, information/instructions would be amazing. Please help.
CptHoovsen said:
Help would be nice, information/instructions would be amazing. Please help.
Click to expand...
Click to collapse
After you boot into the boot loader, Windows sees the device name as Grouper - and there is no Windows driver for Grouper.
Try to find a Linux system to connect with. Linux is much less picky about device names.
[Q] New Nexus 7, Win 7, Nexus 7 Toolkit can't boot into Fastboot, "Too Many Links"
SOLVED!
So I went ahead, tried flashing the stock recovery, no joy (no recovery menu at all - just a bad-android image). After a while, tried flashing CWM touch (via Toolkit) - and now it's working. So, everything seems good now.
----------------
UPDATE 5 - PARTIALLY SOLVED:
So, after the last couple of things, I began to suspect bad hardware, as I alluded in those updates. And I was right.
But... it wasn't the hardware you might have thought.
It was...
(this is embarrassing)
The USB cable.
Yes, the USB cable. It was the wild variations in recognizing the fastboot mode that made me suspicious. Replaced the USB cable with another one and... stability, achieved. Unlock, root, recovery program and SU program all went without a hitch. In fastboot mode, for the first time, the device serial number shows.
HOWEVER - things are not perfect. The recovery mode from the bootloader still gives the bad-android icon.
I just used the toolkit to reflash stock recovery back to the device. This completed rapidly, without error. I then tried the recovery option in the bootloader, but again, no joy.
So at this point, I point a finger partly at the tools used to flash this - they claim there is no problem, yet the flash doesn't take at all, and no error is given. As a sometimes firmware developer, I'm used to flash being followed up by a checksum or other test to verify success of the flash. Is that not being done (shame, if not). If it is, then apparently the flash works, but the software being flashed doesn't? The stock recovery???
Any ideas on how to get this back? I just did the full unlock, which wiped all user data, and proceeded from there. I now have a solid connection, but don't really know how to get things back.
Perhaps I need to manually reinstall 4.2.2?
----------------
UPDATE 4:
So, on a lark, from fastboot in Android, I selected the "Recovery" option - it starts to boot that, then gives the Android with red triangle and exclamation point. So, looks like the recovery was toasted.
This was a brand new device earlier today. It has been completely wiped twice, and none of this has gone away. Seriously: bad device?
-----------------------
UPDATE 3:
So, I thought I'd try the direct approach, as outlined here:
http://forum.xda-developers.com/showthread.php?t=1741395
Device is in Fastboot, Device Manager shows it as ok.
I run fastboot flash recovery <file> -- and IMMEDIATELY get "fastboot has stopped working" - that's right, a hard crash in fastboot. And this is repeatable.
Am I wrong in thinking this looks more and more like a driver problem? I note that fastboot is recognized as a device maybe half the time - the other half, it gets an exclamation point in Device Manger. All I do then is restart the bootloader using the bootloader menu, and usually it fixes right up. But that's obviously a huge red flag, as the device should be recognized every time.
Is this a defective Nexus? The only thing that seems dicey is anything relating to fastboot/bootloader (which is, however, unlocked - or at least it says it is).
----------------
UPDATE 2: Using the "restart bootloader" in fastboot results in slightly worse non-recognition of the device. When I do that, I get a straight "USB Device Not Recognized" from windows - the device manager doesn't even show "Android Phone" as a class of device in this case.
---------------------
UPDATE 1: I found the thread talking about missing entries in the INF file. I added these, and got a somewhat, but not entirely, stable recognition of the Nexus 7 when in fastboot mode. Basically, sometimes it is recognized, other times it is not. By "recognized", I mean that the Windows Device Manager shows the device as "Android Bootloader Interface", with no indication of a problem (which it only does in fastboot mode - it shows as a composite ADB device when booted normally).
However - it seems it fails to recognize fastboot about half the time, although it seems that that is related to reboots - that is, a fresh boot, then going to fastboot through adb seems to work. But restarting fastboot manually fails to be recognized (Windows shows a bang by the "Android Bootloader Interface", and says the device "failed to start").
So, using 4.3.5 Nexus 7 toolkit, I tried to unlock the bootloader. Windows recognized fastboot mode, but the process errored out anyway, after maybe 15 seconds, saying "Too Many Links" - the same error as before.
Again, brand new 32gb wi-fi-only Nexus 7, with 4.2.2 update and the most basic configuration only (dev mode, usb on, etc.)
Any ideas?
-------------------------------------------------------
ORIGINAL
So this is a new, out of the box nexus 7. The only setup has been to connect to wifi, update to 4.2.2, and enable developer mode and USB debugging.
Running latest paid-for toolkit - Update 29 Feb 13, version 4.3.5
Just about everything requires the insecure fastboot, but every time I try any operation that attempts it, I get:
Booting into fastboot mode
downloading 'boot.img' ...
FAILED <status read failed <Too many links>>
I basically can't do anything - in this case, I was trying to backup.
It is being done on 64-bit win7 system that had drivers, and worked for another nexus 7 a couple months ago. But, just to be safe, I uninstalled the drivers, rebooted, and installed.
However, I see this on the home page of the toolkit:
FASTBOOT MODE [If serial shows, drivers are installed]
List of Devices attached
ADB Mode
List of devices attached
<numeric code> device
From this, it seems I should expect the word "serial" to show up if the drivers are installed?
I then unplugged the Nexus, refreshed the menu, and both Fastboot and ADB show no devices.
I then plug in the nexus - I get the usual two tone "device attached" sound, no warning or error message from Windows.Checking the Windows device manager, I see a section "Android Phone" with the entry "Android Composite ADB Interface". There are no unknown devices, which would seem then that drivers are working.
So, another refresh of the main menu, and again, I see, under ADB MODE, a single device ID number, and the word "device".
I don't know what to make of this. Apparently, per the "if serial shows" message in the main menu, drivers a NOT installed. But according to Windows, they are.
This perhaps matches the fastboot failure.
Should I see "serial"?
In any case, what do I do to get the drivers to work properly if they aren't?
And if they ARE working, then what is wrong with fastboot?
At this point, I think the toolkit is broken, and worked a couple months ago.
No, you should not see "serial". Your devices serial number should be displayed under whichever path is valid at that time. If you are in the bootloader, your device serial number should be under "fastboot". If you are booted normally, your device serial number should be under "ADB".
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1741395&highlight=guide
Erik.Leach said:
No, you should not see "serial". Your devices serial number should be displayed under whichever path is valid at that time. If you are in the bootloader, your device serial number should be under "fastboot". If you are booted normally, your device serial number should be under "ADB".
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1741395&highlight=guide
Click to expand...
Click to collapse
I've since figured that out. There was nothing at all, when in fastboot mode, only ADB. But then I found the thread describing two missing INF entries. I added those, updated the driver, and now the fastboot mode (which wasn't even recognized by windows) is now ok in the Device Manager. However, in the main menu, it shows, literally, "??????????" instead of a serial number - that is, there are question marks instead of serial number, Following that, a few spaces and then "fastboot".
Apparently, there are still inadequacies in the driver as relates to very, very new models running 4.2.2 (which this is).
BTW, I do believe I read somewhere that the stock recovery initially comes up with just the android on his back with the warning sign. You then have to hold power and tap volume up or something like that and the recovery menu becomes visible. I could be wrong, I know I had to do this on my old GNex, and those were the steps that worked.
Erik.Leach said:
BTW, I do believe I read somewhere that the stock recovery initially comes up with just the android on his back with the warning sign. You then have to hold power and tap volume up or something like that and the recovery menu becomes visible. I could be wrong, I know I had to do this on my old GNex, and those were the steps that worked.
Click to expand...
Click to collapse
Interesting. I did re-flash the stock recovery, and could get that without the android image.
stickplayer said:
Interesting. I did re-flash the stock recovery, and could get that without the android image.
Click to expand...
Click to collapse
That may have been a GNex thing that I am remembering. Either way, I'm glad you got everything all straightened out. :good:
I'm still kinda new at this stuff too, but if you need any more help, feel free to hit me up. Even if I don't know the answer to the question, I'll help you find it.
Erik.Leach said:
That may have been a GNex thing that I am remembering. Either way, I'm glad you got everything all straightened out. :good:
I'm still kinda new at this stuff too, but if you need any more help, feel free to hit me up. Even if I don't know the answer to the question, I'll help you find it.
Click to expand...
Click to collapse
Thanks! Next is trying to put 4.x on a Samsung Vibrant.
Sorry for the incorrect forum, but it appears there is no such forum for my specific device.
So story goes, I rooted it about 6 months back, lost the charger and stopped using it for maybe 2 months, found the charger yesterday, turned it on, was prompted with a System Update upon connecting to the internet, update failed, tried to do a hard reset (pwr, vol +, lock button) - it returned the message "Unrecoverable Bootloader Error (0x19000008)"
After receiving this message, I am unable to boot the device, it hangs at the "Iconia Tab" splash screen.
I tried various methods found online, including one where I put the device in the "fastboot mode" with the series of buttons previously mentioned, went as far as trying to execute the command "fastboot oem unlock" and other variants of the same command or related commands, and all of them lead me to "< waiting for device >".
This puts me in an uncomfortable position, as I am fairly tech-savvy, and normally capable of knocking out minor inconveniences such as this one.
I am fairly familiar in the android/rooting/rom'ing world with phones, and the methods used for this device were very unfamiliar, and confusing. Normally I'd just use the fastboot files to restore it to stock, and be done with it, the methods with this tablet are confusing and most solutions people have posted have been unsuccessful in my aid to fixing this.
So I ask you ladies and gentlemen, what can I do?
Any and all help is greatly appreciated, and thank you in advance.
PwnFx said:
Sorry for the incorrect forum, but it appears there is no such forum for my specific device.
So story goes, I rooted it about 6 months back, lost the charger and stopped using it for maybe 2 months, found the charger yesterday, turned it on, was prompted with a System Update upon connecting to the internet, update failed, tried to do a hard reset (pwr, vol +, lock button) - it returned the message "Unrecoverable Bootloader Error (0x19000008)"
After receiving this message, I am unable to boot the device, it hangs at the "Iconia Tab" splash screen.
I tried various methods found online, including one where I put the device in the "fastboot mode" with the series of buttons previously mentioned, went as far as trying to execute the command "fastboot oem unlock" and other variants of the same command or related commands, and all of them lead me to "< waiting for device >".
This puts me in an uncomfortable position, as I am fairly tech-savvy, and normally capable of knocking out minor inconveniences such as this one.
I am fairly familiar in the android/rooting/rom'ing world with phones, and the methods used for this device were very unfamiliar, and confusing. Normally I'd just use the fastboot files to restore it to stock, and be done with it, the methods with this tablet are confusing and most solutions people have posted have been unsuccessful in my aid to fixing this.
So I ask you ladies and gentlemen, what can I do?
Any and all help is greatly appreciated, and thank you in advance.
Click to expand...
Click to collapse
Will it boot to the stock recovery? If so, do some searching for a a200 rom or update. If it's an update, then you'll need to decrypt it (look in the Themes and Apps forum for the decrypting tool. It should be one of the first threads). After decrypting, open the zip, and pull the "update.zip" (do not extract), and copy that update.zip to your Ext SD card. Reboot to the stock recovery and see if it installs it. Might have to try several a200 update.zips before one works.
Moscow Desire said:
Will it boot to the stock recovery? If so, do some searching for a a200 rom or update. If it's an update, then you'll need to decrypt it (look in the Themes and Apps forum for the decrypting tool. It should be one of the first threads). After decrypting, open the zip, and pull the "update.zip" (do not extract), and copy that update.zip to your Ext SD card. Reboot to the stock recovery and see if it installs it. Might have to try several a200 update.zips before one works.
Click to expand...
Click to collapse
Please correct me if I am wrong, but the power + volume + lock toggle is the method used to get to the recovery?
When I try that it gives me that bootloader error and will not proceed any further.
PwnFx said:
Sorry for the incorrect forum, but it appears there is no such forum for my specific device.
So story goes, I rooted it about 6 months back, lost the charger and stopped using it for maybe 2 months, found the charger yesterday, turned it on, was prompted with a System Update upon connecting to the internet, update failed, tried to do a hard reset (pwr, vol +, lock button) - it returned the message "Unrecoverable Bootloader Error (0x19000008)"
After receiving this message, I am unable to boot the device, it hangs at the "Iconia Tab" splash screen.
I tried various methods found online, including one where I put the device in the "fastboot mode" with the series of buttons previously mentioned, went as far as trying to execute the command "fastboot oem unlock" and other variants of the same command or related commands, and all of them lead me to "< waiting for device >".
This puts me in an uncomfortable position, as I am fairly tech-savvy, and normally capable of knocking out minor inconveniences such as this one.
I am fairly familiar in the android/rooting/rom'ing world with phones, and the methods used for this device were very unfamiliar, and confusing. Normally I'd just use the fastboot files to restore it to stock, and be done with it, the methods with this tablet are confusing and most solutions people have posted have been unsuccessful in my aid to fixing this.
So I ask you ladies and gentlemen, what can I do?
Any and all help is greatly appreciated, and thank you in advance.
Click to expand...
Click to collapse
I recommend trying in the Acer A200 forum here: http://www.acertabletforum.com/forum/forum.php Does your PC recognize the table when it's plugged in? YOu could try to reflash the bootloader. Just throwing out a couple of ideas.
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
dalviking said:
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
Click to expand...
Click to collapse
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-...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. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Extentho said:
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
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-...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. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Click to expand...
Click to collapse
Thanks a lot Extentho for your feedback.
I've already tried your fair suggestion: unfortunately, I'm stuck at the end of sideloading the signed .zip.
In fact, I see on screen logs that it's applying the update "unconditionally" (that sounds good), but nevertheless, when finished it returns "xfer: 1.00x" on PC shell and in recovery menu, on device.
Now, either if I reboot or power down and boot it again, the result is the same: still bootloop-ing.
Of course, at any other attempts leveraging on administrative privilege, it says that "device is locked", including those done through the shell tool.
Some excerpts from my last launched commands:
c:\_APP\CM>adb devices
List of devices attached
51f8941d sideload
c:\_APP\CM>adb shell
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb root
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
51f8941d sideload
c:\_APP\CM>adb sideload cm-12.1-YOG4PAS3OH-ham-signed.zip
Total xfer: 1.00x
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
my zuk z1 stuck to bootloop,
and android debugging is disabled.
phone can not detecting in fastboot mode.
please help.
Extentho said:
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
Click to expand...
Click to collapse
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
dalviking said:
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
Click to expand...
Click to collapse
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Extentho said:
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Click to expand...
Click to collapse
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
dalviking said:
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
Click to expand...
Click to collapse
Try to post some pics about the troubles you encounter. If we receive a solution, this may be helpful for all of us in the future. Now, exactly, what can you acces on phone(recovery, fastboot, )?
Also, check varios threads from other phones with the same problems(one plus one, lg , htc) ,etc. Find a solved situation like yours, and we may adapt that solution to you
Hi guys,
Just to close this topic.
I was finally able to install the ZUI ROM through the QFIL program.
It's a little bit tricky, due to the fact that it is strongly suggested:
- to use a Windows 7 machine started without Signature Enforcement enabled;
- to start QFIL (admin mode) and be prepared with all needed files loaded in its GUI;
- to power off the phone, then, while pressing volume up button, inserting the USB cable, attached (better if) on a 2.0 port to PC;
- to be fast pressing "Download" button on QFIL program.
After that, I unlocked the bootloader and performed a lot of alternative recovery process.
So, I installed on the device:
- ZUI ROM
- Cyanogen OS convert from ZUI ROM
- Cyanogen OS last updated ROM
- CyanogenMod 12.1 last nightly ROM
- CyanogenMod 13.0 last nightly ROM
and the winner is...
...
...
...
... none of the above.
Each time the very same behaviour: bootloop. So, my last conclusion is: hardware failure (I guess wi-fi module).
I give up.
But for anyone searching a safe way to unlock a bootloader without accessing to developer options: the QFIL method works like a charm (once installed properly).
Thanks for support.
Messed my zuk z1
I tried to flash stock room in my zuk z1 , I downloaded Qualcomm file for the ROM and installed the required in my laptop,I wiped all data in my phone using TWRP .though my power button is not working I used tool kit to reboot my phone by connecting into fast boot mode,here comes the prob by mistake I entered the wrong command which locks my bootloader .I don't know what to do...help me.....
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
McMeth said:
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
Click to expand...
Click to collapse
I've been reading around a little, it seems like it could be a recovery issue? try the official lineage recovery if you're not already. If you can get fastboot working at all try to reflash the stock rom and go from there.
I had a similar problem. Use a windows computer with the essential drivers (you can download from reddit) and use the official cable
DO NOT use the cable supplied with the Essential phone for data transfer, it is likely to brick your phone. Use a high quality one from a reputable manufacturer!