Hi,
I have an unlocked bootloader on the XT1521, with TWRP and Cyanogenmod 13.0 installed. I just updated CM via OTG, which worked correctly, but all Google Apps were removed. When I tried to flash them afterwards, nothing happened.
So I went on and wanted to wipe /system to reinstall CM and GAppsbut apparently, my /system partition is "busy" and cannot be unmounted. I get this error all the time, regardless if I try to a) uncheck the "mount system partition read-only" and swipe to allow modifications, b) try to unmount it manually via the mount menu, c) try to wipe it (the "repair" option is not available for \system unlike for /data, e.g.), d) try to flash CM13.0 zip. The error message is always like "failed to unmount '/system' (Device or resource busy)" and, oddly, I did not find any similar issue via Google, as it is not just a "read-only"-related problem.
Does anybody have a solution to that issue? Thanks!
Alex
alexounet2 said:
Hi,
I have an unlocked bootloader on the XT1521, with TWRP and Cyanogenmod 13.0 installed. I just updated CM via OTG, which worked correctly, but all Google Apps were removed. When I tried to flash them afterwards, nothing happened.
So I went on and wanted to wipe /system to reinstall CM and GAppsbut apparently, my /system partition is "busy" and cannot be unmounted. I get this error all the time, regardless if I try to a) uncheck the "mount system partition read-only" and swipe to allow modifications, b) try to unmount it manually via the mount menu, c) try to wipe it (the "repair" option is not available for \system unlike for /data, e.g.), d) try to flash CM13.0 zip. The error message is always like "failed to unmount '/system' (Device or resource busy)" and, oddly, I did not find any similar issue via Google, as it is not just a "read-only"-related problem.
Does anybody have a solution to that issue? Thanks!
Alex
Click to expand...
Click to collapse
Hey i had this issue and finally pinned it down to the TWRP I was using. It turns Official TWRP has this issue. This can easily be resolved if u flash Squid's TWRP
Download the latest version from here:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
That was the problem apparently. Thank you!
Thank you! I was having this problem as well and that fixed it.
Thanks very much for your help!!!
I was scared of loosing my phone...
Thanks.
I have a US Cellular XT1526 and was unable to install GApps on CM13 without this. CM13 installed fine, and GApps looked like it installed, but on reboot nothing was there; GApps failed to install. Using Squid's TWRP fixed it; thanks!
ayush rao said:
hey i had this issue and finally pinned it down to the twrp i was using. It turns official twrp has this issue. This can easily be resolved if u flash squid's twrp
download the latest version from here:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
Click to expand...
Click to collapse
thank you so much :d
thank you buddy.....
my mother is using Motorola E 2nd gen LTE and i flashed it with cyanogenmod 13 used officialTWRP recovery... and i faced the same problem. thank you very much for your answer and also the other guy for asking the question.
Should I select boot or recovery as partition when flashing this img
cannot restore system mounted read only
Related
Good Morning All...
I'll try to provide as much relevant information as possible while being concise. That being said, let me know if I need to provide addition information.
Basics
Computer OS: Mac + Windows 7 VM and a Windows 7 dedicated machine.
Phone: HTC EVO 4G LTE
Carrier: Sprint
Current ROM: CM10-20120904-NIGHTLY-jewel
Goal
To restore "normal" flashing functionality (detailed below) so I can restore to stock.
Details
My first issue with this phone started on the 4.0.x version of Android that came with the phone. The phone would frequently reboot, at which point it would indicate an error report could be sent to HTC. I sent these faithfully for several weeks. Then an update for the phone was released and I updated OTA. This did not solve the rebooting issue.
At that point, I grew frustrated and decided I would root the phone and install CM10 in the hopes the rebooting issue would be resolved. I rooted the phone with S-ON using the method outlined on HTVEVOHacks.
I was able to push TWRP to the phone and then proceeded to download and install CM10 via Clockwork. After installing Clockwork, I installed Clockwork recovery (I had worked with it previously on my EVO 4G, and wasn't familiar with TWRP) and tried to install CM10. This failed and I pushed TWRP once more and booted into the phone.
I then installed GooManager, at which point I downloaded and successfully installed CM10. This is essentially where I'm at now.
Issues
I've had several issues with CM10, including the phone rebooting (still), and have decided I would like to restore to stock. The issues outlined below comprise all of the trouble I've experienced and is currently impeding my progress:
If I flash a ROM other than the CM10 backup I have, or MIUI, it sits in boot spinning indefinitely (>25-minutes). I've cleared the fastboot cache, as well as the dalvik/cache in an attempt to boot it properly. I've tried MeanROM and a few other Sense-based ROMS (inc. stock-rooted ROMs).
If I try to run the RUU (I've tried several versions), it gets to the point where the HTC logo appears in silver, and then the RUU tells me I have the wrong version.
MIUI proved to be a very poor choice, as I was inundated with error after error (com.phone.android).
If I restore the stock recovery, and perform an oemlock, the bootloader shows 'Tampered - Relocked - Security Warning'.
When in TWRP, any time I try to wipe cache/factory reset, it gives an error: "E:failed to mount /sdcard (Invalid argument)". This appears numerous times throughout the TWRP log (which I can copy to SD, but I can't mount to USB).
At this point, I'd like to be able to take it back to Sprint as I believe the rebooting to be an issue with the phone, but I need to be able to restore back to stock, if possible.
I know this is a long post, but being an engineer, I like to make sure I do as much footwork as possible prior to asking for help. If there are any steps I haven't taken that I should have, please tell me and I'll be happy to do it.
Any help that can be provided is welcome.
Regards,
JadoJodo
Sounds like you need to fast boot flash a sense kernel before flashing a sense ROM.
I'll admit I didn't read all your post but you should check out the thread named " don't panic"
All your answers should be there
Sent from my EVO using xda app-developers app
corcgaigh said:
Sounds like you need to fast boot flash a sense kernel before flashing a sense ROM.
I'll admit I didn't read all your post but you should check out the thread named " don't panic"
All your answers should be there
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I had taken a look at that yesterday and didn't see a guide that matched my issues specifically, but having looked at it again today, I see some relevant info. My question: Where do I get a Sense-based kernel to flash? Is there a specific one I should flash?
JadoJodo
Having reviewed the "Don't Panic" guide by om4, I attempted to solve the sdcard mount issue by reformatting in TWRP. I get the following error:
Code:
* Verifying filesystems...
* Verifying partition sizes...
E:failed to mount /sdcard (Invalid argument)
E:failed to mount /sdcard (Invalid argument)
E:failed to mount /sdcard (Invalid argument)
E:Unable to open ums lunfule 'sys/class/android_usb/android0/f_mass_sto
Using rm -rf on '/dev/block/mmcblk0p38'
E: tw_format_rmfr: unable to locate volume for device "/dev/block/mmcblk0
Mount twrp to pc and reformat
om4 said:
Mount twrp to pc and reformat
Click to expand...
Click to collapse
Thanks for the reply, om4!
I was able to mount the Internal Storage to my PC and format. Once this was done, I found it could be mounted in TWRP, however, using the 'Wipe' function in TWRP to wipe 'Internal Storage' still fails. I am unsure if this functionality is normal, but I can access the Internal Storage when mounted via Windows now.
I am reformatting System, Cache, Dalvik, and reinstalling CM10 once more to test functionality...
First of all, this is my first post on this forum, so I'd like to say hello to everybody.
I made a bit of a mess with my father's phone (it was mine before he had it, so it was already modded), and the explanation will be somewhat long because I tried everything before coming here for help.
This phone had Android 5.1.1 Lollipop, installed through the official Cyanogenmod 12.1 Nightlies. It was working perfectly, but I wanted to install more Gapps on the /system partition and switch some of the original Cyanogenmod apps with the corresponding Google apps. I used Deltadroid's modular Gapps (Thread here: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368) to install everything I needed on the /system partition, but I only did a factory reset+cache wipe instead of wiping the /system partition too and starting from scratch, because I couldn't find the option to wipe the /system partition in the "stock" Cyanogen Recovery. Now the phone will boot, enter recovery mode and even get to the setup screen, but as soon as the Google Play Services are needed, they crash and the setup won't go on. I tried installing the CWM but the signature check fails every time, I tried using ADB but I'm no expert and I don't know how to make it work, I tried reinstalling the ROM and wiping /data and /cache once again to no avail, I tried basically everything but it seems the only thing that can be done is wiping the /system partition and reinstalling both the ROM, the Gapps and the add-ons.
The problem is, I have no idea how to wipe the /system partition, so I was wondering if anyone here could help.
Thanks in advance.
Hi @Valtekken
You just need to have a "signed" .zip to flash through that recovery. Try the philz 6.48.4 attached here. I have heard of a few people not being able to flash this one, if it doesn't install, use the other one first, reboot to recovery, and then flash 6.48.4. So -
1. Flash the philz recovery
2. Reboot to recovery, not system
2a. (Flash the other one, reboot to recovery [if you used XWMS3 first])
3. Do your wipes(you should only need to wipe /system if you want to keep your data, but I always recommend a clean install if possible - /data, /cache, and dalvik/art cache as well)
4. Install the new CM12.1 and gapps
BTW the gapps you can flash will depend on whether or not you have repartitioned. If you have stock /system partition just install a pico or minimal gapps
noppy22 said:
Hi @Valtekken
You just need to have a "signed" .zip to flash through that recovery. Try the philz 6.48.4 attached here. I have heard of a few people not being able to flash this one, if it doesn't install, use the other one first, reboot to recovery, and then flash 6.48.4. So -
1. Flash the philz recovery
2. Reboot to recovery, not system
2a. (Flash the other one, reboot to recovery [if you used XWMS3 first])
3. Do your wipes(you should only need to wipe /system if you want to keep your data, but I always recommend a clean install if possible - /data, /cache, and dalvik/art cache as well)
4. Install the new CM12.1 and gapps
BTW the gapps you can flash will depend on whether or not you have repartitioned. If you have stock /system partition just install a pico or minimal gapps
Click to expand...
Click to collapse
First of all, thank you for answering!
I tried many "-signed" .zips, but none of them worked, so I'll assume I used non-compatible ones. There was space for the Gapps on the /system partition, mainly because I made sure of getting only the Gapps and the few addons I needed, so the MB count was very low.
I'll try your recovery right now and let you know in a moment, hopefully this solves the problem and I can have the phone working again.
Managed to install the recovery, format the /system, /data and /cache partitions, install the rom, the Gapps and the add-ons. It worked, but the phone still gives me an "Unfortunately, Google Play Services has stopped". How can I get the apps to work? What could the problem be?
I solved the problem, finally...I changed the Gapps package (I used TK's Gapps) and managed to install it and make everything work.
Thanks for all your help! I think the thread can be closed now.
I'm trying to do a full wipe, or factory reset on my Moto E 2015 with TWRP 3.0.2 to get a clean install of a previous Cyanogenmod nightly that didn't cause problems with Google Apps (but that's another story). When I enter TWRP recovery and choose Wipe, it says "Factory Reset Complete - Successful" on the top, but when it gives information about what is happening on the bottom in red letters it says "Unable to mount storage". I did take out my external SD card before this because it has my ROM and Gapps zips on it.
When I go into "Advanced Wipe" and select all the partitions except Micro SD card, it says "Wipe Complete - Failed", and in red letters "failed to unmount /system (device or resource busy) , unable to wipe /system, unable to mount storage".
Before all of this I uninstalled Google Play Services and my Google App because of the "google play services stopped" error, then tried to restore using Titanium backup but it was saying "ten elements failed." That's my reason for trying to wipe everything and start fresh.
So having said all that, I can easily flash my ROM and Gapps again, but I'm concerned about these errors. I'm new at this and am very interested in finding out if I did something wrong.
DaveMacD said:
I'm trying to do a full wipe, or factory reset on my Moto E 2015 with TWRP 3.0.2 to get a clean install of a previous Cyanogenmod nightly that didn't cause problems with Google Apps (but that's another story). When I enter TWRP recovery and choose Wipe, it says "Factory Reset Complete - Successful" on the top, but when it gives information about what is happening on the bottom in red letters it says "Unable to mount storage". I did take out my external SD card before this because it has my ROM and Gapps zips on it.
When I go into "Advanced Wipe" and select all the partitions except Micro SD card, it says "Wipe Complete - Failed", and in red letters "failed to unmount /system (device or resource busy) , unable to wipe /system, unable to mount storage".
Before all of this I uninstalled Google Play Services and my Google App because of the "google play services stopped" error, then tried to restore using Titanium backup but it was saying "ten elements failed." That's my reason for trying to wipe everything and start fresh.
So having said all that, I can easily flash my ROM and Gapps again, but I'm concerned about these errors. I'm new at this and am very interested in finding out if I did something wrong.
Click to expand...
Click to collapse
How did you install twrp? Try using fastboot method and make sure to use twrp 3.0
Change with v 3.0.2-1....that problem fixed....
Sent from my Redmi Note 2 using XDA Free mobile app
alv09012013 said:
How did you install twrp? Try using fastboot method and make sure to use twrp 3.0
Click to expand...
Click to collapse
I installed TWRP by fastboot.
But now I've just been told to use two different versions of TWRP. First 3.0 and second 3.0.2-1
My current version is 3.0.2 which according to TWRP's website is the most recently supported version for my surnia (Moto E 2015)
I know 3.0.0 is supported because it's older but I don't see any downloads for 3.0.2-1
Should I revert back to the old 3.0 or risk using a version that says it's not supported yet?
Thanks for advice.
Hey man, this should be a good link http://forum.xda-developers.com/showthread.php?p=61406133 to Squids TWRP latest are there. I'm running the latest 3.02 and found when I upgraded my modem as well (to 6.0) I've had great success with TWRP.
Sent from my XT1527 using XDA-Developers mobile app
I had that same problem, usually after a dirty flash or making kernel tweaks, but a clean flash of the recovery.img (plus modem for me) usually does it. Then I do wipe just to be sure! ?
DaveMacD said:
I installed TWRP by fastboot.
But now I've just been told to use two different versions of TWRP. First 3.0 and second 3.0.2-1
My current version is 3.0.2 which according to TWRP's website is the most recently supported version for my surnia (Moto E 2015)
I know 3.0.0 is supported because it's older but I don't see any downloads for 3.0.2-1
Should I revert back to the old 3.0 or risk using a version that says it's not supported yet?
Thanks for advice.
Click to expand...
Click to collapse
I used 3.0 and I had no problems with it. The only trouble I had was updating stock ROM when boost released an update last week but I went in and edited the script and fixed that issue. But I just updated to 3.0.2-r1 and can confirm it does indeed work. Here is the direct download link http://forum.xda-developers.com/devdb/project/dl/?id=17768&task=get
izzen42 said:
Change with v 3.0.2-1....that problem fixed....
Sent from my Redmi Note 2 using XDA Free mobile app
Click to expand...
Click to collapse
alv09012013 said:
I used 3.0 and I had no problems with it. The only trouble I had was updating stock ROM when boost released an update last week but I went in and edited the script and fixed that issue. But I just updated to 3.0.2-r1 and can confirm it does indeed work. Here is the direct download link http://forum.xda-developers.com/devdb/project/dl/?id=17768&task=get
Click to expand...
Click to collapse
Thanks a lot you guys. After updating to 3.0.2-r1 all my partitions finally got wiped, and all the errors went away. I'll try that kernel from Squid too after my poor head stops spinning after two days of battling through this haha but it's fun to learn. I really appreciate everyone's help.
Hi
I have a problem with my Mi5s plus.
I have updated my rom.
I can boot with my custom rom I just installed. It is ok. I can browse the directories with the file manager. I can use the stock browser, SMS...ok
But when I want to install GAPPS (That I downloaded before)(I know it's no longer called that) with TWRP, I no longer see the installation file, the ZIP. The directories are empty with TWRP but accessible and with files with the Android file manager.
So I can't install applications without open apps.
Of course, when I want, by example, to delete cache I have theses messages : unable to mount /data (invalid argument), error 8 etc.
Help me?
I hope to be able to recover the data so that when I reinstall my applications. I have the data.
Thank you again.
Djoul33 said:
Hi
I have a problem with my Mi5s plus.
I have updated my rom.
I can boot with my custom rom I just installed. It is ok. I can browse the directories with the file manager. I can use the stock browser, SMS...ok
But when I want to install GAPPS (That I downloaded before)(I know it's no longer called that) with TWRP, I no longer see the installation file, the ZIP. The directories are empty with TWRP but accessible and with files with the Android file manager.
So I can't install applications without open apps.
Of course, when I want, by example, to delete cache I have theses messages : unable to mount /data (invalid argument), error 8 etc.
Help me?
I hope to be able to recover the data so that when I reinstall my applications. I have the data.
Thank you again.
Click to expand...
Click to collapse
In TWRP, go to mount and see if data is mounted.
No, it is not mounted in TWRP (But, in Android, it is OK, il see my datas)
But, I can just check :
DSP
System
Cache
Cust
Persist
But I am not able to check
Data
USB OTG.
it is locked.
Djoul33 said:
No, it is not mounted in TWRP (But, in Android, it is OK, il see my datas)
But, I can just check :
DSP
System
Cache
Cust
Persist
But I am not able to check
Data
USB OTG.
it is locked.
Click to expand...
Click to collapse
I have flashed things that did not properly unmount a partition afterwards so I could not mount it in twrp. Try flashing something that mounts data, if not mounted, then unmounts data properly.
Maybe my TWRP is deprecated ?
I have flashed a ROM 8.x then, my TWRP is old : 3.0.2.x By XM maybe ?
2016...
Djoul33 said:
Maybe my TWRP is deprecated ?
I have flashed a ROM 8.x then, my TWRP is old : 3.0.2.x By XM maybe ?
Click to expand...
Click to collapse
Try that first.
Hi,
My TWRP was too old, deprecated. It is OK now.
Thanks.
running on 4.2.2 stock rom GT-i9060 rooted, twrp 3.02 and unlocked bootloader with ez-unlock (fastboot isnt working)
steps I used to flash the ROM:
1. flashing stock rom and getting root
2. enable USB debugging and unlocking bootloader
3. wiping cache, dalvik cache and data, 2nd time tried wiping cache, dalvik cache, data and system, 3rd time wiped cache, dalvik cache, data and added format script to update-script before mounting and extracting files (internal storage was never included because it doesn't make a difference)
4. flashing both of the ROM and gapps
the rom is made for my phone and i'm certain of it if i'm gonna be asked about it (GT-i9060 Baffinlite)
5. Wiping dalvik cache, cache and data
been more than a week working on flashing this rom but all goes back to the bottom
tried removing the assert line
added execute permissions to the zip, didn't make a difference
recovery version is 3.0.2 and tried twrp 2.7, twrp 2.8 and cwm 5.06 but the one the rom developer asked to use wasn't booting but kept powering the phone off after showing device logo, it's on the attachements
after getting error 7 couple of times without editing anything then i tried editing updater-script myself by changing the mount order but i guess the previous is the one used on every lineage rom so that failed too
there's a cm11 rom for the dvice working but full of bugs so what i'm not getting is why the lineage 16 one isn't mounting at all although the other one do
"detected filesystem ex4 for /dev/block/mmcblk0p17
mount: failed to mount /dev/block/mmcblk0p17 at /system"
that comes right after the extracting packages script (system.new.dat.br
ticking the system on twrp gives on log: can't mount system (invalid argument)
there is enough space on system for the rom too
i'm also sure that the system block is "mmcblk0p17" because it worked with the other ROM
the gapps mentioned that the android veriob I am using after installing the ROM is 5.1 (SDK 22) not 9.0 but I ignored it after checking the build.prop inside the system img
im ready for testing if there's a dev getting a solution
I know there would be lots of bugs by running pie on that phone because of the specifications but im okay with it
if someone could fix the mounting ROM bug or tell me if there is something i missed about flashing
Rom by knuxfanwin8
(androidfilehost.com/?fid=6006931924117889489)
Recovery by made_in_androland
(androidfilehost.com/?fid=457095661767119752)
NOT-Working recovery by knuxfanwin8
(androidfilehost.com/?fid=6006931924117902394)
I have the same problem, please give we a solution!
---------- Post added at 10:19 AM ---------- Previous post was at 10:10 AM ----------
Azureus. said:
running on 4.2.2 stock rom GT-i9060 rooted, twrp 3.02 and unlocked bootloader with ez-unlock (fastboot isnt working)
steps I used to flash the ROM:
1. flashing stock rom and getting root
2. enable USB debugging and unlocking bootloader
3. wiping cache, dalvik cache and data, 2nd time tried wiping cache, dalvik cache, data and system, 3rd time wiped cache, dalvik cache, data and added format script to update-script before mounting and extracting files (internal storage was never included because it doesn't make a difference)
4. flashing both of the ROM and gapps
the rom is made for my phone and i'm certain of it if i'm gonna be asked about it (GT-i9060 Baffinlite)
5. Wiping dalvik cache, cache and data
been more than a week working on flashing this rom but all goes back to the bottom
tried removing the assert line
added execute permissions to the zip, didn't make a difference
recovery version is 3.0.2 and tried twrp 2.7, twrp 2.8 and cwm 5.06 but the one the rom developer asked to use wasn't booting but kept powering the phone off after showing device logo, it's on the attachements
after getting error 7 couple of times without editing anything then i tried editing updater-script myself by changing the mount order but i guess the previous is the one used on every lineage rom so that failed too
there's a cm11 rom for the dvice working but full of bugs so what i'm not getting is why the lineage 16 one isn't mounting at all although the other one do
"detected filesystem ex4 for /dev/block/mmcblk0p17
mount: failed to mount /dev/block/mmcblk0p17 at /system"
that comes right after the extracting packages script (system.new.dat.br
ticking the system on twrp gives on log: can't mount system (invalid argument)
there is enough space on system for the rom too
i'm also sure that the system block is "mmcblk0p17" because it worked with the other ROM
the gapps mentioned that the android veriob I am using after installing the ROM is 5.1 (SDK 22) not 9.0 but I ignored it after checking the build.prop inside the system img
im ready for testing if there's a dev getting a solution
I know there would be lots of bugs by running pie on that phone because of the specifications but im okay with it
if someone could fix the mounting ROM bug or tell me if there is something i missed about flashing
Rom by knuxfanwin8
(androidfilehost.com/?fid=6006931924117889489)
Recovery by made_in_androland
(androidfilehost.com/?fid=457095661767119752)
NOT-Working recovery by knuxfanwin8
(androidfilehost.com/?fid=6006931924117902394)
Click to expand...
Click to collapse
I have The same problem, please help me.
I have the galaxy grand neo and i try to install lineage os 16.0 but not work, i have read in a thread that the problem will be the bootloader (its version is too old)
In the post it was written to update the bootloader but for the galaxy grand neo the only one verison of android is 4.2.2.
Maybe i'm wrong, i'm not a pro but i can understand somethings.
Hey any one there?????¿?
Please post a quick reply to help three of us from this drastical problem..........??????
Error 7 occurs when there is not enough space for flashing gapps or rom in system. Can you resize system partition from twrp?
kouseralamin said:
Error 7 occurs when there is not enough space for flashing gapps or rom in system. Can you resize system partition from twrp?
Click to expand...
Click to collapse
Tried but nothing
kouseralamin said:
Error 7 occurs when there is not enough space for flashing gapps or rom in system. Can you resize system partition from twrp?
Click to expand...
Click to collapse
Androcomtweaker said:
Tried but nothing
Click to expand...
Click to collapse
TWRP doesn't give you option Resize Partition but only option Resize File System - what is nothing else than expanding the related FS to reclaim wasted space.