Code:
/*
* Your warranty is no longer valid, unless you lie.
*
* I am not responsible for bricked devices, strained relationships,
* 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 kernel
* 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.
*
*/
What's AOSP?
Android™ SONY Open Source Project (SODP) is AOSP Android as Google publish without any modifications.
*This ROM build is 100% Sony AOSP Code and I planning adding upstream into kernel sony in futures.
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. re-verify you hva respected step flash
----DOWNLOAD SODP ----
GDRIVE
- INSTRUCTIONS FLASH -
1) GO IN FASTBOOTD
On you PC: Enter the following command and wait for the device to reboot into fastbootd : fastboot reboot fastboot or before device start press volume down + power button , in menu select fastbootd
2) DOWNLOAD OEM BINARY & flash it : fastboot flash oem (youroemfile).img
3) UNPACK SODP.ZIP & FLASH these image SODP :
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot flash product product.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash system_ext system_ext.img
fastboot erase metadata ( if you have error partition no exist like me just ignore )
ignore all other img - I have simply added in zip all img generated after compile
4 ) reboot in recovery - wipe data/factory reset
5) reboot in system ENJOY
Bugtracker:
- I tested and build looks stable for daily use. I have doing basic test and seem all working , I can see btw no night mode enabled by default.
SODP Bugtracker -> If you think the problem is in SODP ( REPORT WITCH PROPER LOG )
XDAevDB Information
AOSP, ROM for the Xperia 10 III
Contributors
Sony, SonyAOSP
Source Code: https://github.com/sonyxperiadev
ROM OS Version: Android 12
ROM Kernel: Linux 4.19.x
ROM Firmware Required: Latest Stock Firmware recommended
Based On: AOSP
Version Information
Status: BETA initial release
Current Beta Version: 12
Beta Release Date: 2021-30-12
Is this the same as this?
TrulyPain said:
Is this the same as this?
Click to expand...
Click to collapse
yes its exactly that
ada12 said:
yes its exactly that
Click to expand...
Click to collapse
Okay, thanks for fast answer.
Built it myself in october (AOSP 11), tried to flash it, but got stuck at sony logo and it bootlooped. Will try your tip @ada12 with flashing oem_a and oem_b. Am i right that i have to flash it that way:
fastboot flash oem_a (youroemfile).img
fastboot flash oem_b (youroemfile).img
Do you have any idea how to enable signature spoofing when building the rom? If i succed to do this, i'll build it in the future myself.
Hans Satt said:
Built it myself in october (AOSP 11), tried to flash it, but got stuck at sony logo and it bootlooped. Will try your tip @ada12 with flashing oem_a and oem_b. Am i right that i have to flash it that way:
fastboot flash oem_a (youroemfile).img
fastboot flash oem_b (youroemfile).img
Do you have any idea how to enable signature spoofing when building the rom? If i succed to do this, i'll build it in the future myself.
Click to expand...
Click to collapse
for enable signature spoofing need modify aosp sources ... - you can find patch easy from majority of reposity of custom rom ( pixel experience, ex ... )
I did build and deploy the aosp 11 (not 12) for this phone ok. However did anyone found a way to get the sony camera app on the phone?
The stock app is really basic...
I can also try to deploy the lineageOS version (if one exists) but does anyone know if it has a better camera app?
BTW, I can build aosp 12 but I did not find the sony blob for 12. On their site it is only for 11. Does the OEM 11 works with aosp 12?
Thanks,
M.
Hey, this worked however
I tried this myself and noticed I seem to head into a boot loop after rebooting some 5 times. I don't know what causes this, but I noticed it after trying to get gapps to work via magisk and randomly hit into a "Your device is corrupt" sony boot loop.
I tried without magisk/root, and noticed I hit the same issue after rebooting 5 times (just to see if it was rebooting in general causing this).
It fixes itself with data intact once I reflash the boot once again.
I'm stumped as to what causes this. Is it because I rebooted multiple times within half an hour? Is there something that can trigger the phone to think boot partition is corrupt?
Edit: It was one of the files I flashed from the Op's post, after I flashed everything to stock 167 EU firmware and only updated system.img with a bunch of GSI's (as I learnt they are a thing and damn perfect), I got it working. Guess something was incompatible between my device and the files attached.
Will you be keeping this up to date? How does it compare to GSI? I just want completely barebones degoogled rom.
Good on Sony for offering this up, that's amazing. And thank you OP for building it!
Anyone who is running it - does it have OTA updates? Or do you need to build and flash each time?
WaterMan! said:
Good on Sony for offering this up, that's amazing. And thank you OP for building it!
Anyone who is running it - does it have OTA updates? Or do you need to build and flash each time?
Click to expand...
Click to collapse
I will need rebuild in every update and user will need reflash all img ... december build have selinux permissive its worried me for security I will need modify sony sources for fix it
My phone just got bricked, lol. For the third time. By rebooting my phone. This piece of software has some bugs left. Also pro-tip for the future: Userdebug builds are often more buggy as they are not meant for production use.
Related
OrangeFox Recovery Project Treble
{
"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.
*
*/
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* @hpnightowl , @iamlordutkarsh , @dodyirawan85
* All our testers - for your patience and help
FEATURES:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM
* Flashlight
* Password, torch, led
* Support for Miui and 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!
INSTALLATION
1. Download the OrangeFox Imh to your device
2. Reboot to FastBoot
3. Install the OrangeFox Img !
4. Then Reboot To Recovery
5. Enjoy!
DOWNLOADS
Sources
KERNEL SOURCE
DEVICE TREE
Version Information
Status: Stable
Current Stable Version: R10.1_1
Stable Release Date: 2020-06-16
Is this custom recovery will work in realme ui android 10 stock and realme ui recovery?
D4RKC0RN3RS 0f ANDROID said:
Is this custom recovery will work in realme ui android 10 stock and realme ui recovery?
Click to expand...
Click to collapse
It wil work in Realme ui android 10 !
hello my smartphone realme 5i rmx2030 damaged boot.img please updowloand and send me
hello my smartphone realme 5i rmx2030 damaged boot.img please updowloand and send me link for download boot.img i am input the file using the fastboot in my realme 5i thanks for help
Not work
Bootloader unlocking
go to fastboot
fastboot flash recovery OrangeFox-Unofficial-RMX2030.img
I select the boot in recovery and the phone restarts in fastboot again.
What am I doing wrong?
You need to flash vbmeta!
To keep the Custom recovery you need to flash the vbmeta disabler for RUI through fastboot with proper command. I hope someone may help you!
ksinterphone said:
Bootloader unlocking
go to fastboot
....
What am I doing wrong?
Click to expand...
Click to collapse
the guide in it's current form doesn't work on RMX2030
@iamlordutkarsh. With all due respect the posted guide doesn't yield a positive result. The #4 item - Then Reboot To Recovery - boot the phone into fastboot again, after entering the command "fastboot reboot recovery". Any information on how to actually make it work would be really appreciated. I spent >6 hours trying everything I know and reading all the info I could find on XDA or Realme Telegram channel and now believe RMX2030 is not rootable at this point in time.
G0bl1n said:
@iamlordutkarsh. With all due respect the posted guide doesn't yield a positive result. The #4 item - Then Reboot To Recovery - boot the phone into fastboot again, after entering the command "fastboot reboot recovery". Any information on how to actually make it work would be really appreciated. I spent >6 hours trying everything I know and reading all the info I could find on XDA or Realme Telegram channel and now believe RMX2030 is not rootable at this point in time.
Click to expand...
Click to collapse
Sorry Sir ! lemme update Post
patched vbmeta
iamvijaypushparaj said:
To keep the Custom recovery you need to flash the vbmeta disabler for RUI through fastboot with proper command. I hope someone may help you!
Click to expand...
Click to collapse
do u have vbmeta.img for device if yes kindly share link here
Fine but,
raj2k8 said:
do u have vbmeta.img for device if yes kindly share link here
Click to expand...
Click to collapse
Before providing, I need to know "what vendor you're using?". If you're using Color os, flashing vbmeta is pretty simple. But, if you're in RUI vendor, scene is different. You've to do additional things even after flashing the vbmeta. If not it'll lead you to "Boot.img damaged!" One of the worst OS I've ever seen oof!
I'm strongly recommend you to use TWRP if you're in RUI vendor since Orange Fox facing some errors when flashing. And also for RUI it wasn't official if I'm right.
And one more thing Orange Fox is Official now for RMX2030, Color OS.
iamvijaypushparaj said:
Before providing, I need to know "what vendor you're using?". If you're using Color os, flashing vbmeta is pretty simple. But, if you're in RUI vendor, scene is different. You've to do additional things even after flashing the vbmeta. If not it'll lead you to "Boot.img damaged!" One of the worst OS I've ever seen oof!
I'm strongly recommend you to use TWRP if you're in RUI vendor since Orange Fox facing some errors when flashing. And also for RUI it wasn't official if I'm right.
And one more thing Orange Fox is Official now for RMX2030, Color OS.
Click to expand...
Click to collapse
I'm using Colour OS and would like the vbmeta please.
Is this 100% working for Realme 5i RMX2030?
Running on latest Realme UI at the moment.
I want to switch roms or at least root because free ram barely hits 1GB free -_-
hello?
I guess this is fake/incorrect then?
Yeah, I can't even get this to work on ColorOS. I did "fastboot flash recovery twrp.img" (I renamed the Orangefox file to make it easier) and if I select reboot to recovery on the phone it just boots back to fastboot mode and if I do fastboot reboot it just reboots normally.
Good Luck
doveman said:
I'm using Colour OS and would like the vbmeta please.
Click to expand...
Click to collapse
Sorry, I've been busy with personal things. And good luck!
Okay Before that... Make sure You're
• Unlocked your Bootloader (Necessary).
• Having the proper OrFox, TWRP or SHRP recovery for RMX2030 (Android Pie).
• Having the Pie vbmeta for RMX2030. (See Attachment)
• For additionally you need R5i Decrypt ZIP. (Optional)*
• Having ADB with Platform-tools & ADB driver installed on your PC.
• And I assume you know/read the proper command for flashing the recovery, vbmeta.
ATTACHMENTS: (Google Drive)
Vbmeta | 4KB
5i Decryption | 503KB
*Notes:
> Right after installing the Custom Recovery flash the Decryption zip if you wish.
> In case (it happens rare cases) If you're facing any problems like booting again and again into custom recovery that's because it may need Format Data. So, Format Data through the custom recovery can fix it permanently.
And one more thing I've not tested this OrFox myself. I hope I've been used other release of OrFox. Hope this one works perfectly. If not let me know, I'll maybe share what I've used.
---------- Post added at 03:48 AM ---------- Previous post was at 03:38 AM ----------
booterbotter said:
Is this 100% working for Realme 5i RMX2030?
Running on latest Realme UI at the moment.
I want to switch roms or at least root because free ram barely hits 1GB free -_-
Click to expand...
Click to collapse
Oh yes! When I was using colorOS I've been used OranageFox and TWRP as my recovery. Flashing ozip sometimes cause error. But, it's not a problem at all. You can fix it.
The thing is doing this properly that means if you follow the instructions, you'll be sure succeed. Otherwise may lead to soft brick or even hard.
And now I'm using RUI with TWRP, everything works fine. If you're wanted to switch back to ColorOS it's possible but, for that you sure need TWRP (recommended) and some knowledge to edit things inside the RMX2030 ColorOS ozip. The thing is installing Custom Recovery in RUI is tricky.
---------- Post added at 03:55 AM ---------- Previous post was at 03:48 AM ----------
G0bl1n said:
@iamlordutkarsh. With all due respect the posted guide ... now believe RMX2030 is not rootable at this point in time.
Click to expand...
Click to collapse
Sorry what, I forgot to reply you. I'm Using RMX2030 Rooted already (2 months with ColorOS + 1 month with RUI) and Many others too. Don't worry you'll get what you need.
iamvijaypushparaj said:
Sorry, I've been busy with personal things. And good luck!
Okay Before that... Make sure You're
• Unlocked your Bootloader (Necessary).
• Having the proper OrFox, TWRP or SHRP recovery for RMX2030 (Android Pie).
• Having the Pie vbmeta for RMX2030. (See Attachment)
• For additionally you need R5i Decrypt ZIP. (Optional)*
• Having ADB with Platform-tools & ADB driver installed on your PC.
• And I assume you know/read the proper command for flashing the recovery, vbmeta.
ATTACHMENTS: (Google Drive)
Vbmeta | 4KB
5i Decryption | 503KB
*Notes:
> Right after installing the Custom Recovery flash the Decryption zip if you wish.
> In case (it happens rare cases) If you're facing any problems like booting again and again into custom recovery that's because it may need Format Data. So, Format Data through the custom recovery can fix it permanently.
And one more thing I've not tested this OrFox myself. I hope I've been used other release of OrFox. Hope this one works perfectly. If not let me know, I'll maybe share what I've used.
Click to expand...
Click to collapse
Thanks for doing this but I still can't get the Custom Recovery to boot I'm afraid
I tried:
fastboot flash recovery ofox.img
fastboot flash vbmeta vbmeta.img
fastboot reboot bootloader
That booted back into fastboot and still shows "Secure Boot" and I selected "Recovery mode" but that just rebooted into fastboot.
Then I tried:
fastboot flash recovery ofox.img
fastboot --disable-verification flash vbmeta vbmeta.img
and selected "Recovery mode" on the phone but it just rebooted into fastboot.
Then I tried:
fastboot flash recovery ofox.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
and selected "Recovery mode" on the phone but again it just rebooted into fastboot.
I then tried the last set of commands with twrp instead of OrangeFox but still had the same result.
So I don't really know where I'm going wrong.
iamvijaypushparaj said:
Sorry, I've been busy with personal things. And good luck!
Okay Before that... Make sure You're
• Unlocked your Bootloader (Necessary).
• Having the proper OrFox, TWRP or SHRP recovery for RMX2030 (Android Pie).
• Having the Pie vbmeta for RMX2030. (See Attachment)
• For additionally you need R5i Decrypt ZIP. (Optional)*
• Having ADB with Platform-tools & ADB driver installed on your PC.
• And I assume you know/read the proper command for flashing the recovery, vbmeta.
ATTACHMENTS: (Google Drive)
Vbmeta | 4KB
5i Decryption | 503KB
*Notes:
> Right after installing the Custom Recovery flash the Decryption zip if you wish.
> In case (it happens rare cases) If you're facing any problems like booting again and again into custom recovery that's because it may need Format Data. So, Format Data through the custom recovery can fix it permanently.
And one more thing I've not tested this OrFox myself. I hope I've been used other release of OrFox. Hope this one works perfectly. If not let me know, I'll maybe share what I've used.
---------- Post added at 03:48 AM ---------- Previous post was at 03:38 AM ----------
Oh yes! When I was using colorOS I've been used OranageFox and TWRP as my recovery. Flashing ozip sometimes cause error. But, it's not a problem at all. You can fix it.
The thing is doing this properly that means if you follow the instructions, you'll be sure succeed. Otherwise may lead to soft brick or even hard.
And now I'm using RUI with TWRP, everything works fine. If you're wanted to switch back to ColorOS it's possible but, for that you sure need TWRP (recommended) and some knowledge to edit things inside the RMX2030 ColorOS ozip. The thing is installing Custom Recovery in RUI is tricky.
---------- Post added at 03:55 AM ---------- Previous post was at 03:48 AM ----------
Sorry what, I forgot to reply you. I'm Using RMX2030 Rooted already (2 months with ColorOS + 1 month with RUI) and Many others too. Don't worry you'll get what you need.
Click to expand...
Click to collapse
Can you please provide the realme 5i stock recovery (the one with the RUI)
nvm, can't unlock bootloader because realme themselves is not allowing it for Realme UI Android 10 at the moment.
So I can't even go back to android 9 stock rom realme 5i or do anything. Can't go to bootloader since their unlocking request is not yet open at the moment.
https://c.realme.com/in/board/detail/1215169823105875968
doveman said:
Thanks for doing this but I still can't get the Custom Recovery to boot I'm afraid
I tried:
fastboot flash recovery ofox.img
fastboot flash vbmeta vbmeta.img
fastboot reboot bootloader
That booted back into fastboot and still shows "Secure Boot" and I selected "Recovery mode" but that just rebooted into fastboot.
Then I tried:
fastboot flash recovery ofox.img
fastboot --disable-verification flash vbmeta vbmeta.img
and selected "Recovery mode" on the phone but it just rebooted into fastboot.
Then I tried:
fastboot flash recovery ofox.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
and selected "Recovery mode" on the phone but again it just rebooted into fastboot.
I then tried the last set of commands with twrp instead of OrangeFox but still had the same result.
So I don't really know where I'm going wrong.
Click to expand...
Click to collapse
that happened to me too so I only flash the reocovery and it works after selecting recovery in the phone luckily it boot's in recovery hope it helps
{
"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"
}
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28
2.3.x Gingerbread?
Just installed on my device, works great first try, only thing I've found to not work is Moto Audio with any sort of headphones, works with internal speaker tho. great work thanks!
googl-fi sofiap cannot flash to system
I am unable to flash to the system. It will not let me delete the super or system file. not sure what to do tried everything that is listed on the flash gsi. anyone with some help
lightningdude said:
2.3.x Gingerbread?
Click to expand...
Click to collapse
Typo, dude. F
rooted?
is this rom rooted?
vache said:
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28
Click to expand...
Click to collapse
stolirocks said:
is this rom rooted?
Click to expand...
Click to collapse
Nope.
Although not "rooted" you can root after installation just like you would with stock.
Thank you for the ROM. First time using OmniRom and loving it so far. I have not run into any issues so far. Even on t-mobile, my WiFi calling, visual voicemail and text messages all are working without any issues.
Will you be releasing a version with just MicroG instead of gApps? I ended up just uninstalling all the gApps anyways, but just curious.
Keep up the great work!
GApps Dilemma
I am really looking forward to not having Gapps on this device, I haven't installed yet due to this, and wonder. Is this OpenGApps implentation removable using the same instructions as if it were installed manually after the CFW was flashed? Also, if it is not too much extra work, could you post a non GApps build?
Thanks for the hard work!
griz.droidx said:
Although not "rooted" you can root after installation just like you would with stock.
Click to expand...
Click to collapse
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?
.Solotato said:
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?
Click to expand...
Click to collapse
Greetings Solotato and Moto/Android community ,
I know this post is long excessively but hopefully it'll get the point across. Please don't think I'm talking down to you or anyone else. This whole process had me baffled at first as well and I've used others work to root and rom fur years. I've used Linux on the desktop by dual and even triple booting (Nix,Xpor2K, and 98 for old hardware slash gaming support) I even wrote a config for a guy's app called js2mouse to use 2 pointers at the same time in X(wanted to use my old logitech wingman cordless as a remote. But I'm no expert and still consider myself a little above novice. This isn't meant to offend anyone. Shew (the us is just too politically correct)
You can use twrp i think with magisk. BUT...im pretty sure i flashed twrp once in the recovery bootloader before but nothing else would take and twrp didn't function correctly.
I agree with many others now that it's easier to put a copy of the boot image on your device after installation. It's simple really
Just boot your device,
Enable developer options first thing then adb, then you can connect with a usb cable and approve adb access in your phone.
Copy the boot image to your phone and use the latest official magisk to patch the boot image. In magisk pick install then pick image, you pick your boot image which is then patched and renamed magisk_patched or similar.
It'll be in your downloads folder. Move it back to your pc, the patched one of course, and then just
fastboot flash boot magisk_patched.img
A TIP if you're new to the command line/powershell(win) or terminal(nix/bsd/mac (which is based on bsd)You can even use the up arrow if you dunt want to retype the commands then just replace boot.img with magisk_patched.img just start typing magis then hit tab and it'll complete it for you..
All this looks complicated but trust me after you do it a few times you'll be doing it in a minute or two.
Good luck take your time and read everything you can find. Don't forget to ask the command line for --help! You can find help in a jiffy that way.
Example
fastboot --help i think is the syntax i can't see it on my phone but there's a space between the two dashes and the command your asking for help. And for more details help is included in Linux with man pages. Those are handy in a pinch.
Even though I've done this since the droidx days on many phones, it still took me a lot of research and reading to get this new a/b partitioning and fastboot stuff down to where i can do it quickly.
Read and search these threads you'll be more likely to get answerers from xda members if they can tell you've been reading up on it.
Good luck!
Practice practice practice. That's the advice my uncle gave me on shooting a bow (instinctive or without sights) and he was right. This applies to everything in life.
Anyway I've preached enough. I know it's a long post but hopefully you and others who are relatively new to these moto's will get some help here.
Don't forget to thank the developers and others who made all this coolness possible for us who benefit from
If i helped any at all or you enjoyed my way too many useless details style, please hit thanks. I appreciate that. Sorry for the delay in posting I'm still setting up my most recent rom and I've doing a lot of stuff outside my home before winter.
Sent from my Moto G Stylus using XDA Labs
Sorry guys that was waaaaay too long.
Sent from my Moto G Stylus using XDA Labs
Could anyone point me in the right direction for recompiling this rom's kernel with a different config? I'm looking to poke around & try to get USB OTG/ACA mode to work (i.e. have the phone charge as well as use a usb device, like a mouse/keyboard/storage), which is apparently possible by setting CONFIG_USB_MSM_OTG and CONFIG_USB_MSM_ACA.
I've never compiled a kernel for another arch before, and I assume I need a toolchain that targets arm64 to begin with - I've also never really built anything for android before, and all the guides I've found thus far seem to either be for a specific device or building an entire system image, which seems to be too much - I'm given to understand I can replace the kernel image in boot.img by itself with a tool like mkbootimg.
Any help with where to start would be appreciated, thanks!
My Screen isn't working anymore... using an OTG to move around....
It's the touch screen
Another user asked this previously without any response ... Could you post a degoogled Omni ROM without gapps? Or give any advice how to remove it ? You were the one to put it all together so surely for you it must be easy removing it? As for me, I've been stuck.
Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?
ianspy1 said:
Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?
Click to expand...
Click to collapse
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ?
gatorz_4z said:
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ? My hope is that with that version you will be successful? Another person told me to redownload the ROM and try with a fresh one.
Click to expand...
Click to collapse
Gotta love how unsupported this ROM is... Or just busy dev...
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
Source Code
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:
https://t.me/xda_tv
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:
GCAM Issue
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 -w (Wipes your internal storage and the userdata)
Now you got the AOSP recovery, to please continue with the normal installation
fastboot flash oem_a oem_*.img (Only needed until the device receives mainline support by SODP)
fastboot flash vendor vendor.img
fastboot flash system system.img
News
06.08.2022
End of life. Moved to Android 13.
Click to expand...
Click to collapse
23.07.2022
android-12.1.0_r11 (July security patchlevel)
Click to expand...
Click to collapse
20.06.2022
ftp and android filehost server are fixed
Click to expand...
Click to collapse
13.06.2022
android-12.1.0_r7 (June security patchlevel)
OEMv2a support
Click to expand...
Click to collapse
Because of problems with the ftp server the new release is on google drive.
Click to expand...
Click to collapse
20.05.2022
android-12.1.0_r5 (May security patchlevel)
Click to expand...
Click to collapse
Because of problems with the ftp server the new release is on google drive.
Click to expand...
Click to collapse
12.04.2022
android-12.1.0_r3 (April security patchlevel)
Click to expand...
Click to collapse
30.03.2022
android-12.1.0_r1 (March security patchlevel)
Click to expand...
Click to collapse
14.02.2022
hotfix for the bootloop
Click to expand...
Click to collapse
09.02.2022
android-12.0.0_r28 (February security patchlevel)
OEMv1c support
Click to expand...
Click to collapse
Hi,
thank you very much for bringing up AOSP for the XZ2 series. That is awesome!
I just installed on a XZ2c coming from clean stock 52.1.A.3.49.
fastboot commands works fine but on reboot I encounter bootloop.
'adb logcat -b all' does not give me any output.
Any ideas how to further debug?
It seems not bootable for xz3 dual. I cannot see sony logo after the bootloader.
I flash boot_a, dtbo, oem_a&b, vbmeta, vendor, system_a and clean user data after flashing stock rom.
Same here xz2c dual,
I can see, barely though, the Sony logo. It is very dim, far from its usual full brightness stage. I don't know if that gives you any indication of when the problem occurs...
Code:
fastboot --set-active=a
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot -w
fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot flash vendor vendor.img
fastboot flash system system.img
(same for slot b)
Let me know if there is any command you would like me to run. I cannot seem to reach adb for the logcat :/
I also would like to thank you @MartinX3 , your work is appreciated!
Thank you, guy, for testing
Please open an issue ticket, I only own the xz2
Very happy to also support sony xz3
H9493Can't use
Issue #748
Thank you for creating the issue ticket.
This will fix the decryption bug later.
Any TWRP builds which would suit this ROM? If so, how to boot into them? You see, I want to install a gapps package. I`ve tried Nikgapps, but the builtin recovery complained that there is no META-INF/com/android/metadata, thus failed to install it. I`ve tried both booting and installing some recovery builds through fastboot. Booting simply leads to system coming up. As there is no FOTAKernel, nor recovery partitions, I`ve tried to flash them to the boot partition, but that leaded to a boot loop. Any thoughts?
Hi, does this rom support 120hz screen?
casouzaj said:
Any TWRP builds which would suit this ROM? If so, how to boot into them? You see, I want to install a gapps package. I`ve tried Nikgapps, but the builtin recovery complained that there is no META-INF/com/android/metadata, thus failed to install it. I`ve tried both booting and installing some recovery builds through fastboot. Booting simply leads to system coming up. As there is no FOTAKernel, nor recovery partitions, I`ve tried to flash them to the boot partition, but that leaded to a boot loop. Any thoughts?
Click to expand...
Click to collapse
Firstly the encryption of the AOSP ROM needs to get fixed.
Then the TWRP needs to get recreated from scratch with an android 12 base.
Android 12 changed the encryption and the old Android 9 doesn't compile anymore on modern Linux systems.
But it will be slow, I'm alone and have a busy life.
il.lurask said:
Hi, does this rom support 120hz screen?
Click to expand...
Click to collapse
No. If it gets added into the SODP project, this ROM will support it.
But it gets only added if there are any benefits and no long-term hardware degradations.
il.lurask said:
Hi, does this rom support 120hz screen?
Click to expand...
Click to collapse
What does the XZ2 have a 120HZ screen mode or are you talking about the XZ2 Premium?
BrandonMCMFG said:
What does the XZ2 have a 120HZ screen mode or are you talking about the XZ2 Premium?
Click to expand...
Click to collapse
Just the screen hardware might support it.
14.02.2022
hotfix for the bootloop
Click to expand...
Click to collapse
MartinX3 said:
14.02.2022
Click to expand...
Click to collapse
Thanks.
Btw, Gcam works?
landsome said:
Thanks.
Btw, Gcam works?
Click to expand...
Click to collapse
You're welcome.
Please report issues into the linked gcam issue ticket.
It does not boot yet here, however the change did improve things, I see the Sony logo much longer and with full brightness. Still no logs...
Can someone with apollo confirm this?
EDIT: Do I need to do something with userdata.img? I wiped the device with fastboot -w, and the instructions don't mention that file.
Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.
I have found that resizing GSI system partition could help flash gapps via Ex Kernel Manager directly from the phone.
My big question is if you can resize GSI system partition without TWRP? since Note 2021 does not support recovery, if yes how?
Or can you actually set bigger system partition than system image with this command ? --el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
(following manual steps for gsi installation)
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
what would be number for 20GB size in this command? --el KEY_USERDATA_SIZE 8589934592 how i can write it correctly?
i have enough space to assign big userdata partition.
CyraxMD said:
Is there any fix for this problem? I wish to have phone rooted AND use GSI
Click to expand...
Click to collapse
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..
vegan_monk said:
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..
Click to expand...
Click to collapse
was not neccessary, check this guide which i maked how to do it:
CyraxMD said:
was not neccessary, check this guide which i maked how to do it:
Click to expand...
Click to collapse
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.
vegan_monk said:
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.
Click to expand...
Click to collapse
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.
CyraxMD said:
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.
Click to expand...
Click to collapse
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8
vegan_monk said:
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8
Click to expand...
Click to collapse
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too
CyraxMD said:
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too
Click to expand...
Click to collapse
sorry to disappoint u mate but its just the miui recovery
GSI has better performance than MIUI? Could you tell the pros and cons that you have found?
CyraxMD said:
Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.
Click to expand...
Click to collapse
After seeing your video I understand that you was able to fix your initial problem:
"The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted."
It seem that you have been able to fix that problem, havent you? Have you had any problem using rooted GSI lineage? I am very insterested in rooting my phone using a GSI rom. I am going to follow your tutorial.
thanks
Android 13 for Xperia XZ Premium
Code:
/*
* Your warranty is now void.
* I am 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 me for messing up your device, I will laugh at you.
*/
What's AOSP?
AOSP is Android as Google publish without any modifications. .
What's working :
Boots
Bluetooth
Fingerprint
Wi-Fi
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
Encryption
Offline Charging
Whats not working?
Notification LED
IMS/VOLTE
Half Screen issue(For some users) - Need testing if still persist
Test and Report(with logcat)
Instructions to install up ROM :
Flash latest available Stock ROM(47.2.A.10.107) and boot into it once.
Reboot to Fastboot
Download the OEM Image from HERE, Extract and Flash it. (V5B)
fastboot flash oem SW_binaries_for_Xperia_Android_11_4.14_v5b_yoshino.img
Flash the userdata,boot and system image (Will wipe all the userdata).
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash system system.img
Install Magisk/Gapps(Optional).
Reboot
Downloads :
G8142 : https://sourceforge.net/projects/xzp/files/SODP13/android-13.0.0_r2/G8142/
G8141 : https://sourceforge.net/projects/xzp/files/SODP13/android-13.0.0_r2/G8141/
Kernel Source Code: https://github.com/sonyxperiadev/kernel
Changelog :
08/18/2022 :
Initial release for G8142
08/19/2022:
Initial release for G8141
08/22/2022
Notification LED Fixed
Switched to custom lights hal
Kernel upstreamed to 4.14.260
Good
support gcam?
Markutthel said:
support gcam?
Click to expand...
Click to collapse
It does, you need to find the compatible one.
Shujath said:
It does, you need to find the compatible one.
Click to expand...
Click to collapse
okeyy thx my bruhh
mmmmm,how to raw support?
ooh, brilliant. Unfortunately I have single SIM/8184.
I still have to wait. I am really happy about it.
Can you provide GAAPs and TWRP recovery? Link?
Gordon1979 said:
ooh, brilliant. Unfortunately I have single SIM/8184.
I still have to wait. I am really happy about it.
Can you provide GAAPs and TWRP recovery? Link?
Click to expand...
Click to collapse
Mostly tomorrow, I will share the single sim versions.
Sure, will share the links and steps to install gapps too ..
Great work!
Alright, Links for Single sim variant are up.
Steps to install GAPPS :
Install the attached recovery via fastboot
fastboot flash recovery recovery.img
Boot into recovery mode by pressing and holding power button and volume down button at the same time.
Sideload the gapps or install it from SD card as it cannot decrypt the internal storage yet.
I am using Litegapps (https://sourceforge.net/projects/litegapps/files/litegapps/arm64/33/lite/v2.6/) (Recovery version).
Flash the Gapps and the attached fix for gapps(REQUIRED).
Reboot
other GAAPs for Android 13 cannot be found.
Or does GAAPs for Android 12L work too ?
Gordon1979 said:
other GAAPs for Android 13 cannot be found.
Or does GAAPs for Android 12L work too ?
Click to expand...
Click to collapse
Litegapps are the only one I found currently.
a13 is very in very early stage and other gapps will adapt to it soon.
Do you know if it is possible to install GAAPs12 on Android 13?
Gordon1979 said:
Do you know if it is possible to install GAAPs12 on Android 13?
Click to expand...
Click to collapse
I dont think so....
Litegapps 14, is this for Android 14???
LiteGapps - Browse /litegapps/arm64/34/lite/v2.6 at SourceForge.net
LiteGapps is a custom gapps which is ,small, friendly and complete.
sourceforge.net
Gordon1979 said:
Litegapps 14, is this for Android 14???
LiteGapps - Browse /litegapps/arm64/34/lite/v2.6 at SourceForge.net
LiteGapps is a custom gapps which is ,small, friendly and complete.
sourceforge.net
Click to expand...
Click to collapse
Yes lol :d
@Shujath
After the install, no recovery comes from the device.
Factory reset not possible
I can't restore my APPs, SMS, ..... everything.
Can you remove the search bar on the homescreen?
The display on/off in seconds cycle is also there.
how to flash i don't understand
Flash latest available Stock ROM(47.2.A.10.107) and boot into it once.
Reboot to Fastboot
fastboot flash oem SW_binaries_for_Xperia_Android_11_4.14_v5b_yoshino.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
Boot into recovery mode by pressing and holding power button and volume down button at the same time.
go in to Sideload
flash over PC , Litegapps
Flash the Litegapps fix over TWRP
Reboot
ROM Updated :
22nd Aug'22
Changelog :
Notification LED Fixed
Switched to custom lights hal
Kernel upstreamed to 4.14.260
Download links in first post.