Is this normal?
10-12GB nothing unusual as far as I'm aware
reg66 said:
10-12GB nothing unusual as far as I'm aware
Click to expand...
Click to collapse
Thanks for the response. Can you tell me what are the things included in the system storage? Thanks in advance.
No! is the short answer! But comparing my mi pad 4, mi 9 and even old banger of a galaxy S4 has a system of 6+GB. I'm currently using Ros and that's using nearly 13+GB.
I don't know what or why, but for example, when you install Windows 7 or 10, the file or disc size might 3-4GB but once decompressed, installed with all packages etc, the installation easily takes a LOT more than that - can't remember off hand tho exactly how much! I'd guess at 20oddGB at least, but could easily be off on that one.
Why don't you google it!
You might want to try using the built in cleaner in the security app. It can wipe app and system cache that can easily take 3-5 gigs of memory and also delete unneeded packages (the original zip files) used for system updates.
Cleaner apps that you download from the Play Store are useless since they don't have root access but the built-in cleaner on the MI 9 is a system app so it doesn't need root access. It is genuinely useful but it can also delete stuff you want to keep (like your music artwork) so I always look at what it plans to clean before running it.
zydalili said:
Is this normal?
Click to expand...
Click to collapse
Yes
zydalili said:
Is this normal?
Click to expand...
Click to collapse
Yes the system will take alot of space.
But you can reduce its size by removing all but one of you redundant local backups. Next clear your cache and remove any potential encrypted data that you are not using. Sometimes you can end up with a batch of unused encrypted data if moving from a the beta EU weekly to Global stable or from Mi-Globe custom to either EU weekly or global stable.
If rooted you can keep this from happening by flashing DM No verity after flashing something new via TWRP or by flashing the boot.image from the rom that the encrypted date is originally from. One certain way to remove it is to do a factory reset or formating user data if you have an unlocked bootloader and installed TWRP.
If you are still on stock and you still have a locked bootloader, you can just use the internal cleaning program or a program such as SD Maid which is an awesome program and very much worth buying the pro version
tsongming said:
Yes the system will take alot of space.
But you can reduce its size by removing all but one of you redundant local backups. Next clear your cache and remove any potential encrypted data that you are not using. Sometimes you can end up with a batch of unused encrypted data if moving from a the beta EU weekly to Global stable or from Mi-Globe custom to either EU weekly or global stable.
If rooted you can keep this from happening by flashing DM No verity after flashing something new via TWRP or by flashing the boot.image from the rom that the encrypted date is originally from. One certain way to remove it is to do a factory reset or formating user data if you have an unlocked bootloader and installed TWRP.
If you are still on stock and you still have a locked bootloader, you can just use the internal cleaning program or a program such as SD Maid which is an awesome program and very much worth buying the pro version
Click to expand...
Click to collapse
I see no way to delete the cache partition in recovery mode (standard) as is found on other brands. Is there an option hidden somewhere?
gerhard_wa said:
I see no way to delete the cache partition in recovery mode (standard) as is found on other brands. Is there an option hidden somewhere?
Click to expand...
Click to collapse
You need to be using twrp, I take it ur on Stock
reg66 said:
You need to be using twrp, I take it ur on Stock
Click to expand...
Click to collapse
Yes I´m on the standard EEA firmware and have no intention to either unlock the bootloader nor to flash twrp and a custom rom. Thanks for the info!
The “descriptive explanation” you gave still doesn´t make a reference on how to wipe the cache partition. The cleaning app of the system doesn´t fix it and neither do SD Maid. I have since discovered that it isn’t possible to do it without unlocked bootloader and twrp, and so I will leave it at that.
gerhard_wa said:
The “descriptive explanation” you gave still doesn´t make a reference on how to wipe the cache partition. The cleaning app of the system doesn´t fix it and neither do SD Maid. I have since discovered that it isn’t possible to do it without unlocked bootloader and twrp, and so I will leave it at that.
Click to expand...
Click to collapse
You are on stock, you are overthinking the extra space. If it's not because of redundant local back ups. Its just temporary cache files. I already recommended using SD Maid and I suggested what to do if you are on stock. Otherwise your experience would be much better with the bootloader unlocked and rooted. But as you have stated for some reason you don't want to do that.
Here's a very helpful tip: If someone takes their time to give you more than just a one sentence answer, use common courtesy and click thanks. It's the only motivation for someone to spend their time helping you resolve your issue.
Partition A
Partition B
guys, have a look at the last few posts, they smell better now, huh?
I`d say, be nice to each other, isn`t hard at all, we`re not dealing with money here, is just a lifeless gadget that you may sell it tomorrow, isn`t worth getting into "philosophical" debates
have fun and enjoy the forums!
Device sold, onto Mi 9 now... ?
badaas said:
Partition A
Partition B
Click to expand...
Click to collapse
No, Partition A only on Mi9. No seamless system update on this device.
Can you explain that more clearer on how to root. I formatted my 32gb sdcard as internal storage and it's system storage are 21gb.
Sus
Related
Thanks to everyone here up front for all the awesome help available here.
I just got my Nexus 6, and no issues unlocking bootloader, installing custom recovery (TWRP), getting root and flashing ROMs/zips (currently loving Pure Nexus with xposed).
My question is regarding backups. When you backup your current setup, most of the information I've found don't show the "System Image" partition under the "System" partition when you go to make a new backup. It's quite large, and I was wondering exactly what that is, and if you need to include that in your backup. Anyone know of a helpful link that explains the partitions?
Also, if you make a bunch of backups, and move them to your computer, does that make things harder if you want to restore from a backup? Can you restore from a backup on your computer just as easily as a backup on the phone's internal storage?
Thanks again
Edit (1/15/2016):
Thanks to RMarkwald and scryan for the quick responses and info. So it seems that the system image isn't going to be needed, and backing up System, Data, and Boot will be good enough for normal backup of the phone/rom before trying something that might break the current setup.
giantninja said:
Thanks to everyone here up front for all the awesome help available here.
I just got my Nexus 6, and no issues unlocking bootloader, installing custom recovery (TWRP), getting root and flashing ROMs/zips (currently loving Pure Nexus with xposed).
My question is regarding backups. When you backup your current setup, most of the information I've found don't show the "System Image" partition under the "System" partition when you go to make a new backup. It's quite large, and I was wondering exactly what that is, and if you need to include that in your backup. Anyone know of a helpful link that explains the partitions?
Also, if you make a bunch of backups, and move them to your computer, does that make things harder if you want to restore from a backup? Can you restore from a backup on your computer just as easily as a backup on the phone's internal storage?
Thanks again
Click to expand...
Click to collapse
According to TWRP in regards to System Image: The Team Win Recovery Project has released version 2.8.7.0 of its custom recovery, known simply as TWRP. This update brings a system read-only option that's intended to help you make a pure backup of your system image that you can later flash to receive over-the-air updates after having rooted or ROMed your device.
If you move backups to your computer, you'll either need to move them back to the internal storage of your phone or USB stick to use USB OTG to restore backups.
I already rooted my phone. Where can I get the pure system image now that I can later flash to receive over-the-air updates.
rocco24 said:
I already rooted my phone. Where can I get the pure system image now that I can later flash to receive over-the-air updates.
Click to expand...
Click to collapse
why would you want to unroot your phone, loose all your info, to flash a factory image, just to get an ota? why waste your time??? you can remain rooted, grab the system.img from a factory image, flash it with fastboot, not loose any info, then just reflash SuperSU and a kernel, and be updated. factory images are here https://developers.google.com/android/nexus/images?csw=1#yakju
simms22 said:
why would you want to unroot your phone, loose all your info, to flash a factory image, just to get an ota? why waste your time??? you can remain rooted, grab the system.img from a factory image, flash it with fastboot, not loose any info, then just reflash SuperSU and a kernel, and be updated. factory images are here https://developers.google.com/android/nexus/images?csw=1#yakju
Click to expand...
Click to collapse
Thanks for the explanation. I meant the system.img not the full factory image my bad.
rocco24 said:
Thanks for the explanation. I meant the system.img not the full factory image my bad.
Click to expand...
Click to collapse
the system.img is in the factory.img, just like the boot.img, cache.img, etc..
Nailed it thanks
RMarkwald said:
According to TWRP in regards to System Image: The Team Win Recovery Project has released version 2.8.7.0 of its custom recovery, known simply as TWRP. This update brings a system read-only option that's intended to help you make a pure backup of your system image that you can later flash to receive over-the-air updates after having rooted or ROMed your device.
If you move backups to your computer, you'll either need to move them back to the internal storage of your phone or USB stick to use USB OTG to restore backups.
Click to expand...
Click to collapse
Ok, cool... So, if I want to try another ROM out, when I backup my current setup (Pure Nexus with xposed and some themes etc...), should I just backup System, data and boot? or should I backup that System Image as well? or is that System Image the snapshot of the stock ROM that the phone came with?
Thanks again
giantninja said:
Ok, cool... So, if I want to try another ROM out, when I backup my current setup (Pure Nexus with xposed and some themes etc...), should I just backup System, data and boot? or should I backup that System Image as well? or is that System Image the snapshot of the stock ROM that the phone came with?
Thanks again
Click to expand...
Click to collapse
Don't need the system image.
IIRC the system image will give you and .img file of your backup, you could then fastboot that to restore system. (I think... never tested. I believe you can do install and switch from zip to img as well...)
But for just a standard backup with TWRP so you can restore later if you have any problems... Just do as you said with the normal System (os), data (apps & app data), boot (kernel)
Not really sure who is using the system image option, or why...
scryan said:
Don't need the system image.
IIRC the system image will give you and .img file of your backup, you could then fastboot that to restore system. (I think... never tested. I believe you can do install and switch from zip to img as well...)
But for just a standard backup with TWRP so you can restore later if you have any problems... Just do as you said with the normal System (os), data (apps & app data), boot (kernel)
Not really sure who is using the system image option, or why...
Click to expand...
Click to collapse
Awesome. That's what I was thinking, but I've been wrong before, so it never hurts to verify.
Thanks!
Opps wrong thread... Lol
Do any of you know how to reduce the size of or remove the System Image partition on the phone? It's taking up over 4gb on my phone and preventing me from restoring my data partition since it's running out of space during the restore.
cstokes86 said:
Do any of you know how to reduce the size of or remove the System Image partition on the phone? It's taking up over 4gb on my phone and preventing me from restoring my data partition since it's running out of space during the restore.
Click to expand...
Click to collapse
I delete any foreign keyboards I don't need to reduce the system partition size. Delete /system/app/(GoogleHindiIME, GoogleJapaneseIME, GooglePinyinIME, KoreanIME). You can either mount system in TWRP and delete, or delete them with a root explorer if you're rooted.
JimSmith94 said:
I delete any foreign keyboards I don't need to reduce the system partition size. Delete /system/app/(GoogleHindiIME, GoogleJapaneseIME, GooglePinyinIME, KoreanIME). You can either mount system in TWRP and delete, or delete them with a root explorer if you're rooted.
Click to expand...
Click to collapse
Thanks, Jim. I can wipe my main system partition to free up some space and then restore it later so I don't need to worry about tediously going through and removing unnecessary files. My issue is the "System Image" partition which is actually just over 3GB on my phone. I cannot seem to locate this partition and clear it out so I'm kinda stuck until I can figure out how to reduce the size of this partition ie clear out files from the partition either manually or entirely.
I'm in npd90g preview flashed via twrp.if I want official ota
Just flash system image of mm latest and this downgrade doesn't brick my phone ? Can I get ota? And what other should I flash with system image ? Boot ,data and recovery also ?
I dont no much english like othetr peopel
Promblem is i root my honor5x then device get so heat up . After that i deciede to reset it factory setting i have done it but now my device is stuk in twrp loop its not going back normal condition like factory setting plz help me ........ plz
@Shakil jamali: Wrong forum. Go to Honor 5X forum and ask again.
cstokes86 said:
Thanks, Jim. I can wipe my main system partition to free up some space and then restore it later so I don't need to worry about tediously going through and removing unnecessary files. My issue is the "System Image" partition which is actually just over 3GB on my phone. I cannot seem to locate this partition and clear it out so I'm kinda stuck until I can figure out how to reduce the size of this partition ie clear out files from the partition either manually or entirely.
Click to expand...
Click to collapse
Good question. Is this system image actually a partition? Or something TWRP does combining the system image part with a few others into one file? If it is a partition would it be possible to delete it and resize system partition to make use of the extra space? I'm on a nextbit robin stock 7.1.1. Sys image shows as 3,072mb.
For some reason, i cant backup my device through twrp because of error 255. I tried unticking system, then ticked system image and somehow the backup worked. My question is, is it ok to backup with the system image instead of system? What happens when i restore? TIA
soyti2x said:
For some reason, i cant backup my device through twrp because of error 255. I tried unticking system, then ticked system image and somehow the backup worked. My question is, is it ok to backup with the system image instead of system? What happens when i restore? TIA
Click to expand...
Click to collapse
First, for your 255 error, look at this post. Get rid of the corrupted file and a normal nandroid will work.
To answer your main question, you can use the system.img as a backup. It is intended for people who want an complete, untouched system backup to restore prior to attempting a OTA update.
An alternative approach to backup/restore that works very well in N6, is Chainfire's FlashFire.
What is 12gb of "other" storage data that I can not seem to find [OP3T, 128GB]
Hello,
I just reflashed OxygenOS from Paranoid android after a clean wipe of data, system, cache etc. After set up, I realised there is 12gb of data being occupied under the "other" storage. I proceeded to factory wipe as well and I still have this 12gb of data.
I can not seem to figure out what this 12gb of data is. It is not the oem_logs. I do not have nandroid back ups. I do have around 4gb of titanium backup that I can account for. That means there is still 7gb of data that I can not seem to find.
Any help with figuring this out?
The only thing I could think of now was to wipe internal memory and flash the rom all over. Is that possible? I heard that wiping internal memory is a no no.
I have included some screenshots. If anyone needs more information, please ask.
(The massive app data is because this morning I finally gave in and redownloaded my spotify playlists. Spent 2 days trying to figure out this damn 12gb other data...)
Edit: Forgot to mention, I am on the latest OxygenOS stable. Rooted with latest Magisk and using TWRP 3.1.1-2
An update
An update.
I deleted the titanium back up. Other storage now shows 7gb.
I used DiskUsage to further pinpoint my data use. 10gb in System and 8ishGB in app data.
I checked System folder, it is 2.8 GB.
10gb minus 2.8gb means around 7gb of data that I do not know what is.
Try look into /storage/emulated directory. I had same problem and in this folder I found missing GB's of storage.
Any apk files you've downloaded, logs you've recorded all in that category. Even large flashable zip files and other firmware files are also under that category.
EatDahPewPew said:
An update.
I deleted the titanium back up. Other storage now shows 7gb.
I used DiskUsage to further pinpoint my data use. 10gb in System and 8ishGB in app data.
I checked System folder, it is 2.8 GB.
10gb minus 2.8gb means around 7gb of data that I do not know what is.
Click to expand...
Click to collapse
Twrp backups
If this happens even after clean flashing a new rom/any rom then its something wrong with the partition.
I was facing a similar issue where my internal storage was being dislpayed as 24.6GB (Instead of 54GB) total capacity.
Can be easily fixed by using twrp, Firstly create a backup of the entire Internal Storage (Media)
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Flash your rom and it would be fixed.
Mr.RooT said:
Try look into /storage/emulated directory. I had same problem and in this folder I found missing GB's of storage.
Click to expand...
Click to collapse
Hey, Do you know what exactly I am looking for in there?
vighneshpillai90 said:
If this happens even after clean flashing a new rom/any rom then its something wrong with the partition.
I was facing a similar issue where my internal storage was being dislpayed as 24.6GB (Instead of 54GB) total capacity.
Can be easily fixed by using twrp, Firstly create a backup of the entire Internal Storage (Media)
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Flash your rom and it would be fixed.
Click to expand...
Click to collapse
I think you maybe right. I have flashed a few roms around and noticed it after flashing OOS. I do not know if it was also there before.
I do not care so much about my internal storage (media), I can afford to loose and restart all over.
Will wiping the internal storage be fine? I heard on forums that it messes things up.
Ill probably use OTG USB to flash the rom again. That should be good right?
EatDahPewPew said:
I think you maybe right. I have flashed a few roms around and noticed it after flashing OOS. I do not know if it was also there before.
I do not care so much about my internal storage (media), I can afford to loose and restart all over.
Will wiping the internal storage be fine? I heard on forums that it messes things up.
Ill probably use OTG USB to flash the rom again. That should be good right?
Click to expand...
Click to collapse
I have done all sorts of things with my phone, i have even deleted the root folder using TWRP file manager and managed to bring my device back to life.
So I guess i can assure you that it wont do a thing to your phone if u wipe internal storage
Provided make sure you are using BLU-Spark TWRP.
(BLU-Spark-TWRP v45 for Nougat based roms &
BLU-Spark-TWRP V52 for Oreo based roms).
Do not use the official TWRP as it hasn't been updated since its 3.1.1.2 release.
vighneshpillai90 said:
I have done all sorts of things with my phone, i have even deleted the root folder using TWRP file manager and managed to bring my device back to life.
So I guess i can assure you that it wont do a thing to your phone if u wipe internal storage
Provided make sure you are using BLU-Spark TWRP.
(BLU-Spark-TWRP v45 for Nougat based roms &
BLU-Spark-TWRP V52 for Oreo based roms).
Do not use the official TWRP as it hasn't been updated since its 3.1.1.2 release.
Click to expand...
Click to collapse
I ended up doing the steps but I have TWRP 3.1.1.2. I am a bit out of loop, why is BluSpark better for nougat? I just knew that we needed a specific one for Oreo since TWRP had not been updated
For other people who may come here. I did follow the steps. From 5gb other data, I am now down to 0.8gb. I do not know what that 0.8gb is but ill take it for now.
Steps were
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Step 4. Flash rom, gapps, etc etc
I DID RUN into a problem at step 2. I got an error and then when wiping or flashing rom, my /data would not mount. I googled and found that if you change the data to different format, ext4 and then abck to f2fs, the /data should mount and you can do whatever.
Maybe it is because of the TWRP version, I was on the latest 3.1.1.2.
EatDahPewPew said:
Hey, Do you know what exactly I am looking for in there?
Click to expand...
Click to collapse
Every folder except emulated directory. Firstly I thought that these other folders are links to their original location, but when I deleted that folders, original folders weren't affected. But delete it at your own risk! It could be coincidence, that these folders weren't linked to original ones.
EatDahPewPew said:
I ended up doing the steps but I have TWRP 3.1.1.2. I am a bit out of loop, why is BluSpark better for nougat? I just knew that we needed a specific one for Oreo since TWRP had not been updated
For other people who may come here. I did follow the steps. From 5gb other data, I am now down to 0.8gb. I do not know what that 0.8gb is but ill take it for now.
Steps were
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Step 4. Flash rom, gapps, etc etc
I DID RUN into a problem at step 2. I got an error and then when wiping or flashing rom, my /data would not mount. I googled and found that if you change the data to different format, ext4 and then abck to f2fs, the /data should mount and you can do whatever.
Maybe it is because of the TWRP version, I was on the latest 3.1.1.2.
Click to expand...
Click to collapse
With every new update of Oneplus (wether it be Beta or Stable) the bootloader & firmware might (or might not) get updated and hence if u use the old TWRP there are chances of being incompatible with the new builds/roms. If u notice BLU-Sparks TWRP releases, they follow a trend i.e. he releases a TWRP after every major update of Oneplus Roms which is basically to make sure that the recovery is compatible with the newer builds.
So i would suggest you to use the BLU-Spark TWRP to be on the safer side.
Hope i have cleared the doubt. Cheers. Good day. :good:
vighneshpillai90 said:
With every new update of Oneplus (wether it be Beta or Stable) the bootloader & firmware might (or might not) get updated and hence if u use the old TWRP there are chances of being incompatible with the new builds/roms. If u notice BLU-Sparks TWRP releases, they follow a trend i.e. he releases a TWRP after every major update of Oneplus Roms which is basically to make sure that the recovery is compatible with the newer builds.
So i would suggest you to use the BLU-Spark TWRP to be on the safer side.
Hope i have cleared the doubt. Cheers. Good day. :good:
Click to expand...
Click to collapse
Yes! That helps. I guess I should flash the blu spark twrp soon. Or atleast when I am switching roms. Am on the last paranoid android for nougat. Will wait it out until Oreo is out on either oos or some major role.
Do you know where I can find blu spark twrp? I found blu spark kernel but could not find the twrp.
other than media files and unrecognized file extension
like .zip .apk .flac and etc
EatDahPewPew said:
Yes! That helps. I guess I should flash the blu spark twrp soon. Or atleast when I am switching roms. Am on the last paranoid android for nougat. Will wait it out until Oreo is out on either oos or some major role.
Do you know where I can find blu spark twrp? I found blu spark kernel but could not find the twrp.
Click to expand...
Click to collapse
Open the Blu-Spark thread, go to downloads, keep scrolling and you find the twrp among the kernels listed there (Latest is v8.52).
- T W R P 3.2.3-0L [Labs Mod] -
The Swiss Army Knife TWRP Mod for the Axon 7
INTRODUCTION
This was a long term project that I have been using for a long time. I created some scripts to make it easier and faster to flash new roms and quickly restore the daily driver configuration after a testing session. For easier access I modified the TWRP interface to add direct access to the scripts. They had many problems but they were good to me since I created them and I knew how to used them well, but they were not ready for other users.
But the time has come and I have cleaned up most of the annoyances in the tools and in the UI. I have named it "Labs Mod" since it allows me to have my flashing lab on the go, making it extremely easy to switch to different configurations, or recover the daily driver configuration in a few minutes. I believe it is free of major bugs and now I can concentrate on adding new scripts, and more options to the current scripts.
FEATURES
On top of the latest improvements introduced in the official TWRP 3.2.3-0, this mod offers the following added features:
Full vendor partition support (mount, format, wipe, partition image flash, TWRP backup and restore).
Integrated Bootstack backup and restore.
Modem firmware image flash
Reboot to EDL
Button to enable device mapper verity (DM-Verity) enforcing
Button to disable the eMMC write protection (disemmcwp)
Backup/Restore internal storage to the TWRP Backup folder in the external SD. Ensure you have enough free space, free space check is not yet implemented.
EDL backup zip creation. Dual zip use since the resulting zip can be installed using TWRP from the phone or using MiFlash from the computer. It offers the following package creation options:
OS: Operating system (boot, vendor and system).
GPT: Partition table only.
CONFIG: Device config data (IMEI, SN, MAC, etc).
BOOTSTACK: Boot firmware without modem.
MINIMAL: Includes GPT+bootstack+modem+recovery.
EMERGENCY: Minimal + device config.
FULL: Minimal + OS.
FACTORY: Includes Full + config.
Integrated Treble PARTY tool for creating and removing the vendor partition. Vendor partition is required for Treble ROMs. Removal is required for flashing old non-treble roms.
Lockscreen security removal. Removes password, pattern, fingerprint, etc... (in case you forget your password or the security descriptor gets corrupted).
Google account binding removal (in case you want to wipe from within recovery and test with different google accounts).
Bootloader unlock message removal.
New! Expand OS partitions (Vendor and System) to fit the whole partition. Useful for expanding the GSI filesystem for having space for adding GApps or moving apps to system.
New! Deep Wipe function performs a low level wipe of the partition data, erasing the remaining the portions of the eMMC that stored the partition information.
REQUIREMENTS
You need an unlocked Axon 7
INSTALLATION
WARNING, THIS SOFTWARE COULD WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES TWRP CUSTOM RECOVERY IN AN UNLOCKED DEVICE, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!
Follow these steps:
1. Download the TWRP Labs Mod image to your External SD card.
2. Boot to TWRP and select the Install option in the main manu.
3. Tap on the install image button and select your external SD. select the image file you downloaded, select the recovery partition and confirm.
4. Reboot to recovery again to ensure the changes are applied properly.
DOWNLOAD
TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod.img Flavor of the mod using the official TWRP 3.2.3-0 Kernel binary (Quick boot even when using F2FS, full ADB support, NO B12 Oreo encryption). Use this if you do not plan on using device encryption. Please note that you won't be able to use any tool of this version if your device is encrypted.
TWRP_3.2.3-0L_v1.3.B12-Axon7-Labs_Mod.img Device encryption enabled flavor of the Labs mod. It use the 3.2.1-8 TWRP Kernel binary (Long boot when using F2FS, NO ADB support, B12 Oreo encryption). Use this one if you use device encryption. Please note that this flavor doesn't support adb interface.
NOTES
1. I do not have the time and expertise to dig into kernel hack so this is why I do not provide a unified kernel with fast F2FS boot, ADB and B12 encryption. Probably people developing kernels could help on this issue. It would be nice having a kernel with proper F2FS boot support, B12 encryption and ADB interface. Until then, there is no other way than having 2 flavors depending on the features we require.
SOURCES
C'mon, all of them are scripts!!! the sources are at glance. Use them in your projects but don't forget to give credit to the source !!!
CREDITS
@NFound for the recovery kernel binary supporting Oreo B12 encryption.
@someone755 for the keycheck binary I use in my scripts.
@Chainfire for the TWRP install script hacks.
I hope you enjoy it as much as I did creating and learning throughout the enlightenment journey.
Nice.
Any info on the scripts that are included?
voetbalremco said:
Nice.
Any info on the scripts that are included?
Click to expand...
Click to collapse
Well, all of them are Bourne shell scripts. Some of them are stupidly simple such as those in the Reboot menu, and others in the Advanced > Oki Labs menu are very elaborated, specially:
- PARTY tool: for creating and removing the vendor partition. I released it a few days ago as a separated tool that could well work in other devices.
- EDL backup: for creating EDL flashable backups of a configuration. This tool will probably require a full thread due to the concepts involved. The big feature is that the generated zip can be also flashed using any TWRP.
- Internal Storage Backup/Restore: TWRP doesn't offer a straightforward solution for backing up the internal storage, since it is excluded from the data backup, now it is possible to create a backup and restore the contents of the internal SD in case you want to mess up with the userdata partition. Now this script creates a set of files under the TWRP/backup folder. I am planning to add the possibility of having different backup folders, the same way the GUI treats the data partition.
That is looking very sweet!!!
I'm excited, nice work man!
This is just fantastic!
Well, the non b12 version can't decrypt my device, running los 15.1
also, the lab options did nothing, and when I pressed on PARTY the recovery froze on me.
Hmm.
nfsmw_gr said:
Well, the non b12 version can't decrypt my device, running los 15.1
also, the lab options did nothing, and when I pressed on PARTY the recovery froze on me.
Hmm.
Click to expand...
Click to collapse
Well, that's why in the OP I provide 2 flavors of the mod. If you require decrypt then you have to use the B12. PARTY will not work either if your device is encrypted and you are using the 3.2.3-0L. In your case, using device encryption, you have to use the 3.2.3-0L(B12). You will have all the functions except for ADB. PARTY will work fine too.
Oki said:
Well, that's why in the OP I provide 2 flavors of the mod. If you require decrypt then you have to use the B12. PARTY will not work either if your device is encrypted and you are using the 3.2.3-0L. In your case, using device encryption, you have to use the 3.2.3-0L(B12). You will have all the functions except for ADB. PARTY will work fine too.
Click to expand...
Click to collapse
Got it.
I thought the B12 version was for stock-based ROMs.
Okay I'll flash the other one once I get home, thanks.
nfsmw_gr said:
Got it.
I thought the B12 version was for stock-based ROMs.
Okay I'll flash the other one once I get home, thanks.
Click to expand...
Click to collapse
I'll clarify it a bit more to avoid any misunderstanding. Sorry about that.
Oki said:
I'll clarify it a bit more to avoid any misunderstanding. Sorry about that.
Click to expand...
Click to collapse
Thnx for this tool ! I'll test that this weekend.
It would be great if you'd make a small guide on this with a couple of situations / a possible indepth review with screens / what's possible and what's definitely not possible with this twrp tool.
Anyway seems very promising :good:
Sheesh...i have no external sd card
I have garde flashed your TWRP_3.2.3-0L (B12) -Axon7-Labs_Mod.img but this version says when starting in twrp that my password is wrong. the version 3.2.1.8 of nfound unlocks my password quite normal
Excellent Job! I can't wait to get back my Axon 7 from RMA Services. I'm just going to need sometime to get this running coming from stock MIflavor.
Found bug. Installed the ADB version (thanks Cthulu!), wanted to check the functionality.
Went into the Storage Backup and my phone froze. Rebooting from ADB worked.
EDIT: tried to reproduce the issue - same thing happened 2nd time.
EDIT2: It freezes at any option in Oki Labs
docentore said:
Found bug. Installed the ADB version (thanks Cthulu!), wanted to check the functionality.
Went into the Storage Backup and my phone froze. Rebooting from ADB worked.
EDIT: tried to reproduce the issue - same thing happened 2nd time.
EDIT2: It freezes at any option in Oki Labs
Click to expand...
Click to collapse
I can't duplicate the issue. Are you sure you downloaded it properly? Do you have an SD card? The backup requires an SD card with enough space. Checking for free space is in the todo list for this weekend.
raystef66 said:
Thnx for this tool ! I'll test that this weekend.
Anyway seems very promising :good:
Click to expand...
Click to collapse
Not good enough!
It is downloaded properly. SD card has more than 100gb free space.
As mentioned in edit it is any option that I used in Oki Labs menu that froze my phone
docentore said:
It is downloaded properly. SD card has more than 100gb free space.
As mentioned in edit it is any option that I used in Oki Labs menu that froze my phone
Click to expand...
Click to collapse
What option are you testing? the Storage Backup? What format are you using in your SDCard? Does it happen at the beginning or after a while? Is there any file under TWRP/BACKUPS/STORAGE in your Micro SD after the failure?
@Oki this is amazing. Thank you.
Is it possible to use the recently released kernel sources from los15 to solve the issue of needing two revisions?
Is there any logical reason why many of the modified roms (especially the pixel experience) come to a point where the phone almost hangs up, you end up rebooting with the power button and when you boot up it doesn't start and only fixes itself by flashing the persistent partition?
It's already happened to me like 4 times.
The last time with the last pixel experience, I flashed persist.img and got it to boot, but after 30 seconds it rebooted itself.
In the end with the original miui it goes perfect and never fails.
What's wrong with me?
No root, no magisk... only open bootloader
wrong recovery maybe. Use lr team recovery by wzsx150 if you aren't.
Also https://forum.xda-developers.com/mi-8/help/one-repair-persist-issues-t4036919
What I don't understand is what a recovery has to do with a failure after 1 week of the persist.img partition that is read-only.
kaiseryeahhh said:
What I don't understand is what a recovery has to do with a failure after 1 week of the persist.img partition that is read-only.
Click to expand...
Click to collapse
I wrote an extensive post on this issue. First thank the gods that reflashing a persist works for you, for some it doesn't. I am guessing that you also have a copy of your persist after you have fully setup your phone backed up to your desktop computer? If not do so immediately, just in case you need it one day.
Unfortunately persist is a complex image that handles a lot of responsibility: It contains the calibration data for your sensors: bluetooth, WIFI, Camera, and data signals. It also contains your FRP data such as, google , miCloud, Pay apps etc.
If you want to avoid persist issues permanently go back to stock and don't use root.
I suspect that these issues that people have had with persist are the beginning of the end, when it comes to using root, and maybe eventually impact use of custom roms too?
I have found that I can go for months without experiencing persist issues while keeping root by restoring my phone with a fastboot stock rom. To be clear I am not talking about a recovery rom that can be flashed with TWRP. It must be a fastboot rom, with a full format, it will overwrite TWRP too, so back everything up and start clean.
Unfortunately once you start experiencing persist issues you will get them again and again. I have experienced the best long term results by using the stock rom, and I also use custom recovery and root. My parents Mi8s have never used anything but Xiaomi.EU version of stable or the Stable stock w/root and they have never had the persist issue.
I have been enjoying the new Miui 12 rom. But it has been causing a lot of issues so far. First earlier today my phone stopped connecting to Google apps, and when I rebooted, I could no longer access data. In addition, I have had trouble with phone calls.. Data works but the ability to make a phone call has been sporadic. So I will unfortunately go back to the older stable Xiaomi.EU 11.0.7 rom. Which I like, but miui 12 is such an improvement it's hard to go back.
If you want to stick with Pixel Rom, just do a clean format , and flash a fastboot rom, once setup, You should be able to use it for at least a couple of months before seeing the issue again.
Sometimes you can quickly resolve the issue by simply flashing a root patched boot image that has the the correct system signature. Flash the magisk patched boot, and you may be able to go back to normal without having to reinstall anything. But the issue will return.
Thank you very much for the explanation.
But that's what I'm saying, I don't understand why a partition that in theory is only read and no one touches, gives failures.
I guess it must be a hardware failure, I don't see any other explanation.
I've never used root.
kaiseryeahhh said:
Thank you very much for the explanation.
But that's what I'm saying, I don't understand why a partition that in theory is only read and no one touches, gives failures.
I guess it must be a hardware failure, I don't see any other explanation.
I've never used root.
Click to expand...
Click to collapse
You unlocked the bootloader, maybe this alone contributes to the issue for all of us. Also, this problem occurs on practically on every phone that allows us to unlock the bootloader and use custom Roms.
While, it is possible that it could be a hardware issue, I really don’t think so ( A short would not work without issues for months at a time. For me the issue only appears when I update
You can write to the persist if you are rooted and using a version of TWRP that allows you to write specifically to the persist partition. As I mentioned I made a very extensive thread attempting to figure this issue out myself, and I provided several resolutions.
If you never want to deal with it again then restore your persist backup, return to stock and lock the bootloader. Maybe even sell the phone and buy a onePlus 7T while they are still priced at the low $499…I am considering this myself.
No doubt, Xiaomi contributes to this issue with Mi Cloud restore being available to devices with unlocked bootloaders, I believe that they are recently starting to figure this out for themselves because you can no longer backup and restore every single app.
Also, if I am using a Miui based custom rom. My sim card does not work until I sync my device to Mi-Cloud., and because I switched to a cheaper carrier that does not allow inbound calls from overseas, I have trouble receiving a text from MI Cloud to verify my device. So, I do it manually by going to https://i.mi.com/ on my phone and selecting to find my device.
See the attached image with 2 unknown devices, I believe that this triggers the persist issue. but it can also be triggered by Google. I don’t think it's a hardware issue. Finally, these Roms all seem to use individual variations of FSTAB vendor files, changing this absolutely increases the potential for getting a persist conflict. Keep in mind that your persist partition is NOT really empty when you an issue. It’s is simply encrypted.
tsongming said:
I wrote an extensive post on this issue. First thank the gods that reflashing a persist works for you, for some it doesn't. I am guessing that you also have a copy of your persist after you have fully setup your phone backed up to your desktop computer? If not do so immediately, just in case you need it one day.
Unfortunately persist is a complex image that handles a lot of responsibility: It contains the calibration data for your sensors: bluetooth, WIFI, Camera, and data signals. It also contains your FRP data such as, google , miCloud, Pay apps etc.
If you want to avoid persist issues permanently go back to stock and don't use root.
I suspect that these issues that people have had with persist are the beginning of the end, when it comes to using root, and maybe eventually impact use of custom roms too?
I have found that I can go for months without experiencing persist issues while keeping root by restoring my phone with a fastboot stock rom. To be clear I am not talking about a recovery rom that can be flashed with TWRP. It must be a fastboot rom, with a full format, it will overwrite TWRP too, so back everything up and start clean.
Unfortunately once you start experiencing persist issues you will get them again and again. I have experienced the best long term results by using the stock rom, and I also use custom recovery and root. My parents Mi8s have never used anything but Xiaomi.EU version of stable or the Stable stock w/root and they have never had the persist issue.
I have been enjoying the new Miui 12 rom. But it has been causing a lot of issues so far. First earlier today my phone stopped connecting to Google apps, and when I rebooted, I could no longer access data. In addition, I have had trouble with phone calls.. Data works but the ability to make a phone call has been sporadic. So I will unfortunately go back to the older stable Xiaomi.EU 11.0.7 rom. Which I like, but miui 12 is such an improvement it's hard to go back.
If you want to stick with Pixel Rom, just do a clean format , and flash a fastboot rom, once setup, You should be able to use it for at least a couple of months before seeing the issue again.
Sometimes you can quickly resolve the issue by simply flashing a root patched boot image that has the the correct system signature. Flash the magisk patched boot, and you may be able to go back to normal without having to reinstall anything. But the issue will return.
Click to expand...
Click to collapse
Hm, I had a problem with persist partition on my Mi 8 too, but after 2nd flashing stock persist.img (it was taken from fastboot ROM) via TWRP all seems OK...
But I still have lots of problems with data partition on any ROM (I used xiaomi.eu beta and now I use PE+). The problems can be in files/folders, and I can't simply delete them (on PE+ I can, but the errors from recovery don't disappear...) There's 3 types of errors in data partition I had:
-Operation not permitted
-Structure needs cleaning
-No such file or directory
Now I'm going to explain how I fix these errors on xiaomi.eu:
First error (operation not permitted) can be solved by deleting some app data from system (in system settings of an app)
BUT if the "problem" path isn't app data, I have no idea what I should do... The idea is you should use system standard operations of wiping something.
Second error can be solved by "e2fsck" (fsck operation) from recovery terminal
Third error can be solved by deleting "problem" path/files IN ENCRYPTED STATE. The problem is finding them when they're encrypted. I puted in the first encrypted folder with the problem a lot of files and when I see the folder with a lot of files, I delete it(if the /data/data/*app_data*/cache/*file1* file is problem, then I put a lot of files in /data/data/*app_data* folder (this folder is the first encrypted folder after reboot) and then spend a lot of time to find this folder in encrypted state to delete it)
On PE+ I got only 3 "operation not permitted error", but, as I said, deleting works, but it doesn't "kill" errors
So, obviously, I don't like that from time to time I have errors in my data partitions. Once I didn't fix it, errors "multiplied", I woke app and saw my phone in TWRP with the hundreds errors of different types. So, it's easier to format data... (wiping doesn't give anything, only formatting)
So, does anyone know what I should do? It very looks like hardware error, because I don't see anyone else with the errors...
I guess the problem is watsapp, because always my system UI stucks for a long time (20~30 sec.), which is a signal of appearing another data error, I writed someone in watsapp or has it launched...
Here's an example of the errors (only "operation not permitted" error) on PE+
View attachment 5014159
Plovel said:
Here's an example of the errors (only "operation not permitted" error) on PE+
View attachment 5014159
Click to expand...
Click to collapse
Your log file is not accessible, you reupload it.
You are having the exact issue that I get occasionally.
Try this
The next time you are ready to complete a full format trying changing your user data and cache partition to F2FS format, then install a rom and attempt to to boot to system, some roms will boot and the issue will go away for some people. I have not been able to boot to a miui Rom using this format. However, I helped someone else via PM with this same issue and they told me that changing to F2FS, rebooting to recovery and then changing it back to ext4 work for them, and I never heard about that issue from that person again.
When I installed my recent installation of the Miui 12 5.7 Xiaomi.EU, I followed th3ese steps myself and so far no issues.
In fact, I just found how people with the OnePlus 5T used the exact same solution: https://forum.xda-developers.com/oneplus-5t/help/failed-to-mount-structure-cleaning-t3761674
Hopefully that allows you to run without issues for a while.
Good Luck!
Hi, I'm still having the same problems.
I thought everything I did as an orangefox would solve it, but it doesn't.
After 2 days with pixel experience problems again.
After 2 days with the last miui 12's beta, the mobile becomes very slow, I reboot and lose sensors and even a semi factory reset was done, in which I had lost all the applications but I was still logged in google.
Does this make any sense?
I've seen that there is a persist and a persistbackup partition
Does this come from stock? or is it a twrp add-on?
Is there a way to delete absolutely everything and leave the phone with the original partitions?
Because maybe the problem can come from there.
Also, is the partition still read/write?
I tried flashing the persist image then completely go back to china rom stock and re-lock the bootloader. but now I'm facing the same issue, because my phone got bootloop when I started to reboot due to all apps starts to be unresponsive.
tsongming said:
Your log file is not accessible, you reupload it.
You are having the exact issue that I get occasionally.
Try this
The next time you are ready to complete a full format trying changing your user data and cache partition to F2FS format, then install a rom and attempt to to boot to system, some roms will boot and the issue will go away for some people. I have not been able to boot to a miui Rom using this format. However, I helped someone else via PM with this same issue and they told me that changing to F2FS, rebooting to recovery and then changing it back to ext4 work for them, and I never heard about that issue from that person again.
When I installed my recent installation of the Miui 12 5.7 Xiaomi.EU, I followed th3ese steps myself and so far no issues.
In fact, I just found how people with the OnePlus 5T used the exact same solution: https://forum.xda-developers.com/oneplus-5t/help/failed-to-mount-structure-cleaning-t3761674
Hopefully that allows you to run without issues for a while.
Good Luck!
Click to expand...
Click to collapse
I frarmatted data in F2FS and then back to ext4
Seems good so far
Thank you)
Отправлено с моего Pixel через Tapatalk
tsongming said:
Your log file is not accessible, you reupload it.
You are having the exact issue that I get occasionally.
Try this
The next time you are ready to complete a full format trying changing your user data and cache partition to F2FS format, then install a rom and attempt to to boot to system, some roms will boot and the issue will go away for some people. I have not been able to boot to a miui Rom using this format. However, I helped someone else via PM with this same issue and they told me that changing to F2FS, rebooting to recovery and then changing it back to ext4 work for them, and I never heard about that issue from that person again.
When I installed my recent installation of the Miui 12 5.7 Xiaomi.EU, I followed th3ese steps myself and so far no issues.
In fact, I just found how people with the OnePlus 5T used the exact same solution: https://forum.xda-developers.com/oneplus-5t/help/failed-to-mount-structure-cleaning-t3761674
Hopefully that allows you to run without issues for a while.
Good Luck!
Click to expand...
Click to collapse
Damn...
Now I had "no such file or directory" error (in Chrome data)
I already fixed it, but, I guess, formatting ext4->f2fs->ext4 didn't help(
Отправлено с моего Pixel через Tapatalk
Plovel said:
Damn...
Now I had "no such file or directory" error (in Chrome data)
I already fixed it, but, I guess, formatting ext4->f2fs->ext4 didn't help(
Отправлено с моего Pixel через Tapatalk
Click to expand...
Click to collapse
Did the solution help you?
Plovel said:
Hm, I had a problem with persist partition on my Mi 8 too, but after 2nd flashing stock persist.img (it was taken from fastboot ROM) via TWRP all seems OK...
But I still have lots of problems with data partition on any ROM (I used xiaomi.eu beta and now I use PE+). The problems can be in files/folders, and I can't simply delete them (on PE+ I can, but the errors from recovery don't disappear...) There's 3 types of errors in data partition I had:
-Operation not permitted
-Structure needs cleaning
-No such file or directory
Now I'm going to explain how I fix these errors on xiaomi.eu:
First error (operation not permitted) can be solved by deleting some app data from system (in system settings of an app)
BUT if the "problem" path isn't app data, I have no idea what I should do... The idea is you should use system standard operations of wiping something.
Second error can be solved by "e2fsck" (fsck operation) from recovery terminal
Third error can be solved by deleting "problem" path/files IN ENCRYPTED STATE. The problem is finding them when they're encrypted. I puted in the first encrypted folder with the problem a lot of files and when I see the folder with a lot of files, I delete it(if the /data/data/*app_data*/cache/*file1* file is problem, then I put a lot of files in /data/data/*app_data* folder (this folder is the first encrypted folder after reboot) and then spend a lot of time to find this folder in encrypted state to delete it)
On PE+ I got only 3 "operation not permitted error", but, as I said, deleting works, but it doesn't "kill" errors
So, obviously, I don't like that from time to time I have errors in my data partitions. Once I didn't fix it, errors "multiplied", I woke app and saw my phone in TWRP with the hundreds errors of different types. So, it's easier to format data... (wiping doesn't give anything, only formatting)
So, does anyone know what I should do? It very looks like hardware error, because I don't see anyone else with the errors...
I guess the problem is watsapp, because always my system UI stucks for a long time (20~30 sec.), which is a signal of appearing another data error, I writed someone in watsapp or has it launched...
Here's an example of the errors (only "operation not permitted" error) on PE+
View attachment 5014159
Click to expand...
Click to collapse
I take this topic to comment that I remain the same (not with persist fortunately) with my failures with any custom rom.
Now I'm in stock because it's the only one that works for me in time.
The same thing happened to me as to him, structure failures, data failures, etc...
I've even tried e2fsck with erroneous sectors verification but it doesn't have that function.
This is a example
,android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
at android.database.sqlite.SQLiteConnection.open(Unknown Source:33)
at android.database.sqlite.SQLiteConnection.open(Unknown Source:5)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(Unknown Source:6)
at android.database.sqlite.SQLiteConnectionPool.open(Unknown Source:3)
at android.database.sqlite.SQLiteConnectionPool.open(Unknown Source:7)
at android.database.sqlite.SQLiteDatabase.openInner(Unknown Source:6)
at android.database.sqlite.SQLiteDatabase.open(Unknown Source:2)
at android.database.sqlite.SQLiteDatabase.openDatabase(Unknown Source:49)
at android.database.sqlite.SQLiteDatabase.openDatabase(Unknown Source:4)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(Unknown Source:138)
at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(Unknown Source:2)
at com.android.providers.contacts.aggregation.AbstractContactAggregator.<init>(Unknown Source:62)
at com.android.providers.contacts.aggregation.ContactAggregator.<init>(Unknown Source:0)
at com.android.providers.contacts.aggregation.ProfileAggregator.<init>(Unknown Source:0)
at com.android.providers.contacts.ContactsProvider2.initForDefaultLocale(Unknown Source:155)
at com.android.providers.contacts.ContactsProvider2.performBackgroundTask(Unknown Source:212)
at com.android.providers.contacts.ContactsProvider2$1.onPerformTask(Unknown Source:2)
at com.android.providers.contacts.ContactsTaskScheduler$MyHandler.handleMessage(Unknown Source:62)
at android.os.Handler.dispatchMessage(Unknown Source:19)
at android.os.Looper.loop(Unknown Source:249)
at android.os.HandlerThread.run(Unknown Source:28)
And then in the recovery if I try to repair ext4 gives me a lot of unrecoverable errors.
OjSg said:
Did the solution help you?
Click to expand...
Click to collapse
As I see, it didn't help
Отправлено с моего Pixel через Tapatalk
Hey everyone,
my op10pro became extremely buggy, system settings aren't being saved after reboot, the ui is becoming jank af, i am getting no notifications from any apps, popups are getting blocked... very annoying ****.
how can i fully format my entire system and start from scratch ? i am rooted.
i don't mean a factory reset, i already tried that. something that cleans deeper.
thanks in advance
Install a rollback package, maybe it helps (will install Android 12) or install the latest full package and format data.
I don't necessarily want to go back to an old version of Android, and i fail to see how it would help.
How do you suggest i format data ?
You can format data in recovery mate.
Or if you want a whole new OS then fastboot enhance (FE) will do it.
You can format using fastboot too but FE takes care of that.
PS: if you're restoring your apps after a wipe then that could be why it's buggy, let the system install then see how it feels, then restore only what you absolutely need.