I was applying update using cyanogen recovery but it failed showing can not mount E:/cache (Invalid argument) so someone told me to flash using fastboot so I downloaded fastboot package and flash tools and kept in same folder and double clicked flash-all.bat ,it started flashing and after the procedure get over and command promt automatically closed but the device again stucked on boot logo . I am in deep trouble now don't know what to do ?can Anyone help me
same problem
s.ravi said:
I was applying update using cyanogen recovery but it failed showing can not mount E:/cache (Invalid argument) so someone told me to flash using fastboot so I downloaded fastboot package and flash tools and kept in same folder and double clicked flash-all.bat ,it started flashing and after the procedure get over and command promt automatically closed but the device again stucked on boot logo . I am in deep trouble now don't know what to do ?can Anyone help me
Click to expand...
Click to collapse
same problem is occuring with me. done complete flashing procedure but still it is stuck on YU logo??? what to do please help...
try to flash zip using twrp 3.0.2.0
Related
I have a Moto G 4G, with android 4.4.4 bootloop.
I can enter fastboot mode and TWRP recovery 2.7.0.1 . The recovery tells me I do not have any operating system installed. I get an error E: Unable to mount '/system' when i try to format/wipe, also can´t instal a new os from mfastboot and can not update the TWRP from mfastboot. Using ADB sideload allows me to load zip files but the cellphone is unable to mount any folder so I get an other error.
Any solution ?
Did you tried reflashing stock firmware via fastboot ?
Try to Mount system partition in Ur Recovery then Give a try.
Eurofighter_ty said:
Did you tried reflashing stock firmware via fastboot ?
Click to expand...
Click to collapse
All ready tried to reflash stock 4.4.4 which was the version that it had.
jbanti said:
Try to Mount system partition in Ur Recovery then Give a try.
Click to expand...
Click to collapse
E: Unable to mount '/system
Hello,
I was facing a lot of issues with my YUPHORIA. So, I tried to flash it using the official instructions on official forum using Fastboot.
The flashing got stuck when it was trying to flash the "system" partition. I disconnected the cable and tried the flashing process again.
Now, I am able to flash everything else except "system"
It is giving an error -
"FAILED (remote: flash write failure)"
ADB is not detecting my phone.
QFIL is also showing "No Ports Found"
However, Fastboot is working fine.
I donot have TWRP on my phone as of now.
Please help !
I am having exact same problem. Were you able to find solution for it?
Same issue here
Did you get the final solution?
I cant not flash system.img to my softbricked Yu Yuphoria 5110 even with the latest version of adb and fastboot and even with the -S option! Nothing works! Can't flash only system.img, other images are getting flashed. Pl help!
Hello,
I had Resurrection Remix Android 7.1.2 installed in my Mi4i. The apps were suddendly crashing (was getting app crashed alert) and thought to reboot the phone once.
Once I tried to reboot abnormality started showing up.
Tried flashing the Resurrection Remix again but it stuck at the boot animation screen.
Then tried flashing the official MIUI developer rom and it worked.
Again tried with RR but it did not boot up.
After trying a couple of times, none of the roms did boot up.
After some research found in TWRP logs that it is unable to mount system, cache, dalvik cache etc.
Also I could see that the space/memory is displayed as 0MB.
Some forums said to format the file system as ext4 and even the format failed saying it is unable to mount.
Now whenever I start the phone to goes to the fastboot screen.
The interesting point is that I tried flashing manually the developer rom and it said it falshed successfully.
But i still see the twrp as my recovery and not the stock recovery after flasing.
Also tried manually flashing the recovery like "fastboot flash recovery recovery.img" and did not find any errors still the stock recovery was not flashed instead the twrp remained as the recovery even after successful flash.
I am stuck with my phone now and not sure how to proceed.
Any help regarding this would really be helpful.
Help me to recover my phone please. :crying:
Thanks.
So have you format all of your data including internal data from TWRP ? Is it show some error like "unmount /data" types N how you flash rom manually means you tried of ADB slide load ??
Mukulkathuria008 said:
So have you format all of your data including internal data from TWRP ? Is it show some error like "unmount /data" types N how you flash rom manually means you tried of ADB slide load ??
Click to expand...
Click to collapse
1. Tried formating the partitions from TWRP.. Failed with error message saying cant mount
2. Hence thought TWRP was broken.. Tried flashing twrp again from fastboot as follows :
Code:
fastboot flash recovery recovery.img
Fastboot flashed successfully(got OKAY response in terminal).
3. Rebooted into recovery and tried formatting partitions again. Still got the same error saying cant mount partitions.
4. Thought to flash stock recovery. Had miui fastboot room. Picked up recovery.img from it and flashed from fastboot as follows :
Code:
fastboot flash recovery recovery.img
5. Surprisingly when I rebooted into recovery, the custom recovery was still twrp.. The stock recovery didn't got flashed.
6. To crosscheck, I directly booted the stock recovery fastboot boot recovery.img. But nothing boots up.. Gets stuck at the distorted fastboot screen (Attaching screenshot if possible).
Probal Basak said:
1. Tried formating the partitions from TWRP.. Failed with error message saying cant mount
2. Hence thought TWRP was broken.. Tried flashing twrp again from fastboot as follows :
Code:
fastboot flash recovery recovery.img
Fastboot flashed successfully(got OKAY response in terminal).
3. Rebooted into recovery and tried formatting partitions again. Still got the same error saying cant mount partitions.
4. Thought to flash stock recovery. Had miui fastboot room. Picked up recovery.img from it and flashed from fastboot as follows :
Code:
fastboot flash recovery recovery.img
5. Surprisingly when I rebooted into recovery, the custom recovery was still twrp.. The stock recovery didn't got flashed.
6. To crosscheck, I directly booted the stock recovery fastboot boot recovery.img. But nothing boots up.. Gets stuck at the distorted fastboot screen (Attaching screenshot if possible).
Click to expand...
Click to collapse
Try to flash TWRP v3.2.1.0 you can download from link below:
https://dl.twrp.me/ferrari/twrp-3.2.1-0-ferrari.img.html
And Advance Wipe And change the file format to ex4 and wipe all the data try ROM try flash ROM link below through OTG:
https://forum.xda-developers.com/mi-4i/development/unofficial-dotos-v1-2-t3726924
that surely solve your all problems :fingers-crossed:
Mukulkathuria008 said:
Try to flash TWRP v3.2.1.0 you can download from link below:
https://dl.twrp.me/ferrari/twrp-3.2.1-0-ferrari.img.html
And Advance Wipe And change the file format to ex4 and wipe all the data try ROM try flash ROM link below through OTG:
https://forum.xda-developers.com/mi-4i/development/unofficial-dotos-v1-2-t3726924
that surely solve your all problems :fingers-crossed:
Click to expand...
Click to collapse
Tried formating to ext4.. But nothing happened.. Still getting mount error.
Attaching pics below.
Attachment 1 : Advanced Wipe -> Wipe
Attachment 2 : Advanced Wipe -> Change File System -> /system -> ext4
I have also tried this
Code:
fastboot getvar all
Output:
Code:
all:
finished. total time: 0.001s
Any comments what may have gone wrong?
fix file system. or maybe emmc died
Problem occurred after I flashed with 9.3.1 Global Beta, which ended with "flash system error", unlocked BL and flashed in fastboot mode. Since then the bootloop begins.
I have access to:
Fastboot
Recovery (both TWRP 3.2.3.0 and Stock Recovery 3.0)
EDL - unauthorized (not test point)
My phone has Unlocked Bootloader officially, using the Mi-Unlock after waiting for 15 days.
It's less than a month old, never dropped it. I disabled Driver Signature Enforcement when flashing. I have the phone correctly recognized when in fastboot, EDL and recovery mode by my PC.
I have tried:
Flashing 10.2.2.0 Global in fastboot mode with MiFlash, finished without error
Flashing 9.3.1 Global Beta in fastboot mode with MiFlash, finished without error
Changing USB Port and cables
Flashing 10.2.2.0 Global in TWRP, finished with error Failed to mount '/persist' (invalid argument)
Flashing 9.3.1 Global Beta in TWRP, finished with error Failed to mount '/persist' (invalid argument)
Flashing in TWRP, putting the zip file thru adb push command
Flashing in TWRP, putting the zip file thru MicroSD Card
Erasing/Flashing persist.img thru adb command, with "error:FAILED (remote: Flashing is not allowed for Controlled Partitions"
Using "fastboot erase system" before flashing
Note: While in TWRP, even when I just boot into it, if I click the 3 lines at the bottom right (the opposite of the "back" button), it shows TWRP log and it would have:
Updating partitions (in white color)
Failed to mount '/persist' (invalid argument) (in red color)
The main problem now that makes me confused, is that the fact it flashed successfully without error in MiFlash, but then it bootloops. It doesn't reboot itself, just after the Mi logo with "Unlocked" on the bottom, then it changed to Mi logo with loading animation below with the white dots, then it stays like that..
Please help.. :'(
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Click to expand...
Click to collapse
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
SubwayChamp said:
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
Click to expand...
Click to collapse
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
bob_bricoleur said:
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
Click to expand...
Click to collapse
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
SubwayChamp said:
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
Click to expand...
Click to collapse
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
bob_bricoleur said:
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
Click to expand...
Click to collapse
Some times causes different results flashing the fastboot full image through EDL mode (download mode) instead of through fastboot mode.
It could be the issue the TWRP version if there is other available.
And you could try deleting the recovery partition with fastboot erase recovery, then boot (don´t flash yet) to recovery using fastboot boot whateveriscalled.img, then in TWRP flash the TWRP image or the installer zip, then reboot for first time to TWRP and try again.