Last night my Nexus crashed. It was running Dirty Unicorns v8.1 and everything froze after a few apps updated from the store. Upon reboot the Nexus kept freezing up during the boot logo animation.
I tried to enter recovery but the system would never get past the Teamwin boot screen logo. The I used the Nexus toolkit to try and restore the tablet to stock but it wouldn't work no matter what I tried. Even trying to boot to a temporary recovery just hanged at the Teamwin logo.
Now I've got to the point where I turn on the tablet and I get the Google logo with the unlocked padlock. I also have on the same screen the option to boot into recovery, power off, start or restart the bootloader.
Using the toolkit to restore sock gets as far as this,
sending 'bootloader' (2100 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.437s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
Click to expand...
Click to collapse
Then the device enters APX mode as windows tries to download APX drivers. I even tried the Linux toolkit but this worked less. Just trying all my options!
Is my Nexus 7 finally dead?
Thanks for any help.
You can try the factory images.
The toolkit can't write to the bootloader so I can't flash anything. I can lock the boot loader and then recovery works. But now if I unlock the boot loader it boots into APX mode.
I'm going to pull the battery. Probably pointless but I guess it's dead already and I'm pulling at straws now. [emoji17]
Jabbitt said:
The toolkit can't write to the bootloader so I can't flash anything. I can lock the boot loader and then recovery works. But now if I unlock the boot loader it boots into APX mode.
I'm going to pull the battery. Probably pointless but I guess it's dead already and I'm pulling at straws now. [emoji17]
Click to expand...
Click to collapse
Try installing a Factory image thru FASTBOOT. using Android ADB..
Search for how to restore Nexus 7 using Fastboot.. It could be usb cable or usb driver issue .
Thanks for the suggestion but I think its dead. I can't fastboot a factory image because the bootloader is locked and no matter what I try I can't unlock it.
Can you see it in fast boot?
Fastboot device?
You can unlock it by
Fastboot oem unlock
Then flash the stock factory image directly.
You can find the images on google Dev.
Update : It is solved now.
Here's what exactly happened to my Oneplus2 -
I had successfully unlocked the Bootloader and flashed TWRP using Fastboot.
Using TWRP, I flashed SU Binary and got root privileges.
STUPID Step : I enabled ENCRYPTION on the device.
Which made it impossible for TWRP to mount the encrypted drives. But even after that I was able to boot into Recovery.
Everything was fine (obviously, I wasn't able to flash through TWRP though, due to encryption)
After some days, when I tried to boot into TWRP, the device got powered off promptly just after the boot animation flashed on screen (which hardly lasted for a second)
I don't know what happened. I was not able to reboot device into system either. It just flashes the boot screen for a second and then completely goes blank. Same is the case if I try to boot into Recovery (using Power button + Vol button)
[Currently] I am able to power off my device and boot into Fastboot Mode (using Vol Up + Power)
I tried flashing TWRP again but it fails giving the following error.
Command - fastboot flash recovery TWRP.img
target reported max download size of 536870912 bytes
sending 'recovery' (25956 KB)...
OKAY [ 0.859s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.875s
Click to expand...
Click to collapse
So I checked whether the Bootloader is still unlocked? (And unfortunately it is locked, I have no idea how)
Command - 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.078s]
finished. total time: 0.078s
Click to expand...
Click to collapse
I tried to unlock the bootloader again but still the same result.
Command - fastboot oem unlock
(I'm sure that OEM unlocking was checked and even USB debugging was enabled last time I was booted into the system)
...
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
The bootanimation flashed for a second and then again nothing happened. I again checked the bootloader status. It is still same as quoted above.
I rattled a lot around many forums to get a way to boot into the system.
So what tried was to use this command.
Command - fastboot continue
resuming boot...
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Only a charging screen appears. And on removing USB same thing happens. Device gets powered off and on trying to boot again bootanimation comes up for a second and then blank screen.
I really have no idea what to do? Any help would be appreciated.
Thanks!
Follow this
https://www.youtube.com/watch?v=R4SVSovw4Jo
Nothing to worry about, i was on MM(beta) when this happen... I try to revert back to LP but the oem is locked.. I cnt even boot my phone... But at least fastboot was ok though.. http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543 this one
Flash Stock Recovery & Flash OxygenOS Zip
muk12 said:
Follow this
https://www.youtube.com/watch?v=R4SVSovw4Jo
Click to expand...
Click to collapse
This Video is awesome saved my life...thanks a ton......
SOLVED
The Chinese recovery tool did worked in my second attempt.
Just followed the video.
First time it didn't worked but second time it did.
In my first attempt it failed with some error. I uninstalled the device from the Device Manager. Reconnected it and updated the drivers again. Installed ADB. And then just followed as done in the video and it worked in this attempt.
After the recovery process was complete the device booted normally (And didn't went into Stock Recovery as I was expecting)
I rebooted the device into recovery mode(Stock Recovery)
Then I wiped the data to remove Encryption.
Thanks for the help. Cheers !!!
Folks,
I have a ZF2L aka ZE551KL which is currently in a bootloop. Why that happened I have no idea as I have not dinked with the stock rom or for that matter even unlocked the bootloader.
A little bit of history, over the weekend, I had plugged in my phone to charge it and then when it completed charging I unplugged it and then tried to reboot it. That was the last time I had it working. After the reboot the phone has been in a bootloop ever since.
In order to try to recover from the above, I started reading a bit on what to do and I came across the postings that mentioned the bootloader has to be dropped to the Lollipop level so that it can be unlocked and then the recovery can be upgraded to Marshmallow. While trying to get all of that done, I have ended up here.
I "think" I have unlocked the bootloader using the command
echo -ne "\x01" | dd obs=1 count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo
I ran the above command directly on the phone via the terminal in TWRP. I booted into TWRP using the following fastboot command
fastboot boot twrp-3.2.3-0-Z00T.img
Running the fastboot command, fastboot oem device-info gives me the following output
C:\Users\home\android\platform-tools\images>fastboot oem device-info
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
Finished. Total time: 0.016s
However when I try to flash a new recovery TWRP-3.2.3-0-Z00T I get the following error
C:\Users\home\android\platform-tools\images>fastboot flash recovery twrp-3.2.3-0-Z00T.img
Sending 'recovery' (29856 KB) OKAY [ 1.342s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
Finished. Total time: 1.388s
I'm a little lost on what's going on. The device-info tells me the bootloader is unlocked, however it appears that something else is still locked which is not allowing the recovery to get flashed.
The stock recovery I was on before this all started was asus/WW_Z00T/ASUS_Z00T/6.0.1/MMB29P/WW_user_21.40.1220.2181_20170805. The recovery I currently have is LRX22G.WW_user_1.16.40.763_20151201
Any pointers on what I could do to get this resolved would be helpful?
hi if ur bootloader is unlocked, u an do a fresh flash of all d partitions as sometimes things get messed up on its own.
download firmware from https://drive.google.com/file/d/0B43Ue6xY9MmdN0UzWVRFcno4N0U/view and extract, then run flashall.cmd (in fastboot mode i.e. pwr and vol up)
u should finish without any hiccups. u will lose twrp though
tried on mine it woks. but google frp may be active so keep ur email n pass handy. m not responsible for any damages though ...
Hi,
Today My Asus Zenfone AR stopped working with no apparent reasons or actions performed by me.
When I try to turn it on, it simply remains stuck on the ASUS log screen.
I tried to trigger the recovery mode (POWER+VOLUME DOWN button ) with no success (nothing happens)
I tried POWER+VOLUME UP and I got the fastboot screen. The following infos are displayed:
PRODUCT_NAME - Siva
STORAGE VARIANT - UFS
BOOTLOADER VERSION - 1.21
VERSION - WWZS571KL-14.1600.1712.41
SECURE BOOT - enabled
DEVICE STATE - locked
From the menu I can select 1)start, 2)power off, 3)recovery mode, 4)restart bootloader.
Nothing seems to work, in particular if i select recovery mode, the phone reboots but it remains stuck in the logo again.
Then I tried to follow the steps described by you in: https://forum.xda-developers.com/zenfone-ar/development/recovery-twrp-touch-recovery-t3767745.
adb.exe version 29.0.6-6198805, running on windows10, seems not recognize the device while the phone is in fast boot mode (adb devices shows no output)
Instead, the device is recognized by fastboot.exe (same version). I tried the following four commands with no success:
1) fastboot flashing unlock
FAILED (remote: 'unknown command')
2) fastboot oem unlock
FAILED (remote: 'unknown command')
3) fastboot oem asus-go
(bootloader) Fail to unlock device due to invalide signature!
OKAY [ 0.036s] Finished. Total time: 0.042s
4) fastboot flash recovery twrp-3.2.1-0_CPTB-20180323-03-A002.img
Sending 'recovery' (18672 KB) OKAY [ 0.466s]
Writing 'recovery' FAILED (Status read failed (Too many links))
fastboot: error: Command failed
The phone then turns off.
I suspect the last command failed because of the device is locked but I cannot find a procedure to unlock it from fastboot. (anyway, I have zero experience on android firmware etc).
Can you suggest me on how to proceed?
Hey guys, I need help with this Asus Zenfone 2 Laser that:
Cannot boot to any OS (asus logo pops up, freezes, and then a blue screen flashes for a really short period, before it powers off, see video here.)
Can't download the unlock app to unlock bootloader
Can't access ADB
Cannot access Recovery mode
Can't "factory reset", apply update over ADB, etc.
Bootloader is locked
Can't flash custom recovery, boot TWRP, or really anything...
See fastboot reference below for more info
Code:
$ fastboot boot twrp-3.7.0_9-0-Z00T.img
Sending 'boot.img' (31066 KB) OKAY [ 0.987s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
$ fastboot flash recovery twrp-3.7.0_9-0-Z00T.img
Sending 'recovery' (31066 KB) OKAY [ 0.987s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flash boot boot.img # (Original boot.img from factory image)
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 17980722).
Sending 'boot' (17559 KB) OKAY [ 1.478s]
Writing 'boot' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem device-info
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.003s]
Finished. Total time: 0.003s
As someone who has only worked with Google Pixel phones in the past, I'm very frustrated for a few reasons.
Firstly, why the hell is the ONLY WAY to unlock a bootloader through an app that was released in such a clandestine, under-the-table way?
Second, why is the manufacturer gatekeeping the recovery files? The only way I was able to find the stock recovery.img is through a comment on a Reddit post (ironically posted by an ASUS Employee).
Third, I've been scouring the internet for many, many days trying to find any kind of emergency recovery method, but every single tutorial acts on the assumption that the bootloader is unlocked, and that boot.img, recovery.img, etc. can be flashed.
Enough about the frustration. Now let's talk about what I've tried so far.
I tried ASUS Flash Tool (Finding ADB drivers was a whole different fiasco for this device), and came up empty handed, as it doesn't detect the device when in fastboot mode.
I tried using fastboot to flash boot, recovery, system, fastboot, and dnx/ifwi, to no avail.
I tried booting into recovery via `fastboot reboot recovery`, `fastboot reboot-recovery`, `fastboot oem reboot-recovery`, and by holding Vol Down while booting up. They all give the same result, which is just an instant (<1 second) reboot. My best guess is that recovery.img is either missing or badly corrupt, so the bootloader just gives up and exits immediately.
Please help. I don't want an expensive paperweight sitting in my drawer just because of a bootloop that wasn't my fault (seriously this device just bootlooped itself one day, I didn't flash a custom rom, root or anything like that).
Any help is appreciated,
Thanks in advance
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
alecxs said:
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
Click to expand...
Click to collapse
Probably a dumb question, but how can I put my device into EDL mode?
I've tried many key combinations in conjunction with plugging it into the computer, and I've tried connecting it without a battery.
if nothing else works you need to figure out test points
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87944673
you still have fastboot? try this for EDL mode.
Code:
fastboot oem enter-dload
Good news and bad news. Good news is: I was able to enter EDL mode.
Bad news is, apparently my entire partition scheme was messed up, and upon running "edl w gpt gptboth0.bin", fastboot no longer works.
I have tried flashing aboot using edl ("edl w aboot emmc_appsboot.mbn") and it's not working.
Not to mention that it is almost impossible to find the firmware file with all the factory files such as "emmc_appsboot.mbn". The place where I got my file seemed very sketchy and I'm not surprised if the reason it's not working is because it's the wrong file.
Once again, this is a result of ASUS gatekeeping their recovery files to service centers to drive up repair sales.
If anyone has a link, or would like to provide a donor file, it would be VERY much appreciated.
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
alecxs said:
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
Click to expand...
Click to collapse
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
OS were
sj-dan said:
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
Click to expand...
Click to collapse
So we're you able to find a fix in any way? I find myself in just about the same situation tho for different reasons. I have a radiant max 5g att device i moronicaly tried to download a gsi using the dsu updater, but forgot to unlock bootloader or even enable USB debugging before attempt. So OS system is crashing an saying 'device corrupted' on boot attempt. Recovery mode gets the same result. Was able to use the bugjaegar app to connect ad run the bootloader but every repair attempt is blocked by the fact the USB debugging isn't on. To make matters worse I accidentky hit boot fastbootd command instead of normal and whatever that did wiped out my ability to even connect with bootloader so I'm kind of stuck.
faisaliteb said:
Mod. edit: spammer gone. alecxs
I found many tutorials about fixing bootloops on the Nexus but they all seem to require an unlocked bootloader.
The bootloader on the device is locked. I can see the device in fastboot devices but I can't unlock it.
Any idea how to repair this? Can I somehow flash a factory image onto the device even though OEM unlock is disabled? There is no data on the device that would need to be preserved. I'm ideally looking for a Linux-based solution. more info... ***
Click to expand...
Click to collapse
Yeah man I've been looking at this problem for over a week now and can't find much online at all to help. Except for this EDLmode some devices can boot into, and apparently you can flash a locked system using this emergency download mode. I dunno still researching.