Hi,
So I have TWRP from the toolkit. And I previously had Mokee latest, then I switched to MIUI7 5.11.14(latest).
Now I downloaded Resurrection Remix, and before flashing it I tried to flash MIUI V6.6.10.0.LXIMICF, which failed spectacularly displaying the error below:
mount : failed to mount /dev/block//bootdevice/by-name/userdata at /data : Device or resource busy.
mount : failed to mount /dev/block//bootdevice/by-name/system at /system: Device or resource busy.
the updater script failed to execute
This happens with me quite often when I try to switch between MIUI and CM based ROMs.
And I dunno how this happens but I keep trying to flash MIUI and then reboot if it fails and then wipe "Cache, data, dalvik cache, system" again and flash MIUI again, and sometimes it takes 2-3 tries and it flashes., the script succeeds.
The same happened today
-had MIUI 5.11.14, rebooted to recovery(TWRP)
-wiped [system, data, dalvik cache, cache]
-tried to flash MIUI 6.6.10, it failed
-tried to flash RR, it succeeded but the ROM acted weirdly. The screen would turn off and the phone won't respond. So no luck
-rebooted wiped [system, data, dalvik cache, cache]
-tried to flash MIUI 6.6.10, it failed
-rebooted and factory reset performed. Tried to flash MIUI 6.6.10, it failed
-rebooted again and factory reset performed. flashed MIUI successfully, then performed factory reset, and flashed RR, and successfully booted up the ROM. Finally
This type of flash failure is not limited to the 6.6.10, it happens with 6.7.2 and also 5.8.11(dev version)
Can someone tell me why this happens, and does it happen on everyone's Mi4i? Or am I doing something wrong?
I know its long but I had to explain what I did properly.
Friend, same situation here!
I have my mi4i since august and i try every custom and official/developer rom. Every time i try a rom i have the same problems as you. I never posted because i thought i m doing something wrong but i am very experienced guy, doing such stuff many years, and i couldn't beleave that. Btw, i have the same strange behavior from twrp & flashing roms on my mi4i, and i can't understand what's wrong...
anurox2 said:
Hi,
mount : failed to mount /dev/block//bootdevice/by-name/userdata at /data : Device or resource busy.
mount : failed to mount /dev/block//bootdevice/by-name/system at /system: Device or resource busy.
the updater script failed to execute
Click to expand...
Click to collapse
Thats because you tried to flash miui recovery rom using TWRP. You must flash miui rom with miui stock recovery only. This is why I highly recommended people who wants to try custom ROM to only 'fastboot boot twrp.img' rather than installing it permanently because you can easily flash the miui stock rom again next time u want to back to miui rom.
Unlike twrp, miui 6 recovery is not the same with miui 7. If you tried to flash stock recovery using fastboot flash recovery for different version of miui, it will not work.
Unless you prefer to stay under custom ROM, I highly recommend that you keep your stock recovery intact.
yumm91 said:
Thats because you tried to flash miui recovery rom using TWRP. You must flash miui rom with miui stock recovery only. This is why I highly recommended people who wants to try custom ROM to only 'fastboot boot twrp.img' rather than installing it permanently because you can easily flash the miui stock rom again next time u want to back to miui rom.
Unlike twrp, miui 6 recovery is not the same with miui 7. If you tried to flash stock recovery using fastboot flash recovery for different version of miui, it will not work.
Unless you prefer to stay under custom ROM, I highly recommend that you keep your stock recovery intact.
Click to expand...
Click to collapse
Thank you
I will remember to flash the stock recovery using the toolkit next time I switch back to MIUI.
But
If the MIUI rom[6.6.10] or the latest dev[5.11.14] rom needs stock recovery to flash properly, why did it work on the third try? What made it work?
I mean if we find out what makes it flash without error on TWRP we could avoid using stock recovery na?
And btw I was trying MIUI, not the custom ROM, I always stay on them, just wanted to see what MIUI had changed since September.
BUMP!!
Seriously!! someone??
You need to extract the stock recovery from the firmware, then flash it via fastboot, then flash the stock zip
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
jjeans said:
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
Click to expand...
Click to collapse
Download fastboot rom and flash it
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
jjeans said:
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
Click to expand...
Click to collapse
How do you flash recovery tell me the procedure?
Talha7866 said:
How do you flash recovery tell me the procedure?
Click to expand...
Click to collapse
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
jjeans said:
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
Click to expand...
Click to collapse
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
zhart said:
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
Click to expand...
Click to collapse
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
jjeans said:
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
Click to expand...
Click to collapse
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Sorry, what exaclty is a fastboot rom and where do i get it?
zhart said:
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Click to expand...
Click to collapse
I don't know what happens all the time.
Currently I used MiFlash to make a clean fastboot install. I choosed in MiFlash "flash_all.bat" to do it. (flash_all.bat means everything was reinstalled, also recovery.img). Afterwards everything was normal, MiRecovery 2.x and Mi4C MiUI 7 chinese version was installed without error. But after manual flashing TWRP with "fastboot flash recovery xxx", the recovery loop was again! :/
So AGAIN I made a clean fastboot install again with MiFlash application, but this time I REPLACED the recovery.img with the newest TWRP (renamed to recovery.img) within the fastboot rom installation folder "images". I could see that MiFlash flashed THIS! recovery.img, but after that again the old Mi Recovery was on the device and no TWRP. But why? I replaced the original recovery.img file! How can that happen?
The flash_all.bat included flashing recovery and I could confirm it during the fastboot flash. Strange.
I used fastboot rom libra_images_V7.0.16.0.LXKCNCI_20151104.0000.4_5.1_cn
MiFlash newest version and I tried with 2 TWRP versions (one from decuro and one from sMiUI)
Maybe my phone has a problem with flahing recoverys in general I don't know.
jjeans said:
Maybe my phone has a problem with flahing recoverys in general I don't know.
Click to expand...
Click to collapse
it sound very strange i did all these steps and my phone was all good after it. is it the newest recovery? the one with material theme and touch fix you are using? if not, then thats the only difference between your procedure and mine :/
i hope you can fix it
Edit: I can see that i have the following fastboot roms downloaded, so i used one of these:
libra_images_V7.0.6.0.LXKCNCI_20150917.0000.1_5.1_cn_4dd76a55cb.tgz
or libra_images_V7.0.15.0.LXKCNCI_20151104.0000.4_5.1_cn_f6e955ee14.tgz
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Hello, don't know if applicable. I've read on mi forums that dev Roms need dev recovery, that's different from twrp for stock rom.....
guegangster said:
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Click to expand...
Click to collapse
Hallo,
thank you, that worked for me finally
I have now used another TWRP 2.8.7.1 with touch-issue, but that is now no problem.
I flashed also xiaomi.eu rom, for now seems to be stable and cleaned.
strange everything, but now it is fixed.
BR,
Jimmy
I cant boot into any recovery mode afer installing any the custom roms like pixel experience in redmi note 7 pro violet.
whenever it try to boot into recovery mode , it cannt boot up into any recovery mode. please help me. i am tired of flashing stocked rom again and again for flashing new customs rom. i lost its all recovery mode,neither twrp nor its inbuilt recovery mode. phone only get restarting in normally.
Dhiraj bhattarai said:
I cant boot into any recovery mode afer installing any the custom roms like pixel experience in redmi note 7 pro violet.
whenever it try to boot into recovery mode , it cannt boot up into any recovery mode. please help me. i am tired of flashing stocked rom again and again for flashing new customs rom. i lost its all recovery mode,neither twrp nor its inbuilt recovery mode. phone only get restarting in normally.
Click to expand...
Click to collapse
Reflash twrp using fastboot mode?
Sachin said:
Reflash twrp using fastboot mode?
Click to expand...
Click to collapse
I had tried to reflash twrp in fastboot mode but it also didn't work.. It say "too many link,status red ,failed,error" .....blah blah.. I couldn't do anything rather reflashing stocked ROM. Did I missed anything while flashing new custom ROM so that I had been losing recovery mode??
Dhiraj bhattarai said:
I had tried to reflash twrp in fastboot mode but it also didn't work.. It say "too many link,status red ,failed,error" .....blah blah.. I couldn't do anything rather reflashing stocked ROM. Did I missed anything while flashing new custom ROM so that I had been losing recovery mode??
Click to expand...
Click to collapse
Looks like it. So, next time you flash a ROM just keep these things in yo mind -
Boot to Peter's twrp
Wipe
Flash latest firmware.zip
Flash Rom
Flash Gapps
Flash fcrypt zip
Flash magisk
Format data (if you're installing custom Rom for the first time)
Then reboot.
^^
Sachin said:
Looks like it. So, next time you flash a ROM just keep these things in yo mind -
Boot to Peter's twrp
Wipe
Flash latest firmware.zip
Flash Rom
Flash Gapps
Flash fcrypt zip
Flash magisk
Format data (if you're installing custom Rom for the first time)
Then reboot.
^^
Click to expand...
Click to collapse
Thanks ,?
Sachin said:
Looks like it. So, next time you flash a ROM just keep these things in yo mind -
Boot to Peter's twrp
Wipe
Flash latest firmware.zip
Flash Rom
Flash Gapps
Flash fcrypt zip
Flash magisk
Format data (if you're installing custom Rom for the first time)
Then reboot.
^^
Click to expand...
Click to collapse
fcrypt is optional right
I need help, I unlocked my phone's bootloader, then flashed lastest twrp recovery plus disable DM - verification after rebooting to recovery. Now, from twrp I can't seems to flash anything I get some kind of errors everytime, so I flashed orangefox. From there I tried to flash roms/gapps/magisk, it completes them without any issues but when I try to boot system it goes back to recovery, and now, I greet with 0mb reading on my internal storage, to fix that I format data then flash rom and magisk again and try to boot again but alas! It boots to recovery again, so tried booting to system few more times and it worked, now I'm in corvus os , everythings working fine but if I go to recovery now I again greet with 0mb error.....plz I need help.
Also if I wanna flash any other rom or anything through recovery, I have to flash firmware everytime, and most times they don't even boot