Develop Bugs

[SHARE] Official TWRP 3.4.0-0 for woods MediaTek (Updated)

. The full changelog
5G
OnePlus 6T
Win a Mi 9
Honor View20
Honor Hub
Android Q
Galaxy Note 9
LG V40
Snapdragon 855
Pixel 3
TWRP 3.3.1+ will no longer require installer ZIPs, adds a reboot to EDL mode button, and more
TWRP 3.3.1+ will no longer require installer ZIPs, adds a reboot to EDL mode button, and more
For most users, installing any kind of after-market software modification, whether it be a custom ROM, custom kernel, or other tool, requires the use of a custom recovery like TWRP. TWRP has been around for years as the go-to recovery solution for the XDA community. It’s open source and supports hundreds of devices. It offers features like full backup and restore, ADB sideloading, and much more. Today, the project has been bumped to version 3.3.1-0, bringing many improvements in decryption, new features, and a major change to the way TWRP is installed.
The full changelog outlining the many improvements in TWRP’s decryption support can be found below, but for users, the most important change will be the new way to install the custom recovery. Currently, installing TWRP on a device with A/B partitions requires booting TWRP temporarily and then installing it permanently using an installer script. Going forward, users will be presented with a new “install recovery ramdisk” option in recovery. This means that users can boot TWRP and then install it without downloading a separate ZIP file. XDA Senior Recognized Developer Dees_Troy worked with XDA Recognized Developer topjohnwu to make this possible by adapting Magisk‘s boot image patching for TWRP. Dees_Troy says the team will offer installer ZIPs this time around to give people a chance to update from older versions, but future TWRP releases won’t have separate installer scripts.
The other change that’s most relevant to users is the inclusion of a “reboot to EDL mode” button. Emergency Download mode can help you fully unbrick a device if you have the right tool, but the button combination to enter it isn’t as well known to users as the reboot to recovery method.
Here’s the full changelog for the update:
TWRP 3.4.0-0 Changelog
Merge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (CaptainThrowback and nijel8)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP
Developers behind (Dees_Troy with thanks to topjohnwu of course)
Directory Access
https://eu.dl.twrp.me/woods/
https://eu.dl.twrp.me/woods/twrp-3.4.0-0-woods.img
Fair warning don't restore previous backups from other versions of TWRP make a fresh one first[/SIZE]
:good:

Finally,a dev to keep woods alive

Well done good job sir. We support you. Contribute to moto e4 more.

Does it support the official OTA updates?

nabirosama said:
Does it support the official OTA updates?
Click to expand...
Click to collapse
Yes if your previous version is. From official channel

Abish4 said:
Yes it your previous version is. From official channel
Click to expand...
Click to collapse
On my device it is Software Channel "reteu", should be supported?
The original patch level is on my device october 2018, i think we can not expect updates from the manufacturer any longer.

I unlocked my phone, but fastboot boot twrp-3.3.1-0-woods.img is not booting into recovery. After entering the command in fastboot mode, the device is just restarting.
(Device unlocked message appears, so this should not be a problem.)
Source:
https://dl.twrp.me/woods/twrp-3.3.1-0-woods.img
fastboot boot twrp-3.3.1-0-woods.img
downloading 'boot.img'...
OKAY [ 0.509s]
booting...
OKAY [ 0.068s]
finished. total time: 0.577s
Click to expand...
Click to collapse
I need to make a full backup before flashing. Is this twrp not working with fastboot boot ... ?
Device Moto E4, woods, XT1762

I never try to boot TWRP with fastboot.I always flash it and everything is good. If you need a backup of the recovery partion, you can do that via adb. Everthing else can be backup'ed by TWRP.
Spielmops

Spielmops said:
I never try to boot TWRP with fastboot.I always flash it and everything is good. If you need a backup of the recovery partion, you can do that via adb. Everthing else can be backup'ed by TWRP.
Spielmops
Click to expand...
Click to collapse
The recovery backup would be some kind of a fail save, if twrp will not boot. If the direct boot would work, I had more faith. :fingers-crossed:
How can I backup the recovery over adb?
I found this:
https://android.stackexchange.com/questions/132314/can-we-backup-the-stock-recovery-img-in-any-way
But I still need root and I can not flash magisk without twrp (and system backup).
Update:
However, because it is working by others, i tried flash recovery twrp-3.3.1-0-woods.img (official), it seems to work.
Creating full backup now ...

Have a look here: https://android.stackexchange.com/questions/205354/show-adb-backup-manual

hi, I have the same problem (XT1761), any idea? thank you
maven33 said:
I unlocked my phone, but fastboot boot twrp-3.3.1-0-woods.img is not booting into recovery. After entering the command in fastboot mode, the device is just restarting.
(Device unlocked message appears, so this should not be a problem.)
Source:
https://dl.twrp.me/woods/twrp-3.3.1-0-woods.img
I need to make a full backup before flashing. Is this twrp not working with fastboot boot ... ?
Device Moto E4, woods, XT1762
Click to expand...
Click to collapse

hi, I have the same problem (XT1761), any idea? thank you
Click to expand...
Click to collapse
hi, I have the same advice ...
Spielmops

hi, solved (even if I don't know why)...
extracted "boot.img" from "[ROM][STOCK][TWRP] Original Stock Firmware-(woods) - TWRP Restore [ROOTED]"
boot.img link https://mega.nz/#!I9cSQC7D!44B_MFvW1wwB3VSF09P1C4-82dqY2i21INNVICFajac
and flashed it
fastboot flash boot boot.img
THEN flashed recovery (I used twrp-3.3.1-0-woods.img, but no matter what you use)
fastboot flash recovery twrp.img
NOW I am working recovery and just flashed a custom rom
Spielmops said:
hi, I have the same advice ...
Spielmops
Click to expand...
Click to collapse

hitman72 said:
hi, solved (even if I don't know why)...
NOW I am working recovery and just flashed a custom rom
Click to expand...
Click to collapse
Did you even try to disable verified boot ?
cause thats the almost every time with boot images on newer or updated devices..

The bootloader was unlocked in by activating USB-debugging, EOM-Unlock in the developer settings. In fastboot mode , only "fastboot oem unlock".
I used the twrp-3.3.1-0-woods.img on my Moto E4 (XT1762) woods. This version worked, but I could not start twrp without a flashing it.

dm verity disable
maven33 said:
I used the twrp-3.3.1-0-woods.img on my Moto E4 (XT1762) woods. This version worked, but I could not start twrp without a flashing it.
Click to expand...
Click to collapse
If you are moving from stock rom and locked device u need to unlock with official key or you can just format your device data... DMVERITY must be disabled at all cost or you have to flash entire stock software update to be running.
See or check post relating to disabling verity in FASTBOOT mode (probably zip) also reboot recovery after flashing.
:fingers-crossed:

hitman72 said:
hi, solved (even if I don't know why)...
extracted "boot.img" from "[ROM][STOCK][TWRP] Original Stock Firmware-(woods) - TWRP Restore [ROOTED]"
boot.img link https://mega.nz/#!I9cSQC7D!44B_MFvW1wwB3VSF09P1C4-82dqY2i21INNVICFajac
and flashed it
fastboot flash boot boot.img
THEN flashed recovery (I used twrp-3.3.1-0-woods.img, but no matter what you use)
fastboot flash recovery twrp.img
NOW I am working recovery and just flashed a custom rom
Click to expand...
Click to collapse
The mega link isn't working. Can you please update the link to the file.

[TWRP][RMX2030] OrangeFox Recovery Project [Realme 5i][Unofficial]

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

Development [ROM] AOSP 12 - SODP [12.0.0_r16]

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.

Question GSI wont boot after rooting phone - Xiaomi Redmi Note 8 (2021)

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

[ROM] AOSP 13 - SODP [13.0.0_r2]

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.