SpaceX Kernel Pure Edition
Samsung Galaxy Note 5/S6 Edge+
SpaceX Kernel Features
- Base Stock Kernel/DTB latest
- Stable, battery life optimize
- SELinux Enforcing
- KNOX WARRANTY VOID: 1
- Ramdisk modified:
Patched sepolicy (By SuperSU 2.52 @Chainfire)
Disabled dmverity (if applicable)
Disabled forceencrypt (if applicable)
Auto Root/Busybox
Init.d script support
su.d script support
Auto-Kill Knox/SecurityLogAgent
Deep Sleep fix
Private Mode fix
Wifi pass forget fix
Ram Management optimize
Random reboot/Reboot in calling fix (Note 5/S6e+)
SQLite3 3.8.11.1 binary and optimization script
At every boot the FsTrim command will be excecuted, to keep your Phone smooth and the internal memory fast!
Supported devices
N920C
N920G
N920I
N920K
N920L
N920S
N920T
N920P
N9208
N9200
N920R4
S6 Edge+, soon...
Download
SamFirm.Net
Install Guide
- Via Odin:
Make sure OEM unlock & Usb debugging is also enabled as well (Developer option)
Boot your Note 5 into Download Mode & connect to PC
Flash SpaceX kernel via Odin 3.10.7 in [AP]
After boot: install SuperSU-2.52.apk
Done
Click to expand...
Click to collapse
- Via Recovery custom:
Make sure OEM unlock & Usb debugging is also enabled as well (Developer option)
Copy Kernel (.zip) file to your devices
Boot your Note 5 into Download Mode & connect to PC
Flash your Recovery custom via Odin 3.10.7 in [AP]
Boot into Recovery, flash Kernel
After boot: install SuperSU-2.52.apk
Done
Click to expand...
Click to collapse
Special thanks
@Chainfire - SuperSU 2.50+, patched sepolicy support for Root Android 5.1.1/6.0 with SELinux in Enforcing mode.
XDA:DevDB Information
[Kernel] SpaceX Pure Edition - Stock Modified Ramdisk, Kernel for the Samsung Galaxy Note 5
Contributors
Manh_IT
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 1.0.0
Beta Release Date: 2015-10-30
Created 2015-10-29
Last Updated 2015-11-04
Reserved
Reserved
Good to see N9208 support. Thx dude.
cornelito said:
Good to see N9208 support. Thx dude.
Click to expand...
Click to collapse
Please test and report
Thank !
flash with odin gave me an error and i prompted me to use smart switch to revert back to stock. luckily i was on a 100% stock rom so i just booted into recovery and factory reset
when flashing with custom recovery, flashes properly but when you boot into system it gets stuck on the boot screen (says samsung galaxy note 5) also says kernel is no seandroid enforcing if that matters
N920T, 100% stock rom
Does it have OC abilities?
I know N920CD (Dual SIM) is not mentioned in the list of supported devices but I thought I would check... is it supported?
guaneet said:
flash with odin gave me an error and i prompted me to use smart switch to revert back to stock. luckily i was on a 100% stock rom so i just booted into recovery and factory reset
when flashing with custom recovery, flashes properly but when you boot into system it gets stuck on the boot screen (says samsung galaxy note 5) also says kernel is no seandroid enforcing if that matters
N920T, 100% stock rom
Click to expand...
Click to collapse
I have so exactly the same errors with my N920C.
guaneet said:
flash with odin gave me an error and i prompted me to use smart switch to revert back to stock. luckily i was on a 100% stock rom so i just booted into recovery and factory reset
when flashing with custom recovery, flashes properly but when you boot into system it gets stuck on the boot screen (says samsung galaxy note 5) also says kernel is no seandroid enforcing if that matters
N920T, 100% stock rom
Click to expand...
Click to collapse
After flash finishing device will reboot 2 times, maybe you mistakenly took bootloop
hshah said:
I know N920CD (Dual SIM) is not mentioned in the list of supported devices but I thought I would check... is it supported?
Click to expand...
Click to collapse
Try with N920C kernel. If have bugs, fix soon...
Manh_IT said:
After flash finishing device will reboot 2 times, maybe you mistakenly took bootloop
Click to expand...
Click to collapse
i let it sit for ~5 minutes on the bootloader screen. i didnt see any boot animation scren
guaneet said:
i let it sit for ~5 minutes on the bootloader screen. i didnt see any boot animation scren
Click to expand...
Click to collapse
Ok, I recheck it.
Thank!
guaneet said:
i let it sit for ~5 minutes on the bootloader screen. i didnt see any boot animation scren
Click to expand...
Click to collapse
Try again
rebuild1: https://drive.google.com/folderview?id=0B40ItdHKfkyQdXFVYVFwU2x4azg&usp=sharing
Thank!
Manh_IT said:
Try again
rebuild1: https://drive.google.com/folderview?id=0B40ItdHKfkyQdXFVYVFwU2x4azg&usp=sharing
Thank!
Click to expand...
Click to collapse
still gets stuck on bootloader screen, let it sit for a few minutes. ill get last k_msg when i flash jovy's kernel
https://onedrive.live.com/redir?resid=87D629AAB1E96F70!868&authkey=!AJ8_0kmQggzb-24&ithint=file,
N920CD need some love
guaneet said:
still gets stuck on bootloader screen, let it sit for a few minutes. ill get last k_msg when i flash jovy's kernel
https://onedrive.live.com/redir?resid=87D629AAB1E96F70!868&authkey=!AJ8_0kmQggzb-24&ithint=file,
Click to expand...
Click to collapse
Rebuild2: https://drive.google.com/folderview?id=0B40ItdHKfkyQNDNqY0lLdUgycHc&usp=sharing
Manh_IT said:
Rebuild2: https://drive.google.com/folderview?id=0B40ItdHKfkyQNDNqY0lLdUgycHc&usp=sharing
Click to expand...
Click to collapse
success! thank you! if you need help testing anything in the future for the N920T just shoot me a pm!
guaneet said:
success! thank you! if you need help testing anything in the future for the N920T just shoot me a pm!
Click to expand...
Click to collapse
Ok, thank you!
Can you help me take a screenshot?
Manh_IT said:
Ok, thank you!
Can you help me take a screenshot?
Click to expand...
Click to collapse
Here ya go
Related
Ok folks, Here is Clockworkmod Recovery with Swipe enabled for your Grand 2.
Note: No one but yourself is responsible for what you do to your device.
People to Thank
koush - for his awesome recovery.
Shabbypenguin - For firguring out it was missing the dtb.
bailboxer - for providing needed dumps and contacting me.
Known Issues
doesnt boot due to qcom boot security.
Post and let me know!!!
How to install with Odin
(USB) Disconnect your phone from your computer
Start Odin3-vX.X.exe
Click the PDA button, and select cwm-grand2.tar
Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
(USB) Connect the phone to your computer
Make sure Repartition is NOT checked
Click the Start button
Wait for Android to boot
Done (if it took you more than 30 seconds, you goofed)
NOTE: Sometimes the device does *not* boot into recovery mode. Just do the entire procedure again if this happens. If it still will not install, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
The Goods
ms013g-cwmr.tar
stockrecovery.tar
XDA:DevDB Information
Clockworkmod Recovery Samsung Galaxy Grand 2 SM-G7102, Tool/Utility for the Samsung Galaxy Grand 2
Contributors
PlayfulGod
Version Information
Status: Testing
Created 2014-04-28
Last Updated 2014-07-04
cwm not working
it doesn't boot.. not working
pearlborpuzari said:
it doesn't boot.. not working
Click to expand...
Click to collapse
what does it do?
tar removed for now so no one else installs it.
PlayfulGod said:
what does it do?
tar removed for now so no one else installs it.
Click to expand...
Click to collapse
The recovery doesn't boot.. It gets redirected to download mode.
Probably because of secured bootloader..
Safestrap might work!!..
so before we flash we do to remove cwm recovery from the tar file? or we flash this tar? .. and also where is the stock recovery ? if this cwm not work we can get back to the stock recovery.
reply very soon
Rakesh251 said:
so before we flash we do to remove cwm recovery from the tar file? or we flash this tar? .. and also where is the stock recovery ? if this cwm not work we can get back to the stock recovery.
reply very soon
Click to expand...
Click to collapse
if u are flashing it using Odin u must use .tar!!!
as i have mentioned above the cwm recovery doesn't boot..
if u have already lost the stock recovery here is the link to download
To install follow the same method suggested by PlayfulGod
but replace cwm-grand2.tar with the file downloaded
any one succeeded to boot
Rakesh251 said:
any one succeeded to boot
Click to expand...
Click to collapse
Just was informed that this device appears to be locked down with knox. Knox is Samsungs latest locking method. Some devices with knox dont restrict booting modded boot images (boot/recovery) and some are locked down tighter than grannies panties. The Grand 2 seems to be locked down.
Thanks
Thanks for your efforts..
hope some day we could break Knox security layer :good:
PlayfulGod said:
Just was informed that this device appears to be locked down with knox. Knox is Samsungs latest locking method. Some devices with knox dont restrict booting modded boot images (boot/recovery) and some are locked down tighter than grannies panties. The Grand 2 seems to be locked down.
Click to expand...
Click to collapse
There is no knox security in system and in bootloader like in note2 , S4 and S5 devices .Those devices has knox trip indicator in download mode luckily our device don't has that indicator .Also our device root is supported by @Chainfire .It's just the qualcomm secure boot that restrict any custom recovery and kernel to work in our device .The safestrap recovery can work only if some recognised dev can help us out .
Sent from my SM-G7102 using Tapatalk 2
balliboxer said:
There is no knox security in system and in bootloader like in note2 , S4 and S5 devices .Those devices has knox trip indicator in download mode luckily our device don't has that indicator .Also our device root is supported by @Chainfire .It's just the qualcomm secure boot that restrict any custom recovery and kernel to work in our device .The safestrap recovery can work only if some recognised dev can help us out .
Sent from my SM-G7102 using Tapatalk 2
Click to expand...
Click to collapse
I'll investigate more.
PlayfulGod said:
I'll investigate more.
Click to expand...
Click to collapse
Please do investigate we r all here to test ur upcoming builds .
Sent from my SM-G7102 using Tapatalk 2
Any luck yet?
Hope that one day we will get usb otg cable support for our phone...
sent by my Grand 2
sorry for asking the question in wrong place ...
Don't we have any MegaWipe Script for Grand 2 ?
any news ?
Sent from my SM-G7102 using Tapatalk
Yessss....hope some1 find the way to enable usb otg
Sent from my SM-G7102 using XDA Free mobile app
Awesome
can i use this for Galaxy Grand Prime?
Need stock recovery for 4.4.2 running grand 2. Plz Help...
SM-G7102..... ODIN flashable file
Currently, all official CyanogenMod ROMs use loki tool to install the kernel on the LG G Pad 8.3 v500. Unfortunately, using loki tool causes a benign "secure boot error message" upon startup.
Here are some scripts that can be flashed in the recovery to convert a loki kernel to a bumped (permissive) kernel. The kernel will remain permissive until a new ROM or kernel is flashed again.
When making a kernel permissive, the following commands will be appended to the kernel boot command line:
Code:
androidboot.selinux=permissive selinux=0
Note: Only apply these scripts one time when setting the kernel to permissive mode or the command line above will be appended twice.
Instructions:
1) Flash ROM
2) Flash one of the scripts below, depending on what you want.
1) Convert a loki kernel to a bumped kernel
v500-loki-kernel-to-bumped-kernel-signed.zip
2) Convert a loki kernel to a bumped permissive kernel (turns off selinux)
v500-loki-kernel-to-bumped-permissive-kernel-signed.zip
3) Convert an already bumped kernel to a permissive bumped kernel (turns off selinux)
v500-bumped-kernel-to-bumped-permissive-kernel-signed.zip
Thanks to @Skin1980 for the bash bump code.
Thanks to @aicjofs for the script base.
This is amazing, thanks for your work.
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
annoyingduck said:
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
Click to expand...
Click to collapse
It's fine to use the cm updater, but you will have to reboot into the recovery twice to apply the patch. Also, if you want your Bluetooth pairings to remain intact, then you want to keep the kernel in permissive mode and never let it boot with selinux enabled (at least until the selinux denials are fixed).
@annoyingduck
You can let cm updater download and verify the update and then hit cancel when it asks to install it. Then manually reboot to recovery and install from the cm updater download directory.
Amazing job @Deltadroid! I applied the first patch, rebooted and the warning message was gone!
Thank you very much for your outstanding work!
[]'s
So... This just removes the warning message when booting?
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
Yes
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
That is the only visible effect. It provides a cleaner way of mounting the boot.img
Ok thanks
Works fine with last Infected build.
I assume we have to flash this script after each update.
ledabe974 said:
Works fine with last Infected build.
I assume we have to flash this script after each update.
Click to expand...
Click to collapse
Yes, after each rom or kernel you flash.
Yay! thanks to the permissive script, SuperSU works on CM13! =)
nytral said:
Yay! thanks to the permissive script, SuperSU works on CM13! =)
Click to expand...
Click to collapse
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Deltadroid said:
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Click to expand...
Click to collapse
Well, that's what I thought and what I did first, but actually latest beta SuperSU (2.68) is not breaking the boot sig for some reason (no bootloader error as with previous builds). Looking at logcat during the stuck boot I noticed some zygote process failing because of selinux and that's when I decided to try to disable it -> success! Now a cleaner way would probably be to give the logs to @Chainfire so he can have a look but given the non-popularity of V500 he probably won't care/not be able to fix it without one. Oh well, at least I have something working although not as secure as it should be. So thank you for this :good:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
glyrakos said:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
Click to expand...
Click to collapse
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Deltadroid said:
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Click to expand...
Click to collapse
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
glyrakos said:
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
Click to expand...
Click to collapse
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Deltadroid said:
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Click to expand...
Click to collapse
Maybe I am not doing something good but when using the 3 button method it goes to factory reset and stays there endless if I do not press something .... but power whipes everything (i've re-setup my v500 for about 15 times already....) ... and volume up/down exits the menu and reboots......
Latest TWRP v3.0.2-1 for the Samsung Galaxy SM-A310
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Flash with Odin 3.10.7 using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
twrp_3.0.2-1_sm-a310
TO ROOT
Flash the file below in twrp.
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE LATEST VERSION BELOW:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
NOTE: ON SOME ANDROID 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Device Tree: Coming soon
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Confirmed working by Rotkaeqpchen.
Also thanks to him for his donation. :thumbup: @Rotkaeqpchen, by the way I put a fix in your build for MTP. Does it work?
If you get a USB device not recognised error when enabling MTP then disable it and then quickly hit the button again to re-enable and it should work OK.
ashyx said:
Confirmed working by Rotkaeqpchen.
Also thanks to him for his donation. :thumbup: @Rotkaeqpchen, by the way I put a fix in your build for MTP. Does it work?
If you get a USB device not recognised error when enabling MTP then disable it and then quickly hit the button again to re-enable and it should work OK.
Click to expand...
Click to collapse
Works perfectly, thanks Ashyx!
thomekh said:
Works perfectly, thanks Ashyx!
Click to expand...
Click to collapse
Good, could you confirm something? How long does it take to boot to twrp?
Sure, from the Samsung Galaxy screen to the TWRP logo takes approx 2 seconds.
thomekh said:
Sure, from the Samsung Galaxy screen to the TWRP logo takes approx 2 seconds.
Click to expand...
Click to collapse
That's normal, thanks for confirming.
Worked flawlessly.
NB: If you get a FAP lock error in Odin, Enable OEM unlock in Developer options.
Do i go into download mode first or?
i tried the key combination... but with the combination i only can go into the stock recovery. but not in the download mode ???
is there any trick?
i've managed the flashing..
at first you must shotdown the phone (without connected usb calbe). then go to downloa dmode with vol down + home + power, than you can easyly flash the twrp image. after this go to twrp recovery with the key combination described in the first post and flash supersu.
thx
Does it support the "F" version?
SM-A310F
piroxi said:
Does it support the "F" version?
SM-A310F
Click to expand...
Click to collapse
ashyx said:
Unofficial release -TWRP recovery for the Galaxy A3 - SM-A310F/FD/Y/M Exynos7580
Click to expand...
Click to collapse
. .
ashyx said:
[...] TWRP v3.0.0-0 for the Samsung Galaxy SM-A310 [...]
Device Tree: Coming soon
Click to expand...
Click to collapse
Thanks for TWRP :good: & looking forward to the device tree for the A310 series :highfive:.
Rooted but xmodgames for coc not worked.
Thanks for this custom recovery !
I managed to install TWRP and to root the device.
... but I did not enable OEM unlock in developper options, so I can't boot the phone.
Here are the messages I get :
- "RECOVERY IS NOT SEANDROID ENFORCING"
- "Custom binary blocked by FRP lock"
I have to flash a stock firmware before I can reinstall TWRP.
Where can I get a stock firmware for SM-A310F ? Are the ones listed here safe to flash : http://forum.xda-developers.com/samsung-a-series/help/rom-stock-firmware-samsung-galaxy-a3-t3305861?nocache=1 ?
---------- Post added at 11:34 PM ---------- Previous post was at 11:01 PM ----------
sisssou said:
Thanks for this custom recovery !
I managed to install TWRP and to root the device.
... but I did not enable OEM unlock in developper options, so I can't boot the phone.
Here are the messages I get :
- "RECOVERY IS NOT SEANDROID ENFORCING"
- "Custom binary blocked by FRP lock"
I have to flash a stock firmware before I can reinstall TWRP.
Where can I get a stock firmware for SM-A310F ? Are the ones listed here safe to flash : http://forum.xda-developers.com/samsung-a-series/help/rom-stock-firmware-samsung-galaxy-a3-t3305861?nocache=1 ?
Click to expand...
Click to collapse
Tested one : these roms seem OK
Is there any CUSTOM Rom for the Samsung Galaxy A3 2016?
This is my first Samsung phone, and I would like to know whether there are a lot of updates via OTA or not !
Indeed I want to decide if I have to keep the phone rooted or not to catch these OTAs...
Thanks for your advices
sisssou said:
This is my first Samsung phone, and I would like to know whether there are a lot of updates via OTA or not !
Indeed I want to decide if I have to keep the phone rooted or not to catch these OTAs...
Thanks for your advices
Click to expand...
Click to collapse
Never believe in Samsung's update support. I bought an S5 mini and was promised android l. I got it after the release of android m.....
Any questions?
No more question ; -)
Thanks !
Zocker1304 said:
Never believe in Samsung's update support. I bought an S5 mini and was promised android l. I got it after the release of android m.....
Any questions?
Click to expand...
Click to collapse
Do you know if there are some custom rom for this device?
Hi Everyone,
With all of the hype around the Exynos phone its finally time for the TGY/CHC Snapdragon variants to get some attention.
No this won't work with US variants, please don't ask. This is tested on my normal s10 (SM-G9730). I'm not sure if the s10+ would work.
I've worked with a few key people to get this working. So credit goes to Flatty, Ianmacd and the creators of tomatolei rom.
This setup will let the user do the following:
-Boot/Restart phone without holding any odd button combos to boot into rooted rom.
-Hold the recovery buttons to get into TWRP.
-Not having to worry about losing root when restarting if you forget to hold your buttons, you don't need to hold anything once properly setup.
The following steps below will help you achieve a stock rom with TWRP:
1. You must be on stock rom, ideally non rooted. If you are rooted, flash your stock rom (The rom version is important, this was completed using the ASH2 version of the TGY firmware.) using ODIN (CSC HOME).
2. Once flashed boot into android and ensure OEM unlocking is enabled in developer settings.
3. Boot to download mode by turning the phone off, then press and hold the volume down button along with the Bixby key just beneath it, then press and hold the power button.
4. Flash attached TWRP from download mode. (This led my phone to boot looping). https://www.mediafire.com/file/cg8bcrf78v66v8j/LatestTomato.tar/file
5. Flash the second attached TWRP (you may have to restart and re-enter download mode again). (I believe the above flash is required too, as it likely contains vendor info). https://www.mediafire.com/file/21akg54uxqk3eix/G9730_TWRP_3.3.1-1_tomatolei-0831-v4.0.tar/file
6. Reboot phone to recovery mode (Volume up, bixby and power upon restart) which will now boot you to TWRP.
7. Flash Snapdragon muti disabler from TWRP. https://www.mediafire.com/file/opbsc7wrcr69b2v/multidisabler-samsung-1.6.zip/file *Per @FlatOutRU After flashing multidisabler you must Wipe Data (if you didn't do that before with twrp - Thanks for the clarification.
8. Boot to your rom and ensure all is well.
9. Feel free to download the latest Magisk zip and flash root from TWRP by using the recovery mode button sequence upon restart.
Sidenote: The G9730_TWRP_3.3.1-1_tomatolei-0831-v4.0.tar and tomatolei ROM also let me install PHH AOSP and PHH LineageOS
PHH AOSP microG: https://forum.xda-developers.com/pr...arm64aosp-9-0-0r21-microg-ufofficial-t3878115
PHH LineageOS: https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029
Hopefully this gets a few nice Stock ROMs being produced.
Download links are added.
Fznwolf: congrat for this thread, well explained.
some question:
1) what's bring latestomato.tar ? , because no need this for me
2)magisk work for you even if you don't flash magisk_patched.tar?
3)are you able to make backup into twrp because for me it's failed. i think it work if use tomato rom but i prefer stay to tgy rom
pixiebob said:
Fznwolf: congrat for this thread, well explained.
some question:
1) what's bring latestomato.tar ? , because no need this for me
2)magisk work for you even if you don't flash magisk_patched.tar?
3)are you able to make backup into twrp because for me it's failed. i think it work if use tomato rom but i prefer stay to tgy rom
Click to expand...
Click to collapse
Thanks for the compliment @pixiebob
1) I believe the latestomato.tar has some pieces of tomato rom that allow for booting.
2) Yes, i didnt use magisk_patched.tar. I used the official magisk zip after all of my original steps as the last step.
3) I have several backups, I'm on TGY. Try start from scratch and follow my above steps using a TGY rom. Sounds like you may need to wipe and start over using the original steps provided, make sure to use the multidisabler originally attached.
Fznwolf said:
Thanks for the compliment @pixiebob
1) I believe the latestomato.tar has some pieces of tomato rom that allow for booting.
2) Yes, i didnt use magisk_patched.tar. I used the official magisk zip after all of my original steps as the last step.
3) I have several backups, I'm on TGY. Try start from scratch and follow my above steps using a TGY rom. Sounds like you may need to wipe and start over using the original steps provided, make sure to use the multidisabler originally attached.
Click to expand...
Click to collapse
you are right once multidisabler attached to your first post is installed i'm able in Twrp to backup ending without error, fantastic
pixiebob said:
you are right once multidisabler attached to your first post is installed i'm able in Twrp to backup ending without error, fantastic
Click to expand...
Click to collapse
Great to hear it's working out.
Once we root and install twrp, how we can update the phone ?
Otherwise, thanks for your work !
Yay dude thanks for using my instruction and my modified zips without asking me first
You've got an attempt before - trying to post my 9730 overlay for AOSP
Fznwolf said:
I've worked with a few key people to get this working. So credit goes to Flatty, Ianmacd and the creators of tomatolei rom.
Click to expand...
Click to collapse
No, you didn't work with other people. You just spammed me ,my pm here and in telegram to get explanation and posted it here without permission
You've also forgot one important step. After flashing multidisabler you must Wipe Data (if didn't do that before with twrp)
Multidisabler - i've just changed a few lines in @ianmacd code to get it working on our Snapdragon variant.
Twrp.tar - extracted boot.img and recovery.img from @tomatolei ROM for S10+ 9750
Thanks again @FlatOutRU I've updated the initial description to include the wipe after the muti-disabler flash as per your comments.
Hopefully this allows more work to be done on the Snap s10s!
FlatOutRU said:
Yay dude thanks for using my instruction and my modified zips without asking me first
You've got an attempt before - trying to post my 9730 overlay for AOSP
No, you didn't work with other people. You just spammed me ,my pm here and in telegram to get explanation and posted it here without permission
You've also forgot one important step. After flashing multidisabler you must Wipe Data (if didn't do that before with twrp)
Multidisabler - i've just changed a few lines in @ianmacd code to get it working on our Snapdragon variant.
Twrp.tar - extracted boot.img and recovery.img from @tomatolei ROM for S10+ 9750
Click to expand...
Click to collapse
Thank you, it works perfectly.
what Magisk version do you use ?
Is it working with magisk v20 ?
Vuska said:
what Magisk version do you use ?
Is it working with magisk v20 ?
Click to expand...
Click to collapse
I'm on 19.3, I don't see why 20 wouldn't work.
Fznwolf said:
I'm on 19.3, I don't see why 20 wouldn't work.
Click to expand...
Click to collapse
Not work in G9750 ... dont know why...
Sent from my SM-G9750 using Tapatalk
When you say flash (with only stock recovery installed) do you mean with Odin? Which boxes in odin would this tar files go to (e.g. AP, boot?). My phone is s10+ 9750. has it been tested on that? thanks a lot.
Any chance for 9700 (s10E) support?
NisseGurra said:
Any chance for 9700 (s10E) support?
Click to expand...
Click to collapse
Lets consider my method superseded by https://forum.xda-developers.com/s1...p-3-3-1-v3-t3980463/post80569455#post80569455
Thank you @Mentalmuso
heavenly86 said:
When you say flash (with only stock recovery installed) do you mean with Odin? Which boxes in odin would this tar files go to (e.g. AP, boot?). My phone is s10+ 9750. has it been tested on that? thanks a lot.
Click to expand...
Click to collapse
This would be AP, please use https://forum.xda-developers.com/s1...p-3-3-1-v3-t3980463/post80569455#post80569455
Vuska said:
Not work in G9750 ... dont know why...
Sent from my SM-G9750 using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/s1...p-3-3-1-v3-t3980463/post80569455#post80569455 will work.
Fznwolf said:
I'm on 19.3, I don't see why 20 wouldn't work.
Click to expand...
Click to collapse
Please do not use 20, it is not found to be working. Stick with 19.3.
Any luck on the 975U. I have e an unlocked VZW 975U running Android Q
Blackweiser35 said:
Any luck on the 975U. I have e an unlocked VZW 975U running Android Q
Click to expand...
Click to collapse
I see no one's responded to you in the last few days, probably because the OP says to not bother asking if it works with US variants. No there's no known way to get root on one of the 97_U variants. The bootloader is locked, and it would take a miracle to bypass that.
Cannot use Dex for PC function.
Could you upload tomatolei's twrp v6, which updated the kernel to support the Dex funtion? Many thanks!
AOSP Q for Suzu/f5121
DISCLAIMER
As always use it at your own risk.
Build it in my spare time to test how the development is proceeding.
Installation instructions
NB: This is a full software update in the sense that will replace everything, recovery included, with aosp version. You need to reflash twrp afterwards.
Clean Install
enter twrp and factory reset
format data partition (only if coming from Pie or below)
flash the rom
flash GApps (optional)
reboot
Updating from previous version
enter TWRP and wipe dalvik/cache
flash ROM
reboot
Alternative way to install
You can also unzip the file and flash via flashboot only what you need:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata.img (only if not updating or coming from Pie or below)
fastboot flash oem xxxx.img
Now you can boot into TWRP and flash gapps and other stuff if you want.
First boot will get stuck on Sony logo for 30/40 seconds, and maybe reboot itself one or two time. Just have patience and everything will be all right
Downloads:
ROM: Latest Build
OEM: Binaries for 4.9 kernel
TWRP: Official TWRP for Suzu
BitGapps: Suggested GApps
What's works:
RIL
Bluetooth
Wifi
Fingerprint
NFC
Camera
USB tethering
Everything else?
What doesn't:
Random reboots (should be solved in latest build)
WiFi Hotspot
Expected the same bugs for Pie ROM since the kernel and binaries are the same, but let me know if you find anything else, will do my best to try to fix it.
Click to expand...
Click to collapse
Changelogr41
Update sources to r41
Overvolt BIG processor to improve stability on higher frequencies (should fix random reboots)
r33
Update sources to r33
r32.v1b
Reverted patch to enable developer option by default
r32.v1
Removed default searchbar from Launcher3
Enabled developer settings by default
Add MicroG support (testing)
r32:
Initial booting build
Click to expand...
Click to collapse
ROM Version: r41
ROM Status: Stable
Created: 2019-12-04
Last Update: 2020-09-20
Thanks to:
@twain55 for the screenshot and testing
@dslul to help in the bug fixing
@ix5 for the initial patches
sonyxperiadev project for providing sources
and last but not least thanks to all that will test this.
Screenshots
flashed with fastboot and stuck at splash screen
Adi_OP said:
flashed with fastboot and stuck at splash screen
Click to expand...
Click to collapse
Still testing and had the same results. Can you try to use the old OEM IMG for pie and report if boots? If not I'll try It during the weekend and let you know.
EDIT
Tried with the pie OEM IMG and doesn't boot. Will rebuild the boot image this weekend and see how to fix
Stuck at splash screen too, using fastboot!
Same here with twrp..try with and w/o gapps,stuck at sony logo.It seem the problem is at boot image
lookmanns14 said:
Same here with twrp..try with and w/o gapps,stuck at sony logo.It seem the problem is at boot image
Click to expand...
Click to collapse
It seems to me too. I'm trying to find where is the issue. Building another image today and tested on my device but didn't worked either.
Does it work for F5122?
Thank you for your try.
Does it work for F5122 as well.
Hope you to fix this rom as a stable.
Good luck
Sorry for the waiting, I've had a lot of work to do lately. Hope to have news/a new build (at least for boot.img) this weekend.
New images are up. I'll try them this afternoon (out now) but if someone would take the leap before me here it is the link
https://mega.nz/#F!vNtx2QZZ!GuV1qwYXjLk3ajd3xoaPPA
Let me know. And thanks again for helping me testing.
Unfortunately, still stuck at Sony logo... I used the latest OEM released on December 10th, SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2C_loire, will try with SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2B_loire, but I doubt this will change anything!
Iscariah said:
Unfortunately, still stuck at Sony logo... I used the latest OEM released on December 10th, SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2C_loire, will try with SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2B_loire, but I doubt this will change anything!
Click to expand...
Click to collapse
I doubt it too sadly but if still stuck I'm at a loss right now. I've to try to see if I can catch some log even if stuck at Sony. Thanks for the report
Any update on this ROM? Is it still in development?
GOrMHATRe said:
Any update on this ROM? Is it still in development?
Click to expand...
Click to collapse
It is. Latest build still doesn't boot. I'm debugging to see if I can find the problem.
Have we wait for next weekends till any further update?
Any good news
[email protected] said:
Any good news
Click to expand...
Click to collapse
Sadly not yet. Having trouble with the building of r15. I think that could be some changes in Q building system because pie build correctly. Hope to fix in this holidays.
ParanoidNemo said:
Sadly not yet. Having trouble with the building of r15. I think that could be some changes in Q building system because pie build correctly. Hope to fix in this holidays.
Click to expand...
Click to collapse
Cheers
Any good news
Are there still this random reboots and homescreen freezes we have with Pie and the 4.9 kernel?
mase76 said:
Are there still this random reboots and homescreen freezes we have with Pie and the 4.9 kernel?
Click to expand...
Click to collapse
Right now the ROM doesn't boot. The issue is upstream and as far as I know this should be fixed when the v3 of the binaries is released (right now we are at v2c). Hopefully the reboot issue will be fixed but we have to wait sadly.
@ParanoidNemo
Which kernel did you use?