Installing the AOSP ROM for the MTK RN3, keep coming up with the same issue inside TWRP of "unmount of /system failed; no such volume" However it still sayss "Install Complete" So I wipe dalvik and reboot and it just returns me to TWRP. Been searching online for a few hours now.
Come from CM12.1 having already used another version of CM12 before that so it isnt a unlock/coming from miui I hope.
*** Alright, turns out when I selected inside of twrp to reboot to system it would reboot to Twrp, so I selected power off then turned it back on and it launched like normal using AOSP ***
Any help/advice is appreciated!
How did you solved this problem? Having the same issue on my Mi Mix 2 now, searching for hours now but still no solution. Someone help me pls?
I am also having same issue.
while installing xiaomi redmi note 3 special edition (high version) official rom it takes very much time and doesn't complete the process,
I put it for one whole night (more than 9 hours) but still it is pending and doesn't finish the installation of rom.
While installing custom rom (I am using pixel experiance and others custom rom based on other other android version) it shows installing started and immediately it shows failed to unmount system-no such volume.
my phone is fully dead cause i erased it fully ( dalvik/system/catch/internal storage and all partition) with twrp recovery.
also i used other recovery like red wolf thinking that it will solve this problem, but all are still same in redwolf too.
nothing happens, and my phone is dead with charged 100%.
anyone please help me what can i do to in this.... to make my phone alive....
Help!!!!!!!! ;-(
I have also same problem... anyone knows solutions?
Related
Hello everyone, i checked a lot on internet and on the forum, but anyone has my phone or had the same problem
So, i have a xiaomi mi note 3 with the last global stable 9.5.3.0, miui 9.5 the bootloader was unlocked with the official way
I wanted to root the phone so i downloaded 4 different twrp because some of them just didn't work, i couldn't do nothing, the touch didn't worked or just the phone doesn't responde at all.
So, i found the twrp version that it works, i copied supersu on the main phone's directory and reboot the phone in twrp mode
and here the first problem.
I could find nothing, twrp says i have 0 bytes
i didn't touched anything in twrp setting, so i tryed with a data wipe and my phone got a soft brick
i flashed my rom again, unlocked the bootloader, installed the twrp again and again, 0 bytes
i tryed to wipe data again, soft brick again
Tired of that i just flashed again the rom and actually my bootloader is locked, cuz bored to do the first set up over and over
I really hope someone can help me
Sorry for my english, i know it's bad but it's not my first language
Anyone can help me ?
So, finally i solved the problem
I hope it will help ppl that they have my same problem
As i said i have xiaomi mi note 3 with miui 9, with the global rom 9.5.3.0 Stable, the only one twrp that it works on my phone is the last, 3.2.1-0 version
After i flashed twrp with fastboot it just asked me a password, and nobody knows what password it's needed, just skip that and press cancel
After that i couldn't find magisk or supersu in my internal storage cuz it said i had 0bytes on it, so i did a wipe data but after that the phone got softbricked
So i just pressed volume + and power button to get inside twrp again and now my storage was fixed, so i connected the phone at the pc and i copied magisk inside the internal storage
I flashed it and reboot my phone, it tooks about 5 - 10 minutes so it started the first setup again
After that magisk was finally on my homescreen, i downloaded root checker and it said my device was properly rooted
Until yesterday I had the MIUI ROM for my Redmi Note 4, however I wanted to send another two ROMS (Lineage and Resurrection Remix) to see if they would convince me.
(I clarify that I already knew the process to install Roms).
So I rebooted in Recovery mode, hize / wipe and then install Lineague, but automatically I realized that I was making an error, saying that the rom was for Mido and that my cell phone instead of mido was, literally, a point.
So I turned on the pc, use the xiaomiMiFlash tool to install a miui rom (of course, with the option of clean_all) and unpleasantly I was surprised that it restarted every 20 or 30 sec., Please I need help, because I've tried other roms and it's still the same, turn it on, exit the start menu and after a few seconds it restarts. Tell me what I can do.
What does this mean - "my cell phone instead of mido was, literally, a point"? What cellphone do you have?
rossarnie said:
What does this mean - "my cell phone instead of mido was, literally, a point"? What cellphone do you have?
Click to expand...
Click to collapse
I have a Redmi Note 4(Mido, the version with a Qualcomm CPU) and this restarts every 30 sec, I've even used MiFlash to flash the rom with the option to clean everything and even so it remains the same.
I already try with this guide: https://forum.xda-developers.com/redmi-note-4/how-to/how-to-fix-totally-dead-redmi-note-4-t3746465 and nothing, I get an error of "Sahara" with qfil
Treinor said:
Until yesterday I had the MIUI ROM for my Redmi Note 4, however I wanted to send another two ROMS (Lineage and Resurrection Remix) to see if they would convince me.
(I clarify that I already knew the process to install Roms).
So I rebooted in Recovery mode, hize / wipe and then install Lineague, but automatically I realized that I was making an error, saying that the rom was for Mido and that my cell phone instead of mido was, literally, a point.
So I turned on the pc, use the xiaomiMiFlash tool to install a miui rom (of course, with the option of clean_all) and unpleasantly I was surprised that it restarted every 20 or 30 sec., Please I need help, because I've tried other roms and it's still the same, turn it on, exit the start menu and after a few seconds it restarts. Tell me what I can do.
Click to expand...
Click to collapse
I guess you flashed a treble ROM using a non treble recovery. Use this recovery and try to flash lineage OS again.
https://drive.google.com/a/my.smccd.edu/uc?id=1I_EaHHPWERIaMyBasfGJldugLjadU13P&export=download
Recently I've encountered a problem on my Redmi Note 3 Pro 3 gb ram 32 gb. I've been using custom ROMs and Kernels for a while. One day my phone switched off after getting warm. It switched on after some time. Then I tried Wiping Cache and Dalvik through TWRP and it didn't work as I had the same problem over again. Then I tried flashing another ROM through TWRP and I couldn't complete it as my phone restarted while I tried to flash a new ROM. Then I tried copying my files from phone to USB OTG and that too failed as phone continued to restart. The only option I had is using Fastboot. I downloaded the latest Global ROM MIUI 10 and flashed new ROM using MiFlash. Phone booted perfectly and after I synced my Mi account and Google account the phone switched off again and when I tried to restart it boots up till lockscreen and switches off Immediately.
Again I booted up Xiaomi Recovery as TWRP was now gone and Wiped the ROM and it booted up normally, after few tries I finally didn't sync Mi or Google account and Didn't install anything on phone as it might switch off again. I'm pretty sure it'll switch off again. Other than that I think the device is okay as I'm posting this thread from the same phone. It couldn't be a ROM issue as you can see I've tried different MIUI ROMs even the Custom MIUI ones. What could be the reason for this behavior? I hope someone could help me as it is my main device and this issue is driving me nuts.
Bibin Shree said:
Recently I've encountered a problem on my Redmi Note 3 Pro 3 gb ram 32 gb. I've been using custom ROMs and Kernels for a while. One day my phone switched off after getting warm. It switched on after some time. Then I tried Wiping Cache and Dalvik through TWRP and it didn't work as I had the same problem over again. Then I tried flashing another ROM through TWRP and I couldn't complete it as my phone restarted while I tried to flash a new ROM. Then I tried copying my files from phone to USB OTG and that too failed as phone continued to restart. The only option I had is using Fastboot. I downloaded the latest Global ROM MIUI 10 and flashed new ROM using MiFlash. Phone booted perfectly and after I synced my Mi account and Google account the phone switched off again and when I tried to restart it boots up till lockscreen and switches off Immediately.
Again I booted up Xiaomi Recovery as TWRP was now gone and Wiped the ROM and it booted up normally, after few tries I finally didn't sync Mi or Google account and Didn't install anything on phone as it might switch off again. I'm pretty sure it'll switch off again. Other than that I think the device is okay as I'm posting this thread from the same phone. It couldn't be a ROM issue as you can see I've tried different MIUI ROMs even the Custom MIUI ones. What could be the reason for this behavior? I hope someone could help me as it is my main device and this issue is driving me nuts.
Click to expand...
Click to collapse
Make sure u selected clean flash while flashing fastboot rom including cleaning user storage and internal sd.
Dont encrypt.
Are u rooting ? If rooting use magisk only.... not supersu.
Remove sd card, sim card . clean it. Put back.
If still cant solve....open back cover. Remove both battery connecter and connect again. Charging board flex connector on both end and connect again. Sometimes carbon can create problem.
naik2902 said:
Make sure u selected clean flash while flashing fastboot rom including cleaning user storage and internal sd.
Dont encrypt.
Are u rooting ? If rooting use magisk only.... not supersu.
Remove sd card, sim card . clean it. Put back.
If still cant solve....open back cover. Remove both battery connecter and connect again. Charging board flex connector on both end and connect again. Sometimes carbon can create problem.
Click to expand...
Click to collapse
I've Selected Flash all While Fastboot flashing....Yet I've
Same issue, Boots till lockscreen then screen goes black....Then when I use Mi Recovery to Wipe all it boots up and I can use the phone. But if I try to Open a few apps or try to Sync, phone switches off again. Any way I'll try the cable fix and report here.
Hi, I'm trying using LOS 16 ROM. After I try and I succes.
But I decided to use the official ROM.
Before that I already Backup Full (All options checked using TWRP)
When I restore there's no problem, but once reboot to system I get bootloop in Pocophone logo + unlocked words (Booting - Off - Booting - Off).
Okay, so I try restore it again, now it got past the pochophone logo but it stuck in Pocophone logo + loading screen (where 3 little dot and android words on bottom)
Can someone tell me where I'm wrong?
Closed
Okay, so i try to restore it for the 3rd time while waiting reply there.
And it succed, no bootloop.
(from the 1st restore till 3rd restore i didn't do anything different. Only restore from TWRP. So strange, but at least i got my phone back)
Only the pattern password suddenly got wrong when obviously It's no way to be wrong. Since i have 3 phone and all patern is same :/
I just need to wipe data now. :silly:
seems like /data decryption error
never jump between Miui and LOS roms frequently! miui changes alot of things including OEM (vendor) partitions in latest miui10.2.3 rom! which usually gives BOOTLOOPS and TWRP also CANNOT flash any rom!
I have used the search function, but to no avail. Also, sorry for no log files – cant access them (see below).
I used a work around „Error 7 – Assert failed“ while trying to flash Lineage OS (lineage-16.0-20200104-nightly-kiwi-signed.zip) for my honor 5x (this work around: https://forum.xda-developers.com/showthread.php?t=2522762). I was positive that the .zip i used was for my specific phone and that the twrp was the current one. Even after updating to most recent twrp, the error 7 persisted (I did perform the corrext wipes of storage). After „forcing“ the phone to install the .zip anyway (overriding the assert check with the workaround) , my phone is now bootlooped, or worse (stupid me, i guess). During the first restart after flashing, things seemed fine for a few seconds, the lineage logo started to appear for a short while, but disappeared and now only the honor logo appears. It mostly bootloops. I can still access fastboot mode and, with a little luck, also recovery, but touch screen isnt working. Some fastboot commands work, but some do not seem to work, although i am not very experienced with fastboot and cant tell for sure. I have a nandroid backup available.
My questions: How to save the phone? I would be happy to return to stock for now, just to sort things out from there. I couldnt execute most guides to return to stock, since i have no access to twrp (touchscreen no longer reactive). I‘m happy for all ideas.
My firmware KIW-L21C432B160