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...
Related
How to remove TWRP v2.6.3.3 from my Huawei P6 U06
1) When I use fastboot to flash new_recovery, after reboot to recovery, the old_recovery still here again???
Configuration Android 4.4.2
Recovery Rooted
TWRP v2.6.3.3
MIUI ROM version which stop à MIUI logo
Error when try to wipe /cache is "E:Unable to moun /cache"
LikeM8 said:
How to remove TWRP v2.6.3.3 from my Huawei P6 U06
1) When I use fastboot to flash new_recovery, after reboot to recovery, the old_recovery still here again???
Configuration Android 4.4.2
Recovery Rooted
TWRP v2.6.3.3
MIUI ROM version which stop à MIUI logo
Error when try to wipe /cache is "E:Unable to moun /cache"
Click to expand...
Click to collapse
Any way to remove TWRP 2.6.3.3 version??? I try to use fix posted by surdu_petru and all failed, TWRP 2.6.3.3 version is still here??? Does some one succed to remove it and back to stock recovery?
yes many times..
connect your phone to the pc..
wait 'til your pc recognizes your phone..
enable debug mode under settings-developer options..
then load the adb cmd console..
then type "adb devices" (without "")..
if your phone is found you can do the next step..
type "adb reboot bootloader"..
then wait a few seconds..
before this you should have put the respective recovery.img from your firmware inside the adb folder (from where you started the adb cmd)..
when your phone seems to stuck on the huawei logo you can check if your phone is still recognized by the pc - type "fastboot devices" - it should show some weird things - thats ok..
then you can flash the stock recovery by typing "fastboot flash recovery recovery.img" (the .img must be exactly written how you have it inside the mentioned folder, e.g. b512_recovery.img)..
then you should see some lines describing what the adb has done (sending, writing,flashing or so)..
and that's it..
you should have a stock recovery..
you have just to reboot your phone now by typing "fastboot reboot"..
blueIBI said:
yes many times..
connect your phone to the pc..
wait 'til your pc recognizes your phone..
enable debug mode under settings-developer options..
then load the adb cmd console..
then type "adb devices" (without "")..
if your phone is found you can do the next step..
type "adb reboot bootloader"..
then wait a few seconds..
before this you should have put the respective recovery.img from your firmware inside the adb folder (from where you started the adb cmd)..
when your phone seems to stuck on the huawei logo you can check if your phone is still recognized by the pc - type "fastboot devices" - it should show some weird things - thats ok..
then you can flash the stock recovery by typing "fastboot flash recovery recovery.img" (the .img must be exactly written how you have it inside the mentioned folder, e.g. b512_recovery.img)..
then you should see some lines describing what the adb has done (sending, writing,flashing or so)..
and that's it..
you should have a stock recovery..
you have just to reboot your phone now by typing "fastboot reboot"..
Click to expand...
Click to collapse
Thnaks for your reply but I do this before and failed!
adb devices comand retourn ID phone but fastboot devices something very different ???
"fastboot oem getvar product" return U9510 ??? whats wrong?
hm..the getvar cmd is unknown to me..very strange..
LikeM8 said:
How to remove TWRP v2.6.3.3 from my Huawei P6 U06
1) When I use fastboot to flash new_recovery, after reboot to recovery, the old_recovery still here again???
Configuration Android 4.4.2
Recovery Rooted
TWRP v2.6.3.3
MIUI ROM version which stop à MIUI logo
Error when try to wipe /cache is "E:Unable to moun /cache"
Click to expand...
Click to collapse
Its look like you catch a wrong turn..
I recommend reflash your stock rom..
If only bootloader doesn't work..
AArga said:
Its look like you catch a wrong turn..
I recommend reflash your stock rom..
If only bootloader doesn't work..
Click to expand...
Click to collapse
What do you mean by wrong turn???
I can flash stock rom because:
1) I have TWRP 2.6.3.3 version and I can not back to stock
2) Error from TWRP is "E: Unable to mount '/Ecache"
3) I try to use dload folder with UPDATE.APP and its failed!
4) The phone boot and stop at MIUI logo
LikeM8 said:
What do you mean by wrong turn???
I can flash stock rom because:
1) I have TWRP 2.6.3.3 version and I can not back to stock
2) Error from TWRP is "E: Unable to mount '/Ecache"
3) I try to use dload folder with UPDATE.APP and its failed!
4) The phone boot and stop at MIUI logo
Click to expand...
Click to collapse
Calm man..
If you on stuck.. Cant bootup.. You must reflash your phone firmware..
Cant mount means your twrp has bugs.. Or your firmware corrupt.Try with another source.. To download..
AArga said:
Calm man..
If you on stuck.. Cant bootup.. You must reflash your phone firmware..
Cant mount means your twrp has bugs.. Or your firmware corrupt.Try with another source.. To download..
Click to expand...
Click to collapse
Thanks AArga to reply, I do not any fix???
LikeM8 said:
Thanks AArga to reply, I do not any fix???
Click to expand...
Click to collapse
If you want you can reflash your stock rom.. With pc.. If happened bootloop..
you have the wrong twrp version for miui..look here: http://forum.xda-developers.com/showthread.php?t=2534420
blueIBI said:
you have the wrong twrp version for miui..look here: http://forum.xda-developers.com/showthread.php?t=2534420
Click to expand...
Click to collapse
Ok and what I have to back to recovery stock version?
i dont know if thia is possible..but try to update your twrp to minimum 2.7.0.0 (or higher)
hey
when my phone boots shows that my device is not verified by google , what to do?
Jwtiyar said:
hey
when my phone boots shows that my device is not verified by google , what to do?
Click to expand...
Click to collapse
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
sukhwant717 said:
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
Click to expand...
Click to collapse
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Jwtiyar said:
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Click to expand...
Click to collapse
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
sukhwant717 said:
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
Click to expand...
Click to collapse
You made it really complex bro i dont understand what to do.
Jwtiyar said:
You made it really complex bro i dont understand what to do.
Click to expand...
Click to collapse
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
sukhwant717 said:
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
Click to expand...
Click to collapse
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Jwtiyar said:
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Click to expand...
Click to collapse
device model ze551ml oe ze550ml?
sukhwant717 said:
device model ze551ml oe ze550ml?
Click to expand...
Click to collapse
ze551
Jwtiyar said:
ze551
Click to expand...
Click to collapse
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
sukhwant717 said:
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
Click to expand...
Click to collapse
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Jwtiyar said:
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Click to expand...
Click to collapse
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
I installed RBR ROM which based on MM , now the error gone after flashing boot.img but the will boot to asus logo and will reboot again it seems its bootloop .
sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Jwtiyar said:
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Click to expand...
Click to collapse
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
sukhwant717 said:
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
Click to expand...
Click to collapse
custom MM
Jwtiyar said:
custom MM
Click to expand...
Click to collapse
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
sukhwant717 said:
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
Click to expand...
Click to collapse
thank you very much now its booted successfully
Jwtiyar said:
thank you very much now its booted successfully
Click to expand...
Click to collapse
great good to know your device is alive again
sukhwant717 said:
great good to know your device is alive again
Click to expand...
Click to collapse
Thank you bro
Hey guys, I'm having a problem.
I've installed the Miui 10 8.7.12 Global Beta and all is well, however i want to install TWRP so I can root and uninstall some Xiaomi apps still on the phone. However whenever I try to install TWRP via fastboot there are a few problems I face.
1) I flash twrp.img and its fine then I do fastboot reboot with volume up + power to go into recovery, but instead of taking me to TWRP, or even the stock recovery it keeps going back into fastboot mode.
2) When I try another method with adb reboot recovery it says device not found
3) If I try and directly go into recovery with fastboot boot twrp.img it restarts the phone and goes into the mi screen and nothing happens from there.
I've tried every possible combination I can think of and made sure I downloaded the proper TWRP from the official website and it still isn't working. Any input?
*EDIT*
I managed to figure it out! SORRY!!! Delete pls!
What was the problem?
how you solved ?
you got the anti rollback ?
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
achfighter said:
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
Click to expand...
Click to collapse
it works! thanks
achfighter said:
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
Click to expand...
Click to collapse
really helpfull i was looking several days and didnt found, thanks
Quote:
Originally Posted by achfighter
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
can i do this method without format data ?
I did it and I just got a: "The system has been destroyed" !!!! ¬_¬ -_-
achfighter said:
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
Click to expand...
Click to collapse
syaren said:
Quote:
Originally Posted by achfighter
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
can i do this method without format data ?
Click to expand...
Click to collapse
If you didn't format data, firmware may reinstall stock recovery after reboot.
Blue line, redline twrp blanck screen
Hi guys after installing miui pro miui 10 Oreo , my twrp become blank screen , i try to install using cmd , and i try to boot using cmd also didn't work , help me this .
Hello,
I've unlocked the bootloader and installed twrp..
First thing that was strange was that after I've put the .zip file to the internal memory, and booted back to twrp, the files were not there.. after that I've rebooted the phone, it asked me for a password (I've had no password after I've unlocked the bootloader)...
I've puted the Linage OS and Gapps on the external sd card..
Went to recovery again tried to flash the linage OS, got some error, like step 1 step 2.. and then error, tried to reboot into system.. now it only boots into fastboot.. I can get it to the EDL.. However cant flash twrp.. I get the error - mdp image is corrupted..
So I'm stuck! Don't know what to do anymore..
Any help is much appreciated.
Bucika said:
Hello,
I've unlocked the bootloader and installed twrp..
First thing that was strange was that after I've put the .zip file to the internal memory, and booted back to twrp, the files were not there.. after that I've rebooted the phone, it asked me for a password (I've had no password after I've unlocked the bootloader)...
I've puted the Linage OS and Gapps on the external sd card..
Went to recovery again tried to flash the linage OS, got some error, like step 1 step 2.. and then error, tried to reboot into system.. now it only boots into fastboot.. I can get it to the EDL.. However cant flash twrp.. I get the error - mdp image is corrupted..
So I'm stuck! Don't know what to do anymore..
Any help is much appreciated.
Click to expand...
Click to collapse
For me the problem was that I didn´t formatted DATA!
did you?
anykill said:
For me the problem was that I didn´t formatted DATA!
did you?
Click to expand...
Click to collapse
Damn, no I didn't! But I can't boot into twrp anymore.. just fastboot..
fastboot.exe boot .\twrp-daisy-3.3.0-0-offain.img
adb.exe push .\lineage-16.0-20190601-UNOFFICIAL-daisy.zip sdcard
adb.exe push .\ForcedEncryptionDisablerDaisy.zip sdcard <------ you need to flash this too
adb.exe push .\open_gapps-arm64-9.0-micro-20190601.zip sdcard
in twrp flash lineage (not gapps) than, reboot to fastboot
fastboot.exe boot twrp...
flash gapps
done
or go here!
https://github.com/tkchn/daisyinstall/blob/master/README.md
anykill said:
fastboot.exe boot twrp...
adb.exe push lineage.... /sdcard
adb.exe push gapps.... /sdcard
in twrp flash lineage (not gapps) than, reboot to fastboot
fastboot.exe boot twrp...
flash gapps
done
Click to expand...
Click to collapse
Yeah, it was that easy..
If I try to boot twrp I get the error, that mdpt image is corrupted and it doesn't boot..
Bucika said:
Yeah, it was that easy..
If I try to boot twrp I get the error, that mdpt image is corrupted and it doesn't boot..
Click to expand...
Click to collapse
Oh... maybe you need to do the EDL...
I had to do this one time when I flashed wrong image...
anykill said:
Oh... maybe you need to do the EDL...
I had to do this one time when I flashed wrong image...
Click to expand...
Click to collapse
< waiting for device > is all I get when I boot into EDL..
Bucika said:
< waiting for device > is all I get when I boot into EDL..
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=HTRLumtgqOM
However I do believe that the phone is not totally bricked, as I can boot into EDL and into Fastboot, but there is no system, no recovery.. And when I try to flash anything all I get is mdpt image is corrupted.. And If I try to flash anything from EDL it just says < waiting for device >
No..
I can get into the EDL by typing fastboot oem edl.. and computer recognize the device as Qualcom HS-USB QDloader 9008... I just can't find a way to flash anything..
Bucika said:
Yeah, it was that easy..
If I try to boot twrp I get the error, that mdpt image is corrupted and it doesn't boot..
Click to expand...
Click to collapse
try this
New TWRP 3.3.1-0 update:
Bootable: https://androidfilehost.com/?fid=6006931924117887098
Flashable: https://androidfilehost.com/?fid=6006931924117887097
Same thing.. Corrupted mdtp..
Bucika said:
Same thing.. Corrupted mdtp..
Click to expand...
Click to collapse
you tried the Miflash?
https://www.xiaomiflash.com/
and the stock firmware
https://bigota.d.miui.com/V10.0.8.0.PDLMIXM/miui_DAISYGlobal_V10.0.8.0.PDLMIXM_29324cbe1b_9.0.zip
Bucika said:
Same thing.. Corrupted mdtp..
Click to expand...
Click to collapse
Try to flash version 9.6.4.0. using the QFIL utility (QPST). maybe she will help
Bucika said:
Hello,
I've unlocked the bootloader and installed twrp..
First thing that was strange was that after I've put the .zip file to the internal memory, and booted back to twrp, the files were not there.. after that I've rebooted the phone, it asked me for a password (I've had no password after I've unlocked the bootloader)...
I've puted the Linage OS and Gapps on the external sd card..
Went to recovery again tried to flash the linage OS, got some error, like step 1 step 2.. and then error, tried to reboot into system.. now it only boots into fastboot.. I can get it to the EDL.. However cant flash twrp.. I get the error - mdp image is corrupted..
So I'm stuck! Don't know what to do anymore..
Any help is much appreciated.
Click to expand...
Click to collapse
Bro just stay in fastboot and flash the official stock firmware. Extract it on your computer and run FLASH ALL.
https://en.miui.com/getrom-354.html?m=yes&mobile=2
Btw- make sure you have charge over 50%
I don't recommend to use mi flash tool in that situation.
Download the fastboot rom and adb to the same folder and run the flash_all.bat.
What it will do it delete the partitions and remake them what mi flash tool don't do, after that your phone will be back to stock.
I played with this phone a lot and I even got the system is now destroyed message and also deleted my imei, if I did recovered from that so I know what I'm saying?
MAKE SURE TO NOT RUN THE FLASH_ALL_LOCK.BAT IF YOU DO WITHOUT TESTING IF YOUR SYSTEM BOOT FINE YOU COULD BRICK YOUR PHONE FOREVER!!!
OP did any of these methods work?
I had the exactly same problem when I first got to flashing on my A2 Lite. Download the newest Fastboot image, extract it with 7zip and run the flash_all.bat, <b>NOT THE FLASH_ALL_LOCK.BAT<b/>. This will recover everything. After that you can proceed normal installing. Also use unofficial TWRP by offain instead of the official one.
The exact installing instructions can be found here: https://github.com/tkchn/daisyinstall
Use only this installation guide, except for the disable encryption part: don't flash the disableencyption.zip directly after TWRP on Slot A, but instead install it after the GApps and leave out Magisk. This will automatically install Magisk 16.7 on your phone, but you can upgrade that after a successful boot. If you will try to flash the def.zip on the Slot A, it will give an error and your phone will encrypt the data on the first boot.
Noam5651 said:
I don't recommend to use mi flash tool in that situation.
Download the fastboot rom and adb to the same folder and run the flash_all.bat.
What it will do it delete the partitions and remake them what mi flash tool don't do, after that your phone will be back to stock.
I played with this phone a lot and I even got the system is now destroyed message and also deleted my imei, if I did recovered from that so I know what I'm saying
MAKE SURE TO NOT RUN THE FLASH_ALL_LOCK.BAT IF YOU DO WITHOUT TESTING IF YOUR SYSTEM BOOT FINE YOU COULD BRICK YOUR PHONE FOREVER!!!
Click to expand...
Click to collapse
thanks a lot , it work for my Mi a2 Lite which previously had an error message "device unable to boot Error - mdtp image is corrupted"
now normal again
i found the souliton man do you still need help? i had exact same problem
Hi guys, in short, I wanted to install the latest xiaomi.eu MIUI 12.5 beta on a Mi 10T Pro, european version.
What I did was: unlocked bootloader, flash latest TWRP 3.5 beta version, I think I booted the device normally after this...
Then went back to TWRP and flashed the Zip file right away, don't know what I wiped after the install.
All in all the device won't boot now, I'm stuck to either twrp or fastboot.
Problem is I cant flash a fastboot stock rom, says it's successful but the flashing process is like 2 seconds, i can't copy a recovery rom to the internal storage, i think Data partition got corrupted.
Can't wipe Data partition, there is a FBE decription error, and says unsupporter file system auto.
Does anyone have any idea what can I try.
Already tried to change Data file system to ext2 then back to ext4 but no luck.
PC recognizes the phone as a media device, I can see the Internal storage icon, but can't see any files nor can I copy anything to it.
Tried flashing the stock rom with mi flash tool and with command prompt too.
Any advice is welcome.
WSSRoach said:
Hi guys, in short, I wanted to install the latest xiaomi.eu MIUI 12.5 beta on a Mi 10T Pro, european version.
What I did was: unlocked bootloader, flash latest TWRP 3.5 beta version, I think I booted the device normally after this...
Then went back to TWRP and flashed the Zip file right away, don't know what I wiped after the install.
All in all the device won't boot now, I'm stuck to either twrp or fastboot.
Problem is I cant flash a fastboot stock rom, says it's successful but the flashing process is like 2 seconds, i can't copy a recovery rom to the internal storage, i think Data partition got corrupted.
Can't wipe Data partition, there is a FBE decription error, and says unsupporter file system auto.
Does anyone have any idea what can I try.
Already tried to change Data file system to ext2 then back to ext4 but no luck.
PC recognizes the phone as a media device, I can see the Internal storage icon, but can't see any files nor can I copy anything to it.
Tried flashing the stock rom with mi flash tool and with command prompt too.
Any advice is welcome.
Click to expand...
Click to collapse
LOG IN IN MI FLASH
jjgvv said:
LOG IN IN MI FLASH
Click to expand...
Click to collapse
What do you mean?
how do you flash stock rom 2 secs?
jjgvv said:
how do you flash stock rom 2 secs?
Click to expand...
Click to collapse
I think it doesn't fully flash, says it's successful but nothing really happens.
use what flash tool?
jjgvv said:
use what flash tool?
Click to expand...
Click to collapse
Tried latest from xiaomis website but that gives error, so i tried to download one from another website, says its latest version too
have you log in in that flash tool?
jjgvv said:
have you log in in that flash tool?
Click to expand...
Click to collapse
There is no way to log in, aren't you talking about the mi unlock tool?
mi flash?
jjgvv said:
mi flash?
Click to expand...
Click to collapse
Yes, there is no option to log in to mi flash tool
fastboot erase data then
jjgvv said:
fastboot erase data then
Click to expand...
Click to collapse
How do i do that?
WSSRoach said:
How do i do that?
Click to expand...
Click to collapse
go into fastboot and Type fastboot erase data in the fastboot cmd prompt
jjgvv said:
go into fastboot and Type fastboot erase data in the fastboot cmd prompt
Click to expand...
Click to collapse
Will try as soon as i get near a PC
jjgvv said:
go into fastboot and Type fastboot erase data in the fastboot cmd prompt
Click to expand...
Click to collapse
Sadly it fails
WSSRoach said:
Sadly it fails
Click to expand...
Click to collapse
how does it fail
jjgvv said:
how does it fail
Click to expand...
Click to collapse
I typed fastboot erase data, i get: FAILED (remote: Check device console)
Code:
fastboot -w
or
Code:
fastboot erase userdata
is the correct command. Now, if this fails, find lr-twrp, flash that, reboot, wipe data, and try again... And you have to do fastboot commands from fastboot, not from twrp...
calinorg said:
Code:
fastboot -w
or
Code:
fastboot erase userdata
is the correct command. Now, if this fails, find lr-twrp, flash that, reboot, wipe data, and try again... And you have to do fastboot commands from fastboot, not from twrp...
Click to expand...
Click to collapse
this looks like it worked, still now says unable to mount storage when trying to format data from twrp, but thats a step ahead...now it says in yellow )
I have an idea to flash lineage os recovery with fastboot, might that work?