NEXT Kernel 1.0.0:
STOP! This kernel supports Custom KitKat Roms (e.g. OmniROM, SlimKat, CM 11.0), Custom JB 4.3.x Roms (e.g. CM 10.2) and Stock / Stockbased Roms!
It won't work on any AOSP Android 4.1.x or 4.2.x Custom Roms for now!
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY S3 MINI PROJECT!
Sources:
https://github.com/andi34/android_kernel_samsung_golden
Dual-Boot Solution by @ketut.kumajaya, well known from Samsung Galaxy Tab 2 and Samsung Galaxy Tab 3 8.0
I/O Scheduler : noop | deadline | cfq | sio | sioplus | row | zen
Governor : Abyssplug | Ondemand | Interactive | Powersave | Performance | SmartassV2 | Sakuractive
based on latest Samsung OSRC for Samsung Golden (JB_Update2)
Linux kernel 3.0.101 version
Compiled with GCC 4.7
Open source Samsung exFAT included (v. 1.2.7)
Static BusyBox v1.21.1 in /sbin, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. Thanks to @ketut.kumajaya
"magic busybox" for Stock (based) 4.1 Roms: Ramdisk Busybox will overwrite busybox binary in
/system/bin or /system/xbin and save it as busybox.backup
Auto root on Stock (based) 4.1, but please download SuperSU from Google Play to update
Early boot scripts support
(/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
symlink /system/etc/wifi/bcmdhd_sta.bin_b2 to /system/etc/wifi/bcmdhd_sta.bin
to fix broken Wifi on Stock(based) Roms
SElinux Support
Known Problems:
Bootmenu
- Reboot into Recovery from main Bootmenu does not work
- Reboot into Bootloader from main Bootmenu only reboots normal
StockRom
- USB connection not working, charging works
- Wifi-Tethering not working on Stock / Stockbased Rom
Known fully working Roms
SlimKat by Android-Andi
OmniROM by golden-guy
VanirAOSP by Unjustified Dev
enox Stockbased Rom
Stock Light
Virginity v14
Selfcompiled CM 10.2.1 (based on CM 10.2.1 Stable Source)
Novafusion CM 11 & PAC (ext4 formatted!)
Novafusion CM 10.2 & PAC
Thanks To:
ketut.kumajaya - without you this would never be possible <3
gokhanmoral, Chainfire
@LuuchoRocha
@cocafe
OliverG96
DerTeufel1980
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
I am still learning each day, i learnd most stuff from our great Developer Ketut P. Kumajaya
- i think HE deserves a Beer instead donating to me ATM. If you like you can spend Ketut a beer using PayPal
Screenshots
{
"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"
}
XDA:DevDB Information
[golden] NEXT kernel, Kernel for the Samsung Galaxy S III Mini
Contributors
Android-Andi, ketut.kumajaya
Kernel Special Features:
Version Information
Status: Beta
Created 2014-08-12
Last Updated 2014-10-11
Downloads
All files attached
- NEXT Tool 0.2 to create a 2nd System Partition (system.img) - also included inside PhilZ Touch Blackhawk Recovery
- PhilZ Touch Blackhawk Recovery for Dual-Boot-Support
- NEXT Kernel
Since NEXT Kernel 1.5.4: download latest NEXT Kernel here
Older files for history still here attached!
Changelog
Code:
[U]11.10.2014[/U]
1.5.6 -> 1.6.0
- Utilized blkid further
- Autogenerated fstab adapted from NEXT Kernel for Samsung Galaxy Tab 3
- Initial F2FS Support (experimental)
[U]19.09.2014[/U]
Update dual boot tool 0.3
- Create 1.5 GB dynamic growth sparse image
- Ext4 formatting fix
- Free space calculation fix
1.5.5 -> 1.5.6
- fixes a warning in dmesg (sysfs: cannot create duplicate filename '/devices/virtual/switch/usb_audio')
[U]17.09.2014[/U]
1.5.4 -> 1.5.5
- get rid of DVFS limit without breaking Stock 4.1 or Android 4.3 / Android 4.4
thanks [user=5562153]@LuuchoRocha[/user] and [user=4832589]@cocafe[/user]
[U]16.09.2014[/U]
1.5.3 -> 1.5.4
- Android 4.3: added PAC Support
- Nintendo Wii Remote support (experimental, untested)
- cpufreq: turn all CPUs online when governor gets changed
[U]04.09.2014[/U]
1.5.1 -> 1.5.3
- "magic busybox" for Stock (based) 4.1 Roms: Ramdisk Busybox will overwrite busybox binary in
/system/bin or /system/xbin and save it as busybox.backup
- Auto root on Stock (based) 4.1, but please download SuperSU from Google Play to update
- Early boot scripts support
(/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
- symlink /system/etc/wifi/bcmdhd_sta.bin_b2 to /system/etc/wifi/bcmdhd_sta.bin
to fix broken Wifi on Stock(based) Roms
[u]01.09.2014[/u]
1.5.0 -> 1.5.1
fix broken Dual-Boot (because missing "tmp" folder inside ramdisk? also some file permissions fixed inside ramdisk)
1.4.0 -> 1.5.0
Upstream Kernel Changes to 3.0.101 - thanks a lot to @Fred6681 for fixing some know Problems after Upstream!
Build Xpad module (not tested if it is working)
Enabled DVFS Limit to make the Kernel boot on Stock and AOSP Roms
New Charger-Animation - thanks a lot to @daywalk3r666
[u]25.08.2014[/u]
1.3.1 -> 1.4.0
Initial CM 10.2 support
[u]22.08.2014[/u]
1.3.0 -> 1.3.1
Fix 800mhz bug, thanks to @Fred6681
1.2.0 -> 1.3.0
Updated Android 4.4 ramdisk: this will fix broken Wifi on Novafusion Roms / Roms based on Novafusion source
Build exFat as module
[u]20.08.2014[/u]
1.1.0 -> 1.2.0
Added Stock / Stock based 4.1 Support
More i/o scheduler: Added sioplus | row | zen
Compiled using GCC 4.7 again for better compatibility
Update LZO compression
arm/vfp: Makefile optimization
and some more....
1.0.5 -> 1.1.0
Fixed bootmenu flickering / blackscreen :) now the bootmenu is 100% visible
(Reboot-Recovery option from bootmenu not working, ends in kernel-panic,
reboot bootloader not working, it will normal reboot)
partially restore initial cm11 ramdisk
cleanup cm11 ramdisk
[U]19.08.2014[/U]
1.0.4 -> 1.0.5
Update permissions inside init.samsunggolden.rc,
set SELinux to permissive for now,
lzma compressed ramdisk
1.0.3 -> 1.0.4
Use Linaro 4.8 Toolchain
[U]18.08.2014[/U]
1.0.2 -> 1.0.3
Use Linaro 4.7-2013-04 Toolchain
[U]12.08.2014[/U]
1.0.1 -> 1.0.2
- fix an Superuser issue, added back init.superuser.rc
1.0.0 -> 1.0.1:
- fix "com.android.phone" crashed on Vanir Rom
1.0.0:
- initial release
How-To
Flash PhilZ Touch Blackhawk Recovery
Reboot into PhilZ Touch Blackhawk
Flash NEXT Kernel
Advanced Functions -> Run Aroma Dual Boot Tool
Create a 2nd System.img (choose 1 GB)
Reboot your recovery
Choose the 2nd Bootoption (it is flickering, black screen, just press the volume down key one time and press the power button).
Now the navigation buttons inside PhilZ Touch are RED
Flash a 2nd Rom (i tested my own SlimKat and @golden-guys OmniROM because they don't use F2FS)
Flash NEXT Kernel again
Reboot
Now you will see a Bootmenu (flicckering & blackscreen), you will see it short if you press the volume key,
first option = boot 1st Rom, second option = boot 2nd Rom
USE ON YOUR OWN RISK! MAKE A BACKUP BEFORE TRYING!
Reserved
Dual Boot FAQs
Adapted from @ketut.kumajaya s Dual-Boot FAQ,
original adapted from droidphile's "Dual Boot FAQs".
1. "Why would I wanna dual-boot?"
A. You don't have to.
You need one testing system and don't want to break your daylie Rom.
You can not decide between different Roms - use both
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p24 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel.
b) Flash latest Extended PhilZ Touch recovery: http://forum.xda-developers.com/showpost.php?p=54772218&postcount=2
c) Atleast 90% battery left.
d) 3 GB free on internal SD.
e) Some spare time
1) Present AOSP, setup AOSP as secondary:-
i) Reboot into recovery
ii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery (red on screen navigation buttons)
iv) Flash AOSP ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
2) Present AOSP, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create a 2nd system.img and then close it
iv) Reboot into secondary recovery (red on screen navigation buttons)
v) Nandroid restore your AOSP ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Reboot into primary recovery
viii) Flash AOSP ROM as 1st ROM
ix) Flash blackhawk's NEXT kernel again
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition
20. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool or "Run Aroma Dual Boot Tool" in Advaced Menu from PhilZ Touch Blackhawk and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
21. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
22. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
23. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
24. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
25. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
26. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p25 = /data
mmcblk0p22 = /system
mmcblk0p23 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition.
Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom.
Cache in mmcblk0p24 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p25 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- dev/block/mmcblk0p24 is mounted as /cache.
How to get important Logs
tonyp said:
The three most important log types are:
logcat: the logoutput of the Android system
radio logcat: the log outpur ot your System / BB / RIL communication
kernel log (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
Normal Logcat:
Code:
adb logcat -v time -d > logcat.log
Radio Logcat:
Code:
adb logcat -b radio -v time -d > logcat_radio.log
Note: Cyanogenmod (based) ROMs require the following setting to export kernel logs via adb:
Settings - Developer Options - Root access - choose: "Apps and ADB"
Kernel Log:
Code:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
Click to expand...
Click to collapse
More FAQs will be added and the list will be updated as DB is improved.
Wow!
another milestone in the S3 Mini history!
Keep it up bro :good:
Incredible!!
This will bring my two favorite ROMs on one device!! Unbelievable Till now, I thought it is possible only with linux lubuntu and ROM, like on my tab...
Thank you!
m.
This is amazing! Can we use roms like debloated stock with your roms?
Sent from my GT-I8190/Novafusion CM11
Don't you read the OP?!? Not for stock ROMs! And 4.4.x only!
m.
meduza2 said:
Don't you read the OP?!? Not for stock ROMs! And 4.4.x only!
m.
Click to expand...
Click to collapse
Ah missed that part! Thanks for pointing out.
Sent from my GT-I8190/Novafusion CM11
No worries
m.
heithered said:
This is amazing! Can we use roms like debloated stock with your roms?
Sent from my GT-I8190/Novafusion CM11
Click to expand...
Click to collapse
Will try to add Stock 4.1.2 support sometimes later.
Send from OnePlus One using Tapatalk
Android-Andi said:
Will try to add Stock 4.1.2 support sometimes later.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Hey, this is a big deal. It is still awesome with or without stock support! Thanks for your awesome work!
Sent from my GT-I8190/Novafusion CM11
Well, just to leave an "Amazing work" as always:good:
great work.....dual boot with slimkat and omnirom works perfect.with vanir "com.android.phone" crashed
Top Job and faster as Nova!!!!
especially for you
@Android-Andi,
because of the world first dual boot for our s3mini, we created extra an info banner for you
Please have a look: Weltpremiere bei hubo.in
meduza, bodo_1, daywalksr666, kingg
Wow, you did it! That's so cool! Thanks a lot for this! ?
Simply awesome
It is incredible what AA made for our device.
But what is the sense of this mod?
I can use only one ROM at the same time.
Or am I wrong?
I am happy for explanations
The only idea i have:
First ROM for daily use
Second ROM for testing and replacing with different ROMs...
m.
moonryder said:
It is incredible what AA made for our device.
But what is the sense of this mod?
I can use only one ROM at the same time.
Or am I wrong?
I am happy for explanations
m.
Click to expand...
Click to collapse
you can load two roms to your phone.
at start up,you can choose either of 2 roms.
may be from recovery mode I think.
this is all what I know. hope I helped.
waiting for correction if I was wrong.
thanks and great work and much appreciation to Android Andi bro
@moonryder,
you could quickly boot one of your favorite ROMs or use the second boot partition for test ROMs....
m.
Redmi 2/WT88047 OmniROM PIE 9.0
DOWNLOAD BUILD-28/12/2019 (ARM)
DOWNLOAD BUILD-05/01/2020 (ARM64)
RELEASES:
====================
18/08/19
====================
* Initial release
* Omni upstream as of 18/08
====================
25/08/19
====================
* Selinux enforcing
* Added Dirac support from MIUI
* ZRAM 4.18 backport from a6k kernel
* Fixed the janky flashlight toggle
====================
10/09/19
====================
* Initial ARM64 release
(Thanks to @Cecell3000 for his ARM64 works
and @karthik km for fixing RIL)
====================
28/12/19 - ARM | 05/01/2020 - ARM64
====================
* Fixed VoLTE
* Updated GPS HAL to A6020
* Omni upstream as of 28/12
(looks like the pie branch is no longer updated and is deprecated, maybe its time to discontinue omni pie)
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. TWRP obviously (Use Cecell's ARM64 TWRP)
2. Latest device firmware (WT86047 | WT88047)
3. Repart /system to at least 1.5GB
(Go HERE to resize system partition)
INSTALLATION INSTRUCTIONS:
1. Reboot device to TWRP
2. Wipe everything except internal and external storage
3. Flash the ROM zip file
4. Flash the 3Expand-filesystem zip file (Available HERE)
5. (Optional) Flash a gapps package
6. Reboot device to system
CURRENT ISSUES:
* You tell me!?
SOURCES:
Device tree (ARM | ARM64)
Common tree (ARM | ARM64)
Kernel sauce (ARM | ARM64)
Vendor (ARM | ARM64)
BUG REPORTS:
REPORT BUGS ONLY IF
- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW:
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
OmniROM, ROM for the Xiaomi Redmi 2
Contributors
Rahif M
Source Code: http://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2019-08-18
Last Updated 2020-01-17
Thank you!
Nice...
Thanks, I'm gonna try this :good:
Very good.
Onfire again.
Any review please.
Which rom is comptible arm or arm 64 ???
Flash BUILD-10/09/2019 (ARM64) using twrp 3.2.3.0 - 64 bit, get error 255 "error installing zip file"
system partition: resized to 1.5GB
device: redmi 2 1 GB ram
Wow arm64... I wanna try it
I guess need move rom zip file to internal storage, then flash.
thonipublic said:
Flash BUILD-10/09/2019 (ARM64) using twrp 3.2.3.0 - 64 bit, get error 255 "error installing zip file"
system partition: resized to 1.5GB
device: redmi 2 1 GB ram
Click to expand...
Click to collapse
That's weird, can u provide recovery logs pls?
also did you follow the flash procedure correctly?
flash rom.zip+expandfs.zip and then gapps?
Rahif M said:
That's weird, can u provide recovery logs pls?
also did you follow the flash procedure correctly?
flash rom.zip+expandfs.zip and then gapps?
Click to expand...
Click to collapse
Yes, i had follow the flash procedure.
I will try it again tomorrow to get recovery log.
Currently on other rom.
Rahif M said:
That's weird, can u provide recovery logs pls?
also did you follow the flash procedure correctly?
flash rom.zip+expandfs.zip and then gapps?
Click to expand...
Click to collapse
Successfully flash the rom after resize /system partition to 1.75 gb.
Thanks, for this smooth rom :good:
I am not able to flash and boot into the ARM64 TWRP recovery. It'd just hang at the logo. Meanwhile, the normal TWRP (3.3.1.0) works fine. Am I missing something?
I have a 2014817 1GB variant. Could it be misdetecting as a 2GB instead?
Edit: Figured it out
thank you so much for the arm64 bro, i am going to install and test it.
Managed to get it working by flashing latest MM firmware and then the 64bit TWRP. However, it gets stuck at Google Verifying Account page during setup. I can't get past it even using my own accounts to log in. Anyone else has this issue or knows how to get past this?
Edit: Never mind figured out to boot up first time and then flash Open GApps
conspibro said:
Managed to get it working by flashing latest MM firmware and then the 64bit TWRP. However, it gets stuck at Google Verifying Account page during setup. I can't get past it even using my own accounts to log in. Anyone else has this issue or knows how to get past this?
Edit: Never mind figured out to boot up first time and then flash Open GApps
Click to expand...
Click to collapse
MM firmware? WTF!? ?
nadimhd said:
MM firmware? WTF!? ?
Click to expand...
Click to collapse
My phone was still on its stock Kit Kat firmware. The ARM64 TWRP only works with the latest firmware (MM) it seems.
Firmware for the modem, wifi etc, not the OS.
For you information, the instruction isn't that clear. It pretty much take me one day to make it work
here's how I do it
1. Reboot device to TWRP
2. Flash 1Resize-System-Redmi2 zip (can be found at 3rd requirement link)
3. Resize to 1.75 gb
4. Wipe everything except internal and external storage
5. Flash the ROM zip file
6. Flash the 3Expand-filesystem zip file
7. Flash MindTheGapps gapps package (Don't use opengapps it causes bootloop)
8. Reboot device to system
Hope it helps you!
(choose GSI type ARM64 AB, vanilla or with existing Gapps) in you're choice:smile
Flashing files found here
https://sourceforge.net/projects/chickentikka-projects/files/X01AD/GSI Files/
Android 10 Framware :
https://drive.google.com/file/d/1pAqr2PXnxz6hQ02NHirp7PJuCZi1RjXu/view?usp=drivesdk
Installation steps:
- Make sure your device has bootloader unlocked
1- boot in to TWRP
2- wipe, data dalvik, cache, vendor
3- Flash Frimware Android 10 Asus Max M2 x01ad.zip
4- Flash the GSI as system image
5- Resize system
6- Flash Gapps. (Optional)
7- flash Magisk phh builds use phhmagisk
8- mount system, vendor, persist
9- flash Dm-verity
10- flash permessive v5
11- Reboot to system
Dm-verity , permissive, and firmware Also available in telegram group
Telegram Group
{Mod edit: Link removed!}
/*** BEGIN DISCLAIMER ***/
* Your warranty is now void. All flashing is done at your own risk!
* I am not responsible for bricked devices, dead SD cards, 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
/*** END DISCLAIMER ***/
Here's my first effort at porting the custom ROM to the Galaxy Tab A 9.7 [SM-P555] on Android 11. It's likely to have bugs and is EXPERIMENTAL as it is a work in progress.
S-Pen is not supported on this ROM.
Always backup your current ROM (and/or keep stock firmware close by) before flashing.
Please read the full article before proceeding to flash this rom.
Installation Instructions
If you don't have a custom recovery:
- Download twrp_3.0.2-1_SM-P555_mm_15816.tar
- Reboot your tablet in download mode (power+vol-down+home) and connect it to your pc
- Using ODIN load the downloaded file to the AP slot and press start
- As soon the tablet start to reboot hold vol-up and home (don't let it reboot to system)
- Now you should see TWRP-3.0.2.0
If you have custom recovery:
- Copy rom to sdcard or micro sdcard
- Full Wipe (System, Data, Davik Cache, Cache)
- Flash Rom
- Reboot (time boot up to 10 minute)
ROM Download Links:
Android File Host
Google Apps - Select ARM and Android 11
https://opengapps.org/
Pico Apps Recommended
Change History
20220414:
Initial Version
Working
1. WiFi
2. Bluetooth
3. Brightness
4. Audio via Speakers
5. Location/GPS
6. Camera
7. RIL
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Based On: Lineage
Thanks/Credits
Thanks to @retiredtab @RandomAndroidTinkerer for their extensive work on SM-T550 & SM-T555 build. I have followed their sources and commits to fix the ROM issues.
Special mention to @kgvarunkanth for all the support and hours spent teaching me basics and clearing my doubts while building the Development PC and the ROM. I wouldn't have reached this point without his support.
Device Tree gt5note10lte
Kernel sources Github
KernelSU boot.img
Tested on ugglite, AlphaDroid
(Please comment if it works on other ROMs, thnx!)
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATAs before!
Download KernelSU-ugglite-szancso.zip and KernelSU_v0.4.x-release.apk
Reboot into recovery, and install KernelSU-ugglite-szancso.zip (sideload or copy any storage)
Reboot system
Install KernelSU_v0.4.x-release.apk, and set in app the superuser apps.
DOWNLOAD
Kernel version: 4.9.337
Kernel source: LINK
KernelSU source, and app download: LINK