Related
A friend of mine as the same phone as me, the Huawei Ascend P6, and when she said hers was broken I said I would take a look. I have played around with flashing Android Roms etcetera, but I am totally stuck with this problem.
The problem is as follows: when booting the phone it shows the Huawei Ascend logo (as it should) for a couple of seconds, but then instead of the Huawei animation it shows the name "android" and gets stuck there (see attachment).
After some researching I put the UPDATE.APP file from the Huawei website in the dload folder on the root of the SD-card and tried rebooting. I tried a several times, but nothing happened.
Next I successfully booted in recovery mode but even when starting recovery the screen shows errors (see attachment):
Code:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument
Installing a ZIP file, wipe cache and wipe data give even more errors.
So I thought I would try flashing through ADB/fastboot, and used the HuaweiUpdateExtractor tool to get the images. I can get manually in fastboot mode, but when I try to flash an image get the error
Code:
FAILED (remote: flash failure, ErrNo:2)
I tried using different files, USB ports, cables, linux and windows but nothing seems to help. Has anyone an idea what to do next?
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
blueIBI said:
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
Click to expand...
Click to collapse
Since I can not boot and it's not my own phone I have no clue what the version is
Luckily my PC recognizes the phone in fastboot (indeed with a weird name with a lot of ?), but I am not able to flash twrp because every time I try I get a FAILED response... Maybe the file I have is wrong. Could you point me to a thread about falshing twrp?
here is a guide for unlocking bootloader: http://forum.xda-developers.com/showthread.php?p=50724517
here is a twrp for JB roms: http://forum.xda-developers.com/showthread.php?p=47633501
here for KK roms: http://forum.xda-developers.com/showthread.php?p=51718302
maybe you need to unlock your bootloader at first
changes not working
Thanks for the links! I am able to flash an image, but for some reason my changes won't stick. When I boot in fastboot it says it is locked and I am able to unlock it, but everytime I reboot it is locked again. The same happens with twrp, I am able to flash the image but for some reason when I boot back into recovery nothing has changed.
My fastboot commands and output:
Code:
C:\Android>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 1.952s]
finished. total time: 1.952s
C:\Android>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.012s]
finished. total time: 0.012s
C:\Android>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Android>fastboot flash recovery twrp_2_6_3_3_recovery.img
sending 'recovery' (8690 KB)...
OKAY [ 0.259s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.650s
Any idea?
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
blueIBI said:
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
Click to expand...
Click to collapse
That's what I was afraid of..
I think the unlock code doesn't work correctly on this phone for some reason, but I don't think I'll be able to get an unlock code specific for my device from Huawei, without serial number and such which I can't get since the phone doesn't boot.
I hope there is some warranty left...
Results
If anyone is interested (perhaps in the future), the phone was sent for repairs and is working again. They probably replaced the motherboard, but luckily it all fell under the warranty.
Thanks to blueIBI for trying to help!!
Hey guys !
So since i messed up with the recovery mode, i'm stucked in the fastboot with no Download mode (recovery doesnt work neither).
So after searching 3 days in the internet i found the acces to fast through adb by puting a new laf.img in order to restore the download mode and flash a stock firmware !
My problem is that when i try to enter the command on the cmd, i get severals errors, take a look :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (18432 KB)...
OKAY [ 0.581s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.615s
Also command : "fastboot boot laf.img" result to "Failed(remote: dtb not found) instead of flash write failure..
Of course i have my G3 855 32GB in download mode (but it goes into fastmode), so when i try a command, lines are added in the screen etc..
Does that mean that my laf.img don't work? I assumed that so i try several, but does it have to be the exact same one as the one who was in my phone before( v20a if i record correctly ) or could it be from any 855 32GB version ?
I also thought it could be a recognition problem as when i type "adb devices" or "adb shell" nothing is found..
If someone has any clue or a link to some guide i'll be more than joyful, thanks in advance !
Try adb fastboot when writing command hope it helps
Anik49 said:
Try adb fastboot when writing command hope it helps
Click to expand...
Click to collapse
Hey thank you so much for answering !
What do you mean by that, i already download the adb/fastboot driver and launch a cmd in the directory they are at, writing "adb fastboot" has no result neither, can you be more specific please ?
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again:
Click to expand...
Click to collapse
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly http://forum.xda-developers.com/lg-g...-9008-t3072091
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
Click to expand...
Click to collapse
Like @BigsyBiggins said, this is the guide which could fix your phone. HW Part is not too hard!
Anik49 said:
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly
Click to expand...
Click to collapse
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
SisGG said:
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
Click to expand...
Click to collapse
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Ernesto0023 said:
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Click to expand...
Click to collapse
Well I think i'm still under warranty, so i dont wanna touch to much on the hardware.
So do you think, if i send it back without touching anything, saying i put it on charge one night and the next morning it was like this, the warranty could work?
If they found it's rooted or they understand you did something with your software your warrenty is void ?
SisGG said:
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
Click to expand...
Click to collapse
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
miguexneox said:
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
Click to expand...
Click to collapse
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
SisGG said:
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
Click to expand...
Click to collapse
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
datrmon said:
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
Click to expand...
Click to collapse
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Ghikya said:
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Click to expand...
Click to collapse
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
datrmon said:
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
Click to expand...
Click to collapse
It seems that your phone's bootloader is locked, you can try to execute this command: "fastboot oem unlock", and then check state with "fastboot oem device-info". But some people says that it does nothing, so you can try and check for yourself.
You can also try to boot directly an image from fastboot for eaxmple:
Code:
fastboot boot laf.img
or
Code:
fastboot boot twrp.img
So if you could successfully boot a laf image you would be able to access download mode, and if you could boot a custom recowery then you could access ADB and to try to flash other partitions, or even flash a custom rom...
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
hello, so after trying to flash stock lollipop something went wrong and now can't access download mode, i tried to flash laf.img but i can't flash anything using adb, plz help.
When in fastboot mode:
Code:
fastboot flash laf laf.img
doesn't work?
I've restored download mode on a V410 before that way just to see if it would work, and it was successful. I nuked my laf partition intentionally because we didn't use to have a kdz for the V410, and I thought it would be easier to recover the tablet with fastboot available than a useless (for the V410 without a kdz) download mode.
jason2678 said:
When in fastboot mode:
Code:
fastboot flash laf laf.img
doesn't work?
I've restored download mode on a V410 before that way just to see if it would work, and it was successful. I nuked my laf partition intentionally because we didn't use to have a kdz for the V410, and I thought it would be easier to recover the tablet with fastboot available than a useless (for the V410 without a kdz) download mode.
Click to expand...
Click to collapse
Thank you for the replie, no, every time i trie to flash something or unlock the bootloader i get this message : failed (remote: unknown command)
Hi,
I tried to flash european version of firmware to my LG G7+ by LGUP. It got stuck at 91%. After that i am not able to go in to download mode, becouse phone automaticly goes to fastboot mode.
I tried to flash laf.img extracted from firmware but fastboot is showing error:
Code:
C:\platform-tools>fastboot boot laf.img
Sending 'boot.img' (36736 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
And then I can see that phone is unplugging from computer and fastboot cant see it. (fastboot menu on phone is vanishing in that moment too, there left only charging icon)
Any solutions? If you have any contact to someone who could help, please advice me.
pozdrowiony said:
Hi,
I tried to flash european version of firmware to my LG G7+ by LGUP. It got stuck at 91%. After that i am not able to go in to download mode, becouse phone automaticly goes to fastboot mode.
I tried to flash laf.img extracted from firmware but fastboot is showing error:
And then I can see that phone is unplugging from computer and fastboot cant see it. (fastboot menu on phone is vanishing in that moment too, there left only charging icon)
Any solutions? If you have any contact to someone who could help, please advice me.
Click to expand...
Click to collapse
Try using qfil to flash the required partitions.