C:\Asus_Zen_Phone_2>fastboot3 oem partition /tmp/partition.tbl
...
FAILED (remote: GPT command failed) - Also found in Asus flash tool
[2016-07-14T 01:53:53Z] (0x00000000) [0123456789ABCDEF] Flash image ...
[2016-07-14T 01:54:32Z] (0x00000000) [0123456789ABCDEF] Flash image failure(FAILED (remote: GPT command failed)
I tried to flash boot, recovery, droidboot, and system.img, but no luck. Anytime I reboot, goes to fastboot mode only.
Trying to use xFSTK Downloader v1.7, I do not get USB logo. Phone boots into fastboot mode only.
HELP!
SaHiLzZ said:
C:\Asus_Zen_Phone_2>fastboot3 oem partition /tmp/partition.tbl
...
FAILED (remote: GPT command failed) - Also found in Asus flash tool
[2016-07-14T 01:53:53Z] (0x00000000) [0123456789ABCDEF] Flash image ...
[2016-07-14T 01:54:32Z] (0x00000000) [0123456789ABCDEF] Flash image failure(FAILED (remote: GPT command failed)
I tried to flash boot, recovery, droidboot, and system.img, but no luck. Anytime I reboot, goes to fastboot mode only.
Trying to use xFSTK Downloader v1.7, I do not get USB logo. Phone boots into fastboot mode only.
HELP!
Click to expand...
Click to collapse
If you need help , try to be more specific with how you got in this state ?????!
Uninstall ASUS flash tool.
Uninstall xsftk downloader.
Clean system with ccleaner free !
Install isoc driver first.
Flash in xfstk downloader..
Don't go near ASUS Flash tool till success in xfstk
Then follow , don't be shy with the thanks button !
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
Ps, keep powering off your phone in xfstk.
Pressing power at ten seconds intervals. Till you see it flash.
Keep repeating till success and you get into boot loader version 0094 1069
You on 0094 0183 at the moment coming from 6.0?
Also Happened to me
Please Help It also happened to me to.
my ZF2 is brick,,,
1. i cant xfstk : "failure : FW + OS download did not complete",, just stop in "Firmware download completed. Continuing to OS"
and become "Reconnecting to device". i tried several time but no luck...
several time it give me this
-- "Success: FW download completed! OS download skipped"
and my ZF2 continued to fastboot, but i cant flash splashscreen and droidboot or recovery, etc, only just ifwi its successed. after xfstk my bootloader is become version 0094 1069
2. in Asus Flash Tool give me error to it says "Flash image failure (FAILED (wrong image format))". trying to download several time raw file 2.15.40.13 and 2.20.40.139, but no luck...
pocax said:
Please Help It also happened to me to.
my ZF2 is brick,,,
1. i cant xfstk : "failure : FW + OS download did not complete",, just stop in "Firmware download completed. Continuing to OS"
and become "Reconnecting to device". i tried several time but no luck...
several time it give me this
-- "Success: FW download completed! OS download skipped"
and my ZF2 continued to fastboot, but i cant flash splashscreen and droidboot or recovery, etc, only just ifwi its successed. after xfstk my bootloader is become version 0094 1069
2. in Asus Flash Tool give me error to it says "Flash image failure (FAILED (wrong image format))". trying to download several time raw file 2.15.40.13 and 2.20.40.139, but no luck...
Click to expand...
Click to collapse
In 1069 boot loader , you then flash raw file in flash tool
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
Watch the vid ..
If you flashed anything in fastboot ..re flash ifwi etc till success again ..but then flash raw.
The vid is easy to understand !
timbernot said:
If you need help , try to be more specific with how you got in this state ?????!
Uninstall ASUS flash tool.
Uninstall xsftk downloader.
Clean system with ccleaner free !
Install isoc driver first.
Flash in xfstk downloader..
Don't go near ASUS Flash tool till success in xfstk
Then follow , don't be shy with the thanks button !
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
Ps, keep powering off your phone in xfstk.
Pressing power at ten seconds intervals. Till you see it flash.
Keep repeating till success and you get into boot loader version 0094 1069
You on 0094 0183 at the moment coming from 6.0?
Click to expand...
Click to collapse
Keep flashing but failing after 20 attempts in xfstk.
how it happened, its someone else's phone, i think running cm13, and then it stopped working by itself. phone had no access to recovery, and only fastboot or boot cm logo.
SaHiLzZ said:
Keep flashing but failing after 20 attempts in xfstk.
how it happened, its someone else's phone, i think running cm13, and then it stopped working by itself. phone had no access to recovery, and only fastboot or boot cm logo.
Click to expand...
Click to collapse
When you get to that fastboot loop, the only way is indeed xfstk.
I suspect you either didnt follow the video keeping 4 zeros only in the xfstk option, 0x80000807, also remember, you need to run the Flash tool twice, first time you run it, it should show result: OKAY on the phone, then you close the flash tool and say yes to forcibly close, this makes the serial numbers match in the flash tool and the phone, hen launch and flash with the RAW file again, you should press volume up I think to ensure the phone is connected again. Ensure you always select Wipe everything in the flashtool, or it will not boot properly, pay well attention in the video to what timbernot does and says, though for none native english speakers, it might be a little hard to understand everything , but if you do if do this right everything should work.
Also remember, you NEED to boot into recovery mode on Win10 in order to install the iSoc drivers and disable the force driver signature, else they will not install.
I had massive problems with Bootloader when running any tools, so had to go back and do this process several times. Once you get your system up and running, I suggest not even trying the boot unlock tool from ASUS, it has caused me nothing but grief, root your device after the rawflash is succesful and then do the unoffcial bootload unlock via adb.
SaHiLzZ said:
Keep flashing but failing after 20 attempts in xfstk.
how it happened, its someone else's phone, i think running cm13, and then it stopped working by itself. phone had no access to recovery, and only fastboot or boot cm logo.
Click to expand...
Click to collapse
its happened to me to..
always fail in xfstk...
I hope you guys or gals are all sorted now and have lovely nice new stock systems , up n running
LBN said:
When you get to that fastboot loop, the only way is indeed xfstk.
I suspect you either didnt follow the video keeping 4 zeros only in the xfstk option, 0x80000807, also remember, you need to run the Flash tool twice, first time you run it, it should show result: OKAY on the phone, then you close the flash tool and say yes to forcibly close, this makes the serial numbers match in the flash tool and the phone, hen launch and flash with the RAW file again, you should press volume up I think to ensure the phone is connected again. Ensure you always select Wipe everything in the flashtool, or it will not boot properly, pay well attention in the video to what timbernot does and says, though for none native english speakers, it might be a little hard to understand everything , but if you do if do this right everything should work.
Also remember, you NEED to boot into recovery mode on Win10 in order to install the iSoc drivers and disable the force driver signature, else they will not install.
I had massive problems with Bootloader when running any tools, so had to go back and do this process several times. Once you get your system up and running, I suggest not even trying the boot unlock tool from ASUS, it has caused me nothing but grief, root your device after the rawflash is succesful and then do the unoffcial bootload unlock via adb.
Click to expand...
Click to collapse
timbernot said:
I hope you guys or gals are all sorted now and have lovely nice new stock systems , up n running
Click to expand...
Click to collapse
I got the xftsk to flash, successfully:
{
"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"
}
Got USB flash sign, but NO 4 colored lines. Phone still boots to fastboot.
Help?
Flash again now , repeat till bootloader
timbernot said:
Flash again now , repeat till bootloader
Click to expand...
Click to collapse
flash using xfstk? until what? the four lines?
SaHiLzZ said:
flash using xfstk? until what? the four lines?
Click to expand...
Click to collapse
Yup and don't come back till you succeed
---------- Post added at 06:19 PM ---------- Previous post was at 06:10 PM ----------
SaHiLzZ said:
flash using xfstk? until what? the four lines?
Click to expand...
Click to collapse
wait a minute, what is the number of boot loader ?
0094 1069 ?if not what is it ?
You may have missed the four colours so if 1069 flash with flash tool raw.
If any other number carry on with xfstk
timbernot said:
Yup and don't come back till you succeed
---------- Post added at 06:19 PM ---------- Previous post was at 06:10 PM ----------
wait a minute, what is the number of boot loader ?
0094 1069 ?if not what is it ?
You may have missed the four colours so if 1069 flash with flash tool raw.
If any other number carry on with xfstk
Click to expand...
Click to collapse
Yes 1069.. Fastboot flash with Asus flasher fail with error in first post. GPT error.
All I can suggest is keep flashing xfstk.
When says success again.
Wait till it boots into boot loader fastboot.
Then wait a little longer before flashing raw.
timbernot said:
All I can suggest is keep flashing xfstk.
When says success again.
Wait till it boots into boot loader fastboot.
Then wait a little longer before flashing raw.
Click to expand...
Click to collapse
Done a bit of digging re gpt error.
Stands for grand partition table.
So to me sounds like deep trouble beyond my knowledge .
The reason I say flash xfstk till success and then wait is because I had the same you are experiencing.
I left the phone connected. I went to make a brew, a breather
And a smoke , then all of a sudden ..I seen commands flashing to the phone. Then after about 15 mins I was able to flash raw
I put this down to a couple of possibilities.
One being constant abuse overload through constant attempts in xfstk.
Two , also battery getting low.
And or a mixture of both.
So again I suggest.
Charge fone a couple of hrs.
Let it cool.
Try again.
When success in xfstk, leave connected to PC and see if command start to flash on fone.
Then flash raw
Can I ask you what are the figures you are using in the second box at the bottom ending in CRC in xfstk? .Are they 0x80000807 with gp overide flag ticked ?
LBN said:
When you get to that fastboot loop, the only way is indeed xfstk.
I suspect you either didnt follow the video keeping 4 zeros only in the xfstk option, 0x80000807, also remember, you need to run the Flash tool twice, first time you run it, it should show result: OKAY on the phone, then you close the flash tool and say yes to forcibly close, this makes the serial numbers match in the flash tool and the phone, hen launch and flash with the RAW file again, you should press volume up I think to ensure the phone is connected again. Ensure you always select Wipe everything in the flashtool, or it will not boot properly, pay well attention in the video to what timbernot does and says, though for none native english speakers, it might be a little hard to understand everything , but if you do if do this right everything should work.
Also remember, you NEED to boot into recovery mode on Win10 in order to install the iSoc drivers and disable the force driver signature, else they will not install.
I had massive problems with Bootloader when running any tools, so had to go back and do this process several times. Once you get your system up and running, I suggest not even trying the boot unlock tool from ASUS, it has caused me nothing but grief, root your device after the rawflash is succesful and then do the unoffcial bootload unlock via adb.
Click to expand...
Click to collapse
You don't know it but the lil info you gave there about flashtool having to be ran twice is a gem of info. Developed migraines till this one little bit... Thanks a million.
Zenfone 2 Delux Z00AD ZE551ML Bricked - No Fastboot comands,
hi guys,
i need some help.
i Bricked my Zenfone 2 Delux z00AD ZE551ML
even following the instructions and with all the drivers correctly installed i cant unbrick it.
After sending the XFSTK files (dnx_fwr.bin, e droidboot_dnx.img.POS_sign.bin) my phone has reseted, has gone through the colored screen and then the screen has gone all black.
The fastboot recognizes the device and the ficctitious serial number but doesnt accept the comands.
I´m copying the xFSTK, Asus Flash Tool and fastboot logs below, if anyone can help me i would really aprecciate.
Thank you.
##### xFSTK Downloader 1.7 #####
Settings -> Download Options:
Enable GP Flag Overrider
GP Flag Overrider valeu 0x80000807
Devixe detection Timeout 120
Success: Download of FW Completed OK!
OS: Operating system download completed. ok!
Log:
20:05:08 - XFSTK-STATUS--Firmware and OS download completed.
20:05:08 - XFSTK-LOG--virtual bool MerrifieldDownloader::GetStatus()
20:05:08 - Success: Download of FW Completed.
##### Asus Flash Tool #####
Flash imagem (FAILED (remote: GPT command failed
Log failure:
[2016-09-11T 19:27:25Z] (0x00000000) Detect: 0B05:4DAF:0123456789ABCDEF:0005:0004:0
[2016-09-11T 19:27:27Z] (0x00000000) Detect: 0B05:4DAF:0123456789ABCDEF:0005:0004:1
[2016-09-11T 19:38:03Z] (0x00000000) [0123456789ABCDEF] User remove device from list
[2016-09-11T 19:38:18Z] (0x00000000) Detect: 0B05:4DAF:0123456789ABCDEF:0005:0004:0
[2016-09-11T 19:38:24Z] (0x00000000) Detect: 0B05:4DAF:0123456789ABCDEF:0005:0004:1
[2016-09-11T 19:38:24Z] (0x00000000) [0123456789ABCDEF] Detected this device
[2016-09-11T 19:38:35Z] (0x00000000) [0123456789ABCDEF] Check the detected serial number ...
[2016-09-11T 19:38:35Z] (0x00000000) [0123456789ABCDEF] Flash image ...
[2016-09-11T 19:39:26Z] (0x00000000) [0123456789ABCDEF] Flash image failure(FAILED (remote: GPT command failed)
##### ADB and Fastboot #####
C:\fastboot devices
0123456789ABCDEF fastboot
C:\fastboot oem erase_osip_header
...
(bootloader) cmd_oem!arg= erase_osip_header S
(bootloader) [0]erase_osip_header S
OKAY [ 1.295s]
finished. total time: 1.295s
C:\fastboot oem erase_token
...
(bootloader) cmd_oem!arg= erase_token S
(bootloader) [0]erase_token S
FAILED (remote: Fail erase_token_umip)
finished. total time: 0.764s
C:\fastboot oem start_partitioning
...
(bootloader) cmd_oem!arg= start_partitioning S
(bootloader) [0]start_partitioning S
(bootloader) Start partitioning
OKAY [ 0.998s]
finished. total time: 0.998s
C:\fastboot flash /tmp/partition.tb
l partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.983s]
writing '/tmp/partition.tbl'...
OKAY [ 1.295s]
finished. total time: 2.293s
C:\fastboot oem partition /tmp/part
ition.tbl
...
(bootloader) cmd_oem!arg= partition /tmp/partition.tbl S
(bootloader) [0]partition S
(bootloader) [1]/tmp/partition.tbl S
FAILED (remote: GPT command failed
)
finished. total time: 0.764s
C:\fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 0.905s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
< waiting for any device >
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
finished. total time: 1.186s
timbernot said:
Done a bit of digging re gpt error.
Stands for grand partition table.
So to me sounds like deep trouble beyond my knowledge .
The reason I say flash xfstk till success and then wait is because I had the same you are experiencing.
I left the phone connected. I went to make a brew, a breather
And a smoke , then all of a sudden ..I seen commands flashing to the phone. Then after about 15 mins I was able to flash raw
I put this down to a couple of possibilities.
One being constant abuse overload through constant attempts in xfstk.
Two , also battery getting low.
And or a mixture of both.
So again I suggest.
Charge fone a couple of hrs.
Let it cool.
Try again.
When success in xfstk, leave connected to PC and see if command start to flash on fone.
Then flash raw
Can I ask you what are the figures you are using in the second box at the bottom ending in CRC in xfstk? .Are they 0x80000807 with gp overide flag ticked ?
Click to expand...
Click to collapse
it is a issue related to emmc. here may be 2 cases. 1. your emmc is corrupted 2. it is not formatted correctly. i am working on it. unfortunately i don't have any bricked device. especially 2gb ram one. even though will update soon if i am able to figure out the issue.. till then before pushing the partition table and after erasing osip header. try to run command " fastboot erase partition" or "fastboot oem erase partition" please reply if something happens
marcusvrbrito said:
hi guys,
i need some help.
i Bricked my Zenfone 2 Delux z00AD ZE551ML
even following the instructions and with all the drivers correctly installed i cant unbrick it.
After sending the XFSTK files (dnx_fwr.bin, e droidboot_dnx.img.POS_sign.bin) my phone has reseted, has gone through the colored screen and then the screen has gone all black.
The fastboot recognizes the device and the ficctitious serial number but doesnt accept the comands.
I´m copying the xFSTK, Asus Flash Tool and fastboot logs below, if anyone can help me i would really aprecciate.
Thank you.
Click to expand...
Click to collapse
U need to do raw flashing two times
once to sort out serial
reboot to bootloader again
second for full flash
I have my MI MIX 2 with official global V10.3.5.0.ODEMIXM. I upgraded to this version via regular OTA update about 2 weeks ago.
After factory recovery I did last day I stuck in restart loop with error.
I picked up language, region, and after that on Just a sec screen I have error Find Device closed unexpectedly and going to restart loop.
Via Mi suite 3 beta I am able to flash same firmware, but this is causing same error and loop. Older firmwares are not possible to flash because of error. (flashing firmware older the nactual firmware on phone)
Via fastboot I am not able to flash anything as phone has locked bootloader and is not assigned to my Mi account so unlock tool is not able to unlock it.
So.. what can I do to fix it ?
hi , if you have access to fastboot look if arb is on , download this => https://androidfilehost.com/?fid=24686681827312411 and copy/paste that => fastboot getvar anti ,, if you get 4, arb is on ..... if you have under , you can flash older firmware
So if you have 4 , search '' Anti-rollback Protection and Fastboot Unlocker '' to download antirbpass dummy.img
So
fastboot getvar anti
anti: 1
fastboot flash antirbpass dummy.img
target reported max download size of 536870912 bytes
sending 'antirbpass' (8 KB)...
OKAY [ 0.002s]
writing 'antirbpass'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.006s
Mi suite 3.0 still says:
Sorry, I can't support the rollback to a non-newer previous version.
Push Man Brush Pack Version: V10.3.5.0.ODEMIXM
hi you have anti 1 , you can flash older rom without brick , you have unlock bootloader
rom 10.2.2.0 =>http://bigota.d.miui.com/V10.2.2.0....XM_20190109.0000.00_8.0_global_ffb701bb41.tgz ,, you can flash ,, after that make upgrade firmware via update
ps: un flash.bat it will ask for 0 to flash ............. i did mistake ....... you can try flash beta rom , it's under pie , i flashed it to and it's stable
=> https://bigota.d.miui.com/9.5.30/ch...30_20190530.0000.00_9.0_global_6c535734e7.tgz
after flash search update normaly get 9.6.13
I really appreciate your help, but I was not succesfull.
Bootloader is locked and unlocking via MI Unlock is not succesfull because no Mi account is bound to the device.
Flashing via Mi Suite 3 always ends like this:
V9.5.8 (pie) -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V9.6.13 -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V10.2.2.0.ODEMIXM - > ROM Package verification failed Unknown Error[2013]
V10.3.1.0.ODEMIXM -> Sorry, I can't support the rollback to a non-newer previous version.
V10.3.5.0.ODEMIXM -> Succesfull, but always get boot loop with error FIND DEVICE CLOSED UNEXPECTEDLY
I also tried to reboot to EDL with help of this srticle: https://www.xiaomigeek.com/edl-mode-xiaomi.html second option - 2. How to Boot into EDL From Fastboot Mode.
But it always restarts and goes to boot loop.
So is last try open the phone and test point method? http://en.miui.com/thread-1351514-1-1.html
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
ClementNerma said:
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
Click to expand...
Click to collapse
please , i want to know , how can i give fastboot on my redmi7 device
H R Habib said:
please , i want to know , how can i give fastboot on my redmi7 device
Click to expand...
Click to collapse
This is a forum dedicated to the Poco F3 so I think you should ask it on the Redmi 7's forum
Use MiFlash to flash the fastboot Version of stock.
ClementNerma said:
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
Click to expand...
Click to collapse
Don't flash recovery. Use this command instead:
Code:
fastboot boot recovery.img
and it will boot into recovery. Then you can install recovery ramdisk.
Phoost said:
Use MiFlash to flash the fastboot Version of stock.
Click to expand...
Click to collapse
I didn't find an official MiFlash tool and I don't trust closed-source tools for this kind of things.
avidduo said:
Don't flash recovery. Use this command instead:
Code:
fastboot boot recovery.img
and it will boot into recovery. Then you can install recovery ramdisk.
Click to expand...
Click to collapse
I tried that but it didn't work.
EDIT: After re-trying several times, I was finally able to make it work by booting with ArrowOS' recovery. TWRP was not accepted, but ArrowOS' one was
So I've been able to flash the Xiaomi.EU rom, I'll stick with it for now.