[RECOVERY] TWRP-3.3.0 with Pie decryption support [experimental] - OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel

TWRP compiled from the latest omnirom 9.0 branch with support for Android Pie (9) and its encryption/decryption (backward compatible with older Android versions).
Tested:
Decrypting Pie data partition (with pattern) - Works
Flashing a zip file - Works
MTP - Works
Nandroid backup/restore - Works
Everything else works fine, but use on your own risk!
The build IS UNIFIED (for OP5 and 5T, based on the blu_spark device tree).
This TWRP is treble compatible!
Download:
https://www.androidfilehost.com/?w=files&flid=281621
Source code:
https://github.com/engstk/android_device_oneplus_cheeseburger
https://github.com/omnirom/android_bootable_recovery
Credits: @eng.stk @Dees_Troy
And the whole TWRP/Omnirom team

It works great, thank you!

Mirrors here! (including themed, un-unthemed, treble and non-treble versions)

Thanks. It works.

Hey, quick question, i'm on DU (8.1) and my device says "Device is decrypted" , does this mean i don't have to wipe data in order to flash a 9.0 ROM? Thanks in advance!

Fechinator said:
Hey, quick question, i'm on DU (8.1) and my device says "Device is decrypted" , does this mean i don't have to wipe data in order to flash a 9.0 ROM? Thanks in advance!
Click to expand...
Click to collapse
A data wipe is always recommended while switching between major Android versions to avoid running into issues, minor or major.

I can't use twrp since it can't recognize my password
can this build fix this problem ??

Works perfectly just like your Roms
Thank you very much

the link to download doesn't work!
Sent from my [device_name] using XDA-Developers Legacy app

sharaq said:
the link to download doesn't work![/url]
Click to expand...
Click to collapse
Issue is definitely at your end. I just tested downloading and it went fine. It's an AndroidFileHost folder link.

Works good. Tested on crDroid Pie.
Thank you for this.

Seems Afh is having some issue here too.
Sent from my ONEPLUS A5000 using Tapatalk
Tried again, working now. ( ಠ◡ಠ )

I have an encrypted device, i want to stay encrypted after installing pie ROMs, is this recovery keep my device encrypted or it will remove the encryption? Need some guidance

Alipk52 said:
I have an encrypted device, i want to stay encrypted after installing pie ROMs, is this recovery keep my device encrypted or it will remove the encryption? Need some guidance
Click to expand...
Click to collapse
You will remain encrypted if the ROM supports encryption but this recovery is experimental according to the title

Aroma OpenGApps 9.0 arm64 breaks when starting to install. On Oneplus 5, Lineage OS 16.0 experimental by codeworkx.

Works for me using pixen2 rom !

siankatabg said:
TWRP compiled from the latest omnirom 9.0 branch with support for decrypting the Android Pie (9) encryption (backward compatible with older Android versions).
Tested:
Decrypting Pie data partition (with pattern) - Works
Flashing a zip file - Works
MTP - Works
Nandroid backup/restore - Works
All else should work fine, but the whole recovery is experimental, so use on your own risk!
The build should be unified (for OP5 and 5T, based on the blu_spark device tree), but it was tested only on Oneplus 5! This TWRP is treble compatible.
Download:
https://www.androidfilehost.com/?w=files&flid=281621
Source code:
https://github.com/engstk/android_device_oneplus_cheeseburger
https://github.com/omnirom/android_bootable_recovery
Credits: @[email protected]_Troy
And the whole TWRP/Omnirom team
Click to expand...
Click to collapse
Working perfect on PixEn2 9.0

Tried this recovery out with Oxygen OS 8.1 Beta 19, magisk 17.2 beta. When I go to recovery -> Backup -> Select everything and try to make a backup, everything goes fine until the very last minute, when the "createTarFork() process ended with ERROR: 255" error pops up followed by "Backup Failed. Cleaning Backup Folder.". Here is the last few lines from the recovery.log for reference.
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.apps.messaging/1538020684432.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.apps.messaging/1538020684442.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.apps.messaging/1538020684447.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.dialer' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
found policy '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.dialer' - '1CE0' - '0cbd0fc0ceed9bb2'
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.dialer/1537817225643.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.dialer/1537817225646.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.dialer/1537817225650.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.contacts' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
found policy '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.contacts' - '1CE0' - '0cbd0fc0ceed9bb2'
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.contacts/1537954281562.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.contacts/1537954281602.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.contacts/1537954281623.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/recent_images' including root: 1
==> set selinux context: ubject_r:system_data_file:s0
found policy '/data/system_ce/0/recent_images' - '1CE0' - '0cbd0fc0ceed9bb2'
I:addFile '/data/system_ce/999' including root: 1
==> set selinux context: ubject_r:system_data_file:s0
failed to lookup tar policy for '/data/system_ce/999' - '2507fb304b76812a'
I:Error adding file '/data/system_ce/999' to '/data/media/0/TWRP/BACKUPS/33e1533a/2018-09-27--09-49-58/data.ext4.win010'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/33e1533a/2018-09-27--09-49-58/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/33e1533a/2018-09-27--09-49-58/recovery.log
Click to expand...
Click to collapse
Any help in identifying and sorting this out is greatly appreciated. I would like to install the Pixen Pie and would like to take a full backup before proceeding.

Hi Im new here,
the swap button order missing
edited: and also sim card on off

srikaran said:
Tried this recovery out with Oxygen OS 8.1 Beta 19, magisk 17.2 beta. When I go to recovery -> Backup -> Select everything and try to make a backup, everything goes fine until the very last minute, when the "createTarFork() process ended with ERROR: 255" error pops up followed by "Backup Failed. Cleaning Backup Folder.". Here is the last few lines from the recovery.log for reference.
Any help in identifying and sorting this out is greatly appreciated. I would like to install the Pixen Pie and would like to take a full backup before proceeding.
Click to expand...
Click to collapse
After waiting and further searching and all, I came to know that deleting the so called 999 folders does the trick where it lets you backup in twrp. So, I created a del999.sh script with the following commands in it
Code:
rm -rf /data/system/999
rm -rf /data/system_ce/999
rm -rf /data/system_de/999
rm -rf /data/misc/999
rm -rf /data/misc_ce/999
rm -rf /data/misc_de/999
rm -rf /data/user/999
rm -rf /data/user_ce/999
rm -rf /data/user_de/999
In twrp, I navigated to Advanced - Terminal. In there, typed the following commands
Code:
cd sdcard
chmod +x del999.sh
./del999.sh
After this navigating to twrp and back up works just fine.
To restore however, the same steps worked for the most part. However, I had to do a factory reset first, followed by a reboot to recovery followed by del999 and then restore worked. Trying to boot into the system now, fingers crossed, hopefully everything will work as expected.

Related

Sim not working after fastboot erase /config & twrp restore (Z00AD)

TLDR; I have a twrp backup of my zenfone2 at a working state, but sim cards are not detected or unable to unlock after restore
Hi all,
I was trying to restore a TWRP backup (twrp-3.1.1-0-Z00A.img) of my lineageos install (lineage-14.1-20170721-nightly-Z00A-signed.zip) and /config was not restoring (error: "Unable to wipe config."),
so I ended up doing "fastboot erase config" to force the restore, which didn't help and might have been a mistake ...
(the real error after looking at the twrp logs is: "error: build_default_directory_structure: cannot lookup security context for /config/lost+found" / "Unable to wipe config.")
At first I restored /config by hand extracting the backup file (config.ext4.win) on my computer and using cp in twrp terminal, but android was crashing as soon as I inserted a sim card (permissions / selinux problems I guess)
I tried some chown / chmod / restorecon but no luck
I then reflashed stock rom (tried multiple recent versions, Android L and M, using adb sideload) but no luck
I used the "Unlock Device App" but my bootlooder was not locked while reflashing stock rom.
I'm now running lineageos again, I was able to restore /config using "rm -rf" option in twrp, but I either don't see the sim cards, or the phone is unable to unlock them
looking at logcat, the phone is looping trying to flash the modem (https://pastebin.com/zBnjtW1v)
I haven't try Asus Flash Tool and "raw" firmware, would it help ? (I don't have a windows machine handy, only linux / mac)
Any recommended stock version I should try?
To sum up I have a TWRP backup at a know good state (but don't know if the backup is good as it's the first time I try a restore ...),
a zenfone with non working sim cards (working in an other phone), and I would like to make it work again
Thanks
Etienne
Now flashed WW_ZE551ML_4.21.40.223_20161216.raw using Asus Flash Tool (https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966)
but still no sim cards
Can someone share a dd dump of /config partition of a Z00AD?
Thanks
Etienne
Found some errors in the logcat:
08-06 21:02:21.683 263 1603 D : (NVM_1) OpenNvmBinFiles - NOTICE: Error in opening /config/telephony/1//calib.nvm
08-06 21:02:21.683 263 1603 D : (NVM_1) InitNvmModule - Error opening the NVM file
If someone can share /config permissions on their zenfone2 (permissions / owner / group / selinux)
Thanks
Etienne
champtar said:
Found some errors in the logcat:
08-06 21:02:21.683 263 1603 D : (NVM_1) OpenNvmBinFiles - NOTICE: Error in opening /config/telephony/1//calib.nvm
08-06 21:02:21.683 263 1603 D : (NVM_1) InitNvmModule - Error opening the NVM file
If someone can share /config permissions on their zenfone2 (permissions / owner / group / selinux)
Thanks
Etienne
Click to expand...
Click to collapse
kindly PM me your serial number i will send you config files
Same problem hefe !!!!
Hi,
it took me a lot of flashing and tries, but what fixed it was (I think):
0) make a full backup of your phone with TWRP (all partitions)
1) flash latest stock version (UL-Z00A-WW-4.21.40.352-user.zip)
at this point sim card where not working, I was seeing selinux error (avc: denied ...) for process mmgr (looking with adb logcat)
2) reunlock the phone if needed and install latest TWRP
3) in TWRP, mount all partitions, then go to the terminal
4) list selinux permissions for everything in /config
ls -RZ /config
take notes on a paper, we need to restore them later
5) change selinux permissions using
chcon -R -t config_file /config
(found this looking at /file_contexts file, line "/config(/.*)? ubject_r:config_file:s0")
6) reboot in the stock rom and wait (looking at logcat it seemed to recalibrate itself),
at some point (maybe 5min) it asked me for sim pin \o/
7) reinstall lineageos (in my case restore backup except /config)
8) change the selinux permissions of /config back to what they were (step 4)
9) reboot in lineage os and wait again (it took maybe 5 min for the phone to ask the sim card pin)
Hope this work for you
Fastboot erase config....
After that I stucked at boot logo
Used xfstk then aft but stucked at boot used fastboot commands for flashing system all gonna smooth but stucked at boot...
Used recovery to sideload marshmallow ... succeed. But also stucked at boot ..unlock boot loader flash TWRP flashing custom rom also stucked at boot logo... PLZZ help me guyzzz
And it shows error in TWRP
Unable:to mount Config(invalid argument)

TWRP: Unable to backup phone from recovery

I just bought a Nova 2, unlocked the bootloader, and installed TWRP custom recovery. Haven't used the phone otherwise. Before rooting, I just wanted to take a complete nandroid backup of the entire phone. When I do so, it fails while backing up data.
The final error I get is: createTarFork() process ended with ERROR: 255
recovery.log shows the following toward the end. Please advice. Somewhere I read that it could be due to encryption, but not sure how to overcome this issue.
Invalid encryption mode file /data/unencrypted/mode
Backing up Data (excl. storage)...
Backups of Data do not include any files in internal storage such as pictures or downloads.
Invalid encryption mode file /data/unencrypted/mode
I:Creating backup...
I:Creating tar file '/external_sd/TWRP/BACKUPS/RJCDU17907003548/2018-01-05--23-21-48/data.f2fs.win'
I:addFile '/data/encrypted_flag' including root: 0
==> set selinux context: ubject_r:system_data_file:s0
I:addFile '/data/bootchart' including root: 0
==> set selinux context: ubject_r:bootchart_data_file:s0
I:addFile '/data/local' including root: 0
==> set selinux context: ubject_r:system_data_file:s0
I:addFile '/data/local/yx8W3bT4y1rt+jDAk291rB' including root: 0
==> set selinux context: ubject_r:shell_data_file:s0
I:addFile '/data/update' including root: 0
==> set selinux context: ubject_r:cache_recovery_file:s0
I:addFile '/data/data' including root: 0
==> set selinux context: ubject_r:system_data_file:s0
I:addFile '/data/data/ToOvP+8Gnd7ynGhqdp9AfkwNnj8yYtESAx2Y7D' including root: 0
==> set selinux context: ubject_r:app_data_file:s0:c512,c768
I:addFile '/data/data/GVZV,8DUcOwIFtFJXcMPGkhUh5P499fcLlHhDD' including root: 0
==> set selinux context: ubject_r:app_data_file:s0:c512,c768
I:addFile '/data/data/GVZV,8DUcOwIFtFJXcMPGkhUh5P499fcLlHhDD/z7wMMtIY6U5cqu63JtYX5D' including root: 0
==> set selinux context: ubject_r:app_data_file:s0:c512,c768
I:addFile '/data/data/GVZV,8DUcOwIFtFJXcMPGkhUh5P499fcLlHhDD/z7wMMtIY6U5cqu63JtYX5D/CSyHTkrSrWBpz3y81z7,5FDtohM' including root: 0
==> set selinux context: ubject_r:app_data_file:s0:c512,c768
I:Error adding file '/data/data/GVZV,8DUcOwIFtFJXcMPGkhUh5P499fcLlHhDD/z7wMMtIY6U5cqu63JtYX5D/CSyHTkrSrWBpz3y81z7,5FDtohM' to '/external_sd/TWRP/BACKUPS/RJCDU17907003548/2018-01-05--23-21-48/data.f2fs.win'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/RJCDU17907003548/2018-01-05--23-21-48/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Set overlay: ''
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/RJCDU17907003548/2018-01-05--23-21-48/recovery.log
Click to expand...
Click to collapse
The filename of the image looks wired. "/data/data/GVZV,8DUcOwIFtFJXcMPGkhUh5P499fcLlHhDD/z7wMMtIY6U5cqu63JtYX5D/CSyHTkrSrWBpz3y81z7,5FDtohM' to '/external_sd/TWRP/BACKUPS/RJCDU17907003548"
Is the partition encrypted?
Which Version of TRWP are you using and how exactly did you installed TWRP?
I am using TWRP for Nova 2 (my phone) by Cofface. I believe it was version 3.2, and I installed it using the Fastboot method.
Seems it is due to TWRP not being able to decrypt the data partition

Cannot Root Magisk Canary On Samsung A505F

I have a Samsung A505F running android 10 (custom rom = HavocOS 3.1). Whenever I try to flash magisk canary, I get this error.
Code:
- Mounting /system, /vendor
! Cannot mount /system
- Unmounting partitions
Updater process ended with ERROR: 1
Edit: Fixed by installing TWRP which installs Magisk by default, but magisk manager isn't there. Also, if you get the one from Samsung A50 telegram, random reboots is fixed.
ShinyPlasm said:
I have a Samsung A505F running android 10 (custom rom = HavocOS 3.1). Whenever I try to flash magisk canary, I get this error.
Code:
- Mounting /system, /vendor
! Cannot mount /system
- Unmounting partitions
Updater process ended with ERROR: 1
Click to expand...
Click to collapse
Anything?

[HELP] TWRP Nandroid Backup ERROR: 255.

Device: OnePlus 5T (dumpling)
OS: crDroid v6.5
Firmware: firmware_H056_oneplus5T
TWRP Version: 3.3.1-20190908-0-codeworkx-signed-forcedecrypt
Add-ons: Magisk-v20.4 and MinMicroG-NoGoolag-2.7-beta2.
Hello XDA Fourm,
Every time I go to do a backup; I get an error upon backing up the "Data" partition. Here is a snippet of the "recovery.log" TWRP produced:
Code:
I:addFile '/data/per_boot' including root: 0
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/per_boot' - '3ceb982b622fe097'
I:Error adding file '/data/per_boot' to '/data/media/0/TWRP/BACKUPS/[REDACTED]/2020-04-22--23-01-37_QQ2A200405005_release-keys/data.ext4.win'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/[REDACTED]/2020-04-22--23-01-37_QQ2A200405005_release-keys/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/[REDACTED]/2020-04-22--23-01-37_QQ2A200405005_release-keys/recovery.log
Things I have tried:
Backing up everything except the "Data" partition. Back up completes successfully.
Reflashing TWRP.
Any help is appreciated.
Hi,
I'm facing the same issue.
Did you find any solution for this issue?
THX
Use TWRP file manager and go to "/data/per_boot" and delete the folder "per_boot" and try backup again it will work
Thank me later

[Fixed] FireTV Stick 2nd Gen (tank) stuck on logo. Potentially broken file system/partitions. (Unlocked + TWRP available)

Hey folks! I unlocked my FireTV stick and was able to install TWRP following the amazing guide by @k4y0z (https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-tv-stick-2nd-gen-tank.3907002/).
I can boot into TWRP just OK.
I am using adb shell to issue TWRP commands. (I don't have an OTG cable with power input).
I began by flashing stock ROMs by @0815hoffi from here (https://forum.xda-developers.com/t/...-7-ota-zip-launcher-replacement-root.4155489/).
Then I tried installing pre-rooted images by @rbox (https://forum.xda-developers.com/t/fire-tv-stick-2-tank-prerooted-stock-images-5-2-7-3_r1.3912271/) along with magisk.
Here are the general steps I followed while flashing these images :
1. wiping everything. I suspect my first issue here :
Code:
$ adb shell
$ twrp wipe cache
$ twrp wipe data
$ twrp wipe dalvik
$ twrp wipe /system
~ # twrp wipe cache
Formatting Cache using make_ext4fs...
Failed to mount '/cache' (No such device)
Done processing script file
Click to expand...
Click to collapse
~ # twrp wipe /system
Formatting System using make_ext4fs...
Failed to mount '/system' (No such device)
Done processing script file
Click to expand...
Click to collapse
~ # mount /cache
mount: mounting /dev/block/mmcblk0p12 on /cache failed: No such device
Click to expand...
Click to collapse
~ # stat /dev/block/mmcblk0p12
File: '/dev/block/mmcblk0p12'
Size: 0 Blocks: 0 IO Block: 4096 block special file
Device: ch/12d Inode: 5332 Links: 1 Device type: b3,c
Access: (0600/brw-------) Uid: ( 0/ root) Gid: ( 0/ root)
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Access: 2010-01-01 00:17:58.000000000
Modify: 2010-01-01 00:17:57.000000000
Change: 2010-01-01 00:17:57.000000000
Click to expand...
Click to collapse
2. push images to /sdcard
Code:
$ adb push update-kindle-full_tank-288.6.6.4_user_664657620.bin /sdcard/firm.zip
update-kindle-full_tank-288.6.6.4_user... 6.1 MB/s (532252995 bytes in 83.009s)
3. Install image
adb shell
~ # twrp install /sdcard/firm.zip
Installing zip file '/sdcard/firm.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
[amonet] Remove boot patch...
[amonet] OK
Patching system image unconditionally...
Copying preloader_prod.img to boot partition 0 for secure device...
script succeeded: result was [][amonet] Install boot patch...
[amonet] OK
[amonet] Install recovery patch...
[amonet] ALREADY_INSTALLED
Done processing script file
Click to expand...
Click to collapse
4. `adb shell reboot`
They all install just OK. But in all cases, every time I do `reboot` in `adb shell` after `adb install` commands, it boots and gets stuck on 'fireTV Stick' logo.
At first I thought maybe it takes time to boot for first time, but I let it go for as long as half an hour and still no good.
I tried wiping cache and dalvik before rebooting too, no avail (had same could not mount /cache prompt).
I am pretty sure I am doing something stupid, I'd really appreciate any help. I'll be happy if I get it back to a working state, I do not really need root. This all started because the stick went into bootloop outta nowhere. My initial finding pointed at a failed update, see :
https://twitter.com/i/web/status/1393963756426698756
Maybe try with 5.2.7.7
ftvs2k-5.2.7.7
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
0815hoffi said:
Maybe try with 5.2.7.7
ftvs2k-5.2.7.7
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Thanks @0815hoffi , that's actually the very first image I tried with from your thread.
Looking back, I think there's something wrong with my partitions.
If I see logs of other people from these threads, it says
script succeeded: result was [ALL DONE][amonet] Install boot patch...
Click to expand...
Click to collapse
Whereas for me, it says
script succeeded: result was [][amonet] Install boot patch...
Click to expand...
Click to collapse
This may mean that my flash is not successful, right? It's same everytime I flash.
I wonder, is there a way to bring everything to a clean state?
Given your expertise in amonet, @k4y0z from the thread and this comment, do you have a suspicion of what could be going wrong?
It looks like like it indeed were messed up partitions. My initial plan was to flash GPT fix in DL mode (by @k4y0z : link). But I thought might as well play with few things if am anyway going to re-do everything.
I started by going deleting directories manually (e.g. `rm -rf /system`). My plan was to manually flash each partition through fastboot.
Before that I attempted
Code:
fastboot format all
and received a bunch of errors, specifically
Code:
Formatting is not supported for file system with type ''.
Though format didn't work, I decided to wipe anyway
Code:
fastboot -w
It finished with few errors, but looked like it created those directories which I deleted earlier. So I rebooted to TWRP and did
Code:
twrp wipe data
Re-flashed @0815hoffi 's image and luckily it booted into "Optimising storage" screen. Post boot-up it appears to be working OK so far. Had an issue with wifi, but restart fixed it.
tl;dr
Code:
rm -rf /cache
rm -rf /data/dalvik
rm -rf /system
fastboot format userdata # errors
fastboot -w # completed but some errors
twrp wipe data
twrp install <img.zip>
reboot
EDIT : Looks like @Sus_i and @racega went through a similar journey and ended up with a similar fix. Good to know the fix is reproducible. Here's their posts : https://forum.xda-developers.com/t/...ck-2nd-gen-tank.3907002/page-61#post-83031003
saurabhshri said:
It looks like like it indeed were messed up partitions. My initial plan was to flash GPT fix in DL mode (by @k4y0z : link). But I thought might as well play with few things if am anyway going to re-do everything.
I started by going deleting directories manually (e.g. `rm -rf /system`). My plan was to manually flash each partition through fastboot.
Before that I attempted
Code:
fastboot format all
and received a bunch of errors, specifically
Code:
Formatting is not supported for file system with type ''.
Though format didn't work, I decided to wipe anyway
Code:
fastboot -w
It finished with few errors, but looked like it created those directories which I deleted earlier. So I rebooted to TWRP and did
Code:
twrp wipe data
Re-flashed @0815hoffi 's image and luckily it booted into "Optimising storage" screen. Post boot-up it appears to be working OK so far. Had an issue with wifi, but restart fixed it.
tl;dr
Code:
rm -rf /cache
rm -rf /data/dalvik
rm -rf /system
fastboot format userdata # errors
fastboot -w # completed but some errors
twrp wipe data
twrp install <img.zip>
reboot
EDIT : Looks like @Sus_i and @racega went through a similar journey and ended up with a similar fix. Good to know the fix is reproducible. Here's their posts : https://forum.xda-developers.com/t/...ck-2nd-gen-tank.3907002/page-61#post-83031003
Click to expand...
Click to collapse
Usually when this corrupted partitions happen you may try the command:
fastboot format userdata
followed by :
adb shell
(to call twrp#)
Then :
twrp wipe data
twrp wipe system
twrp wipe cache
twrp wipe dalvik
Then adb push the rom, gapps/magisk to /sdcard
twrp install nameofyourrom.zip
twrp install gappsxx.zip
Let it boot once and go back and update magisk via recovery.
(adb reboot recovery once permissions set or use powermenu little vic apk for quickness)
Another method I found which works good with fireos is :
When faced with corrupted/encrypted partition issues and/or unable to mount/format data issues
goto advanced wipe
select change file system
change it to EXT2
it will format data and data should appear become mount
hit back and change to EXT4 Filesystem again.
Then push rom and any other zips etc to /sdcard and install in usual way.
Good you got it working
Regards
Thank you for writing this down @Bertonumber1, I am sure it'll be very helpful to people who will encounter such situation in future.
Bertonumber1 said:
select change file system
change it to EXT2
it will format data and data should appear become mount
hit back and change to EXT4 Filesystem again.
Click to expand...
Click to collapse
I sincerely wish I could have done this. But I don't have an OTG with power input and deliveries are closed due to the pandemic. I was issuing TWRP commands through adb. I'll keep this in mind for future!
Thanks!
saurabhshri said:
Thank you for writing this down @Bertonumber1, I am sure it'll be very helpful to people who will encounter such situation in future.
I sincerely wish I could have done this. But I don't have an OTG with power input and deliveries are closed due to the pandemic. I was issuing TWRP commands through adb. I'll keep this in mind for future!
Thanks!
Click to expand...
Click to collapse
Ah I see, I'm sure the twrp can be commanded to repair change file systems. However, you are correct it is much easier via otg mouse or keyboard.
Regards

Categories

Resources