Related
Code:
Disclaimer:
I am not responsible for anything that may happen to your phone as a result of installing this GSI and/or kernels. You do so at your own risk and take the responsibility upon yourself.
MOD EDIT: Remember to be prepared for an experimental or unstable ROM. If do you not know what you are doing or not experienced with flashing and recovering your data then it's not recommended.
REMEMBER TO BACKUP EVERYTHING AS THIS WILL REPARTITION YOUR USERDATA AND WILL WIPE YOUR INTERNAL STORAGE. ALSO, REMEMBER TO READ EVERYTHING AS ALL FIXES ARE POSTED BELOW. DON'T JUST FLASH THEN JOIN TELEGRAM TO ASK WHY THIS DOESN'T WORK FOR YOU.
READ THE IMPORTANT NOTES POSTED HERE
TO REVERT TO NON-TREBLE/STOCK ROM, WATCH THIS VIDEO BY @GizmoFreak OR FOLLOW THIS POST
Here's everything I can provide to the normal user willing to try this out on their Mi A1.
PLEASE VISIT THIS NOTE TO SEE ALL THE REMAINING BUGS
OR JUST READ THEM HERE
SELinux is permissive
Hw key lights don't light up
Everything else works fine. Just need to update your Google Play services app and you can restore apps via Google Backup (if you didn't already do it with Titanium Backup). Yes, rooting with Magisk works and some modules work as well such as Blobmojis among others.
Here are the steps to install it in your Mi A1 if you're coming from stock ROM
Or watch a video made by @GizmoFreak
Enable Developer options in Settings app
Check Enable OEM Unlocking
Reboot to fastboot mode
Unlock your bootloader
Install TWRP-fastboot only through fastboot boot command (Extract the .img file from the zip)
Flash CosmicDan's TWRP Installer through your current TWRP. Credits to @CosmicDan for his TWRP and @mohancm for official TWRP sources.
Reboot to TWRP recovery
Go to WIPE then ADVANCED then click FORMAT data. This will remove Encryption on your device and allows you to set new passwords when installing the GSI. Note that this will format your internal storage.
Treblelize through TWRP Tissot Manager (Go to advanced, click Tissot Manager and choose the repartition userdata option. Select singleboot option then click repartition)
Flash latest Vendor.img as VENDOR IMAGE
Flash A/B system Pie PR2 img as SYSTEM IMAGE (Extract the .img file from the zip) (special thanks to @dgadelha for the sGSI)
Flash POST-sGSI 1 tissot zip.
Flash POST-sGSI 2 tissot zip.
Flash a treble-compatible kernel (Moun, ProjectK,Velocity)(credits to @mountaser halak, @khusika, @kdragon)
Reboot to system.
Once booted, install the latest Play services linked above either via the Files app or via adb. This will fix the Pixel Setup and Google Backup issues as well as allows you access to the Play Store without problems.
You can now flash Magisk 17.3. This is the version that works properly with treble. Credits to @topjohnwu for Magisk.
Install the Data transfer tool APK update as well.
Special thanks to @erfanoabdi for porting the Pie A/B GSI.
Some features may seem to be broken but can actually be fixed with a few tweaks
USB MTP FIX
To enable USB MTP, enable Developer options in the About phone section of the Settings app by tapping the Build Number 4 times. Then look for the File Transfer option in the Dev options.
ENABLE NAV BAR GESTURES
To enable Nav Bar, I installed this nav bar enabler by @Hugwalk via Magisk.
After rebooting, go to Settings > System > Gesture and enable Swipe Up on Home Button to enable the Nav Bar Gestures.
SUBSTRATUM
Substratum is now much better for Pie.
Install the latest APK from this telegram channel and now all themes with Pie support can be installed.. Just reboot after building the themes and go into managers to enable the overlays you built.
Ethereal - https://play.google.com/store/apps/d...ethereal&hl=en
Outline - https://play.google.com/store/apps/d....outline&hl=en
Compound - https://play.google.com/store/apps/d...compound&hl=en
Sai's theme - https://t.me/tissotpsemigsi/33526
Click to expand...
Click to collapse
You should have the Android Pie booting on your Mi A1 now with less issues.
To update from PR1 to PR2, you can do so without wiping data
Wipe system ONLY
Flash PIE PR2 AB GSI
Reboot to system
Click to expand...
Click to collapse
To update your post post GSI zips, follow this
Wipe vendor ONLY
Flash vendor
Flash POST-sGSI 1 tissot zip.
Flash POST-sGSI 2 tissot zip.
Reboot to system
Click to expand...
Click to collapse
Awesome work @joeyhuab bro ?
Edit:- Chrome sucks! Posted same thing twice.
Youtube not working for me(
Great job!!!i will wait to change to beta
Tornado95 said:
Youtube not working for me(
Click to expand...
Click to collapse
I also encounter YouTube issues. :/
Don't work the camera and black for me
ErickCartman17 said:
Don't work the camera and black for me
Click to expand...
Click to collapse
Try Footej Camera from Play Store please, it can be usefull if Footej or Open Camera works
waiting camera fix
cant mount system(invalid argument)
Failed to mount system after i try to flash GSI
I will wait for the stable...but is a good work... Thanks for try this.
andrexp31 said:
I will wait for the stable...but is a good work... Thanks for try this.
Click to expand...
Click to collapse
lol, then just wait for the official release. This is as close as we can get, for now since google hasn't uploaded the source code for P yet
I'm already looking into a fix for Camera. I'll post it once it's available.
What if I want to come back from Android Phone to another Custom ROM? Do I have to "un-treble" the device?
When I Flash A/B system GSI img i have a 255 error: Updater process ended with ERROR: 255 Error installing xip file `tissot_manager/flash_proxy.zip`. How i can fix it? What is the problem?
danilguy said:
When I Flash A/B system GSI img i have a 255 error: Updater process ended with ERROR: 255 Error installing xip file `tissot_manager/flash_proxy.zip`. How i can fix it? What is the problem?
Click to expand...
Click to collapse
Remove the spaces from the folder name and try... Works for me...
Camera has been fixed. Just adding some more fixes and we'll probably get fingerprint working too. I'll update the links later when done.
joeyhuab said:
Camera has been fixed. Just adding some more fixes and we'll probably get fingerprint working too. I'll update the links later when done.
Click to expand...
Click to collapse
U have don great work
Really well done
Waiting for camera, fingerprint and flash bugs fixed and i will surely test the rom
What about Bluetooth?
Chris_Cheekyz said:
What about Bluetooth?
Click to expand...
Click to collapse
Fixed as well together with Camera fix. Credits to Rupansh and @kdragon for using Whyred's blobs. Credits also to @ghpranav for BT fix.
Download
[A530x][A730F]
SaboorROM
PLEASE READ ALL THIS BEFORE DOING ANYTHING
________________________________________________
NOTICE:
I am not responsible for any happy endings, a nuclear war with your device, your alarm clock electrically shocking you, or your device literally freezing, so dont blame me for my mistakes or yours, or else i will laugh at you
Please backup your device (System, Data, EFS, and Cache, Especially EFS) because you might regret flashing this
________________________________________________
CREDITS:
@prashantp01 for Quantum Kernel
SuperR kitchen to build rom
________________________________________________
FEATURES:
Canada A530WVLU4CSCA base
Debloated
Deknoxed
Rooted
S10 Sounds and ringtones
Screen Recording (check section 2 on post #3 for more details)
build.prop tweaks
Status bar size options (check section 1 on post #3 for more details)
G975F/G975W ODM
ODM mods that add mobile data quick settings tiles etc
Applock
Call recording
Mobile data toggle in power menu
________________________________________________
BUGS:
Freezes on bootanimation and when playing video (sometimes) (i dont think there is with 4/23 build, someone test and tell me ASAP)
Digital wellbeing not showing stats (check section 3 on post #3 for workaround) (DIGITAL WELLBEING NOT AVAILABLE ON 4/23 BUILD I WILL ADD IT ON FUTURE BUILDS LOL I JUST FORGOT ABOUT DIGITAL WELLBEING)
Everything else works
________________________________________________
INSTRUCTIONS:
1. Download the ROM zip, and zip #2 for your model under this section
2. Boot into TWRP
3. Wipe system, cache, and data
4. Flash ROM zip
5. Flash zip #2
6. Boot and setup
7. done! (PLEASE READ THE BUGS BEFORE YOU GO TO THE COMMENTS AND SAY "sar why my phone freeze so much ur rom is stupid")
________________________________________________
DOWNLOAD
DOWNLOAD ROM AND ZIP #2
DOWNLOAD UNTESTED NEWER 4/23 BUILD AND ZIP #2
________________________________________________
How to update from existing version of rom
1. Dont forget to download the zip #2 update too, that zip updates too!
2. Flash ROM zip
3. Flash zip #2
4. Wipe cache/dalvik
5. Wait for device to finish optimizing and updating before reporting any bugs
________________________________________________
XDA:DevDB Information
SaboorROM, ROM for the Samsung Galaxy A8+ (2018)
Contributors
587.saboor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 420-11:11AM
Stable Release Date: 2019-04-20
Current Beta Version: 4-23-6:50PM
Beta Release Date: 2019-04-23
Created 2019-04-13
Last Updated 2019-04-23
/////////////////////////////////////////////////////////////////
Click here to join us in the one and only A8/A8+ Telegram group
/////////////////////////////////////////////////////////////////
_____________________________________________
STATUS BAR SIZE
If you see the screenshot below, you'll see the status bar is a bit big (pls don't mind the blank settings page lol)
https://photos.app.goo.gl/wiYKVbJed52t9SiN6
DON'T PANIC BIG STATUS BAR HATERS! THIS IS ONLY OPTIONAL AND THIS EVEN HAS OPTION FOR SMALLER STATUS BAR
How do you get it, you ask?
just follow these steps after installing the rom
1. go to settings
2. developer options (u already know how to turn dev options on)
3. scroll down to "Simulate display with a cutout" and tap it
4. select a size of status bar (this wont add any notch on your phone, this only makes the status bar a bit bigger like on the screenshot)
5. done!
_____________________________________________
SCREEN RECORDER
You can record your screen with sound too
How do you get it, you ask?
just add it to the quick settings menu
_____________________________________________
DIGITAL WELLBEING FIX
Digital wellbeing doesn't show stats but you can make it show
How?
just follow these steps:
1. go to settings
2. search "Special Access"
3. press Special Access
4. scroll down to Usage data access and press it
5. press the 3 dot menu on the top right
6. press Show system apps
7. press Digital wellbeing and enable allow usage tracking
8. done!
_____________________________________________
SCREENSHOTS
https://photos.app.goo.gl/4USaY78w3cm8DG5p9
_____________________________________________
yeet
587.saboor said:
yeet
Click to expand...
Click to collapse
Why do you think Samsung released a updated that has bugs?
mchlbenner said:
Why do you think Samsung released a updated that has bugs?
Click to expand...
Click to collapse
idk cuz they're high? ????
A8 2018 - SM-A530F
Upgrade from Nougat (Android 7.x):
-installed newest TWRP via TWRP
-backed up the old Nougat via TWRP
-wiped and installed DOWNLOAD ROM AND ZIP #2 (non-beta) via TWRP
-reboot
-it took about 15 minutes and several reboots --> be patient
-message "KERNEL IS NOT SEANDROID ENFORCING" at every boot now (top left of screen, small red font)
Root problem:
if you grant apps root, magisk manager is constantly crashing (if an app uses root) (e.g Titanium Backup, Total Commander)
-reduce to core functions in magisk manager did not help
-upgrading magisk manager to 7.1.1 did not help
-downgrading magisk to 18.1 helped (I removed magisk 19.0 with Magisk-uninstaller-20190328.zip in TWRP first)
EdXposed is working (I had to flash it _twice_ via TWRP)
-flash magisk-riru-core-v18.zip
-flash magisk-EdXposed-v0.3.1.7_beta-release.zip
-install EdXposedInstaller_v2.2.4-release.apk
Important apps that work: AFWall+ 2.99, XPrivacyLua 1.24, Titanium Backup, FM-radio
Looks like, I can't go back to Nougat (just want to do this because I missed to save settings in XPrivacy and wifi passwords before the upgrade).
Downgrading to Nougat (Restore in TWRP) didn't work:
-backed up the new Pie and wiped data, system, cache
-restoring Nougat went well but gave one error at the end:
-Failed to mount '/system' (Invalid argument)
-I got bootloops.
So I restored Pie in TWRP:
-wiped data, system, cache
-wiping went well but gave one error at the end:
Failed to mount '/system' (Invalid argument)
-restore went well, no bootloops
phocriab said:
A8 2018 - SM-A530F
Upgrade from Nougat (Android 7.x):
-installed newest TWRP via TWRP
-backed up the old Nougat via TWRP
-wiped and installed DOWNLOAD ROM AND ZIP #2 (non-beta) via TWRP
-reboot
-it took about 15 minutes and several reboots --> be patient
-message "KERNEL IS NOT SEANDROID ENFORCING" at every boot now (top left of screen, small red font)
Root problem:
if you grant apps root, magisk manager is constantly crashing (if an app uses root) (e.g Titanium Backup, Total Commander)
-reduce to core functions in magisk manager did not help
-upgrading magisk manager to 7.1.1 did not help
-downgrading magisk to 18.1 helped (I removed magisk 19.0 with Magisk-uninstaller-20190328.zip in TWRP first)
EdXposed is working (I had to flash it _twice_ via TWRP)
-flash magisk-riru-core-v18.zip
-flash magisk-EdXposed-v0.3.1.7_beta-release.zip
-install EdXposedInstaller_v2.2.4-release.apk
Important apps that work: AFWall+ 2.99, XPrivacyLua 1.24, Titanium Backup, FM-radio
Looks like, I can't go back to Nougat (just want to do this because I missed to save settings in XPrivacy and wifi passwords before the upgrade).
Downgrading to Nougat (Restore in TWRP) didn't work:
-backed up the new Pie and wiped data, system, cache
-restoring Nougat went well but gave one error at the end:
-Failed to mount '/system' (Invalid argument)
-I got bootloops.
So I restored Pie in TWRP:
-wiped data, system, cache
-wiping went well but gave one error at the end:
Failed to mount '/system' (Invalid argument)
-restore went well, no bootloops
Click to expand...
Click to collapse
lol
first of all, why are you downloading this rom from nougat? it's gonna obviously cause problems if you're coming from nougat so i recommend going to pie first from odin, then flash this rom, or oreo if you really dont want pie.
second of all, you shouldnt use xposed with samsung firmware, or else you would encounter issues but it's fine if you want to use stuff like greenify or something
third of all, the KERNEL IS NOT SEANDROID ENFORCING is normal but shouldn't show up anyways, it's showing up because you have old nougat bootloader so thats another reason to flash official pie from odin before flashing this rom
587.saboor said:
first of all, why are you downloading this rom from nougat? it's gonna obviously cause problems if you're coming from nougat so i recommend going to pie first from odin, then flash this rom, or oreo if you really dont want pie.
Click to expand...
Click to collapse
that's the lazy man's approach, just give it a try
587.saboor said:
second of all, you shouldnt use xposed with samsung firmware, or else you would encounter issues but it's fine if you want to use stuff like greenify or something
Click to expand...
Click to collapse
okay, i switchted from XPrivacyLua to AppOps
587.saboor said:
third of all, the KERNEL IS NOT SEANDROID ENFORCING is normal but shouldn't show up anyways, it's showing up because you have old nougat bootloader so thats another reason to flash official pie from odin before flashing this rom
Click to expand...
Click to collapse
imho it is not obvious: you can still boot windows 10 with a windows 7 bootloader, same for linux
probably you should add that hint to you first post
phocriab said:
imho it is not obvious: you can still boot windows 10 with a windows 7 bootloader, same for linux
probably you should add that hint to you first post
Click to expand...
Click to collapse
nah i dont really need to add the hint cuz ur literally the only one here who's flashing on nougat bootloader lol
587.saboor said:
nah i dont really need to add the hint cuz ur literally the only one here who's flashing on nougat bootloader lol
Click to expand...
Click to collapse
I recently upgraded to the latest bootloader to see if it would help pie boot better.
Which it did not these roms issues freezing on boot up and video freezing is Samsung fault.
I have contacted them and I ask why they would released a buggy update their been giving me excuses instead of answers.
Back to Oreo for a couple months until I sell this phone no more Samsung!
mchlbenner said:
I recently upgraded to the latest bootloader to see if it would help pie boot better.
Which it did not these roms issues freezing on boot up and video freezing is Samsung fault.
I have contacted them and I ask why they would released a buggy update their been giving me excuses instead of answers.
Back to Oreo for a couple months until I sell this phone no more Samsung!
Click to expand...
Click to collapse
ye its complete bs that they give excuses and s*** like that smh
new 4/20 build is out
Changelog:
Call recording
Mobile data toggle in power menu
My phone broke, so development will be temporarily suspended till I get a replacement.
For now, as an "update" flash quantum kernel v2 and then magisk after flashing the latest version
For now, I'll see y'all later when I get a new replacement a8
Pls donate to me
paypal.me/youhavebeenyoted
This is just so I can fully pay for my replacement A8 which is $229 or make it more affordable for me
I'd be very thankful if you donate
lol i did say development was suspended till i get a replacement a8 but i just dont know what to do in my free time other than this
anyways new build 4/23 blah blah blah heres the changelog:
separated zip 2 for people with limited internet data i guess
updated base to a530w base
someone pls try this build and tell me if there are any freezes or not ASAP thanks
enjoy
587.saboor said:
lol i did say development was suspended till i get a replacement a8 but i just dont know what to do in my free time other than this
anyways new build 4/23 blah blah blah heres the changelog:
separated zip 2 for people with limited internet data i guess
updated base to a530w base
someone pls try this build and tell me if there are any freezes or not ASAP thanks
enjoy
Click to expand...
Click to collapse
What are the two zips
mchlbenner said:
What are the two zips
Click to expand...
Click to collapse
What two zips?
Theres 2 zips to flash for the rom
First one is the rom zip
Then the zip 2, ignore the ones that arent your model number
587.saboor said:
What two zips?
Theres 2 zips to flash for the rom
First one is the rom zip
Then the zip 2, ignore the ones that arent your model number
Click to expand...
Click to collapse
I have discovered that on the latest pie you have use custom kernel or you will get locked but reflashed stock then I was able to flash twrp.
mchlbenner said:
I have discovered that on the latest pie you have use custom kernel or you will get locked but reflashed stock then I was able to flash twrp.
Click to expand...
Click to collapse
Lol the zip 2 contains the custom kernel
Introduction
This is an unofficial build of LineageOS 16 for Redmi Note 7 Pro. Differences from the one provided by Dyneteve include:
- Ported the CAF wrappedkey encryption stuff, which is what MIUI uses, over using patches from https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged), This requires an recovery with wrappedkey decryption support, e.g. this one
- Applied unmerged patch https://review.lineageos.org/c/LineageOS/android_build/+/247066 to mount system as /system_root properly on install. This makes addon.d scripts (e.g. Magisk / GApps survival script) work again on our device. This requires an recovery with proper system_as_root support, e.g. this one
- ROM includes its own vendor image instead of relying on one provided by MIUI. I intend to try to build as much of vendor image as possible from CAF source in the future.
Flash instructions
- Make sure you have the latest firmware images. If not, update them before flashing.
- Flash a TWRP recovery that supports mounting system as /system_root and supports wrappedkey encryption (the one provided above)
- Wipe data partition (without wiping /data/media). If you came from another non-CAF ROM (ROM that do not support wrappedkey mode) and had encryption enabled, you will need to format your data partition (including /data/media).
Note: If you decide to format your data partition, always format with 'advanced wipe' in TWRP recovery. DO NOT use fastboot -w or fastboot erase, even if you do, please format again in recovery, otherwise the system might not work.
- Install the zip in TWRP.
- Install whatever you want e.g. Magisk, OpenGapps
- DO NOT install the fcrypt disabler.
- Reboot and enjoy
Known issues
DO NOT remove screen lock passwords if you set one. You can change the password just fine, but DO NOT REMOVE IT. YOU WILL LOSE ACCESS TO ALL DATA IF YOU DO THIS AND REBOOT.
Removing screen lock passwords work after 20190528-1.
Downloads
20190609-1: https://mega.nz/#!PdRnxIia!Boh-a8e5JHt8YEBwbXKt8rWYj3PC56mdpEIXwDEY2ng
changelog: 1) Merged upstream LineageOS (June security patch) 2) Updated kernel to 4.14.123 3) Updated MIUI binary blobs 4) Some clean-up
NOTE: /proc/last_kmsg support is removed due to incompatibility. This feature is replaced by pstore, which you could find more information on through some Google-fu.
History versions:
20190528-1: https://mega.nz/#!nZRTQCbS!qf-RdT-ijayg8UBxyyz3Hoi2O_8ZtpWewgNv-eVDcqA
changelog: 1) merged upstream LineageOS; 2) fixed the bug of removing screen lock passwords, now it won't swallow all your data (this commit: https://github.com/PeterCxy/android...mmit/d2fe3434cddb98eeb414906e71a817559ade1b26; 3) merged LTS kernel 4.14.122, thanks to YaroST and aviraxp; 4) fixed potential charging problem; 5) some other kernel improvements
20190526-1: https://mega.nz/#!rRgwmY5T!2fQyDjukLoGmk7KRtas5n2Y_it9QS_s2noAItzNvFfY
Sources
Device: https://github.com/PeterCxy/android_device_xiaomi_violet
Kernel: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150
Other changes and patches: see what is available on my GitHub https://github.com/PeterCxy/, everything is open-source for this ROM.
Contributors
PeterCxy, GuaiYiHu, aviraxp
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet
Thanks ?
Thank you for the ROM!
There's a Typo in the ROM os version description.
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.
jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
Sorry I have no idea here.. What ROM you were on before flashing this?
Dwughjsd said:
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.
Click to expand...
Click to collapse
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.
jyoti.id said:
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.
Click to expand...
Click to collapse
Just keep in mind that safety first
Download link not working
Edit: UC browser was the culprit
dwughjsd said:
just keep in mind that safety first
Click to expand...
Click to collapse
how u fixed storage issue
gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
It was @jyoti.id that faced and solved the issue, so let's call him for an answer
rom keeps rebooting into twrp , i did every step
gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
I just flashed the whole fastboot rom again & it fixed everything.
---------- Post added at 04:34 AM ---------- Previous post was at 04:33 AM ----------
King_Dinoco10 said:
rom keeps rebooting into twrp , i did every step
Click to expand...
Click to collapse
Same thing happened with me too
Device not charging above 86%. Anyone else facing this bug ?
PeterCxy said:
Sorry I have no idea here.. What ROM you were on before flashing this?
Click to expand...
Click to collapse
The phone does not charge more than 91%!
lapo_chel said:
The phone does not charge more than 91%!
Click to expand...
Click to collapse
now should be fixed, try today's new build
PeterCxy said:
now should be fixed, try today's new build
Click to expand...
Click to collapse
Safetynet does not pass.
lapo_chel said:
Safetynet does not pass.
Click to expand...
Click to collapse
It's because I used vendor files from MIUI beta. You can bypass it with a magisk module to reset the build fingerprint
Many thanks for your build! I like it much.
IMHO, SELinux should be enabled.
Hello,
can anybody help me for my Problem with my Galaxy S4 GT-I9506
i have do the following
1. TWRP install the actual version
2. flash lineage-16.0-20190609-UNOFFICIAL-ks01ltexx https://forum.xda-developers.com/galaxy-s4/i9506-develop/rom-lineageos-16-0-unofficial-galaxy-s4-t3848597
3. flash open_gapps-arm-9.0-pico-20190612 TWRP
4. flash Magisk-v19.3 mit TWRP
But i have problems with them
https://prntscr.com/o7onem
https://prntscr.com/o7oneu
https://prntscr.com/o7oner
i have no idea what i can do can anybody help me please?
Does the ROM come rooted? It may have system root inside still, my s5 ROMs always did I think. I always had to use adb shell or flash a zip inside twrp. Usually did both.
Search XDA for osm0sis tool called unsu, it should be a .zip. Flash in twrp after installing gapps and booting once. This should clear system root, and allow you to pass once magisk is installed.
The other issue I can think of is maybe signature verification or something with the playstore. I don't remember what it is, my phones and ROMs have always worked after magisk. If the above steps don't work maybe that's related. We will have to look around if that's the case
I had a look at the device tree and I can see a couple of things for your dev @kyasu to possibly add
- we had safetynet start failing a few weeks back on i9505 and these were the fixes I found
- Product_name - Samsung never released a product called full_ks01ltexx - will need to be set to correct product that google recognises by a build_prop_override ("GT-I9506" or similar).
- Change build fingerprints to pixel3 versions.
- hide permissive with init script.
these 2 commits here show what needs done:
https://github.com/JDCTeam/android_...mmit/ea27cf29e4084d860fb8549be2e3cdb1599a6d08
https://github.com/PixelExperience-...mmit/045dc32219172a288c10f503478deb3eb3b2aee5
andrew2432 said:
Does the ROM come rooted? It may have system root inside still, my s5 ROMs always did I think. I always had to use adb shell or flash a zip inside twrp. Usually did both.
Search XDA for osm0sis tool called unsu, it should be a .zip. Flash in twrp after installing gapps and booting once. This should clear system root, and allow you to pass once magisk is installed.
The other issue I can think of is maybe signature verification or something with the playstore. I don't remember what it is, my phones and ROMs have always worked after magisk. If the above steps don't work maybe that's related. We will have to look around if that's the case
Click to expand...
Click to collapse
is this tool correct? https://forum.xda-developers.com/showpost.php?p=63615067
is the rom correct what i use?
OK i have unSu the device and have reinstall Magisk ..
https://prnt.sc/o929eu
but i have the same problem
tuvok1981de said:
OK i have unSu the device and have reinstall Magisk ..
https://prnt.sc/o929eu
but i have the same problem
Click to expand...
Click to collapse
- have you tried changing fingerprint with Magiskhide?
- has it worked previously and just recently stopped working or is this your first attempt?
- do other users on the same ROM have similar results?
I incidentally also checked DT if the ROM is rooted and doesn't look like it. Kernel also has namespace commits too, so it's not that.
Buff99 said:
- have you tried changing fingerprint with Magiskhide?
- has it worked previously and just recently stopped working or is this your first attempt?
- do other users on the same ROM have similar results?
I incidentally also checked DT if the ROM is rooted and doesn't look like it. Kernel also has namespace commits too, so it's not that.
Click to expand...
Click to collapse
- yes i have make with MagiskHidePropsConf-v.4.0.3 and terminal props S4 and S4 Active variante but it will not do this
- it will not work all the time where i have flash my S4
- i have no idea iam not the developer from the rom iam only a User
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
andrew2432 said:
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
Click to expand...
Click to collapse
Point 1. is on the Phone
ähm where must i make Point 6 ?
andrew2432 said:
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
Click to expand...
Click to collapse
OK i have make flash new all 5 Points
but ctsProfile: false / basicIntegrity: false on Magisk Manager
tuvok1981de said:
-
- i have no idea iam not the developer from the rom iam only a User
Click to expand...
Click to collapse
Yeah, well this is a developer forum. There is a thread for the ROM you use. It is assumed you have already seeked advice there from other users of the same rom...?
Being aware of whether others have this working or not shows whether you are wasting your time or not.
Buff99 said:
Yeah, well this is a developer forum. There is a thread for the ROM you use. It is assumed you have already seeked advice there from other users of the same rom...?
Being aware of whether others have this working or not shows whether you are wasting your time or not.
Click to expand...
Click to collapse
in this forum say the users i must go in the Samsung S4 Forum and ask my Question!
tuvok1981de said:
in this forum say the users i must go in the Samsung S4 Forum and ask my Question!
Click to expand...
Click to collapse
I searched safety net inside the ROM forum, it said to change selinux to enforcing. I am not sure how. Maybe with a magisk module
Edit: credit for these instructions goes to @DiamondJohn
The user only installed magisk and safety net passed. Are you installing xposed or anything?
stecko said:
Can you guide me how to switch selinux to enforcing?
Click to expand...
Click to collapse
in a terminal, or part of a boot script
Code:
su;
setenforce 1;
or you could try the app I built, where you will find it under the menu
Code:
Current State>SELinux>Set SELinux Enforcing.
https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260
andrew2432 said:
I searched safety net inside the ROM forum, it said to change selinux to enforcing. I am not sure how. Maybe with a magisk module
Edit: credit for these instructions goes to @DiamondJohn
The user only installed magisk and safety net passed. Are you installing xposed or anything?
in a terminal, or part of a boot script
Code:
su;
setenforce 1;
or you could try the app I built, where you will find it under the menu
Code:
Current State>SELinux>Set SELinux Enforcing.
https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260
Click to expand...
Click to collapse
Very Nice .. this part have help ..
Code:
su;
setenforce 1;
https://prnt.sc/o9gchi
thank you!
[UPDATE/KEEP ROOT GUIDE] SEP 2020 (RP1A.200720.009) "CORAL" Magisk/Stock Boot Images
**Huge thanks to @murphyjasonc for sharing the pre-patched boot image, and @sidhaarthm for testing this method and his detailed notes!**
PLEASE READ ALL ADDITIONAL NOTES IN THE FIRST 3 POSTS. THIS IS A MAJOR UPDATE TO A NEW VERSION OF ANDROID AND CONSEQUENTLY COMES WITH A MUCH HIGHER RISK OF BOOTLOOPING IF YOU'RE NOT CAREFUL. I PERSONALLY AM WAITING TO UPDATE TO ANDROID R (WAITING ON GRAVITYBOX GOODNESS) SO I WON'T BE ABLE TO HELP AS MUCH - PLEASE BE KIND TO ONE ANOTHER AND HELP EACH OTHER OUT! =)
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR "RP1A.200720.009, Sep 2020, All carriers except IN"!
Magisk Canary v20424 (11f254e5) Patched Boot Image: https://www.androidfilehost.com/?fid=8889791610682933259
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=8889791610682933258
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=8889791610682933260
[SAFETYNET INFO]: Again, I'm not updating myself yet, so I'm not sure about this. I will update this info as others report back. On Android 10, using the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choosing option 2 - Force BASIC key attestation would force BASIC HW attestation and allow SafetyNet to pass again. This works perfectly for me, and I even run additional mods including EdXposed. I'm not sure if this works on Android 11, and I won't be able to confirm myself for a while. If anybody tries it, please let me know and I'll update this section. The module and info on using it can be found here: https://forum.xda-developers.com/ap...just search for it in the Magisk Manager app.
READ THIS ENTIRE POST BEFORE PROCEEDING!
ADDITIONAL PRELIMINARY STEPS COMPARED TO PREVIOUS MONTHS - DO NOT SKIP!!!!:
A. Make sure all of your Magisk / EdXposed modules are updated for compatibility with R. For example:
* Magisk Module: Riru (Riru - Core) v21.3
* Magisk Module / EdXposed version: EdXposed v.0.5.0.6-android_r (4561) [this is a Canary build]
B. Recommend disabling any Magisk and/or Xposed modules that have not been tested with Android R.
C. Install latest Magisk Manager Canary build: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
D. Regular reboot the phone to make sure updates are applied before proceeding with the rest of the update process.
---------------------------
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "10.0.0 (QQ3A.200805.001, Aug 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-qq3a.200805.001-factory-dtbo.img: https://androidfilehost.com/?fid=8889791610682906527
coral-qq3a.200805.001-factory-boot.img: https://androidfilehost.com/?fid=8889791610682906525
September 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rp1a.200720.009-b447daff.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-qq3a.200805.001-factory-boot.img
3. fastboot flash dtbo coral-qq3a.200805.001-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rp1a.200720.009-b447daff.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rp1a.200720.009-magisk_patched-c20424.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
---------------------------
ADDITIONAL NOTES FROM @sidhaarthm, WHO TESTED FOR ME - THERE'S SOME GOOD INFO HERE TO HELP PREP YOU BEFORE UPDATING YOUR PHONE:
Okay, so I just successfully completed the steps and I'm booted into Android 11 without issues.
Here are my observations, notes and findings:
Pre-requisites:
- I installed the Canary Build of Magisk apk - it basically overwrote the existing installation of Magisk and worked straight away. I remained on the 'stable' update channel.
- I uninstalled all the Accent and Colour Mods from Tulsadiver as he is yet to update the mods for R11 (although he's confirmed its' possible and will publish it soon).
- I also deleted the AK3 Helper module from Magisk that gets flashed with Kirisakura Kernel since I was about to to flash the stock kernel anyway.
- I left the GPay SQlite Fix, Systemless Hosts, Busybox, V4A and AML Modules in Magisk enabled and as is.
Upgrade Notes:
- Followed your instructions to the T and the upgrade process was a breeze.
- I did extract the boot file from the factory ROM and patched it in Canary Magisk myself on my P4XL, but I chickened out at the last minute and flashed the boot file you had provided anyway. Reason being the flashed boot IMG I generated was 33,292 KB vs the one you had provided (and the ones I saw posted in other threads) were all 33,332 KB. So there was definitely some differences there and I just didn't want to risk it at that point.
- The phone got a bit hot during the upgrade process - around 40C+ but I suppose that's alright. Its' cooled down now and running okay.
- I did not flash any Kernel yet since I am waiting for the next official Kirisakura Kernel release for R11.
Findings:
- My P4XL booted first time, no bootloops etc - finalised the upgrade in a couple of minutes and everything thereafter seems smooth as butter.
- GPay works perfect without any tinkering (that's a big plus!)
- Device is rooted and all Root apps (AdAway, TiB etc), all work as normal. Camera, WiFi, Bluetooth, everything works, no issues whatsoever.
- Face Unlock works as normal and so do all the apps that use the biometric API to unlock (banking apps etc).
- SafetyNet fails on ctsProfile (evalType Hardware) but it was the same before upgrading to R11, so not surprised.
- Viper FX doesn't work post upgrading to R11 - that's expected and people have already reported the same 'failed at patching system' error on the main thread. Hopefully we get an upgrade at some point. Really gutted about this one as I love V4A!
Click to expand...
Click to collapse
Big thanks to @sidhaarthm for being an awesome and detailed tester!
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
* Looks like Tulsadiver uploaded a boot image for A11, although it hasn't been tested yet: https://forum.xda-developers.com/showpost.php?p=83462451&postcount=150
Coming from an earlier build than August 2020?
Download the September 2020 Full Factory Image .zip file and extract it. BEFORE RUNNING THE FLASH-ALL BATCH / SHELL FILE, EDIT THE FILE AND REMOVE THE "-w" FLAG FROM THE LAST FASTBOOT LINE. If you fail to remove -w, your phone will be wiped when it reaches this step. After flashing the full factory image, your phone will automatically reboot into O/S. From here, reboot back into bootloader, and flash the new Magisk patched boot image.
Since this is a major jump to a new version of Android, I don't want to recommend this yet until someone tests it. If anybody tries this way successfully, please let me know so we can update this part. Thanks!
I just updated from Android 10 August (I use your method since, what, April now?) and everything worked without a problem. For security purposes I deactivated Edxposed beforehand, though. The first booting takes a while after the updating, maybe 3-4 minutes, don't be afraid to wait. I was. Lol.
Edit: Jea, Android4Viper is broken. Needs fix asap
Also a big thanks from me, all went well! A little reminder for people running lawnchair & quickswitch: disable both and set stock recent provider to pixel launcher! Both are not compatible yet... Almost had to factory reset because of this ?
An other big thanks from me, I used your guide again and everything is working.
I used Magisk from the Canary channel and installed MagiskHide Props Config.
Safetynet : Basicintegrity V, ctsProfile V and evalType BASIC., this is good.
When the Kirisakura Kernel is available I will install this kernel for Android 11.
when you install latest Magisk Manager Canary build, is this supposed to overwrite the current stable build or ad an additional separate magisk app?
has anyone installed riru and edxposed (if so what version you using) after root from a fresh update (Full wipe update, root, then install modules) any issues?
***EDIT (for dummies like me)*** can confirm works via fresh install too
-Just download / install riru core 21.3 via magisk.
-Download latest edXposed manager v4.5.7.
-Download v0.5.0.6 4561 from canary tab in edXposed manager.
-Flash that zip in magisk.
-Just make sure you don't flash and exposed directly from the download module list in magisk those are not the canary builds. You have to flash the zip from internal storage you just downloaded.
So I went with the fresh install and now the patches boot img returns a "partition not found" error.
I've tried powershell, cmd and same error. Does anyone have another command that could get me up and running? I re-root several times a year and never have this kind of problem.
Just to check that I'm using the correct command. - Fastboot flash boot patched boot img-
Would the patches image name make a difference?
bigmatt503 said:
So I went with the fresh install and now the patches boot img returns a "partition not found" error.
I've tried powershell, cmd and same error. Does anyone have another command that could get me up and running? I re-root several times a year and never have this kind of problem.
Just to check that I'm using the correct command. - Fastboot flash boot patched boot img-
Would the patches image name make a difference?
Click to expand...
Click to collapse
fastboot flash boot magisk_patched.img --slot all
Homeboy76 said:
fastboot flash boot magisk_patched.img --slot all
Click to expand...
Click to collapse
Thanks for the help. I got working by flashing "_a" after img
bigmatt503 said:
Thanks for the help. I got working by flashing "_a" after img
Click to expand...
Click to collapse
No problem, glad you found a solution to the problem. :good:
Ok, the first time I did this, it didn't change anything(after I finished I was still on Android 10, with the August update), so I may have did something wrong, I'm not sure. Anyway, I did it a second time, and voila, it works. Your guides are always the best bro!
Any chance someone could say if Google Pay is working (and banking apps) with this method? Want to jump to 11 but everything works great on Aug 10 right now.
Thanks
Not able to boot after flashing the patched img says no valid slot to boot
bluedog220 said:
Any chance someone could say if Google Pay is working (and banking apps) with this method? Want to jump to 11 but everything works great on Aug 10 right now.
Thanks
Click to expand...
Click to collapse
Google Pay works - I utilised the GPay SQlite fix method (look it up, plenty of threads on it) but I actually had that before I upgraded to R11. Once I successfully upgraded using the steps provided in this thread, I didn't have to do a thing and GPay still works
As for banking apps, depends where you are. I'm in the UK and with Magisk Hide and some trickery, I've manged to get Monzo, Starling, Amex, HSBC and Tesco Banking apps to work on my Pixel 4 XL. The only ones I seem to struggle with (that have strong root detection) are Barclaycard and Lloyds Banking Group apps such as Halifax, MBNA etc.
Hope that helps :good:
bluedog220 said:
Any chance someone could say if Google Pay is working (and banking apps) with this method? Want to jump to 11 but everything works great on Aug 10 right now.
Thanks
Click to expand...
Click to collapse
I'm in the USA and G-pay works without doing anything. All of my banking /credit card apps work too
Has anyone had SafetyNet randomly stop passing for both basicIntegrity and ctsProfile together? When I first upgraded to 11 and set everything up, I was able to pass even with EdXposed installed, then it stopped passing with EdXposed a few days later, but would pass both with it disabled. Now it won't pass at all even with EdXposed disabled.
Anyone have any ideas before I resort to wiping and starting over?
has anybody with android 11 and magisk able to use smali patcher or app systemizer? i cannot get either to work yet
This guide worked perfectly for me, cheers.
Just need to wait for YouTube vanced