I just got a used TF700t 64gb US version and I'm trying to flash it to CROMBI-KK. I was able to get it unlocked and TWRP 2.8.3.0 installed (the latest version as of 12/22/2014). However, every time I boot to recovery, it begins with a serious looking error. The output screen always starts off with this:
Updating partition details...
... done
Full SELinux support is present.
E:Failed to get default contexts and file mode for storage files.
MTP Enabled
No other errors are shown at first and I was able to flash the ROM. I tweaked something and it failed to boot so I went back in to reflash it. The error was still there. I have tried several wipes and changed to F2FS but the same error remains. I don't know if it's related to the error or not, but when I try to install while configured for F2FS, it always ends with another error and no OS installed. I didn't get the exact wording, but something about recursion and that something failed (it's quite vague).
Right now it is back to working, but it had to be on regular EXT4 and data journaling to work. Anyone know if there is any way to remove the storage error? Are there any other options I could try to get F2FS working?
You are only changing /data to f2fs, right?
Try to get the recovery log whenever something fails that shouldn't.
In TWRP: Advanced > Copy log
From PC: adb pull /tmp/recovery.log
berndblb said:
You are only changing /data to f2fs, right?
Try to get the recovery log whenever something fails that shouldn't.
In TWRP: Advanced > Copy log
From PC: adb pull /tmp/recovery.log
Click to expand...
Click to collapse
I was trying to do F2FS on all three available locations (/system, /cache, and /data). I didn't realize that I was only supposed to do it on /data, though when I looked at my older device, that's how it was configured as well.
So the F2FS error is figured out, but then there was the issue of the error in TWRP immediately on loading it. I rebooted my older TF700 into recovery and it did not have the error line. However, I noticed that it was running TWRP 2.8.0.1 and my newer one was running TWRP 2.8.3.0. I upgraded the older device to 2.8.3.0 and, lo and behold, the error appeared. So I'm relieved that the error doesn't seem to be an actual problem with my new device, but I'm curious still on what it means and how to resolve it. Is this something that is just inherently funky with TWRP now, or is there something I can do to configure my device so it will register as TWRP is expecting?
techturtle said:
I was trying to do F2FS on all three available locations (/system, /cache, and /data). I didn't realize that I was only supposed to do it on /data, though when I looked at my older device, that's how it was configured as well.
So the F2FS error is figured out, but then there was the issue of the error in TWRP immediately on loading it. I rebooted my older TF700 into recovery and it did not have the error line. However, I noticed that it was running TWRP 2.8.0.1 and my newer one was running TWRP 2.8.3.0. I upgraded the older device to 2.8.3.0 and, lo and behold, the error appeared. So I'm relieved that the error doesn't seem to be an actual problem with my new device, but I'm curious still on what it means and how to resolve it. Is this something that is just inherently funky with TWRP now, or is there something I can do to configure my device so it will register as TWRP is expecting?
Click to expand...
Click to collapse
It seems to be a bug in TWRP 2.8.3. I just flashed that version (was on 2.8.1 before), flashed data2sd.zip an got the E: Failed to get default context.... error. I am dirty flashing ZOMBi now and got the same error although the flash seems to be going fine.
I'll post the logs in the TWRP thread. Let's see what the experts have to say....
Related
When I try to install the CM11 nightly builds as found through this thread:
http://forum.xda-developers.com/showthread.php?t=2570965
the update process fails. Below a snip ffrom the TWRP log (I've attached the complete log).
minzip: Extracted file "/system/xbin/vim"
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sdcard/ROM/cm-11-20140101-NIGHTLY-tf300t.zip'
Error flashing zip '/external_sdcard/ROM/cm-11-20140101-NIGHTLY-tf300t.zip'
Through creative Googling I found some references to the install failing with TWRP and succeeding with CWM. However, the CWM ROM Manager tells me there is no supported recovery version for the TF300, so I have no idea which version to pick.
I should mention I may have partially broken my partition table when making nvFlash available though. I made another post about that:
http://forum.xda-developers.com/showthread.php?t=2594142
to which I was hoping to get a reply by now.
I'm hoping someone could help me out, I'd really like to try KitKat on this tablet.
Thanks!
Wrong TWRP?!
Orionos said:
When I try to install the CM11 nightly builds as found through this thread:
http://forum.xda-developers.com/showthread.php?t=2570965
t[...]
I'm hoping someone could help me out, I'd really like to try KitKat on this tablet.
Thanks!
Click to expand...
Click to collapse
Hmm, regularly the issue with TWRP for the TF300T is that you need a very specific/modified version, more often than not for the TF300T not the one from the TWRP site.
I can only recommend using this script to update to CM11, as it does all the installation/downloading/flashing for you, inlcuding the correct TWRP and CM/Omni and GAPPS.
http://forum.xda-developers.com/showthread.php?t=2579922
Hope this helps
recovery
Recheck the original post and make sure you are using the correct recovery.
buche,
Your script helped. When using that particular recovery, not only can I install KitKat, but my backups started working as well. Of course, the patched TWRP generates an error when installing CM10. Go figure.
norskyforce,
The post stated:
"To install, you need a recent CWM or other recovery."
I figured I was fine with the TWRP from the TWRP site. Apparently not.
Maybe I'll try the poster's recovery image. I'm still looking for the correct CWM to use, to see if it has more options. I miss 4ext
Thanks for the help.
Unfortunately, CM11/Omni don't appear to support my WiFi's channel 13. Took me a while to figure out why I could see all the neighbors' networks, but not my own.
And I just figured out neither CM10 or 11 supports my ASUS Connect Dock, which I use for the wired ethernet and USB. Grrr...
First I like to thank berndblb for Beginners Guide to root and flashing a custom ROM on the TF700T. :good:
I was able to get it unlocked and TWRP 2.8.4.0 installed using Minimal ADB and Fastboot . Got this error when creating a nandroid and also it happened again when Copying Log to SD.
E:Failed to get default contexts and file mode for storage files.
From what I can find on error ,it seems to be in TWRP related after version is 2.8.1.0. Should I flash 2.8.1.0 and do I have to delete 2.8.4.0 first ?
I am still reading about About F2FS and getting ready to flash a Rom. But before I Screw stuff up as a Noob.
I am trying to learn be for I (Error}!
I attached a copy of data log.
Thanks,
Never North
Never North said:
E:Failed to get default contexts and file mode for storage files.
From what I can find on error ,it seems to be in TWRP related after version is 2.8.1.0. Should I flash 2.8.1.0 and do I have to delete 2.8.4.0 first ?
Click to expand...
Click to collapse
Just ignore the error message, it's harmless.
Hello guys,
Today I wanted to update my Honor 8 (FDR-L09) because it was showing me, that there is a new update ready to install (FRD-L09C432B405) and I was on a very old firmware (something from mid 2017). So it was time for me to update.
I downloaded the latest update (FRD-L09C432B405) and tried to wipe the cache, dalvik, and Data, but for some reason it "couldn't mount /data" and the wipe failed.
After an advanced wipe it worked and I tried to flash the stock image (the update which was shown to me (FRD-L09C432B405) with TWRP (3.1.1.1.)).
Now my hassle starts:
1. The Rom couldn't get flashed because of "Error: 7" --> I fixed it with the common "Error 7 fix --> editing the update-script and removing the assert line. (And yes, I'm 100% sure that it was the right ROM.
2. Now TWRP seemingly starts to flash the rom but inbetween the lines there is "mountencrypt: failed to mount /data: no such file or directory and it ends with "unknown command [[]" and it takes just two seconds, so the flash obviously isn't succsessfull.
I tried the "failed to mount /data" fix, where I change the data system to ext3 and then back to f2fs and change it back, but it won't work.
In my frustration I did another pretty bad thing and made another advanced wipe and wiped the system too, so now I don't have an OS on my system.
Maybe it's also important to note that there was a window showing up for a very short amount of time, with something like "encryption/encrypted" showed up.
What should I do now? Is there a way to fix the "/data couldn't be mounted" problem? Or am I missing a vital step in flashing the stock rom?
Thanks for your kind help!
You can not flash an update with twrp unless you use hurupdater. You essentially bricked your phone. Look for hurupdater here on xda and follow the instructions and you'll be fine
I'm trying to install LineageOS and then GAPPS on my Pixel XL from TWRP recovery. I'll try to `Advance Wipe` the `/systems` directory and `Format Data`, but I continue to get multiple errors:
Code:
Failed to mount '/system' (Device or resource busy)
Code:
Failed to mount '/vendor' (Device or resource busy)
And
Code:
Unable to wipe 'System'
Code:
Unable to wipe '/system'
If I just continue with `adb sideload lineageos.zip` most of the time it stops about halfway (PowerShell shows `47%`) through and then TWRP shell shows:
Code:
Installing zip file '/sideload/package.zip'
Step 1/2
Step 2/2
I then try to `sideload` the `gapps.zip` file and get another error saying `/system` doesn't have enough space. I've tried sideloading several different gapps versions including their smallest `pico` zip fie of `91.39 MiB`.
I am able to then boot into LineageOS, but no GAPPS show and I'm not able to run any new apps installed via APK without them crashing.
My assumption is that I need to fully wipe `system` and format it, but I've been trying for two days now and still get the above `(Device or resource busy)` errors. Any help would be much appreciated!
Make sure you have the latest tools.
Latest TWRP for marlin is 3.3.0-0
Latest platform-tools is 29.0.1
Not sure what's the cause of this, but if you want to wipe and start fresh I think the best option is reflash the stock factory image that completely wipes everything and restores everything stock.
Then, you can retry wiping the device using the latest TWRP (currently, marlin is 3.3.1-0, the zip is 3.3.0-0, try just boot it and don't flash the zip), flash LOS and then gapps.
Also, as pointed by @post-mortem, make sure you are using the latest adb version when flashing the factory image, just to avoid any potential issue.
Don't use 3.3.1-0. Try 3.3.0-0. I had the same issue.
Why doesn't TWRP Team provide an answer as to why this happens? It appears to affect everyone with the latest official Pixel ROM.
Twrp is for Android pie and has trouble mounting stock Android 10. They have announced this on their website. This shouldn't matter since you're installing lineage. You don't need to wipe system before installing lineage because it installs into the inactive slot. You need to sideload lineage then reboot into recovery to switch slot's. The instructions are on the lineage website.
Did OP manage to solve this issue?
I've been running ArrowOS - Arrow-v12.0-vayu-OFFICIAL-20211108-VANILLA - and pleased with it's stability, but decided it was time to update to the Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA version.
Recovery was TWRP-3.5.2-vayu-Nebrassy-2 so I used the TWRP app to update that to the official TWRP-3.6.0.
My phone is encrypted and without a password. TWRP-3.6.0 couldn't mount partitions or view files.
Data partition etc show 0 bytes' and adb sideload failed to connect - may have been an unreliable cable - so I added a 4-digit pin which worked in the system and rebooted to recovery. TWRP didn't ask for a password and showed the same encrypted and invisible partitions. Trying the 'Decrypt Data' option in TWRP 'Mount' menu, I got the errors 'Failed to decrypt data' 'Password failed'.
I tried using adb shell to decrypt:
vayu:/ # twrp decrypt 1234
Attempting to decrypt data partition or user data via command line.
Failed to decrypt data.
Click to expand...
Click to collapse
Then I tried adb sideload from TWRP which failed quickly with:
updater process ended with signal 7
Click to expand...
Click to collapse
And on my Ubuntu laptop:
$ adb sideload Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA.zip
serving: 'Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA.zip' (~7%) adb: failed to read command: Success
Click to expand...
Click to collapse
I rebooted into System, and got Fastboot instead. I can reboot into recovery.
Can anyone suggest how to repair the phone, and get TWRP to decrypt the filesystem?
TIA!
Giallograle said:
I've been running ArrowOS - Arrow-v12.0-vayu-OFFICIAL-20211108-VANILLA - and pleased with it's stability, but decided it was time to update to the Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA version.
Recovery was TWRP-3.5.2-vayu-Nebrassy-2 so I used the TWRP app to update that to the official TWRP-3.6.0.
My phone is encrypted and without a password. TWRP-3.6.0 couldn't mount partitions or view files.
Data partition etc show 0 bytes' and adb sideload failed to connect - may have been an unreliable cable - so I added a 4-digit pin which worked in the system and rebooted to recovery. TWRP didn't ask for a password and showed the same encrypted and invisible partitions. Trying the 'Decrypt Data' option in TWRP 'Mount' menu, I got the errors 'Failed to decrypt data' 'Password failed'.
I tried using adb shell to decrypt:
Then I tried adb sideload from TWRP which failed quickly with:
And on my Ubuntu laptop:
I rebooted into System, and got Fastboot instead. I can reboot into recovery.
Can anyone suggest how to repair the phone, and get TWRP to decrypt the filesystem?
TIA!
Click to expand...
Click to collapse
Any custom recovery at the moment cannot decrypt Android 12.
Try USB OTG or microSD card to flash in custom recovery.
Oic thanks!
Sounds like an easy fix. Before I do that, am I going to lose data, settings etc by flashing the update when the recovery can't access all the filesystem?
Giallograle said:
Oic thanks!
Sounds like an easy fix. Before I do that, am I going to lose data, settings etc by flashing the update when the recovery can't access all the filesystem?
Click to expand...
Click to collapse
Not sure if your previous actions messed up your data partition or not, so not sure if you will loose your data or not.
Recoveries cannot decrypt data partition, but the system file writing ability should be working.
If you still have the zip file of the old version 20211108, you can flash it and see if the system will boot and read your data correctly.
If it boots and your phone is like before update attempt, then you can try flash the update zip.
If it did not boot into the OS, chances are some of your earlier actions messed up data partition. In this case, format data is the way, which will loose your data.
If format data still doesn't help, you might need to go back to MIUI and start again.
That was a good suggestion. I reinstalled the Arrow-v12.0-vayu-OFFICIAL-20211108-VANILLA rom and the phone rebooted.
Only glitch is constant notifications that Google Play Services keeps stopping, and various other apps notifications to 'Get Google Play Services'.
I presume that Play Services may have been rolled back by the reinstallation, and I'm wondering whether to try to find a more recent copy to install and see if that fixes it, or just go directly to the Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA rom.
Giallograle said:
That was a good suggestion. I reinstalled the Arrow-v12.0-vayu-OFFICIAL-20211108-VANILLA rom and the phone rebooted.
Only glitch is constant notifications that Google Play Services keeps stopping, and various other apps notifications to 'Get Google Play Services'.
I presume that Play Services may have been rolled back by the reinstallation, and I'm wondering whether to try to find a more recent copy to install and see if that fixes it, or just go directly to the Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA rom.
Click to expand...
Click to collapse
Did you install GApps manually?
If you did not, but your system has Google Play Services, then you probably had installed GApps version of ArrowOS instead of Vanilla version.
Switching between Vanilla and GApps is probably not working well if you did not format data. Maybe from Vanilla to GApps version is possible, but from GApps version to Vanilla may cause some issues.
Make sure which version you had, GApps or Vanilla.
If you are not very sure, then backup all your personal data and apps and do a clean flash with format data.