I used this Cwm to flash my mi3 (16 gb, bought from flipkart).
en*miui*com/thread-32222-1-1.html
First I wiped data and cache
It showed..
Wiping \data
wiping \cache
Then when it was stuck on it for more than 2 minutes, I powered off my phone (I know, big mistake)
Then when I booted into recovery again, then it was showing something like this.. (I don't remember completely)
E: can't mount \cache
E: can't open \cache
E: can't mount \cache\recovery\last_install
Etc.... (I am sorry if I didn't got it right, but you guys are probably experienced with this kind of error)
Then I wiped Dalvik cache
Wiped system
Installed zip successfully (can't install gapps "insufficient storage") but thought that cm11 should still boot without gapps. It was then stuck on cm11 boot logo for half an hour then I surrendered and powered it off.
Again I booted into recovery it still the can't mount cache error and now can't wipe cache (its just stuck there) (I read on that link that this cm11 takes 5 minutes or more first time to wipe cache, but yeah I screwed up,) now it won't even finish on 5 minutes, it's stuck for forever.
I did some research and found that I got my cache partition corrupted (everything else is fine i.e, data, system, dalvik-cache. I checked).
So is there any way to fix my cache partition, if there is any pls help me.
Flash TWRP, Mi3 has now got official support for it. The latest version being 2.8.5.0
Then Try Flashing MOKEE ROM or XenonHD or iVan's ROM they are based on lollipop.
They all have no major bugs.
Links to everything i have mentioned can be found in Mi3's Forum here on XDA.
Tried it
akshayAXE said:
Flash TWRP, Mi3 has now got official support for it. The latest version being 2.8.5.0
Then Try Flashing MOKEE ROM or XenonHD or iVan's ROM they are based on lollipop.
They all have no major bugs.
Links to everything i have mentioned can be found in Mi3's Forum here on XDA.
Click to expand...
Click to collapse
I tried twrp 2.8.5.0, it also shows can't mount cache. I tried MOKEE and xenon both stuck at boot. :/
booo159159 said:
I tried twrp 2.8.5.0, it also shows can't mount cache. I tried MOKEE and xenon both stuck at boot. :/
Click to expand...
Click to collapse
Use Miflash with fastboot it will fix the mess and then you could flash cwm/twrp again
Are you ok now?
Related
I was trying to flash CM12 on my XT1068 indian version through TWRP, while installing CM 12 & GAPS GAPPS gave me some errors and it did't flash so i wiped system, data, dalvik cache, cache.
Again i tried to flash CM12 rom and gave me error "unable to mount system".
after that the phone kept restarting even TWPR won't work, so i tried to flashed CWM through fastboot still unavailable to start.
i can boot my phone in bootloader.
Please Help im a Newbe
Return to stock
Flash CM11 let it boot (make sure your using the latest TWRP) and then flash CM12
Hansil said:
I was trying to flash CM12 on my XT1068 indian version through TWRP, while installing CM 12 & GAPS GAPPS gave me some errors and it did't flash so i wiped system, data, dalvik cache, cache.
Again i tried to flash CM12 rom and gave me error "unable to mount system".
after that the phone kept restarting even TWPR won't work, so i tried to flashed CWM through fastboot still unavailable to start.
i can boot my phone in bootloader.
Please Help im a Newbe
Click to expand...
Click to collapse
Flash stock firmware, use this:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
Hi all,
I tried to flash a custom Rom and gapps but it got in a bootloop (first i wiped data, system, cache and art/dalvik cache). It says kernel is not seandroid enforcing.
In think the problem was that the custom rom was android 6.0 but the tablet was on 5.0
What can I do now? How do I get into twrp? I tried all button combinations.
Thanks!
Edit: fixed it, finally managed to get into twrp and restore my backup. Now I still have to figure out how to install the custom rom
That's good uve got it working, if your device is compatible just use the relevant sections from the following guide:
http://forum.xda-developers.com/tab-s2/general/sm-t710-6-0-1-t710xxu2cpd9-marshmallow-t3371545
Hey Boys and girls,
I dont know why lineage os 14. 1 dont run on my s4active. Its a I9295.
First i installed twrp 3.1.1.0 recovery with heimdall 1.4.1 on ubuntu 16.04.
Then i flashed lineage-14.1-20171017-UNOFFICIAL-jactivelte from Sd Card in recovery mode
(with the same setup and method i flashed lineage os 14.1 on I9300 and I9500 without problems)
Next i can see lineage startscreen for hours
I tested it too with twrp 3.1.0.0 and two older builds of lineage 14.1. with and without gapps, everytimes I wiped Dalvik, System, Data, Internal Storage and Cache bevore flashing,
and wipe cache&Dalvik after flashing. Always whithout errors.
Thank you everybody and sorry for my scool english
Unfortunately I can't offer help, because I suffer from the exact same problem. Tried to flash tsvetkov_vlad's CM14.1 once some time back in spring already and the behavior has not changed since.
It remains stuck showing the boot animation and does not even arrive at the screen to input the encryption password.
There are no errors in the TWRP log.
Ok, I found the solution (for me). I stumbled accross some blog post claiming that most of the time when the boot animation shows infinitely long, there is a problem with mounting some partition. For me, that was /cache, which I had previously formatted as f2fs. After changing it back to ext4 again, booting works as expected. This has never been a problem with any of the older versions of CM I used before, though.
Maybe this helps?!
Oh yes this was the solution for me too.:fingers-crossed:
I had to formate /cache in f2fs then back in ext4 for four times.
Then booting was completely normal.
Longpu you have changed my live My gratitude will haunt you forever and ever
Cant boot into system after installing miui11. Everytime when i boot into system it reboots into twrp.
nerijusas said:
Cant boot into system after installing miui11. Everytime when i boot into system it reboots into twrp.
Click to expand...
Click to collapse
More details needed if you want some help or all you wanted is some condolence?
P.S. If you don't know what details, just describe what actions have been taken I was on ROM x versions x.x.x with TWRP x, how you flashed MIUI11 and what MIUI11 ROM and version you used.
TWRP version is: 3.3.1-42
I was on original rom and I used this rom: xiaomi.eu_multi_MI9_V11.0.2.0.QFACNXM_v11-10
Procedure: I wiped dalvik/ART cahce, cache, System Data and then installed the rom and rebooted and I am now in bootloop.
P.S I have global version
nerijusas said:
TWRP version is: 3.3.1-42
I was on original rom and I used this rom: xiaomi.eu_multi_MI9_V11.0.2.0.QFACNXM_v11-10
Procedure: I wiped dalvik/ART cahce, cache, System Data and then installed the rom and rebooted and I am now in bootloop.
Click to expand...
Click to collapse
Does your TWRP successfully decrypt data now? Do you have access to files in TWRP? Or you just see strange names.
If that is the case, just format data, it's an option in wipe menu. And then reflash ROM.
btw wiping system is not needed and useless.
Decrypts successfully because i install rom from internal storage and still it doesnt help.
nerijusas said:
Decrypts successfully because i install rom from internal storage and still it doesnt help.
Click to expand...
Click to collapse
Then everything should work, try to read this thread: https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/ , may be you not the only one.
But i would try format data any way. Format will remove everything and will create a fresh unecrypted file system. Wipe only delete files.
If it won't help you may try to flash fastboot ROM, and then format and etc.
btw When you wipe cache/dalvik, it takes some time to boot, it can be 5-10 minutes.
(Im spanish, sorry if my english has errors or is really bad )
Hi, i've got a problem, I spent all day trying to fix a wrong rom installation but nothing works.
I was using Revolution Remix 8.6.2 and I wanted to try the new official hentaiOS, so I made a complete twrp backup of everything and I copied it to my computer, I wiped system, data, dalvick, and cache, and I flash hentaiOS rom zip. It was a normal bootloop so I just wiped all and restored the backup, but it didnt work (System had magisk with some modules but nothing happend in the previous reboots), so I rebooted into recovery to flash the clean RROS zip and try restoring only some parts of the backup to see which partition was causing the bootloop, but I was unable to boot into recovery, I used mi flash with miui 12 fastboot rom, it worked so I flashed TWRP again and tried to install RROS but nothing works.
I already tried with RROS 8.6.2, 8.6.1 and 8.6.0 but no one works, now Im gonna try with ArrowOS (It didn't work) but I want to use RROS, what can I do?
Xsoft32 said:
(Im spanish, sorry if my english has errors or is really bad )
Hi, i've got a problem, I spent all day trying to fix a wrong rom installation but nothing works.
I was using Revolution Remix 8.6.2 and I wanted to try the new official hentaiOS, so I made a complete twrp backup of everything and I copied it to my computer, I wiped system, data, dalvick, and cache, and I flash hentaiOS rom zip. It was a normal bootloop so I just wiped all and restored the backup, but it didnt work (System had magisk with some modules but nothing happend in the previous reboots), so I rebooted into recovery to flash the clean RROS zip and try restoring only some parts of the backup to see which partition was causing the bootloop, but I was unable to boot into recovery, I used mi flash with miui 12 fastboot rom, it worked so I flashed TWRP again and tried to install RROS but nothing works.
I already tried with RROS 8.6.2, 8.6.1 and 8.6.0 but no one works, now Im gonna try with ArrowOS (It didn't work) but I want to use RROS, what can I do?
Click to expand...
Click to collapse
I found the way to boot RROS, I flashed the vendor of the lineageOS post
(Link: https://forum.xda-developers.com/k20-pro/development/rom-lineageos-17-0-t3976469 )
and after that I flash RROS 8.6.0, once it boot I reboot to recovery and started updating it.
Hope this info is useful for someone