OK, after several weeks of google-ing and trying different solutions I still have not been able to find a fix for this so I'm hoping that a bit more details & illustrated post will help.
Description: I flashed the device with Cyanogen Mod, all worked fine but when I then tried to install G-apps it went through the installation process, rebooted and then stuck on the spinning Cyanogenmod logo.
I've tried rebooting it into recovery mode to find a solution. Going through the factory reset option runs through the whole process and then reboots into the looped boot logo again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I reboot the device in recovery mode I get this screen and options:
This is the text at the bottom of the recovery screen:
The screen after I hold down power & volume up (and release volume up after 3 seconds):
This is the options I get when choosing ADB mode:
Factory restore option menu:
One of the issues I think is that the device is no longer detected by my PC which seems to remove the option of pushing a new ROM to is.
Any ideas would be very much appreciate.
evertb said:
OK, after several weeks of google-ing and trying different solutions I still have not been able to find a fix for this so I'm hoping that a bit more details & illustrated post will help.
One of the issues I think is that the device is no longer detected by my PC which seems to remove the option of pushing a new ROM to is.
Any ideas would be very much appreciate.
Click to expand...
Click to collapse
Edit: The screens you're calling recovery are actually the bootloader, use the volume keys to select recovery mode, and power key to confirm. If you have a working recovery it should boot into it, just go from there to clean flash your rom again (or an alternate one if desired). If gapps gave you issues, you might try redownloading gapps (may as well check the ROM file too). If you don't have a working recovery, then follow the other instructions below.
Your device should be recoverable, you're booting into fastboot mode on the bootloader screen and are unlocked, so you should be able to use this to restore a factory image of your choice.
Use the steps in this thread (it's stickied at the top of this section) http://forum.xda-developers.com/showthread.php?t=1907796
First type the command "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode, if it returns your device's serial number, you should be good to go and won't need to follow the steps to install drivers. If it doesn't return the devices serial number, you have driver issues with adb/fastboot and will need to resolve this first (there are tips and links for installing or updating drivers in the guide).
Also, you can skip the "fastboot erase boot" and "fastboot flash bootloader" commands, as your bootloader is fine. There are also corrupt versions included in several of the google factory images, so i would recommend to just not do this if it's not needed.
Hope that helps and good luck!
Thanks for those instructions, yes have gone into recovery from the bootloader but that leads back to the bootscreen.
Will try your instructions in the morning!
PrizmaticSmoke said:
Edit: The screens you're calling recovery are actually the bootloader, use the volume keys to select recovery mode, and power key to confirm. If you have a working recovery it should boot into it, just go from there to clean flash your rom again (or an alternate one if desired). If gapps gave you issues, you might try redownloading gapps (may as well check the ROM file too). If you don't have a working recovery, then follow the other instructions below.
Your device should be recoverable, you're booting into fastboot mode on the bootloader screen and are unlocked, so you should be able to use this to restore a factory image of your choice.
Use the steps in this thread (it's stickied at the top of this section) http://forum.xda-developers.com/showthread.php?t=1907796
First type the command "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode, if it returns your device's serial number, you should be good to go and won't need to follow the steps to install drivers. If it doesn't return the devices serial number, you have driver issues with adb/fastboot and will need to resolve this first (there are tips and links for installing or updating drivers in the guide).
Also, you can skip the "fastboot erase boot" and "fastboot flash bootloader" commands, as your bootloader is fine. There are also corrupt versions included in several of the google factory images, so i would recommend to just not do this if it's not needed.
Hope that helps and good luck!
Click to expand...
Click to collapse
Where/when exactly do I type in "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode?
evertb said:
Where/when exactly do I type in "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode?
Click to expand...
Click to collapse
With the device in Fastboot mode (like your second screenshot, you'll see "Fastboot Mode" in the lower left at the top of the block of text) and connected to your PC, open a command prompt on the PC, and just type the command "fastboot devices" then hit enter.
PrizmaticSmoke said:
With the device in Fastboot mode (like your second screenshot, you'll see "Fastboot Mode" in the lower left at the top of the block of text) and connected to your PC, open a command prompt on the PC, and just type the command "fastboot devices" then hit enter.
Click to expand...
Click to collapse
At the c: prompt?
I did this and get the following error: "fastboot' is not recognised as an internal or external command, operable program or batch file...
evertb said:
At the c: prompt?
I did this and get the following error: "fastboot' is not recognised as an internal or external command, operable program or batch file...
Click to expand...
Click to collapse
Okay, then you need to install the Android SDK and Java development kit, there are links and instructions on how to do this in the guide i linked to above in the "Software Requirements" section.
PrizmaticSmoke said:
Okay, then you need to install the Android SDK and Java development kit, there are links and instructions on how to do this in the guide i linked to above in the "Software Requirements" section.
Click to expand...
Click to collapse
I did that prior to trying this.
Will uninstall everything and start from scratch.
I think you just had to be in the folder where fastboot.exe is installed. I went to the C:\Users\myname\Downloads\Android SDK\sdk\platform-tools (where I installed the sdk files). From that folder I did a shift, rt-click and 'open a command window here'. Then I typed in the fastboot command and it executed properly.
Groid said:
I think you just had to be in the folder where fastboot.exe is installed. I went to the C:\Users\myname\Downloads\Android SDK\sdk\platform-tools (where I installed the sdk files). From that folder I did a shift, rt-click and 'open a command window here'. Then I typed in the fastboot command and it executed properly.
Click to expand...
Click to collapse
I've tried all the options outlined above but am not getting anywhere for the simple reason that the device is not being detected by any computer that I connect it to.
I have deleted all drivers so it would install fresh but that hasn't made any difference either.
I looked at installing a fresh ROM via OTG but even that is not an option on the device it seems.
What I am at is the following:
- I can boot into Fastboot
- booting into recovery puts up the "dead android" screen.
- Holding down "power" and "volume up" and then releasing "volume up brings up a screen with the following options: "reboot system
now", "apply update from adb", "wipe data/factory reset" & "wipe cache partition".
- "apply update from adb" brings me to the adb screen but as the device isn't being detected I cannot do anything there. The "wipe data" & "wipe cache" options complete but then bring me back in the same screen.
There does not seem to be an option to load a ROM via the OTG cable.
Basically at this stage I cannot find *any* option to flash a fresh ROM.
Banging my head of the wall here so would really appreciate some help from people more knowledgable than me.
Related
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.
You may be have got attracted to those new roms out there on the internet and would have probably bricked your device.Or maybe did some modding and in worst case somehow your phone bootlooped.
so please follow the guide for unbricking or solving bootloop issues:
CAUTION:
[1] FIRST OF ALL, I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE.
[2] NEVER UNPLUG THE USB CABLE WHILE FLASHING IS IN PROGRESS.IT MIGHT PERMANENTLY BRICK UR DEVICE..
ONLY FOR ZENFONE 5,A501CG/00CG
download the required files:
[1] kitkat firmware: for zenfone5(a501cg/00cg only other zf5 users download appropriate firmware from asus support page): http://dlcdnet.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-2.21.40.44-user.zip
[2] adb/fastboot files: from here
[3] device drivers:if you do not have device drivers download and install pc link on pc from asus website,it will automatically install device drivers on your pc.(download from: http://liveupdate01.asus.com/pub/ASUS/LiveUpdate/Release/ZenFone/APP/LinkRim/PCLinkSetup.exe)
IF U R BRICKED PROCEED FROM STEP 2 ELSE FOR BOOTLOOP START FROM STEP 1:
step 1] try booting into recovery and perform a factory rest and wipe cache if this solves the bootloop(in most cases it should).if it still bootloops then follow the following tutorial
step 2]extract the fastboot files on the desktop and paste the firmware(it will be in .zip)in the fastboot folder
step 3]after copying the firmware also extract and copy the recovery.img and fastboot.img file from the firmware into the fastboot folder. (don't remove original firmware zip)
now your fastbootfolder should contain fastboot files+recovery.img+fastboot.img+firmware you dowloaded(compressed in .zip)
step4]boot into the fastboot by switching off the phone and powering it on by power+vol up key until asus logo comes up
if u r returning from some other rom u need to relock the bootloader so scroll some below to see how to relockbootloader.
step5]once you booted to fastboot ,open command promt in fastboot folder (downloaded earlier) by pressing right click+shift in any blank space on folder screen and selecting open command promt here.
in cmd write:
step6]
Code:
fastboot flash fastboot fastboot.img
step7] fastboot reboot-bootloader
wait until reboot is complete then write
step8]
Code:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
step9] now we will be erasing data and cache for a clean flashing
Code:
fastboot clear data
fastboot clear cache
both of them take time and screen may turn off to save power so don't panic
next use volume keys to navigate to recovery and select it using power key .once your phone boots up showing android with belly open symbol press and hold volume up+volume down until recovery menu appears.if that does not open recovery try this:
hold volume down button, click and release vol up button,,,then finally release vol down button.
i admit it brothers,,it is sometimes really difficult to boot into recovery...but keep trying,,it is a bit difficult but is fruitful
if it doesnt appears it may be due to unssucceful flashing, unplug usb cable,force switch off phone by holding power button for few seconds.now again boot in bootloader by power button and vol up key and repeat from :step[8]
once in recovery select apply update from adb
step10] write on cmd
Code:
adb sideload <downloaded firmware name>.zip
for convenience you can rename firmware to kk.zip or any thing you like so command will be adb sideload kk.zip(it may take 15 to 20 mins)
step 11]once thats done select wipe data and cache in recovery and at last select reboot from recovery menu(dont skip this else you may face freezing on welcome screen itself)
hopefully you will boot into homescreen and be patient first bootup may take upto 20 mins.
[UPDATE] HOW TO RELOCK BOOTLOADER{only for zenfone 5 other device users pls google the procedure}
(USE THIS ONLY IF U R RETURNING FROM ANY CUSTOM ROM ITS NOT NEEDED FOR BOOTLOOPING PROBLEM)
hi guys i know u will be needing to relock the bootloader while returning to stock rom..
so what u have do is use the following steps before flashing fastboot.img that is before STEP [5] mentioned above
[1] download this file (its a zip file extract it using password zenfone-five.blogspot.com)...(link=https://drive.google.com/file/d/0B0o7qWuG7vvVRE9CV0hJWGRJS2c/view?usp=sharing)
[2]follow the on screen instructions
after the bootloader is locked carry on the steps from step[5]
PLEASE NOTE---THE UNLOCKING/LOCKING TOOL PROVIDED ABOVE IS NIETHER WRITTEN NOR OWNED BY ME...ALL CREDIT GOES TO ITS RESPECTIVE DEVELOPERS
this method can be used for:
1]unbricking
2]returning to stock rom
3]bootloop issues
IF YOU ARE NOT ABLE TO BOOT INTO FASTBOOT(maybe stuck on usb logo)--see this: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800 it is written by asus guys and will help you
thanks
if you face any issue please ask in comments...........
sources and credits===== www.windroidica.in
SCREENSHOTS DISCRIPTION:
pic 1] sideloading in progress
pic 2] the screen you will get when u will perform step [10] ( ignore the error "can't open /tmp/update-script.log")
pic 3]sideloading in progress (ignore the error: "please upgrade to newest 4.3 first")
pic 4] sideloading complete
NOT HITTING THANKS WILL LEAD TO A ZOMBIE APOCLYPSE(JUST KIDDING) ........dont forget to hit 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"
}
Kitkat link isn't working. Can I download it from another site? (Yes, it is a beginner problem )
DogeLordTR said:
Kitkat link isn't working. Can I download it from another site? (Yes, it is a beginner problem )
Click to expand...
Click to collapse
I wonder why it isn't working..... Yes u can download it from other sources. I will update the link as soon as possible...
update= download link working now...i omitted a "/" symbol and that gave the error
reserved----
AWESOME
Thanks for solution dude! You rock!
DogeLordTR said:
Thanks for solution dude! You rock!
Click to expand...
Click to collapse
Thanks bro... Ask for help anytime
hi, i have follow all the step, but until adb sideload <filename>.zip, it say at command prompt "error: device not found"
Now the phone stuck at asus logo.. :crying::cryinglease help......
zldjian said:
hi, i have follow all the step, but until adb sideload <filename>.zip, it say at command prompt "error: device not found"
Now the phone stuck at asus logo.. :crying::cryinglease help......
Click to expand...
Click to collapse
already solved the problem by using the method on this thread..
http://forum.xda-developers.com/zenfone-5/help/config-factory-partition-backup-t3316469
zldjian said:
already solved the problem by using the method on this thread..
http://forum.xda-developers.com/zenfone-5/help/config-factory-partition-backup-t3316469
Click to expand...
Click to collapse
great you have your problem solved,the error you were facing due to wrong drivers.
Cant boot recovery mode..
I am not able to boot into recovery mode..
rsunilkumar92 said:
I am not able to boot into recovery mode..
Click to expand...
Click to collapse
provide me more details. is it after flashing recovery.img? what is opening instead of recovery?
[email protected] said:
provide me more details. is it after flashing recovery.img? what is opening instead of recovery?
Click to expand...
Click to collapse
when i select recovery in bootloader, device will restart and stuck with the very frst logo.... "ASUS & Android Logo"
rsunilkumar92 said:
when i select recovery in bootloader, device will restart and stuck with the very frst logo.... "ASUS & Android Logo"
Click to expand...
Click to collapse
whats the current installed recovery?
[email protected] said:
whats the current installed recovery?
Click to expand...
Click to collapse
i tried TWRP ond also stock recovery
rsunilkumar92 said:
i tried TWRP ond also stock recovery
Click to expand...
Click to collapse
then try a guide on the forums by the name "de-brick with ruined partitions" i dont remember correctly but you'll find it easily
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.
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.