Database Users

Can not flash anything, PLEASE HELP

ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks

zendick said:
ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
Click to expand...
Click to collapse
There should be an option on fastboot to go to bootloader and then from there recovery should be available, is that option available to you?

yes but recovery won't boot, sits at mt4g boot screen or sits at 3 skaters in center screen, depending on how I access it (ie go to fastboot then back again)

Power down your phone, hold volume down and the power button. That will take you into the hboot screen. You can then select to go into recovery from there.

thats what I have tried, it goes to three skaters center screen does nothing

I have tried flashing recovery from fastboot
tried hboot from fastboot
tried radio from fastboot
NOTHING flashes trust me I have been androiding for a while now never had I had a problem like this.

zendick said:
thats what I have tried, it goes to three skaters center screen does nothing
Click to expand...
Click to collapse
Is three skaters your boot animation or splash screen? Not sure what that is referring to.

the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens

zendick said:
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
Click to expand...
Click to collapse
Oh ok, i know what your talking about now. Your on the bootloader screen under fastboot. And when you select recovery option it does not boot into recovery?

correct and like i said I have tried to reflash everything from fastboot but no go

Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error

got recovery to boot but get
e:can't mount /cache/recovery/command
etc
tried to mount, tried to format
no go

What do you mean tried ruu??
zendick said:
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
Click to expand...
Click to collapse
Edit: nvm. Is doing RUU better option than loading PD15IMG.ZIP on sdcard and doing it that way?
Sent from my SGH-T959 using XDA App

tried a pd15 and it doesn't complete, drops a failed message

Sounds like you maybe victim of fail-pu. But if thats not the case and you don't care about your "/data" and just want working phone again then I suggest from fastboot you do "fastboot flash recovery recovery.img" which will replace the current recovery.img and flash it to mmcblk0p21. Once thats done do "fastboot erase system -w" and it will nuke everything so /system, /data, ect will all be erased. After that you can enter recovery by selecting it from hboot and then do factory wipe and flash another rom.
Keep in mind you will run in to errors in recovery after -w as its normal but depending on the fail-pu if you do get the failed partition update flag you can't make any changes as the errors will stick because you can't format the drives. Also the new recovery.img for CWMR can be found in dev section if not post here and ill send you.

I don't care at all about the data (I am well backed up) but I can't flash a recovery I have tried through fastboot, I agree the partition is F_D but I will try the erase system -w and see if that lets me do anything
thanks

uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s

Exactly what I got too, seems we have bricked our phones. Wish I had a way of making the phone unable to boot to recovery or at all.
zendick said:
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

I dont get how a phone can run for weeks since its last flash and have this happen, I made no changes updates etc just running as normal.
Is there a way to wipe evidence of cm of so I can get this phone repaired? To me this obviously a faulty emmc, I just can't see it being anything else.
or is it possible to boot recovery on sd like the nook?

any ideas on how to wipe cm bits atleast?

[Q] Is my Nexus 7 (Grouper) recoverable?

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.

Bricked 2012 Wifi Only Nexus 7, Please Help

Sorry if this has been addressed but I've been searching and reading and freaking out because I can't find out how to recover my Nexus 7.
I'm trying to manually update my 2012 Wifi Only Nexus 7 to Lollipop and my computer will not see the device any longer in ADB.
I downloaded the latest sdk and the latest image file (Nakasi 5.0.2 (LRX22G).
Ran through the steps found here: http://www.androidcentral.com/how-manually-upgrade-your-nexus
At this step fastboot flash bootloader [bootloader file].img it just sat there for about an hour and didn't do anything.
***Edit- I got it to work and then got the invalidstate error.
I then read that others have had success updating to Lollipop without updating there bootloader here: http://android.stackexchange.com/qu...t-flash-bootloader-failed-remote-invalidstate
***This is because my bootloader was already on 4.23.***
I then proceeded with fastboot -w update [image file].zip
The image failed after wiping everything with an error about too many links.
Now when I try I get "C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot -w upd
ate image-nakasi-lrx22g.ziparchive does not contain 'boot.sig'"
At this point, I can't get any adb commands to work as the device is not showing up as a connected device. I've rebooted my pc and the tablet multiple times. Fastboot keeps crashing as well.
Please help me get my Nexus back up and running. Thanks so much.

The Bootloader in the factory image is not valid see here
If you still can get into fastboot on your device,
Extract the img files from the zip file and manually flash each of them.
Alternatively, you could extract all the .img files in the zip file and flash them manually one at a time. This makes things really handy if you're using the factory image to act as an update rather than a complete return to stock. If trying to update using the factory image, extract the .img from the zip file into the same directory as your bootloader and radio img files and execute the following commands in order:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
Click to expand...
Click to collapse
Quote taken from here

corkiejp said:
The Bootloader in the factory image is not valid see here
If you still can get into fastboot on your device,
Extract the img files from the zip file and manually flash each of them.
Quote taken from here
Click to expand...
Click to collapse
Thanks, this is what I get
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
sending 'system' (648819 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>

touch_rules said:
Thanks, this is what I get
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
sending 'system' (648819 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
Are you in fastboot mode?
Step 4: Make sure the device is connected to the computer while in fastboot mode. Different devices may require different commands to get into fastboot mode. Make sure the device is powered off and then use the following button commands:
Nexus 7 - Vol Down + Power
Click to expand...
Click to collapse
Since you issued an Adb command first, suggest your not?
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.

corkiejp said:
Are you in fastboot mode?
Since you issued an Adb command first, suggest your not?
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.
Click to expand...
Click to collapse
Yes, I am. Please take a look at this picture. Thanks.
View attachment 3085046

Now I'm getting this At least it's different
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
erasing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 0.176s

corkiejp said:
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.
Click to expand...
Click to collapse
Noticed this part after I posted last, seems to be working....I'll let you know. Thanks so much. Wish I would have seen the toolkit earlier today when I started haha.

You rock corkiejp! Working like a champ now! Thanks so much.

I had exactly the same problem and ended up using Wug's toolkit and the individual images.
Sent from my Nexus 7 using XDA Free mobile app

I literally had it restore the factory image and it did it all. Made sure I had force flash checked.

Man, I really need some help here. i am in a almost exact situation here. Only thing different is that my tablet is locked. I go to wugs and flash stock image and get stuck on "waiting for device".
{
"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"
}
Any help would be highly appreciated!!!

Your bootloader is locked.
rayandreas said:
Man, I really need some help here. i am in a almost exact situation here. Only thing different is that my tablet is locked. I go to wugs and flash stock image and get stuck on "waiting for device". View attachment 3237509
Any help would be highly appreciated!!!
Click to expand...
Click to collapse
Hi, rayandreas...
Something is definately not quite right with your posted screenshot/output.
Transcribing it as follows, we have...
Code:
erasing 'boot'...
OKAY [ 1.154s]
finished. total time: 1.155s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 3.045s]
finished. total time: 3.045s
erasing 'recovery'...
OKAY [ 0.240s]
finished. total time: 0.241s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.014s]
finished. total time: 0.014s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.014s]
finished. total time: 0.014a
So far, so good.
I can see nothing wrong with this output, thus far... and I've seen something similar on my Nexus 7 many times when I've fastboot flashed stuff.
----
But then this bombshell hits!!
Code:
sending 'bootloader' <2100 KB>...
[COLOR=RED][B]
FAILED <remote: Bootloader is locked.>
[/B][/COLOR]
finished. total time: 0.015s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
----
WTF!!!
Bootloader is now locked!
How is this even remotely possible?
----
If the bootloader is locked, the first half of your posted output simply shouldn't have been possible... But yet, your screenshot proves otherwise.
The bootloader is either locked and NO fastboot flash commands are possible, or the bootloader is unlocked and ALL fastboot flash commands are possible...
Your Nexus 7 seems to have 'changed its mind' about its bootloader lock status, halfway through fastboot flashing!!!
----
To determine the bootloader lock status of your Nexus 7, you need to boot your Nexus 7 into it's bootloader manually...
*** shut down the device completely.
*** press and hold VOL DOWN, and press POWER ON.
*** the text in the lower left hand corner of the screen should indicate the devices bootloader locked status.
See my attached screenshot for the sort of thing you should expect to see if the bootloader is unlocked.
---
If it's locked, try unlocking it manually (ie, via fastboot), with...
Code:
fastboot oem unlock
Hope this helps.
Rgrds,
Ged.

GedBlake said:
Hi, rayandreas...
Something is definately not quite right with your posted screenshot/output.
Transcribing it as follows, we have...
Code:
erasing 'boot'...
OKAY [ 1.154s]
finished. total time: 1.155s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 3.045s]
finished. total time: 3.045s
erasing 'recovery'...
OKAY [ 0.240s]
finished. total time: 0.241s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.014s]
finished. total time: 0.014s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.014s]
finished. total time: 0.014a
So far, so good.
I can see nothing wrong with this output, thus far... and I've seen something similar on my Nexus 7 many times when I've fastboot flashed stuff.
----
But then this bombshell hits!!
Code:
sending 'bootloader' <2100 KB>...
[COLOR=RED][B]
FAILED <remote: Bootloader is locked.>
[/B][/COLOR]
finished. total time: 0.015s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
----
WTF!!!
Bootloader is now locked!
How is this even remotely possible?
----
If the bootloader is locked, the first half of your posted output simply shouldn't have been possible... But yet, your screenshot proves otherwise.
The bootloader is either locked and NO fastboot flash commands are possible, or the bootloader is unlocked and ALL fastboot flash commands are possible...
Your Nexus 7 seems to have 'changed its mind' about its bootloader lock status, halfway through fastboot flashing!!!
----
To determine the bootloader lock status of your Nexus 7, you need to boot your Nexus 7 into it's bootloader manually...
*** shut down the device completely.
*** press and hold VOL DOWN, and press POWER ON.
*** the text in the lower left hand corner of the screen should indicate the devices bootloader locked status.
See my attached screenshot for the sort of thing you should expect to see if the bootloader is unlocked.
---
If it's locked, try unlocking it manually (ie, via fastboot), with...
Code:
fastboot oem unlock
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you for even taking time for helping me thus far. I can say that it states the boot loader is locked. I have tried using wugs to unlock it but it doesn't work. I can't boot it up either. Just stays on the google splash screen. I am at a loss at what to do as of now. If I could get some help on how to rescue this thing I would be glad to donate a 12 pack or a 10 coffee or something. I received the tablet this way. I am hoping to fix it so my wife can use it.

rayandreas said:
Thank you for even taking time for helping me thus far. I can say that it states the boot loader is locked. I have tried using wugs to unlock it but it doesn't work. I can't boot it up either. Just stays on the google splash screen. I am at a loss at what to do as of now. If I could get some help on how to rescue this thing I would be glad to donate a 12 pack or a 10 coffee or something. I received the tablet this way. I am hoping to fix it so my wife can use it.
Click to expand...
Click to collapse
Hi again, rayandreas...
If it where my tablet, I'd just fastboot flash the Google factory stock image for your device.
The Google factory stock image for your device can be found here...
https://developers.google.com/android/nexus/images#nakasi
There's little point in my re-inventing the wheel by writing yet another tutorial... full details and instructions can be found here...
[GUIDE] Flashing a Factory Image with fastboot / return to stock
----
But all of this is contingent upon successfully UNLOCKING THE BOOTLOADER.
The bootloader needs to be unlocked, before anything can be fastboot flashed.
Whilst this can be done with toolkits (such as Wugs), I personally prefer to deal with fastboot directly (instead of through a layer of GUI polished menus and dialogue boxes).
----
From power-down state, or to force boot the device into its bootloader...
** Press and hold VOL-DOWN.
** Whilst holding VOL-DOWN, press POWER ON.
** Keep BOTH buttons pressed for a good 30 seconds.
If successful, you should see a GREEN ANDROID lying on its back...
----
USB connect it to your laptop/PC. Ensure you have the correct drivers installed on your laptop/PC as per the instructions detailed in the above link.
The command is as follows...
Code:
fastboot oem unlock
Due to security considerations, this command will wipe the Nexus 7, and you will be advised of this by the Nexus 7 itself, and you'll also need to confirm the bootloader unlock request at the Nexus 7 end via a confirmation dialogue box.
(See the attached screenshot for the sort of thing you should expect to see).
If successful, you should see an unlocked padlock symbol at the bottom of the screen, underneath the Google logo, whenever the device boots.
----
Unlocking the bootloader is critical if you wish to fastboot flash anything. Even official Google factory stock images require an unlocked bootloader to be fastboot flashed. And with the Google recommendation that the bootloader is re-locked afterwards with...
Code:
fastboot oem lock
This is optional of course, and I would generally recommend against it, because if you wish to unlock the bootloader again at some future date, it will wipe/factory reset the device...
General point of advice: Once Unlocked - Leave it Unlocked.
---
Hope this helps... and good luck.
Rgrds,
Ged.

View attachment 3240619
Man, it was looking promising. Went into boot loader, asked me if I wanted to unlock and then it failed : ( This is crazy!!! Please see attached pics. Any other ideas? I am at a loss...

rayandreas said:
View attachment 3240618
View attachment 3240619
View attachment 3240620
Man, it was looking promising. Went into boot loader, asked me if I wanted to unlock and then it failed : ( This is crazy!!! Please see attached pics. Any other ideas? I am at a loss...
Click to expand...
Click to collapse
Maybe your bootloader is corrupted? @GedBlake, can you provide him with latest 4.23 bootloader? I was searching the web and found out some bootloaders can be bad. Someone correct me if I said something wrong(just trying to help xD)

Fobos531 said:
Maybe your bootloader is corrupted? @GedBlake, can you provide him with latest 4.23 bootloader? I was searching the web and found out some bootloaders can be bad. Someone correct me if I said something wrong(just trying to help xD)
Click to expand...
Click to collapse
Man, I'll try anything. It is really racking my brain!
Thanks guys, for all the help so far...

rayandreas said:
Man, I'll try anything. It is really racking my brain!
Thanks guys, for all the help so far...
Click to expand...
Click to collapse
According to this article, some of bootloaders were corrupted or what. Update NRT masterlists in the toolkit and try flashing the latest bootloader if that is possible through the toolkit. Maybe it will let you to unlock the bootloader afterwards. If the toolkit can't do that for you, download latest factory image(4.4.4 or 5.1, what you desire) and extract the bootloader from the image. It will probably be named "bootloader-nakasi....." Try manually flashing it through CMD/ADB using "fastboot flash bootloader "name of bootloader file". I repeat, I don't have much experience with this tablet, but I'm doing what I can. Try doing what I suggested, maybe it'll work. You can't make it worse after all Good luck!
EDIT: In the link I posted, there are some neat instructions and a link to the new bootloader down the page. Make sure to check that out too.

I did update the NRT images and tried again with no luck. I also tried going into recovery and this is what I get. So, it looks like I have a crazy locked boot loader and no recovery at all. I am trying the other method now. We shall see!
Thanks for all the help so far. It means a lot!

rayandreas said:
I did update the NRT images and tried again with no luck. I also tried going into recovery and this is what I get. So, it looks like I have a crazy locked boot loader and no recovery at all. I am trying the other method now. We shall see!
Thanks for all the help so far. It means a lot!
View attachment 3242733
Click to expand...
Click to collapse
You actually have a recovery, a stock one. While at that screen, press Volume Up + Power for 1 sec( or only Volume Up, not sure) to access it. You can try doing a factory reset there if that helps anyhow.

Cannot flash to any partitions

My bootloader is off the rocker right know and I can't seem to get anything done.
Cant access recovery, multiple bootloops, etc. EVEN after flashing stock images from the Dump thread.
Now I cant even do that because nothing wants to flash to the partitions, e.g.
Code:
FAILED (remote: Error flashing partition.)
Code:
c:\tools>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.000s
I'm at a loss here, is there anyway I can fix this?
Thanks guys

jAm-0 said:
My bootloader is off the rocker right know and I can't seem to get anything done.
Cant access recovery, multiple bootloops, etc. EVEN after flashing stock images from the Dump thread.
Now I cant even do that because nothing wants to flash to the partitions, e.g.
I'm at a loss here, is there anyway I can fix this?
Thanks guys
Click to expand...
Click to collapse
I'm sure you've already tried this but, what about the other USB ports? I had this very same issue and it took me about an hour to get my phone to recognize "fastboot -w" again.
If I recall correctly, I had to power off the PC and phone, then downgraded my Minimal ADB and Fastboot and everything started working again surprisingly, commands were recognized and I could wipe and flash with no issues.

Welcome to the club. There are a few of us now. I had this happen when trying to flash TWRP after installing the 8.1 beta. AFAIK there's nothing you can do. I've tried every combination of USB port, cable and OS. Its either a hardware error or somethings ****ed with the bootloader. Essential isn't claiming any responsibility and its just offering a $200 out of warranty replacement to US customers.

[HELP] Z00TD/ZE551KL soft-bricked? No recovery mode, no OS, locked bootloader.

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.