Related
Hi everyone !
Yesterday, I wanted to wipe cache for some reasons, and I stupidly restarted the phone while formatting cache.
Result :
-A bootloop at the firt restart, then a "Error !"
-Can't acces Recovery mode, "Error !". I tried power button+volum up, don't work.
-ADB don't work anymore, I can't see the phone via adb devices
The only thing I can do is execute fastboot commands in Windows. I successfully made a tethered TWRP recovery, but I seriously don't know what to do from here. I tried flahsing a ROM, but it didn't worked (still have Error !).
I tried install permanent TWRP (unofficial), but I can't acces it. Probably because my bootloader is locked.
So... what should I do ?
Fastboot format cache should do the trick.
KillerNo2 said:
Fastboot format cache should do the trick.
Click to expand...
Click to collapse
I tried it.
Still don't start correctly, don't forget that I did some **** to try to fix it :s
The ROM is probably also damaged...
EDIT : Now it don't show the Error ! anymore, it always return to fastboot mode...
Baldriksen said:
I tried it.
Still don't start correctly, don't forget that I did some **** to try to fix it :s
The ROM is probably also damaged...
EDIT : Now it don't show the Error ! anymore, it always return to fastboot mode...
Click to expand...
Click to collapse
After formating cache you should've been able to get into recovery mode, if not, download recovery image from here then:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
You can always sideload stock roms from there.
KillerNo2 said:
After formating cache you should've been able to get into recovery mode, if not, download recovery image from here then:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
You can always sideload stock roms from there.
Click to expand...
Click to collapse
I get this :
">fastboot flash F:\recovery.img
unknown partition 'F:\recovery.img'
error: cannot determine image filename for 'F:\recovery.img'"
EDIT : oh **** sorry i misswrited the command é_è
EDIT 2 : THANKS ! I have acces to normal recovery. Can you tell me what should I do now ? (seriously don't want to make everything goes brick again ^^')
Baldriksen said:
I get this :
">fastboot flash F:\recovery.img
unknown partition 'F:\recovery.img'
error: cannot determine image filename for 'F:\recovery.img'"
Click to expand...
Click to collapse
Put all image files into the adb folder.
KillerNo2 said:
Put all image files into the adb folder.
Click to expand...
Click to collapse
Sorry, I edited my message, the error was from me.
So now I am on recovery... what should I do ?
Baldriksen said:
Sorry, I edited my message, the error was from me.
So now I am on recovery... what should I do ?
Click to expand...
Click to collapse
Download stock ROM from Asus site, and then sideload the ROM in recovery mode. Follow 3.2) Flashing Zenfone 2 via ADB in this thread.
KillerNo2 said:
Download stock ROM from Asus site, and then sideload the ROM in recovery mode.
Click to expand...
Click to collapse
Sideload with "Apply update from ADB" ?
The stock ROM is a zip of about 1.1GB ? I heard that their were update only package and full firmware ?
Baldriksen said:
Sideload with "Apply update from ADB" ?
The stock ROM is a zip of about 1.1GB ? I heard that their were update only package and full firmware ?
Click to expand...
Click to collapse
That zip file is a full firmware.
Thanks !
I did it and I have now the stock firmware installed correctly !
I have the same problem... But there is no option to fastboot format cache... only normal boot, power off, recovery mode... can't enter recovery mode either...
ndruqltn said:
I have the same problem... But there is no option to fastboot format cache... only normal boot, power off, recovery mode... can't enter recovery mode either...
Click to expand...
Click to collapse
You need to follow the steps in this thread to install drivers and adb package first. Fast boot firmat cache is the command that you should type in on your PC.
Just a thought but instead of trying to install anything through adb why not instal a pre-rooted rom img through fastboot too. You can always wipe out root with the next OTA...
I have already wipe cache and now boots up properly but the problem is that touch screen doesn't seem to work...
Can't connect my Zenfone 2 to my pc even though I have installed drivers and adb...
HW_Version -
Bootloader Version - unknown
IFWI Version - 0094 - 1069
Serial Number - my #
Signing - ?
Secure_boot - ?
RESULT: FAILD (remote: flash_cmds error!)
Thats what my bootloader looks like. What happened was I tried to update from Stock .184 to the new MM build. I downloaded the file and got prompted the update in my phone. It installed or did something and when it rebooted I was stuck in a bootloop with no screen.
I ended up using xFSTK Downloader everything went fine, my phone turned on with 4 colored bars and brought me in to the bootloader. I proceed to use Asus Flash Tool to flash the raw file of .194 and that's where my problem started.
It was taking soo long so I took my dog out for a good 15-20 min walk came back and the flash tool was still doing its thing and the green bar was still moving and on my phone it said RESULT OKAY.
I ended up closing the Flash Tool because it was taking soo long. I rebooted my phone then it goes in a bootloop with the 4 colored bars on the screen. Then I just keep repeating these steps and can't get anywhere.
When I am able to get in the bootloader after using xFSTK Downloader I cant use some flashboot commands. I cant flash twrp because I get FAILD (remote: flash_cmds error!) .
I was going by this guide here. http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
EDIT: I just noticed that my phone doesnt come up as MOOREFIELD in device manager. when it turns on and goes in to the bootloader it shows for a second and goes away.
I'm very thankful for anyone that responds. Thx for reading.
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
kenbo111 said:
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I wish they said that in the steps for updating on their site
Chrodechild said:
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Click to expand...
Click to collapse
im gonna get some breakfest in my belly and have another go at it.. couldnt use have my phone at all yesterday and I tried fixing it for atleast 8-10 hour.. it sucks lol.
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
Ill watch you video and see if it helps. the instructions on the unbrick I was using was kinda hard to understand for the most part.
timbernot said:
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
Click to expand...
Click to collapse
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
So now it seems I can use xFSTK and now im in the bootloader with the 4 color bars. But when I goto flash using the Flash tool my phone just sits on FASTBOOT CMD WAITING and the flash tool fails with FLASH IMAGE Failure[FAILED[wrong image format]]
I need some serious help :[
quarterbreed said:
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
Click to expand...
Click to collapse
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
sukhwant717 said:
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
quarterbreed said:
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
Click to expand...
Click to collapse
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
sukhwant717 said:
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
Click to expand...
Click to collapse
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
sukhwant717 said:
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
Click to expand...
Click to collapse
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Is it ok to put the MM build on my internal storage and apply the system update from there?
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
quarterbreed said:
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Click to expand...
Click to collapse
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
I didnt do a factory restore after installing .194 I'll do that now.
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
Im sure what you mean sorry. I have .194 on my phone with the help of your steps in fastboot. It booted and im in my phone and its updating all my apps and stuff..
Do you mean factory restore in bootloader? If so I tried adb reboot recovery the phone restarts and goes to a screen with https://i.ytimg.com/vi/wuixmZ11Kyc/maxresdefault.jpg Im guessing if i cant get in to recovery I cant do a factory restore?
in fastboot my bootloader doesnt have a version number it just says unknown
EDIT when the picture above showed up I held the power button and vol + to get into recovery and its performing a factory reset atm.
Anyone else bricked ?
Unbrick and into system with correct serial and imei numbers in 20 mins ..see my signature for zubes ..
PS, save yourself days of pain , after xfstk , flash an earlier raw ..
PMSL
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
i need help urgently with my A2 Lite. from TWRP it says cannot mount "./system" :crying:. During boot it says "no OS found" . Help to get it back up and running is greatly appreciated.
agbadino said:
i need help urgently with my A2 Lite. from TWRP it says cannot mount "./system" :crying:. During boot it says "no OS found" . Help to get it back up and running is greatly appreciated.
Click to expand...
Click to collapse
Hi, which system was the last system you used?
Are you aware of ADB and fastboot and which OS do your pc use?
Voodoojonny said:
Hi, which system was the last system you used?
Are you aware of ADB and fastboot and which OS do your pc use?
Click to expand...
Click to collapse
am aware of ADB and Fastboot generally speaking.
my computer is windows, dats wat am more familiar with. any suggestions or solutions? thanks
agbadino said:
am aware of ADB and Fastboot generally speaking.
my computer is windows, dats wat am more familiar with. any suggestions or solutions? thanks
Click to expand...
Click to collapse
So the easy way should be repairing your file-system of your system partition and reflashing your system partition.
1. go to twrp and select wipe -> advanced wipe -> select "system" and press the button "change or repair filesystem" -> "repair filesystem"
2. flash your system partition: download the fastboot rom you used before your system got broken from here
3. Extract rom and copy system.img to your fastboot folder
4. If you use windows 10: shift+right click somewhere in the white area of your fastboot folder "open power shell window here" - on windws 7 it will be open command prompt here...
5. flash system (windows 10 - for windows 7 copy code without ./)
Code:
./fastboot flash system system.img
Now your system shoud run again.
Alternatively you can download mi fash tool and flash your fastboot rom with flashtool - in the flashtool you can select the folder of your extracted fastboot rom and if your phone is in fastboot mode you can press "flash"
Important on the lower right corner you can select "clean all" ths will erase data, "save userdata" this will keep your data and "clean all and lock" this will erase data and relock your bootloader - last choice I wouldn´t recommend...
Voodoojonny said:
So the easy way should be repairing your file-system of your system partition and reflashing your system partition.
1. go to twrp and select wipe -> advanced wipe -> select "system" and press the button "change or repair filesystem" -> "repair filesystem"
2. flash your system partition: download the fastboot rom you used before your system got broken from here
3. Extract rom and copy system.img to your fastboot folder
4. If you use windows 10: shift+right click somewhere in the white area of your fastboot folder "open power shell window here" - on windws 7 it will be open command prompt here...
5. flash system (windows 10 - for windows 7 copy code without ./)
Code:
./fastboot flash system system.img
Now your system shoud run again.
Alternatively you can download mi fash tool and flash your fastboot rom with flashtool - in the flashtool you can select the folder of your extracted fastboot rom and if your phone is in fastboot mode you can press "flash"
Important on the lower right corner you can select "clean all" ths will erase data, "save userdata" this will keep your data and "clean all and lock" this will erase data and relock your bootloader - last choice I wouldn´t recommend...
Click to expand...
Click to collapse
First of all, thanks for taking the time.
so i had 9.6.4 stock oreo on the phone. then i updated. i have the folder for it. but even when i tried to flash "system.img" but there is some kind of error.
i have access to a windows 7 pc at work, so i could probably try it all again tomorrow, using ur steps here.
whatever happens i will update here. thanks again
Voodoojonny said:
So the easy way should be repairing your file-system of your system partition and reflashing your system partition.
1. go to twrp and select wipe -> advanced wipe -> select "system" and press the button "change or repair filesystem" -> "repair filesystem"...
Click to expand...
Click to collapse
one more thing, miflash gives error "cant find script" when i select "clean all" or "clean all and lock". so i think my only option will be to try adb or maybe you have the proper .bat file you could attach for me.
.bat files i have are in the "daisy_V9.6.11.0.ODLMIFF_8.1" folder i extracted
agbadino said:
one more thing, miflash gives error "cant find script" when i select "clean all" or "clean all and lock". so i think my only option will be to try adb or maybe you have the proper .bat file you could attach for me.
.bat files i have are in the "daisy_V9.6.11.0.ODLMIFF_8.1" folder i extracted
Click to expand...
Click to collapse
Download rom and right click "extract here" a folder will be created and this folder you need to select in miflash. In the folder you should see the .bat files and a folder "images"
---------- Post added at 04:38 PM ---------- Previous post was at 04:36 PM ----------
agbadino said:
First of all, thanks for taking the time.
so i had 9.6.4 stock oreo on the phone. then i updated. i have the folder for it. but even when i tried to flash "system.img" but there is some kind of error.
i have access to a windows 7 pc at work, so i could probably try it all again tomorrow, using ur steps here.
whatever happens i will update here. thanks again
Click to expand...
Click to collapse
You have to copy system.img to fastboot folder and right click somewhere to select "open command prompt here"
Then type
Code:
fastboot flash system system.img
Your phone has to be in fastboot mode...
i did exactly as you directed. but still nothing. i have attached the result of the cmd executions so far.
Voodoojonny said:
Download rom and right click "extract here" a folder will be created and this folder you need to select in miflash. In the folder you should see the .bat files and a folder "images"
---------- Post added at 04:38 PM ---------- Previous post was at 04:36 PM ----------
You have to copy system.img to fastboot folder and right click somewhere to select "open command prompt here"
Then type
Code:
fastboot flash system system.img
Your phone has to be in fastboot mode...
Click to expand...
Click to collapse
i did exactly as you directed. but still nothing. i have attached the result of the cmd executions so far.
TWRP shows my current slot as B. i just took note of that. probably why all flash cmds arent working. Any ideas?
agbadino said:
i did exactly as you directed. but still nothing. i have attached the result of the cmd executions so far.
TWRP shows my current slot as B. i just took note of that. probably why all flash cmds arent working. Any ideas?
Click to expand...
Click to collapse
Ah, I see, yes, you did everything right. It's still a problem with your system partition...
Have you tried formatting your system partition via twrp? And have you done the repair of the partition, I suggested above?
If you can enter fastboot mode, that's good enough
In the fastboot mode, send this command 'fastboot oem edl' to enter the emergency download mode.
Then flash any of the firmware ROM in that mode.
The phone will automatically reboot when done.
Voodoojonny said:
Ah, I see, yes, you did everything right. It's still a problem with your system partition...
Have you tried formatting your system partition via twrp? And have you done the repair of the partition, I suggested above?
Click to expand...
Click to collapse
Yes i did. thats on Slot A after i noticed which slot was active. so basically:
1. i switched to Slot A.
2. changed the file format type. den repaired and formatted it back to ext4.
3. as an after thought after trying adb and faile, i tried Miflash again.
4. dont kno how long it takes to flash. it started, wch was a surprise but its been on for...let me check...2530secs
how long is it expected to tAKE. its 5.46pm now and i have to shutdown soon
ashimiyy said:
If you can enter fastboot mode, that's good enough
In the fastboot mode, send this command 'fastboot oem edl' to enter the emergency download mode.
Then flash any of the firmware ROM in that mode.
The phone will automatically reboot when done.
Click to expand...
Click to collapse
i have tried entering edl mode before. but as i dont kno wat commands to use while in dat mode, i just reboot to recovery or fastboot.
so please help with the possible sequence of commands to use to flash rom once in "EDL mode"
agbadino said:
i have tried entering edl mode before. but as i dont kno wat commands to use while in dat mode, i just reboot to recovery or fastboot.
so please help with the possible sequence of commands to use to flash rom once in "EDL mode"
Click to expand...
Click to collapse
Okay, while in that mode
Connect your phone to laptop
Open miflash tool, your phone should appear as COM32 or so
Then flash in this mode selecting clean all.
You should be fine.
agbadino said:
i have tried entering edl mode before. but as i dont kno wat commands to use while in dat mode, i just reboot to recovery or fastboot.
so please help with the possible sequence of commands to use to flash rom once in "EDL mode"
Click to expand...
Click to collapse
The command is
Code:
fastboot oem edl
Voodoojonny said:
The command is
Code:
fastboot oem edl
Click to expand...
Click to collapse
Goodmorning. so i entered edl mode and den tried Miflash. it starts the process and stops with an error of cant find "keymaster.img"
on second try it says "looking for hello packet" and ends with "cant find hello packet"
agbadino said:
Goodmorning. so i entered edl mode and den tried Miflash. it starts the process and stops with an error of cant find "keymaster.img"
on second try it says "looking for hello packet" and ends with "cant find hello packet"
Click to expand...
Click to collapse
1. Exit edl by pressing pwr for more than 10 sec.
2. Make sure keymaster.img is in the folder "images" of your extracted fastboot image.
3. Go back to fastboot and enter
Code:
fastboot oem edl
The extracted folder with the images should look like image 1
4. Open MiFlash and select the folder daisy global image v9.x.x.x....
5. Now flash...
Voodoojonny said:
1. Exit edl by pressing pwr for more than 10 sec.
2. Make sure keymaster.img is in the folder "images" of your extracted fastboot image.
3. Go back to fastboot and enter
Code:
fastboot oem edl
The extracted folder with the images should look like image 1
4. Open MiFlash and select the folder daisy global image v9.x.x.x....
5. Now flash...
Click to expand...
Click to collapse
i see that urs is slightly different than mine. so i will ask u some favors.
1. please send me a link to download urz. bcos urz seems to be more complete n possibly more reliable.
2. help me confirm in twrp what is the default file system for slot A and slot B. so i can be sure what file system i set mine to.
thanks.
agbadino said:
i see that urs is slightly different than mine. so i will ask u some favors.
1. please send me a link to download urz. bcos urz seems to be more complete n possibly more reliable.
2. help me confirm in twrp what is the default file system for slot A and slot B. so i can be sure what file system i set mine to.
thanks.
Click to expand...
Click to collapse
If you like pie, that´s the last one: http://bigota.d.miui.com/V10.0.3.0.P...e8d8d4a6d0.tgz
And the last oreo build: http://bigota.d.miui.com/V9.6.11.0.O...8028e3bf1c.tgz
Install winrar - if you don´t have and right click on the downloaded file: "extract here"
Now you should have the same file struckture as shown on image 1... Good luck!
Voodoojonny said:
If you like pie, that´s the last one: http://bigota.d.miui.com/V10.0.3.0.P...e8d8d4a6d0.tgz
And the last oreo build: http://bigota.d.miui.com/V9.6.11.0.O...8028e3bf1c.tgz
Install winrar - if you don´t have and right click on the downloaded file: "extract here"
Now you should have the same file struckture as shown on image 1... Good luck!
Click to expand...
Click to collapse
so far so good. but can you help me check ur TWRP on ur A2 lite and confirm wat the standard "default" file system is. d options there are "ext2, ext3, ext4, fat, exfat" the current file system is displayed at d top.
so help me check wats displayed at d top of urz. thanks
Hi,
My phone is bricked, cause i used twrp temporaly, to install a new rom, but after an unexpected wipe my phone lost OS files so i'm just able to use adb & fastboot with the fastboot mode, so lock & unlock oem principaly. Please help me it's very very important cause i need to use this phone ...
Thanks.
Is your bootloader (still) unlocked and do you have access to fastboot?
Veran125 said:
Is your bootloader (still) unlocked and do you have access to fastboot?
Click to expand...
Click to collapse
Yes, bootloader's still unlocked and i have acces to fastboot.
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse
Thanks for your magic answer, but i can't find your toolkit, BUT i found this https://forum.xda-developers.com/mi...ol-tool-one-driversunlocktwrpfactory-t3866191. Is it good also ?
You can just get newest fastboot rom, and then flash with Miflash
Veran125 said:
You can just get newest fastboot rom, and then flash with Miflash
Click to expand...
Click to collapse
If it was too simply ... I think i did that already, But fastboot room, what do you mean with that ?
I just want, now, to be sure, can i save my phone ? It's not dead ?
Cause it's a very good phone and i don't want to loose it, really.
Nope, it's not dead, even with locked bootloader it wouldn't be. But now that you've got an unlocked bootloader, it's very easy to restore
I'm more happy so, 5 hours ( no fake really ) i search a solution .... SO
I found a global rom without .bat files in this folder so i got an error with Mi Flash Tool .. Tell me more about your idea
What's the error if I may ask?
Veran125 said:
What's the error if I may ask?
Click to expand...
Click to collapse
Can not found ( don't remember the file name).bat
FamosoFT said:
Hi,
My phone is bricked, cause i used twrp temporaly, to install a new rom, but after an unexpected wipe my phone lost OS files so i'm just able to use adb & fastboot with the fastboot mode, so lock & unlock oem principaly. Please help me it's very very important cause i need to use this phone ...
Thanks.
Click to expand...
Click to collapse
-Tente isso:
Download this official rom: https://en.miui.com/download-354.html
Download this Mi Flash Tool: http://api.en.miui.com/url/MiFlashTool
*I'm assuming you already have the ADB drivers installed on your PC
*Remember to check the CLEAN ALL option
-If the above method does not work, do the following:
* It will only work if you do not have TWRP installed, if it is with twrp installed, I recommend reinstalling the original recovery *
1-Turn off the device and press (POWER BUTTON + VOLUME UP). At that point, the android doll will appear and spelled 'NO COMMAND'
2-Press only (POWER BUTTON) and click quickly (VOLUME UP BUTTON). In this screen you will see the recovery options, use the volume buttons to go to the WIPE DATA/FACTORY RESET option, confirm with YES and restart the device.
3- Wait patiently for 3/5 minutes.
-If none of this works and you can still access twrp, I recommend you try installing a GSI rom using this method: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-functional-twrp-magisk-pie-gsi-t3900119
I recommend this GSI rom (I'm using this now): https://get.resurrectionremix.com/?dir=gsi (choose 'arm64-ab')
This will give you a working system and make it easier to return to stock.
Hope one of these methods helped!
Hi all,
The problem was my PC i had not the .bat files so it couldn't work ...
Thanks @Bruno_Designer for your message, but i hate RROS but you're solution was good
FamosoFT said:
Hi,
My phone is bricked, cause i used twrp temporaly, to install a new rom, but after an unexpected wipe my phone lost OS files so i'm just able to use adb & fastboot with the fastboot mode, so lock & unlock oem principaly. Please help me it's very very important cause i need to use this phone ...
Thanks.
Click to expand...
Click to collapse
If u alredy used twrp den u have adb.
U need mi flash tool.
Download any one of the full fastboot roms for Mi A2 Lie below:
9.6.4.0: https://xiaomifirmware.com/download/10399/
9.6.10.0: https://xiaomifirmware.com/download/10867/
10.0.3: https://xiaomifirmware.com/download/11586/
So to revive ur fone, u do dis. Dis was how i did mine.
1. After downloading a rom of choice, u extract on ur pc using winrar, 7zip or izarc. U basically open the archive using any of these software n copy out the folder contained. The name usually starts with "daisy global ...."
2. U open the extracted rom folder. U will see a bunch of files including "flash_all.bat" etc and a folder called "images".
3. Click on the address bar of d rom folder and copy the address. Den open "mi flash tool" and paste d copied address in the mi flash tool address bar n click on refresh.
4. Boot ur phone to fastboot mode, using "power" & "volume down" buttons together.
connect d phone to ur pc via usb cable.
5. Open ur adb folder and open the adb command window.
Type in the following, one after the other n click enter:
" fastboot devices " dis to confirm the adb connection
" fastboot oem edl " dis to enter edl mode. Ur fone led starts blinking at 1sec intervals.
6. Back to mi flash tool, u click on "refresh". After a second ur fone should be seen as a COM port "COM 10"
7. At d bottom right, u shd find 3 options. Selct "clean all". This shd leave ur bootloader unlocked after the process.
8. U click on "flash" button at the top right. All things going well, within 10 mins the process shd be done and u will see "green" indicator with "success".
9. Hold ur fone n press d power botton for 10 secs. Then ur fone shd power up. Give ur fone exactly about 5 mins to come up "look at the clock & dnt assume"
Dis is an edit of others tutorials. But this is exactly how it worked for me. As long as u use any of the 3 roms i linked u.
Unless i use edl mode, it jus doesnt work for me.
Good luck. Leta know how it goes. And pls click thanks if i helped u.
Problem solved
Thread closed at OP request
i tried to install twrp in asus 5z through commands then i flashed the wrong active slot or may be both.
now my mobile is stuck at fastboot , i tried many tools and commands, it is getting out i means turns off and turns on the screen then the next second itself it shows fastboot
nothing is working i tried power botton and vol+ and vol- plus power and all the combinations mobile turning off and turning on into fastboot dirctly
what should i do ?????
dharmateja439 said:
i tried to install twrp in asus 5z through commands then i flashed the wrong active slot or may be both.
now my mobile is stuck at fastboot , i tried many tools and commands, it is getting out i means turns off and turns on the screen then the next second itself it shows fastboot
nothing is working i tried power botton and vol+ and vol- plus power and all the combinations mobile turning off and turning on into fastboot dirctly
what should i do ?????
Click to expand...
Click to collapse
1. Flash original boot.img, or
2. flash full original ROM, or
3. factory reset.
dharmateja439 said:
i tried to install twrp in asus 5z through commands then i flashed the wrong active slot or may be both.
now my mobile is stuck at fastboot , i tried many tools and commands, it is getting out i means turns off and turns on the screen then the next second itself it shows fastboot
nothing is working i tried power botton and vol+ and vol- plus power and all the combinations mobile turning off and turning on into fastboot dirctly
what should i do ?????
Click to expand...
Click to collapse
1. Flash the boot.img
2. Or flash FB ROM from here:
https://dlcdnets.asus.com/pub/ASUS/...KL-90.11.162.58-MR5-user_20190424-release.zip
i tried to flash this by command fastboot flash boot filename.zip
but it saysinvalid sparse file format at header magic
and some more errors says mmultiple blocks
and failed remote flashing partition
dharmateja439 said:
i tried to flash this by command fastboot flash boot filename.zip
but it saysinvalid sparse file format at header magic
and some more errors says mmultiple blocks
and failed remote flashing partition
Click to expand...
Click to collapse
You cannot flash .zip file. Command shoulf be:
fastboot flash boot boot.img (in case the boot.img file is located in the same folder as fastboot.exe).
Do not forget to flash it to the right slot A/B, where your system is currently located.
dharmateja439 said:
i tried to flash this by command fastboot flash boot filename.zip
but it saysinvalid sparse file format at header magic
and some more errors says mmultiple blocks
and failed remote flashing partition
Click to expand...
Click to collapse
You don't have to flash it like that.
1. Extract the zip.
2. Open the extracted folder.
3. Put your phone in bootloader (fastboot mode).
4. Double click on 'flash_ALL.bat' file.
Flashing will start.
---------- Post added at 08:51 PM ---------- Previous post was at 08:51 PM ----------
pvscz said:
You cannot flash .zip file. Command shoulf be:
fastboot flash boot boot.img (in case the boot.img file is located in the same folder as fastboot.exe).
Do not forget to flash it to the right slot A/B, where your system is currently located.
Click to expand...
Click to collapse
No. It's an FB ROM, you don't have to select any partition. It will do everything on its own.
Ok, I thought you are flashing only boot... Anyway, hamzain just replied you correctly.
hamzain said:
You don't have to flash it like that.
1. Extract the zip.
2. Open the extracted folder.
3. Put your phone in bootloader (fastboot mode).
4. Double click on 'flash_ALL.bat' file.
Flashing will start.
thank you so much hamzain
you are awsme
i have been searcing for solution since 2 days ur trick worked
my mobie is alive
thanks again
Click to expand...
Click to collapse
dharmateja439 said:
hamzain said:
You don't have to flash it like that.
1. Extract the zip.
2. Open the extracted folder.
3. Put your phone in bootloader (fastboot mode).
4. Double click on 'flash_ALL.bat' file.
Flashing will start.
thank you so much hamzain
you are awsme
i have been searcing for solution since 2 days ur trick worked
my mobie is alive
thanks again
Click to expand...
Click to collapse
Nice. Don't just say thanks, click thanks
Click to expand...
Click to collapse
wth is wrong with me/asus/xda
why in the world am running CSC ROM, should i stop looking for answer and better move on to my old life?
I'm Stuck in fast boot loop while installing TWRP . your kind help will highly appreciate.
977Hemant said:
I'm Stuck in fast boot loop while installing TWRP . your kind help will highly appreciate.
Click to expand...
Click to collapse
Furthermore, my device is not connecting to PC as well.. Please don't let me sink .
#HELP#HELP
I fix your phone in 1 day