TWRP won't wipe "/system" - E 2015 Q&A, Help & Troubleshooting

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.

Related

[Q] Can't load ROM's with fakeCID ulock?

Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
rudyo78427 said:
Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
Click to expand...
Click to collapse
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
also, you need to be on software 2.17.605.2-which I assume you are to be unlocked
Aldo101t said:
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
Click to expand...
Click to collapse
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
yes the zip needs to be on ext-sdcard not the internal card.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
rudyo78427 said:
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
Click to expand...
Click to collapse
what version of twrp are you using-the is an official twrp 2.4.3 now
http://techerrata.com/file/twrp2/fireball/openrecovery-twrp-2.4.3.0-fireball.img
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
rudyo78427 said:
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
there is an option under wipe for system.
---------- Post added at 01:16 PM ---------- Previous post was at 01:10 PM ----------
Aldo101t said:
rudyo78427 said:
there is an option under wipe for system.
Click to expand...
Click to collapse
you should wipe data/factory reset--wipe cache--wipe dalvic--wipe system then install rom
Click to expand...
Click to collapse
Click to expand...
Click to collapse
rudyo78427 said:
...I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen...
Click to expand...
Click to collapse
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Atomic83 said:
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Click to expand...
Click to collapse
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Success!!!
rudyo78427 said:
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Click to expand...
Click to collapse
Success!!!!! Thanks for the last tip to try a lower recovery version. Seems TWRP 2.4 on up didn't work allowing the Aroma Installer to complete installation. I have downgraded to twrp version 2.3.3.0 and the ROM's flash now. Thank you XDA community!!! :laugh:
rudyo78427 said:
... I erase every thing 3x as stated in various posts ....
Click to expand...
Click to collapse
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Edit: TWRP 2.4.3.0 and newer seem to have trouble with Aroma
mdmower said:
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Click to expand...
Click to collapse
Thanks for the feedback, mdmower. I had done a complete format of my sd card on the comp and loaded only the zip file on the card. I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe. All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully. I have since flashed Pizzuto claw's and now running ViperLTE. I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
rudyo78427 said:
I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe.
Click to expand...
Click to collapse
First thing, drop this habit. A single factory reset will suffice.
rudyo78427 said:
All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully.
Click to expand...
Click to collapse
Issues with aroma and TWRP versions 2.4.3.0 and greater have been confirmed (possibly other 2.4.x releases). The folks behind TWRP suspect a problem with make_ext4fs, but it is unclear whether the blame lies within TWRP, the update_binary, or the particular make_ext4fs called by Aroma.
rudyo78427 said:
I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
Click to expand...
Click to collapse
Read the first post in the CM thread. Others have successfully used CM outside the U.S.

Really weird wifi problem and mmcblk0p37 error

When I'm on the old CM10.1 ROM, my Rezound detects and connects to my house's wifi and other wifi sources with [seemingly] no problem, and I can access the web pages on chrome when I'm connected to wifi on the old CM10.1 ROM. However, when I flashed to CM10.1.2, and I'm on the starting set up page, trying to connect to a wifi, no wifi source ever pops up, even when my house's wifi is on and there are usually 1-2 other wifi sources in my area that should also pop up. I wait for over 10 minutes, and still no wifi source appears on the starting set up page for cm10.1.2. Additionally, now, when I'm on the old CM10.1 ROM, I can't download any updates or new apps from the play store at all. I was able to download google drive on my rezound only a week ago.
Anyways, the recovery I use is AMON RA-VIGOR-v3.16, and I noticed in amon ra that when I try "Wipe ALL data/factory reset", I get this:
Wipe ALL userdata
Press Power to confirm,
any other key to about.
Formatting DATA:...
Formatting SDCARD:.android_secure...
Formatting INTERNALSD:.android_secure...
E:Can't mount /dev/block/mmcblk0p37 (or /dev/block/mmcblk0p38)
(Invalid argument)
Error mounting /internal_sdcard/.android_secure!
Skipping format...
Formatting CACHE:...
Skipping format of /sd-ext.
Userdata wipe complete!
And that's it. What does this mean? just a couple days ago was the first time I flashed a new ROM on my Rezound for a month, and I think this "error mounting internal_sdcard/.android_secure" started when I flashed the first new ROM in a month. Is there anyway to fix this error and problem? I would really like to keep my Rezound and not have to buy a new phone... I would be happy to provide additional information if it would help solve this problem.
urstinky said:
When I'm on the old CM10.1 ROM, my Rezound detects and connects to my house's wifi and other wifi sources with [seemingly] no problem, and I can access the web pages on chrome when I'm connected to wifi on the old CM10.1 ROM. However, when I flashed to CM10.1.2, and I'm on the starting set up page, trying to connect to a wifi, no wifi source ever pops up, even when my house's wifi is on and there are usually 1-2 other wifi sources in my area that should also pop up. I wait for over 10 minutes, and still no wifi source appears on the starting set up page for cm10.1.2. Additionally, now, when I'm on the old CM10.1 ROM, I can't download any updates or new apps from the play store at all. I was able to download google drive on my rezound only a week ago.
Anyways, the recovery I use is AMON RA-VIGOR-v3.16, and I noticed in amon ra that when I try "Wipe ALL data/factory reset", I get this:
Wipe ALL userdata
Press Power to confirm,
any other key to about.
Formatting DATA:...
Formatting SDCARD:.android_secure...
Formatting INTERNALSD:.android_secure...
E:Can't mount /dev/block/mmcblk0p37 (or /dev/block/mmcblk0p38)
(Invalid argument)
Error mounting /internal_sdcard/.android_secure!
Skipping format...
Formatting CACHE:...
Skipping format of /sd-ext.
Userdata wipe complete!
And that's it. What does this mean? just a couple days ago was the first time I flashed a new ROM on my Rezound for a month, and I think this "error mounting internal_sdcard/.android_secure" started when I flashed the first new ROM in a month. Is there anyway to fix this error and problem? I would really like to keep my Rezound and not have to buy a new phone... I would be happy to provide additional information if it would help solve this problem.
Click to expand...
Click to collapse
try switching to twrp and erasing in that recovery, you can switch back to amon ra right after that if you want to http://forum.xda-developers.com/showthread.php?t=1902381
most mounting errors are fixed by either switching to a different recovery to reformat/partition the partitions (amon ra is a bit outdated, i used it in the past and and got mounting errors to. mostly after RUU and tried to install a ROM right away)
they can be fixed by running the RUU again, if you still get mounting error in amon ra after the RUU than all you have to do is reboot into the stock ROM and unmount and erase the sdcard in the storage settings than go back to recovery and it should be fixed
bunchies said:
try switching to twrp and erasing in that recovery, you can switch back to amon ra right after that if you want to http://forum.xda-developers.com/showthread.php?t=1902381
most mounting errors are fixed by either switching to a different recovery to reformat/partition the partitions (amon ra is a bit outdated, i used it in the past and and got mounting errors to. mostly after RUU and tried to install a ROM right away)
they can be fixed by running the RUU again, if you still get mounting error in amon ra after the RUU than all you have to do is reboot into the stock ROM and unmount and erase the sdcard in the storage settings than go back to recovery and it should be fixed
Click to expand...
Click to collapse
Thank you, bunchies. I never heard of TWRP prior to your response, so I appreciate it. I flashed TWRP version 2.6.0.0 with no problem and did the standard wipe first, which gave me an error and said it failed to wipe. So I went to the advanced settings in wipe and checked all tick boxes except the 'wipe ext sd' check box, and it was successful! I did it 2 more times to try to make sure it was successful. I decided to try to install the July 12 2013 build of CM10.1.2, and then the GSM patch and gapps, but it came out with the same problem of not recognizing any wifi sources within the vicinity like 2 days ago. When I downloaded CM10.1.2 2 days ago, I made sure to check its md5 sum, and it was equal to the one provided. Then I modified it by replacing its mms.apk, copied the resulting ROM to my rezound's root, and checked each others md5 sums, which where again equal. So I flashed amon ra v3.16 again and wiped everything and this time I didn't encounter ANY mounting error. I NAND restored my old back up of cm10.1 and tried to download google drive from google play....but it didn't work again...The error message I get in google play is this:
"Google Drive" could not be downloaded due to an error. (Error retrieving information from server. [RPC:S-5:AEC-0])
When I try to download Rezound Prox Sensor Calibrator, the same exact error message pops up (except inside the quotation marks in Rezound Prox Sensor Calibrator). And still, browsing the web on google chrome works like it should.... what can I do next to try to fix my rezound?
*edit* nevermind about the google play store problem. I went to settings>apps>all, cleared the cache of "google play store" and force stopped it, and cleared the data of both "google play services" and "google services framework" and force stopped both (though I've read that I probably don't have to do all that to google play services). I rebooted and for some reason, I can download and update from google play again. The problem of wifi not ever being recognized for me after I flash to the July 12 2013 build of CM10.1.2 still exists, though.
urstinky said:
So I flashed amon ra v3.16 again and wiped everything and this time I didn't encounter ANY mounting error. I NAND restored my old back up of cm10.1
Click to expand...
Click to collapse
Was this nand backup made during the time of mounting error, or during the time of the wifi problem?
the DATA folder may be corrupted in some way, i have had an issue before where i had a problem with my current rom than did a nand backup of just my data folder because the data folder holds things like apps/setting and other stuff which i didnt want to loose in my new flash but something in there can be corrupted. but after i would re-install the rom and did a nand restore of the DATA folder i would get the same issue in the new flash.
so if you did something like that it could be messing with your wifi
if you did something like that and you have time maybe just do a Nand backup of what you have now. than factory reset/wipe boot/data/system/caches and install the rom again without restoring anything and see if the wifi works as intended
if that makes any sense.. :silly:
bunchies said:
Was this nand backup made during the time of mounting error, or during the time of the wifi problem?
the DATA folder may be corrupted in some way, i have had an issue before where i had a problem with my current rom than did a nand backup of just my data folder because the data folder holds things like apps/setting and other stuff which i didnt want to loose in my new flash but something in there can be corrupted. but after i would re-install the rom and did a nand restore of the DATA folder i would get the same issue in the new flash.
so if you did something like that it could be messing with your wifi
if you did something like that and you have time maybe just do a Nand backup of what you have now. than factory reset/wipe boot/data/system/caches and install the rom again without restoring anything and see if the wifi works as intended
if that makes any sense.. :silly:
Click to expand...
Click to collapse
The nand backup I'm using right now was a backup I saved over a month ago (in June 6). The nand backup I made 2 days ago I think was corrupted (though i don't remember what it did anymore...I didn't think it was important at the time...), so I deleted it. In any case, every time I flashed the new rom, I never nand restored the "DATA" part. I didn't even know you can do that! Is DATA also where all text messages are saved? Anyways...nope, I haven't been nand restoring DATA after flashing the new ROM. I even tried flashing CM10.1.2 by itself without the gapps and gsm patch, but it still didn't recognize any wifi in the area.
urstinky said:
The nand backup I'm using right now was a backup I saved over a month ago (in June 6). The nand backup I made 2 days ago I think was corrupted (though i don't remember what it did anymore...I didn't think it was important at the time...), so I deleted it. In any case, every time I flashed the new rom, I never nand restored the "DATA" part. I didn't even know you can do that! Is DATA also where all text messages are saved? Anyways...nope, I haven't been nand restoring DATA after flashing the new ROM. I even tried flashing CM10.1.2 by itself without the gapps and gsm patch, but it still didn't recognize any wifi in the area.
Click to expand...
Click to collapse
Yeah data holds just about everything user end. this guy is having WiFi problems on 10.1.2 to http://forum.xda-developers.com/showthread.php?p=43605690
Just an observation
Edit: if a clean flash of ROM/gapps didn't work it could either be the ROM has a broken driver or hardware. Could be something els to but not sure, you can keep an eye on that thread to see if he gets his problem fixed if you want
Sent from my ADR6425LVW using xda app-developers app
Was the problem pinned down or resolved? I'm on an SIII, but experiencing a very similar problem.

CM13.0/TWRP - Unable to unmount system in recovery

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

[URGENT] Phone stuck on Just a Sec screen, HELP !

I am using Redmi Note 4 SD625. I was easily running AEX {9.0}, without any problems.
I decided to switch to HavocOS. After installing the zip, and also Gapps {pico}, my phone got stuck on Just a Sec screen after Language Selection. I already tried using different ROMS, clearing Internal Storage, Formatting Data using TWRP, but nothing is working. I really need to get this device going. Please Help. Also, my phone's system UI keeps crashing while on Just a Sec Screen [ black screen and then instant refresh of notification panel]. Is this something to do with my gaps? Please help.:crying:
Sp_3ctr_3 said:
I am using Redmi Note 4 SD625. I was easily running AEX {9.0}, without any problems.
I decided to switch to HavocOS. After installing the zip, and also Gapps {pico}, my phone got stuck on Just a Sec screen after Language Selection. I already tried using different ROMS, clearing Internal Storage, Formatting Data using TWRP, but nothing is working. I really need to get this device going. Please Help. Also, my phone's system UI keeps crashing while on Just a Sec Screen [ black screen and then instant refresh of notification panel]. Is this something to do with my gaps? Please help.:crying:
Click to expand...
Click to collapse
You need the following GApps: ARM64 - Android 9.0
https://github.com/opengapps/arm64/releases/download/20190608/open_gapps-arm64-9.0-pico-20190608.zip
Noter2017 said:
You need the following GApps: ARM64 - Android 9.0
Click to expand...
Click to collapse
Already using this gapps. Tried stock build too. Dont know what is going wrong. If i call on my number, the phone app has stopped dialogue box appears.
Sp_3ctr_3 said:
Already using this gapps. Tried stock build too. Dont know what is going wrong. If i call on my number, the phone app has stopped dialogue box appears.
Click to expand...
Click to collapse
Just try it once more.
1. Update your TWRP. Use OrangeFox 9 which you can find here. Boot into your recovery and install OrangeFox:
https://forum.xda-developers.com/re...-orangefox-recovery-project-t3775933?&ampcf=1
2. Update your firmware. Most people prefer firmware 9.6.1.0 which you can find here. Just flash it in OrangeFox recovery:
https://sourceforge.net/projects/xi..._V9.6.1.0.NCFMIFD_2ffa61cdd6_7.0.zip/download
3. Download the ROM and GApps you want to use and save them to your SD card.
4. Boot into recovery and make all the necessary wipes (Internal, Data etc) and also format "Data". You will have to type "YES"
5. Install the ROM you want to use, install GApps and reboot your phone
Noter2017 said:
3. Download the ROM and GApps you want to use and save them to your SD card.
Click to expand...
Click to collapse
I have a hybrid slot so i dont use SD Card. Should i get one for this process or go ahead with internal storage? I do have a SD card.
Sp_3ctr_3 said:
I have a hybrid slot so i dont use SD Card. Should i get one for this process or go ahead with internal storage? I do have a SD card.
Click to expand...
Click to collapse
You can use internal storage as well.
After you do all the wipes, you will need a computer and can then copy the ROM and GApps to internal storage.
Using a SD card, you won't need a computer.
Noter2017 said:
You can use internal storage as well.
After you do all the wipes, you will need a computer and can then copy the ROM and GApps to internal storage.
Using a SD card, you won't need a computer.
Click to expand...
Click to collapse
Looks like my phone is f****d up bad. I tried internal, didn't work. I tried USB OTG and it is still stuck on Just a sec. Now what?
By the way, i used gapps from your link.
Thanks for your help till now!.
Is there any ROM which doesn't have this type of startup/setup screen?
Sp_3ctr_3 said:
Looks like my phone is f****d up bad. I tried internal, didn't work. I tried USB OTG and it is still stuck on Just a sec. Now what? btw, i used gapps from ur link
Click to expand...
Click to collapse
Maybe it's a problem with the ROM you are using?
You can try to remove your Sim cards. Remove your Sim cards, do the setup and once everything works, put them back it.
Noter2017 said:
Maybe it's a problem with the ROM you are using?
You can try to remove your Sim cards. Remove your Sim cards, do the setup and once everything works, put them back it.
Click to expand...
Click to collapse
Tried that too. Still stuck. Used AEX, RR, HavocOS. Dunno whats wrong with my device. Somehow no matter what ROM i use, the system UI keeps crashing.
Sp_3ctr_3 said:
Tried that too. Still stuck. Used AEX, RR, HavocOS. Dunno whats wrong with my device. Somehow no matter what ROM i use, the system UI keeps crashing.
Click to expand...
Click to collapse
If system UI keeps crashing, you probably didn't wipe your system before flashing a new ROM.
In OrangeFox go to:
Wipe - Advanced Wipe
and select everything except external storage and "Cust"
then swipe to wipe
After that go back to:
Wipe - Format Data
type "Yes" and format Data.
After that is done, flash the ROM and GApps right afterwards.
Noter2017 said:
If system UI keeps crashing, you probably didn't wipe your system before flashing a new ROM.
In OrangeFox go to:
Wipe - Advanced Wipe
and select everything except external storage and "Cust"
then swipe to wipe
After that go back to:
Wipe - Format Data
type "Yes" and format Data.
After that is done, flash the ROM and GApps right afterwards.
Click to expand...
Click to collapse
Both Cust and external storage option isn't available in the menu. Also this error shows up when i wipe everything
Unable to wipe '/sdcard 1 ' -- Unknown file system 'auto'
Use Pixel Experiance April build
Use Pixel Experiance april build. it works completely fin. Even I had this problem. Hope it works fine
Sp_3ctr_3 said:
Both Cust and external storage option isn't available in the menu. Also this error shows up when i wipe everything
Unable to wipe '/sdcard 1 ' -- Unknown file system 'auto'
Click to expand...
Click to collapse
Restart to recovery
Wipe - Format Data and type yes.
After that works, wipe everything and install the ROM and GApps.
Alternatively, Wipe and then "Swipe to Factory Reset" like in the screenshot attached.
If this doesn't work, maybe there's a problem because you encrypted your phone. Maybe this will help then:
https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137?&ampcf=1
Noter2017 said:
Restart to recovery
Wipe - Format Data and type yes.
After that works, wipe everything and install the ROM and GApps.
Alternatively, Wipe and then "Swipe to Factory Reset" like in the screenshot attached.
If this doesn't work, maybe there's a problem because you encrypted your phone. Maybe this will help then:
https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137?&ampcf=1
Click to expand...
Click to collapse
It wont be solved I assure you. There is no probelm with gapps either as i have tried an older (feb 19 built gapps package) and it didn"t worked with any rom(havoc,rr). Try to flash the older Pixel Experience april build . Check your private messege inbox as i have sent you the link. It will surely work.
:fingers-crossed:
DROIDMANN_PANDA said:
It wont be solved I assure you. There is no probelm with gapps either as i have tried an older (feb 19 built gapps package) and it didn"t worked with any rom(havoc,rr). Try to flash the older Pixel Experience april build . Check your private messege inbox as i have sent you the link. It will surely work.
:fingers-crossed:
Click to expand...
Click to collapse
Yup it worked! But there are 2 problems,
1] My SIM card are not being detected.
2] The phone is stuck on Phone Is Starting, i tried installing Nova with adb, but the default app selection settings still is blank. (after finishing the setup, which was a pain in the ass since i had no keyboard for some reason.
Sp_3ctr_3 said:
I am using Redmi Note 4 SD625. I was easily running AEX {9.0}, without any problems.
I decided to switch to HavocOS. After installing the zip, and also Gapps {pico}, my phone got stuck on Just a Sec screen after Language Selection. I already tried using different ROMS, clearing Internal Storage, Formatting Data using TWRP, but nothing is working. I really need to get this device going. Please Help. Also, my phone's system UI keeps crashing while on Just a Sec Screen [ black screen and then instant refresh of notification panel]. Is this something to do with my gaps? Please help.:crying:
Click to expand...
Click to collapse
"SYSTEM UI KEEPS CRASHING" FACED THE SAME ERROR A YEAR AGO!!!???
I flashed miui via miflash or any rom via twrp, the same error. Last option was to flash stock ROM , lock bootloader and sent to mi service centre.
They said that the motherboard got damaged and replaced with a new one..
akkeo said:
"SYSTEM UI KEEPS CRASHING" FACED THE SAME ERROR A YEAR AGO!!!
I flashed miui via miflash or any rom via twrp, the same error. Last option was to flash stock ROM , lock bootloader and sent to mi service centre.
They said that the motherboard got damaged and replaced with a new one..
Click to expand...
Click to collapse
My warranty is expired so i guess they will take money for it? Any idea about the costs?
Sp_3ctr_3 said:
Yup it worked! But there are 2 problems,
1] My SIM card are not being detected.
2] The phone is stuck on Phone Is Starting, i tried installing Nova with adb, but the default app selection settings still is blank. (after finishing the setup, which was a pain in the ass since i had no keyboard for some reason.
Click to expand...
Click to collapse
Nevermind! This ROM is working completely fine. Sadly i lost all the customization features , but i guess you reap what you sow. I did messed up while installing a new ROM, as you guys mentioned. Thank you all for your support!
Sp_3ctr_3 said:
My warranty is expired so i guess they will take money for it? Any idea about the costs?
Click to expand...
Click to collapse
Bro they will charge 5000 INR.
Noter2017 said:
Restart to recovery
Wipe - Format Data and type yes.
After that works, wipe everything and install the ROM and GApps.
Alternatively, Wipe and then "Swipe to Factory Reset" like in the screenshot attached.
If this doesn't work, maybe there's a problem because you encrypted your phone. Maybe this will help then:
https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137?&ampcf=1
Click to expand...
Click to collapse
Sp_3ctr_3 said:
Nevermind! This ROM is working completely fine. Sadly i lost all the customization features , but i guess you reap what you sow. I did messed up while installing a new ROM, as you guys mentioned. Thank you all for your support!
Click to expand...
Click to collapse
Probably you want a clean flash. Install latest twrp, go to wipe, select sys,vendom,data,dalvik,chache and wipe.
after this flash the pixel experience rom which i sent you . Always go for a clean flash.. your phone will jump back to life

TWRP not reading storage.

After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8).
Now the thing is that everything was working perfectly fine until this latest magisk update. Rom works fine (Havoc OS v2. 5), magisk works fine, root works fine, phone is encrypted just as it was before, everything is fine except twrp and i really need twrp to keep working as it was before.
Now yes, I have removed pin/password and tried to make twrp work, switched from pattern to pin as some solutions out there say that twrp will ask for the pin on boot up and on entering the correct pin it will decrypt the internal storage and all will be fine. But no, it didn't work.
Whatever it is am damn sure its magisk. Rom is the same, kernel is what came with the rom, no magisk modules installed, infact I run magisk in core mode only (yes I have disabled core mode only to see if it fixes the problem). I have attached a screen shot of magisk home screen and you can see that under the advanced settings Force encryption is enabled (just like it was enabled while installing magisk for the first time, I have never messed with those settings) and the other two are disabled. Do i need to check that recovery mode? Whatever the solution is, it is preferable that I don't loose my rom and data. But if there's a 100% working solution which involves wiping everything then please mention that too.
Also some solutions need you to change the file format of the internal storage, and I am a little afraid to try that.
Sorry for the extra long post, Thanks in advance.
ronish.x said:
After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8)....
Click to expand...
Click to collapse
Check your TWRP logs. They will contain clues as to what might be the problem. Then post the logs in your TWRP forum. You can get the logs via adb
Code:
adb pull /tmp/recovery.log
adb pull /tmp/dmesg.log
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Soojikahalwa said:
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Click to expand...
Click to collapse
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
ronish.x said:
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
Click to expand...
Click to collapse
Try using an older version of twrp first. Changing storage type for system or data might lead to data lose. Make a backup in any case.

Categories

Resources