Here are recent A13 GSIs that booted and worked on my P20 lite Hi6250
Requirements:
You can flash SHRP recovery that have all the requirements to make Android 13 boot normally (including permissive kernel, decrypt data, selinux fix, AIO fix and Mgisk) from here
------- or
- latest kernel from here
- Stock kernel 4.9148 from here
- SELinux-fix from here
- AIO patch for android 13 here (that include offline charging fix, SELinuxfix and other fixes)
- EMUI 9
-Arm64 AB GSI image (vndklite version is recommended)
- How to install: here
NameMaintainerLinkKernel and fixesUpdatedAOSP@phhusson TrebleDroid™ BuildersDownloadOption 1: Stock kernel
Option 2: Latest kernel from here13/11/2022crDroidNazimDownload
Option 1: Latest kernel from here
Option 2: Stock kernel27/12/2022Pixel Experience +
Pixel Experience PlusponcesDownloadOption 1: Stock kernel
Option 2: Latest kernel from here4/1/2023Evolution X@poncesDownloadOption 1: Stock kernel
Option 2: Latest kernel from here5/1/2023Superior OSChonDoeDownloadOption 1: Stock kernel
Option 2: Latest kernel from here17/11/2022LeaOS-PHHAltairFRDownloadPhenix Linux 4.9.31923/12/2022LineageOS TD-based@AndyYanDownloadOption 1: latest permissive kernel from here
Option 2: Latest kernel from here + SELinux fix or AIO11/11/2022Cherish OSChonDoeDownloadOption 1: Latest permissive kernel from here
Option 2: Latest kernel from here + SELinux fix or AIO
Option 3: Stock kernel+ SELinux fix or AIO13/11/2022ArrowNazimDownloadOption 1: Stock kernel
Option 2: Latest kernel from here8/1/2023SparkNazimDownloadOption 1: Stock kernel
Option 2: Latest kernel from here10/1/2023RiceDroid@LynixFoxDownloadOption 1: Stock kernel
Option 2: Latest kernel from here22/12/2022Project Elixir@LynixFoxDownloadOption 1: Stock kernel
Option 2: Latest kernel from here12/1/2023
Some Fixes for A13
1- solve network problem
adb shell settings put global restricted_networking_mode 0
2- remove phh su from A13(solve magisk problems)
adb shell
su 0
/system/bin/phh-securize.sh
3- Enable offline charging
Flash this Zip file using TWRP/SHRP
Download From here
Selinux-fix-Yahia-V5.0.zip: Selinux fix for Pixel Experience A13 including missing selinux policies for offline charging (it may work with other GSIs, if not you can back to sock vendor policies by flash selinux-Stock-Yahia-V1.0.zip or from your vendor backup)
- Backup Vendor partition
- It also disable encryption
- Flash "Selinux-fix-Yahia-V5.0.zip" using TWRP
Selinux-fix-Yahia-V2.0.zip works with Pixel Experience A13
Kernel 4.9.319 for A13. I have rebuild it to fix keymaster2 error
Contributors
@TureX
Abdelhay.ali said:
Kernel 4.9.319 for A13. I have rebuild it to fix keymaster2 error
Contributors
@TureX
Click to expand...
Click to collapse
Hi!
What you have done to fix it? Is the error just for android 13 right? I might do a branch just for android 13
Cheers
TureX said:
Hi!
What you have done to fix it? Is the error just for android 13 right? I might do a branch just for android 13
Cheers
Click to expand...
Click to collapse
revert these two commits 1 2 . yes for A13 only
I don't want to create a seperate thread for this so here goes.
I tried to merge all patches related to Android 13 in a single package. This includes @AltairFR 's NFC, DRM and offline charging fixes, @Abdelhay.ali 's selinux rules and to top it off some tweaks from here and there from me. I made sure it can be flashed from official twrp, can't promise same for modified twrps.
I also made an opt version which doesn't include selinux rules since required ones are already merged to trebledroid. I recommend flashing that one, if you can't boot afterwards flash @Abdelhay.ali 's selinux patch above.
What it does:
- Edits vendor build.prop for safetynet
- Edits system build.prop for performance and spoofing phone model
- Edits vendor fstab to remove encryption
- Edits vendor selinux rules to boot enforcing
- Adds DRM service and required fixes to both system and vendor
- Adds NFC config files to system and system/product
- Adds iceow's offline charging binary & images and edits init.rc accordingly
- Removes unneeded com.android.vndk.vxx folders from system_ext/apex to save some space
- Added ability to resize system before extracting stuff
(twrp might say zip is flashed even tho it didn't because of resize functionality, that happened to me only when I dirty flashed it so I recommend flashing this before booting your system)
I'm a dumb dumb who can't figure out how to sign a zip so here's CRC64 to check for integrity manually :
1.3.1 : AC55639A998DA2B4
1.3.1-opt : 436BCBE5DECF34E0
Also I don't want to create another zip just to go back to stock, all you need to do is get stock vendor image from here and flash it over vendor via twrp. adb push VENDOR.img /sdcard will send it to internal storage, from there you can install image.
Good job frax3r !!!
Update
There are two versions of stock kernel 4.9.148 :
1- Sock kernel 4.9.148 for emui 9.1.0.401 from here extract by Frax3r
2- Sock kernel 4.9.148 for Emui < 9.1.0.401 attached
Thanks @AltairFR for this information
--------------
Stock Kernel 4.9.148 for Emui < 9.1.0.401 backup from TWRP
Because I didn't find any worked .img for 4.9.148 stock kernel. I have attached my Stock Kernel 4.9.148 backup from TWRP. You can use it via Restore option in TWRP after decompress it.
Abdelhay.ali said:
I didn't find any worked .img for 4.9.148 stock kernel
Click to expand...
Click to collapse
Use Huawei Update Extractor.
-Alf- said:
Use Huawei Update Extractor.
Click to expand...
Click to collapse
Thank you for your reply. I have already used it, but the output kernel.img not working on my device. Also, I have tried this from @Frax3r, not working too. (It is boot to fastboot with error message)
You can see the size of the extracted kernel is 24Mb and the normal kernel size around 12Mb
Abdelhay.ali said:
extracted kernel is 24Mb and the normal kernel size around 12Mb
Click to expand...
Click to collapse
Are you sure?
-Alf- said:
Are you sure?
Click to expand...
Click to collapse
Yes. Ask huawei enginners why they put 12 mb of empty space.
{
"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"
}
Abdelhay.ali said:
You can see the size of the extracted kernel is 24Mb and the normal kernel size around 12Mb
Click to expand...
Click to collapse
Maybe I don't understand it (I'm just a hobbyist), but when the extracted kernel.img is 24Mb and the your TWRP backup kernel.img is also 24Mb, where is the difference?
-Alf- said:
Maybe I don't understand it (I'm just a hobbyist), but when the extracted kernel.img is 24Mb and the your TWRP backup kernel.img is also 24Mb, where is the difference?
Click to expand...
Click to collapse
TWRP take a backup of the whole kernel partition including space.( Like backup system and backup system image).
This is not our problem . There is an error in extracting kernel from UPDATE.APP using Huawei Update Extractor at least with me. I have mentioned size of the extracted kernel to indicated that.
Abdelhay.ali said:
TWRP take a backup of the whole kernel partition including space.( Like backup system and backup system image).
This is not our problem . There is an error in extracting kernel from UPDATE.APP using Huawei Update Extractor at least with me. I have mentioned size of the extracted kernel to indicated that.
Click to expand...
Click to collapse
Just ignore checksum in option of huawei extractor or use linux extract script
AltairFR said:
Just ignore checksum in option of huawei extractor or use linux extract script
Click to expand...
Click to collapse
I have used both methods. but after flash the kernel, it does not boot normally . I attached the error
anyway, I can return to stock kernel using my backup
Abdelhay.ali said:
I have used both methods. but after flash the kernel, it does not boot normally . I attached the error
anyway, I can return to stock kernel using my backup
Click to expand...
Click to collapse
Check your usb cable, I had the same issue. Turns out cable was faulty. Even my proper cable corrupted few images while flashing, switched usb ports and it flashed uncorrupted. Try different usb ports, if it's same switch cable.
Frax3r said:
Check your usb cable, I had the same issue. Turns out cable was faulty. Even my proper cable corrupted few images while flashing, switched usb ports and it flashed uncorrupted. Try different usb ports, if it's same switch cable.
Click to expand...
Click to collapse
You can also prefer usb-a port
Hi,
I'm trying to install pixel experience on my phone with this guide and I'm using the first recommended twrp. When I want to flash the AIO fix zip file, both adb sideload and install from twrp show the error
'Failed to mount /system_root (invalid arguement)'I tried many methods from the google search and nothing works. I tried mount /system rw manually, both twrp mount and terminal not working and resize file system from twrp wipe also failed.
How can I solve this? Thanks for your help.
art0001 said:
Hi,
I'm trying to install pixel experience on my phone with this guide and I'm using the first recommended twrp. When I want to flash the AIO fix zip file, both adb sideload and install from twrp show the error
'Failed to mount /system_root (invalid arguement)'I tried many methods from the google search and nothing works. I tried mount /system rw manually, both twrp mount and terminal not working and resize file system from twrp wipe also failed.
How can I solve this? Thanks for your help.
Click to expand...
Click to collapse
Use vndk lite version of PE
Related
WARNING: When using custom kernels on the S7, never turn off developer options or OEM unlock. If you do, you will lose all your data and have to flash a full stock firmware restore to use your device again!
OKAY SO
This is Kali NetHunter 3.15.2 for the Galaxy S7.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
Most ROMs should be supported, as our installer uses a dynamic patching method on your current boot image!
The NetHunter installer zip will add a few files to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local/nhsystem, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
NetHunter also includes its own Busybox that gives you full large file support and some extra applets.
It will not overwrite your current one, and will happily install alongside it as busybox_nh.
DOWNLOAD
Current version: 3.15.2 (stable, 2016-11-04)
Please be careful to download the right version based on this table:
SM-G930F, SM-G930FD, SM-G930W8, SM-G930X: kernel-nethunter-herolte-*
SM-G930K, SM-G930L, SM-G930S: kernel-nethunter-heroltekor-*
S7 edge: You're in the wrong forum!
All others be sad.
For the apps, chroot, and everything other than just the kernel, you will also need to download:
nethunter-generic-arm64-*
See installation instructions before proceeding!
Downloads are available at: http://build.nethunter.com/nightly/
BEFORE INSTALLING
IMPORTANT: Kali NetHunter requires write access to your data partition!
This means that if your data partition is encrypted, you will need to use the [Format Data] button in TWRP to remove encryption.
This will delete all your data, including internal storage.
You should back everything up first before installing Kali NetHunter.
Samsung Smart Switch Mobile can be useful for this, and allows you to back up your apps to a location on an external SDcard.
Unfortunately it doesn't back up most app data.
The Kali chroot and apps are installed on your data partition (in /data/local/nhsystem for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The generic NetHunter installer will automatically install SuperSU. We try to keep it up to date, but it isn't always.
If you already have SuperSU or another root method installed, please simply delete the supersu.zip from the root of the zip file before installing it.
It's recommended that you restore or flash your ROM's original kernel before installing NetHunter.
It's become apparent that there may be issues with the stock ROM and this kernel, and that it might run best on a Note 7 port.
FULL INSTALLATION STEPS
Install Team Win Recovery Project to your recovery partition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recommended: If you have a custom kernel or SuperSU installed, restore your stock kernel. (called Boot in TWRP)
This isn't entirely necessary, but you may need to flash the NetHunter kernel again if SuperSU replaces it.
If your data partition doesn't mount in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Once your data partition is formatted, go to [Reboot] -> [Recovery].
Download the kernel-nethunter zip specific to your device.
Without exiting TWRP, transfer the NetHunter kernel installer zip to your device over MTP* and flash it using [Install] in TWRP.
If you wiped your data partition in step 2:
Go to [Reboot] -> [System].
Set up your phone by following the Android setup wizard.
Once it's set up, reboot back into recovery.
For new installations: Download the nethunter-generic-arm64-kalifs zip.
For upgrades: Download the update-nethunter-generic-arm64 zip.
Without exiting TWRP, transfer the NetHunter generic arm64 installer zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
Open the NetHunter app to initialize the environment
You're done!
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TO A NEWER BUILD OR UPDATING YOUR ROM
Follow the installation steps above. NetHunter can be installed over itself as many times as you'd like.
If you don't want to lose your chroot, flash the smaller update-nethunter-generic-arm64 zip instead.
THE KERNEL
The NetHunter kernel for the Galaxy S7 is based on Samsung's OSRC N930SKSU2BPID Note 7 kernel sources.
It has the following changes:
Carefully updated to Linux 3.18.44 (with dirtycow vulnerability patched)
SELinux permissive
F2FS updated to Jaeguek Kim's latest kernel.org f2fs-stable sources
F2FS formatted data partition support
Enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
FIOPS IO scheduler as default IO scheduler, SIO available
USB HID Gadget keyboard & mouse support
mac80211 packet injection support
DriveDroid compatibility
Additional drivers built in for the full Kali NetHunter experience
Data partition encryption disabled (not supported by custom kernels at the moment)
Kernel module support, insert your own modules!
CIFS, NFS available through included kernel modules
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
If your issue is with a specific app, it might be better to contact the developer of that app.
For Kali NetHunter bugs/issues, you can open a ticket at: https://github.com/offensive-security/kali-nethunter/issues
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard - The keyboard is unusable when using Google Keyboard as your input method. Switch to Hacker's Keyboard.
Reboot after 60 seconds - Sometimes when you boot your device it could reboot after 60 seconds because of a Samsung secure service not responding. Unresolved, but rare, and only happens within 60 seconds of a boot.
DEVELOPMENT
You can see the main branch of NetHunter's development on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Galaxy S7 NetHunter kernel source: https://github.com/jcadduono/android_kernel_samsung_universal8890/tree/nethunter-6.0
SCREENSHOTS
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
XDA:DevDB Information
Kali NetHunter for the Galaxy S7, Kernel for the Samsung Galaxy S7
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/offensive-security/kali-nethunter
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.15.2
Stable Release Date: 2016-11-04
Created 2016-10-06
Last Updated 2016-11-04
I cannot test this today, but i ****in love you !
saphirrot said:
I cannot test this today, but i ****in love you !
Click to expand...
Click to collapse
Yeah I just hope it's all working fine this time Last time I opened a thread for NetHunter on S7 it was a little embarrassing as I didn't own any recent Galaxy phones I had no idea they'd be such a challenge to get custom development going on.
I still haven't exactly tested this, but I do have the Note 7 now so I'm really hoping that everything done to make it work on the Note 7 makes it work on the S7 and S7 edge too... *crosses fingers*
We've got a few issues to fix before an actual release but they're all related to the apps.
1. The NetHunter Terminal app is quite buggy, so you might want to use JuiceSSH local terminal for now. (type su -c bootkali_login to enter Kali environment)
2. The NetHunter app's scripts are all hardcoded for armhf right now. I've actually completed arm64 support in the installer and we can build working arm64 rootfs and install it, just the NetHunter app can't see it yet so we're using armhf on arm64 instead for now.
Anyways, hope to hear some good news from ya! These remaining issues shouldn't take long for us to overcome...
For s7 edge do I have download the arm packages or arm64 packages?
Handeman707 said:
For s7 edge do I have download the arm packages or arm64 packages?
Click to expand...
Click to collapse
you're in the wrong forum, go to S7 edge forum
http://forum.xda-developers.com/s7-edge/development/kernel-kali-nethunter-galaxy-s7-edge-t3475413
this probably isn't something you want to play around with if you don't know if your phone is arm or arm64 :/
Has anyone else been able to get DriveDroid working bootabley (definitely a real word) on this build / Galaxy S7?
I can get the device to show in Windows, but none of the configuration options seem to make it show up as a boot option.
I've tried with both the DriveDroid apk in the nethunter installer, and the latest one from the DriveDroid website.
(P.S. It's not a configuration issue on my laptop as it works with DriveDroid on a Nexus 5. )
XanSama said:
Has anyone else been able to get DriveDroid working bootabley (definitely a real word) on this build / Galaxy S7?
I can get the device to show in Windows, but none of the configuration options seem to make it show up as a boot option.
I've tried with both the DriveDroid apk in the nethunter installer, and the latest one from the DriveDroid website.
(P.S. It's not a configuration issue on my laptop as it works with DriveDroid on a Nexus 5. )
Click to expand...
Click to collapse
I've never been able to boot from DriveDroid CDROM mode but always just mounted ISOs as USB Storage and booted off that, essentially the same as dd'ing an ISO to a flash drive.
Not sure what the Nexus 5 is doing differently... It is kernel related though, as actually mounting this stuff is very trivial and can be done through terminal.
jcadduono said:
I've never been able to boot from DriveDroid CDROM mode but always just mounted ISOs as USB Storage and booted off that, essentially the same as dd'ing an ISO to a flash drive.
Not sure what the Nexus 5 is doing differently... It is kernel related though, as actually mounting this stuff is very trivial and can be done through terminal.
Click to expand...
Click to collapse
Doesn't seem to be working for me in USB RW, USB RO, or CDROM mode on this build; are you saying that the one of the USB modes -is- functioning for you currently? or none at all (same as me?)
XanSama said:
Doesn't seem to be working for me in USB RW, USB RO, or CDROM mode on this build; are you saying that the one of the USB modes -is- functioning for you currently? or none at all (same as me?)
Click to expand...
Click to collapse
Used USB RO to install Windows 10 from boot the other day, but that was in UEFI mode
dude pls tell me what is the best rom to have nethunter because i tried a lot of roms it keeps ending in bootloop. also pls tell me whether it works in stock rom...
ahamed.rafi135 said:
dude pls tell me what is the best rom to have nethunter because i tried a lot of roms it keeps ending in bootloop. also pls tell me whether it works in stock rom...
Click to expand...
Click to collapse
Only tested on latest stock FXXU1BPI firmware
jcadduono said:
Only tested on latest stock FXXU1BPI firmware
Click to expand...
Click to collapse
but when i try flashing on stock it says boot image failed
boot image file xxxxxbits larger
ahamed.rafi135 said:
but when i try flashing on stock it says boot image failed
boot image file xxxxxbits larger
Click to expand...
Click to collapse
recovery log...
doesnt make sense, by my calculations the resulting image should be close to 40953856 bytes and partition should fit it at *41943040 bytes :/
jcadduono said:
recovery log...
doesnt make sense, by my calculations the resulting image should be close to 40953856 bytes and partition should fit it at *41943040 bytes :/
Click to expand...
Click to collapse
yeah dude just gimme a moment flashing stock rom, btw i just did all the setup in bobcat rom it is soooooo lagggy
and i would like to have this on stock rom. And one more thing thanks for your continuous support.
AND MY FIRMWARE IS G935FXXU1APB6 is it ok?
ahamed.rafi135 said:
yeah dude just gimme a moment flashing stock rom, btw i just did all the setup in bobcat rom it is soooooo lagggy
and i would like to have this on stock rom. And one more thing thanks for your continuous support.
AND MY FIRMWARE IS G935FXXU1APB6 is it ok?
Click to expand...
Click to collapse
i have no idea...only tested on FXXU1BP firmware... maybe consider updating?
i will see about maybe removing ffu and signature checker binaries to reduce size, i dont think they are even able to run except by OTAs/stock anyway which are broken by custom kernels
i have attached the log
jcadduono said:
i have no idea...only tested on FXXU1BP firmware... maybe consider updating?
i will see about maybe removing ffu and signature checker binaries to reduce size, i dont think they are even able to run except by OTAs/stock anyway which are broken by custom kernels
Click to expand...
Click to collapse
also which rom do you recommend?
ahamed.rafi135 said:
also which rom do you recommend?
Click to expand...
Click to collapse
the one that matches your boot image...
i will always recommend stock over anything else though
ok try a build from here instead:
http://build.nethunter.com/test-builds/
update: tested myself and it worked fine, posted new nightly build with changes
it will remove the firmware upgrade service from boot image, which is useless anyway as we can't take OTAs with custom kernels
Hi, I have flashed both of the lastest kernels (kernel-nethunter-herolte-marshmallow-3.15.2-20161024-2241) and (kernel-nethunter-herolte-marshmallow-3.15.2-20161023-0148) but they are still laggy and are having poor CPU performance in geekbench tests. Any fix?
Does it requires an external WiFi adapter to test my internet security or does the WiFi adapter of the S7 can do the job ?
Thank you
REVIVING THE LOVE FOR STOCK ROM. OPTIMISED STOCK ROM on the base of NPJS25.93-14-4 for MOTO G4/PLUS.
{
"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"
}
NOTE: This thread is best viewed on a desktop browser like Microsoft Edge/ Google Chrome/etc.
FEATURES:
1. FULLY DE-ODEXED by smali-2.2.0 and baksmali-2.2.0 .
2. FULLY DE-BLOATED
3. ZIP-ALIGNED ALL SYSTEM AND FRAMEWORK APPS
4. March 1 Security patch & Android Nougat 7.0
ALLEGED PERFORMANCE IMPROVEMENTS THAN STOCK NPJ25.93-14:
1. Faster in general UI performance.
2. Apps will use less storage and memory because the ROM is deodexed, debloated and zipaligned.
3. More battery efficiency as claimed by the update npjs25.93-14-4 + point 2.
4. A bit less of heating than stock owing to debloat.
DOWNLOADS:
1. TWRP 3.1 by @oadam11: Post 2 of Ground Zero ROMs thread for athene
2. ROM: Android File Host Link
3. SuperSU v2.79 SR3: [BETA]SuperSU v2.79 SR3 thread
4. Magisk v12 : Magisk Release Thread
5. Magisk Terminal Debloater v4 module/script: Download manually here from this Thread or from the Download section under Magisk Manager App.
6. ElementalX Kernel v1.04 for Stock N ROM: ElementalX Kernel thread for athene
7. Vegito Kernel v6.5 for Stock N ROM: Vegito Kernel Thread
INSTALLATION PROCEDURE:
1. Make appropriate backups in TWRP.
2. Wipe System, Data, Cache and ART Cache.
3. Install the ROM. (No need for GApps)
4. Reboot.
5. Update Google Play Store via tapping on version in Play store settings and after that update the Google Play services.
6. Update all the apps and reboot once.
NON-ROOTED. Why?
Simply because some people want MagiskSU and some want SuperSU. Moreover rooting would require changing the kernel to ElementalX or Vegito as there was no root exploit in stock N kernel.
BUGS:
1. Settings app MAY crash if you open the Apps section. If you want to configure the default apps tap the gear icon immediately.
Getting it to work is pure LUCK. Sorry I have no fix for it. Happens only to me idk why. No one else reported this.
ROOTING PROCEDURE:
WARNING: IF YOU DIRECTLY FLASH SOME SU MANAGER YOUR DEVICE WON'T BOOT.
1. Take appropriate backups in twrp (Boot partition recommended).
2. Flash ElementalX kernel v1.04 for Stock ROM or Vegito Kernel v6.5.
3. Reboot (Optional).
4. Flash your desired su manager (Magisk v12 or SuperSU v2.79 SR3).
5. Reboot (Incase of SuperSU boot process will loop once).
6. Update the Magisk Manager/ SuperSU from PlayStore(If needed).
IMPORTANT NOTES:
DON'T TRY INSTALLING ANY FUTURE OFFICIAL OTA FROM MOTOROLA ON THIS ROM. FLASH STOCK NOUGAT FROM HERE IF NEED BE. I have already removed the '3c_ota' app using the magisk terminal debloater script, although, if you get any update via the OTA app, don't try installing it.
SUBSTRATUM/OMS Support won't be possible on this ROM as it is based on prebuilt system images instead of some raw source code. Legacy mode may work with root. Do not report bugs for the same. I'm not responsible for the consequences of themeing.
This ROM will NOT upgrade your BOOTLOADER and PARTITION TABLE. They'll remain the same as NPJ25.93-14 (Dec 1 Patch) unless you had flashed the March 1 patch in stock recovery.
Hello moto sound and boot animation works fine
Credits/Thanks:
1. @kosmasgr for the TWRP backup.
2. @Swapney Raul for testing the ROM.
3. @oadam11 for TWRP 3.1.0
4. @Chainfire for SuperSU.
5. @topjohnwu for Magisk.
6. @veez21 for Magisk Terminal Debloater.
7. @flar2 for ElementalX kernel.
8. @Dreamstar for Vegito kernel
9. XDA for the amazing dev portal.
10. Motorola for the device. (Ik many of you hate Lenovo)
11. Google ofc for Android and the open source community.
12. Android File Host for hosting the downloads.
If I missed anyone..do PM for the same. :good:
Do check out the bootlogos/splash screens I have made for athene.
ADDITIONAL SUPPORT:
1. Custom ROM help thread.
2. For further assistance, you can message at Telegram: Personal or Community.
HIT THANKS IF YOU LIKED IT. :good:
XDA:DevDB Information
RevivorOS, ROM for the Moto G4 Plus
Contributors
tywinlannister7
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock N 93-14-4
Based On: Stock ROM
Version Information
Status: Stable
Created 2017-05-18
Last Updated 2019-11-22
Reserved :good:
Thanks ? and files manager works fine if u update the app.
Hi! Can I flash without wiping data if I'm already on stock NPJS25.93-14? Thanks!
A BIG NO
pblasi said:
Hi! Can I flash without wiping data if I'm already on stock NPJS25.93-14? Thanks!
Click to expand...
Click to collapse
No I would not recommend this. Since the apps are deodexed and zipaligned with many of them being removed. So this will create a problem on a dirty flash. Instead use Titanium Backup for apps and their respective data.
fr3d0x said:
Thanks and files manager works fine if u update the app.
Click to expand...
Click to collapse
Thanks for the heads-up :good:
Αwesome rom @tywinlannister7. Also i edited build prop , adding line ro.sf.lcd_density=410 before flashing and works excellent.
I have fc with file manager but there is no file manager ( strange ) and fc with appbox but also there is no this app
Wipe data and cache will solve the problem
tywinlannister7 said:
1. Moto File Manager and a few apps may give you Force Stops on first boot. If force stopping the app and then clearing its data and wiping cache (both)
FIX: Force Stop the apps>Clear Data>Update from Google Play>Wipe caches (both ) in twrp> Reboot
Click to expand...
Click to collapse
I tried this, but still getting "Retail Config Service" FC at boot... Any ideas to get rid of it?
kosmasgr said:
Αwesome rom @tywinlannister7. Also i edited build prop , adding line ro.sf.lcd_density=410 before flashing and works excellent.
I have fc with file manager but there is no file manager ( strange ) and fc with appbox but also there is no this app
Wipe data and cache will solve the problem
Click to expand...
Click to collapse
Deodexing and debloating might be a reason. These apps work in the background as system apps and create a bit of the force stop thing.
pblasi said:
I tried this, but still getting "Retail Config Service" FC at boot... Any ideas to get rid of it?
Click to expand...
Click to collapse
What model do you have? I have tested this on the indian xt1643. Although the base of the ROM is from the European model (Shouldn't make any difference imo).
Can you try disabling or uninstalling it? (Proceed with backup). If no help, I'll need a logcat and try to find a fix. I'm still a beginner and this is my first ROM after Lineage. ?
pblasi said:
I tried this, but still getting "Retail Config Service" FC at boot... Any ideas to get rid of it?
Click to expand...
Click to collapse
I got this error while setting up the device but after the setup it was gone haven't seen that error since then,do you get it often?
If i flash this from mm will my modem will change to nougat?
dedik46 said:
If i flash this from mm will my modem will change to nougat?
Click to expand...
Click to collapse
No
It would be nice if you could add substratum support
[email protected] said:
It would be nice if you could add substratum support
Click to expand...
Click to collapse
I think as this is a stock ROM we can't add Substratum commits in, though if I'm incorrect someone correct me!
Nice work by the way, tywinlannister7 good to see a TWRP flash of the latest security patch and OS!
Thanks for this stock rom just only two question....Is RetBR base or wich?? is necessary flash official nougat before???
diegomartinezlovey said:
is necessary flash official nougat before???
Click to expand...
Click to collapse
I think you should do so, ideally, so that your baseband and other firmware is at least on Nougat, before then wiping your device and then flashing this TWRP file as per the opening post.
diegomartinezlovey said:
Thanks for this stock rom just only two question....Is RetBR base or wich?? is necessary flash official nougat before???
Click to expand...
Click to collapse
You need to first flash the Dec 1 path update then this so that all things work.
echo92 said:
I think as this is a stock ROM we can't add Substratum commits in, though if I'm incorrect someone correct me!
Nice work by the way, tywinlannister7 good to see a TWRP flash of the latest security patch and OS!
Click to expand...
Click to collapse
As far as I know we can add using small editor but it's a hard job so no one does that.
diegomartinezlovey said:
Thanks for this stock rom just only two question....Is RetBR base or wich?? is necessary flash official nougat before???
Click to expand...
Click to collapse
I had used the system and boot dump from the reteu model owned by @kosmasgr . But the ROM should work fine as long as you have updated to Nougat NPJ25.93-14 or above.
{
"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"
}
I am sharing my kernel/boot.img, which is build from Sony Open Source/Qualcomm/ and android source (Very close to Stock KERNEL). Designed to keep balance security/ with high Performance and battery life.
Code:
###Disclaimer###
I am not responsible for any damage, broken or boot looping.
Please read the instructions and notes before flashing anything. Don't ask me if you don't read the instructions.Please respect and try to help each other. You may face sometimes that I cannot answer your questions/or answer your questions a bit later. I am busy with my work and don't have enough time to read and answer all your questions at the same time.
DONATE ME HERE
DONATE-HERE
##############################
Requirements-
##############################
- A working driver for your device.
USB drivers for Xperia devices
- Unlock bootloader
- A Working TWRP-with latest patch security
- YOUR firmware must match my kernel version. I used to update the kernel with latest firmware.
- Backup your stuff for future
- YOU NEED a refresh stock ROM (means you have to wipe EVERYTHING). Use flashtool to flash the latest firmware. (Remember to check Wipe USERDATA in flashtool). It seems not necessary if you have already flashed my kernel and have a working camera
- USE LATEST FLASHTOOL VERSION TO FLASH THE LATEST FIRMWARE
- (DOWNLOAD FROM HERE:- LATEST FLASHTOOL)
[/INDENT]##############################
Features 11/3/2019
##############################
- Based on latest kernel source VERSION = 4, PATCHLEVEL = 4, SUBLEVEL = 148 (version 47.2.A.8.24) MARCH, 2019
- Up to date with the September security update MARCH, 2019
- Hide verifiedbootstate from /proc/cmdline in order to fix the failed SafetyNet CTS check(It can still fail through other means)-GOOGLE PAY SHOULD WORK
- Remove verifiedbootstate flag from /proc/cmdline - Disable CRC check
- Support wireguard VPN protocol
- dm-verity removed
- Sepolicy is patched for latest Oreo (deodex ROMs)
- Scheduler optimize/support for heterogeneous multi-core. Battery efficiency
- Energy Aware Scheduling (EAS) feature is enabled/optimize energy consumption for advanced multicore SoCs
- Update and add Qualcomm PM driver/APM driver updated reduce battery usage during sleeping
- Enable latest energy aware scheduling patches
- Multi-core scheduler enable/optimized
- A lot subsystems converted to use power efficient work-queues
- CAF improvements and optimized
- Enable latest energy aware scheduling patches
- Enable work-queue power-efficient mode by default
- Several other patches to improve the speed and battery usage
- Tweaked the scheduler to reduce/save power by scaling down the frequency of the CPU's or idling them,
- Tweaked to predict the best time to save power on the CPU without affecting performance
- Tweaked/optimized the scheduler to balance the load across all CPUs without any regards to the power costs.
##############################
Instructions-
##############################
- Boot into custom-recovery and flash the zip OR UNZIP the zip, then move the boot.img into your adb/fastboot folder and follow
Code:
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img
- fastboot reboot
- DONE AND ENJOY
##############################
Downloads
##############################
Xperia XZ Premium(G8141 and G8142)-[LATEST]-[11/MARCH/2019]
##############################
Xperia XZ Premium(G8141 and G8142)--ALL-BOOT IMAGES-[KERNEL][DRM-PATCHING]-
##############################
##############################
Source/GitHub
##############################
Kernel Source
-47.1.A.12.xxx
https://github.com/Nexusma/msm-4.4
https://github.com/toffyjan/android_kernel_Sony_lilac_poplar
https://github.com/sonyxperiadev/device-sony-lilac
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN DON'T FORGET TO BUY ME COFFEE
DONATE ME HERE
DONATE-HERE
Special Thanks To:
If you can, donate and respect all the devs
@Chainfire for his great work to achieve root SuperSU
@Sultanxda for his great work in android kernel and SafetyNet CTS check
@Androxyde for Flashtool. merci beaucoup pour tout
@munjeni for his great knowledge and tools for extracting SIN images
@sToRm// for his effort on DRM work, THANKS
@SuperR. for SuperR's Kitchen , THANK YOU
@M-Rom Thanks for sharing drm-fix and patch
@serajr Thanks for DRM Fix Workaround and Sony RIC disabler
THANK YOU SONY FOR SUPPORTING DEVs AND ALLOWING US TO UNLOCK THE BOOTLOADER
Thanks to XDA And everyone else who share their knowledge and works among us in xda.
##############################
Detailed instructions-
##############################
Please install all drivers and ADB files needed.
1. Download to PC XperiFirm_5.3.6_(by_Igor_Eisberg).
2. Download to PC newflasher_v11.
3. Download to PC and unzip XZ-Premium-G8141/G8142-Kernel+DRM+patch+Magisk+47.1.A.xx.xxx.zip.
4. copy the 4 zip files to the any device microSDcard folder.
5. Download to PC twrp 3.2.1-0-maple and copy the img file to ADB folder.
6. Run XperiFirm and download latest firmware update, for G8141 or G8142
7. copy the newflasher.exe to the firmware downloaded folder.
8. power off the device, press and hold vol- and plug the USB cable some seconds, review the green led is on, bootloader mode.
9. run the newflasher copied on the firmware folder.
10. unplug the USB cable when the process finished.
11. press and hold vol+ and plug the USB cable some seconds, blue led is on, flash mode.
12. open a window "cmd" and go to ADB folder.
13. run the command "fastboot devices" to check the device is showed.
14. run the command "fastboot flash recovery twrp-3.2.1-0-maple.img".
15. unplug the USB cable and reboot to twrp recovery (press and hold vol- + power button).
16. On twrp menu, go to "Advanced" and "File Manager" and copy from microSDcard folder the 4 zip files to root "/" internal storage.
17. install the 1-kernel and reboot to recovery.
18. install the 2,3,4 zip on order and reboot.
19. enjoy
THANKS TO hbenavid FOR THESE STEPS
janjan said:
For future-
Click to expand...
Click to collapse
Hello, if you want to make it for dual sim I'm able to be the tester of the kernel if you want talk to me in private
SilverGamer_YT said:
Hello, if you want to make it for dual sim I'm able to be the tester of the kernel if you want talk to me in private
Click to expand...
Click to collapse
I will start build one for Dual SIM tonight.
janjan said:
I will start build one for Dual SIM tonight.
Click to expand...
Click to collapse
Perfect I'm here for any test
Your links need a decryption key buddy.
Beetle84 said:
Your links need a decryption key buddy.
Click to expand...
Click to collapse
yes, links encrypted need decryption key to open
SilverGamer_YT said:
Perfect I'm here for any test
Click to expand...
Click to collapse
Done. Enjoy
Beetle84 said:
Your links need a decryption key buddy.
Click to expand...
Click to collapse
karrouma said:
yes, links encrypted need decryption key to open
Click to expand...
Click to collapse
Links are fixed now. Enjoy
janjan said:
Links are fixed now. Enjoy
Click to expand...
Click to collapse
dual sim got bootloop with magisk 16.3 and 16.4
didn't try oldest version. tomorrow i will try
karrouma said:
dual sim got bootloop with magisk 16.3 and 16.4
didn't try oldest version. tomorrow i will try
Click to expand...
Click to collapse
Be more clear please. Did you follow the instructions? Are you on stock ROM without any kind of modifications. Otherwise it doesn't work.
janjan said:
Done. Enjoy
Click to expand...
Click to collapse
there is a problem when i tried to flash 2-patching
/vendor cannot be mounted
SilverGamer_YT said:
there is a problem when i tried to flash 2-patching
/vendor cannot be mounted
Click to expand...
Click to collapse
Please follow the 2nd method to flash 2-patch.zip
Very important.You should be on stock ROM.
Let me know if it doesn't work for you.
Hi,
Thanks for your work.
1. I have flashed the firmware: G8141_Customized CE1_1308-5321_47.1.A.12.145_R5B via "newflasher"
2. flashed the recovery twrp-3.2.1-0-maple.img
3. flashed the boot 1-boot.img
4. copied the 2-Patching.zip, 3-Magisk-latest.zip and 4-kernel-permissive.zip to "Download" folder in the internal storage.
5. reboot to twrp recovery.
6. Try to flash 2-Patching.zip and error: /vendor cannot be mounted.
stop.
SilverGamer_YT said:
there is a problem when i tried to flash 2-patching
/vendor cannot be mounted
Click to expand...
Click to collapse
when u first boot into TWRP , select mount then tick system then install the Zips
7aMooD-DmC said:
when u first boot into TWRP , select mount then tick system then install the Zips
Click to expand...
Click to collapse
That is how you fix the same issue as me?
7aMooD-DmC said:
when u first boot into TWRP , select mount then tick system then install the Zips
Click to expand...
Click to collapse
@janjan
Also tried to tick system then install 2-patching.zip
And same error like others.
If i flash the 1-boot.img and restart my phone i got bootloop on xperia.
I testet on stock xz premium dual. (not any other rom)
Also trying with turbo rom on my other xz premium and same problem also
karrouma said:
@janjan
Also tried to tick system then install 2-patching.zip
And same error like others.
If i flash the 1-boot.img and restart my phone i got bootloop on xperia.
I testet on stock xz premium dual. (not any other rom)
Also trying with turbo rom on my other xz premium and same problem also
Click to expand...
Click to collapse
I will take a look once again. Thanks for the report
janjan said:
Be more clear please. Did you follow the instructions? Are you on stock ROM without any kind of modifications. Otherwise it doesn't work.
Click to expand...
Click to collapse
Yes , after hard reset.
Phone boot without rooting.
After flashing 1 boot.img i got boot loop.
I follow system mount and same problem can't glash 2-patching also.
SilverGamer_YT said:
there is a problem when i tried to flash 2-patching
/vendor cannot be mounted
Click to expand...
Click to collapse
hbenavid said:
Hi,
Thanks for your work.
1. I have flashed the firmware: G8141_Customized CE1_1308-5321_47.1.A.12.145_R5B via "newflasher"
2. flashed the recovery twrp-3.2.1-0-maple.img
3. flashed the boot 1-boot.img
4. copied the 2-Patching.zip, 3-Magisk-latest.zip and 4-kernel-permissive.zip to "Download" folder in the internal storage.
5. reboot to twrp recovery.
6. Try to flash 2-Patching.zip and error: /vendor cannot be mounted.
stop.
Click to expand...
Click to collapse
karrouma said:
@janjan
Also tried to tick system then install 2-patching.zip
And same error like others.
If i flash the 1-boot.img and restart my phone i got bootloop on xperia.
I testet on stock xz premium dual. (not any other rom)
Also trying with turbo rom on my other xz premium and same problem also
Click to expand...
Click to collapse
Here is a new build. for G8142 Dual SIM. Follow the steps from 1st post.
https://mega.nz/#!wpRyzSQB!HsqTpJIEozjd85DLXHHWO3LjTo0d4dkYdRA8RimRn4M
Please let me know, if there is something. It should work for XZ premium too (works fine with XZ1 and XZ1 compact. NO issue there)
{
"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"
}
We’re really excited to announce the release of Paranoid Android Pie betas.
On first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. For those who are unfamiliar, Hampus is a multi-disciplinary artist whose design stands itself and we’re glad to have him onboard. We also added further UI touches that we believe enhances the overall user experience.
The beta builds include adjustments and improvements on top of the stock Android CAF base. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features.
Device-specific issues
- DT2W
- Camera crashes if it detects a face
Note: Custom kernels are NOT supported!
Download
Get the latest Xiaomi Mi A2 Lite build here!
Changelogs
Paranoid Android Pie beta released
Requirements
* Required * firmware version must be based on P-based builds.
Formatting/Wiping data (all user data is wiped, including internal storage (in case of a format)) is a must if you were using a different rom previously.
Instructions
Boot recovery from fastboot (TWRP recovery for Mi A2 Lite)
Format/Wipe /system and /data
Install AOSPA zip package
Install [optional] TWRP flashable
Don't forget to change slots after installing the rom in TWRP!
You have to reboot TWRP to the "new" slot to install GApps!
Important / Useful links
TWRP (bootable): https://androidfilehost.com/?fid=1395089523397933315
TWRP (flashable): https://androidfilehost.com/?fid=1395089523397933316
Forced encryption disabler: https://androidfilehost.com/?fid=1395089523397907941
Kernel source: https://github.com/33bca/android_kernel_xiaomi_msm8953
Help us improve PA by submitting good bug reports possibly with a log attached. Learn how to take logs here.
Our device maintainer for Xiaomi Mi A2 Lite is @33bca. Mention (@) me if you need some assistance and/or when reporting bugs.
Cheers and #StayParanoid!
# Reserved
# Reserved 2
a many thanks @33bca for your hard work you put into developing for our a2 lite
what bothers me most before trying your pa rom is the question if i can revert back to stock (inlcuding a/B Partitons and Stock Recovery, Encryption ) without any problem ? and if so what steps do i have to do to revert back to stock ?
normaly i would just make a backup from within twrp of my stock Phone and then do a restore if needed but as i unterstand it right thats not possible at the moment with the extisting versions of twrp for our a2 lite ? so maybe just get a2 lite into fastboot mode and flash an original fastboot image ?
Nice thanks ?
and some more questions @33bca on your instructions to install the rom:
Requirements
* Required * firmware version must be based on P-based builds.
so one must have 10.0.3.0 or 10.0.4.0 version of stock firmware on the a2 lite?
Formatting data (all user data is wiped, including internal storage) is a must if the storage was encrypted previously.
how do i find out if phone is encrypted or not ? if i goto settings and then security & location - advanced and if there under encryption and credentials at encrypt phone it says encrypted - then i have to format data (from whithin stock rom or from within twrp ?
Instructions:
Boot recovery from fastboot (TWRP recovery for Mi A2 Lite)
so here i use your bootable twrp img file (from your first link) with the command "fastboot boot recovery twrp-daisy-3.2.3-0-offain.img" ?
Format /system and /data
ist this the step you mention in the requirements or to i have to do this additionally to the step in the requirements ?
Install AOSPA zip package
just flash your pa rom within twrp ?
Install [optional] TWRP flashable
so here i flash the twrp (flashable from your second link) within twrp ?
and finally when should the "Forced encryption disabler" be flashed right after first time booting into twrp or after formating system and data ?
Yeah I need more detailed instructions to get this work ?
apelamod said:
Yeah I need more detailed instructions to get this work ?
Click to expand...
Click to collapse
Go to custom driod a2 lite twrp easyist way I've seen.besides that littwrl just flash ROM n switch slots o yea plus gapps.then u will have to reinstall twrp
ilovebytes said:
what bothers me most before trying your pa rom is the question if i can revert back to stock (inlcuding a/B Partitons and Stock Recovery, Encryption ) without any problem ? and if so what steps do i have to do to revert back to stock ?
normaly i would just make a backup from within twrp of my stock Phone and then do a restore if needed but as i unterstand it right thats not possible at the moment with the extisting versions of twrp for our a2 lite ? so maybe just get a2 lite into fastboot mode and flash an original fastboot image ?
Click to expand...
Click to collapse
rob420p said:
I would imagine u would need to use mi flash.or switch back to the other slot
Click to expand...
Click to collapse
hope you don't mind i put your quote from the other Thread into this one as i think its more usefull here now
thats what i need to know before i am gonnna give it a try - can i revert back to a completely Stock A2 lite from PA Rom with just putting the A2 lite into Fastboot Mode an flash a pie fastboot image (10.0.3.0 ore 10.0.4.0) with Miflash ?
- Camera crashes if it detects a face
Can face detecting be turned off?
@33bca after install opencamera app I have not bug Camera crashes if it detects a face
can someone who successfully install this rom make a noob-friendly guide how to install it? like how to change slot and is it mandatory to install forced encryption disabler?
adhitore said:
can someone who successfully install this rom make a noob-friendly guide how to install it? like how to change slot and is it mandatory to install forced encryption disabler?
Click to expand...
Click to collapse
Yes I like to get clean tutorial also ?
guide install
- use pie base firmware
boot to twrp :
-need to wipe /data , /system
- install zip pa
- install zip disable encryption
- optional install twrp installer
- change to slot b and boot to system after
- booted pa is fine ! install opencamera app for resolve error cam
- optional 2 : return to twrp after first boot for install : magisks , opengapps ...
adhitore said:
can someone who successfully install this rom make a noob-friendly guide how to install it? like how to change slot and is it mandatory to install forced encryption disabler?
Click to expand...
Click to collapse
ada12 said:
- use pie base firmware
-need to wipe /data , /system in twrp
- install zip pa
- install zip disable encryption
- optional install twrp installer
- change to slot b
- booted pa is fine ! install opencamera app for resolve error cam
- optional 2 : return to twrp after first boot for install : magisks , opengapps ...
Click to expand...
Click to collapse
install Gapps after change to slot b?. there is a menu in twrp to change slot or what?
Thanks dev! What about Bluetooth Slow Wifi Bug? Flickering? Are these annoying stock rom bugs fixed?
Thank you very much!
Reboot menu twrp for option slot change...
For gapps read my guide
adhitore said:
install Gapps after change to slot b?. there is a menu in twrp to change slot or what?
Click to expand...
Click to collapse
edit: USB preference cannot be selected , camera broken if you enable camera2 API
Should I unlock the bootloader first? It didn't mentioned in first post
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S22 S901B
Download & Guide:
1. Unlock your bootloader.
2. Downloads for S22: AFH: r0s twrp and kernel / Drive: r0s twrp and kernel
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.- Go back to Wipe > Format Data > type yes.- Reboot to recovery.7. Flash custom kernel and magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
@Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
Donators
Sources:
Kernel tree
Device tree
Changelog:
GitHub History
Note1: You need a custom permissive kernel to boot with R/W vendor.
Note2: If you got bootloop on Samsung logo, reboot to TWRP and wipe metadata from Advanced Wipe section.
Hi, thank you for twrp. Can this make system R/W ? I need to modify some files in system image. Thanks
NaiimAb10 said:
Hi, thank you for twrp. Can this make system R/W ? I need to modify some files in system image. Thanks
Click to expand...
Click to collapse
Not yet, still need a lot of work
Can S22 with 8GEN1 use this TWRP ？
sinaamos said:
Can S22 with 8GEN1 use this TWRP ？
Click to expand...
Click to collapse
Check OP there is supported list, also you know 8gen1 is snapdragon and the title says exynos and you still asking if it works?
Check the othe snapdragon thread.
Step 4 fails for me because of Knox Guard. Custom binaries blocked.
There is no way around this right?
Hi, noob question here...
Can I update firmware and retain root and TWRP without losing data? If yes - how to do it?
Worked perfectly with given guide!
1. TWRP recovery running
2. Could flash custom kernel from afaneh92
3. Also I downloaded Kernel tree and used build_menu to compile the same kernel with arch/arm64/configs/afaneh_r0s_defconfig
4. Could flash custom kernel self compiled as mentioned from (3.)
Next step was to adjust the defconfig from afaneh92 with some other features, but everytime I stuck in bootloop if I try. My approach was the following:
1. Load env variables from build_menu
2. make menuconfig load afaneh_r0s_defconfig
3. activate features from =n to =y (i.e. CONFIG_IP_VS=y)
4. copy newly created .config settings into afaneh_r0s_defconfig
5. start build_menu -> build kernel -> r0s
6. make flashable zip
7. boot into TWRP recovery and install custom kernel
8. Result: stuck in bootloop
my config still has CONFIG_SECURITY_ALWAYS_PERMISSIVE=y
Is this the right approach to add features to my kernel, or I am totally wrong with this? Here are some features I need for my kernel:
BLK_CGROUPDUMMYBLK_DEV_THROTTLINGEXT3_FS_POSIX_ACLBRIDGEIP_VSBRIDGE_NETFILTERIP_VS_NFCTVLAN_8021QIP_VS_PROTO_TCPBRIDGE_VLAN_FILTERINGIP_VS_PROTO_UDPBTRFS_FSIP_VS_RRBTRFS_FS_POSIX_ACLIPC_NSCFQ_GROUP_IOSCHEDNET_L3_MASTER_DEVHUGETLBFSIPVLANCGROUP_HUGETLBMACVLANCGROUP_NET_PRIONETFILTER_XT_MATCH_ADDRTYPECGROUP_PERFNETFILTER_XT_MATCH_IPVSDM_THIN_PROVISIONINGSECURITY_APPARMORVXLANUSER_NS
lowowly said:
Worked perfectly with given guide!
1. TWRP recovery running
2. Could flash custom kernel from afaneh92
3. Also I downloaded Kernel tree and used build_menu to compile the same kernel with arch/arm64/configs/afaneh_r0s_defconfig
4. Could flash custom kernel self compiled as mentioned from (3.)
Next step was to adjust the defconfig from afaneh92 with some other features, but everytime I stuck in bootloop if I try. My approach was the following:
1. Load env variables from build_menu
2. make menuconfig load afaneh_r0s_defconfig
3. activate features from =n to =y (i.e. CONFIG_IP_VS=y)
4. copy newly created .config settings into afaneh_r0s_defconfig
5. start build_menu -> build kernel -> r0s
6. make flashable zip
7. boot into TWRP recovery and install custom kernel
8. Result: stuck in bootloop
my config still has CONFIG_SECURITY_ALWAYS_PERMISSIVE=y
Is this the right approach to add features to my kernel, or I am totally wrong with this? Here are some features I need for my kernel:
BLK_CGROUPDUMMYBLK_DEV_THROTTLINGEXT3_FS_POSIX_ACLBRIDGEIP_VSBRIDGE_NETFILTERIP_VS_NFCTVLAN_8021QIP_VS_PROTO_TCPBRIDGE_VLAN_FILTERINGIP_VS_PROTO_UDPBTRFS_FSIP_VS_RRBTRFS_FS_POSIX_ACLIPC_NSCFQ_GROUP_IOSCHEDNET_L3_MASTER_DEVHUGETLBFSIPVLANCGROUP_HUGETLBMACVLANCGROUP_NET_PRIONETFILTER_XT_MATCH_ADDRTYPECGROUP_PERFNETFILTER_XT_MATCH_IPVSDM_THIN_PROVISIONINGSECURITY_APPARMORVXLANUSER_NS
Click to expand...
Click to collapse
you can simply edit afaneh_r0s_defconfig
I did. I.e. I changed
# CONFIG_IP_VS is not set
to
CONFIG_IP_VS=y
then compiled, flashed and tried to boot into system but stuck in bootloop.
I started to create the config with menuconfig because sometimes activating some of the CONFIG_ features additionally dependencies come in place or are not even available to activate.
Like activating CONFIG_IP_VS with menuconfig result in following:
CONFIG_IP_VS=y
# CONFIG_IP_VS_IPV6 is not set
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12
Or if you want to use CONFIG_BRIDGE_VLAN_FILTERING you first need to activate CONFIG_VLAN_8021Q because of the dependencie.
So I thought doing with menuconfig is the "saver" solution. But anyway, got the same problem.
lowowly said:
I did. I.e. I changed
# CONFIG_IP_VS is not set
to
CONFIG_IP_VS=y
then compiled, flashed and tried to boot into system but stuck in bootloop.
I started to create the config with menuconfig because sometimes activating some of the CONFIG_ features additionally dependencies come in place or are not even available to activate.
Like activating CONFIG_IP_VS with menuconfig result in following:
CONFIG_IP_VS=y
# CONFIG_IP_VS_IPV6 is not set
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12
Or if you want to use CONFIG_BRIDGE_VLAN_FILTERING you first need to activate CONFIG_VLAN_8021Q because of the dependencie.
So I thought doing with menuconfig is the "saver" solution. But anyway, got the same problem.
Click to expand...
Click to collapse
Anyway this is twrp thread, and I don't support kernel edit, mine is stock permissive
Thank you so far. Then I need some help in kernel edit. I start a new topic in questions section.
I'm getting bootloops on Android 13 BWA2, ADB doesn't work either. There's no possibility to install ROMs since the data partition is wiped when you flash TWRP and you can't copy files from windows to the device because it's not recognized.
neo2k12 said:
I'm getting bootloops on Android 13 BWA2, ADB doesn't work either. There's no possibility to install ROMs since the data partition is wiped when you flash TWRP and you can't copy files from windows to the device because it's not recognized.
Click to expand...
Click to collapse
You flashed the kernel!
afaneh92 said:
You flashed the kernel!
Click to expand...
Click to collapse
How am I supposed to flash the kernel if I can't get the zip file on my phone? Can you provide a tar file to be flashable in Download mode?
Will your TWRP be compatible with the new S23 series?
Well done. Flashed this image on four S22 phones, no problem. Fifth, my own - well, as mentioned on Telegram channel, I forgot to flash multidisabler. Wouldn't be a problem, but as I already setup the phone and moved over 180GB in it, I would like to query wheter it would be possible to support Samsung encryption. I am not demanding, so please don't be mad - just asking for possibility. Would be nice to have feature. While I can backup my data using migrate, I still prefer NAND backups.
neo2k12 said:
How am I supposed to flash the kernel if I can't get the zip file on my phone? Can you provide a tar file to be flashable in Download mode?
Click to expand...
Click to collapse
plugin flash drive. Mount as OTG. Problem solved