TWRP cant mount /system - Honor 9 Questions & Answers

Booting into TWRP give me an error "Unable to unmount /system, partition or resource busy" and subsequently, i can't flash any GSIs to the system partition, i get the error "Unable to install images to file systems". It is possible to boot into fastboot and flash however.
This seems to be an issue regarding to TWRP mounting /system, iv'e read up a bit on it, and it seems that a data wipe in TWRP should fix it?
i
Im on TWRP 3.2.1 for the H9

Related

[Q] /data is encrypted, so CWM can't mount /sdcard from zip installing

Hi!
I used to run CyanogenMod 9.1 with device encryption on my Galaxy S3, and decided today that I wanted to try a CM 10 nightly.
A problem with device encryption that I didn't know about before is that it's impossible to turn off. ClockworkMod Recovery (5.8.4.3) can't mount the /data partition (and, by extension, /sdcard). This means that I can't use CWM to factory reset or install a new update.zip, since the update.zip must lie on the internal sdcard.
Trying "choose zip from sdcard" gives "E:Can't mount /sdcard/" and choosing "apply /sdcard/update.zip" gives "E:Can't mount /sdcard/update.zip". This happens even if I've used adb to put the update.zip in the /sdcard mountpoint.
Factory resetting from CWM gives these two errors: "Error mounting /data!" and "Error mounting /sdcard/.android_secure!". Factory resetting from CM9 didn't work. I've since tried to flash CM10 with MobileOdin, which didn't work, and now I can only boot to CWM.
Does anyone have any idea about how I could mount /data or otherwise get a working ROM? I've taken backups of everything.
TL;DR: S3 only boots to CWM, but CWM won't mount /data and so can't flash zips.
I have the exact smae problem. i hope someone knows how to fix!!

Help! problem loading Roms

Not sure if this has been answered, but I have been searching and cannot find an answer.
I'm S-Off with Dirty Racun, have been flashing Roms for the past year, no problems, backing up and restoring Roms with no problem. Recently was using the latest Hatka LTE but wanted to restore to an earlier version. Didn't work. Did a super wipe and tried to install clean. Didn't work.
Have been messing with this all day and am stuck. At first it was saying that it could not mount the /sdcard. I thought maybe the internal sdcard was corrupt, so I formatted the internal sdcard. Didn't help.
Anyways, yes, I can get into bootloader and I can get into TWRP.
Yes, I have tried other versions of TWRP. All my backups were created under 2.4.1, have tried 2.4.4 and 2.5 to restore, no success.
In TWRP 2.4.1:
It will say:
Restoring 4 partitions...
Wiping System...
Formatting System using mke2fs...
Done.
Restoring system...
E:Unable to extract tar archive '/sdcard2/TWRP/BACKUPS/HT2324......
Wiping Cache..
Formatting Cache using mke2fs...
Done.
Restoring cache...
[cache done]
Restoring boot...
[boot done]
Updating partition details....
E:Unable to unmount '/system'
Also, not sure if this is related, but when I do Factory Reset under the Wipe section, it will only show that it is formatting cache, formatting data, and wiping .android_secure. It used to say formatting system, but now doesn't mention it?
Also, immediately after it says unable to mount /system, if I try to wipe system, it will give me a fail, unable to unmount /system
Basically, I'm stuck at TWRP and bootloader.
Also, when I try to install a ROM, any ROM, it will die - for example MeanBean 3.09, it will say:
Formatting and Mounting Partition...
Clearing cache and dalvik...
Installing /system....
Installing /data...
symlink: some symlinks failed
E: Error in /sdcard2/MeanBean-v309-jewel-ltevo.zip (Status 7)
Please help! What can I do to restore it back to the way it was so that I can at least get a working ROM on my phone?
Thanks!
Also, if it will help, I am HBoot 1.19.22222
Radio 1.12.11.1210
OpenDSP-v31.1.0.45.0815
Thanks for any help in advance!! Really need this phone to boot into something working.
Buffpandabear said:
Not sure if this has been answered, but I have been searching and cannot find an answer.
I'm S-Off with Dirty Racun, have been flashing Roms for the past year, no problems, backing up and restoring Roms with no problem. Recently was using the latest Hatka LTE but wanted to restore to an earlier version. Didn't work. Did a super wipe and tried to install clean. Didn't work.
Have been messing with this all day and am stuck. At first it was saying that it could not mount the /sdcard. I thought maybe the internal sdcard was corrupt, so I formatted the internal sdcard. Didn't help.
Anyways, yes, I can get into bootloader and I can get into TWRP.
Yes, I have tried other versions of TWRP. All my backups were created under 2.4.1, have tried 2.4.4 and 2.5 to restore, no success.
In TWRP 2.4.1:
It will say:
Restoring 4 partitions...
Wiping System...
Formatting System using mke2fs...
Done.
Restoring system...
E:Unable to extract tar archive '/sdcard2/TWRP/BACKUPS/HT2324......
Wiping Cache..
Formatting Cache using mke2fs...
Done.
Restoring cache...
[cache done]
Restoring boot...
[boot done]
Updating partition details....
E:Unable to unmount '/system'
Also, not sure if this is related, but when I do Factory Reset under the Wipe section, it will only show that it is formatting cache, formatting data, and wiping .android_secure. It used to say formatting system, but now doesn't mention it?
Also, immediately after it says unable to mount /system, if I try to wipe system, it will give me a fail, unable to unmount /system
Basically, I'm stuck at TWRP and bootloader.
Also, when I try to install a ROM, any ROM, it will die - for example MeanBean 3.09, it will say:
Formatting and Mounting Partition...
Clearing cache and dalvik...
Installing /system....
Installing /data...
symlink: some symlinks failed
E: Error in /sdcard2/MeanBean-v309-jewel-ltevo.zip (Status 7)
Please help! What can I do to restore it back to the way it was so that I can at least get a working ROM on my phone?
Thanks!
Click to expand...
Click to collapse
sorry for the replies to myself, but as an update, now even after rebooting into recovery, I can't even wipe - the first thing that happens after I reboot into recovery is I see
E: Unable to mount '/sdcard'
E:Unable to recreate android secure folder.
E:Unable to mount '/sdcard', which repeats itself a couple of times
then Running boot script...
Finished running boot script...
This happens before I press a single button in recovery (TWRP 2.4.1), I mean it happens immediately as it is booting into recovery
Buffpandabear said:
sorry for the replies to myself, but as an update, now even after rebooting into recovery, I can't even wipe - the first thing that happens after I reboot into recovery is I see
E: Unable to mount '/sdcard'
E:Unable to recreate android secure folder.
E:Unable to mount '/sdcard', which repeats itself a couple of times
then Running boot script...
Finished running boot script...
This happens before I press a single button in recovery (TWRP 2.4.1), I mean it happens immediately as it is booting into recovery
Click to expand...
Click to collapse
I had the same issue and ended up using three different versions of TWRP, but if you go to the TWRP thread, captain just posted his version of recovery that he built from source and he fixed some of the issues with the android secure and changed some of the wipes, check it out and reformat using rm rf, works better for me it's in the advanced options...
Edit: link to captain's post
http://forum.xda-developers.com/showthread.php?p=41528948
Sent from my EVO using xda app-developers app

(Solved) Can't mount /sdcard in recovery.

Android Version 4.4.2
S-on
Bootloader Unlocked
Philzrecovery
No system or data
I can't mount my sdcard in recovery to get to the backup I made of my previous rom. So as of right now I'm in recovery mode waiting for help.
Getting "E:Can't mount /sdcard" error
Edit1: tried reflashing philzrecovery to see if if that was the problem. It didn't fix it.
Edit2: Formatted /sdcard in recovery. I can mount it now. Now all I need is a .zip file. (I hope)
Edit3: Sideloading .zip
Final edit: it's all good! I formatted everything in recovery (system, data, sdcard) then transferred a Rom successfully via adb. Flashed it, and all is well!
How about now?

Nabi 2 Flashing trouble with TWRP

Hello, I have a Nabi sitting around and decide to get it out, update it and put it to use. My flashing skills are novice, I do a phone or tablet once in a blue moon and it it usually been with a AIO or relatively trouble free.
I have TWRP 2.3.3.0 and the Kernel is 1.9.3.7 from last year I install custom recovery
I attempted to install Monarch UI Removed/SuperSU & SU Binaries Installed including BusyBox 3.0.13( Fuhu/Nabi/Keenhi Stuff Removed ) - n3wt when that failed I attempted Stock Rom 3.0.13 via TWRP - aicjofs
I did a full Wipe, attempted to install with TWRP and ADB sideload.
The ADB sideload reaches 100% on PC and is marked failed on the Tablet in TWRP sideload UI.
Installing in TWRP I get the following errors in the Terminal
Code:
Updating Partitions details...
E:/Unable to mount '/data'
E:/Unable to mount '/data'
E:/Unable to mount '/system'
E:/Unable to mount '/cache'
E:/Unable to mount '/data'
E:/Unable to mount '/addon'
I also tried installing Stock Version 1.9.37 with similar results.
In the mount menu I can't selec "Using internal storage" or any of the mount options.
Also all wiping options for cash and system fail.
Next I re-installed TWRP 2.3.3.0 through fastboot to make sure everything was clean and it appeared to all take, and I still get the same results trying to flash.
So I am at a loss as what to try next and would appreciate any help.
While posted I've been trying NabiLab here is the error I received on a stock recovery.
*********** Restore Nabi to Factory 1.9.37 from ANDROID ****************
Install recovery to Internal or External SD card?
-If external make sure your card is installed-
1. Internal SD
2. External SD
Choose an option:1
Files are prepared. Press any key to begin restore.
Press any key to continue . . .
rebooting...
When TWRP is done booting press enter
Press any key to continue . . .
Pushing stock recovery to your device
Ignore external SD card error if you have none installed
This files are 1.2GB this will take many minutes. Please wait.
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /data on ext4 failed: No such file or directory
mount: mounting /addon on ext4 failed: No such file or directory
mkdir: can't create directory '//data/media/TWRP/BACKUPS/0123456789ABCDEF/abcdst
ock123': No such file or directory
1332 KB/s (8388608 bytes in 6.149s)
9 KB/s (48 bytes in 0.005s)
Click to expand...
Click to collapse
jumbojimx said:
Hello, I have a Nabi sitting around and decide to get it out, update it and put it to use. My flashing skills are novice, I do a phone or tablet once in a blue moon and it it usually been with a AIO or relatively trouble free.
I have TWRP 2.3.3.0 and the Kernel is 1.9.3.7 from last year I install custom recovery
I attempted to install Monarch UI Removed/SuperSU & SU Binaries Installed including BusyBox 3.0.13( Fuhu/Nabi/Keenhi Stuff Removed ) - n3wt when that failed I attempted Stock Rom 3.0.13 via TWRP - aicjofs
I did a full Wipe, attempted to install with TWRP and ADB sideload.
The ADB sideload reaches 100% on PC and is marked failed on the Tablet in TWRP sideload UI.
Installing in TWRP I get the following errors in the Terminal
Code:
Updating Partitions details...
E:/Unable to mount '/data'
E:/Unable to mount '/data'
E:/Unable to mount '/system'
E:/Unable to mount '/cache'
E:/Unable to mount '/data'
E:/Unable to mount '/addon'
I also tried installing Stock Version 1.9.37 with similar results.
In the mount menu I can't selec "Using internal storage" or any of the mount options.
Also all wiping options for cash and system fail.
Next I re-installed TWRP 2.3.3.0 through fastboot to make sure everything was clean and it appeared to all take, and I still get the same results trying to flash.
So I am at a loss as what to try next and would appreciate any help.
While posted I've been trying NabiLab here is the error I received on a stock recovery.
Click to expand...
Click to collapse
Wrong TWRP version is my guess. http://forum.xda-developers.com/showpost.php?p=62391871&postcount=2635 There are the 3 versions you need to try.
Thanks, got it fixed.
It was the wrong TWRP. Then I wasn't seeing any recovery files. ADB was giving me an odd generic serial number, I did a back up and then dumped the files in the TWRP created folder and they appeared.
Original Post.
aicjofs said:
Wrong TWRP version is my guess. http://forum.xda-developers.com/showpost.php?p=62391871&postcount=2635 There are the 3 versions you need to try.
Click to expand...
Click to collapse
Thanks for the reply.
I tried all 3 versions of TWRP in your post . TWRPv263 for ICS Nothing (cache,data,system, extsdcard etc) will mount. TWRPv285 for JB&KK Everything but /system will mount.
Using all 3 versions of TWRP I tried to install 3013stock.zip and 3013bootloader. No files from the extracted zip show up in TWRP recovery tab.
So I assume the issue I am aiming at is getting /system to mount in either KK or JB version of TWRP. v285?
Click to expand...
Click to collapse

[HELP]Moto E TWRP error in filesystem and Boot-loop.

Im using Moto E 1st generation, Bootloader unlocked with TWRP custom recovery. I was using custom rom Marshmallow by Temasek and I thought to change the rom. Recently, I upgraded TWRP to 3.0.2-0.
I have wiped system, dalvik, internal storage, cache and data everything went smoothly.
when i tried to install Rom zip i encounter and error that causing boot loop.
HTML:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name system at /system: invalid argument
unmount of /system failed : no such volume
Patching system image unconditionally ...
flashing Supersu..
scripting succeed result was []
update partition details
...done
when i reboot, my phone goes in boot loop.
i tried with repair or change file system but still the error is same
my file system and format
/system ext4
/Data ext4
/cache ext4
Please Help to recover my mobile thank you...
flash the stock firmware, some times it fix this issues.
flash the stock firmware without flashing the recovery partition, and flash again twrp to avoid any issue, then flash temasek

Categories

Resources