[TOOL][Linux/Mac] Capire Le Treble | Treble without Vendor Partition - Treble-Enabled Device Development A/AB ROMS

Capire le treble
Terble without Vendor Partition
{
"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"
}
As you guys all know google recently announced the project treble with releasing android Oreo, which is coming to pixel devices and some other developers ported it to their devices.
In my opinion first rule of porting treble is “move every possible thing to vendor”, so on and so forth.
So we can boot generic system images (GSI) on treble enabled devices IF DEVICE HAVE SEPERATE VENDOR PARTITION.
On some legacy devices, we don’t see vendor partition, so developers are trying to find an unused partition (for example some OEM partitions) and using it as vendor.
When I was trying to port treble on my device found out that it doesn’t have vendor partition also OEM partition was too small and can’t be used to put files on it.
I kept working on treble but my vendor files are in “/system/vendor” (system partition)
Obviously can’t flash GSIs because I’ll lose my vendor files which exist on system partition.
This project is helping developers or users to create device specific system images (DSSI) by “copy and pasting” vendor files into GSI and recreate system image for the device.
Now everyone can enjoy treble.
 
How to use CLT, and how it works?
Requairments
GSI image
Treblized rom system image
Linux or Mac
Images must be mounted
And if rom is not fully treblized don’t worry, this script has ability to copy any blobs from system of treblized rom.
In CLT script there’s optional entry called “proprietary-files.txt”, here you can enter prop files from device tree to automatically copy every needed files to system
Also, you can add extra lines.
One Extra rule:
In CLT prop-files.txt all non-vendor lines will be forced replaced, except lines starting with “?”, which won’t replace files if GSI image has that file
Actually, CLT script is not simple copy paste, it’s mirroring files from images using “tar” to keep permissions and symlinks of files
Even for correctly enabling selinux in output image it’s reading file_contexts of both images.
Using CLT is very very very simple you don't need to be a developer, all you need to do is download CLT from github (git clone)
and run it
Code:
./CLT-ify.sh
To see CLT in action here is a youtube video for it
CLT : https://github.com/erfanoabdi/Capire-Le-Treble
example of CLT in Motorola Moto Z(griffin): https://forum.xda-developers.com/moto-z/how-to/guide-how-to-make-gsis-examples-du-aosp-t3774869
Special Thanks:
phhusson: for his great work on GSIs
badi: for name
superr: for his great kitchain

Looks promising!!

Thanks for doing this, I know this has been asked several times.
Why do you take a proprietary-files.txt? Why not simply copying vendor folder? (perhaps also product/odm/oem)
Do you plan on targetting users as well? You're losing a bit of user's freedom, and making it require a lot of more maintainance for devs
("doing something targetting users is complicated" is a perfectly valid answer )
Did you consider the pro and cons compared to my no-vendor gpt-based solution?

phhusson said:
Thanks for doing this, I know this has been asked several times.
Why do you take a proprietary-files.txt? Why not simply copying vendor folder? (perhaps also product/odm/oem)
Do you plan on targetting users as well? You're losing a bit of user's freedom, and making it require a lot of more maintainance for devs
("doing something targetting users is complicated" is a perfectly valid answer )
Did you consider the pro and cons compared to my no-vendor gpt-based solution?
Click to expand...
Click to collapse
thanks for your hard work on GSIs :good:
it's "copy and pasting" full vendor, but using proprietary-files.txt is optional as i explained in OP
i've put proprietary-files.txt option for copy pasting blobs exist in /system for not fully treblized roms.
your no-vendor gpt-based solution is amazing, it's just another simple solution

erfanoabdi said:
thanks for your hard work on GSIs :good:
it's "copy and pasting" full vendor, but using proprietary-files.txt is optional as i explained in OP
i've put proprietary-files.txt option for copy pasting blobs exist in /system for not fully treblized roms.
your no-vendor gpt-based solution is amazing, it's just another simple solution
Click to expand...
Click to collapse
Oh oops, sorry
FWIW, I'm still hoping to be able to do OTAs in my GSIs (that's quite a challenge though), but with CLT, I'm just going to brick devices

phhusson said:
Oh oops, sorry
FWIW, I'm still hoping to be able to do OTAs in my GSIs (that's quite a challenge though), but with CLT, I'm just going to brick devices
Click to expand...
Click to collapse
maybe i can add in-phone CLT-ifization, the new GSI after downloading OTA on updater app

Is it possible to use it on device which doesn't have stock oreo release? For example HTC one m8 which last stock was marshmellow.

djlukas1983 said:
Is it possible to use it on device which doesn't have stock oreo release? For example HTC one m8 which last stock was marshmellow.
Click to expand...
Click to collapse
i'm not sure but worthy to try
need to build a rom with https://review.lineageos.org/#/c/LineageOS/android_device_xiaomi_msm8996-common/+/206015/
and a good prop-files.txt contains needed system blobs.

will it support exynos 8895 note 8?

It is amazing, I want to ask if it would work with nougat bloobs, if not i will have to wait to oreo or any oreo custom rom, thanks a lot and keep it upgraded, it is a great news for all treble lovers without a treble compatible device

Hello everyone! I believe the Asus Zenfone 4 has this implementation of Treble. If you got any ROMs to test under this implementation, let me know!

erfanoabdi said:
i'm not sure but worthy to try
need to build a rom with https://review.lineageos.org/#/c/LineageOS/android_device_xiaomi_msm8996-common/+/206015/
and a good prop-files.txt contains needed system blobs.
Click to expand...
Click to collapse
Will it be possible to use GSIs' on older devices like HTC Desire 816?? Sorry because its a noob type question:silly:

Is it possible to have some detailed instructions on how to make our own Capire Le Treble roms for our devices?

what is the difference between GSI image and Treblized rom system image?

khaledose said:
what is the difference between GSI image and Treblized rom system image?
Click to expand...
Click to collapse
They are same.
GSI - Generic System Image
A system image which can be flashed in all treblized devices. And that is why it is Treblized rom system image.

hemant_jeengar said:
They are same.
GSI - Generic System Image
A system image which can be flashed in all treblized devices. And that is why it is Treblized rom system image.
Click to expand...
Click to collapse
Nope
If you guys read the title
It's for treble enabled devices without vendor partition
System image of treblized is the system image only for the device and have /vendor folder
Not vendor symlink

This is amazing, I'm going to be trying to utilize this on Motorola Nexus 6, shamu. Thank u for your great work. Seriously.amazing.

Do you know how to get Android P on Treble devices ? I flashed Pixel2XL system.img on Redmi Note 4 after installing treble support and it doesn't boot. If I look in /system in TWRP theres only a bin folder so something is wrong with the img format or something

Curi0 said:
Do you know how to get Android P on Treble devices ? I flashed Pixel2XL system.img on Redmi Note 4 after installing treble support and it doesn't boot. If I look in /system in TWRP theres only a bin folder so something is wrong with the img format or something
Click to expand...
Click to collapse
Oh god ?????
That's a device specific image. You need a gsi

erfanoabdi said:
Nope
If you guys read the title
It's for treble enabled devices without vendor partition
System image of treblized is the system image only for the device and have /vendor folder
Not vendor symlink
Click to expand...
Click to collapse
@erfanoabdi
Is it for Treble devices without a dedicated /vendor partition OR devices without Treble support?
This story from the XDA Portal (https://www.xda-developers.com/motorola-moto-z-android-p/) says that the Moto Z in question does not support Treble, yet he used your script.
Can you please clarify?
Edit: And what if I repartition my device to make a /vendor partition? What's left to be done for Treble?

Related

[SM-T580][SM-T585][UNOFFICIAL] 20180906 Treble Project 64Bits

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. flash my twrp from link above - this is latest twrp with system_image support, it need to restore system treble images
2. download system image from https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Known Issues
1. rotate sensor working, but strange - on rotate tablet show black screen for a moment and then back to normal in right state
2. SM-T580 only: gps
Links
Treble images
SM-T585:
1. 20180827: initial treble: https://drive.google.com/file/d/1uX5JYqLCTMPpT5Zx2Wvi0U-Ms49S0YrW/view?usp=sharing
2. 20180904: camera recording in oreo images, both sdcards in pie images: https://drive.google.com/file/d/1cTEXJb9n5oZad0O3DXT5nlEhnlBDP6QB/view?usp=sharing
3, 20180906: remove shim for mediaserver - only for pie!!!: https://drive.google.com/file/d/1C0MfHt0SNYL4hD-BtOj3i7O_qBBPD25t/view?usp=sharing
SM-T580:
1. 20180828: initial treble: https://drive.google.com/file/d/1sgB1xQjRWyGM1OfF73Yhl5vRNunP04iK/view?usp=sharing
2. 20180904: camera recording in oreo images, both sdcards in pie images: https://drive.google.com/file/d/13WL9_Q_WoStf0WVHbmoYaL2CHbCluzNO/view?usp=sharing
3, 20180906: remove shim for mediaserver - only for pie!!!: https://drive.google.com/file/d/15dN2DugPBjhi_m0SOy4qYwVmR03nyY69/view?usp=sharing
Root
Use Magisk, it's should work. If during install Magisk give error about missed /vendor, run my prepare script and the install Magisk: https://drive.google.com/file/d/10JnOtyF5Y_4q1OE3FOZYPDcR7TK1jRhA/view?usp=sharing
GApps - Pie only!!!
Right now on T580\T585 pie images with gapps dnw, it's stuck on the start wizard, what is strange.
Solution: flash image without gapps and then flash gapps. It's working. I'm playing right now with aosp 9.0 and gapps.
We have 32bit recovery and right now standalone gapps think about arm and 6.0.1 version, what is wrong. I took gapps from https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141 and fix script inside to arm64 and right sdk version, this is gapps with my fix, what should work on T580\T585: https://drive.google.com/file/d/1kkHUPSznfibcER0DV89GhDdepEjqjCl9/view?usp=sharing
How install gapps:
1. install treble image, then pie system image
2. boot to system
3. restart to twrp and install gapps
4. boot to system, go to play market and login
For now working only this sequence
Recovery
SM-t585:
1. twrp-3.2.3-0: https://drive.google.com/file/d/16D-sFDt41n-wxNu1A0q01oRRKiZ-AsfF/view?usp=sharing
SM-T580:
1. this is original twrp (from https://dl.twrp.me/gtaxlwifi/twrp-3.2.3-0-gtaxlwifi.img.html), I just added system_image support and repack: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
All firmware say about wrong vendor version. This is normal, just press OK.
System images:A only and 64Bits
Checked firmwares
Almost all oreo roms from treble's thread working.
Even new Android 9.0 Pie roms working, but it has issue with sdcard, it will require additional checks from me.
Installation
1. (optional): "Wipe\Format Data": type yes and press ok
{
"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"
}
2. wipe data: "Wipe\Advanced Wipe" and select "Dalvik/ARP Cache" / "Data" / "Internal Storage" / "System" / "Cache"
3. install treble: "Install", then navigate to lineage-15.1-20180827-treble.zip and "Swipe to confirm Flash"
4. install system: "Install", then press "Install Image" then navigate to system images, then select "System Image" and "Swipe to confirm Flash"
5. reboot
let's experiment together!
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. go to the current twrp and full wipe
2. flash my twrp - this is latest twrp with system_image support, it need to restore system treble images (twrp-3.2.3-0-gtaxlltexx.img): https://drive.google.com/file/d/16D-sFDt41n-wxNu1A0q01oRRKiZ-AsfF/view?usp=sharing
3. flash zip with vendor data and boot image (lineage-15.1-20180827-treble.zip): https://drive.google.com/file/d/1uX5JYqLCTMPpT5Zx2Wvi0U-Ms49S0YrW/view?usp=sharing
4. now you device is ready to flash any treble system image from: https://forum.xda-developers.com/project-treble/trebleenabled-device-development - download img, copy to sdcard and then flash as system image in twrp
5. if you wanna check another rom, just make 1-4 again
Known Issues
1. video-recording
2. rotate sensor working, but strange - on rotate tablet show black screen for a moment and then back to normal in right state
All firmware say about wrong vendor version. This is normal, just press OK.
System A only
Checked firmwares
Almost all oreo roms from treble's thread working.
Even new Android 9.0 Pie roms working, but it has issue with sdcard, it will require additional checks from me.
let's experiment together!
Click to expand...
Click to collapse
You are amazing dude thanks so much for releasing this to us. Keep up the great work.
Wow, can you Do the same for the WiFi Version SM-T580?
This is by far the best news for our device. I am wondering if when we'll get official Oreo, Samsung will provide us with a treble rom as well.
Thanks Valera for you support.
I get "No OS installed"
Wow. Good job, my friend! I already want to try it on T580 wifi version. I remember that the roms of t585 work in the wifi version, can you flash this without problems?
Many cravings
Thank you!
paulo boë said:
I get "No OS installed"
Click to expand...
Click to collapse
just ignore this error. look like twrp not quite correctly handle the situation with restore via system_image and think that there is no system.
alanloax said:
Wow. Good job, my friend! I already want to try it on T580 wifi version. I remember that the roms of t585 work in the wifi version, can you flash this without problems?
Many cravings
Thank you!
Click to expand...
Click to collapse
I can build version for t580, the kernel and almost all stuff is not a problem, question only in the gps. In the t585 it's connect to the ril, but t580 using own gps chip. I don't know, where I can get 64bit binary for it. In case of t585 i'm using proprietary bin\libs from a5'17. Need to check, can I use 32bit gps in 64bit system.
And may be can be a problems (not sure now) - all treble's images created for phones. tablet with lte is close to phone, but not a witi version. but in any way - it's need to check.
Valera1978 said:
I can build version for t580, the kernel and almost all stuff is not a problem, question only in the gps. In the t585 it's connect to the ril, but t580 using own gps chip. I don't know, where I can get 64bit binary for it. In case of t585 i'm using proprietary bin\libs from a5'17. Need to check, can I use 32bit gps in 64bit system.
And may be can be a problems (not sure now) - all treble's images created for phones. tablet with lte is close to phone, but not a witi version. but in any way - it's need to check.
Click to expand...
Click to collapse
Oh I understand. Luckily I use little the gps. At least to try haha.
Thank you very much again for contributing to these devices, very good work!
Valera1978 said:
just ignore this error. look like twrp not quite correctly handle the situation with restore via system_image and think that there is no system.
Click to expand...
Click to collapse
And still it reboots over and over. The Galaxy Tab logo, then 6 7 secs black screen and the the Galaxy tab logo again.
paulo boë said:
And still it reboots over and over. The Galaxy Tab logo, then 6 7 secs black screen and the the Galaxy tab logo again.
Click to expand...
Click to collapse
Did you flashed anything other than rom? Magisk, gapps?
EugenStanis said:
Did you flashed anything other than rom? Magisk, gapps?
Click to expand...
Click to collapse
Nope, but I kinda forgot to mention that I use it on the T580
Hey, very good job. Please make a 580 version, GPS doesn't matter. You said it was experimental.
paulo boë said:
Nope, but I kinda forgot to mention that I use it on the T580
Click to expand...
Click to collapse
It's cannt work on T580 right now, because treble require changes in DTB. Without DTB changes system cann't mount /cache as /vendor and you will get boot before animation.
Will try build T580 today.
Please someone check version for T580
Valera1978 said:
Please someone check version for T580
Click to expand...
Click to collapse
And the twrp for t580? Cuz when I flash I get "this is for wifi this is lte"
Also can you post some screenshots with a link to the treble rom that works?
paulo boë said:
And the twrp for t580? Cuz when I flash I get "this is for wifi this is lte"
Click to expand...
Click to collapse
are your right now on twrp for lte? In this case in the gtaxlwifi-20180828-treble.zip - go to "\META-INF\com\google\android\updater-script" and remove first line with assert
Or you can use my twrp repack for t580: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
this is original 3.23 version, I added only system-image
Valera1978 said:
are your right now on twrp for lte? In this case in the gtaxlwifi-20180828-treble.zip - go to "\META-INF\com\google\android\updater-script" and remove first line with assert
Or you can use my twrp repack for t580: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
this is original 3.23 version, I added only system-image
Click to expand...
Click to collapse
I flashed it. Tried to flash a img, but still reboots back into galaxy logo
paulo boë said:
I flashed it. Tried to flash a img, but still reboots back into galaxy logo
Click to expand...
Click to collapse
can you send me /data/tombstones and /proc/last_kmsg?
SM-T285YD
Hi,
I have twrp for SM-T285YD but I cannot find any rom for my SM-T285YD. So can I flash this rom in my SM-T285YD.
If not then tell me what I need to do to get it working in my SM-T285YD and also I have the twrp but tell me how can make my twrp treble supported twrp....
Best regards....

Development MARS_SOMs - Stock - VoLTE, VoWifi, Carrier Video Calls

MARS SOM
{
"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"
}
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into a simple Magisk Module.
Features:
Ported Pixel Apps
Ported Pixel Features
Ported Pixel UI & Colors
Ported Pixel Black Dark Mode
Xperia Sound Enhancements
Xperia Pro-I Content Ported
HTC UI & User Sounds
Xperia Live Wallpapers
Enabled various Android Features
Enabled various Hardware Features
Enhanced Security Support
Enhanced Display Quality
Enhanced Audio Output
Enhanced Audio Input
Enhanced FHD/4K HDR Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Stable 24+
Android 13 Stock Xperia FW
Magisk Init.d Injector
Download:
Sign in - Google Accounts
Bugs:
Report them if You found one!
Donations:
paypal.me/miustone​
Reserved <3
Nice work. I'm glad to already see some custom ROMs (well, in that case, SOM).
However, this is the first time I encounter a SOM, is it just a Magisk module that can be turned on and off at will, switching between stock and Mars? Or shouldn't I do that?
Miustone said:
Welcome to MARS SOM
The first so called SOM
Systemless-On-Memory
SOM - The right naming for a new age of Android ROMs
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into two Zip Files...
Features:
Full Camera API2 Support
Full Pixel User Interface
Full Darkmode Support
Ported Pixel Apps
Ported Pixel Features
Enabled various Android Features
Enhanced Security Support
Enhanced Display 4K HDR Support
Enhanced Audio Output
Enhanced Audio Input
Enhanced Display Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Beta or Canary Channel
Android 11
A way to extract and create Zip Files
(For GitHub Zips)
Downloads:
Miustone - Overview
Founder of Dev Ice Software Technologies. Miustone has 10 repositories available. Follow their code on GitHub.
github.com
Note: Zips from GitHub can't be flashed ootb.
GitHub?!:
Extract the 2 Downloaded Zips and repack everything inside of the second "MARS_SOM_XXX" Folders to Zips
Flash these Zips with Magisk and enjoy <3
Bugs:
QuickSwitch is needed for the Pixel Launcher
Donations:
paypal.me/miustone​
Click to expand...
Click to collapse
Could you please tell me where can I obtain more information about this "Mars Som" and more details instruction to install it. Thanks for your reply.
Thanks for Your Interest! I'm reconstructing the SOMs on GitHub and the ReadMe's there will be updated soon with more Infos! For now, just Check My (Discontinued) MARS-SOM Repo on GitHub...
BR
Hrm guessing this isnt rdy yet? Just tried installing the base and rom in Magisk 23 as modules but it causes a bootloop. Noticed on GitHub says android 12 is required?
tonysunshine said:
Hrm guessing this isnt rdy yet? Just tried installing the base and rom in Magisk 23 as modules but it causes a bootloop. Noticed on GitHub says android 12 is required?
Click to expand...
Click to collapse
Sorry for the Issues! Could You try again now? I have removed the Vendor stuff for now...
Can You also try to use them seperated? I do actually not own the 1 III so i can't test Myself. Feel also free to collab. with Me on GitHub
Miustone said:
Sorry for the Issues! Could You try again now? I have removed the Vendor stuff for now...
Can You also try to use them seperated? I do actually not own the 1 III so i can't test Myself. Feel also free to collab. with Me on GitHub
Click to expand...
Click to collapse
Hi what do you mean by use them separated? Like install/activate the base module, reboot, then do the system module?
Yep, it could be one of them or both which causes the Bootloops. I updated the Base so it might be that... The System should cause less Problems at the end... @tonysunshine
I also got a bootloop after installing the zips. I tried following the instructions on your github and was able to do the device simulation with the props config module, but can't follow the next step "Download and extract the NgaResources.apk to /MARS_SOM_SYSTEM/system/product/app/NgaResources" as there's no NgaResources.apk file anywhere on the github that I can find. Could it be this missing file that's causing issues?
Xperia 1 III here.
I followed the steps on github and everything went smoothly even after I flashed the MARS_SOM_BASE zip. However, after flashing the MARS_SOM_SYSTEM , I stuck in a bootloop. I have downloaded the MARS_Product_Overlay apk and place it.
I am willing to help if you need further info.
akkk44 said:
Xperia 1 III here.
I followed the steps on github and everything went smoothly even after I flashed the MARS_SOM_BASE zip. However, after flashing the MARS_SOM_SYSTEM , I stuck in a bootloop. I have downloaded the MARS_Product_Overlay apk and place it.
I am willing to help if you need further info.
Click to expand...
Click to collapse
Wow, I'm glad the BASE zip worked so far. You are getting a lot out of it. But I'm pretty sure there will be bugs around somewhere...
And thanks a ton for Your Post! I'm on the go but if You want to test around...
Move folders out of the _SYSTEM /system Folder like /product, /vendor and so on. Start with removing all except for one Folder and try if it boots up. If You can tell Me which folder causes issues or even which files will I handle it on GitHub for You.
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Miustone said:
Wow, I'm glad the BASE zip worked so far. You are getting a lot out of it. But I'm pretty sure there will be bugs around somewhere...
And thanks a ton for Your Post! I'm on the go but if You want to test around...
Move folders out of the _SYSTEM /system Folder like /product, /vendor and so on. Start with removing all except for one Folder and try if it boots up. If You can tell Me which folder causes issues or even which files will I handle it on GitHub for You.
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Click to expand...
Click to collapse
I wanna help but recovering from bootloop is a real pain in my a**. I somehow managed to disable all magisk moudules and get out of boot loop but I am not sure if I can do it again. The only two methods I knew about getting out od a bootloop is removing modules with TWRP but currently 1 iii doesn't have one, the other method is using the adb command but I am not sure how to send adb commands to the phone while it stucked in a bootloop.
Any ideas?
akkk44 said:
I wanna help but recovering from bootloop is a real pain in my a**. I somehow managed to disable all magisk moudules and get out of boot loop but I am not sure if I can do it again. The only two methods I knew about getting out od a bootloop is removing modules with TWRP but currently 1 iii doesn't have one, the other method is using the adb command but I am not sure how to send adb commands to the phone while it stucked in a bootloop.
Any ideas?
Click to expand...
Click to collapse
You can simply hold Volume down while booting to get into "Recovery Mode". It disables all Modules and most Apps. You can reboot from that into the normal state again... Should mention that somewhere I think... (It's a Magisk Feature too)
Edit: Does not work with USB Connected! Hold Volume down after You see the Bootloader Unlocked Message. Keep holding until You are in Android
Edit 2: Think Ill make Video guides too for some needs if there is enough Interest...
Miustone said:
You can simply hold Volume down while booting to get into "Recovery Mode". It disables all Modules and most Apps. You can reboot from that into the normal state again... Should mention that somewhere I think... (It's a Magisk Feature too)
Edit: Does not work with USB Connected! Hold Volume down after You see the Bootloader Unlocked Message. Keep holding until You are in Android
Edit 2: Think Ill make Video guides too for some needs if there is enough Interest...
Click to expand...
Click to collapse
Understood! I will test the module out sometime……
akkk44 said:
Understood! I will test the module out sometime……
Click to expand...
Click to collapse
Great! Thanks in advance!
Miustone said:
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Click to expand...
Click to collapse
I tried there, but the file mentioned on the github readme (NgaResources.apk) isn't there - just these two:
tardis_42 said:
I tried there, but the file mentioned on the github readme (NgaResources.apk) isn't there - just these two:
View attachment 5445471
Click to expand...
Click to collapse
Thanks for pointing out. I'm uploading the latest Version to this Google Drive Directory rn! Sorry for the Trouble...
Updated the Thread, MARS_SOMs and GitHub<3
HUGE UPDATES INCOMING!
MARS will be available over GitHub Releases so You can easily Download ready-to-use Zips of MARS for Magisk. Also included are now OTA Updates for MARS over Magisk and the focus Changed to GSIs again. Use PHH AOSP 12 or PIXEL EXPIERENCE 12 by Ponces to unleash Your Xperias

Themes / Apps / Mods [DEV] Kernel Flasher

{
"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"
}
Kernel Flasher is an Android app to flash, backup, and restore kernels.
Features
Flash partition images and AK3 kernel zips
Backup and Restore kernel partitions
Mount, Map, and Resize vendor_dlkm
Save dmesg, logcat, and ramoops
Check for kernel updates
Notes
When making a backup of the active slot, to save time, it is assumed that the kernel on disk is the same as the running kernel. The Check Kernel Version button can retrieve it from disk prior to backup.
Depending on the method used, the updated contents of vendor_dlkm may not be immediately available for backup after flash or restore. This can be resolved by unmounting, unmapping, then remapping it.
AK3 helper modules are not backed up.
Credits
@osm0sis for AK3, feedback, and general guidance
@eng.stk & @Freak07 for feedback, advice, and encouragement
@phhusson for lptools
@topjohnwu for Magisk and libsu
Latest Update
2023-02-20 v1.0.0-alpha13
Hi, great app!
Can you please leave the kernel installation log opened after the process ends with an error? Currently it's impossible to see what went wrong since the log disappears instantly and is being replaced by an error screen.
Nezorflame said:
Can you please leave the kernel installation log opened after the process ends with an error? Currently it's impossible to see what went wrong since the log disappears instantly and is being replaced by an error screen.
Click to expand...
Click to collapse
That is already done in my own personal test version of the app, but I haven't had a chance to clean it up and get it released. I'll make an effort to get that done this evening.
I've got several other enhancements planned, but most of my focus has been on Hashtree Patcher lately, though I think that is nearly wrapped up. I'll try to get the installation log issue fixed asap, then I'll work on the rest over the next few days.
I pushed a new build that resolves the installation log issue. Here is the full changelog:
added option to backup AK3 zips
disabled flash and restore on inactive slot
added save ramoops button
added stderr to AK3 logs
added .log file extension to log files
filtered ui_print and progress in AK3 logs
sorted backups
Click to expand...
Click to collapse
I also added a list of planned and potential features to the OP. If you've got some interest in seeing any of them or anything I may have missed in a future build, feel free to note it here. If the list gets to be too big of a pain to maintain here, I may request that they go to the issue tracker, instead. Note that I don't currently plan to add kernel tweaks to the app.
Edit: There was a bug in the v1.0.0-alpha03 build that caused it to crash frequently. This has been fixed in v1.0.0-alpha04.
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
osm0sis said:
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
Click to expand...
Click to collapse
Hum installed fine on mine, maybe github acting up?
md5:
KernelFlasher-v1.0.0-alpha04.apk 94a1b66b29e95e23c918b054b9b3b1d6
eng.stk said:
Hum installed fine on mine, maybe github acting up?
md5:
KernelFlasher-v1.0.0-alpha04.apk 94a1b66b29e95e23c918b054b9b3b1d6
Click to expand...
Click to collapse
I have that checksum too but it's not working, maybe it's minimum Android 12?
Edit: Yep! Can the minimum API be lowered to support Android 11?
osm0sis said:
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
Click to expand...
Click to collapse
osm0sis said:
I have that checksum too but it's not working, maybe it's minimum Android 12?
Click to expand...
Click to collapse
Yes, I was playing with the new Splashscreen API, which requires Android 12, and I don't have an Android 11 device to test on, so I just set minSdk to 31. I'll see if I can get it to build against something lower.
I pushed a new build that will hopefully work on Android 11. Here are the changes:
lowered minSdk to 30
added vbmeta to raw partition backups
fixed vendor_dlkm map and mount
Click to expand...
Click to collapse
Note: With verity enabled, you may have to unmap vendor_dlkm twice, once for the verity device and again for the actual partition. The partition is remounted without verity, though I'm not sure there's a scenario where it's necessary to remount it at all.
capntrips said:
I pushed a new build that will hopefully work on Android 11. Here are the changes:
Note: With verity enabled, you may have to unmap vendor_dlkm twice, once for the verity device and again for the actual partition. The partition is remounted without verity, though I'm not sure there's a scenario where it's necessary to remount it at all.
Click to expand...
Click to collapse
Thanks! Crashes after the splash screen on my OP8T on OOS11, not seeing anything in the logcat however..
osm0sis said:
Thanks! Crashes after the splash screen on my OP8T on OOS11, not seeing anything in the logcat however..
Click to expand...
Click to collapse
I pushed a new build that hopefully fixes the issue. It now makes it to the point where it requires root to continue on an Android 11 AVD. I assume if it makes it to that point, the rest will work as expected. Anything beyond that, and I'll have to root the AVD to test it (though I did see an article about that a few weeks back, and it seemed simple enough).
Now works on lineage 18.1 Sony xz2 slot a/b device
A few random thoughts/ideas while testing on my 8T :
Got some errors trying to backup on my 8T since there's no vendor_boot, so I guess some logic will be needed for whether they exist.
Probably the feature should be like "backup slot" and save init_boot, boot, vendor_boot, dtbo, recovery, vendor_dlkm and vbmeta from the chosen slot if any of them exist.
If vendor_dlkm doesn't exist on an older device it doesn't make sense to show "Not Found" all over the place, nor offer to allow me to map it, it should hide those messages/buttons and just only show boot or whatever other partitions exist on the device.
If the reboot button had a ... to reveal an advanced reboot menu (menu items like the Magisk app) that would be excellent!
Magisk/RebootEvent.kt at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Magisk/XSU.kt at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Overall looking really good! Exciting to see a well written free alternative.
osm0sis said:
A few random thoughts/ideas while testing on my 8T
Click to expand...
Click to collapse
All good ideas. Probably good enough to check by path for the existence of a partition, rather than finding and parsing fstab. My next two weeks are brutal, but I'll see if I find some time to fiddle with it in there.
When you have time to work on the next update, would it be possible to make boot image flashing possible (External ones, not just saved backups), as well as zips?
shoey63 said:
When you have time to work on the next update, would it be possible to make boot image flashing possible (External ones, not just saved backups), as well as zips?
Click to expand...
Click to collapse
The backup format is very basic. You could easily drop the image you want into the backup folder and create the properties file. I'll take a look at adding something to simplify direct flashing in the next few revisions. I'm out of pocket through the weekend and will probably need a few days of catch-up when I get back.
----- posted in error ------
can I flash an uncompressed boot.img file with this app? the github only mentions flashing an AK3 zip file, so I was curious
sorry, I see the other reply. I'm hoping this app gets this feature in a future update soon. making a video about this app right now
Doesn't open up on Pixel 6. Anyone has a similar problem?
radekmazur said:
Doesn't open up on Pixel 6. Anyone has a similar problem?
Click to expand...
Click to collapse
Does it throw an error message? If not, is there anything in the logcat?

How To Guide [GSI][PHH][13] Guide & Support [Mojito][Sunny]

Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯​Yes. But this thread exists due to the following reasons:
You don't wanna fear about devs stop shipping updates.​
You don't wanna re-flash your custom recovery / kernel after each update.​
Unlike some ROMs, no clean flashes necessary after you update.​
You don't wanna be a flashoholic / beta tester of a ROM maintainer.​
GSIs are like Linux Distros. Flexible, hasslefree & minimal.​
All GSIs support signature spoofing out of the box.​
Differences between GSIs & ROMs:
ROM updates modify all the partitions (boot, recovery, kernel, system, vendor, etc). A GSI update is just a system partition that updates "only" the system, that runs upon stock firmware.​
ROMs might pass safetynet out of the box. But for GSIs, you must root & use magisk modules to achieve that.​
You can't flash gapps on vanilla GSIs, as you do on vanilla ROMs. You must use bgS/bgN GSI variants.​
For now, GSIs have to be installed via fastbootd, as recoveries still yet to support logical partitions. So you need computer available when you update or change them.​
AOSP GSI project is being alive for almost many years now. I've been daily driving his project on this device for almost two years. Everyone claim GSIs are buggy & not daily drivable, which is a complete false claim. There are no compromises with GSIs when compared to ROMs.
PREREQUISITES​
USB Drivers (guide to install)​
Platform Tools (guide to setup)​
Stock ROM (fastboot)​
MicroG (for vanilla)​
vbmeta.img (from google)​
TWRP (thanks to Nebrassy)​
Magisk (thanks to topjohnwu)​
SafetyNet Fix (thanks to kdrag0n)​
Recommended GSIs :
TrebleDroid (thanks to phhusson)​
Pixel Experience (thanks to ponces)​
LineageOS (thanks to AndyYan)​
More to test from here
INSTALLATION​NOTE: I'm assuming you've already unlocked bootloader, backed up your data & know all the technical consequences of flashing & modding.
Download / extract all prerequisites in one place.​
From stock firmware, edit flash_all_except_data_storage.bat/sh & modify last line to fastboot reboot fastboot​
Enter fastboot mode {vol_down+power}, connect to PC & flash firmware using above edited script. When device enters fastbootd, from terminal/cmd execute :​
fastboot erase userdata​
fastboot flash vbmeta vbmeta.img​
fastboot flash system <gsi-file.img> (ignore INVALID SPARSE warning)​
fastboot reboot & make sure your GSI boots up. Power off & return to fastboot again.​
fastboot boot <twrp-file.img>, head to Advanced & run flash current TWRP to make recovery persistent across reboots.​
Finally Magisk (for root, safetynet fix, additional modding, etc).​
BUG_1: Don't touch the screen while booting to avoid touch issues after you boot (this bug occurs only on custom kernels).
BUG_2: Don't set up password on startup wizard. Instead, set it up later & then disable Android Setup app if it exists. Else it'll crash fingerprint settings.
UPDATE / DIRTY FLASH HOW ?​
fastboot reboot fastboot
fastboot flash system <new-gsi.img> & reboot twice
All phh based GSIs are dirty flashable (unless you switch between vanilla & gapps). If any GSI doesn't boot up, you can always reflash the older GSI & restore the previous state without any data wipes.
POST CONFIGURATION​
Enable the following Settings > Phh Treble Settings:​
Qualcomm features / Use alternate camera profile & audio policy​
Misc features / Disable audio effects​
IMS features / Force the presense of 4G calling & Install IMS Apk for Qualcomm vendor from notification panel.​
Setup magisk, hide the app, enable Zygisk & Enforce Denylist.​
Use SafetyNet-Fix module to pass safetynet. Still won't pass? Try Pixel-Props (redfin) that ensures fingerprinting.​
microG module if you chose vanilla variant (Safetynet works. Most of the banking apps work except gpay).​
NOTE: Flash custom kernels only through your custom recovery. Flashing through kernel managers (FKM, SPKM, etc) is not suggested.
MAGISK NOT WORKING ?​In this case, the GSI you selected isn't securized (comes with su bydefault). Through TWRP, do
mount -o rw /dev/block/mapper/system_a /system_root from terminal
Code:
rm /system_root/system/xbin/su
rm /system_root/system/bin/phh-su
rm /system_root/system/etc/init/su.rc
Or instead, you can use recovery's file manager to delete the above files. Then reboot.
EXTRAS​My Recommendations for great experience:
SPKM to set GPU > GPU Governor > Performance (fixes UI lags)​
Lawnchair / Quickswitch for launcher customization with gesture navigation support.​
Lineage Dialer for built-in call recording (push into /product/priv-app/Dialer/Dialer.apk).​
ANXCam for MIUI camera's post processing.​
GCam for google camera's post processing.​
Aurora Store / Droid for microg users.​
Kiwi Browser for chrome extensions support.​
Migrate to backup / restore user apps & data, incase you lose your setup.​
Thanks for reading all the way through here.
I have been using GSIs on my old Huawei P10 lite for almost 3 years, and it was a very good experience.
Now with mojito I find myself lazy always using Roms -_- '
Thanks for the guide!
Hami_Do said:
I have been using GSIs on my old Huawei P10 lite for almost 3 years, and it was a very good experience.
Now with mojito I find myself lazy always using Roms -_- '
Thanks for the guide!
Click to expand...
Click to collapse
The only official dev for this device, who's actually from core development of a reputed project (PE), is Zid. There aren't any, as I do not find others to be helping from core (except couple of kernel devs).
ROMs have no complete guarantees for future updates. Although you can use other project GSIs such as crD by Nazim, LOS by Andy, phhusson's the one who's consistently providing regular monthly updates with built-in OTA.
Can I install MIUI gsi roms like this?
Furkantaner said:
Can I install MIUI gsi roms like this?
Click to expand...
Click to collapse
You can install any AOSP GSIs with this guide. Not sure of other skins, as they're proprietary.
And why would you need MIUI GSI? Mojito stock "is" MIUI.
Furkantaner said:
Can I install MIUI gsi roms like this?
Click to expand...
Click to collapse
Miui and its similar sGsi ( semi gsi ) such as OneUi , Color os .. and other AOSPs based ported with Erfan tool aren't real gsi.
They miss patches from Phh and Andy.
The recommanded gsis with full patches (minimum issues) are from Phh (aosp), AndyYan (LOS 18.1/19.1), Ponces (PE) and many others you can check them here for example :
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
There are also more by Nazim and eremitein, you can check them in telegram groups.
can i use this method from aosp?
and what stock rom version should i use?
AlsoKouki said:
can i use this method from aosp?
and what stock rom version should i use?
Click to expand...
Click to collapse
Any version would work. Open stock ROM link in main post & make sure it's fastboot, not recovery.
As for AOSP, you can use any of them from this list (except A13).
in the last line i should change it to "fastboot %* reboot fastboot" or "fastboot reboot fastboot" ?
AlsoKouki said:
in the last line i should change it to "fastboot %* reboot fastboot" or "fastboot reboot fastboot" ?
Click to expand...
Click to collapse
Both work & imply the same btw. That line I've wrote just to make device go to fastboot instead of stock miui.
Adding fingerprint force closes settings.
Youtube fc aswell.
MPK99 said:
Both work & imply the same btw. That line I've wrote just to make device go to fastboot instead of stock miui.
Click to expand...
Click to collapse
i already execute the "flash_all_except_data_storage.bat" but nothing happen should i execute it with mi flash tool?
Samir2298 said:
Adding fingerprint force closes settings.
Youtube fc aswell.
Click to expand...
Click to collapse
No issues here. The procedure I've laid out is exact to that of my device. Some more info from your side might help, such as what you did from the start.
AlsoKouki said:
i already execute the "flash_all_except_data_storage.bat" but nothing happen should i execute it with mi flash tool?
Click to expand...
Click to collapse
I bet it's usb drivers issue. There's guide link in main post.
You should know the issue if you flashed a fastboot rom before.
MPK99 said:
I bet it's usb drivers issue. There's guide link in main post.
You should know the issue if you flashed a fastboot rom before.
Click to expand...
Click to collapse
{
"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"
}
nah its already installed and its detected in fastboot
i tried move the firmware to plarform-tools/ after i execute it this happen
MPK99 said:
No issues here. The procedure I've laid out is exact to that of my device. Some more info from your side might help, such as what you did from the start.
Click to expand...
Click to collapse
Followed exactly as in OP.
I did remove some apps tho from product app/priavpp and system app/privapp, so maybe that caused an issue? Is there anything related to fingerprint in those folders?
AlsoKouki said:
tried move the firmware to plarform-tools/ after i execute it this happen
Click to expand...
Click to collapse
This is redmi Note 10 forum mate. So I had stock ROM link of mojito/sunny. Your device (3rd screenshot) closely states it's Rainbow (Wiko).
Although this is a GSI guide, I suggest you to flash your own device's stock rom.
Still, it won't be enough caz I don't have overlay patch of your device.
Samir2298 said:
I did remove some apps tho from product app/priavpp and system app/privapp, so maybe that caused an issue? Is there anything related to fingerprint in those folders?
Click to expand...
Click to collapse
Probably. Try removing only one or two apps that are disablable from settings.. For overlay just 20kB is needed.
You can reflash system image from fastbootd & boot up without wiping again.
MPK99 said:
Probably. Try removing only one or two apps that are disablable from settings.. For overlay just 20kB is needed.
You can reflash system image from fastbootd & boot up without wiping again.
Click to expand...
Click to collapse
Alright, thanks! I'll try reflash.
Sorry for off-topic, does microg support whatsapp google drive backup/restore? I searched google but all answers are years old.
MPK99 said:
This is redmi Note 10 forum mate. So I had stock ROM link of mojito/sunny. Your device (3rd screenshot) closely states it's Rainbow (Wiko).
Although this is a GSI guide, I suggest you to flash your own device's stock rom.
Still, it won't be enough caz I don't have overlay patch of your device.
Click to expand...
Click to collapse
ahh sorry its because the spoofing feature from the rom,i forgot to disable that, will disable it and try again

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S23 Ultra

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S23 Ultra S918B/S918N/S9180.
Download & Guide:
1. Unlock your bootloader.
2. Downloads for S23 Ultra: AFH: dm3q twrp
3. Reboot to download mode
4. Uncheck auto reboot in Odin and flash TWRP in AP slot and vbmeta_disabled_R.tar in USERDATA slot.
5. Hold volume down and power until the screen goes black then immediately switch to holding volume up and power to reboot into TWRP.
6. Go to wipe, format data, and type "yes" to confirm.
7. Reboot to TWRP
8. Flash boot_repack.zip (To fix stock recovery restoration)
9. Flash magisk canary (Optional)
10. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Decryption will only work if no password/PIN/pattern is set in Android.
- No erofs r/w support yet.
Thanks:
TWRP team
@BlackMesa123 for helping me to add encryption support
@dr.ketan for supporting me​Donators
Sources:
Kernel tree
Device tree
Changelog:
GitHub History
mine
afaneh92 said:
Bugs:
- Encryption not fully working.
- No erofs r/w support yet.
Click to expand...
Click to collapse
Data decrypt support should be mandatory for this device expecially with the newer A13 EROFS partitions, please consider adding it.
BlackMesa123 said:
Data decrypt support should be mandatory for this device expecially with the newer A13 EROFS partitions, please consider adding it.
Click to expand...
Click to collapse
I tried on S20+ and S22 ultra it was harder than A series. But will try again when the device delivered, I may ask for your help. Thanks.
afaneh92 said:
I tried on S20+ and S22 ultra it was harder than A series. But will try again when the device delivered, I may ask for your help. Thanks.
Click to expand...
Click to collapse
Implementing crypto support is not that hard as it seems, in the S23 family it should even be easier since you can just implement the official TeamWin QSEE scripts in your device tree. I imagine the big deal on S20/S22 is due to those device having an Exynos SoC with TEEgris TZ, but even in that case it should be easy to handle. What I'm more afraid of is that this device probably has Knox SDP in vold so decrypt with PIN/password set won't work, but it's better than nothing atm.
BlackMesa123 said:
Implementing crypto support is not that hard as it seems, in the S23 family it should even be easier since you can just implement the official TeamWin QSEE scripts in your device tree. I imagine the big deal on S20/S22 is due to those device having an Exynos SoC with TEEgris TZ, but even in that case it should be easy to handle. What I'm more afraid of is that this device probably has Knox SDP in vold so decrypt with PIN/password set won't work, but it's better than nothing atm.
Click to expand...
Click to collapse
I was referring to snapdragon, and never worked. I used your implementation and device wasn't able to decrypt data. S22 was harder since data wasn't able to mount. I will wait for device, thanks again.
afaneh92 said:
I was referring to snapdragon, and never worked. I used your implementation and device wasn't able to decrypt data. S22 was harder since data wasn't able to mount. I will wait for device, thanks again.
Click to expand...
Click to collapse
We can surely work it out to fix it
@afaneh92 it looks like S23 vold has no crap A11 code leftovers which does break decrypt with PIN/password on TWRP, I compared the vold bin with my A52s' one and certain stuff is clearly missing. So it might just work out of the box once support for it gets added
BlackMesa123 said:
@afaneh92 it looks like S23 vold has no crap A11 code leftovers which does break decrypt with PIN/password on TWRP, I compared the vold bin with my A52s' one and certain stuff is clearly missing. So it might just work out of the box once support for it gets added
Click to expand...
Click to collapse
I hope so.
Nice work!
I followed the steps above, and when trying to reboot to system I get back to to twrp. Help please?
I just want to ask if anyone has tried installing viper4android yet and does it work? If it's like the s22 ultra and doesn't work. I might sound crazy but I wouldn't buy it. Music is more important to me then spen and camera although admittedly they are good to. It's mind blowing to think 1200 dollar won't sound as good as my Poco f3 or even my lg tribute 10 years ago.
lcd047 said:
I followed the steps above, and when trying to reboot to system I get back to to twrp. Help please?
Click to expand...
Click to collapse
I have exactly the same:
- after following all steps one by one there is only a reboot into TWRP itself possible
I compared the steps from this thread with the steps which are successfully working on my Galaxy Tab S8 Ultra ( https://forum.xda-developers.com/t/...-for-galaxy-tab-s8-series-snapdragon.4455491/ ) and I see a difference at step 7:
7. Flash custom kernel and magisk apk in twrp.
Click to expand...
Click to collapse
I do not see any "custom kernel" to download in this thread (at least for now) so I think this is the missing part. Or it only works correct in combination with "dr.ketans rom" (which I do not want to use for now).
@afaneh92: Thank you very much for your work (on "root" and also with "twrp")!
Edit: I just read the installation pdf from "dr. ketans rom". There is written in red letters:
DON'T run multidisabler from TWRP termial/zip or any system-rw script after flashing ROM else device won't boot.
Click to expand...
Click to collapse
So maybe the not booting system is related to the work which the "multidisabler" should do.
I will be happy if there will be some light regarding the non booting system after flashing TWRP.
Maybe I will give "dr. ketans rom" a try and have an eye on this thread how the things go on.
________________________________________
@Techguy777: This is very offtopic but I am with you that "Viper4Android" is a very important part also of my daily used tools. I just have found a (for me) good running workaround.
Search the fDroid store for the app "RootlessJamesDSP". Depending on which parts of "Viper4Android" you care about, the app is an extremely good working replacement. In my example, the "Convolver" with the impulse response files are important and that works wonderfully with the players I use.
hurray said:
I will go back for now to (rooted) stock ROM and Recovery and will have a look how this thread will go on.
Click to expand...
Click to collapse
Sadly flashing "dr.ketans rom" (or the "unroot" one, for that matter) doesn't fix the problem for me. Ironically everything was working fine with "dr.ketans rom" alone, but I just had to try disabling encryption. Well I suppose better is the enemy of good.
lcd047 said:
Sadly flashing "dr.ketans rom" (or the "unroot" one, for that matter) doesn't fix the problem for me. Ironically everything was working fine with "dr.ketans rom" alone, but I just had to try disabling encryption. Well I suppose better is the enemy of good.
Click to expand...
Click to collapse
I just flashed the orginal FW from samfw.com and my S23 Ultra is booting correctly into the system. Now I will try the current "S918B_WA6_DrKetan_ROM_T02". It seems that TWRP is build in into the ROM. If this works I will try a backup & restore of user data (this is the most important part from TWRP for me).
hurray said:
I just flashed the orginal FW from samfw.com and my S23 Ultra is booting correctly into the system. Now I will try the current "S918B_WA6_DrKetan_ROM_T02". It seems that TWRP is build in into the ROM. If this works I will try a backup & restore of user data (this is the most important part from TWRP for me).
Click to expand...
Click to collapse
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
dr.ketan said:
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
Click to expand...
Click to collapse
Yup, flashing the full ROM works. Many thanks, and keep up the amazing work!
dr.ketan said:
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
Click to expand...
Click to collapse
You have convinced me of your ROM. After flashing I had to reformat "data" but afterwards the system booted correctly.
The ROM works very well so far and the additional functions via "ROM Tools S23" are also good (especially that they can be selectively enabled and disabled).
Backup and recovery of user data has also worked flawlessly.
So now I can start with the actual setup of all apps.
Thanks a lot for your work!
hurray said:
You have convinced me of your ROM. After flashing I had to reformat "data" but afterwards the system booted correctly.
The ROM works very well so far and the additional functions via "ROM Tools S23" are also good (especially that they can be selectively enabled and disabled).
Backup and recovery of user data has also worked flawlessly.
So now I can start with the actual setup of all apps.
Thanks a lot for your work!
Click to expand...
Click to collapse
I have seen many users don't want "custom" roms, but my ROM will have complete stock look + single click all critical fix. It won't force users to use customised look. Also it have more options to make modifications in ui but everything will be by user's will.

Categories

Resources