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.
Related
Hey, i tried to install the android 6.0 beta from this forum, but i was rooted, now its stuck in a loop where it turns off, turns on and tries to install it and fails at 0%, and again. I can enter Fastboot/rescue mode and thats it. I tried to flash recovery boot and system.img in adb and fastboot, but it shows this:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 1.265s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.265s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.858s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.874s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system.img
unknown partition 'SYSTEM.img'
error: cannot determine image filename for 'SYSTEM.im
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 471859200 bytes
Help pls. I tried everything...
System.img flash failed after 2 mins now too. Still no idea.
Looks like you've used the KingRoot method to root your phone.
Flashing via fastboot requires the fastboot to be unlocked.
The message "FAILED (remote: Command not allowed)" indicates, that the script tried to execute the command, but because the bootloader is still locked, it cannot do such thing.
There are 2 solutions:
Download the original firmware and try to update to it via the "dload" method. (sdCard>dload>UPDATE.APP)
Try to unlock the bootloader. But for unlocking, you'll need the Product ID, which as of now, only obtainable, when the phone is able to boot up.
I really recommend trying to download the firmware, and give the "dload" method a shot, because without an unlocked bootloader, nothing you can do at home.
Right, it's almost nothing. There's this site called DC-Unlocker, and with a fast runthrough, it should be able to unlock the bootloader, but I haven't tried, or tested it in any way. Still an interesting program, though.
Edit:
Just saw your post under the other similar topic.
You should try to do a Factory Reset, by hand, via fastboot, and then updating with the "dload" method again.
The commands are:
fastboot erase cache
fastboot erase userdata
Maybe this helps.
daviddosa said:
Looks like you've used the KingRoot method to root your phone.
Flashing via fastboot requires the fastboot to be unlocked.
The message "FAILED (remote: Command not allowed)" indicates, that the script tried to execute the command, but because the bootloader is still locked, it cannot do such thing.
There are 2 solutions:
Download the original firmware and try to update to it via the "dload" method. (sdCard>dload>UPDATE.APP)
Try to unlock the bootloader. But for unlocking, you'll need the Product ID, which as of now, only obtainable, when the phone is able to boot up.
I really recommend trying to download the firmware, and give the "dload" method a shot, because without an unlocked bootloader, nothing you can do at home.
Right, it's almost nothing. There's this site called DC-Unlocker, and with a fast runthrough, it should be able to unlock the bootloader, but I haven't tried, or tested it in any way. Still an interesting program, though.
Click to expand...
Click to collapse
Ive got all the informations for getting the bootloader unlock code, but when i type it in the thing by huawei to get the unlock code it tells me that its wrong... I could get it here if you could help me with it?
Hello,
I'd like to request a bootloader unlock code for my Huawei device
Information:
Product: HUAWEI ALE-L21
SN:
IMEI:Nvm
Product IDups.
Thank you!
So, this is the e-mail i sent to Huawei, they couldnt help me. Everything here is directly from the phone itself, so i dont think its wrong.
With the Product ID, you can get the code, but the details above are wrong, more precisely one of them, which is the Phone Name
Try it without the HUAWEI, it should look like this: "ALE-L21" (without the " of course).
If it somehow would not work for you, I sent you a PM with your unlock code in it.
Note: I recommend not to publish your information like this. The phone is blockable with the IMEI remotely by the service providers or the police. Please remove them for your own safety.
Tried the update again, now flashing doesnt even work.
I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
unknown_geek said:
I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
Click to expand...
Click to collapse
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
echo92 said:
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
Click to expand...
Click to collapse
Hi @echo92,
Thanks for pointing out what I was doing wrong. I now realize that the TWRP recovery was being overwritten by stock recovery and I didn't know adb commands don't work while still in bootloader mode.
I did boot into recovery mode from the bootloader (using the volume buttons from the phone) and it worked.
And the ID: bad key is also gone and now it shows ID: N/A.
Thanks again for your help!
Regards
____Mdd said:
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
Click to expand...
Click to collapse
Hi @____Mdd,
I rebooted into recovery right after flashing TWRP and it worked fine. Now, I'm able to boot into TWRP recovery.
Thanks for your response.
Regards.
Im Facing this issue while flashing TWRP
C:\adb>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (12644 KB) OKAY [ 0.422s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
vaibhavhr2010 said:
Im Facing this issue while flashing TWRP
Click to expand...
Click to collapse
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
echo92 said:
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
Click to expand...
Click to collapse
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
vaibhavhr2010 said:
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
Click to expand...
Click to collapse
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
echo92 said:
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
Click to expand...
Click to collapse
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
vaibhavhr2010 said:
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
Click to expand...
Click to collapse
That TWRP won't work, if it's for Titan. The codename for Moto G4/plus is athene, only TWRP images specifying athene in their name will work.
https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 or https://eu.dl.twrp.me/athene/ give these a try instead
Hi so I want to revert back to factory image, however I keep on getting "file not found" or "target didn't report max-download-size" error. I already installed the drivers, unlock the bootloader and when I check fastboot devices, the phone shows up.
Any help would be greatly appreciated.
Ive had similar performance within the bootloader menu. Some things to check on your pc verify that the phone is showing up in device manager as essential phone fastboot. You may need to restart the pc or change usb port to get it to properly communicate.
You should also be able to revert to the factory image through the normal recovery; instead of attempting to install twrp to flash the stock image (sounds like what you might be trying to do your post is a little unclear) you can always just run the normal essential recovery partition and then use adb sideload from there to restore the factory image.
From essential's website
https://www.essential.com/developer/beta-builds
Your device is now in Recovery mode. An Android logo with red exclamation mark should appear on screen.
Hold the Power button, then press the Volume-Up button one time. When the menu appears, select Apply update from ADB.
Run the following command: adb devices. Then check that your device shows up with “sideload” next to its name
Run the following command: adb sideload ota_file.zip where ota_file.zip is the name of the file you downloaded and verified
Once the update finishes, select Reboot system now to reboot your phone
I tried this and it seems to work great but if I select slot b it will not boot properly. Has anyone else tried this?
I don't believe that the Essential bath file flashes both slots. I had to use the BTS file to fix my phone.
Halp
Zargone said:
I tried this and it seems to work great but if I select slot b it will not boot properly. Has anyone else tried this?
I don't believe that the Essential bath file flashes both slots. I had to use the BTS file to fix my phone.
Click to expand...
Click to collapse
Did you manage to successfully flash the stock image? If yes, would you kindly provide the steps that you performed? Im trying to get back to Oreo from Android P Beta so that I can have my unit replaced
I just got one of these phones as payment for some consulting. I booted into fastboot mode and checked fastboot devices before agreeing on the deal and I see the device listed. I get home and start to unlock bootloader etc...only to continue getting this error...
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.005s
This was a simple process on my Huawei. WHats going on here does anyone know?
lolifer said:
I just got one of these phones as payment for some consulting. I booted into fastboot mode and checked fastboot devices before agreeing on the deal and I see the device listed. I get home and start to unlock bootloader etc...only to continue getting this error...
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.005s
This was a simple process on my Huawei. WHats going on here does anyone know?
Click to expand...
Click to collapse
Have you enabled oem unlock in developer options?
I cannot boot into android to check. I literally got this phone a couple hours ago. Is there anyway to enable it via fastboot?
The guy that I got it from told me it was stuck on boot logo. I simply hooked it up to laptop, installed adb/fastboot, and drivers and booted to fastboot and ran fastboot devices which gave me the serial #. So i figured I would be able to restore it no matter as long as fastboot could see the device.
lolifer said:
I cannot boot into android to check. I literally got this phone a couple hours ago. Is there anyway to enable it via fastboot?
The guy that I got it from told me it was stuck on boot logo. I simply hooked it up to laptop, installed adb/fastboot, and drivers and booted to fastboot and ran fastboot devices which gave me the serial #. So i figured I would be able to restore it no matter as long as fastboot could see the device.
Click to expand...
Click to collapse
There is no way to unlock bootloader if you can't enable oem unlock option in developer menu.
You can try to boot to recovery and do a factory reset,or try switching slots a/b and see if you can boot ur phone.
gm007 said:
There is no way to unlock bootloader if you can't enable oem unlock option in developer menu.
You can try to boot to recovery and do a factory reset,or try switching slots a/b and see if you can boot ur phone.
Click to expand...
Click to collapse
i already did those options. each time FB fails to write because of locked state. I cannot access recovery. I tried to> fastboot boot boot.img and this is what I get:
platform-tools_r28.0.1-windows\platform-tools>fastboot boot boot.img
Downloading 'boot.img' OKAY [ 0.935s]
booting FAILED (remote: 'unknown command')
Finished. Total time: 0.962s
EDIT**** Just specified a USB device using fastboot -s. Looks like the partitions were created but just couldnt wipe userdata. What is SuperBlocks backup?
C:\Users\Leebo\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot -s PM1LHMD762601033 -w
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: 672d99c8-c617-11e8-8c24-45c467b7c233
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Erasing 'userdata' FAILED (remote: 'Erase is not allowed in Lock State')
Finished. Total time: 1.068s
lolifer said:
i already did those options. each time FB fails to write because of locked state. I cannot access recovery. I tried to> fastboot boot boot.img and this is what I get:
platform-tools_r28.0.1-windows\platform-tools>fastboot boot boot.img
Downloading 'boot.img' OKAY [ 0.935s]
booting FAILED (remote: 'unknown command')
Finished. Total time: 0.962s
EDIT**** Just specified a USB device using fastboot -s. Looks like the partitions were created but just couldnt wipe userdata. What is SuperBlocks backup?
C:\Users\Leebo\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot -s PM1LHMD762601033 -w
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: 672d99c8-c617-11e8-8c24-45c467b7c233
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Erasing 'userdata' FAILED (remote: 'Erase is not allowed in Lock State')
Finished. Total time: 1.068s
Click to expand...
Click to collapse
You will need to side load the OTA.
You cannot flash.
tech_head said:
You will need to side load the OTA.
You cannot flash.
Click to expand...
Click to collapse
But I cannot get adb to work, only fastboot. I install essentials ADB, download Essential drivers. Am I missing something? In Device Manager while in fastboot it says Essential Fastboot Phone.
Im starting to think the original owner must have had twrp and installed OTA update without going back to stock recovery. If I were to assume this the case, what would be the next step to recover?
tech_head said:
You will need to side load the OTA.
You cannot flash.
Click to expand...
Click to collapse
How do I go about sideloading from fastboot?
Don't know. My phone is rooted and bl unlocked
lolifer said:
How do I go about sideloading from fastboot?
Click to expand...
Click to collapse
Pretty sure you cannot sideload with fastboot. Anything flashing related in the bootloader with fastboot requires an unlocked bootloader. If twrp was previously installed than he would unlocked the bootloader at some point. What happens when you boot to recovery from the bootloader? Or the hardware buttons?
galakanokis said:
Pretty sure you cannot sideload with fastboot. Anything flashing related in the bootloader with fastboot requires an unlocked bootloader. If twrp was previously installed than he would unlocked the bootloader at some point. What happens when you boot to recovery from the bootloader? Or the hardware buttons?
Click to expand...
Click to collapse
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
lolifer said:
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
Click to expand...
Click to collapse
Yeah, was just curious about what you were seeing in recovery. If your bootloader is locked and you have somehow lost recovery I am not to sure what else you can do. You said you switched slots and still were unable to boot to recovery?
lolifer said:
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
Click to expand...
Click to collapse
Ok...
Let's try this thing...
Grab the fastboot images from the Essential website...
Download and unzip it...
Try flashing boot to it's partition...
Theory- signed by the OEM?
Once you can get to recovery... You can use ADB
rignfool said:
Ok...
Let's try this thing...
Grab the fastboot images from the Essential website...
Download and unzip it...
Try flashing boot to it's partition...
Theory- signed by the OEM?
Once you can get to recovery... You can use ADB
Click to expand...
Click to collapse
...downloading images for PIE now.
EDIT**Here is the fastboot result..
C:\Users\Administrator\Downloads\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_b' (20769 KB)...
OKAY [ 0.830s]
writing 'boot_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.845s
lolifer said:
...downloading images for PIE now.
EDIT**Here is the fastboot result..
C:\Users\Administrator\Downloads\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_b' (20769 KB)...
OKAY [ 0.830s]
writing 'boot_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.845s
Click to expand...
Click to collapse
Damn...
I woulda thought for sure you could flash signed image...
just fired up miraclebox and did a read info under the qualcomm section and this was my result.
Starting..
Waiting for Phone...
Phone Found..
version:0.5
unlocked:no
off-mode-charge:1
charger-screen-enabled:1
battery-soc-ok:yes
battery-voltage:3721
version-baseband:2.0.c4-M1.2
version-bootloader:mata-4452425
variant:
partition-type:userdata:ext4
partition-size:userdata: 0x1987357000
partition-type:system_b:ext4
partition-size:system_b: 0x100000000
has-slot:nvdef:yes
has-slot:dsp:yes
has-slot:vendor:yes
has-slot:devcfg:yes
has-slot:cmnlib64:yes
has-slot:cmnlib:yes
has-slot:boot:yes
has-slot:keymaster:yes
has-slot:abl:yes
has-slot:mdtp:yes
has-slot:mdtpsecapp:yes
has-slot:bluetooth:yes
has-slot:modem:yes
has-slotmic:yes
has-slot:hyp:yes
has-slot:tz:yes
has-slot:rpm:yes
has-slot:xbl:yes
has-slot:system:yes
current-slot:_b
slot-retry-count:_b:0
slot-unbootable:_b:no
slot-successful:_b:no
slot-retry-count:_a:0
slot-unbootable:_a:yes
slot-successful:_a:no
slot-count:2
slot-suffixes:_a,_b,
secure:yes
serialnoM1LHMD762601033
product:Mata
max-download-size:0x20000000
kernel:uefi
all:
0.011s
>>Process Done...
hello friends I have the motorola g5 plus xt1680 by telcel. I have the bootloader blocked and I also have many files in memory that I do not want to lose.
I got a security patch which I downloaded and installed correctly, after updating my mistake I let the cell phone completely discharge, reaching the battery at 0%, after this I can not turn on the device stays in the motorola logo.
I have already tried to flash firmwares using adb but I can not mark me error, errors similar to this one:
fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling
gpt.default.xml
FAILED (remote failure)
finished. total time: 0.066s
for more than download firmware images, all of them make me the same error and I can not find the solution on the internet.
I have been several days and can not find a solution, it is very important not to lose my files that I have on my cell phone.
Would any of you help me please?
Have u tried using the Moto Smart Assist to reflash the phone? It should automatically detect the correct firmware for you.
But if you want to flash one of the firmwares you have, leave out the "fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img" commands and the flash should work fine. Apparently the update you took updated the partition tables on your device so you either have to flash without downgrading or flash using the exact firmware that the gpt.bin file is using.
If you need to get your files off first, download TWRP here, and then copy it into the directory where you have fastboot and run
"fastboot flash recovery twrp-3.2.3-1-potter.img" and then scroll down with the vol keys until you get reboot to recovery. (If it doesn't flash correctly you may have to push vol key down to reboot bootloader and try flash again) After inside TWRP, you should be able to use your password to decrypt your data and then use a USB cable to get your things off the phone or take a TWRP backup of your data / internal storage partitions and restore those after a fresh flash.
Drkmatr1984 said:
Have u tried using the Moto Smart Assist to reflash the phone? It should automatically detect the correct firmware for you.
But if you want to flash one of the firmwares you have, leave out the "fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img" commands and the flash should work fine. Apparently the update you took updated the partition tables on your device so you either have to flash without downgrading or flash using the exact firmware that the gpt.bin file is using.
If you need to get your files off first, download TWRP here, and then copy it into the directory where you have fastboot and run
"fastboot flash recovery twrp-3.2.3-1-potter.img" and then scroll down with the vol keys until you get reboot to recovery. (If it doesn't flash correctly you may have to push vol key down to reboot bootloader and try flash again) After inside TWRP, you should be able to use your password to decrypt your data and then use a USB cable to get your things off the phone or take a TWRP backup of your data / internal storage partitions and restore those after a fresh flash.
Click to expand...
Click to collapse
thanks, I had already tried to revive my phone with moto smart assist but the software tells me that my phone is not compatible.
I can install twrp if I have the bootloader blocked or I need to open the bootloader to use twrp? but when I open the bootloader my phone restarts from the factory that will erase all my files
I think I've already got the most recent security patch that is updated, apparently this is:
https://mega.nz/#!jxUEXazJ!TVU8n458ZZwd5TfP12I_uEvslYgGc5vakyUaOeSqMOs
can I install that version on my cellphone without any risk ?
then I can flash it without losing my data by omitting the command fastboot erase userdata or is it more advisable to use the ocpion of twrp to recover my data as you explain my friend?
Thank you very much for the help
Well, if the bootloader is locked, then you can't flash TWRP until you unlock it, which you can't do because you can't get into the system to enable OEM unlocking from developer options. So you're pretty limited to what you can do...
I believe fastboot flashing everything using the exact same firmware as your most recent update, but omitting the gpt.bin, bootloader, and userdata commands would work.
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
july48 said:
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
Click to expand...
Click to collapse
Why don't use ADB pull command to pull the data from device and run the all command of flashing except bootloader and gpt.
riyan65 said:
Why don't use ADB pull command to pull the data from device and run the all command of flashing except bootloader and gpt.
Click to expand...
Click to collapse
I think the problem is he can't get past bootloader so no ADB commands for him to have access to, and his bootloader is locked and since his system won't boot he can't turn on OEM unlocking to unlock it to flash TWRP or something similar to give him ADB commands.
july48 said:
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
Click to expand...
Click to collapse
Your problems are not related to the errors for "customize" and "clogo". These entries are for customazions made by Moto Maker and it's normal that they fail if you don't have any of these.
If your device doesn't boot you may have downgraded your bootloader in the past.
I have already tried to omit the bootloader and gpt commands, and I still have the same problems only in that part of the code, having the bootloader blocked limits me a lot, I do not know if I have to wait for the firmware of my phone company Telcel to flash it by adb and see if only so I retrieve the phone.
I do not know what else to try if there is any other solution
july48 said:
I have already tried to omit the bootloader and gpt commands, and I still have the same problems only in that part of the code, having the bootloader blocked limits me a lot, I do not know if I have to wait for the firmware of my phone company Telcel to flash it by adb and see if only so I retrieve the phone.
I do not know what else to try if there is any other solution
Click to expand...
Click to collapse
If you have the most recent firmware you don't need to omit the bootloader and gpt commands, and the clogo and customize commands almost always fail, you don't even really need them.
If it's still not booting I'm not sure what else to tell you to try. Someone in another one of my posts suggested trying to boot with "fastboot boot boot.img" and then possibly you could switch on OEM unlocking from the developer options, then reboot, unlock bootloader, and flash again or flash TWRP and use recovery to recover from there.
But I'm not guaranteeing that will do anything other than be stuck at boot logo.
I was asked yesterday to install LineageOS on someone's phone. It's been a few years, and I screwed some stuff up and now I need help. I'll go through what I did first and then I'll go through my current problems.
Enabled USB debugging and OEM unlock in the phone's settings.
Used ADB to reboot ot bootloader (adb reboot bootloader)
Verified the device's existence with adb.
Used Motorola's website to unlock the phone's bootloader. Process went fine.
Restarted the phone. Got the message that the bootloader was unlocked.
Went back to developer settings to re-enable USB debugging.
Rebooted to fastboot.
Typed in "fastboot flash boot twrp.img" (the file name was longer, but I'll abbreviate for the sake of brevity).
Wiped data.
Formatted data
Now, this is where the problems started. With the data formatted, I couldn't sideload anything, mounting didn't work, and the TWRP file manager showed literally nothing on the phone. No file system or anything, it looked like. This was done on a Linux computer (which also turned two of my MicroSD cards into read only. Thanks Fedora.
Anyway, I figured I should go back to fastboot to fix things. This was probably a mistake, because now I can't do anything. I can't flash TWRP, I can't boot into it, nothing. For example, when I type in
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
I get this:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (27096 KB) OKAY [ 0.802s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
I Googled around. Some people said I might need to flash partitions from gpt.bin, but that didn't work either. Every time, I get "invalid partition name xxx."
What can I do?
Thanks you in advance.