Related
TWRP data mount fix for oreo
As many users are facing issue because of data mount issue with TWRP on oreo, till it get fixed here is temporary solution.
Download file according root method you are using
1. For Magisk
2. For SuperSU
Installation :
- Flash downloaded file from recovery - Ignore if any message with red color regarding data mount while flashing
- Reboot to system (This step is Must)
- Done !
Now again you can reboot to recovery to check for data mount fix.
PS : You need to reflash this again after every time you flash Kernel/Root/ROM
This can be use with any working TWRP for N8/any kernel stock/custom
Credits : Credits : @Chainfire @topjohnwu @osm0sis and some International forum discussion for original idea
Thank you Dr.Ketan I am experiencing this problem.
I guess twrp will do an update
Envoyé de mon SM-N950F en utilisant Tapatalk
baloo30310 said:
Thank you Dr.Ketan I am experiencing this problem.
I guess twrp will do an update
Envoyé de mon SM-N950F en utilisant Tapatalk
Click to expand...
Click to collapse
Yes this is temporary fix, lots of users were facing lots pain with this issue, at least this will get some relief meanwhile.
For now only with magisk?
kenpaci said:
For now only with magisk?
Click to expand...
Click to collapse
I will make new later today to work on both
works for me on magisk
Envoyé de mon SM-N950F en utilisant Tapatalk
Fix updated - Now it can work on any TWRP/Kernel (working on N8). Also provided for both Magisk/SuperSU root method
PS : You need to flash again whenever you flash ROM/Kernel/Magisk/superSU
dr.ketan said:
Fix updated - Now it can work on any TWRP/Kernel (working on N8). Also provided for both Magisk/SuperSU root method
PS : You need to flash again whenever you flash ROM/Kernel/Magisk/superSU
Click to expand...
Click to collapse
Thank you Dr Ketan. I tried from scratch with the newest fix and now I have my carrier back and TWRP working and everything wonderful. Thank you for all your help and work on this!
So am I correct in saying I flash twrp then the ROM of choice then this fix?
marcushesketh1991 said:
So am I correct in saying I flash twrp then the ROM of choice then this fix?
Click to expand...
Click to collapse
Exactly
Also if you need to flash magisk/supersu then you have to flash this fix again after that
dr.ketan said:
Exactly
Also if you need to flash magisk/supersu then you have to flash this fix again after that
Click to expand...
Click to collapse
Awesome thanks our for the help
Hero
Thank you Dr.ketan. Do i have to flash this every time i flash a new rom?
Wahaj_Alden said:
Thank you Dr.ketan. Do i have to flash this every time i flash a new rom?
Click to expand...
Click to collapse
yes
Actually whenever you flash magisk/Supersu. (most ROM does that)
Thanks for the fix Dr. Katen.
I just applied it and it fixed the /data mounting issue in TWRP; However, Now I'm facing a new issue with Magisk not saving Superuser granting authorizations for root apps.
Every time I open Adaway, for example, I get the notification asking me to grant it Superuser access eventhough I have already given it that authorization few minutes ago. Same applies with every root app. I've checked the Superuser section of Magisk app and it is empty.
So I decided to uninstall the Magisk App and reinstall it again and it didn't help. Rebooting also didn't help
Code:
03-28 20:10:31.357 3219 3219 I Magisk : * Creating /sbin overlay
03-28 20:10:31.358 3219 3219 I Magisk : * Mounting mirrors
03-28 20:10:31.358 3219 3219 I Magisk : mount: /sbin/.core/mirror/system <- /dev/block/platform/11120000.ufs/by-name/SYSTEM
03-28 20:10:31.358 3219 3219 I Magisk : link: /sbin/.core/mirror/vendor <- /sbin/.core/mirror/system/vendor
03-28 20:10:31.358 3219 3219 E Magisk : mount /data/adb/magisk->/sbin/.core/mirror/bin failed with 2: No such file or directory
03-28 20:10:31.358 3219 3219 I Magisk : bind_mount: /sbin/.core/mirror/bin <- /data/adb/magisk
03-28 20:10:31.358 3219 3219 I Magisk : * Setting up internal busybox
03-28 20:10:31.359 3223 3223 E Magisk : execvpe /sbin/.core/mirror/bin/busybox failed with 2: No such file or directory
03-28 20:10:31.359 3223 3223 I Magisk : Magisk v16.2(1620) daemon started
03-28 20:10:31.489 3223 3226 I Magisk : ** post-fs mode running
03-28 23:10:31.867 3223 3312 I Magisk : ** post-fs-data mode running
03-28 23:10:31.867 3223 3312 I Magisk : * Mounting /data/adb/magisk.img
03-28 23:10:31.996 3223 3312 I Magisk : * Running post-fs-data.d scripts
03-28 23:10:31.996 3223 3312 I Magisk : * Running module post-fs-data scripts
03-28 23:10:31.996 3223 3312 I Magisk : * Loading modules
03-28 23:10:31.996 3223 3329 I Magisk : * Starting MagiskHide
03-28 23:10:31.996 3223 3329 I Magisk : hide_utils: Hiding sensitive props
03-28 23:10:31.997 3223 3329 I Magisk : hide_list: [com.google.android.gms.unstable]
03-28 23:10:32.026 3223 3329 I Magisk : proc_monitor: init ns=mnt:[4026531840]
03-28 23:10:32.861 3223 3521 I Magisk : ** late_start service mode running
03-28 23:10:32.862 3223 3521 I Magisk : * Running service.d scripts
03-28 23:10:32.862 3223 3521 I Magisk : * Running module service scripts
03-28 23:10:34.190 3223 3329 I Magisk : proc_monitor: zygote ns=mnt:[4026533640] zygote64 ns=mnt:[4026533642]
03-28 23:11:13.729 3223 8095 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:11:15.363 3223 8273 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:11:44.435 3223 9931 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:14:05.970 3223 17463 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:14:33.823 3223 18127 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:14:43.171 3223 18311 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:15:12.022 3223 18501 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:15:12.065 3223 18506 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:17:31.625 3223 20852 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:17:31.625 3223 20852 E Magisk : su: cannot find requester
03-28 23:17:31.632 20853 20853 W Magisk : su: request rejected (10194->0)
03-28 23:18:39.193 3223 21503 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:01.085 3223 22144 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:18.133 3223 22262 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:20.712 3223 22376 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:29.971 3223 22420 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:34.801 3223 22544 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:34.831 3223 22550 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:31:11.013 3223 23856 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:31:49.143 3223 24268 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:31:55.675 3223 24339 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:31:55.710 3223 24346 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:32:03.414 3223 24424 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:32:03.447 3223 24430 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:32:09.133 3223 24526 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:32:14.642 3223 24589 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:34:01.110 3223 25126 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:34:01.143 3223 25131 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:35:46.910 3223 25363 E Magisk : sqlite3 open failure: unable to open database file
Says only official released binaries are allowed to be flashed
Alright,
I have the 950F/DS XEF
Installed the latest TWRP, everything went fine
Formatted Data, everything went fine
Installed the Data fix, everything went fine
Booted system, went thru the setup, skipped everything until I got to the home screen
Tried to reboot into TWRP so I could Root. Boot Loop and Red writing at the top. Had to do a clean install. Dreaded 7 days again.
Did I miss something? Did I forget the OEM Patch?
jeraldbro said:
Alright,
I have the 950F/DS XEF
Installed the latest TWRP, everything went fine
Formatted Data, everything went fine
Installed the Data fix, everything went fine
Booted system, went thru the setup, skipped everything until I got to the home screen
Tried to reboot into TWRP so I could Root. Boot Loop and Red writing at the top. Had to do a clean install. Dreaded 7 days again.
Did I miss something? Did I forget the OEM Patch?
Click to expand...
Click to collapse
Yup, forgot OEM patch.
Always flash OEM patch after flashing any rom (or TWRP for the first time)
If flashing Oreo rom, always flash data fix after.
Always flash data fix after if flashing root and/or kernel.
Always flash root after flashing kernel.
S5Sickness said:
Says only official released binaries are allowed to be flashed
Click to expand...
Click to collapse
jeraldbro said:
Alright,
I have the 950F/DS XEF
Installed the latest TWRP, everything went fine
Formatted Data, everything went fine
Installed the Data fix, everything went fine
Booted system, went thru the setup, skipped everything until I got to the home screen
Tried to reboot into TWRP so I could Root. Boot Loop and Red writing at the top. Had to do a clean install. Dreaded 7 days again.
Did I miss something? Did I forget the OEM Patch?
Click to expand...
Click to collapse
You need to flash oem fix just after flashing twrp before you reboot
Guys. A bit quick help please? I forgot to install this zip after installing a new oreo rom. The phone works fine. But I can't mount anything from TWRP. No internal or external. How can I flash this .zip?
PREREQUISITE
- adb enabled [developer options]
- root [Magisk/SU]
- original /vendor partition [flashed with official update/firmware]
- File/Root Explorer
- adb for Windows [Minimal ADB and Fastboot, provided]
- UKA [Unpacker Kitchen for Android] - Send me a PM
- USB cable always connected
Reserved
You can do the same steps for the other logical partitions [system & product]
At the end you do :
System
tune2fs -L / /data/local/UnpackerSystem/system.new.img
tune2fs -O ^read-only /data/local/UnpackerSystem/system.new.img
tune2fs -O ^has_journal /data/local/UnpackerSystem/system.new.img
adb shell
su
dd if=/sdcard/system.img of=/dev/block/dm-2
(just copy/past to avoid errors !)
Reboot your phone right away !
Product
must be renamed vendor because the Magisk Module still doesn't support this name yet ... just rename it vendor.img before taking any action ... and after creating your image, do :
tune2fs -L product /data/local/UnpackerSystem/vendor.new.img
tune2fs -O ^read-only /data/local/UnpackerSystem/vendor.new.img
tune2fs -O ^has_journal /data/local/UnpackerSystem/vendor.new.img
NOW you can rename it product.img
adb shell
su
dd if=/sdcard/product.img of=/dev/block/dm-0
Reboot your phone right away !
"Houston, we have problem!"
Now what? Is this only for MIUI users? I have flashed Nusantara ROM right now...
Also it is possible, that you can create "default" RW images for surya, upload them somewhere on cloud (one RW system please! medium rare, thank you ... 12.0.7 is fine for me...)
... but anyway, thanks for your hard work...
BTW @brigudav already created flashable RW vendor for Surya, can that be done also for system?
jeryll said:
"Houston, we have problem!"
View attachment 5232079
Now what? Is this only for MIUI users? I have flashed Nusantara ROM right now...
Also it is possible, that you can create "default" RW images for surya, upload them somewhere on cloud (one RW system please! medium rare, thank you ... 12.0.7 is fine for me...)
... but anyway, thanks for your hard work...
BTW @brigudav already created flashable RW vendor for Surya, can that be done also for system?
Click to expand...
Click to collapse
Check your Mount Namespace Mode in Magisk Manager
No it's not only for miui, it's for all roms ! (btw i'm on LOS 17.1 ... and i never used MIUI)
Yes, you can do that for the 3 logical partitions ... this tutorial is for all devices with dynamic paritition aka super.img (not limited to poco x3 nfc !!!)
I will put a clean vendor.img later (with RW enabled and AVB-Verity Disabled)
I will put a modded version of Magisk 20.4 too if someone would use it (like me)
janhammer504 said:
Check your Mount Namespace Mode in Magisk Manager
No it's not only for miui, it's for all roms ! (btw i'm on LOS 17.1 ... and i never used MIUI)
Click to expand...
Click to collapse
- thanks for the answer, but I must say I'm unable to continue, because I'm unable to install UKA module on A11 ROM
- regardless of Mount Namespace Mode - I checked all three - with reboot - result is the same
- I'm also unable to install magisk 20.4 on A11 ROM - and with v21.0 or higher - UKA will not install
- so Id say this guide is for now useable only for A10 users
- I will test A10 ROM in a few days
- maybe there is a problem with my phone, but I reflashed full recovery version of latest MIUI before flashing custom rom together with encryption disabler, so my super partition should be cleaned up
- so using unencrypted storage could be another problem for this to work?
jeryll said:
- thanks for the answer, but I must say I'm unable to continue, because I'm unable to install UKA module on A11 ROM
- regardless of Mount Namespace Mode - I checked all three - with reboot - result is the same
- I'm also unable to install magisk 20.4 on A11 ROM - and with v21.0 or higher - UKA will not install
- so Id say this guide is for now useable only for A10 users
- I will test A10 ROM in a few days
- maybe there is a problem with my phone, but I reflashed full recovery version of latest MIUI before flashing custom rom together with encryption disabler, so my super partition should be cleaned up
- so using unencrypted storage could be another problem for this to work?
Click to expand...
Click to collapse
Hi, flash an official MIUI for your device.
Do the dirty job and save your vendor.img
Reflash your rom !
(i have already uploaded a clean vendor.img here)
I close this thread too since a lot of features have been added to this work ... and since there are many disrespectful developers-like around who steal my work and give no credit !
Check my custom vendor thread to learn more about this work !
If you have any question, send me a PM, i will check first if you are not a troll : if you get no answer from me, then understand by yourself !
@janhammer504 Hi. For the sake of the community it's always sad to see someone taking their work from XDA.
If you've got issues with other people using your work without credit here on XDA you can always reach out to someone on the moderator team for help. Or better yet, one of us on the Developer Relations team. We can help you solve any disputes and make sure you get proper credit.
You can find a list of moderators here:
https://docs.google.com/document/d/1lK5rP103OL3StU3q9iqwX9LU_k8XABeSQIAT3EHCqgM/pub
Hi,
is there any way to set selinux permissive permanently on LiR? Everything I've found and tried only works until the next reboot.
I would like to install some audio modifications, e.g. Dolby, Viper, James, etc., and I heard they require selinux permissive.
ANE-LX1 said:
Hi,
is there any way to set selinux permissive permanently on LiR? Everything I've found and tried only works until the next reboot.
I would like to install some audio modifications, e.g. Dolby, Viper, James, etc., and I heard they require selinux permissive.
Click to expand...
Click to collapse
Try to set 'permissive' using Magisk, it works similar to init.d method
(worked for me on stock EMUI, should work on LiR too):
- First of all flash in TWRP "Phenix kernel" by @TureX and wipe Dalvik/ART cache, reboot.
- open root Explorer (e.g. Solid explorer), go to directory data/adb/post-fs-data.d , create a file , rename it as selinux
- add the line
setenforce 0
in the file 'selinux' and save it.
- change the permissions of a 'selinux' file to rwxrwxrwx (777) .
- reboot.
The phone should reboot into selinux permissive.
You can change selinux status via "Termux", without reboot, if needed.
(su <enter>
setenforce 0 <enter>
or
setenforce 1 <enter>
Status:
su <enter>
getenforce <enter> ).
Maybe this will help you.
P.S.: As for installing Viper or Dolby Atmos, it's just an academic question, imo...
-Alf- said:
Try to set 'permissive' using Magisk, it works similar to init.d method
(worked for me on stock EMUI, should work on LiR too):
- First of all flash in TWRP "Phenix kernel" by @TureX and wipe Dalvik/ART cache, reboot.
- open root Explorer (e.g. Solid explorer), go to directory data/adb/post-fs-data.d , create a file , rename it as selinux
- add the line
setenforce 0
in the file 'selinux' and save it.
- change the permissions of a 'selinux' file to rwxrwxrwx (777) .
- reboot.
The phone should reboot into selinux permissive.
You can change selinux status via "Termux", without reboot, if needed.
(su <enter>
setenforce 0 <enter>
or
setenforce 1 <enter>
Status:
su <enter>
getenforce <enter> ).
Maybe this will help you.
P.S.: As for installing Viper or Dolby Atmos, it's just an academic question, imo...
Click to expand...
Click to collapse
It's a little bit complicated for me...
Thanks for your help anyway!
P.S.: what do you mean by that?
-Alf- said:
As for installing Viper or Dolby Atmos, it's just an academic question
Click to expand...
Click to collapse
ANE-LX1 said:
P.S.: what do you mean by that?
Click to expand...
Click to collapse
I mean, neither of them will work.
-Alf- said:
I mean, neither of them will work.
Click to expand...
Click to collapse
Unfortunately, you are perhaps right and it has been a vain hope. Is there really no chance to have Volte and Dolby on a custom ROM??
ANE-LX1 said:
Unfortunately, you are perhaps right and it has been a vain hope. Is there really no chance to have Volte and Dolby on a custom ROM??
Click to expand...
Click to collapse
Oreo is your friend
Hi there,
When Magisk (or adbd insecure) "patched the boot.img", and created a new file "magisk-patched-25200_random-string",
- what did Magisk do to boot.img extracted from stock firmware;
- what does "patching" mean in the context?
Thanks in advance.
Regards,
Wen
magisk will replace init binary with its own magiskinit and install its root stuff (modified SELinux policy rules with secontext u:r:magisk:s0 for magisk su daemon) and more.
https://topjohnwu.github.io/Magisk/details.html#pre-init
you have to flash that patched image from fastboot back to device yourself in order to obtain root access.
aIecxs said:
magisk will replace init binary with it's own magiskinit and install it's root stuff (modified SELinux policy rules with secontext u:r:magisk:s0 for magisk su daemon) and more.
https://topjohnwu.github.io/Magisk/details.html#pre-init
you have to flash that patched image from fastboot back to device yourself in order to obtain root access.
Click to expand...
Click to collapse
Ok, I'll look into it.
Btw: adbd Insecure v2.00 by @Chainfire won't modify boot partition, only latest SuperSU v2.79 SR3 by @Chainfire predecessor to Magisk does (although origin of systemless-root idea was born from Magisk)
This step by step tutorial is all about
☆☆☆ FastbootD video tutorial : https://m.youtube.com/playlist?list=PLvggR4skCxYzhB3SXxpSx4LvRzGwx9k45Full round-trip of "GSIs flashing process".
Step to install Stock ROM with Fastboot ability.(need 3in1.tar)
Step to flash GSI on top of Stock ROM.
get rid of SU.which came with "bvS" or "bgS" Variant.(option if you want Magisk)
Step to update GSI without lost your data include magisk.
Step to Recovery back to the First Boot with Magisk (hidden).
<<Additional for PHH AOSP>>
Add Adaptive Auto-brightness for T225 (magisk module) here
Add Face Unlock. here
<< Additional for Stock SAM A13 based>>
Add Restore Samsung Knox features.(had lost from unlocked and root)
Add Advanced Setup New LeOS
ADD DUAL BOOT WITH Vega Bobo DSU Sideloader. (SAM Stock A13 Base) Example here:
**FastbootD Help.
fastboot commands
fastboot commands. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
--info--
Sam did not provided " fastboot mode" for all devices. only "Odin flashing tool".
What is the FasdtbootD?
What is FastbootD? How to Boot to FastbootD Mode
In this tutorial, we will explain you what is FastbootD Mode in Android, how to boot to FastbootD Mode and how to exit this mode.
www.droidwin.com
*Limitation of FastbootD
FastbootD not the same as regular "fastboot", impossible to use fastbootd without " Dynamic partition. etc., dynamic partitions are automatically created, resized, or deleted as needed.
*FastbootD has access in logical partition like Super Partition.
( have odm +product+vendor+system partition inside) , Because dynamic partitions are implemented in userspace, partitions needed by the bootloader can't be made dynamic. For example, boot, dtbo, and vbmeta are read by the bootloader, and so must remain as physical partitions.
then
You can't uses by fastbootD performed
Code:
fastboot --disable-verity flash vbmata vbmeta.img
✓ Not enough space to resize partition solution
Solution:
Removing stock system_ext and/or product from fastbootd is enough, like so:
***Don't uses this command
"fastboot delete-logical-partition product"
why ?
the product partition, with around 1.3GB in size isn’t even required by the GSIs.
then you can delete data on product partition.
*(Didn't delete product partition itself but deletes only data inside this partition , then android will auto-resize product'spartition.)
Do this.
Code:
adb reboot fastboot
Code:
fastboot erase product
set the size of the product partition to 0
Code:
fastboot resize-logical-partition product 0x0
To verify if the partition size has become 0.
Code:
fastboot getvar all
If one of the lines shows the below code, then the process is a success.
Code:
(bootloader) partition-size:product:0x0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
or
>fastboot erase system_ext
>fastboot resize-logical-partition system_ext 0x0
---End Info--
Resource:
Basic knownledge.
my customAP tutorial.
** When using FastbootD you should knows
Set of fastbootd command.
-content-
Flashing Any GSIsUsing Fastboot without CustomAP 》Save your time.Example_use AOSP A13 from phhusson TrebleDroid GSI.
Complete Cycle From Fastboot Flashing >>>ROOT (Magisk,SU)>>Customized UI >>Update without Lost Data and Magisk.Requirement:
-Unlocked BootLoader
-(Recommend) Stock Firmware Update to A13 such as
"SM-T225XXU1CWA2" etc.,
Why? Used Android 13 GSIs.
1. MTP works
2. Offline Charging works
3. Google Assistant can call for you. (Ok Google call xxx) Stock A13 didn't do it.
etc.,
>Step to install Stock ROM together with Fastboot ability at the same time.
(clean install with stock firmware)
Extract AP Framework File for "recovery.img.lz4" and patch to add FastbootD ability. [ Download Attach file ] or patch by yourself here https://github.com/Johx22/Patch-Recovery.
Flash Stock Framework File with odin. (AP , BL, CP, CSC_not_home) + Magisk patch-boot & vbmeta & patch-recovery at (USERDATA Slot) ( include 3 patch-files to one tar file) [ Download Attach file ] -After reboot must connects internet and set "Developer options = enable OEM unlocking + USB debugging"
(Computer) Download and extract Platform tools to C:\ https://developer.android.com/studio/releases/platform-tools.
(Computer) Download and install Fastboot interface Driver. https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
Note:
1.you can dirty flash patched fastbootD-recovery at AP slot. When you had any firmware or gsi installed.
2.Howto magisk-patch (boot.img.lz4 + vbmeta.img.lz4). in General Section.
>Step to flash GSI on top of Stock ROM
Set of Command to install GSIs on top of Stock Firmware.
-Connect device with USB cable to Computer.
-Download your GSIs.
-Extract "GSI.img file into platform tools directory.
-open CMD inside the platform-tools folder and then type in the below command
** Check device was already connected with computer.
*** Check bootloader version (patched) is the same as your device's firmware.
0.
Code:
adb devices
1.
Code:
adb reboot fastboot
-Device will turn display into FastbootD mode
2.
Code:
fastboot erase system
option: if you founded ‘Not enough space to resize partition’) error.
Code:
fastboot delete-logical-partition product
3.
Code:
fastboot flash system gsi-filename.img
4. FastootD (pic below)Select "Enter recovery menu"
5.Recovery (pic below)
Select "wipe data/factory reset" menu
6. Recovery (pic above)
Select "reboot system now" menu
>>Finished " Flashing with FastbootD"<<
After installation.
- This variant was included with " PHH-SU".
>Step get rid of SU.(option if you want Magisk) (bvS or bgS variant)
adb shell Enter
su Enter
chmod +x /system/bin/phh-securize.sh Enter
/system/bin/phh-securize.sh Enter
* Device will auto reboot.
After this Magisk icon will show up.
Click Magisk icon to continue setup additional files and reboot.
-----------------------------------------------------------------
*Step to update GSI without lost your data include magisk.
*** (Recommended: use Magisk-Gapps, if you don't want to re-process install gapps again.)
Disable all magisk modules. (if you used another Launcher or Port it from another GSI , pleases uninstall it first.)
Flash New-Update-GSI with FastbootD
Code:
fastboot flash system new-gsi.IMG
then REBOOT System (No factory reset or wipe data)
Code:
fastboot reboot
After get rid of SU , magisk will show up.
get rid of SU
Code:
adb shell
Code:
su
Code:
chmod +x /system/bin/phh-securize.sh
Code:
/system/bin/phh-securize.sh
Note: After this magisk will works again. (with all modules you had installed .)
===End of Update Version info===
Scripts by phhusson to automatically build/CI/Release TrebleDroid GSI
more than 2 times per month
Then I write this easy additional way to update without lost your data..
>Step to Recovery back toThe First Boot with Magisk (hidden installed).
1.Run Factory Reset From Recovery by press and hold (Power+ Vol down)
2. Connect internet and enable Developer options.
3. Enable OEM unlocking & USB debugging.
4. Reboot after that Magisk setting icon will show up again.
--End update--
Happy Chinese New Year!General Section
** Compared 2 projects
** Restore Samsung Knox features.
✓ How to create Magisk patch for boot.img + vbmeta.img
extract (vbmeta.img.lz4 + boot.img.lz4) from your AP Stock
create compress one file xxx .tar with 7zip
move (vbmeta.img.lz4 + boot.img.lz4).tar (xxx.tar) to tab a7 lite
install magisk.apk on you tab a7 lite
patch the tar file. (with magisk manager)
result magisk-patch file at Tab a7 :-Download folder.
✓ Howto install fastboot driver.
How to Install Fastboot Drivers in Windows 11
In this comprehensive tutorial, we will show you the detailed steps to install the Fastboot Drivers onto your Windows 11 PC
www.droidwin.com
✓ [Add pre-patch-recovery-FastbootD]
*** S2 = can't downgrade (Android version) even firmware version.
SM-T220 A13SM-T225 A13SM-T 227U A13SM-T 225N A13T220XXS2CWA7T225XXS2CWA8T227UVLU3CVLAT225NKOU1CWA3T220XXU1CWA2T225XXS2CWA6T220XXU1CWA1T225XXU1CWA2T220XXU1CVL7T225XXU1CVL6T220XXU1CVL5T225XXU1CVL5T220XXS2CWA8T225XXU2CWB3
✓ Howto install "adb &fastboot" on PC
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
You should also replace your adb with the latest binaries by Google.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download the platform tools for windows zip file. Find out where your current adb.exe file is located. Extract the zip into that location, overwrite the old file(s).
Note: Don't delete any files from platform-tools
>>>>>>>>>>>>>>
√ Download:
Where are New AOSP A13 official?
Releases · TrebleDroid/treble_experimentations
Scripts to automatically build/CI/Release TrebleDroid GSI - TrebleDroid/treble_experimentations
github.com
Note: (Read/Write System should uses variant "vndklite".)
✓Changes PHH-SU to Magisk.
- Connect device with your computer. run below command.
Code:
adb shell Enter
su Enter
chmod +x /system/bin/phh-securize.sh Enter
/system/bin/phh-securize.sh Enter
May be didn't found phh-securize.sh only uses root file manager deleted "/system/xbin/su"
√ You can install "GAPPS" by adb shell or by Magisk-Gapps module.
(Cause we didn't have TWRP, but don't worry about TWRP.)
*install Bromite Systemwebview
*Vega Bobo DSU Sideloader (Root mode with magisk)
*this firmware can't downgrade.**S2**T225XXS2CWA6 , it will no longer be possible to roll back even to the previous firmware .
( A13"SM-T225XXU1CWA2)
* Add some T220 FastbootD -Recovery-patch
Reserved:
Option tools for customize your AOSP GSI.
Install Gapps modules with Magisk. ( For Android 13)DOWNLOAD: https://litegapps.site/index.html
CLICK NAME FOR DOWNLOAD
1. [MAGISK]LiteGapps_Nano_arm64_13.0_v2.8_official.zip (Base)
2. GoogleSearch_LiteGapps_Addon_arm64_13.0.zip. (add-on)
3. GoogleAssistant_LiteGapps_Addon_arm64_13.0.zip. (add-on)
Note: you can add add-on mod from here.
STEP. ( with magisk manager )
Flash 1 and Reboot
Flash 2 and Reboot
Flash 3 and Reboot
How to configure Google Assistant . ( For make a call )
-Set Default Digital Assistant.
Open Setting and Search with keyword " digital assistant or assistant"
-Configure OK Google.
Open Setting 》Google 》Setting for Google apps 》Search Assistant & Voice 》 Google Assistant 》Hey Google & Voice match
ENABLE Hey Google.
tom.android said:
You can install "GAPPS" by adb shell .
Click to expand...
Click to collapse
Where can I download a compatible package and what command besides adb shell do I have to run in order to install?
nirogu325 said:
Where can I download a compatible package and what command besides adb shell do I have to run in order to install?
Click to expand...
Click to collapse
readme inside archrive.
tom.android said:
readme inside archrive.
Click to expand...
Click to collapse
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
1. install root explorer app. (such as Mixplorer)
2. create directory "gapps" or anyname at /data
such as /data/gapps
3. extract archrive " TitaTheGapps.zip" to dir from 2
4. open terminal adb shell ----then su then
cd /data/gapps/tita
chmod +x ./installer.sh
5. add more space for new gapps by delete some unuseful from "/system/system_ext/apex"
Del "android.vndk.v.28,29,30,32 keep only v31
6. run script---> sh ./installer.sh
note you can use command "mount -o rw,remount /system" or used root explorer do it. (changes RO to RW) before mod system.
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
Here is what I did to install GApps on AOSP A13:
Get TheGappsInstaller-Tita archive here: https://github.com/ChonDoit/TheGappsInstaller/releases/tag/Tita (specifically: TitaTheGapps_Terminal_20221225.tar.xz)
Extract the tar archive from the tar.xz file
Follow instructions below (credits: ozmage)
adb push TitaTheGapps_Terminal_20221225.tar /sdcard/Download
adb root
adb shell
cd /data
mkdir GAPPS
mv /sdcard/Download/TitaTheGapps_Terminal_20221225.tar GAPPS
cd GAPPS
tar xvpf TitaTheGapps_Terminal_20221225.tar
cd TitaTheGapps_Terminal_20221225
chmod a+x ./installer.sh
sh ./installer.sh
tom.android said:
1. install root explorer app. (such as Mixplorer)
2. create directory "gapps" or anyname at /data
such as /data/gapps
3. extract archrive " TitaTheGapps.zip" to dir from 2
Click to expand...
Click to collapse
dapr0b said:
Here is what I did to install GApps on AOSP A13:
Get TheGappsInstaller-Tita archive here: https://github.com/ChonDoit/TheGappsInstaller/releases/tag/Tita (specifically: TitaTheGapps_Terminal_20221225.tar.xz)
*instructions*
Click to expand...
Click to collapse
Thank you both, THAT is real support.
Update: Howto update GSI without lost your data.
Update.
Flashing Any GSIsUsing Fastboot without CustomAP any longer.
tom.android said:
Update.Flashing Any GSIsUsing Fastboot without CustomAP any longer.
Click to expand...
Click to collapse
Thank you.
I have one question though.
My tab is already updated to SM-T225XXU1CWA2. In the firs step, can I just simply flash with ODIN your attached fastbootd-recovery.tar in AP slot and the 3-in-1.tar in USERDATA slot without including the stock framework file (AP, BL, CP, CSC)?
jtrakx said:
Thank you.
I have one question though.
My tab is already updated to SM-T225XXU1CWA2. In the firs step, can I just simply flash with ODIN your attached fastbootd-recovery.tar in AP slot and the 3-in-1.tar in USERDATA slot without including the stock framework file (AP, BL, CP, CSC)?
Click to expand...
Click to collapse
1. flash only 3in1.tar at AP slot. (magisk 25.2 + vbmeta + recovery-patch)
-install gsi
2. remove SU by
adb shell Enter
su Enter
bra bra bra
look at my tutorial
tom.android said:
1. flash only 3in1.tar at AP slot. (magisk 25.2 + vbmeta + recovery-patch)
2. remove SU by
adb shell Enter
su Enter
bra bra bra
look at my tutorial
Click to expand...
Click to collapse
Thank you. That's a big help.
update iconify v6.0 (extract zip file run iconify.apk ) or update from app.
Iconify • Customize Boring Android UI
Updated to v6.0.0
What's new?
• Custom battery color
• Semi Transparent Brightness bar style
• Semi Transparent QS tile style
• Semi Transparent Notification style
• 5 styles of volume panel
• Improved UI roundness
XPosed Menu: (LSPosed recommended)
• Transparent Qs Panel (Supports more rom)
• Window Level Blur and Force blur enabler for unsupported ROMs
• Vertical QS tiles
• Custom header image (GIF supported)
• Custom header clocks
• Custom lockscreen clocks (custom font supported)
• Clock and status icons background chip
Full Changelog: Click Here
Teamfly Launcher (Didn't test)
TeamFiles Launcher
A launcher which aims to provide stability, speed & customizationMore info at github.com/TeamFiles/TeamFiles-LauncherJoin t.me/loopprojects to get more updates!
store.kde.org
May be compatible with quick switch of OneUI 5.
I also have a question, is this only for SM-T225XXU1CWA2 only ? or T220 can do this too . I have T220 XAR us version android 13 gsi pixel Experience plus with magisk. I want to install fastbootD and install gsi without custom AP.. do I use this guide?
abc1054 said:
I also have a question, is this only for SM-T225XXU1CWA2 only ? or T220 can do this too . I have T220 XAR us version android 13 gsi pixel Experience plus with magisk. I want to install fastbootD and install gsi without custom AP.. do I use this guide?
Click to expand...
Click to collapse
yes u can , extract AP file>>recovery.img.lz4. boot.img.lz4. vbmeta.img.lz4. upload here if you can't patch.
Can you explain how to patch it. Thanks
abc1054 said:
Can you explain how to patch it. Thanks
Click to expand...
Click to collapse
1.boot.IMG.lz4. 2. vbmeta.IMG.lz4. patch with magisk
2.recovery.IMG.lz4. patch follow with https://github.com/Johx22/Patch-Recovery
tom.android said:
yes u can , extract AP file>>recovery.img.lz4. boot.img.lz4. vbmeta.img.lz4. upload here if you can't patch.
Click to expand...
Click to collapse
Here is my files