Related
<!---This is a forum post template for manitainers to use on XDA, or whatever forum you post your build(s) on. You can copy/paste what is here and edit as necessary for your purposes-->
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
step 1 : Flash Stock ROM
step 2 : Flash Recovery in Fastboot
step 3 : Flash ROM GAPPS and Magis
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/Yoshino-StockDevelopment
Download:
ROM https://crdroid.net/<device codename>
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_maple.txt
Known issues:
. Test and Tell
Visit official website @ crDroid.net
Xperia ALL ROMS Group
crDroid Community Telegram
Donate to help our team pay server costs
Contributors
Shujath, modpunk, derf elotROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: Lineage
Version Information
Status: Stable
Stable Release Date: 2020-06-29
Created 2020-06-29
Last Updated 2020-06-29
Instructions :
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
Install Latest Firmware
Grab the Sony Stock firmware using e.g. XPeriFrim. You should always flash the firmware matching the LOS build.
Grab newflasher and put it in the same folder as the firmware files.
Read the newflasher original post on XDA for general instructions!
Remove the following from the folder so they won't get flashed:
all *.ta files (keep the one in the boot/ directory)
Turn off your phone
Hold the volume down button and attach it via USB to your system till you see LED turning green
Run newflasher from within this directory to flash the remaining files
Skip the second optional step (dumping of trim area), it's useless if your bootloader is unlocked already and takes a long time.
Hit Yes for all the next questions asked in Newflasher(Only dumpin of trim area should be selected no and rest all questions should be selected as yes.
Once Newflasher flashes the Stock rom, boot into it and make sure volte is available.(VOLTE WILL NOT WORK ON BLISS IF YOU DO NOT HAVE IT IN STOCK ROM.
Incase you are not able to see volte icon in stock either your carrier does not support it or there is an issue with the stock rom(Try flashing it again).
Once you confirm Volte is available in stock, Flash the TWRP recovery and follow below instructions carefully.
Boot into recovery >> Format Data >> Power off the Phone.
Again boot into recovery >> Format Data >> Power off the Phone.
This time boot into recovery >> Wipe Internal Storage.
Flash ROM, Gapps, Magisk.
In the setup wizard select SIM 1 as the default sim for calls data and message.
Once Boot is complete, wait patiently for few mins.
Go to Settings >> Blissify >> Advanced System Icons >> Set icon for Volte.
Voilllaa you should have volte and dual sim both enabled.
Google Apps
You can download and install the Google Apps from opengapps.org. You need ARM64 and 10.x. I suggest to *always* use the pico or nano package. If you need additional apps you find them in the Play Store.
MicroG
This ROM does support Signature Spoofing. However we are watching MicroG and check if they provide newer builds e.g. for Android Pie.
FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Partially OK(Working with carrier network)
- Camera: Ok (SONY Stock Camera)
- Camcorder: Ok (SONY Stock Camera)
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Ok(Need Testing)
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- Offline Charging: Ok
- USB: Ok
- USB OTG: (Need Testing)
- Encryption: Broken
- Live Display (Profile changing on Reboot)
- SEPolicies: Enforcing
[/SIZE]
Known Issues
Please test and reply
Download and Changelog:
29th June :
-- Initial Release :
Changelog :
- Enabled strict thermals for quick charging
- Updated display related props
- Fixed randomly loosing of network
- Maps Fixed.
- Many more which I forgot
Download : https://www.androidfilehost.com/?fid=8889791610682881314
09th August 2020
Changelog :
* We are now Official.
* Managed to get RIL and Volte working wihtout
* Modem Switcher
* Customization Selector
* Modem Customization
* Fixed Random loss of Network on both Single and Dual SIM.
* Fixed Maps Crash, Huge thanks to @rcmiku
* Added Xperia Album thanks to @
* Removed Unncessary volte props causing crashes on the system.
* Satery net still passing out of the box
* Enabled Vulkan rendering.
* Removed unused Symlinks for Adreno.
* Downgraded android.hardware.gnss to 1.0
* Upgraded display vendor vendor.display.config to 1.9
* Added GNSS packages in try to fix offline GPS.
* Added CNE packages for better connectivity.
* Added IWlanService for VoWifi(Still not working)
* Added NXP hal for NFC
* Addressed CND Denails.
* Fixed Android Debugging
* Fixed Stock Camera memory Leak
* Unified Device Trees (Device will get props accordingly)
* Fixed data issue on single SIM devices(No need to toggle WiFI)
* Removed Vulkan rendering which was causing Blank screen on various apps.
* Added Sony Stock Movie Creator App
* Removed buggy DT2W
* August Security Patch merged
* Kernel upstreamed to 4.4.232
* GPS Fixed
* Enabled Doze
* Enabled sensor based wakeups(Includes Tilt, handwave, pickup, Pocket).
Download Link : https://sourceforge.net/projects/cr...Android-10.0-20200809-maple-v6.9.zip/download
11th Feb 2021
Changelog :
* January Securty Patch
* 4.4.255 Kernel
* CrDroid code upstream.
* Encryption Fixed(Format Data if you are unable to boot).
Download : https://www.androidfilehost.com/?fid=17248734326145735327
I did try Android 11 and felt Camera quality is degraded, Will stick around to 10 for a while.
woahhhh i will try now sob ???
wowwwwww, thank you so muchh
update, I have tested this rom:
+ gmaps latest version works
+ camera hardware button works(need go to rom settings -> enable camera hardware button )
+ the rom is really smooth, but from my experience, havoc is the most smooth rom
Great work Shujath!!!
duongcuong96 said:
update, I have tested this rom:
+ gmaps latest version works
+ camera hardware button works(need go to rom settings -> enable camera hardware button )
+ the rom is really smooth, but from my experience, havoc is the most smooth rom
Great work Shujath!!!
Click to expand...
Click to collapse
Hello. Is havoc stable? Gmaps is working? How much time to detect sim card?
Thanks.
Dark mode deactivate after reboot.
Led battery bar not working.
It's possible to change "lineage_maple" to for example G8142 o Xperia G8142? Where?
Thanks
Edit. Anyone knows wth happened?
Sent from my Sony lineage_maple using XDA Labs
Where is "smart charging" fuction?
Thank you
zavros said:
Where is "smart charging" fuction?
Thank you
Click to expand...
Click to collapse
Use battery charge limit from playstore.
Sent from my Sony lineage_maple using XDA Labs
Hakkinen3K said:
Hello. Is havoc stable? Gmaps is working? How much time to detect sim card?
Thanks.
Click to expand...
Click to collapse
Hello, havoc is pretty stable, but camera button not working, sim card detect is fast, just like crDroid you are using now, Gmaps latest version did not work yet, but will be fixed soon, since our great Shujath also maintenance havoc too
Hakkinen3K said:
Dark mode deactivate after reboot.
Led battery bar not working.
It's possible to change "lineage_maple" to for example G8142 o Xperia G8142? Where?
Thanks
Edit. Anyone knows wth happened?
Click to expand...
Click to collapse
First of all if no logs provided no bugs detected
Dark mode is working fine after restart and led battery bar too
Did u follow my instructions on how to install the ROM?
duongcuong96 said:
update, I have tested this rom:
+ gmaps latest version works
+ camera hardware button works(need go to rom settings -> enable camera hardware button )
+ the rom is really smooth, but from my experience, havoc is the most smooth rom
Great work Shujath!!!
Click to expand...
Click to collapse
Very much agree, havoc is really smooth
Got a question if anybody can help me, not involve the rom but I don't know...I tried to edit Mixer_paths_tasha.xml for change values for Volume I use mix Explorer text editor, code editor, fx file manager text editor and when I save the values changed but if I reboot the phone the values back to default.
Sent from my Sony lineage_maple using XDA Labs
I installed Bliss on my wife's XZP and due to the network problem and as @Shujath mentioned that the network problem is fixed on crDroid and it will be fixed on the other roms along with July security update, I decided to use crDroid till then but now that i installed it I don't know after fixing Bliss which rom should I use: crDroid? Bliss? Havoc OS? PE? I mean all of them are great. Thanks to Shujath, you guys have a lot of options to use on XZP.
09th August 2020
Changelog :
* We are now Official.
* Managed to get RIL and Volte working wihtout
* Modem Switcher
* Customization Selector
* Modem Customization
* Fixed Random loss of Network on both Single and Dual SIM.
* Fixed Maps Crash, Huge thanks to @rcmiku
* Added Xperia Album thanks to @
* Removed Unncessary volte props causing crashes on the system.
* Satery net still passing out of the box
* Enabled Vulkan rendering.
* Removed unused Symlinks for Adreno.
* Downgraded android.hardware.gnss to 1.0
* Upgraded display vendor vendor.display.config to 1.9
* Added GNSS packages in try to fix offline GPS.
* Added CNE packages for better connectivity.
* Added IWlanService for VoWifi(Still not working)
* Added NXP hal for NFC
* Addressed CND Denails.
* Fixed Android Debugging
* Fixed Stock Camera memory Leak
* Unified Device Trees (Device will get props accordingly)
* Fixed data issue on single SIM devices(No need to toggle WiFI)
* Removed Vulkan rendering which was causing Blank screen on various apps.
* Added Sony Stock Movie Creator App
* Removed buggy DT2W
* August Security Patch merged
* Kernel upstreamed to 4.4.232
* GPS Fixed
* Enabled Doze
* Enabled sensor based wakeups(Includes Tilt, handwave, pickup, Pocket).
Head over to Post#3 for download links.
Thanks for the update, it's one of my favorite and the best rom!!
@Shujath, thanks for the update.
Is webview fix even with vulkan enabled?
Sent from my Sony G8142 using XDA Labs
I have been testing the rom for a few days and it is going quite well, only I have the doubt if there is any way to improve the audio? since at least the speaker is too low. And is there also a way to change the size of the icons at startup? since I did not find how to do it. Thank you
Habacuck said:
I have been testing the rom for a few days and it is going quite well, only I have the doubt if there is any way to improve the audio? since at least the speaker is too low. And is there also a way to change the size of the icons at startup? since I did not find how to do it. Thank you
Click to expand...
Click to collapse
For sound, edit Mixer_paths_tasha.xml search for:
Code:
<path name="SPEAKER">
replace de values 82 for 84,85, maximum 86.
For headphones, search for:
Code:
<path name="headphones">
and replace de values to 82 or 84
Recommend that you install Dolby Digital 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"
}
About LineageOS
Lineage-17.1-X00TD-Asus Zenfone Max Pro M1
Build type : UNOFFICIAL
Build and signed by @[email protected] | Rajesh R
Disclaimer : ROMs are built for development purpose only. Use at your own risk.
This ROM completely compiled on lineage source code and with minimum workarounds for a successful build. Builds are signed with release-keys.Before installing, refer instructions and changelog for each builds.
About build variants
ROM-Signed release key-user build
My Projects
lineage-17.1-20210606-X00TD-user-signed.zip
fastboot-lineage-17.1-20210606-X00TD-user-signed-images.zip
lineage-17.1-20210606-recovery-X00TD.img
Features
*Gesture navigation android 10.
*Enforcing selinux and user build properties
* Certified device status under google play
* SafetyNet Test is passed
* Smooth ROM experience
Instructions
Backup procedure and precaution information
Must read before unlocking bootloader and flashing custom ROM
Some explanation regarding the whole widewine L1-L3-Qbeta etc ( Info @ https://t.me/ASUSX00TD from a member )
Starting from Q builds Asus has begun wiping DRM keys if bootloader is unlocked on that build, which is actually default behavior among most other OEMs like pixels, oneplus. Flashing Q builds (Stock beta 1 or latest) or custom ROM on unlocked bootloader through TWRP will permanently loose their L1 certification. widewine keys will be wiped by firmware itself as it detects unlocked bootloader. This also explains why some people, who flashed previous stock Q beta before on locked bootloader, even though first stock Q beta had L3 which means they hadn't fixed L1 on that beta that time , retained their L1/DRM keys on reverting to pie via downgrade zip provided by asus. So in conclusion Asus Q builds/custom ROM will wipe your DRM keys if flashed on Unlocked bootloader. Flashing on locked bootloader shouldn't be any problem!
Also those who have their persist partition backed up in pie should have no problem restoring their DRM keys in case thet got wiped by Q firmware/builds
How to Backup Persist ?
Dump all partitions and make complete backup | Partition layout and structure
Recovery method
use recoveries which support persist partition backup (eg. Orangefox)
Go to recovery > Backup > tick persist > backup > store it safe somewhere with multiple copies.
How to Restore Persist ?
Go to recovery > Restore menu > select backup > tick persist partition > Restore (process similar/different for different recoveries)
Upgrading to LineageOS 17.1
1. Make a backup of your important data
2. Download the build and also Gapps.
3. Download proper addons packages GApps for Android 10/Lineage OS 17.1
4. Make sure your recovery and firmware are up to date
5. For clean flash, Format your system,vendor,data and cache partition partition to install ROM and Gapps.
6. For installing updates format system,vendor and cache partition. keep data partition intact to flash ROM and Gapps.
Secure ROM experience
Avoid permissive selinux and rooting methods for secure ROM experience.
Refer
1. Root & SELinux Risks
2. TWRP password protection
3. TWRP encryption
Screenshots
Upcoming builds ( Only for volunteer testers )
lineage-17.1-20210512-X00TD-user-signed
* Check if audio distortion present at peak volume.
* Based on new device trees and kernel.
* Only clean flash recommended.
To test any ROM
Requirements:
Windows/linux Pc
adb drivers
Usb cable.
Steps to take log:
1. Install adb drivers in pc and enable usb debugging mode in phone. Also enable root debugging if needed.
2. Connect phone through usb and type the command "adb logcat -d>logcat.txt" in adb command window.You can choose any name you want for txt file. If needed give admin privilege for adb command window.
3. This procedure can also be used to watch occurance of bugs at realtime by connecting phone at adb mode to pc.
Steps to take boot log:
1. Make sure adb is enabled in phone. Connect the phone in usb mode to pc and open adb command window.
2. Switch off the phone and type "adb logcat -d>bootlog.txt".
3. Initially "waiting for the device" message is noticed on adb command window and switch on the phone now. once the device powers on, boot log is recorded.
log text files are stored in location where adb drivers are installed.
Note : Test builds are released here and intended to test upcoming fixes and features.
Source Code
Kernel source code : https://github.com/SagarMakhar/android_kernel_asus_sdm660
Kernel developer credits : @SagarMakhar
Credits
Google's AOSP Project.
Lineage OS for the source code and The Open GApps Project.
Contribute to Lineage OS at https://paypal.me/LineageOS
Contribute to Gapps at https://www.paypal.com/donate/?toke...EScTbkNmciIDl9n5LyDW&country.x=US&locale.x=US
Thanks to developers and their contribution on custom ROM development for Asus zenfone max pro M1. Thanks @Patching.Unconditionally, @patkk for testing builds.
Special thanks for the build server admin and @abhishekt295 , TheButti for upload server.
It's all free, but donations are welcome
Donations will be contributed to server maintenance
Support developers on their respective threads.
Feedback and bug reports are welcome.
Kindly use english language on comment section
Changelog
24. OTA : lineage-17.1-20210606-X00TD-user-signed.zip
* Synced with source updates and fixes.
23. OTA : lineage-17.1-20210603-X00TD-user-signed.zip
* OTA support to lineage-17.1-20210531-X00TD-user-signed.zip
* Sound output Fixes
22. Build : lineage-17.1-20210531-X00TD-user-signed.zip
* FBE-File-Based Encryption implementation. Only clean flash recommended. It is not OTA release
* Updated media configs from stock.
* Update fingerprint to UL-ASUS_X01BD-WW-17.2018.2012.438-user
* Upgradable to build lineage-18.1-20210525-X00TD-user-signed.zip through dirty flash.
21. Build : lineage-17.1-20210526-X00TD-user-signed.zip
* AVB disabled and Verity Enabled.
* Locking bootloader supported. Works only with lineage recovery.
Note : Lock only if lineage recovery is flashed. If bootloader locked with twrp. Device fails to boot and only fastboot mode helps to solve the issue to unlock bootloader again.
* Dirty flash on previous lineage-17.1 builds wont work. It is not OTA release. Only clean flash recommended.
* Sound control features added.
* Adaptive sleep features.
* Upgradable to build lineage-18.1-20210525-X00TD-user-signed.zip through dirty flash.
20. OTA update : lineage-17.1-20210518-X00TD-user-signed
* Device tree updates.
* Synced with lineage source updates.
* Update to lineage-18.1 through OTA is supported.
19. OTA update : lineage-17.1-20210404-X00TD-user-signed
* KSM tunning
* Removal of SoterService
18. OTA update : lineage-17.1-20210327-X00TD-user-signed
* VoLTE icon support on status bar.
* Updated audio drivers.
* KSM tunning.
17. OTA update : lineage-17.1-20210306-X00TD-user-signed
* CAF audio.
* Updated audio configs from stock 10 release.
16. OTA update : lineage-17.1-20210204-X00TD-user-signed
* Kernel updates
* Sepolicy updates on enforcing selinux.
* Fingerprint biometrics fixes.
* Safetynet fixes.
15. OTA update : lineage-17.1-20210103-X00TD-user-signed
* Sepolicy updates on enforcing selinux.
* Fingerprint biometrics fixes
* MusicFX Equalizer (Download optional add-on )
14. OTA update : lineage-17.1-20210101-X00TD-user-signed (Optional download)
*Permissive selinux .
13. Build name :lineage-17.1-20201229-X00TD-user-signed
* OTA support through lineage updater.
* Sepolicy cleanup
* MusicFX Equalizer (Download optional add-on )
12. Build name :lineage-17.1-20201215-X00TD-user-signed
* Security patch update
* Updated Fingerprint driver from asus android 10 beta.
11. Build name :lineage-17.1-20201112-X00TD-user-signed
* Security patch update
*Added Fingerprint driver
10. Build name : lineage-17.1-20201101-user-signed
* Safetynet fixes and sepolicy updates.
9. Build name : lineage-17.1-20201017-user-signed
Status : Working fine
Bugs: Fingerprint missing
8. Build name : lineage-17.1-20201015-user-signed
*Charging current restored to Stock values.
* Improvements in battery backup.
* Camera2api support for snap camera.
* Ambient display
* Scoped storage related fixes.
* Dirty flash Supported over lineage-17.1-20201005-X00TD-user-signed build
Status : Working fine
7. Build name : lineage-17.1-20201005-user-signed
* Enforcing selinux and user build properties
* Certified device status under google play
* SafetyNet Test is passed
* Dirty flash supported over lineage-17.1-20201003/20200927-userdebug-signed builds
Status : Working fine
6 .Build name : lineage-17.1-20201003-userdebug-signed
* Enforcing selinux
* Certified device status under google play
* SafetyNet Test is passed
* Dirty flash supported over lineage-17.1-20200927-userdebug-signed
Status : Working fine
5 .Build name : lineage-17.1-20200927-userdebug-signed
* Permissive boot
Status : Working fine
4. Build name : lineage-17.1-20200926-userdebug-signed
* Permissive boot
Status : booted but no display
3. Build name : lineage-17.1-20200925-user/userdebug-signed
Status : bootloop
2. Build name : lineage-17.1-20200924-user/userdebug-signed
Status : bootloop
1. Build name : lineage-17.1-20200923-X00TD-user-signed
* Lineage-17.1-20200923 | Android10_r41
* release key user build
* Status : Experimental release-not booting
Rom doesnt boot
I installed everything and the rom reboots to LOS Recovery
Andys4c said:
I installed everything and the rom reboots to LOS Recovery
Click to expand...
Click to collapse
Did you clean flash.? Facing bootloop.? Or not even booting rom.?
This rom uses stable trees from corvus ROM. I will checkout issues. Meanwhile try out userdebug rom by changing kernel or permissive boot.:good:
This build project aims to replicate stock ROM properties and has its first experimental build. Wait for the stable build.:good:
[email protected] said:
Did you clean flash.? Facing bootloop.? Or not even booting rom.?
This rom uses stable trees from corvus ROM. I will checkout issues. Meanwhile try out userdebug rom by changing kernel or permissive boot.:good:
This build project aims to replicate stock ROM properties and has its first experimental build. Wait for the stable build.:good:
Click to expand...
Click to collapse
i always cleanflash. The rom hang on lineage Logo and then rebooted to lineage Recovery
Andys4c said:
i always cleanflash. The rom hang on lineage Logo and then rebooted to lineage Recovery
Click to expand...
Click to collapse
If you see lineage boot animation (logo) it is bootloop. Changing kernel or permissive boot may help. To fix ROM, I am building new userdebug enforcing build. Kindly wait.:fingers-crossed: Once we succeed userdebug build then its is worth trying user build with signed release keys:good:
Advantage of release key builds : Building an Android OS image using make will sign all .apk files using the test-keys. Since the test-keys are publicly known, anybody can sign their own .apk files with the same keys, which may allow them to replace or hijack system apps built into your OS image. For this reason it is critical to sign any publicly released or deployed Android OS image with a special set of release-keys that only you have access to.
Build Variants :
eng - Engineering build comes with default root access.
user-debug - User debug build does not come with default root access but can be rooted. It also contains extra logging.
user - User build is the one flashed on production phones. Has no root access.
Source : https://stackoverflow.com/questions/13950589/difference-between-eng-and-user-debug-build-in-android
Most of the custom ROMs are userdebug and stock ROMs are user builds.
i seen that you uploaded new buld. Does it boot?
still doesnt boot
I tried every build, changing kernel etc... but i give up.This is the poorest buildbotting i ever seen
Andys4c said:
I tried every build, changing kernel etc... but i give up.This is the poorest buildbotting i ever seen
Click to expand...
Click to collapse
Did you try permissive boot.? I used device source code from previous successful builds. I came to know asus ROM development is not user friendly and also not intended to perfection. Not a healthy coordination across developers. All development stops at engineering builds because of its complexity involved.
The truth is even stock ROM lack some features . It's the best secure build to be trusted with android secure properties.:good:
how to make rom permissive? by creating permissive kernel?
??
Bro check before uploading if it boots or not coz..many of us don't have pc ? after that we can test n tell bugs thankyou
Andys4c said:
??
Click to expand...
Click to collapse
All userdebug enforcing ROM support permissive boot by including the line "androidboot.selinux=permissive" on the kernel command line. Kernel command line is found on boot.img. You can reverse engineer boot.img by using this tool https://github.com/xiaolu/mkbootimg_tools. Test this only on userdebug builds.
For easy , I will upload permissive boot ROM:good:
lineage-17.1-20200927-X00TD-userdebug-signed.zip
* Release key signed build.
* Updated with latest source based on lineage-17.1
* Permissive boot.
[email protected] said:
lineage-17.1-20200927-X00TD-userdebug-signed.zip
* Release key signed build.
* Updated with latest source based on lineage-17.1
* Permissive boot.
Click to expand...
Click to collapse
finally!! Btw, do you have the device or buildbotting blindly?
Andys4c said:
finally!! Btw, do you have the device or buildbotting blindly?
Click to expand...
Click to collapse
Didnt give up till it boots.My builds are built using server and volunteerly tested. As mentioned before blindly taking source from successful xda ROM threads are not working. They needed some fixes. Next thing is to push this builds to enforcing boot. Hereafter, only successful builds will be updated.:good:
New update
Build name : lineage-17.1-20201003-userdebug-signed
* Enforcing selinux
* Certified device status under google play
* SafetyNet Test is passed
Status : Working fine
wow, Amazing. Does F2FS partition support?
a_fahruddin said:
wow, Amazing. Does F2FS partition support?
Click to expand...
Click to collapse
Not sure..check source code ..if not i will add support in upcoming builds..Next thing is to push the build project to user build properties like stock ROM.:good:
thanks sir
i hope in the next update sound is more louder.
{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty may be void.
*
* We're not responsible for bricked devices, dead OTGs or you 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 us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on: TWRP v3.4.0
PitchBlack version: 3.0.0
Device: picasso (all models should work)
Picasso TG general group: https://t.me/XiaomiRedmiK30
Maintainer/Authors build: masemoel and Hadenix
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version/another recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From fastboot
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
From TWRP app
(Ideal if you don't own a PC).
Download Official TWRP app from Play Store.
Extract the PBRP zip.
Flash the recovery.img with the TWRP app.
Reboot to recovery.
Flash the whole PBRP zip (otherwise you won't have PBRP tools working properly).
Enjoy
Changelog
PBRP changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR\
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Picasso changelog
Code:
PBRP 3.0.0 2020-12-17 - Android Q and R
- Added nano editor.
- Fixed decryption issues with Android 11 (now it should decrypt even when the password is not a pattern). This makes now A11 PBRP be marked as stable!
- All PBRP changes in the latest month.
PBRP 3.0.0 2020-11-10 - Android Q and R
- Fixed errors when wiping some partitions.
- Touch delay on the first 5 seconds has gone.
- Minor touches on fstabs.
- All PBRP work in the latest week.
PBRP 3.0.0 2020-11-03 - Android Q and R
- Updated vendor, kernel and dtbo to xiaomi.eu 12.0.7.0 ones.
- Fixed wiping errors in [U]Wipe[/U] section.
- Fixed some flags in dynamic partitions.
- (Hopefully) Fixed asking decryption key when it's not needed.
- Fixed flashing failure with multiple Migrate zips.
- Fixed duplicated super partition in backup section.
- Translations updated (PBRP team) and other minor stuff by the team as well :).
PBRP 3.0.0 2020-10-03 - Android R
- Initial XDA release, based on Q tree.
PBRP 3.0.0 2020-10-03 - Android Q
- Update kernel stuff to stable MiUI 12.0.6.
- Remove DTBO partition from Wipe section (it can't be wiped).
- Some PBRP UI fixes by the team.
PBRP 3.0.0 2020-10-01 - Android Q
- Now we don't need to unmount anything before flashing.
- Translation characters are now showed correctly (fixes issue with Asian fonts not showing).
- Some UI fixes and other improvement by the PBRP team.
PBRP 3.0.0 2020-09-19 - Android Q
- Initial XDA release
Bugs
- You tell me!
- Check current issues at the GitHub Issues tracker before reporting one (it may already exist): https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery/issues
Downloads
Flashable Android 10/Q zip [MEGA folder]
https://mega.nz/folder/10I1RKgC#onjHUvM4-trZ9qcfkWkLtw
Flashable Android 11/R zip [MEGA folder]
https://mega.nz/folder/EoIHDYIL#kFemXVyMKd53kKCdZm3SUg
Note that this is still experimental as Android 11 source for PBRP hasn't been still released!
Version information
Status: Stable
Created: 2020-09-19
Last updated: 2020-11-03
Beers & coffees (obviously hitting the thanks button is always enough, but this will motivate me 1000%): https://www.paypal.com/paypalme/masemoel
Little reminder here: I abandoned this project in favour of OrangeFox Recovery Project, so don't expect any updates from my side here anymore. If anyone is willing to continue this project, my trees are available as always on my GitHub (see the OP).
OrangeFox Recovery Project for picasso
Ey, Jienensse. Sabes porque cada vez que intento flashear este PichBlack recovery, flasheandose correctamente no inicia nada? Directamente entra a Android como si no hubiera recovery alguno...
Saludos de un murciano
(PD) Estoy en la ROM Xiaomi.EU 11.0.11, actualmente atrapado sin TWRP... ?
Dan Ratia said:
Ey, Jienensse. Sabes porque cada vez que intento flashear este PichBlack recovery, flasheandose correctamente no inicia nada? Directamente entra a Android como si no hubiera recovery alguno...
Saludos de un murciano
(PD) Estoy en la ROM Xiaomi.EU 11.0.11, actualmente atrapado sin TWRP... ?
Click to expand...
Click to collapse
Hola. ¿Has seguido los pasos que indico para instalar PBRP mediante TWRP o fastboot?
Para entrar a la recovery tienes que hacer volumen + y botón de encendido a la misma vez.
(Recuerda que, según las reglas de XDA, sólo se puede hablar inglés en los foros)
----------------------------
Hi. Have you followed the steps in the main post to flash via TWRP or fastboot?
To enter into recovery, you must shut on your phone by pressing volume + and power button at the same time.
(Remember that you can only speak English here, XDA rules).
Sent from my Redmi K30 5G using XDA Labs
masemoel said:
Hola. ¿Has seguido los pasos que indico para instalar PBRP mediante TWRP o fastboot?
Para entrar a la recovery tienes que hacer volumen + y botón de encendido a la misma vez.
(Recuerda que, según las reglas de XDA, sólo se puede hablar inglés en los foros)
----------------------------
Hi. Have you followed the steps in the main post to flash via TWRP or fastboot?
To enter into recovery, you must shut on your phone by pressing volume + and power button at the same time.
(Remember that you can only speak English here, XDA rules).
Sent from my Redmi K30 5G using XDA Labs
Click to expand...
Click to collapse
Of course, first I tried an unofficial Chinese TWRP, which although it worked, it did not let me interact with the system partition and I wanted to change to this one. It flashes but does not start.
Then I tried from Flashify and from the TWRP app. Same result.
Then from the PC via fastboot, first from the Xiaomi ADB Fastboot Tool and then from CMD, with and without vbmeta.img. Same result.
In fact, I tried other versions and the same ...
It's strange, I have never had problems with flashing TWRP on Xiaomi, what's more, I have a YouTube channel where I show the processes in many of them and I wanted to make a video of this PichBlack for the K30.
Dan Ratia said:
Of course, first I tried an unofficial Chinese TWRP, which although it worked, it did not let me interact with the system partition and I wanted to change to this one. It flashes but does not start.
Then I tried from Flashify and from the TWRP app. Same result.
Then from the PC via fastboot, first from the Xiaomi ADB Fastboot Tool and then from CMD, with and without vbmeta.img. Same result.
In fact, I tried other versions and the same ...
It's strange, I have never had problems with flashing TWRP on Xiaomi, what's more, I have a YouTube channel where I show the processes in many of them and I wanted to make a video of this PichBlack for the K30.
Click to expand...
Click to collapse
Weird... Ensure that you have Redmi K30 5G version, and not normal K30 (aka phoenix).
Sent from my Redmi K30 5G using XDA Labs
Yes, i am sure it is Redmi K30 5G
Dan Ratia said:
Yes, i am sure it is Redmi K30 5G
Click to expand...
Click to collapse
Then it's very weird... No one has reported that the recovery is not booting on their picasso.
Did you flashed that modified vbmeta image by PeterCxy for his LineageOS recovery? (If you flashed it, then flash the original one)
Either that or your outdated vendor base would be the reason why it's not booting for you.
Sent from my Redmi K30 5G using XDA Labs
I don't know, man, this has never happened to me and I've been using modified recovery since CMW 3. The only thing I have not tried yet is to install the original Miui recovery and try again with the modified recovery.
Dan Ratia said:
I don't know, man, this has never happened to me and I've been using modified recovery since CMW 3. The only thing I have not tried yet is to install the original Miui recovery and try again with the modified recovery.
Click to expand...
Click to collapse
Consider upgrading to a newer MiUI version (like latest 11 or 12 version) via LRTWRP.
Then PBRP should boot.
Sent from my Redmi K30 5G using XDA Labs
Dear Masemoel：
Appreciate your contribution to such a nice work. I have noticed that you are working on another unofficial TWRP, and it also works great. Do you consider to add it in this thread or creat another thread? Cuz i think both recoveries are very cool custom recoveries and ppl are very willing to use them.
ThomasRhin said:
Dear Masemoel：
Appreciate your contribution to such a nice work. I have noticed that you are working on another unofficial TWRP, and it also works great. Do you consider to add it in this thread or creat another thread? Cuz i think both recoveries are very cool custom recoveries and ppl are very willing to use them.
Click to expand...
Click to collapse
Hello and thanks, Thomas.
The unofficial TWRP is being maintained by Hadenix in GitHub's picasso group right now.
Me I will stay in PBRP as I feel comfortable, safe, and has a lot of features with a nice UI ?
I once built TWRP to ensure that the device tree I did was working as it should, and also to see if an issue in PBRP was happening in TWRP as well.
https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery/releases/tag/TWRP
But I won't build it anymore for now, PBRP works flawlessly + there is already another dev compiling and improving it.
Sent from my Redmi K30 5G using XDA Labs
so its only for k30 5g or it will aslo work on k30i 5g?
@tensionless said:
so its only for k30 5g or it will aslo work on k30i 5g?
Click to expand...
Click to collapse
It should work... I haven't tested though as I don't have that picasso variant
Sent from my Redmi K30 5G using XDA Labs
masemoel said:
Consider upgrading to a newer MiUI version (like latest 11 or 12 version) via LRTWRP.
Then PBRP should boot.
Sent from my Redmi K30 5G using XDA Labs
Click to expand...
Click to collapse
Thanks man, I had to do that to make PBRP work in the end :highfive:
One more doubt, I installed the CrDdroid port ROM that I found in your repository and I am not able to root. I have tried Magisk 20.1, 20.2, 20.3 and 20.4 (including the canary version), but when flashing the ROM it does not start. Is there any way to get Magisk to work on this unofficial CrDroid?
Dan Ratia said:
Thanks man, I had to do that to make PBRP work in the end :highfive:
One more doubt, I installed the CrDdroid port ROM that I found in your repository and I am not able to root. I have tried Magisk 20.1, 20.2, 20.3 and 20.4 (including the canary version), but when flashing the ROM it does not start. Is there any way to get Magisk to work on this unofficial CrDroid?
Click to expand...
Click to collapse
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access
masemoel said:
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access
Click to expand...
Click to collapse
Well i wil try again, i flashed ROM, Gapps, start ROM, Format data and Magisk.
masemoel said:
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access
Click to expand...
Click to collapse
I already did the steps you mention, but the result is the same, the ROM does not start. It only starts when uninstalling magisk.
In fact, CrDroid itself tries to install the Magisk addon and it doesn't succeed (I attach images), try Magisk 20.4 and 20.1 from the official website.
Could you pass me the AICP that you are using? I want AOSP with root ...
Dan Ratia said:
I already did the steps you mention, but the result is the same, the ROM does not start. It only starts when uninstalling magisk.
In fact, CrDroid itself tries to install the Magisk addon and it doesn't succeed (I attach images), try Magisk 20.4 and 20.1 from the official website.
Could you pass me the AICP that you are using? I want AOSP with root ...
Click to expand...
Click to collapse
You are flashing Magisk and then flashing crDroid????
Wipe everything (data, cache and dalvik)
Reboot to recovery
Flash crDroid
Flash Magisk
Flash GApps (obviously this is optional)
Wipe data and dalvik again
Reboot
I don't know what's that Magisk addon.d ... But it might be causing the bootloop.
Also ensure that you're using the latest PBRP release for Android 10 and that you are not mounting any partition other than data and cache.
Use the zip from the GitHub's Magisk releases pages I sent you...
Sent from my Redmi K30 5G using XDA Labs
masemoel said:
You are flashing Magisk and then flashing crDroid????
Wipe everything (data, cache and dalvik)
Reboot to recovery
Flash crDroid
Flash Magisk
Flash GApps (obviously this is optional)
Wipe data and dalvik again
Reboot
I don't know what's that Magisk addon.d ... But it might be causing the bootloop.
Also ensure that you're using the latest PBRP release for Android 10 and that you are not mounting any partition other than data and cache.
Use the zip from the GitHub's Magisk releases pages I sent you...
Click to expand...
Click to collapse
Ok I got it... You are flashing the forcing encryption disabler... Then you have to flash Magisk 20.3 only, and later you can upgrade if you want...
Flash it after crDroid as well
EDIT: You can look at my AICP build either in the Telegram group mentioned in the OP, or by looking at Redmi-30-5G GitHub.
Sent from my Redmi K30 5G using XDA Labs
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you 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 us for messing up your device, we will laugh at you.
*
*/
This is the AOSP ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
AOSP, ROM for the Xperia XZ2
Contributors
MartinX3, Sony, SonyAOSP
Source Code: https://github.com/sonyxperiadev
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 11
Beta Release Date: 2020-10-23
Created 2020-10-23
Last Updated 2020-10-23
Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
Please use the the OEM build which came before my last release, if you getting problems like a not bootable or crashing device.
GCAM Camera App:
Suggested GCams
Installation with a recovery:
fastboot flash oem _a oem_*.img (Only needed until the device receives mainline support by SODP)
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
OpenGapps (Requires TWRP or a custom ROM recovery)
Dual Sim Patcher (Requires TWRP or a custom ROM recovery)
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w (Wipes your internal storage and the userdata)
Now you got the AOSP recovery, to please continue with the normal installation
News
09.02.2022
android 12
[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1 [Alpha]
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :) Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you! Official site...
forum.xda-developers.com
Click to expand...
Click to collapse
20.09.2021
android-11.0.0_r43 (September security patchlevel)
OEMv7 support
Click to expand...
Click to collapse
19.09.2021
Revoked the r43 buiild because of error
AndroidRuntime: java.lang.IllegalArgumentException: invokeOemRilRequestRaw failed with rc = -2
We need to wait until the following PRs get merged
[TRANSPOWER] [3/4] Convert all makefiles to BluePrint by MarijnS95 · Pull Request #14 · sonyxperiadev/transpower
Depends on #13 Blueprint is easier to read, has less possibilities for complicated configuration (for the better) and is much quicker to parse by the build system. Note that an extra android_librar...
github.com
[TRANSPOWER] [4/4] [WIP/RFC] Make SDK-28 compliant, use HookMediator for qcrild by MarijnS95 · Pull Request #11 · sonyxperiadev/transpower
Depends on #14 Hi @jzoran, This PR attempts to fix a multitude of things related to recent changes on SODP and Android API compatibility. Let me run through them sequentially: Kumano requires qcril...
github.com
Click to expand...
Click to collapse
17.09.2021
android-11.0.0_r43 (September security patchlevel)
OEMv7 support
Click to expand...
Click to collapse
17.08.2021
android-11.0.0_r40 (August security patchlevel)
OEMv6 support (Now our device uses the same camx camera framework like Xperia 1/5 (I / II / III)
Click to expand...
Click to collapse
25.07.2021
android-11.0.0_r39 (July security patchlevel)
Click to expand...
Click to collapse
10.06.2021
android-11.0.0_r38 (June security patchlevel)
OEMv5 support!
Click to expand...
Click to collapse
10.05.2021
android-11.0.0_r36 (May security patchlevel)
Click to expand...
Click to collapse
08.04.2021
android-11.0.0_r34 (April security patchlevel)
OEMv4 support!
Click to expand...
Click to collapse
12.03.2021
android-11.0.0_r32 (March security patchlevel)
Fixed mobile and wifi
Click to expand...
Click to collapse
13.02.2021
android-11.0.0_r29 (February security patchlevel)
Click to expand...
Click to collapse
12.01.2021
android-11.0.0_r27 (January security patchlevel)
Click to expand...
Click to collapse
12.12.2020
android-11.0.0_r18 (December security patchlevel)
Click to expand...
Click to collapse
14.11.2020
android-11.0.0_r17 (november security patchlevel)
Click to expand...
Click to collapse
23.10.2020
hello android-11.0.0_r4 (october security patches!) for the xz2, xz2c & xz3
Click to expand...
Click to collapse
23.10.2020
Hello android-11.0.0_r4 (October Security patches!) for the XZ2, XZ2C & XZ3
Click to expand...
Click to collapse
Wow..thanks a lot bro. I go test it tomorrow
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk
NYGGAZ said:
Wow..thanks a lot bro. I go test it tomorrow
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk
Click to expand...
Click to collapse
You're welcome
And please report back if the dual sim patcher is still working
MartinX3 said:
You're welcome
And please report back if the dual sim patcher is still working
Click to expand...
Click to collapse
Of course bro.. I hope it work. Thanks a lot for your work[emoji6][emoji6]
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk
thank you i am going to try it soon
Thank you very much for the effort to keep this phone alive!
Can I flash oem directly over the LOS 17.1 or need to reflash the latest FW?
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk
NYGGAZ said:
Can I flash oem directly over the LOS 17.1 or need to reflash the latest FW?
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk
Click to expand...
Click to collapse
Depends if you booted the latest FW on both slots the last time you came from stock.
Deleted
NYGGAZ said:
All is very VERY GOOD.. thanks Martin.. [emoji6][emoji6]View attachment 5123697
Envoyé de mon Xperia XZ3 (AOSP) en utilisant Tapatalk
View attachment 5123699
Click to expand...
Click to collapse
Thank you
But please hide several numbers in your screenshots.
Is it works with latest october blobs?
Coz my compiled one doesn't. Only works with latest A10 blobs.
zhka said:
Is it works with latest october blobs?
Coz my compiled one doesn't. Only works with latest A10 blobs.
Click to expand...
Click to collapse
Yes, this one only works with the newest OEM released before my builds.
which gapps to use
logan123456 said:
which gapps to use
Click to expand...
Click to collapse
Every
I prefer pico
I have been following the "no recovery" steps.
I have got the payload.bin extracted with this https://github.com/vm03/payload_dumper
Afterwards, I have got all the img flashed with fastboot.
Where should the SW_binaries_for_Xperia_Android_11_4.14_v1a_tama.img be used?
y2kbugleung said:
I have been following the "no recovery" steps.
I have got the payload.bin extracted with this https://github.com/vm03/payload_dumper
Afterwards, I have got all the img flashed with fastboot.
Where should the SW_binaries_for_Xperia_Android_11_4.14_v1a_tama.img be used?
Click to expand...
Click to collapse
Nice!
The OEM step of the normal installation above
MartinX3 said:
Nice!
The OEM step of the normal installation above
Click to expand...
Click to collapse
So I fastboot flash oem SW...tama.img after flashing all ROM images.
Afterwards, do I still need a recovery (TWRP) to flash GApps and dual-sim-patch?
How could I install a recovery? I cannot find one from TWRP official site.
Thanks.
OrangeFox Recovery Project
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
OrangeFox is FREE SOFTWARE
Credits:
* TeamWin - for TWRP
* The OrangeFox Team - for their hard work
* @DarthJabba9 for his help throughout the process and for bearing my spam.
* @ me xD
FEATURES:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* Support for managing Magisk modules
* Aroma FM
* Password
* Support Custom ROMs
* Superb new UI and themes
* OrangeFox theme engine:
* Choice of theme (black, dark, etc)
* Choice of color scheme
* Choice of splash screen
* Alternative lockscreen
* And many more!
DOWNLOADS
R11.1/R11.1_1:
Official website download link: Here
R11.1_2:
GitHub : Here
R11.1_3:
GitHub : Here
INSTALLATION
1. Download the OrangeFox zip to your device
2. Reboot to your existing OrangeFox/TWRP (or other custom TWRP-based) Recovery
3. Install the OrangeFox zip as a normal zip installer
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
For bugs and changelog see the 2nd post.
FAQ and Guides:
Guides and Frequently Asked Questions
wiki.orangefox.tech
Device Tree:
GitHub - Yilliee/recovery_a51: Recovery device tree for Galaxy A51 4g (SM-A515X)
Recovery device tree for Galaxy A51 4g (SM-A515X). Contribute to Yilliee/recovery_a51 development by creating an account on GitHub.
github.com
Kernel Source:
GitHub - Yilliee/android_kernel_samsung_exynos9611
Contribute to Yilliee/android_kernel_samsung_exynos9611 development by creating an account on GitHub.
github.com
XDA:DevDB Information
OrangeFox Recovery Project, Tool/Utility for the Samsung Galaxy A51 4G
Contributors (OrangeFox Team)
MrYacha, DarthJabba9
Source Code:
OrangeFox Recovery · GitLab
OrangeFox Recovery | OFR
gitlab.com
Version Information for a51
Status: Stable
Current Latest Version: R11.1_3
Beta Release Date: 2022-26-05
Post details
Created: 2021-02-22
Last Updated: 2021-31-05
Changelogs
R11.0:
- Initial Build for a51.
R11.1:
- Update to R11.1
- Removed system image mount from fstab. (Use Dynapatch)
- Fixed Standalone ADB and ADB sideload.
- Fixed AromaFM.
- Fixed Themes getting reset after rebooting recovery.
- Fixed Vibration.
- Fixed the codename / dtbo errors woth respect to BlueFly.
- Added Vbmeta, Vbmeta_samsung and Dtbo to backup menu and allow flashing images to them.
R11.1_2:
- Fix status bar height ( It is now right till the bottom of punch-hole )
- Add up_param entry in fstab ( You can flash the .bin/.tar files by renaming them to .img and just using the flash image option ).
- Integrate multidisabler by @ianmacd into the build and allow specifying specific things to disable.
- Fix AVB. ( Recovery does not need a patched vbmeta to boot anymore ).
- Switch to Celica Kernel and dtb+dtbo built from source.
- Fix issues with adb, sideload and mtp.
- Fix fastbootd ( Reboot >> fastboot in recovery ).
- Exclude twrp_Apex.cpp. ( Fixes the blinking issue with Android-12 ).
- Skip the Samsung selinux enforce patches as well as creating a .tar file placed within the zip.
- Implement FOX_CUSTOM_BINS_TO_SDCARD. ( Adds nano editor, sed binary, tar binary, unzip binary and xz utils ).
- Don't keep persistent log history.
- Include @phhusson's lptools binary.
- Include HexDump Utility.
R11.1_3:
- Fix the syntax issues with multidisabler script.
- Bump version number to _3 and change status from beta to stable.
- Include app manager and amend it to work with Android 11/12.
- Don't show the warnings
unable to update logical partition
on the console.
- Update kernel to Celicia-v2.0 (Based on A515FXXU5FVC2).
Bugs
R11.0:
- Just ignore the following error/red lines in console for the meanwhile:
E:unable to update logical partition: /system_image
- See the post below for AromaFM fix.
- Haptic feedback aka Vibration doesn't work.
R11.1:
- Decryption
- Fastbootd doesn't work so the configs have been removed for the meanwhile.
R11.1_2+:
- None
Extra Fixes
Only for R11.0:
For fixing AromaFM, download the aromafm.zip from here and replace in Internal Storage /Fox/FoxFiles/AromaFM/ with the one attached here
Great work!!
The error that mentions that it appears seems to me that it is a thing of the fstab (E:unable to update logical partition: /system_image) it may also be that the gsi that were tested were in RO Just what I think, I'm new enough to Samsung to really know
or try to use, but my device goes to Download mode and says vbmeta is missing, any solution?
LichtEstarossx said:
or try to use, but my device goes to Download mode and says vbmeta is missing, any solution?
Click to expand...
Click to collapse
Your android version must be compatible with the recovery.
GrandmaGotGuns said:
Your android version must be compatible with the recovery.
Click to expand...
Click to collapse
according to the tree it is for android
LichtEstarossx said:
according to the tree it is for android
Click to expand...
Click to collapse
Sure but this recovery is specifically for Android R aka android 11 if you device was at android 10 by default i.e. it was shipped with Android 10 and has not been updated to android 11, then it might be the cause. Just update to latest android version and all these issue will go away
U can download one ui 3 from here.
Select the region and it'll show all the one ui roms available, if one ui 3 is not available in your region then change the region, like to Russia.
Model : SM-A515F - Galaxy A51 — Samfrew.com
Model : SM-A515F | Samsung Firmware Database
samfrew.com
LichtEstarossx said:
or try to use, but my device goes to Download mode and says vbmeta is missing, any solution?
Click to expand...
Click to collapse
Make sure you are on ONEUI 3 /Android 11 /Android R. And flash a null vbmeta to get it to boot.
LichtEstarossx said:
The error that mentions that it appears seems to me that it is a thing of the fstab (E:unable to update logical partition: /system_image) it may also be that the gsi that were tested were in RO Just what I think, I'm new enough to Samsung to really know
Click to expand...
Click to collapse
That error message shows because system is a logical partition and logical partitions are supposed to be read only but in order to add support for direct gsi flashing, system image has been mounted as rw which causes the error to be displayed.
I had to choose between removing the error or the direct GSI support, and I ended up choosing the latter.
Yillié said:
Make sure you are on ONEUI 3 /Android 11 /Android R. And flash a null vbmeta to get it to boot.
Click to expand...
Click to collapse
what? the tree said it is for Android 10 ._.
LichtEstarossx said:
what? the tree said it is for Android 10 ._.
Click to expand...
Click to collapse
Does the tree says anywhere that the builds will only be for Android 10???
It only mentions that the build system was based on Android 10 not for only Android 10.
Great job thank you
eu
Yillié said:
Essa mensagem de erro é exibida porque o sistema é uma partição lógica e as partições lógicas devem ser somente leitura, mas para adicionar suporte para flashing gsi direto, a imagem do sistema foi montada como rw, o que faz com que o erro seja exibido.
Tive que escolher entre remover o erro ou o suporte direto ao GSI, e acabei escolhendo o último.
Click to expand...
Click to collapse
Is possible flash direct GSI?
Chondoe no necessary in OrangeFox?
hacker812c said:
eu
Is possible flash direct GSI?
Chondoe no necessary in OrangeFox?
Click to expand...
Click to collapse
For the R11.0 build it can be flashed directlyno need for any Addons or anything of that sort. Tho if you wanna flash Gapps right after the gsi without booting even once , try checking out the system_resizer.zip on my sourceforge account.
Yillié said:
For the R11.0 build it can be flashed directlyno need for any Addons or anything of that sort. Tho if you wanna flash Gapps right after the gsi without booting even once , try checking out the system_resizer.zip on my sourceforge account.
Click to expand...
Click to collapse
Thank you
System resizer script separate system and vendor?
Great work
I don t have access to write text in telegram group
Sorry not respost you @Yillié
Send link of script system please
hacker812c said:
I don t have access to write text in telegram group
Sorry not respost you @Yillié
Send link of script system please
Click to expand...
Click to collapse
Ah wait lemme unmute you there and here's the link of the zip;
https://sourceforge.net/projects/yilliee-projects/files/Partition%20Resizer/System-Resizer.zip/download
Yillié said:
Ah wait lemme unmute you there and here's the link of the zip;
https://sourceforge.net/projects/yilliee-projects/files/Partition%20Resizer/System-Resizer.zip/download
Click to expand...
Click to collapse
Explain more system resizer
Thank you