Related
Hello everyone!!
Whenever i try to install stock firmware on my xt-1022, i get following error in cmd-
C:\Users\stock>mfastboot flash partition
gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.484s
I am also facing same problem any knows the solution?
shubhm said:
Hello everyone!!
Whenever i try to install stock firmware on my xt-1022, i get following error in cmd-
C:\Users\stock>mfastboot flash partition
gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.484s
Click to expand...
Click to collapse
Are you trying to revert to 4.4.2 or 4.4.4?
Yeah
Sent from my MI PAD using Tapatalk
shubhm said:
Yeah
Sent from my MI PAD using Tapatalk
Click to expand...
Click to collapse
What yeah?
BTW you dont need to flash gpt.bin and motoboot.img.
nilanko said:
What yeah?
BTW you dont need to flash gpt.bin and motoboot.img.
Click to expand...
Click to collapse
People these days do not follow the quote "Look before you Leap"
Don't you feel the same @nilanko?
Rohitagni said:
People these days do not follow the quote "Look before you Leap"
Don't you feel the same @nilanko?
Click to expand...
Click to collapse
LOL yeah, I pheel the same
I tried flashing stock firmware without flashing these files.
But i was unable to flash it.
Since my phone was stuck at bootlogo.
So in the end i decided to flash whole firmware again along with these files.
Sent from my MI PAD using Tapatalk
I have the same problume Do you find any solution. Emmc corrupt may be
I have the same issue my Moto E 1st Gen stuck in AP fast boot mode and give same error like Failed to program partition table while flushing ROM. While i google I got to know that my EMMC is corrupt and there is no solution of this.
Moto Auto Flasher / Root Script By Jamesjerss
________________________________________________________________________________
Connect in Bootloader Mode (fastboot Mode)
FLASHING PARTITIONS...
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.088s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 5.622s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
error: cannot load 'Firmware\motoboot.img': No error
FLASHING BOOTLOADER..
target max-sparse-size: 256MB
error: cannot load 'Firmware\bootloader.img': No error
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (247 KB)...
OKAY [ 0.094s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 5.114s
FLASHING BOOT...
target max-sparse-size: 256MB
error: cannot load 'Firmware\boot.img': No error
FLASHING RECOVERY...
target max-sparse-size: 256MB
error: cannot load 'Firmware\recovery.img': No error
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS...
target max-sparse-size: 256MB
error: cannot load 'Firmware\system.img': No error
target max-sparse-size: 256MB
error: cannot load 'Firmware\system.img_sparsechunk.0': No error
target max-sparse-size: 256MB
error: cannot load 'Firmware\system.img_sparsechunk.1': No error
thanks
hey manoj am facing out the sameissue i can get to bootloader nothing will flash what you have done to your device
It worked for me
shubhm said:
Hello everyone!!
Whenever i try to install stock firmware on my xt-1022, i get following error in cmd-
C:\Users\stock>mfastboot flash partition
gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.484s
Click to expand...
Click to collapse
Start with the below commands then try from the first commands you are currently using:
Try with
mfastboot erase system
mfastboot erase gpt
Then start from
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Above commands has been worked for me.
vivektiwari said:
Start with the below commands then try from the first commands you are currently using:
Try with
mfastboot erase system
mfastboot erase gpt
Then start from
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Above commands has been worked for me.
Click to expand...
Click to collapse
Same issue - Im getting PERMISSION DENIED error to all of those commands.
oem_locked once rebooted - I cannot enter in system for there´s none bootable to unlock it in developer menu.
ADB menu for booting img files doesnt work either.
Any tips?
Daniel Nascimento said:
Same issue - Im getting PERMISSION DENIED error to all of those commands.
oem_locked once rebooted - I cannot enter in system for there´s none bootable to unlock it in developer menu.
ADB menu for booting img files doesnt work either.
Any tips?
Click to expand...
Click to collapse
Can you go to twrp??
Sent from my AO5510 using Tapatalk
Daniel Nascimento said:
Same issue - Im getting PERMISSION DENIED error to all of those commands.
oem_locked once rebooted - I cannot enter in system for there´s none bootable to unlock it in developer menu.
ADB menu for booting img files doesnt work either.
Any tips?
Click to expand...
Click to collapse
Try to install the LAST official firmware. It does where you downgrade gpt.bin
HeaDekBatHblu said:
Try to install the LAST official firmware. It does where you downgrade gpt.bin
Click to expand...
Click to collapse
You can flash gpt.bin via adb command only(not fastboot)
dd if=/sdcard/gpt.bin of=/dev/block/mmcblk0 bs=512 count=34
Sent from my AO5510 using Tapatalk
Rajendran Rasa said:
You can flash gpt.bin via adb command only(not fastboot)
dd if=/sdcard/gpt.bin of=/dev/block/mmcblk0 bs=512 count=34
Click to expand...
Click to collapse
No. mfastboot flash partition gpt.bin
HeaDekBatHblu said:
No. mfastboot flash partition gpt.bin
Click to expand...
Click to collapse
If fastboot method failed then try ADB method
Rajendran Rasa said:
If fastboot method failed then try ADB method
Click to expand...
Click to collapse
Fastboot method failed only in case, if you flash gpt.bin from previous version frimvare. Eg frimvare 5.1.1 and you flash gpt from 4.4.4 or 5.1 previous build
Hi guys. I have bricked my phone, I've been usin cm12 and once I rebooted and it was bricked.
It just boots in bootloader with the next code:
failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
I've tried to follow this guide to restore firmware to unbrick it but I can´t and I'm sure that I'm using a compatible firmware (for XT1511).
I have the following problems:
Code:
mfastboot oem fb_mode_set
returns
Code:
FAILED (remote failure)
then
Code:
mfastboot flash partition gpt.bin
returns
Code:
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
So everything else fail to flash.
There's another way to unbrick my phone, shoul I try a different firmware?
Thank you
That's strange. If you have the bootloader unlocked you should be able to flash. Try another firmware, make sure it is your phone's original one. I guess you should make a total wipe before you flash. Make a backup in TWRP, and wipe everything.
I was having the exact same issue. All of the commands were failing with "remote failure". At some point (like, an hour ago) I did "mfastboot erase modemst1" and it worked. After that all other commands started working and I was able to restore my phone. I'm not sure what exactly made it work, but I'd say try erasing/flashing various things... I've had been trying for a few hours over quite a few days.
FegFeg said:
Hi guys. I have bricked my phone, I've been usin cm12 and once I rebooted and it was bricked.
It just boots in bootloader with the next code:
failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
I've tried to follow this guide to restore firmware to unbrick it but I can´t and I'm sure that I'm using a compatible firmware (for XT1511).
I have the following problems:
Code:
mfastboot oem fb_mode_set
returns
Code:
FAILED (remote failure)
then
Code:
mfastboot flash partition gpt.bin
returns
Code:
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
So everything else fail to flash.
There's another way to unbrick my phone, shoul I try a different firmware?
Thank you
Click to expand...
Click to collapse
Hello folks,
On a fine day when I was disabling the airport mode, I realised the phone is hung as both the home screens - Aviate and Google were not responding. So I forced switched off the phone by holding down the power key for 15-20 seconds. The phone booted in fast boot mode and since then its not starting up.
Note - I never enabled USB debugging (developer mode) in this phone, so ADB will not work and I did not select "Allow OEM Unlock" - obviously I was not hoping this kind of unprovoked crash/bricking.
I am on Mac OS X with USB drivers installed for the device. I have access to a Windows Machine also, in case any of the suggested solutions work with windows tools.
Here is what I have tried so far after reading various threads in xdaDevelopers. Please note I have tried mfastboot on windows as well and have the same output -
(1.) Tried unlocking the phone as mentioned in the Motorola website and elsewhere in the forum. I get an error
Code:
$ ./fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.105s
The phone is unlockable with a cid of 0x007
Code:
$ fastboot getvar all
......
(bootloader) cid: 0x0007
......
(2.) Downloaded the MotoE stock firmware from here and followed the "How to flash Stock Firmware". All the commands are failing, below is the output.
Code:
$ fastboot devices -l
TA38500WHO fastboot usb:1D110000
$ fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.023s
$ fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.098s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.548s
$ fastboot flash bootloader bootloader.imgtarget reported max download size of 268435456 bytes
sending 'bootloader' (2410 KB)...
OKAY [ 0.155s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.391s
$ fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (679 KB)...
OKAY [ 0.137s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.245s
$ fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (679 KB)...
OKAY [ 0.175s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.282s
$ fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (32752 KB)...
OKAY [ 1.108s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.803s
$ fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (32752 KB)...
OKAY [ 1.251s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.947s
$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262143 KB)...
OKAY [ 8.315s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.847s
$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 8.331s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.427s
$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 8.335s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.453s
$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (256116 KB)...
OKAY [ 8.120s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.229s
$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (240640 KB)...
OKAY [ 7.653s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.764s
$ fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (124212 KB)...
OKAY [ 3.977s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.064s
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (54616 KB)...
OKAY [ 1.789s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.908s
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (54616 KB)...
OKAY [ 1.846s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.925s
$ fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.126s
$ fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.173s
$ fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (1518 KB)...
OKAY [ 0.143s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.247s
$ fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (1518 KB)...
OKAY [ 0.189s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.293s
$ fastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.167s
$ fastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.146s
$ fastboot erase customize
erasing 'customize'...
(bootloader) Invalid partition name customize
FAILED (remote failure)
finished. total time: 0.049s
$ fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.023s
Any help in recovering the phone will be appreciated.
If you can get in to recovery from bootloader maybe try factory reset
When I select factory reset or recovery I got thrown to the fast boot prompt back. I checked the Bootloader logs in the fastboot mode which says - "failed to validate boot image. Boot up failed"
The same problem on 1528 after flashing stock rom!!? somebody can help us??
the firmware xt1528 have 6 files system.img_sparsechunk, and in the instruction -5, thats why phone cant start.....may be 1521 ? Look in unzipped folder with firmware how much files youve got?
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Romik80 said:
the firmware xt1528 have 6 files system.img_sparsechunk, and in the instruction -5, thats why phone cant start.....may be 1521 ? Look in unzipped folder with firmware how much files youve got?
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
It has 6 with me. There are errors / failures at every stage of flashing. That's what I am not able to understand.
ajitabhpandey said:
It has 6 with me. There are errors / failures at every stage of flashing. That's what I am not able to understand.
Click to expand...
Click to collapse
does it being flashed successfully?
sounds like it isn't therefor not booting up
according to the "log" you're not unlocked, therefore it fails
Tools to unbrick the device!
ajitabhpandey said:
Any help in recovering the phone will be appreciated.
Click to expand...
Click to collapse
Do take a look at this link:http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
I have the same problem even though my bootloader is unlocked. My phone decided to reboot one fine day and subsequently have been stuck at the bootloader. All the commands are accompanied in the log by "failed to validate abc image" where abc=boot,system,recovery etc.
Since my moto e is unlocked, I can't even RMA to Motorola for warranty :/
what were you running ?
what were you flashing ?
bootloader was locked when the problem occurred ?
Hey,
In the fastboot mode navigate to factory mode and then keep pressing the power button fast about 20-30 times till it boots into the os. Now u can access developer options and unlock the boot loader. Once the boot loader is unlocked u can flash the same rom again.......
I installed unofficial cm13 on my xt1521 everything good as of now .. i dont like the boot animation really worse.... so if any solution ?? pls do.... btw how to flash that i tried via twrp but no changes ...
kumaranwade said:
I installed unofficial cm13 on my xt1521 everything good as of now .. i dont like the boot animation really worse.... so if any solution ?? pls do.... btw how to flash that i tried via twrp but no changes ...
Click to expand...
Click to collapse
Install a theme with an alternate boot animation.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Hi everyone. I am trying to wipe my pixel 6, as I want to install a custom rom.
When trying to wipe, this happens.
fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable (partition-type:cache) not found)
erasing 'userdata'...
OKAY [ 0.191s]
erasing 'cache'...
FAILED (remote: partition not found)
finished. total time: 0.196s
When trying to flash a bootloader, It gives me this error:
sending 'bootloader' (11506 KB)...
OKAY [ 0.269s]
writing 'bootloader'...
(bootloader) Flashing pack version slider-1.2-8318357
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_a
(bootloader) Validating partition pbl_a
(bootloader) failed: invalid rollback counter
(bootloader) image(pbl_a): rejected, fails validation
(bootloader) failed to validate partition (pbl_a)
FAILED (remote: failed to flash partition (bootloader))
finished. total time: 0.347s
I believe these two errors are connected, but I am not sure why this is happening. I am aware google did something regarding preventing bootloader rollback with android 13, and I recall accidentally installing it OTA once and having to rollback to 12.
You flashed Android 13 at some point (the "invalid rollback counter" error). Once Android 13 is installed you cannot install older bootloaders. Period.
The other error? Raw format means no formatting at all. In essence you have a blank drive. You may want to try restoring using Google's flash tool prior to installing your chosen ROM.
I have flashed (fastboot method) twrp.img to my locked device and now I'm stuck at boot. At first I was getting boot loop and "corrupt" message (g.co/ABH). Luckily, I could still access fastboot mode. By looking around, I managed to remedy that a bit by:
Code:
$ wget https://dlcdnets.asus.com/pub/ASUS/ZenFone/AI2202/UL-ASUS_AI2202-ASUS-33.0804.2060.100-1.1.1-2302-user.zip
$ unzip *zip
$ payload_dumper payload.bin
$ for i in boot dtbo vendor_boot vbmeta vbmeta_system
do
fastboot flash $i output/$i.img
done
$ fastboot reboot fastboot
# these will fail due to resizing partitions on a locked device
$ for i in system system_ext product odm vendor
do
fastboot flash $i output/$i.img
done
Resizing partition ... (Can't in locked state)
Now I get bootloader, fastbootd, and stock recovery. Wiping/resetting in recovery mode almost succeeds:
Code:
misc_vab_msg.version: 0x2
misc_vab_msg.magic: ...
misc_vag_msg.merge_status: 0x0
misc_vag_msg.source_slot: 0x1
-- Wiping data...
E:Open failed: /metadata/ota: No such file or directory
-- Clean boot sound files...
Formatting /data...
Formatting /metadata...
-- Data wipe complete.
At this point, restarting the system results in the device turning itself off a few seconds after the ASUS logo.
My phone is on stock firmware 33.0804.2060.100 (android 13). Could someone kindly help me and tell me what to do next?
Here's all the info I can get now:
Code:
$ fastboot oem device-info
(bootloader) Verity mode: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) WaterMask unlock: N
(bootloader) XBL:
(bootloader) ABL: 0.0.029.0-WW-user
(bootloader) SSN: ...
(bootloader) ISN: ...
(bootloader) IMEI: ...
(bootloader) IMEI2: ...
(bootloader) CID: ASUS
(bootloader) COUNTRY: EU
(bootloader) Project: DAVINCI
(bootloader) DT ID: 66
(bootloader) SB: Y
(bootloader) SBNR: Y
(bootloader) DDR Manufacturer ID: 1
(bootloader) DDR Device Type: 8
(bootloader) TotalDMCounter: 0
(bootloader) DMCounter: 0
(bootloader) SlotARetryCounter: 0
(bootloader) SlotAUnbootableCounter: 0
(bootloader) SlotBRetryCounter: 0
(bootloader) SlotBUnbootableCounter: 0
(bootloader) BOOT_COUNT: 0
(bootloader) LOCK_COUNT: 0
(bootloader) Check_APDP: 1
(bootloader) rawdump_en: false
(bootloader) force start logcat-asdf: false
(bootloader) Current Slot: a
(bootloader) Slot_a bootable: Bootable
(bootloader) AVB Verity: Enable
(bootloader) Verify vbmeta ret: 0
(bootloader) ABL_FTM: FALSE
(bootloader) UART-ON Status: false
I have a feeling that I'm not using the right image for this purpose. I don't know how to get my hands on a RAW image. I keep reading about some android beta page, but just can't find a link for Zenfone 9.
You dont need any raw fw, flash stock recovery and reboot:
fastboot flash recovery recovery.img
Download Data package from February 25th.
Size of the data package: 100 MB. Free transfer of up to 6 GB of photos, videos and documents. Send large files via email or a link to share. No registration, no ads, just simple file sharing!
filetransfer.io
Recovery from UL-ASUS_AI2202-ASUS-33.0804.2060.100
@NisseGurra thanks for your input. I checked the md5sum of your recovery image and the one I extracted from the payload.bin. They are indeed the same. I have flashed it alright:
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.396s]
Writing 'recovery' OKAY [ 0.162s]
Finished. Total time: 3.570s
Now, what should I do? reboot to bootloader -> recovery? then what?
Because still letting the device boot normally will lead to its shutdown in 20 seconds.
lordbit said:
@NisseGurra thanks for your input. I checked the md5sum of your recovery image and the one I extracted from the payload.bin. They are indeed the same. I have flashed it alright:
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.396s]
Writing 'recovery' OKAY [ 0.162s]
Finished. Total time: 3.570s
Now, what should I do? reboot to bootloader -> recovery? then what?
Because still letting the device boot normally will lead to its shutdown in 20 seconds.
Click to expand...
Click to collapse
Seems something got messed up.
You have some options: find an recovery that have adb sideload support: flash the stock fw from it,
adb sideload xxx.zip
Option 2
Repack the stock fw (use payload dumper to extract all img), create an folder with all extracted img and add adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll and install.bat (attached, rename to .bat)
Connect phone, enter fastboot and click on the bat file, it should install full rom.
Thanks! I will try it.
I tried your second method. Most of the images got flashed alright, except these ones:
Code:
Sending 'odm' (1248 KB) OKAY [ 0.055s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending sparse 'product' 1/4 (524236 KB) OKAY [ 19.285s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'system' 1/7 (524232 KB) OKAY [ 19.632s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (386600 KB) OKAY [ 14.180s]
Writing 'system_ext' FAILED (remote: '(system_ext_a) No such partition')
fastboot: error: Command failed
Sending sparse 'vendor' 1/3 (524176 KB) OKAY [ 18.675s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vendor_dlkm' (73448 KB) OKAY [ 2.577s]
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
fastboot: error: Command failed
I think those should be flashed after a
Code:
fastboot reboot fastboot
But in that case, the "flash" command will try to resize the partitions and I get an error that says "Resizing in a locked state of the device is not possible". I am paraphrasing here.
Option 3, install https://forum.xda-developers.com/t/paranoid-android-topaz-alpha-1-asus-zenfone-9.4557631/
Use the suggested image way. It install new recovery, if i rember correct it has adb support
Reboot recovery and use option2
@NisseGurra sorry if my question seems dumb. But I have not unlocked my bootloader (when I had the chance). Do these recovery.img methods with adb work for me?
lordbit said:
@NisseGurra sorry if my question seems dumb. But I have not unlocked my bootloader (when I had the chance). Do these recovery.img methods with adb work for me?
Click to expand...
Click to collapse
If you bootloader is locked so you cant flash anything not signed by Asus, no twrp etc, So strange it got messed up
Yeah it's weird that you could flash anything at all, that isn't signed
anyway, it seems like you where able to flash the asus recovery?
can you boot it?
If so try booting it and tipe "adb reboot sideload" if everything goes well it should reboot and allow you to sideload unmodified (asus signed) .zips, do this
Also consider data wipe from recovery
Darkmasterhk said:
Yeah it's weird that you could flash anything at all, that isn't signed
anyway, it seems like you where able to flash the asus recovery?
can you boot it?
If so try booting it and tipe "adb reboot sideload" if everything goes well it should reboot and allow you to sideload unmodified (asus signed) .zips, do this
Also consider data wipe from recovery
Click to expand...
Click to collapse
1. I pressed power button + vol-up, ended up in "bootloader" menu.
2. Chose "Recovery mode"
3. At this point, on my laptop, I executed "adb reboot sideload" as you suggested.
However, I am prompted with an error that this device is unauthorized.
Code:
adb devices
List of devices attached
N...P unauthorized
How can I "authorize" this? When I had access to fully-booted system, I just needed to confirm some dialogue. Here there is no question.
Aww that's bad, I don't know how to allow a device from recovery, sorry.
Usually, if it worked under Android itself, it works in recovery as well.
Just to make sure, it worked under Android, right?
I assume u use a Linux system and I somehow had trouble under Linux, with adb and authorization
Yes, "adb" did work between my Linux system and phone before it gets stuck in this mode.
I managed to fix the problem by using a RAW image from romdevelopers. Extracted the content of the zip file and executed "flashall_AFT.cmd" on a Windows machine with the right drivers installed.
For the record, these posts [1][2] are pretty close to what I did.
Thank you both for your support.
EDIT:
I converted the "flashall_AFT.cmd' to "flashall_AFT.sh", so I could be able to achieve the same on a Linux system. USE IT AT YOUR OWN RISK.