Hi everyone, i'm kinda new here and noob i'll describe the problem.
I have already followed many guides about bricked phones, fastboot solving and xftsk.
I have this Zenfone 2 Deluxe that i have modded with Groovy Android, tried to root with magisk but it didn't work so i wiped everything with TWRP(every option). Only TWRP worked for 2 days telling me that there was no OS. So i tried to flash a stock firmware via ASUS Flash tool but it didn't work cause it couldn't enable ADB. ADB didn't work once, first it didn't detect phone, then it said device offline so I gave up. Found the xFTSK method. Tried it and worked ( it booted into bootloader with the rainbow icon and still does) but the serial changed to 0123456789ABCDEF. Tried Fastboot right after as guides said. Fastboot didn't and still don't work. He couldn't find files, couldn't load them and now it says " failed (write to device failed(unknown error)). So I tried ASUS flash tool again but he said flash image failure status read failed too many links, then that fastboot coulnd't be loaded and other errors.
Along the way recovery mode "disappeared" too. It doesn't work anymore. Plus sometimes the phone boots and keeps rebooting into a white usb icon.
What should I do? Feel free to re-link me guides, PM or something else, i'm open to almost everything to solve that.
Thanks in advance.
Edit: fastboot gaves some kinda errors with partitions too ex: can't erase cache.
Battery and cable are not ASUS original ones.
MixedFried said:
Hi everyone, i'm kinda new here and noob i'll describe the problem.
I have already followed many guides about bricked phones, fastboot solving and xftsk.
I have this Zenfone 2 Deluxe that i have modded with Groovy Android, tried to root with magisk but it didn't work so i wiped everything with TWRP(every option). Only TWRP worked for 2 days telling me that there was no OS. So i tried to flash a stock firmware via ASUS Flash tool but it didn't work cause it couldn't enable ADB. ADB didn't work once, first it didn't detect phone, then it said device offline so I gave up. Found the xFTSK method. Tried it and worked ( it booted into bootloader with the rainbow icon and still does) but the serial changed to 0123456789ABCDEF. Tried Fastboot right after as guides said. Fastboot didn't and still don't work. He couldn't find files, couldn't load them and now it says " failed (write to device failed(unknown error)). So I tried ASUS flash tool again but he said flash image failure status read failed too many links, then that fastboot coulnd't be loaded and other errors.
Along the way recovery mode "disappeared" too. It doesn't work anymore. Plus sometimes the phone boots and keeps rebooting into a white usb icon.
What should I do? Feel free to re-link me guides, PM or something else, i'm open to almost everything to solve that.
Thanks in advance.
Edit: fastboot gaves some kinda errors with partitions too ex: can't erase cache.
Battery and cable are not ASUS original ones.
Click to expand...
Click to collapse
do not use asus flash tool to flash raw firmware. use commands to flash firmware. second if you will use latest raw after xFSTK it will not work. Use old raw firmware provided in guide. Hoping that ASUS flash tool has not messed up your device. use old firmware in guide command's method. if fails once again use xFSTK and flash old firmware via commands. Stay away from asus flash tool.
sukhwant717 said:
do not use asus flash tool to flash raw firmware. use commands to flash firmware. second if you will use latest raw after xFSTK it will not work. Use old raw firmware provided in guide. Hoping that ASUS flash tool has not messed up your device. use old firmware in guide command's method. if fails once again use xFSTK and flash old firmware via commands. Stay away from asus flash tool.
Click to expand...
Click to collapse
Thanks for the advices. Fact is, fastboot commands do not work so I tried flashing varius raw files via Asus flash tool but without success. If u think u can help me I can post screenshots about the errors ( I don't know why they change everytime)
MixedFried said:
Thanks for the advices. Fact is, fastboot commands do not work so I tried flashing varius raw files via Asus flash tool but without success. If u think u can help me I can post screenshots about the errors ( I don't know why they change everytime)
Click to expand...
Click to collapse
yes a screenshot would be good. as i told earlier. new firmware version or bootloader have different set of commands. post raw firmware version number you are using along withifwi version and bootloader version you are on currently.
sukhwant717 said:
yes a screenshot would be good. as i told earlier. new firmware version or bootloader have different set of commands. post raw firmware version number you are using along withifwi version and bootloader version you are on currently.
Click to expand...
Click to collapse
Fine, bootloader version says " unknown " now, i'll try re-using xFSTK. About the screenshots here they are. http://puu.sh/D7tXU/b83ccf1502.png
Related
Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks
I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
EdoIsa said:
I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
Click to expand...
Click to collapse
What are FZ DnX, IFWI, FW DnX and OS images files ?
How to extract them from the site you mentioned?
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....
I have no experience with FZ DnX, IFWI, FW DnX files, but the OS image file is on the site I posted.
Follow my link. Once there, expand the list 'Firmware' and download firmware Version WW_2.15.40.10. Once its downloaded, open the zip file. Inside should be a System.img file. Extract the System.img file into your Fastboot folder. This is the OS image the guide is referring to.
Ask around for the meaning of the other files. Meanwhile, I will research more about those files later tomorrow and get back with any info I can find. Good luck!
cde2006 said:
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....
Click to expand...
Click to collapse
install driver manually. see attachment.
When you plug your phone into the computer, does the phone show up in the device management? Typing devmgmt.msc into the windows 7 start menu or the start run menu on XP is the fastest way to get to Device Manager.
Is the device already known by your computer?
What does device manager think it is?
If its unknown, please let us know what the Hardware Ids and Compatible Ids for this device show up as. In device manageer, you can open the devices properties and under the details tab choose Hardware Ids and Compatible Ids. you could screen shot these with Alt + PrtScn and use mspaint to save them off. Otherwise you have to use Ctrl + C to copy them out . You can choose all lines by selecting the first and while holding Shift, select the last. Then you can Ctrl + C to copy all of them out.
Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.
Chinaphonearena said:
Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.
Click to expand...
Click to collapse
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.
I think that avoiding flashing droidboot and recovery, and making sure file hashes match, everything should be fine.
Same issue
---------- Post added at 04:05 AM ---------- Previous post was at 04:02 AM ----------
cde2006 said:
Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks
Click to expand...
Click to collapse
I put my 64gb sd in my ZF2 that I originally partitioned for my LG Optimus Pro and I moved a bunch of apps to the SD with link2sd and the first time I rebooted, the same screen with the USB logo and a full progress bar showed up. It won't recognize any fastboot or adb commands even though the ASUS adb is showing up in device manager. Nothing else shows up. In devices and printers I get Moorefield. The phone randomly reboots and goes back to the same screen over and over and each time the asus adb disappears from device manager and then returns. I found a guide on the zenfone 5 that looks promising, using the intel flash tool, however it requires the ZenFone 2 raw firmware files and I can't find them... Hopefully someone could help me salvage my ZF2 cuz I was really beginning love the phone... Thanks ahead of time for anyone that looks into this for me!
i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.
sry, had only the files for V5. I will load down and put it here.
boot error and bricked zenfone 2
i have same problem with my phone please send moorefields or other intel based boot drivers.. tanks
please tutor how to fixed it, thanks for advice
cde2006 said:
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.
Click to expand...
Click to collapse
Lol @ "got sequence on this forum" and "more safe proven way."
You didn't read the instructions carefully enough and made a big mistake as a result. The correct sequence was given. You just didn't read it carefully. Lesson learned.
Hopefully you can unbrick it.
No offense, but this type of thing is what happens when people just copy/paste and don't understand what they're doing.
What you did was overwrite the fastboot partition each time you flashed. You flashed a 2GB system img on top of your fastboot partition. This probably seemed like it locked up and you either unplugged or turned it off. This likely caused a corrupt partition.
Reading is key when you do anything with your phone.
This is perfectly safe. This is the way it works for all devices. It has nothing to do with the files or the phone. This was 100% user error. Simple as that.
ze550ml hard brick
http://forum.xda-developers.com/zenfone2/help/zenfone2-ze550ml-hard-bricked-t3148174#post61657126
my ze550ml hard brick too. please help me
sorry for bad english.
hardbrick zenfone 2
konsolen said:
i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.
Click to expand...
Click to collapse
Hello, i have the same issue with my zenfone 2, I download the firmware files from Asus website, but the Intel flash tool can't found a flashable image file. My question is to, if you have the firmware files that send it to me?
same issues here please help,
same issues here please help,
Hi! Im sort of new at this thread and Im a definite nooob when it comes to android stuff
I've tried to flash a pre rooted system.img as well as stock img which i got from a thread in this website
I've made sure to follow the guide thoroughly and have managed to flash the droidboot, recovery and boot img perfectly fine
But everytime I try to flash system.img the cmd prompt always says:
FAILED<command write failed <Invalid argument>>
The fastboot.exe I used has the latest version and Ive tried several times but still get the same result. I also placed all the img files in the same folder with the flashtools. Ive extracted system.img from its .zip as well
Does anyone know how to fix this?
Thanks a lot in advance
NyxHouse said:
Hi! Im sort of new at this thread and Im a definite nooob when it comes to android stuff
I've tried to flash a pre rooted system.img as well as stock img which i got from a thread in this website
I've made sure to follow the guide thoroughly and have managed to flash the droidboot, recovery and boot img perfectly fine
But everytime I try to flash system.img the cmd prompt always says:
FAILED<command write failed <Invalid argument>>
The fastboot.exe I used has the latest version and Ive tried several times but still get the same result. I also placed all the img files in the same folder with the flashtools. Ive extracted system.img from its .zip as well
Does anyone know how to fix this?
Thanks a lot in advance
Click to expand...
Click to collapse
Does
fastboot devices
gives you list with devicess connected ?
I think you havent installed properly drivers so fastboot cant install files.
I understand that everything you flash in bootloader mode on the fone.
Not in debugging mode when phone is turned on.
vivix said:
Does
fastboot devices
gives you list with devicess connected ?
I think you havent installed properly drivers so fastboot cant install files.
I understand that everything you flash in bootloader mode on the fone.
Not in debugging mode when phone is turned on.
Click to expand...
Click to collapse
The phone is indeed in bootloader mode and properly connected and recognized by pc.
Entering
fastboot devices
Shows the phone as well.
Can you please elaborate more on the drivers I need to install? Is it for the usb connection or for something else?
Thanks a lot for the reply
try this flastool version.
My ZE551ML was rooted and I decided to update it being unaware that I was supposed to unroot it before updating. Once I got to the recovery menu, I attempted to sideload the newest firmware but the device was not found despite being able to be found during the bootloop. I then performed a factory reset and now it is stuck on a bootloop and cannot be detected by adb at any point.
U can use fastboot to flash ur device
But be careful with it u can hard brick ur device if done the wrong way
Sent from my Karbonn A1+ Super using XDA Free mobile app
yakub234go said:
U can use fastboot to flash ur device
But be careful with it u can hard brick ur device if done the wrong way
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
But how do I fastboot to flash? Every tutorial I found told me to use adb sideload which I never found possible.
Edit:
I solved my problem by copying the firmware I downloaded into an external sd card under the name MOFD_SDUPDATE.zip and going to recovery mode.
download full firmware according to ur device from here https://mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw give Thanks @shakalaca for this
download (Z00A)2.19.40.18 if u want to unlock ur bootloader cause latest one cause problems with unlocking bootloader
when the device is off press power wait till it vibrates once then immediately press vol up button
u will boot into fastboot mode
there u can use fastboot commands
now form ur pc go to the path where u downloaded the firmware
press & hold shift & right click
select open command window here
now in command prompt give these commands
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
all done ur device will reboot
now u have a rooted device
remember if u want to update than first unroot it reboot than update
where do u get the system.img?
im also in a similar situation where im out of usb debug cause of factory reset
loganj said:
where do u get the system.img?
im also in a similar situation where im out of usb debug cause of factory reset
Click to expand...
Click to collapse
Here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
ultramag69 said:
Here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Click to expand...
Click to collapse
thank you
well i manage to do adb sideload even though my phone was wiped completely clean from recovery and still unable to start the android.... it was a miracle . but thanks to your link i know now how to get the system.img
now if i can only understand what system.img is compare to entire firmware zip.....probably i should try to mount one and have a look
loganj said:
thank you
well i manage to do adb sideload even though my phone was wiped completely clean from recovery and still unable to start the android.... it was a miracle . but thanks to your link i know now how to get the system.img
now if i can only understand what system.img is compare to entire firmware zip.....probably i should try to mount one and have a look
Click to expand...
Click to collapse
System.img is the entire firmware except for boot, droidboot and recovery... These can be flashed separately BUT make sure you use the right commands...
If you get to the usb symbol only displaying on your screen, you've stuffed up and it is a true brick...
yakub234go said:
when the device is off press power wait till it vibrates once then immediately press vol up button
u will boot into fastboot mode
there u can use fastboot commands
now form ur pc go to the path where u downloaded the firmware
press & hold shift & right click
select open command window here
now in command prompt give these commands
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
all done ur device will reboot
now u have a rooted device
remember if u want to update than first unroot it reboot than update
Click to expand...
Click to collapse
Hey the procces struck whe i flash system img, stuck at "sending sparse 'system' (524056 KB)" Can you help me please?
After a long time waiting, probably over 1 hour i touch my phone screen then it just powered off suddenly. I really need help please
EDIT: i figured out that when sending sparse, after 10 second my phone just turned off
Maybe this tutorial works for you: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=12528
Sent from my GT-I9500
krasCGQ said:
Maybe this tutorial works for you:
Sent from my GT-I9500
Click to expand...
Click to collapse
I can't access my phone, how am i gonna turn on USB Debuggin when it's on bootloop ?
okokokokok i meet it
i have done adb side load but cant turn my phone. so, i went fastboot mode to flash it. but the bootloader is locked and cannot unlock it. when i enter the command flashing unlock,there is no response in the command prompt. can you also tell me how can i turn on usb debugging without switch on my android phone
I have the same problem than vinod.katakam!
I try to update my Asus Zenfone 2 Laser (ze601kl), to a recente version of Android, because i'm stuck on a older version of Lollipop.
My system had a SKU WW, so i downloaded the recent version WW (marshmallow) from Asus website, and treid to update, and that gives me an error. But i reboot the phone a it works fine. But still on my old android version.
Then i tried to just update to a more recent version of Lollipop, the process appears to start fine, but then it gives me an error. Now, i tried to reboot and i end up with a endless bootloop.
I tried everithing, update by adb (cant open the file), update by sdcard (E:Error in /sideload/package.zip (Status 1) E: fota_return_code 408), and fastboot boot.img, recovery.img, but on system.img says the file is to big.
I dont have de USB Debbugind activated. Is that a problem?
I dont have important data on the phone, i just want to make it work again.
Please help!!!!
pedrofg said:
I have the same problem than vinod.katakam!
I try to update my Asus Zenfone 2 Laser (ze601kl), to a recente version of Android, because i'm stuck on a older version of Lollipop.
My system had a SKU WW, so i downloaded the recent version WW (marshmallow) from Asus website, and treid to update, and that gives me an error. But i reboot the phone a it works fine. But still on my old android version.
Then i tried to just update to a more recent version of Lollipop, the process appears to start fine, but then it gives me an error. Now, i tried to reboot and i end up with a endless bootloop.
I tried everithing, update by adb (cant open the file), update by sdcard (E:Error in /sideload/package.zip (Status 1) E: fota_return_code 408), and fastboot boot.img, recovery.img, but on system.img says the file is to big.
I dont have de USB Debbugind activated. Is that a problem?
I dont have important data on the phone, i just want to make it work again.
Please help!!!!
Click to expand...
Click to collapse
if you are on 64 bit windows and fastboot flash system system.img gives you error. probably you are not using 64 bit fastboot tool below is the link to 64 bit tool
https://drive.google.com/open?id=0B72QQTXqZSRwUkFRMl81b1pWa0k
The problem still remains!
The problem still remains!
"C:\adb>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.022s]
sending sparse 'system' 1/12 (259338 KB)...
OKAY [ 11.418s]
writing 'system' 1/12...
FAILED (remote: size too large)
finished. total time: 11.471s"
Hello guys!
Well, i manage to understand my problem and solv it!
I bought my phone from Gearbest, and the problem begins there. Why? Because, regarless my phone is a CN device, it came somehow with a WW sku. You must know that a CN device have system partition smaller than the WW device.
So, when i tried to updated it with a more recent WW system there was no room for that, and the instalation stops with a error message.
After many "Trial and error", i understand what my problem is, and tried to install a CN system version by "fastboot flash" with a system.img with root that i find here: "https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw"
To fastboot i used the fastboot tool that sukhwant717 told me to, in the post #15.
Well, that worked, so i now have a phone working. Them i go to Asus website and downloaded the latest CN firmware to my divece, copy it by USB to the internal memory of my device and upgrade it.
So, now i have a phone working with a factory system but with no google apps.
I found this website with google installer: "https://www.digitbin.com/google-installer-apk/" follow the intructions and finaly i have Google play in my phone!
Now everithing works fine!
I hope that my story could help someone with the same problem!
Hello all,
I have Zenfone 2 on which I intended to use a custom ROM.
So the first thing was to unlock the bootloader.
On previous occasion, on my Nexus, I had used the - fastboot oem unlock - command and it had worked. So with that in mind, I booted into the bootloader and tried the command, but it failed - saying oem command unrecognized.
Then I searched online and apparently, to unlock the bootloader, Asus has launched an app! But to be able to install the app, I need to get a normal boot happening, which is not happening now.
In between all this, I tried the commands - fastboot flash recovery <recovery.img>, fastboot flash boot <boot.img> too. But none of these were successful, and each of them returned a 'Permission denied' message, probably coz the bootloader was locked.
Now the situation is that -
- Bootloader is locked.
- Phone is stuck in bootloader
- There is no recovery installed. In fact, from the bootloader, when I try to boot into 'Recovery Mode', it goes there for a second and returns back to the bootloader. Doesn't show the normal android image with a 'X' on top.
- There is no root access.
Now I think the first step is to get root access, and for this I want to try the method with installing CWM recovery and SuperSu.
But for this, I need to be able to push the SuperSu.zip to the phone, which I am not able to.
Can somebody please help!
r the drivers for fastboot & adb update to date?
Android version?
If the phone is stuck in bootloader, you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Raw files: https://yadi.sk/d/FijRoAVJtvRiG
AFT: https://yadi.sk/d/NQCiY--IsQjBr (I use AsusFlashToolInstaller1.0.0.14.exe).
you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Click to expand...
Click to collapse
Have to choose wipe the data or not?
hafiz019 said:
Have to choose wipe the data or not?
Click to expand...
Click to collapse
stay away from aft. if will f**k up yor device completely. AFT is too unstable. lot of times it bricks the device to unrecoverable state. tell me the bootloader version, ifwi version shown on screen while in bootloader mode.
So I've been following unbricking tutorials, and I have fastboot. Serial number is the 0123456789 ABCDEF thing, ifwi is 0094.0177, bootloader and hw version are unknown, and signing and secure boot are ?. So I've tried asus flash tool, and it tells me error 1, and if I check the logs it ends at "fastboot oem partition /tmp/partition.tbl." I've followed a tutorial to do it manually, and whenever I get to "fastboot oem partition /tmp/partition.tbl," it tells me gpt partition error. Recovery doesn't work, but I was able to boot into temp twrp and cwm. They both can't mount anything, and twrp tells me I have 0 mb of internal storage. Is it fixable? Thanks in advance.
135hussein said:
So I've been following unbricking tutorials, and I have fastboot. Serial number is the 0123456789 ABCDEF thing, ifwi is 0094.0177, bootloader and hw version are unknown, and signing and secure boot are ?. So I've tried asus flash tool, and it tells me error 1, and if I check the logs it ends at "fastboot oem partition /tmp/partition.tbl." I've followed a tutorial to do it manually, and whenever I get to "fastboot oem partition /tmp/partition.tbl," it tells me gpt partition error. Recovery doesn't work, but I was able to boot into temp twrp and cwm. They both can't mount anything, and twrp tells me I have 0 mb of internal storage. Is it fixable? Thanks in advance.
Click to expand...
Click to collapse
Can you connect in bootloader again , also load everything to AFT ,then whilst attached to pc ..then press vol+ once ?
Is the serial corrected now ?
Nope nothing. Still the same.
135hussein said:
Nope nothing. Still the same.
Click to expand...
Click to collapse
Have you used xFSTK on this device ? Did you buy this device in this state ?
If you did use xFSTK , then i would reflash again and follow my unbrick procedure in the link in my signature for correcting serial during the two part flash in AFT.
If you did buy this device in this state , then somebody could`ve incorrectly flashed wrong files in xFSTK
.
Going off your ifwi version , you have a 551 , but if someones flashed a 550 with 551 files (which i`ve witnessed on here ) then anything and everything could go wrong.
timbernot said:
Have you used xFSTK on this device ? Did you buy this device in this state ?
If you did use xFSTK , then i would reflash again and follow my unbrick procedure in the link in my signature for correcting serial during the two part flash in AFT.
If you did buy this device in this state , then somebody could`ve incorrectly flashed wrong files in xFSTK
.
Going off your ifwi version , you have a 551 , but if someones flashed a 550 with 551 files (which i`ve witnessed on here ) then anything and everything could go wrong.
Click to expand...
Click to collapse
Yes, I've used xfstk, and whenever I try it, it ends at 11%, and yells me usb_bulk_read() windriver error. I've tried the files from multiple posts, all ZE551ML, but still no luck.
135hussein said:
Yes, I've used xfstk, and whenever I try it, it ends at 11%, and yells me usb_bulk_read() windriver error. I've tried the files from multiple posts, all ZE551ML, but still no luck.
Click to expand...
Click to collapse
Thanks for that , when you get success in xFSTK you will then get temp bootloader 0094 0169 , then if incorrectly flashed raw in AFT you get 0-F serial or if correctly flashed 0-F to start with which is normal but then following the two part flash procedure , it then gets corrected -- Flashed incorrectly or correctly in AFT will leave you with 0094 0177 bootloader.
So , correctly flashing now in xFSTK seems the way to go .
So i am assuming you did get success at some point in xFSTK but are now no longer -- am i right ?
timbernot said:
Thanks for that , when you get success in xFSTK you will then get temp bootloader 0094 0169 , then if incorrectly flashed raw in AFT you get 0-F serial or if correctly flashed 0-F to start with which is normal but then following the two part flash procedure , it then gets corrected -- Flashed incorrectly or correctly in AFT will leave you with 0094 0177 bootloader.
So , correctly flashing now in xFSTK seems the way to go .
So i am assuming you did get success at some point in xFSTK but are now no longer -- am i right ?
Click to expand...
Click to collapse
Thanks for taking the time to help me. I've never gotten success in xFSTK. Always windriver error. I thought I had divers installed incorrectly, since that's what it sounds like, but after reinstalling multiple times, still nothing.
135hussein said:
Thanks for taking the time to help me. I've never gotten success in xFSTK. Always windriver error. I thought I had divers installed incorrectly, since that's what it sounds like, but after reinstalling multiple times, still nothing.
Click to expand...
Click to collapse
Okey so we need to try and get xFSTK to run successfully , i`m not sure whether it part flashing to a certain percent corrupts but i think it must have in your case.
1 if xFSTK Downloader opens up and you can fill in the files , then isoc driver is installed correctly.
2 you are putting in gp over ride value at 0x80000807 in the bottom section that ends in [bla bla CRC] ?
and ticking the box ?
3 you are running xFSTK as administrator too?
---------- Post added at 07:37 PM ---------- Previous post was at 06:56 PM ----------
A few things to try going off what you have give me so far , if above you understand and have already preset in xFSTK -- Try, uninstall AFT -- uninstall xFSTK -- clean pc with ccleaner , registry too(free)
reinstall xFSTK from my files in my unbrick thread in my signature -- the 3 files for xFSTK are there too.
Power off pc , power off phone but leave connected to pc.
Reboot pc -- when set up -- power up phone to bootloader and repeat xFSTK flash with my files.
@135hussein
Hows it going ?
Sorry for not replying sooner. I've been busy. Will try this tomorrow, and I'll get back to you. Thanks for the help.
Fastboot erase config....
After that I stucked at boot logo
Used xfstk then aft but stucked at boot used fastboot commands for flashing system all gonna smooth but stucked at boot...
Used recovery to sideload marshmallow ... succeed. But also stucked at boot ..unlock boot loader flash TWRP flashing custom rom also stucked at boot logo... PLZZ help me guyzzz
And it shows error in TWRP
Unable:to mount Config(invalid argument)