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
Related
{
"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"
}
Flashing tips by @ramjet73, this should be read by everyone
http://forum.xda-developers.com/showpost.php?p=55228784&postcount=12583
This is an enhanced version of the 81c developer preview that google released.
It has currently been ported for Mako and Deb and improved for Hammerhead and Flo
It offers a permissive selinux policy, aosp merged in and rock solid stabilty along with drastic improvements in speed and smoothness.
It offers updated proprietary files, updated google apps, fonts, res files and animations from the newer sdks.
Click to expand...
Click to collapse
Deb does not have a working mobile radio yet, radio turns on but without access to the settings, we can't configure it. A work around is being worked on
Big thanks to @defconoi , @zyr3x , @percy_g2 , @ben1066 [MENTION=1050103] for improving and originally helping with the old lpv79 port to Mako.
Right now I rebased the entire project to clean it out and smooth it out
Huge thanks to @ramjet73 @bitstra @manueltts @skiman10 @psycho693 @jayfallen for helping me get it over to the other devices I don't have and testing everything I threw at them and the huge brainstorming and trying things I couldn't. It would have not been possible without these guys so please thank them
Click to expand...
Click to collapse
Warning. This has heavy ramdisk mods that are essential for it to work. You can flash current up to date "kit Kat kernels or L updaters only" but not full boot.imgs as this will break the ROM. If you do happen to flash a a boot.img, you can pull it out if the rom and fastboot flash boot boot.img
Hammerhead can only use L preview Kernels.
Remember, this is a port of a developer preview, there is already bugs in the official version from google and without the L code, we can not fix google's bugs. There are fixes to known problems in N7 2013 and N5 forums so if you do find them, please provide them with the bug
Click to expand...
Click to collapse
INSTALLATION INSTRUCTIONS
FIRST TIME FLASHING
Put the file onto your Internal Storage
Reboot into Recovery (CWM/TWRP]
"wipe data/factory reset"
"mounts and storage" -> "format system"
"install zip" -> "install zip from sdcard" -> choose the mako-bla-bla-zip and confirm flashing procedure
"reboot into system"
first boot may take up to 10 minutes - be patient
UPDATING
Put the latest L-bla-bla.zip onto your Internal Storage
Reboot into Recovery (CWM/TWRP)
"wipe data/factory reset"
"install zip" -> "install zip from sdcard" -> choose the [filename.zip] and confirm flashing procedure
"reboot into system"
Updater-script wipes the cache files so no need to wipe cache
Sources
Mako
GPL KERNEL SOURCE - github.com/Android-L-Porting-Team/android_kernel_mako
Flo, Deb and Hammerhead use the modifed stock preview with the kexec-hardboot patch directly provided by @tassadar to provide multirom support. Flo and Deb use the same kernel.
Hammerhead - http://forum.xda-developers.com/showpost.php?p=48508468&postcount=2
Flo - http://forum.xda-developers.com/showpost.php?p=45886584&postcount=2
We are using the rebase repos right now since they are cleaned out
Github https://github.com/Android-L-Porting-Team
Downloads
Stable - 9001
Full
Afh - https://www.androidfilehost.com/?fid=95747613655040641
Google Drive - https://drive.google.com/file/d/0By0vn8iv_zrVYUlFbmVrMEtHcDA/edit?usp=sharing
Dev-Host-
Mega-
Click to expand...
Click to collapse
Downloads
Stable - 9001
Slim -
Afh - https://www.androidfilehost.com/?fid=95747613655040642
Google Drive - https://drive.google.com/file/d/0By0vn8iv_zrVS1hDakt6VWM3WGc/edit?usp=sharing
Dev-Host
Mega-
Click to expand...
Click to collapse
slim builds have excess google apps cut out for those on a bandwidth budget or like to pick and choose their google apps from the play store
OT talk is welcomed in my threads and development is done in the open. I encourage involvement in the project in any way.
Please do not complain about OT, it encourages a fun and relaxed environment
Like the work I did, consider donating. I'm currently not working so it helps feed me
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=BPFLE54YPRV92
Yes, my PayPal account is thatguy32404, I like to keep my banking stuff separated from my social account
nexus devices threads
Mako
http://forum.xda-developers.com/nexus-4/development/lpv-79-mako-port-beta-t2807446
deb
http://forum.xda-developers.com/nex...e/l-android-lpv-dev-deb-t2856915#post55016443+
flo
http://forum.xda-developers.com/nex...id-lpv-dev-flo-enhanced-t2856920#post55016534
hammerhead
http://forum.xda-developers.com/google-nexus-5/development/l-android-lpv-dev-n5-enhanced-t2856934
Changlelog.
Changlelog.
Stable-9001
Now over 9000!!!!!!
Updated selinux security policy
tracked down some missing permissions
did some other work but can't remember
B7.0.1
Flo & Deb
removed some excess apps that were replaced and I missed in b7
B7
updated fonts, res files, animations from the latest sdk
updater-script wipes cache files
updated some more google apps.
now using smart-art
force dns to google's public dns
B6
6 finishes up the rebasing work from 5 (5.9 was just a stepping stone and getting it out to other devices so we could work out all the kinks)
(Mako only info)
The rebasing work meant a lot of clean up and trying to get it as efficient as possible so from 5 to 6 is a big step and will be quite noticeable
(mako, flo, deb)
updated egl drivers are from qcom developer are in here which are newer then the preview ones
(Hammerhead )
Proper working sound now
(All)
Built in Busybox should be working. I tested the functions and seemed good to me.
Got rid of all the looping code and debugging code to speed everything up.
Updated the preview proprietary binaries to the latest version (some can't go all the way up and are stuck on a previous set or even original preview versions)
(Hammerhead has the latest preview egl drivers)
Built in google apps have been updated.
Introduction of slim builds for those on a bandwidth budget.
Can't think of what else.
Most kinks have all been worked out
Click to expand...
Click to collapse
B5.9
Rebased completely from scratch on 81c
improved reliability and stability.
Ported to Deb, Flo and Hammerhead
Beta 5
fully permissive sepolicy based on aosp, cleaned out a lot of crud
removed reliance on n5 frameworks, merged in some current aosp
improved smoothness and increased reliability, daily driver status
Beta 4
New Kernel
more smashy smashy bugs
Dpat09 said:
For all camera issues please try this: go to the Dev settings and disable nuplayer! I'm posting it again because I think it will be lost in all the posts! If it works hopefully the contributing devs will catch it and put it in the main post
Click to expand...
Click to collapse
reserved for @defconoi kernel info
Installed it now, works great. Thank you for bringing this to deb.
Now all we gotta do is figure out how to access the radio setting outside of the setting app since they aren't there.
I had to track down the radio files and pulled them out of 4.4.3 to get the radio to start but I don't have a deb so I can't troubleshoot it as well.
I'm using the n7 as a base for mako along with all the framework files but had to use the n5's apps. The problem with deb is that if you try to use non tablet apps, it breaks the multi user feature so that might not be am option there so a script or an app that replicates the setting and configure it to the network might have to be done
sykopompos said:
Now all we gotta do is figure out how to access the radio setting outside of the setting app since they aren't there.
I had to track down the radio files and pulled them out of 4.4.3 to get the radio to start but I don't have a deb so I can't troubleshoot it as well.
I'm using the n7 as a base for mako along with all the framework files but had to use the n5's apps. The problem with deb is that if you try to use non tablet apps, it breaks the multi user feature so that might not be am option there so a script or an app that replicates the setting and configure it to the network might have to be done
Click to expand...
Click to collapse
What's the difference between your port and my
http://forum.xda-developers.com/nexus-7-2013/development-lte/android-lpv81c-deb-t2849013
Just so you all know it was me who actually did all this stuff, @sykopompos is taking all the credit ? no but really without sykopompos and his wizardly ways there would be no way this would have gotten done. He was nice enough to help with the project, then "take it over" and get it done the right way. Make sure to give him a big thanks for taking time out of his day and working on this through the nights. Without him this might have never happened. Thanks a lot man!
Sent from my Nexus 7 LTE using Tapatalk
Ansanen said:
What's the difference between your port and my
http://forum.xda-developers.com/nexus-7-2013/development-lte/android-lpv81c-deb-t2849013
Click to expand...
Click to collapse
Give it a flash and come back and give me an answer.
Oh BTW, this should have been out like a month ago but I didn't realize my really stupid derp of not modifying the bootclasspath so it wouldn't boot. I didn't realize this till after I started work on flo so if @skiman10 was helping you, you might have a part of my earlier work in yours.
Also do you have the radio files in yours?
Hoping that you guys could figure out the radio issue, soon~ thanks!
jayfallen said:
Hoping that you guys could figure out the radio issue, soon~ thanks!
Click to expand...
Click to collapse
@skiman10 is looking into our options here since he has a deb.
This is gonna be a bit of a pain to figure out how to work around this
Being that the file is almost 500mb, I assume the gapps are included in the file?
Yes @papikev thats right.
papikev said:
Being that the file is almost 500mb, I assume the gapps are included in the file?
Click to expand...
Click to collapse
Yes... Because the L apps are speeeeecccciiiiaaaaallll. Very special.
skiman10 said:
Yes... Because the L apps are speeeeecccciiiiaaaaallll. Very special.
Click to expand...
Click to collapse
oooooh, sounds phuuuuuun, Thanks guys.
Now I need L for Nexus 10 and I'll be happy
Fatal1ty_18_RUS said:
Now I need L for Nexus 10 and I'll be happy
Click to expand...
Click to collapse
Buy me a Nexus 10 and your wish will be granted lol
Once the radio gets straightened out, this will be (yet it already is) a killer rom. Very smooth. Nice new features on L. First time running it, good stuff guys. 5 star this thread. Look forward to the future with this one.:good:
skiman10 said:
Buy me a Nexus 10 and your wish will be granted lol
Click to expand...
Click to collapse
You mean buy me one...
sykopompos said:
You mean buy me one...
Click to expand...
Click to collapse
I got this one... Your apprentice is ready!
skiman10 said:
I got this one... Your apprentice is ready!
Click to expand...
Click to collapse
Good, because it wouldn't be one bit easy
{
"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"
}
Machao44(the original dev) has now created the XDA thread over here,head here instead of this link,use this thread only if you want to use the older versions of the ROMs or some fixes:
https://forum.xda-developers.com/z3-compact/development/rom-los-xperia-ui-z3c-t3654894
It has the stock Sony Nougat theme and apps found on Xperia XZ Premium,XZs,Xperia L1 and so on.
Also includes the stock Sony camera app with 4K 60FPS recording support,AR effect etc.
Usually the ROM itself is very fast and it is good as a daily driver.
You can download Xposed for this ROM as an addon,but not sure how stable it is.
Install guide:
NOTE: If you are coming from Concept ROM,it is NECESSARY to flash back to stock MM,or you will have a bootloop or the ROM will just fail to install.
1. Download the ROM from here:
https://mega.nz/#F!ZgAhhJLI!PvIf-ZLY0Ihs6fY-8c6SBA (link from Machao44's thread)
2. Download SuperSU or Magisk,both do work(they are not included in ROM zip)
3. Download & install TWRP recovery found on the Lineage thread(if you don't know how to install go to @tomascus's thread and read the second post where the install guide is)
4. Install the zip and start Aroma
5. Select the apps and features you need
6. Once it's done,flash any additional zips and reboot.
NOTE 2: Recovery might get removed after you flash the ROM(if you flash unmodified versions of ROMs),so you need to re-flash through fastboot.
For custom kernels,as reported for now Kernel12 version 11 works fine with this ROM,if you want to try something else then try to flash it and report back if it works,since I believe that not all custom kernels for LineageOS do work.
If Wi-Fi has very weak signal or it doesn't work at all,download and flash this zip:
https://mega.nz/#!hh8m3aIb!z1X66R8uK8BrG9g853lvDtkDiMdTAl7wbACGyXNxwjo
If you have issues with Bluetooth calling,flash this zip(thanks to @jimmy123322):
https://www.androidfilehost.com/?fid=673368273298979213
If you use M-ROM 1.2.0 or 1.2.5 you will have a brightness issue,to fix download the framework-res.apk from this post(thanks @wolfmannight):
https://forum.xda-developers.com/z3...ny-themed-android-7-1-1-t3627518/post73000345
Current issues:
-Sony Themes doesn't work,themes won't apply
If you do find any other issues,please report them here.
Links for older versions:
https://mega.nz/#F!YlAkxBLL!mJra95HcQu9ZjD0JbTvyjw - M-ROM 2.2.0
https://mega.nz/#!B0EBxIAD!8fa0OmRI1Z5nUpa8j-2GqmLH63wkmUXNFwj0QmRrQjI - M-ROM 2.1.0
https://mega.nz/#!88l2ybTB!xVuQJIJZ8x8yGAt4j2U8aFFiE6aDogg92ttttg3kfZo - M-ROM 2.0.0
https://mega.nz/#!hwkC0SKZ!KKs0RTnK1ASeYKG6IGtH8pxg5wP96gaMeDMU9D7qhJ4 - M-ROM 1.2.5
https://mega.nz/#!0oNh0BQL!xy8Z53b_SpChzFZbcy24jPAnvX6hhVVG5UaEpiamc5g - M-ROM 1.2.0
If anyone needs for experimental purposes here are the links to the unmodified ROMs:
https://mega.nz/#!w4kClZCZ!puWpP9Y-uwg8kZUcVLDFM_TlD9gVMfFL4YDkslsTLLk - M-ROM 2.1.0
https://mega.nz/#!Ak1kHaja!xVTh-K8NX-g9YIjlnVn0t0X2W9K93NtbR42JDJm0XQ0 - M-ROM 2.0.0
https://mega.nz/#!EhsQxRBR!E214YYEfcBc_MirbwvV2ghRE6SC9M7xQrTAdYsiiZAA - M-ROM 1.2.5
https://mega.nz/#!dls0HJSS!Zu0brC3-FFfkvvxJDVAwL2ohlbt3QmMVLH4y_-VoC5c - M-ROM 1.2.0
Big thanks to the original devs of this ROM:
@M-Rom - seen as machao44 on bbs.gfan.com
@SuperLamic
@rcstar6696
@nailyk
@xkeita
@Myself5 - original dev of CarbonROM which is based of LineageOS kernel sources
@tomascus - original dev of the base ROM - LineageOS
Also thanks to:
@vooR9er - helped to translate the Aroma installer
@ztxgeol - found every single download link for every version of this ROM including the link to Xposed,and I have just re-uploaded them all to a better download provider so you are not forced to download from Baidu
@unpair - thanks for testing almost every single version of this ROM and also thanks to everyone who tested the ROMs,but he did help the most
"Also includes the stock Sony camera app with 4K 60FPS recording support,AR effect and so on."
Does this also mean that image enhancing (Settings -> Display) is working also? (if TA.img was "sideloaded" with PoC Tool od DK.ftf)
Is this that ROM where framework etc were modded that LOS reacts like Sony stock regarding all this DRM stuff?
fluffi444 said:
"Also includes the stock Sony camera app with 4K 60FPS recording support,AR effect and so on."
Does this also mean that image enhancing (Settings -> Display) is working also? (if TA.img was "sideloaded" with PoC Tool od DK.ftf)
Is this that ROM where framework etc were modded that LOS reacts like Sony stock regarding all this DRM stuff?
Click to expand...
Click to collapse
To be honest,I don't really know,and I believe there is no image enhancing of any sort,I wasn't really able to reach the Settings to see that.
Oops,I uploaded by accident the wrong build to MEGA,the link won't work for 45 minutes,will keep you updated.
EDIT: You can now download the ROM and try to install it.
HUGE CHANGELOG:
-First of all,when installing the ROM do not press to install Google Play services,that actually corrupts everything,will mention in it in OP
-Google Play works fine
-To answer @fluffi444 image enhancing is actually there with Sony Sound mods,but Sony themes currently doesn't work
-The ROM doesn't come with any keyboard installed,so I will include Gboard inside the ROM
-I will debloat the ROM from chinese apps
New build will be up with screenshots in the end of the night.
EDIT: Build is now up! Download it and tell me how it runs!
First of all thank you for this ROM, planning to try some day soon
How is camera quality?
Do I need to flash stock image first or can I flash directly from lineageos?
k13tas said:
First of all thank you for this ROM, planning to try some day soon
How is camera quality?
Do I need to flash stock image first or can I flash directly from lineageos?
Click to expand...
Click to collapse
Camera quality is like in stock ROM,and it doesn't really matter what you have before installing this ROM,but it only won't work if you are now running Concept ROM,if that is the case then yes you need to flash the stock image first
Dinkec27 said:
Camera quality is like in stock ROM,and it doesn't really matter what you have before installing this ROM,but it only won't work if you are now running Concept ROM,if that is the case then yes you need to flash the stock image first
Click to expand...
Click to collapse
Thank you for answering
So DRM keys are not needed with this ROM, right?
k13tas said:
Thank you for answering
So DRM keys are not needed with this ROM, right?
Click to expand...
Click to collapse
Nope
After Clean installation I get system ui crash cant use this rom..
shrazy said:
After Clean installation I get system ui crash cant use this rom..
Click to expand...
Click to collapse
SystemUI crash? Try to get a logcat and I'll look into it,while you can in that time try to re-download the ROM and try to install it again,and make sure you use TWRP from the link in the Lineage thread.
Would like it very much, but i cannot receive calls, can make phone calls though.
Second time i started fresh from stock, unlocked bootloader and fastboot flashed fotakernel twrp from lineage thread, same problem: when i call myself from another phone the screen turns white with xperia logo and the call ends.
Sorry i can't take logs (never tried actually)
Also when i reboot into recovery chinese twrp appears and i can switch only to english (needed to watch a youtube video to figure out which was the settings button). I'm quite sure it's not the one i installed (don't remember the number version).
Google play works fine: don't understand what you wrote in op about unchecking it. In the aroma you are asked to check what you don't want to be installed, and without it i wouldn't know how to do.
Well i hope to use this ROM in the future, Thank you for your efforts so far
The brightness on my screen is always high, I can't change it... The brightness is in automatic and the sensor works well
unpair said:
Would like it very much, but i cannot receive calls, can make phone calls though.
Second time i started fresh from stock, unlocked bootloader and fastboot flashed fotakernel twrp from lineage thread, same problem: when i call myself from another phone the screen turns white with xperia logo and the call ends.
Sorry i can't take logs (never tried actually)
Also when i reboot into recovery chinese twrp appears and i can switch only to english (needed to watch a youtube video to figure out which was the settings button). I'm quite sure it's not the one i installed (don't remember the number version).
Google play works fine: don't understand what you wrote in op about unchecking it. In the aroma you are asked to check what you don't want to be installed, and without it i wouldn't know how to do.
Well i hope to use this ROM in the future, Thank you for your efforts so far
Click to expand...
Click to collapse
I wrote in the OP that you don't install Play because after I checked that it always crashed and dissapeared after a reboot.
For chinese TWRP,I didn't even know it was on there lol,so that's I guess another reason to flash TWRP from the Lineage thread after you flash the ROM.
For phone calls I really can't do much without logs or anything,so would highly appreciate if you try to get me a logcat of some sort,there are many guides online.
As for future plans for this ROM,I am looking to re-build it and use the latest Lineage build as base ROM to remove as much bugs as possible.
Kriztian96 said:
The brightness on my screen is always high, I can't change it... The brightness is in automatic and the sensor works well
Click to expand...
Click to collapse
So when there is no automatic brightness enabled the brightness is always high? I couldn't really notice that the only reason being I use my phone on the highest screen brightness all the time.
How about the blouetooth and reboot bugs of the other llineageOS? If there aren't, this rom can help find this bugs!
andry360 said:
How about the blouetooth and reboot bugs of the other llineageOS? If there aren't, this rom can help find this bugs!
Click to expand...
Click to collapse
Not sure,haven't had any random reboots tbh,even with the latest build I haven't had any random reboots nor any bluetooth issues,maybe those can apply for something else but I only use Bluetooth for connecting a Bluetooth speaker,headphones and occasionally transfering files and all of that worked.
Dinkec27 said:
So when there is no automatic brightness enabled the brightness is always high? I couldn't really notice that the only reason being I use my phone on the highest screen brightness all the time.
Click to expand...
Click to collapse
When the automatic brightness is enabled or not, the brightness is always high, and when I use the slider for change the level of it, it doesn't change, it's always the same high brightness... I can't use it in the dark because it's so high
Kriztian96 said:
When the automatic brightness is enabled or not, the brightness is always high, and when I use the slider for change the level of it, it doesn't change, it's always the same high brightness... I can't use it in the dark because it's so high
Click to expand...
Click to collapse
I'll look into it,thanks.
keep it up
{
"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?
{
"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"
}
With Great power comes great responsibility.
Disclaimer::
Please use this Kernel in accordance with local law and with the privacy of yourself and others in mind. Not responsible for any charges you might accrue, bail money or fines if you choose to use it for unlawful reasons
Warning your warranty is now void. Do this at your own risk. The mad clown is in no way responsible for the chaos, worldwide disease, nuclear destruction, laughing fish, costumed caped crusaders or damage caused to your device by performing the steps involved.
The mad tech clown is back with another Kernel for all of the Kali-linux-nethunter users wanting the portability of kali-nethunter for their Pixel 6 and 6Pro devices codenamed Oriole and Raven .
I now bring you the
Mad-Kali-Maxhunter kernel for raviole
Some of the features include:
-power efficient workqueues
-fsync switch
-boeffla wake lock blocker
-force usb fastcharge
-mm: oom_kill: Reduce some verbose logging
-cpufreq: add cleanslate battery optimizer feature
-/dev/tmp and /dev/tmp/ mount
-full bluetooth support
-Wifi injection
-dvb / sdr support
Plus:
-Everything neeeded to use kali properly on your device plus some systemd stuff
-dns resolver support
-full usb/otg support
See source commits for more
This is not a super fancy pot luck kernel with every allowable feature. This is tuned out quite effeciently and ive found that adding certain features or too many causes heat to rise and we all know thats not good with this device.
Source
GitHub - Biohazardousrom/android_kernel_google_raviole
Contribute to Biohazardousrom/android_kernel_google_raviole development by creating an account on GitHub.
github.com
Download
16.68 GB folder on MEGA
74 files and 20 subfolders
mega.nz
How to Flash:
pre-requisites:
Franco Kernel Manager & root
Download zip to the internal storage of your device.
Open FKM and tap 3 line menu and choose flasher.
Choose manual flash and navigate to the zip file, select it and choose reboot after flash.
Enjoy
For more support
gs101 and gs201 development/support
Pixel 6/pro & 7/pro discussion group for general support and development
t.me
Thanks to
acuicultor
freak07
tbalden
arter97
andip71
for all your development
reserved
Some notes to help you get the Kali-nethunter system set up on your device.
1. Please install the Kali-nethunter magisk modules. These will have the firmwares needed to use the various USB dongles for wifi/bluetooth.
2. Visit this site to download and install the Kali-nethunter store https://store.nethunter.com/en/
3. After installing the store app let it update and then install these 3 apps
-Kali-nethunter installer updater and interface (aka kali-nethunter gui)
-Kali-nethunter terminal
-Kali-nethunter bvnc and kex manager
once installed open the kali gui app and ok any permissions it asks for. it will then force close.
Note:: Since android 12 the gui quit asking for several permissions needed for running scripts in the terminal so you will need to download the attached file kadb.sh to your pc then connect your device to the pc and open a command prompt and run
./kadb.sh
this will grant the missing permissions and allow the gui to open again without it force closing. script was written for linuxed based pc's. if you use windows just open it up and copy and paste the comnands one by one.
or if you have another rooted device you can connect the two via otg and run from the extra rooted device
4. open the gui app once more and navigate to install and start chroot. if you have your own just add the location to the given box when you choose install. for everyone else let the app download it and install from the Kali repository.
Note:: this will take some time please do not exit the app while in the process of downloading or installing
5. to make it easier to enter the kali nethunter terminal app create a custom comnand in the gui. it can be anuthing ls, apt-get update just what ever. then save it to kali and use it when ever you want to use the terminal
Note:: If you want to use the Kex manager/vnc you will need the root password to run programs as root. That password is toor.
Also you can activate wlan0 and wlan1 without a usb dongle. But for some reason it wont allow use of bluetooth without a dongle. i never could find a rhyme or reason for this but i have found when using bluetooth on my pc that kali would not use the built in bluetooth either and i would have to use a dongle. this is probably by design for stealth reasons but dont quote me.
I have found dual wifi and bluetooth adapters in the past and they work simultaneously
This is great! Will it be possible for you to share the kernel build instructions here? I cloned you repo into private/gs-google and ran BUILD_KERNEL=1 ./build_slider.sh -j$(nproc) after that. I do see the kernel files in out/mixed/dist. I flashed them, and it gave me boot loops.
It would be awesome if you could share some build instructions as well.
you can find more info on building kernels here....
Building Kernels | Android Open Source Project
source.android.com
but the steps i took were to initialize and sync the repo listed in the link above. then from there i made my cherry picks. next i went to /arch/arm64/configs and edited the gki_defconfig to match the needed configs i needed for kali linux. after that i ran build/build.sh.
it will error after that because the abi_symbol_allowlist in /android/abi_gki_aarch64_generic file will need updated with the new symbols now compiled in the newly customized kernel.
then after you have corrected all the errors and its built a kernel you will have 4 items to flash..
boot.img
dtbo.img
vendor_boot.img
vendor_dlkm.img
dtbo and boot are flashed in fastboot while vendor_boot and vendor_dlkm are flashed in fastbootd.
but the easiest way to flash is by making an anykernel.zip
also need to point out that some custom roms will not allow you to flash custom kernels so i would hop on tg and ask the maintainer if that rom permits flashing kernels else your gonna have a hard time
thanks for the build @Duhjoker. I managed to flash it on a Pixel 6 and install NetHunter but wifi monitoring mode doesn't work. This is the output from `airmon --debug`
Hey Duhjoker! Thanks for your work on this! Its a dream come true! I just have one question. Is there any chance we will see a pixel 6a version of this kernel with wifi injection? Or is this a pipedream?
evansfromza said:
thanks for the build @Duhjoker. I managed to flash it on a Pixel 6 and install NetHunter but wifi monitoring mode doesn't work. This is the output from `airmon --debug`
View attachment 5705665
Click to expand...
Click to collapse
i am aware of the problem and im looking into it. to be honest i never could get airmon-ng to work on any android.
im thinking monitor mode may need to be enabled first through /sys/ like qualcomm but i could be wrong. this is my first exynos kernel and im having to relearn stuff.
gahndii said:
Hey Duhjoker! Thanks for your work on this! Its a dream come true! I just have one question. Is there any chance we will see a pixel 6a version of this kernel with wifi injection? Or is this a pipedream?
Click to expand...
Click to collapse
I can but i dont own a pixel 6a. The build would have to completely blind but if your willing to test i can try. i did the same for the pixel 3 so it shouldnt be a problem but read next post to see whats up on the current state of building
ok so i dont know whats up with android 13 kernel source but so far none of the builds are booting. ive been at it since release and no go.
but be assured i am working on stuff
Duhjoker said:
I can but i dont own a pixel 6a. The build would have to completely blind but if your willing to test i can try. i did the same for the pixel 3 so it shouldnt be a problem but read next post to see whats up on the current state of building
Click to expand...
Click to collapse
Though I wouldn't mind testing something like that, however would not consider myself a reliable tester. I'm more of a tinkerer honestly. I haven't flashed a rom in 4-5 years haha I gave up years ago on a kernel with wifi packet injection drivers baked in. (for a model I owned) I would not be able to give you solid reliable feedback but id happily try it out for fun. From what ive been reading looks like im staying on Android 12 for a bit longer.
The ramdisk provided by Google for A13 is the issue, you must extract it from vendor_boot and replace it inside prebuilts folder, thanks to freak07 for the solution.
Here's the commit from him.
acuicultor said:
The ramdisk provided by Google for A13 is the issue, you must extract it from vendor_boot and replace it inside prebuilts folder, thanks to freak07 for the solution.
Here's the commit from him.
Click to expand...
Click to collapse
Thank you so much for that. it was driving me crazy and couldnt understand what the problem was.
so now we have kali coming for a13 in a couple days
ok guys Mad-Kali-MaxHunter-Raviole-T for android 13 is now live and linked in op.
I have been researching the wifi monitor mode and packet injection properties on the wlan and heres the state of the driver from my google searches
The bcm4389 wifi 6e client set of chips was announced in 2020 by broadcom and can be found in the Samsung galaxy s21 and google pixel 6, 6pro and 6a models along with some xiaome phones.
For us that means that the drivers and firmware are so new that theres been very little development for it. i myself was only able to find a bluetooth patch that im sure has already been picked up by the google source kernel devs.
from what i can tell of the other drivers by looking at the nexmon github page and further reading the previous wlan modules needed patched firmware to enable airmon-ng.
im still doing research into how to fix this but if anyone has any clues please speak up.
but for now if you should be able to get by using a usb wifi dongle.
Hi, @Duhjoker I was able to install everything successfuly but it seems like the kernel is missing some features not directly related to Kali but that would be nice to add.
HID attack support from Rucky, and ISO usb host from DriveDroid.
I'm using a Pixel 6 Pro on A13
Thanks for your work
Unfortunately, usb wifi dongles aren't working even if they're supported, even after installing their firmwares. Something's wrong with the kernel.
I have good news. Seems google did the hard work for us on hacking the firmware for monitor mode and it looks like we can now use monitor mode to catch packets "NATIVELY".
please read here for the details.
Get BCM4389 into monitor mode for WIFI sniffing
Hey all, I was trying to watch beacon frames transmitted by my access point, but had no capable hardware in my house to sniff it. Or did I? Turns out, Pixel 6 / Pixel 6 Pro can do it. Here's my howto...
forum.xda-developers.com
i havent tested this fully yet but a friend in my tg chat helped me snag the binaries rc files and best of all the firmware.
i dont currently have a magisk module yet but with root copy the vendor folder in the zip to /data/adb/modules pick any module for example
/data/adb/modules/busybox-ndk/system
reboot and enjoy
edit: you made need to chmod the binaries after placing them
deleted
tried that, it doesn't work.
also, wifi dongles are recognized by lsusb but not mounted (airmon-ng only shows phy0 - internal wlan interfaces)
{
"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"
}
Release v20221023 · ChonDoit/treble_blaze_patches
CHANGELOG | Initial and latest Release | Fixed Safety Net | Fixed things which exist on source but not on final product (Amazing, right?) | Broken as expected | Enjoy as it or GTFO Why so big image...
github.com
-》No video tutorial for "CustomAP" cause it is very easy to read step by step -》The last i will compared our Mod Stock A12 ROM with ProjectBlaze GSI as the same features.
i want to modify system then i selected this variant.
ProjectBlaze_v415-arm64-bgS-slim-lite_20221023.img.xz
*** Not Project Blaze from j7b3y
Note Download : There are only "bgS variant then if you wants "magisk" ...must mod system.img yourself by
Delete
/system/xbin/su
/system/etc/init/su.rc
/system/bin/phh-su
/system/bin/phh-securize.sh
su app in /system/app/phh.superuser
Together with
*disable toggle SuperSU in phh-treble setting.
or
Select this variant "ProjectBlaze_v415-RO-arm64-bgS-slim-secure_20221023.img.xz" which no build-in SuperSU but you can't mod system files cause its Read Only .
Note2: Advanced mod options ( edit sub partition)
Because we don't have TWRP on Android 12 then you want my step by step CustomAP Part 2 to work with editing System before flashing CustomAP with odin.
Update 30 oct 2022: Custom AP Step by Step(install GSI without TWRP Part 1, 2)
New Trick.. for Low Spec Computer. Part 3 Step By Step CustomAP for Odin (Non-TWRP) Enable Linux Subsystem and Install Ubuntu in Windows 10 (For modify GSI system image) 30 Oct 2022 ✓ Don't try Android 13 with base on TrebleDroids patch. (...
forum.xda-developers.com
Requirements
Android 12 Stock ROM ( T22xXXU1BVGB ) I'm not update to T225XXS1BVI2 cause Bootloader will changes to S1. >>will be lost ability to downgrade from Android 12 to Android 11. ( But if currently you re on XxxBVI2 then you can make it )
CustomAP file >tar.md5< for Odin. (Edit Stock AP firmware with Linux Subsystem on Win 10,11)
Fdroid-termux
*** proximity sensor not working
*** Gyroscope sensor not working.
But i test it on STOCK A11, A12 it show result test the same as below.
Check spec: Tab A7 Lite only have 3 sensor. Accelerometer, Geomagnetic, light sensor.
Specification sheet (buy online): SM-T225 Samsung SM-T225 Galaxy Tab A7 Lite 8.7" WXGA+ 1340x800 Android Tablet with LTE
Specification sheet: SM-T225 Samsung SM-T225 Galaxy Tab A7 Lite 8.7" WXGA+ 1340x800 Android Tablet with LTE. Information, datasheets and documents. Where to buy in South Africa.
www.comx-computers.co.za
*Not supported Tablet Display ( All GSI did not )
** Not supported VoLTE for Samsung devices.
We can test with this code.
Be Supported: test by myself
Face-unlock
MTP ( open Developer options >Default USB configuration>File Transfer)
exFat SD card
Double tab for screen sleep from BlazeHouse menu
Double tab for awake screen from Phh-treble Setting menu
GPS
Bluetooth sound & audio
Headphone ( Bluetooth & wire)
Phone (except VoLTE)
* ** Offline charging for break Samsung warranty bit warning massages. (options) **** Power_off charging animation = non
Hotspot
Nearby Share
Screen Recording
Battery usages history reset
* Protect battery (to extend the lifespan of your battery , limit the min &maximum charge to any % you like.)
* Auto Screen Brightness. (velis auto brightness)
Screen Casting
Safety Net PASS ( but i don't care about this )
Screen Casting
* * *optional ( did not explained in tutorial )
Sound module supported from magisk modules list here.
*Not support Hi-res
GitHub - reiryuki/Audio-Wizard-DTSX-Ultra-Asus-Zenfone-6-Magisk-Module
Contribute to reiryuki/Audio-Wizard-DTSX-Ultra-Asus-Zenfone-6-Magisk-Module development by creating an account on GitHub.
github.com
GitHub - reiryuki/Arkamys-Audio-BLU-BOLD-N1-Magisk-Module
Contribute to reiryuki/Arkamys-Audio-BLU-BOLD-N1-Magisk-Module development by creating an account on GitHub.
github.com
!Garranty | Better than Stock DOLBY
PHH Treble Setting for fixing Bluetooth Error .
DTSX
Note: I will fix auto-brightness conflict with battery usages history soon.
[Close].Treble GSIs overlay
Overlay uses with all GSI
forum.xda-developers.com
Specificed Customize Menu of This GSI.
>>> Add Battery Charging Limit Apps
GitHub - VR-25/acc: Advanced Charging Controller
Advanced Charging Controller. Contribute to VR-25/acc development by creating an account on GitHub.
github.com
1. Flash Backend ACC with Magisk Manager.
2.Find suitable Charger_switch
Plug your Charger with tab 7 lite
type
Code:
su
acc -t
and you'll find the list of all the charging swich you can use. (Switch work ✓)
3.Enforce your Charger Switch
Code:
acc -ss
and Select No.x which Switch work ✓ + idle mode = true
4.Install Frontend.
Now you could easily use any features with no type command.
Run acc --test (or acc -t) to see which switches work.
Run acc --set charging_switch (or acc -ss) to enforce a working switch.
Test the reliability of the set switch. If it doesn't work properly, try another.
Testing .. Please share your.
Auto Brightness (after installed i made it be system app.)
How's the performance? Anyone can upload any video of using this rom?
SykoraLukas said:
How's the performance? Anyone can upload any video of using this rom?
Click to expand...
Click to collapse
Yes
Need A13
Difficul said:
Need A13
Click to expand...
Click to collapse
on based A12 -- No testing A13 is good for SM-T225, 220 yet.
tom.android said:
Release v20221023 · ChonDoit/treble_blaze_patches
CHANGELOG | Initial and latest Release | Fixed Safety Net | Fixed things which exist on source but not on final product (Amazing, right?) | Broken as expected | Enjoy as it or GTFO Why so big image...
github.com
Note Download : There are only "bgS variant then if you wants "magisk" ...must mod system.img yourself.
Delete
/system/xbin/su
/system/etc/init/su.rc
/system/bin/phh-su
/system/bin/phh-securize.sh
su app in /system/app/phh.superuser
Together with disable toggle SuperSU in phh-treble setting.
Note2; Because we don't have TWRP on Android 12 then you want my step by step CustomAP Part 2 to work with editing System before flashing CustomAP with odin.
Click to expand...
Click to collapse
Managed to make a GSI from this ROM for my T220...but I did not have to follow any of those instructions. I just patched the .tar file with Magisk 25.2 as usual and Magisk setup did everything including disabling phh-SU. I did have to manually install the Magisk app at first.
Edit: Question, do the last two tabs inside Settings > BlazeHouse crash on you? They do here.
Difficul said:
Need A13
Click to expand...
Click to collapse
Then you should compile it if you "need" it. New versions of Android always take several months until they get stable. Do remember Phhusson is no longer actively maintaning GSIs so we have to give the new TrebleDroid team lots of time to master everything GSI.
SykoraLukas said:
How's the performance? Anyone can upload any video of using this rom?
Click to expand...
Click to collapse
Performance depends on the user configuration (as does battery life). To me, they're all similar in both performance and features.
NOOB HERE : is it possible for someone to post already compiled custom AP to download and then flash it with correct BL and CSC for (t220) ?
Doesn't matter witch build or region
And should the bootloader be unlocked for that?
Thanks
niksot said:
NOOB HERE : is it possible for someone to post already compiled custom AP to download and then flash it with correct BL and CSC for (t220) ?
Doesn't matter witch build or region
And should the bootloader be unlocked for that?
Thanks
Click to expand...
Click to collapse
1. Can't do, sorry. My connection's currently having upstream issues (1Mbps or less).
2. Yes, the bootloader should be unlocked, otherwise the firmware won't allow you to flash anything custom. Also, users that do post their custom AP should always state which firmware they're using or they're risking others to brick their devices so yeah, be careful with that crucial detail. I for one moved to Android 12 firmware but there are others that have not.
nirogu325 said:
Managed to make a GSI from this ROM for my T220...but I did not have to follow any of those instructions. I just patched the .tar file with Magisk 25.2 as usual and Magisk setup did everything including disabling phh-SU. I did have to manually install the Magisk app at first.
Edit: Question, do the last two tabs inside Settings > BlazeHouse crash on you? They do here.
Click to expand...
Click to collapse
Hello BlazeHouse menu do its job well. thanks for sharing "disabling phh-su with magisk"
i must modified system.img of GSI ( before Odin fashing ) to patch offline-charging for breaking warranty bit of Samsung Warning state, but can't tell details because of English language is not my mother language. sorry
tom.android said:
Hello BlazeHouse menu do its job well. thanks for sharing "disabling phh-su with magisk"
i must modified system.img of GSI ( before Odin fashing ) to patch offline-charging for breaking warranty bit of Samsung Warning state, but can't tell details because of English language is not my mother language. sorry
Click to expand...
Click to collapse
Hmm. The last two tabs inside BlazeHouse crash for me. Weird. If they work for you, can you take some screenshots just to see what they are about?
nirogu325 said:
Hmm. The last two tabs inside BlazeHouse crash for me. Weird. If they work for you, can you take some screenshots just to see what they are about?
Click to expand...
Click to collapse
ok i wll take sreccnshot, during this you can see my video attach .
tom.android said:
ok i wll take sreccnshot, during this you can see my video attach .
Click to expand...
Click to collapse
I see many interesting things in those two tabs. Gonna reflash the GSI to see if that fixes it. It could be me tapping on Securize that broke those two tabs, who knows. Thank you.
nirogu325 said:
I see many interesting things in those two tabs. Gonna reflash the GSI to see if that fixes it. It could be me tapping on Securize that broke those two tabs, who knows. Thank you.
Click to expand...
Click to collapse
if you want , can make customAP for patch offline-charging breaking Warranty bit .
tom.android said:
if you want , can make customAP for patch offline-charging breaking Warranty bit .
Click to expand...
Click to collapse
The normal ROM doesn't have that? I thought it did. How do you patch something like that? Is it too hard?
nirogu325 said:
The normal ROM doesn't have that? I thought it did. How do you patch something like that? Is it too hard?
Click to expand...
Click to collapse
-normal gsi don't
-too many step ( hard to explain for me )
but final step to show %charging not success. but can break samsung warranty bit stop state.
-what firmware you need?
tom.android said:
-normal gsi don't
-too many step ( hard to explain for me )
but final step to show %charging not success. but can break samsung warranty bit stop state.
-what firmware you need?
Click to expand...
Click to collapse
Ah, I see. Nah, it's ok, I don't charge anything while it's off. Thanks though. The August CherishOS did have the offline charging right?
nirogu325 said:
Ah, I see. Nah, it's ok, I don't charge anything while it's off. Thanks though. The August CherishOS did have the offline charging right?
Click to expand...
Click to collapse
yes
niksot said:
NOOB HERE : is it possible for someone to post already compiled custom AP to download and then flash it with correct BL and CSC for (t220) ?
Doesn't matter witch build or region
And should the bootloader be unlocked for that?
Thanks
Click to expand...
Click to collapse
CustomAP must be created with specific firmware , firmware must depended on zone or country from Samsung.
This is my example for user' s problem.
CustomAP 2022
The only way to get away from the official firmware. Changes Degoogle (LeOS-TD.2.0 ) A13 GSI Home Launcher For SM-T225 FastbootD ☆☆☆ Tips and Tricks For [ LOS TD Unofficial GSI ] latest 2023-03-24 microG...
forum.xda-developers.com