[RECOVERY][DISCONTINUED] TWRP 3.5.0_9-0 [I9300] - Galaxy S III Original Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Code:
* [B][U]Your warranty is now void.[/U][/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Odin
- Odin3 v3.13.3
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy S III (International Exynos)
How to flash TWRP with Odin​1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down, and Home buttons simultaneously. When the blue screen appears, release all 3 buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP" and press the "Start" button.
3. Pull the battery as soon as your phone vibrates.
4. You can then boot directly into TWRP by pressing the Power, Volume Up, and Home buttons simultaneously. Release all three buttons as soon as you see the boot screen ("Samsung Galaxy S III").
How to flash TWRP within a previous version of TWRP​1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power, Volume Up, and Home buttons simultaneously. Release all 3 buttons when the boot screen appears ("Samsung Galaxy S III").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Changelog
- See post #2.
Bugs
- You tell me!
Credits
- Option58, rgib, stek-kravari, and every other open source developer and user who contributes directly or indirectly to the TWRP community in the development of and in providing feedback for the i9300.
Sources
- Option58
- rgib
- i9300 repository
- TWRP repository
XDA:DevDB Information
TWRP 3.5.0_9-0, ROM for the Samsung Galaxy S III I9300
Contributors
ripee
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 3.5.0_9-0
Stable Release Date: 2020-12-28
Created 2019-12-22
Last Updated 2022-12-09

Reserved

Reserved

Official Preview Build!
Bigbiff has run a preview build with TeamWin's builder: https://build.twrp.me/twrp-3.3.1-0-i9300.img
Please compare this one to the one linked in the OP.

Wasn't i9300 already supported by offcial twrp?

theandroid02 said:
Wasn't i9300 already supported by offcial twrp?
Click to expand...
Click to collapse
The original official 3.3.1-0 was built from an old source branch that was a modified rom source. It was pulled because it didn't work.
I adapted my pure i9305 twrp source branch for i9300. My 3.3.1-0 build is confirmed to be working. Once enough users test it, I will tell bigbiff at TeamWin to run a production build, ie. to make it official.

ripee said:
Official Preview Build!
Bigbiff has run a preview build with TeamWin's builder: https://build.twrp.me/twrp-3.3.1-0-i9300.img
Please compare this one to the one linked in the OP.
Click to expand...
Click to collapse
i confirmed that this one is stable in my s3 i9300. i use this recovery now. :good:

Changelog
OP link has been updated with the new official 3.3.1-0 build on TeamWin's page.

Updated to twrp-3.3.1-0-i9300.img and got this error when installing this rom [ROM][UNOFFICIAL][9.0.0] LineageOS 16.0 [BETA][3.12.2020]
"Failed to map file (Directory/Filename such and such) Error installing zip file (Directory/Filename such and such)
Re-installed twrp-3.2.3-0-i9300.img and rom [ROM][UNOFFICIAL][9.0.0] LineageOS 16.0 [BETA][3.12.2020] installed fine.

mbdroidsony said:
Updated to twrp-3.3.1-0-i9300.img and got this error when installing this rom [ROM][UNOFFICIAL][9.0.0] LineageOS 16.0 [BETA][3.12.2020]
"Failed to map file (Directory/Filename such and such) Error installing zip file (Directory/Filename such and such)
Re-installed twrp-3.2.3-0-i9300.img and rom [ROM][UNOFFICIAL][9.0.0] LineageOS 16.0 [BETA][3.12.2020] installed fine.
Click to expand...
Click to collapse
That's because 3.2.3 was built from a modified rom source, whereas 3.3.1 is built from a pure twrp source. In order to make the switch, please delete the hidden twrp settings file in the TWRP folder in your internal storage. If that doesn't help, I'm afraid the only way to move forward is to wipe Data first, then all the other partitions, except internal storage, and flash again.
This issue appears often when going from a twrp built from a rom source, which is the dirty way of doing it, to one that is made from a dedicated source. If you don't want to go through the hassle of clean flashing, 3.2.3 will work well for you until and unless Q or a future version is developed for i9300 that will no longer be compatible with 3.2.3.

ripee said:
That's because 3.2.3 was built from a modified rom source, whereas 3.3.1 is built from a pure twrp source. In order to make the switch, please delete the hidden twrp settings file in the TWRP folder in your internal storage. If that doesn't help, I'm afraid the only way to move forward is to wipe Data first, then all the other partitions, except internal storage, and flash again.
This issue appears often when going from a twrp built from a rom source, which is the dirty way of doing it, to one that is made from a dedicated source. If you don't want to go through the hassle of clean flashing, 3.2.3 will work well for you until and unless Q or a future version is developed for i9300 that will no longer be compatible with 3.2.3.
Click to expand...
Click to collapse
Good to know, thanks

On version 3.3.1.0 there problems, when I click "wipe data" appears "E: Unable to decrypte FBE device". And nothing is installed, it gives an error.
I did a full reset, nothing helped, returned 3.2.3

Robert\ said:
On version 3.3.1.0 there problems, when I click "wipe data" appears "E: Unable to decrypte FBE device". And nothing is installed, it gives an error.
I did a full reset, nothing helped, returned 3.2.3
Click to expand...
Click to collapse
Encryption is removed by formatting data partition.

kurtn said:
Encryption is removed by formatting data partition.
Click to expand...
Click to collapse
I did (Advanced wipe) all sections, and (Format Data) this does not help, he still writes (E: Unable to decrypte FBE device), and when I click install something, it gives an error.

Help me out here, i installed this, and it no longer asks for password, and i can't mount the data partition. clicking mount just results in nothing

postafoa said:
Help me out here, i installed this, and it no longer asks for password, and i can't mount the data partition. clicking mount just results in nothing
Click to expand...
Click to collapse
Is there data of value? If not, simply format data.

nothing of value, i just need to flash some ROM and gapps pico so i can download an app from google play that is necessary for KYC/AML hell
I hate the bankers, and i hate google, and it's amazing how this one private american company has all the data of all the people on earth and nobody is allowed to even buy food without a damn google account. This is a nightmare
---------- Post added at 20:59 ---------- Previous post was at 20:57 ----------
anything i do in recovery just results in 'failed to mount'
---------- Post added at 21:00 ---------- Previous post was at 20:59 ----------
failed to mount /data (invalid argument)
no matter what i do
---------- Post added at 21:02 ---------- Previous post was at 21:00 ----------
unable to format to remove encryption

postafoa said:
nothing of value, i just need to flash some ROM and gapps pico so i can download an app from google play that is necessary for KYC/AML hell
I hate the bankers, and i hate google, and it's amazing how this one private american company has all the data of all the people on earth and nobody is allowed to even buy food without a damn google account. This is a nightmare
---------- Post added at 20:59 ---------- Previous post was at 20:57 ----------
anything i do in recovery just results in 'failed to mount'
---------- Post added at 21:00 ---------- Previous post was at 20:59 ----------
failed to mount /data (invalid argument)
no matter what i do
Click to expand...
Click to collapse
Next steps:
1 try older twrp / custom recovery
2 flash stock ROM

i tried installing older twrp, same thing, it can't do anything
funny thing is i can boot the system etc
---------- Post added at 21:11 ---------- Previous post was at 21:09 ----------
i'm ready to grind this phone into dust, i just need to use it for gapps pico one time tonight
but i had to go installing this TWRP, and now i can't do anything at all
---------- Post added at 21:24 ---------- Previous post was at 21:11 ----------
failed to map file gapps.zip etc etc
everything is wiped, formatted, repaired, factory resetted
---------- Post added at 21:25 ---------- Previous post was at 21:24 ----------
why did i have to install this twrp..

postafoa said:
i tried installing older twrp, same thing, it can't do anything
funny thing is i can boot the system etc
---------- Post added at 21:11 ---------- Previous post was at 21:09 ----------
i'm ready to grind this phone into dust, i just need to use it for gapps pico one time tonight
but i had to go installing this TWRP, and now i can't do anything at all
---------- Post added at 21:24 ---------- Previous post was at 21:11 ----------
failed to map file gapps.zip etc etc
everything is wiped, formatted, repaired, factory resetted
---------- Post added at 21:25 ---------- Previous post was at 21:24 ----------
why did i have to install this twrp..
Click to expand...
Click to collapse
I hope you have a PC for Odin or heimdall

Related

[MOD] MultiROM v33b

Introduction
{
"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"
}
MultiROM is one-of-a-kind multi-boot mod for Oneplus One. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
You can install it either from MultiROM Manager app or from this guide:
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM - download the ZIP file from second post and flash it in recovery.
Modified recovery - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.​
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.​
3. Firefox OS
Firefox OS is just another Android ROM from MultiROM's point of view, so add it as if it were Android​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/KINGbabasula/android_kernel_oneplus_msm8974
MultiROM device tree - https://github.com/KINGbabasula/android_device_oneplus_bacon​
Thanks a lot to Tasssadar for creating this awesome utility.
Thanks to ATMOSF3AR for his Oneplus One template
XDA:DevDB Information
MultiROM, Tool/Utility for the OnePlus One
Contributors
KINGbabasula
Source Code: https://github.com/Tasssadar/multirom
Version Information
Status: Stable
Current Stable Version: 33
Created 2014-08-02
Last Updated 2016-04-17
Reserved
Downloads
1. Main downloads
MultiROM: Zip
Modified recovery (based on TWRP): recovery.img
Kernel with kexec hardboot patch:
Supported kernels: AK, Furnace
You need to have kernel with kexec-hardboot patch only in primary ROM
Nicely ask your kernel developer to merge this https://github.com/KINGbabasula/and...mmit/af5ef3d76f863f02c51cf860702b01536620ebf5.​
3. Uninstaller
MultiROM uninstaller: Zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.​
Reserved
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.​
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.​
Where can I find files from other ROMs?
http://forum.xda-developers.com/showpost.php?p=58563378&postcount=1864​
Can I have different versions of Android working alongside? How to use KitKat and Lollipop at the same time?
Yes. The systems are separated.
guide on Kitakt + Lollipop: http://forum.xda-developers.com/one...ips-tricks-t3027926/post58776196#post58776196​
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.​
The boot animation shows after a few seconds on primary ROMs, why?
Because the framebuffer gets blanked for a few seconds after it gets closed by MultiROM.​
Can I use MultiROM without root?
Yes, if you don't use MultiROM Manager app but flash everything manually​
Will I get OTAs when I have MultiROM installed? Do I lose secondary ROMs after an OTA?
Probably not, you will have to install them manually and you'll have to reinstall MultiROM
No, you won't lose secondary ROMs​
My secondary ROM doesn't boot, what should I do?
Probably you forgot to inject current boot sector once, MultiROM didn't run, so /data SELinux context is set to secondary ROMs that are in /data/media so secondary /system has /data contexts.
Go into recovery Advanced > MultiROM > List ROMs > Choose the non booting ROM > Run restorecon
This will fix SELinux contexts and the ROM will boot again​
Help Videos
Install MultiROM
Install OxygenOS as secondary ROM
Amazing, thank you bro!
Amazing! Reserved for impressions!
Woot !!!!!!! Donation incoming, as promised
Also, what kernel is yours based on ?
And finally, is it compatible with official multirom manager ?
Edit : Donation done : 2D0766769R4457313
bud77 said:
Woot !!!!!!! Donation incoming, as promised
Also, what kernel is yours based on ?
And finally, is it compatible with official multirom manager ?
Click to expand...
Click to collapse
My kernel is cm11 (not cm11s)with kexec. So it won't work on cm11s, Paranoid android and cm11s based roms.
Tomorrow is the last time I'll use pc before leaving so I may add support in multirom manager and build an unofficial version of the app because it's not officially supported
Thanks, again !
Did you try to get in touch with @Tasssadar for the frame buffer issue ?
bud77 said:
Thanks, again !
Did you try to get in touch with @Tasssadar for the frame buffer issue ?
Click to expand...
Click to collapse
I tried on hangouts but I guess he doesn't use it. I think I should port a few things from TWRP into MultiROM because it seems they use the same way of rendering images.
Thank you very much for your efforts,
That is really nice to have, am looking forward to use it. If the Multirom Manager app is usable here, will it be possible to install Ubuntu Touch or has it first to be ported to this phone? Just asking because I always wanted to try out Ubuntu...
dansou901 said:
That is really nice to have, am looking forward to use it. If the Multirom Manager app is usable here, will it be possible to install Ubuntu Touch or has it first to be ported to this phone? Just asking because I always wanted to try out Ubuntu...
Click to expand...
Click to collapse
First we need a working ubuntu touch port. I don't think it will be too hard to do. The opo is very similar to nexus 5
nfl46 said:
Anyone got everything up and running yet? Attempting to install MR now.
Click to expand...
Click to collapse
I'm just about to start doing this...
---------- Post added at 04:32 PM ---------- Previous post was at 04:12 PM ----------
OK, multibooting ColorOS and MIUI doesn't work, will continue testing with other ROMs...
---------- Post added at 04:37 PM ---------- Previous post was at 04:32 PM ----------
And another thing... For me boot menu is visible...
dansou901 said:
I'm just about to start doing this...
---------- Post added at 04:32 PM ---------- Previous post was at 04:12 PM ----------
OK, multibooting ColorOS and MIUI doesn't work, will continue testing with other ROMs...
Click to expand...
Click to collapse
That's because you need a kernel with kexec hardboot patch in secondary rom too. So you need a special kernel for color os and a special one for miui. You may try instlling the rom choosing "share kernel" option so it will use main rom kernel which has kexec
dansou901 said:
I'm just about to start doing this...
---------- Post added at 04:32 PM ---------- Previous post was at 04:12 PM ----------
OK, multibooting ColorOS and MIUI doesn't work, will continue testing with other ROMs...
---------- Post added at 04:37 PM ---------- Previous post was at 04:32 PM ----------
And another thing... For me boot menu is visible...
Click to expand...
Click to collapse
WHAT! I have black screen :|
KINGbabasula said:
WHAT! I have black screen :|
Click to expand...
Click to collapse
Maybe it is because you have CM 11 kernel installed? With ColorOS kernel it works...
dansou901 said:
Maybe it is because you have CM 11 kernel installed? With ColorOS kernel it works...
Click to expand...
Click to collapse
Surely I have something wrong in the kernel. Thanks for telling me that
If I try to share kernel between ColorOS and MIUI, MIUI won't boot (black screen after selecting it from the boot menu)...
dansou901 said:
If I try to share kernel between ColorOS and MIUI, MIUI won't boot (black screen after selecting it from the boot menu)...
Click to expand...
Click to collapse
Well that's expected because they use different kernels. The solution is to compile miui kernel with kexec patch and color os kernel with kexec patch. I tried only cm based roms. I'm on cm11 and I can boot slim and mahdi sharing kernel
OK, so we have to find kernel sources from Color OS and MIUI for this to work...

[RECOVERY][OFFICIAL] TWRP 3.5.2_9-0 [I9190][I9192][I9195][L520]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Code:
* [B][U]Your warranty is now void.[/U][/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Odin
- Odin3 v3.13.3
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy S4 Mini (International 3G)
TWRP for Samsung Galaxy S4 Mini (International Dual SIM)
TWRP for Samsung Galaxy S4 Mini (International LTE)
TWRP for Samsung Galaxy S4 Mini Sprint
How to flash TWRP with Odin​1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down, and Home buttons simultaneously. When the blue screen appears, release all 3 buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP" and press the "Start" button.
3. Pull the battery as soon as your phone vibrates.
4. You can then boot directly into TWRP by pressing the Power, Volume Up, and Home buttons simultaneously. Release all three buttons as soon as you see the boot screen ("Samsung Galaxy S4 mini").
How to flash TWRP within a previous version of TWRP​1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power, Volume Up, and Home buttons simultaneously. Release all 3 buttons when the boot screen appears ("Samsung Galaxy S4 mini").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Changelog
- See post #2.
Bugs
- You tell me!
Credits
- Inspiration in motivating me to learn how to build TWRP: ne0zone75
- arco68 and every other open source developer and user who contributes directly or indirectly to the TWRP community in the development of and in providing feedback for the serrano3gxx, serranodsdd, and serranoltexx.
Sources
- msm8930-common kernel repository
- serrano3gxx repository
- serranodsdd repository
- serranoltespr repository
- serranoltexx repository
- TWRP repository
XDA:DevDB Information
TWRP 3.5.2_9-0, ROM for the Samsung Galaxy S4 Mini
Contributors
ripee
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-0
Stable Release Date: 2021-04-06
Created 2018-01-17
Last Updated 2022-12-09
Reserved
CHANGELOG
3.2.1-1
* Restored compatibility with SD cards formatted in exFAT.
3.2.1-2
* Restored preload partition being visible when creating a backup.
Reserved
Your member of the TWRP Team ?.
It is nice to see that we have now an official TWRP.
Does new Build also support arco68 unofficial LOS 15.1 Version ?
Thanks @ripee !
Maybe you could link the the materialized theme in the OP : https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Clean design with a bunch of extra tools / options to enhance TWRP, this is really useful and handy ?
Sent from my S4 Mini using XDA Labs
lars85destroyer said:
Thanks @ripee !
Maybe you could link the the materialized theme in the OP : https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Clean design with a bunch of extra tools / options to enhance TWRP, this is really useful and handy
Sent from my S4 Mini using XDA Labs
Click to expand...
Click to collapse
Ok sure
ripee said:
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Click to expand...
Click to collapse
Thanks but seeing that Nougat version, will it work on a regular KitKat stock ROM ?
If not, which other version of TWRP should I use for an I9195 ?
TheRealKeyserSoze said:
Thanks but seeing that Nougat version, will it work on a regular KitKat stock ROM ?
If not, which other version of TWRP should I use for an I9195 ?
Click to expand...
Click to collapse
I have no reason to believe that 3.2.1-0 wouldn't work with stock KitKat. Just remember to pull the battery as soon as your phone vibrates after the flash finishes or else your stock rom could quickly re-flash its own stock recovery.
Please report feedback if you get it to work or not
That worked a treat!
Flawless flashing followed by installing root from TWRP.
Thanks a lot!
Been waiting on this...
Thank you for your job, but on my i9195 I had troubles with this release. Often it doesn't recognize my 32GB sdcard (it seems to be empty), instead of 3.2.0-1 that works as usual, also with oreo. Maybe I forgot to mount the microsd? But it's strnge, I've never mounted the microsd on previous versions.
Please include the exfat Samsung kernel driver:
https://forum.xda-developers.com/showpost.php?p=75650598&postcount=1638
sacharja said:
Indeed, however there seems to be a solution for Samsung products at least: https://github.com/bkuhn/exfat . Maybe ne0zone75 included this, but the TWRP guys don't use any Samsung device specific drivers.
Click to expand...
Click to collapse
I had the same issues with my SD
Dead here?
fankool said:
Thank you for your job, but on my i9195 I had troubles with this release. Often it doesn't recognize my 32GB sdcard (it seems to be empty), instead of 3.2.0-1 that works as usual, also with oreo. Maybe I forgot to mount the microsd? But it's strnge, I've never mounted the microsd on previous versions.
Click to expand...
Click to collapse
sacharja said:
Please include the exfat Samsung kernel driver:
https://forum.xda-developers.com/showpost.php?p=75650598&postcount=1638
I had the same issues with my SD
Click to expand...
Click to collapse
This has less to do with the exFAT driver and more to do with a missing TWRP flag in my device tree. I'll look into it.
What file format is your SD card in? Please try FAT32, exFAT, and NTFS so we can cover these most frequent possibilities.
sacharja said:
Dead here?
Click to expand...
Click to collapse
Users are used to ne0z0ne's unofficial builds perhaps.
sacharja said:
Please include the exfat Samsung kernel driver:
https://forum.xda-developers.com/showpost.php?p=75650598&postcount=1638
I had the same issues with my SD
Click to expand...
Click to collapse
I remember a similar problem with my TWRP build for the big S4, which I fixed by removing the following line from the BoardConfig.mk file:
Code:
TW_NO_EXFAT_FUSE := true
GT-I9190
twrp-3.2.1-1-serrano3gxx.img
twrp-3.2.1-1-serrano3gxx.tar
GT-I9192
twrp-3.2.1-1-serranodsdd.img
twrp-3.2.1-1-serranodsdd.tar
GT-I9195
twrp-3.2.1-1-serranoltexx.img
twrp-3.2.1-1-serranoltexx.tar
ripee said:
What file format is your SD card in? Please try FAT32, exFAT, and NTFS so we can cover these most frequent possibilities.
Click to expand...
Click to collapse
I'm not 100% sure but I remember last time I formatted using exfat
---------- Post added at 21:55 ---------- Previous post was at 21:31 ----------
GT-I9195
twrp-3.2.1-1-serranoltexx.img
twrp-3.2.1-1-serranoltexx.tar[/QUOTE]
Worked! Just booted in recovery and tried to open sdcard from file manager and I saw the files stored. Thank you.
fankool said:
I'm not 100% sure but I remember last time I formatted using exfat
---------- Post added at 21:55 ---------- Previous post was at 21:31 ----------
GT-I9195
twrp-3.2.1-1-serranoltexx.img
twrp-3.2.1-1-serranoltexx.tar
Click to expand...
Click to collapse
Worked! Just booted in recovery and tried to open sdcard from file manager and I saw the files stored. Thank you.[/QUOTE]
Fantastic! Thanks very much for your feedback! I'll update the official repo and ask TeamWin to compile official 3.2.1-1 builds.
Cool, it also worked for me now with the exfat SD (NTFS is of course working too).
Great job ripee, many thanks for your good work
@ripee
Hi this is the first time i want to install twrp on s4 mini lte version. By odin. But i do not boot in twrp. Always stock recovery.
What am i doing wrong ?
djbosanac said:
@ripee
Hi this is the first time i want to install twrp on s4 mini lte version. By odin. But i do not boot in twrp. Always stock recovery.
What am i doing wrong ?
Click to expand...
Click to collapse
If you have stock installed, you have to very quickly pull the battery as soon as your phone vibrates when Odin says PASSED! The stock rom is very sneaky because, if you don't pull the battery, it will re-flash its own stock recovery before rebooting into system.

[8.1.x][OFFICIAL][MONTHLY] CarbonROM | cr-6.1 [marlin]

{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Notice:
In order to install GApps, you must flash the ROM then reboot into TWRP before flashing our custom GApps package (as this switches slots). Custom GApps package can be found at https://mirror.myself5.de/taimen/GApps. We're working with the team behind MindTheGapps to fix the upstream for taimen.
Also, we know the default wallpaper on is black. We know it's caused by the RRO overlays on vendor and unfortunately we can't change the default (yet?), you can change it manually without complications though.
We know it’s complicated, but it sure is worth it!
Install Instructions:
Flash the newest factory images on both slots
Move your ROM + [GApps] + TWRP.zip to your internal storage
Boot the TWRP.img > Check what Slot you're on (Reboot Menu) ->Wipe Data & Cache -> Flash the ROM as well as the TWRP.zip
Either Reboot to system or, in case you want GApps, reboot to recovery via TWRP (Reboot -> Recovery)
Check and confirm that you are on the opposite slot from Step 3. If not, switch to it and reboot the recovery again (Reboot Menu) -> Flash GApps (and whatever else you want to flash -> Reboot to System -> Enjoy CarbonROM
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Google Pixel XL
Contributors
@joe_pacino, @Myself5
Source Code: [url]https://github.com/CarbonROM[/url]
ROM OS Version: 8.x oreo
ROM Kernel: Linux 3.18.x
Based On: AOSP
Version Information
Status: Weekly
Created 2018-05-01
Last Updated 2018-05-01
Bugs: None.
Note: I'm not the Marlin maintainer, @joe_pacino is. I maintain sailfish. He just does not use xda so I decided to maintain the thread.
Nice!
Which gapps I picked arm64
---------- Post added at 06:09 AM ---------- Previous post was at 05:10 AM ----------
Magisk 16.3 and 16.4 boot loop
---------- Post added at 06:37 AM ---------- Previous post was at 06:09 AM ----------
ok this doesn't work, it boots and the google framework crashes and the phone is unresponsive. when rebooting after this failure to start up with gapps, the phone is wiped in twrp...
sapphirecoupe said:
Which gapps I picked arm64
---------- Post added at 06:09 AM ---------- Previous post was at 05:10 AM ----------
Magisk 16.3 and 16.4 boot loop
---------- Post added at 06:37 AM ---------- Previous post was at 06:09 AM ----------
ok this doesn't work, it boots and the google framework crashes and the phone is unresponsive. when rebooting after this failure to start up with gapps, the phone is wiped in twrp...
Click to expand...
Click to collapse
I'm using it right now with no problems. Use these gapps as stated in the op https://mirror.myself5.de/taimen/GApps/ and just follow the instructions, and you should be good.
When trying to flash the image I am encountering 'updater process ended with error 1' I could not find a solution for this. Any ideas?
criminal666 said:
How do we flash the latest factory image on both slots? I am not familiar with this process
Click to expand...
Click to collapse
Easiest way is to backup your internal storage and select flash all
criminal666 said:
When trying to flash the image I am encountering 'updater process ended with error 1' I could not find a solution for this. Any ideas?
Click to expand...
Click to collapse
Needs latest TWRP
HueyT said:
Needs latest TWRP
Click to expand...
Click to collapse
That worked. Now my Google Play Services are crashing upon setup.
I am having a hell of a time.
criminal666 said:
That worked. Now my Google Play Services are crashing upon setup.
I am having a hell of a time.
Click to expand...
Click to collapse
Make sure you use the gapps listed in the op.
magisk 16.4,razorlove gapps 0328,dolby,subt. all working fine!
If you get boot loop using razorlove gapps just force reboot and your good to go!
I also wanted point out something this rom does that no other rom does.When using dolby there is no popping at all and when you clear recents there is no clicking at all.
You can double tap anywhere on screen,not even DU rom does that!Great start guys,awesome rom!Very glad your back!
Sean
---------- Post added at 05:57 PM ---------- Previous post was at 05:53 PM ----------
Do not flash custom kernel, you wont even be able to get back into recovery and you'll have flash factory image
Some apps are force closing when doing some things. Gallery closes when editing an image. Snapchat closes when trying to open a story or a photo someone sent you. I reported in the jira, but if anyone has a fix, i'm all ears. (I can provide a logcat)
---------- Post added at 05:57 PM ---------- Previous post was at 05:53 PM ----------
Do not flash custom kernel, you wont even be able to get back into recovery and you'll have flash factory image
Click to expand...
Click to collapse
Confirmed. Will try to " fastboot boot twrp.IMG " and then flash latest TWRP zip in this temp recovery to put recovery back (while connected to Windows PC and in boot loader mode)
petiolarissean said:
magisk 16.4,razorlove gapps 0328,dolby,subt. all working fine!
If you get boot loop using razorlove gapps just force reboot and your good to go!
I also wanted point out something this rom does that no other rom does.When using dolby there is no popping at all and when you clear recents there is no clicking at all.
You can double tap anywhere on screen,not even DU rom does that!Great start guys,awesome rom!Very glad your back!
Sean
---------- Post added at 05:57 PM ---------- Previous post was at 05:53 PM ----------
Do not flash custom kernel, you wont even be able to get back into recovery and you'll have flash factory image
Click to expand...
Click to collapse
Used my own kernel booted fine
kingbri said:
Some apps are force closing when doing some things. Gallery closes when editing an image. Snapchat closes when trying to open a story or a photo someone sent you. I reported in the jira, but if anyone has a fix, i'm all ears. (I can provide a logcat)
Click to expand...
Click to collapse
I am looking into this. Thanks for reporting.
Sorry should said exnoshadez kernal doesnt work for me caused me softbrick
liam_davenport said:
Used my own kernel booted fine
Click to expand...
Click to collapse
Sure, it'll boot fine but erases recovery --unless flashes kernel, magisk, twrp and then u can keep recovery
HueyT said:
Sure, it'll boot fine but erases recovery --unless flashes kernel, magisk, twrp and then u can keep recovery
Click to expand...
Click to collapse
My recovery was intact sounds like a kernel issue more than a rom issue contact the kernel dev they can look into it
shagbag913 said:
I am looking into this. Thanks for reporting.
Click to expand...
Click to collapse
I put 2 logcats filtering gallery and Snapchat on the jira. Called carbonrom-25. Hope this gets fixed soon!
kingbri said:
I put 2 logcats filtering gallery and Snapchat on the jira. Called carbonrom-25. Hope this gets fixed soon!
Click to expand...
Click to collapse
I will keep looking, thanks for uploading those logs !

[ROM][10.0][angler] ExtendedUI OFFICIAL

{
"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"
}
ExtendedUI is custom-rom based on PixelExperience that aims to provide different UI than any other rom on the market.
Also, we got our Telegram channel you can find here updates about the rom, screenshots and more.​
​
- Refined UI by cfdddd (00day/00day0)
- GAPPS included
- Ambient edge lighting
- FOD icon picker
- Double-tap to sleep on statusbar / lockscreeen
- Smart replies toggle
- Battery charging light customizations
- Notification snooze function
- Navigation bar customizations
- Lockscreen shortcuts customizations
- Configurable amount of screen height used for gestures​
First Time Install / Clean Flash
DO NOT FLASH GAPPS, ALREADY INCLUDED
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Data/Cache/System
4 Flash vendor/firmware for your device
5. Flash the ROM
6. Flash Magisk (Optional)
7. Reboot to System
Update / Dirty Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash the ROM
4. Reboot to System​
SOURCEFORGE
ExtendedUI source code
ExtendedUI devices source code​
- PixelExperience
- LineageOS
- OmniROM
- POSP
- Havoc-OS​
XDA:DevDB Information
ExtendedUI 10, ROM for the Huawei Nexus 6P
Contributors
PixelBoot
Source Code: https://github.com/Extended-UI
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2020-04-11
Last Updated 2020-04-11
Install Instructions
Grab our recovery from the peripherals section and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done, I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.
Peripherals
FBE Recovery: TWRP
FBE Recovery (4 Core): TWRP
BLOD Patch (4 Core): Osmosis BLOD Workaround Injector Addon AK3
PixelBoot on Fire !!
Omg .... Pixelboot is amazing..??? thanks
ExtendedUI 1.1 20200411
Changelog:
Device Changes:
Stabilized NFC
Stabilized video playback
Download:
SOURCEFORGE
how to flash Magisk on this Rom???
The new update .. is amazing .. the rom is stable 100% .. thanks pixel boot ..????
---------- Post added at 08:22 PM ---------- Previous post was at 08:03 PM ----------
everything is working very well, only the camera I love this rom is super fast I hope in the next update it will be solved ..
Hi, just a question, why is it that you have instructions in the OP, and a couple of posts down another? (sorry if noob question)
skoopster said:
Hi, just a question, why is it that you have instructions in the OP, and a couple of posts down another? (sorry if noob question)
Click to expand...
Click to collapse
The instructions in the first post is a generic copy & paste method not aimed at this specific device. You should follow the instructions in Post #2 and use the TWRP (and BLOD patch if needed) in Post #3.
---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------
Shabbirkt said:
how to flash Magisk on this Rom???
Click to expand...
Click to collapse
Through TWRP.
The new update .. is amazing .. the rom is stable 100% .. thanks pixel boot
The new update .. is amazing .. the rom is stable 100% .. thanks pixel boot
pixelboot, I know i'm four months late but I just ripped PE a new one on telegram.....unreal. They just released a build for the 5X on march 27th. The nerve of those dudes. I know you have moved on and I applaud you for that. Thanks for continuing the work. This latest build is fantastic. I finally managed to install a new battery into "The last nexus." Your hard work has enabled me to bring life back to Angler. I can't thank you enough.
I was swiping to unlock the device and suddenly it booted into Google logo..then I have to again restart the device by going into twrp..
Aditya kukreti said:
I was swiping to unlock the device and suddenly it booted into Google logo..then I have to again restart the device by going into twrp..
Click to expand...
Click to collapse
same problem...
well after i posted last night I tried to reboot back into exUI....got stuck at white screen with G logo. I was so mad that I ended up WIPING EVERYTHING....which was probably the worst thing I could have done. I tried re-installing the last stock android image. I did so successfully however, again when I booted up it got "stuck" again but this time with the black screen and Android logo in all CAP WHITE letters. I'm going to see if I can install a different rom but something tells me it's going to get "stuck" again.
mizzike32 said:
well after i posted last night I tried to reboot back into exUI....got stuck at white screen with G logo. I was so mad that I ended up WIPING EVERYTHING....which was probably the worst thing I could have done. I tried re-installing the last stock android image. I did so successfully however, again when I booted up it got "stuck" again but this time with the black screen and Android logo in all CAP WHITE letters. I'm going to see if I can install a different rom but something tells me it's going to get "stuck" again.
Click to expand...
Click to collapse
Maybe you only have 4 cores working now. That's how it happened to me. Hope that's not what happened to you[emoji51]
Sent from my [device_name] using XDA-Developers Legacy app
bigcelo75 said:
Maybe you only have 4 cores working now. That's how it happened to me. Hope that's not what happened to you[emoji51]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Believe me over these past couple of years (years 3 and 4 with angler) I have thought to myself do I finally have the dreaded BLOD.....but as it turns out I don't.
I just installed a new battery...(I've been dragging my rear getting around to do this....needed a new battery 2 years ago).
I think I screwed up with the ExUI build when I didn't "format data" right after flashing it. And the instructions specifically say to do that. What I don't understand is if that indeed what was wrong why did it bother to boot into exUI in the first place, only to get stuck at boot screen on first reboot.
I was also thinking maybe it was an app I downloaded upon install but I don't know.
---------- Post added at 11:52 PM ---------- Previous post was at 11:49 PM ----------
I know this is a major faux pas but I installed pixe1dust rom and have restarted several times and I have no problems on the latest build of that. This is how I know I don't have BLOD.
thx to pixelboot for that as well.
I will say that extendedUI is a lot smoother but for the time being I'm going to keep using pixe1dust until I start going crazy again. Maybe down the line I will try extendedUI again.
mizzike32 said:
Believe me over these past couple of years (years 3 and 4 with angler) I have thought to myself do I finally have the dreaded BLOD.....but as it turns out I don't.
I just installed a new battery...(I've been dragging my rear getting around to do this....needed a new battery 2 years ago).
I think I screwed up with the ExUI build when I didn't "format data" right after flashing it. And the instructions specifically say to do that. What I don't understand is if that indeed what was wrong why did it bother to boot into exUI in the first place, only to get stuck at boot screen on first reboot.
I was also thinking maybe it was an app I downloaded upon install but I don't know.
---------- Post added at 11:52 PM ---------- Previous post was at 11:49 PM ----------
I know this is a major faux pas but I installed pixe1dust rom and have restarted several times and I have no problems on the latest build of that. This is how I know I don't have BLOD.
thx to pixelboot for that as well.
I will say that extendedUI is a lot smoother but for the time being I'm going to keep using pixe1dust until I start going crazy again. Maybe down the line I will try extendedUI again.
Click to expand...
Click to collapse
Glad to hear that! Cheers [emoji6]
Sent from my [device_name] using XDA-Developers Legacy app
Pixel boot the legend
main happiness is when twrp asks for pin to decrypt data <3 this rom is 100% stable and smooth . no words to thank PixelBoot!
Camera is crushing sometimes while I take many pictures..

[ROM][Android 11][BERYLLIUM] crDroid v7.15 [20.02.2022]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (here)
NikGapps core (Download from here)
Magisk 21 or newer for root (after first boot) - (Download from here)
First time installation:
Backup your data to PC, OTG flash drive
Flash recovery and boot to recovery
Wipe system, data, cache and format data, then reboot to recovery
Copy crDroid and Gapps to internal memory then flash them in TWRP in same order
Reboot and enjoy
*Optional reboot again after first boot to flash Magisk for root
Update installation:
Boot to recovery and make a backup
Wipe system and cache
Flash updated crDroid and Gapps (and Magisk if you had this as root method)
Reboot and enjoy
Do note that crDroid doesn't encrypt your device, so there is no need to flash DFE or any similar stuff that can cause issues!
Sources:
ROM: https://github.com/crdroidandroid
Kernel source: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm845
Download:
ROM https://crdroid.net/beryllium#crDroid-v7
Changelog: https://github.com/crdroidandroid/android_vendor_crDroidOTA/blob/11.0/changelog_beryllium.txt
Known isues:
- none critical
Visit official website @ crDroid.net
crDroid Poco Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
ROM OS Version: Android 11
ROM Kernel: Linux 4.9
Encrypt data
As crDroid doesn't enforce encryption, you'll have to flash a special flashable zip in recovery in order to run encrypted
Please follow steps below
Warning Warning Warning --- This works only on clean flash
1. Flash crDroid.zip in recovery
2. Mount vendor partition in recovery (for some reason is not mounting with newer TWRP)
3. Flash encrypt zip
4. Reboot to system
Note:
The encrypt zip needs to be flashed after every update
So flash crDroid zip and follow with encrypt zip
Note2:
Recovery that is able to decrypt data is required in order to see data while booted to recovery
Official TWRP should be alright
Recommended Gapps?
I used NikGapps and it didn't let me restore my backup.
Well gapps for A11 are not quite ready
You'll have to seek a different version of gapps on the web
Note that unofficial opengapps turned to bootloop for me due to some missing permissions
The one posted in op is working but might miss some stuff as it's core version
Until a later date when gapps for a11 are more stable, you'll just have to play and install different versions for your needs
Thanks bro for releasing a11 version...awesome
gwolfu said:
Well gapps for A11 are not quite ready
You'll have to seek a different version of gapps on the web
Note that unofficial opengapps turned to bootloop for me due to some missing permissions
The one posted in op is working but might miss some stuff as it's core version
Until a later date when gapps for a11 are more stable, you'll just have to play and install different versions for your needs
Click to expand...
Click to collapse
There's a bug with the Gapps release. Need to setup everything and then restore from the settings.
Will give a brief review after done with the setup.
Thanks dev!
Please add signature spoofing support.
Is Live Display present with Display profiles?
udayan.divakaran said:
Is Live Display present with Display profiles?
Click to expand...
Click to collapse
only color calibration for now
Which TWRP we need to use to flash, the one which supports FBE or FDE?
keep the one from Android 10
we don't enforce encryption and FBE TWRP is kinda buggy
Good work on first release with most of customisation.
Does app migrate of backup and restore work here?
I have strange problem of any ROM working on custom kernel only, stock kernel fc all app after migrate restore!
What version of gcam works on this firmware?
I found, that Bluetooth Audio does not work.
Audio output will not switch to a BT device, once it gets connected.
If you have a media playback in your notifications, you get an Option, to select another output device there. When I select my BT headphones, it does nothing and the BT settings will say, that the connection to the BT device can't be established.
I tested this with multiple BT headphones and a BT speaker.
Can confirm that Bluetooth connection does not work. Also, did anyone else have their recovery changed to Lineage recovery?! Flashed using TWRP and now it's Lineage recovery. How do I change it back? Guess I'll be Googling.
monkeymagic2178 said:
Can confirm that Bluetooth connection does not work. Also, did anyone else have their recovery changed to Lineage recovery?! Flashed using TWRP and now it's Lineage recovery. How do I change it back? Guess I'll be Googling.
Click to expand...
Click to collapse
Can't confirm BT yet, the LOS recovery thing happened though. Just use fastboot from pc and flash it again if you don't have root on the device otherwise you can use the twrp app or an app like flashify. A custom kernel or magisk should make twrp stick. You simply can't flash twrp or basically anything through LOS recovery.
After "Preparing your phone..." and full white screen appears and i'm blocked. Anyone experienced this issue?
---------- Post added at 09:17 AM ---------- Previous post was at 09:10 AM ----------
Another issue I noticed is that the ROM doesn't recognize my SD-Card. I came from ReloadedOS there works, maybe dev can check commits from them? But if you manage to get into the OS, it is super fast!
speter2 said:
After "Preparing your phone..." and full white screen appears and i'm blocked. Anyone experienced this issue?
---------- Post added at 09:17 AM ---------- Previous post was at 09:10 AM ----------
Another issue I noticed is that the ROM doesn't recognize my SD-Card. I came from ReloadedOS there works, maybe dev can check commits from them? But if you manage to get into the OS, it is super fast!
Click to expand...
Click to collapse
I'm not sure if you mean external SD or internal SD, but for me on stock kernel it recognizes both. My internal SD and my 128gb Samsung micro SD card.
Twrp/fastboot corrupted after installation
Installed the rom and it replaced my twrp recovery. Now i am unable to change the recovery from neither recovery nor fastboot. Whenever i try to sideload any other file, it shows me the following error
"E:footer is wrong
E:Signature verification failed
E: error:21"
MrEvilPanda said:
Installed the rom and it replaced my twrp recovery. Now i am unable to change the recovery from neither recovery nor fastboot. Whenever i try to sideload any other file, it shows me the following error
"E:footer is wrong
E:Signature verification failed
E: error:21"
Click to expand...
Click to collapse
What I did to get back twrp was the following:
Downloaded the latest official twrp.
Downloaded Minimal fastboot&adb and extracted it.
Copyed the recovery.img to the folder where i extracted fastboot.
Rebooted phone into bootloader.
I typed the following command: 'fastboot boot recovery.img' and i got back into twrp where I used the 'Install Image' to install recovery.
I hope this helps
---------- Post added at 04:24 PM ---------- Previous post was at 04:24 PM ----------
JD. A said:
I'm not sure if you mean external SD or internal SD, but for me on stock kernel it recognizes both. My internal SD and my 128gb Samsung micro SD card.
Click to expand...
Click to collapse
My external SD Card appears as corrupted, even tho in recovery it works fine and when I install other roms i can read/write from/to it without problems.

Categories

Resources