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,
*/
Bootleggers ROM is an aftermarket firmware based on Ground Zero Open Source Project (GZOSP) and brings custom features with the most useful apps on your device, with the goal of "Making you feel like 家".
Using the stability and compatibility of GZOSP, this ROM is also packed with some custom wallpaper (Dawn by fxckingdeathwish), ringtones, and fonts, to bring to your device into a more fresh look, also with a selection of apps, header packs and wallpapers (on ShishuWalls app)..
Introduction:
This is the unofficial bootleggers OS thread for the Motorola G7 Power, codename ocean.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
ROM:
https://drive.google.com/file/d/1KkDEp2CVxAT1L5RgfZ9mWP6aLXfi2UQM/view?usp=drivesdk
Recovery:
https://drive.google.com/file/d/1-4Wz5wTDoEe3fOiUVMwnpcbyEydB4EoI/view?usp=drivesdk
Copy Partitions: (To setup slot_b)
https://drive.google.com/file/d/1-1uphzJPDvG4Ly44nmNasZRxF1fzyn5V/view?usp=drivesdk
Preparation for A/B Roms:
01. Download TWRP and the Firmware for your variant from the links above.
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Flash your factory firmware image on slot_A
Hold power + Volume down untill you reach bootloader (fastboot mode)
In your extracted firmware folder open a terminal and flash your firmware files with these commands.
NOTE: This last step installs vendor.img to slot_b as well.
05. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
06. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
07. While in TWRP choose Reboot > bootloader
08. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM, TWRP and GApps from the links above.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Flash ROM.zip + TWRP_installer/boot.img ramdisk method
04. Reboot > Recovery
05. Install Gapps + Magisk (if you choose)
06. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. fasboot boot twrp.img
03. Install ROM.zip + TWRP_installer/boot.img ramdisk method
04. Reboot > Recovery
05. flash gapps + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must use 'fastboot -w' to erase it before using ROMS
Contributors
SyberHexen, BootleggersRom Team
Source Code:
Kernel
https://github.com/SyberHexen/android_kernel_motorola_msm8953
Vendor
https://github.com/SyberHexen/proprietary_vendor_motorola-1
Device
https://github.com/SyberHexen/android_device_motorola_ocean
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Stock Vendor.img
Version Information
Status: Testing
First!
Nice one mate, tried this rom on s4 & really liked it... Great to see some development for g7
So first off........ Great Rom. Love the features and settings. Had to follow lineage's instructions for this Rom installation. One problem I am having though is when I finished up the installation, go back to recovery, my sdcard(internal storage) is encrypted I think. I don't know if I did something wrong.
krayzieiyian23 said:
So first off........ Great Rom. Love the features and settings. Had to follow lineage's instructions for this Rom installation. One problem I am having though is when I finished up the installation, go back to recovery, my sdcard(internal storage) is encrypted I think. I don't know if I did something wrong.
Click to expand...
Click to collapse
Format data after twrp install
Does it work on the 1955-2 ocean model, South American version?
KUSANAGUI said:
Does it work on the 1955-2 ocean model, South American version?
Click to expand...
Click to collapse
should work, ive flashed the other roms theyve been developing and they will flash
Ok I got bootlooped after I set apns wasn't getting any data on att unlocked version of the phone
Não consigo desbloquear meu moto g7 power
Já reset fiz tudo mais nao vai
Finally got it running after days of banging my head on the wall i love this rom so much freedom to customize the system to your liking running really good and stable i just cant flash the recovery or it will not even make it to the bootscreen just using fastboot to boot into twrp im rooted with Magisk and now my moto is a very awesome phone that makes people with expensive phones jealous i Love it thank you so much will send you a donation as soon as I get some$ whats $20 for a custom rom that makes your phone a much more functional and way more pleasing to the eyes
Related
Hi,
I've packed the Firmware (without system.img) into a 7z file for flashing GSI easier.
**DISCLAIMER**
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
**DISCLAIMER**
Step-by-Step Guide:
1. Download and unpack the nokia_3.2_october_gsi_base.7z file anywhere on your computer. And reboot to bootloader mode (i think you already unlocked your bootloader)
2. Go ahead and first execute flash-all.bat and then flash-magisk-nodm.bat. Thats because for having the October 2019 firmware on your device, because the magisk patched image file is from October firmware and has removed the AVB/DM-Verity parameter.
3. Download any GSI ROM you want, but best is if you use a GSI with GApps included, because you can't flash GApps manually. (I've got a TWRP Port but you could brick your device and you can't flash anything to system with it, so it simply useless)
I can recommend Havoc OS from ExpressLuke GSI. (It now has GApps included)
4. After unpacked the xz file just flash it with 'fastboot flash system GSI_ROM_FILE_NAME_HERE.img'
5 Reboot and Done!
Downloads
https://drive.google.com/open?id=1NxEMAOZvEvx8Nw0qsw9_1jaEC4UYS-fu
How to unlock Bootloader:
How to Unlock the Bootloader of the Nokia 3.2
Step 1 – Enable OEM unlocking
You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings, About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
Step 2 – Unlock your phone
Set up adb, reboot into your bootloader and run the following command. Yes, it’s really that simple!
fastboot oem unlock
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Source: https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/
Btw is it safe to downgrade?
Stupid question but as i had told u that im on latest January update is it necessary to just flash an old update to get things working?
Cant u plz provide me a patched boot.img based on latest January update?
Plus which GSI rom u have used and find it better ? (In battery and stability). .what were the bugs ?
I need latest boot.img plz i have 00ww varient
On latest January 2020 update
If you want to flash gsi just downgrade your firmware using the pack I've created. Because I don't have boot img file from January 2020 firmware
Can you explain what is GSI ? Is it a flash-able custom ROM or what ?
GSI is a Generic System Image that could be from Google itself or from Custom ROM developers like LineageOS. The GSIs use drivers from manufacturers. Any devices that support project Treble (GSI support) have the drivers for dealing with a GSI image and Adapting the Android version to your device.
s3tupw1zard said:
Hi,
I've packed the Firmware (without system.img) into a 7z file for flashing GSI easier.
**DISCLAIMER**
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
**DISCLAIMER**
Step-by-Step Guide:
1. Download and unpack the nokia_3.2_october_gsi_base.7z file anywhere on your computer. And reboot to bootloader mode (i think you already unlocked your bootloader)
2. Go ahead and first execute flash-all.bat and then flash-magisk-nodm.bat. Thats because for having the October 2019 firmware on your device, because the magisk patched image file is from October firmware and has removed the AVB/DM-Verity parameter.
3. Download any GSI ROM you want, but best is if you use a GSI with GApps included, because you can't flash GApps manually. (I've got a TWRP Port but you could brick your device and you can't flash anything to system with it, so it simply useless)
I can recommend Havoc OS from ExpressLuke GSI. (It now has GApps included)
4. After unpacked the xz file just flash it with 'fastboot flash system GSI_ROM_FILE_NAME_HERE.img'
5 Reboot and Done!
Downloads
https://drive.google.com/open?id=1NxEMAOZvEvx8Nw0qsw9_1jaEC4UYS-fu
How to unlock Bootloader:
How to Unlock the Bootloader of the Nokia 3.2
Step 1 – Enable OEM unlocking
You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings, About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
Step 2 – Unlock your phone
Set up adb, reboot into your bootloader and run the following command. Yes, it’s really that simple!
fastboot oem unlock
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Source: https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/
Click to expand...
Click to collapse
File is in trash xd
s3tupw1zard said:
Hi,
I've packed the Firmware (without system.img) into a 7z file for flashing GSI easier.
**DISCLAIMER**
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
**DISCLAIMER**
Step-by-Step Guide:
1. Download and unpack the nokia_3.2_october_gsi_base.7z file anywhere on your computer. And reboot to bootloader mode (i think you already unlocked your bootloader)
2. Go ahead and first execute flash-all.bat and then flash-magisk-nodm.bat. Thats because for having the October 2019 firmware on your device, because the magisk patched image file is from October firmware and has removed the AVB/DM-Verity parameter.
3. Download any GSI ROM you want, but best is if you use a GSI with GApps included, because you can't flash GApps manually. (I've got a TWRP Port but you could brick your device and you can't flash anything to system with it, so it simply useless)
I can recommend Havoc OS from ExpressLuke GSI. (It now has GApps included)
4. After unpacked the xz file just flash it with 'fastboot flash system GSI_ROM_FILE_NAME_HERE.img'
5 Reboot and Done!
Downloads
https://drive.google.com/open?id=1NxEMAOZvEvx8Nw0qsw9_1jaEC4UYS-fu
How to unlock Bootloader:
How to Unlock the Bootloader of the Nokia 3.2
Step 1 – Enable OEM unlocking
You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings, About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
Step 2 – Unlock your phone
Set up adb, reboot into your bootloader and run the following command. Yes, it’s really that simple!
fastboot oem unlock
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Source: https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/
Click to expand...
Click to collapse
The file is trashed.
MKashifSajjad said:
The file is trashed.
Click to expand...
Click to collapse
I have the Android 9 October 2019 images here:
https://drive.google.com/drive/folders/16bxdyEKEnBEVadC6lbrAoXxJIDAnGw0m
If anything goes wrong after using flash bat/sh files just run this command using fastboot:
Code:
fastboot --set-active=a
you can also try setting "b" as the active slot, both works. No differences.
Can anyone with a lineageos or AOSP/Phhusson GSI confirm what is working and what is not working?
WIFI
RIL (SIMcard)
GPS
Thanks
link is broken plz update the link
s3tupw1zard said:
Hi,
I've packed the Firmware (without system.img) into a 7z file for flashing GSI easier.
**DISCLAIMER**
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
**DISCLAIMER**
Step-by-Step Guide:
1. Download and unpack the nokia_3.2_october_gsi_base.7z file anywhere on your computer. And reboot to bootloader mode (i think you already unlocked your bootloader)
2. Go ahead and first execute flash-all.bat and then flash-magisk-nodm.bat. Thats because for having the October 2019 firmware on your device, because the magisk patched image file is from October firmware and has removed the AVB/DM-Verity parameter.
3. Download any GSI ROM you want, but best is if you use a GSI with GApps included, because you can't flash GApps manually. (I've got a TWRP Port but you could brick your device and you can't flash anything to system with it, so it simply useless)
I can recommend Havoc OS from ExpressLuke GSI. (It now has GApps included)
4. After unpacked the xz file just flash it with 'fastboot flash system GSI_ROM_FILE_NAME_HERE.img'
5 Reboot and Done!
Downloads
https://drive.google.com/open?id=1NxEMAOZvEvx8Nw0qsw9_1jaEC4UYS-fu
How to unlock Bootloader:
How to Unlock the Bootloader of the Nokia 3.2
Step 1 – Enable OEM unlocking
You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings, About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
Step 2 – Unlock your phone
Set up adb, reboot into your bootloader and run the following command. Yes, it’s really that simple!
fastboot oem unlock
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Source: https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/
Click to expand...
Click to collapse
YO DUDE LINK IS EMPTY
Followed all steps and its working...
Android Open Source Project - android-11.0.0_r17
* 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.
Credits: Google, Sony Xperia Developer World
-------------------------------------------------------------
Sorry for my english.
Hi everyone, this is the first time I am compiling a ROM.
It's just a test, as it seems to work I decided to share it with you.
-------------------------------------------------------------
Instructions:
Before you flash the images, make sure your device is unlocked through Sony’s unlock boot loader service and that the device is in Fastboot mode.
- Download the vendor image and flash first:
https://developer.sony.com/file/dow...es-for-aosp-android-11-0-kernel-4-14-yoshino/
- Unpack the vendor zip file to obtain the vendor image;
- Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable. When the device is in Fastboot mode, the LED on the device will be illuminated in blue.
- Flash the vendor image by entering the following commands in a terminal window:
fastboot flash oem SW_binaries_for_Xperia_Android_<release version>_<platform>.img
- Download ROM:
http://www.mediafire.com/file/ph3z52u2staujx6/android-11.0.0_r17.zip/file
- Unpack the rom zip file to obtain the rom image;
- Flash the image by entering the following commands in a terminal window:
fastboot flash boot boot.img
fastboot flash recovery recovery.img ( Don't use the recovery in this rom, I've tested this TWRP 3.3.1 found here: https://forum.xda-developers.com/xperia-xz1/themes/twrp-3-3-0-aroma-compatible-ultra-low-t3922527 )
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
-------------------------------------------------------------
Bugs:
- Tethering usb;
- Factory reset don't work;
- After the system is started the first time, restarting in recovery, the twrp goes into bootloop. To start twrp again you need to flash the userdata.img (factory reset) via fastboot;
- I don't know.
Tested:
- 4G;
- 3G;
- 2G;
- GPS;
- Voice Call;
- Wifi;
- Stock Camera;
- Fingerprint;
- Bluetooth.
-------------------------------------------------------------
I flashed the Android 11 GAPPS and everything seems to be working fine.
-------------------------------------------------------------
Source Code: https://github.com/sonyxperiadev/kernel/tree/aosp/LA.UM.7.1.r1
ROM OS Version: Android 11
ROM Kernel: Linux 4.14.196
Based On: AOSP
Security Patch: 05 November 2020
Version Information
Status: Test
Created 2020-07-11
Last Updated 2020-07-11
Can you share us the screenshots of ROM?
Also, is this ROM has Sony Music (Walkman) and Album app?
Demirag said:
Can you share us the screenshots of ROM?
Also, is this ROM has Sony Music (Walkman) and Album app?
Click to expand...
Click to collapse
I just downloaded the android 11 source code (40 Gb) and compiled it. So the rom is basic, it only has the main android stock apps:
phone, address book, calendar, camera, gallery and file browser.
If i try to flash it on my XZ Premium (G8141), can it be successfull? XZP is also Yoshino platform
gsep said:
Android Open Source Project - android-11.0.0_r17
* 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.
Credits: Google, Sony Xperia Developer World
-------------------------------------------------------------
Sorry for my english.
Hi everyone, this is the first time I am compiling a ROM.
It's just a test, as it seems to work I decided to share it with you.
-------------------------------------------------------------
Instructions:
Before you flash the images, make sure your device is unlocked through Sony’s unlock boot loader service and that the device is in Fastboot mode.
- Download the vendor image and flash first:
https://developer.sony.com/file/dow...es-for-aosp-android-11-0-kernel-4-14-yoshino/
- Unpack the vendor zip file to obtain the vendor image;
- Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable. When the device is in Fastboot mode, the LED on the device will be illuminated in blue.
- Flash the vendor image by entering the following commands in a terminal window:
fastboot flash oem SW_binaries_for_Xperia_Android_<release version>_<platform>.img
- Download ROM:
http://www.mediafire.com/file/ph3z52u2staujx6/android-11.0.0_r17.zip/file
- Unpack the rom zip file to obtain the rom image;
- Flash the image by entering the following commands in a terminal window:
fastboot flash boot boot.img
fastboot flash recovery recovery.img ( Don't use the recovery in this rom, I've tested this TWRP 3.3.1 found here: https://forum.xda-developers.com/xperia-xz1/themes/twrp-3-3-0-aroma-compatible-ultra-low-t3922527 )
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
-------------------------------------------------------------
Bugs:
- I don't know.
Tested:
- 4G;
- 3G;
- 2G;
- GPS;
- Voice Call;
- Wifi;
- Stock Camera;
- Fingerprint.
-------------------------------------------------------------
I flashed the Android 11 GAPPS and everything seems to be working fine.
-------------------------------------------------------------
ROM OS Version: Android 11
ROM Kernel: Linux 4.14.196
Based On: AOSP
Security Patch: 05 November 2020
Version Information
Status: Test
Created 2020-07-11
Last Updated 2020-07-11
Click to expand...
Click to collapse
I have tried this rom
thank you for your hard work.
In my opinion, this ROM is pretty good with almost no problems
But please fix Eraser All data (factory reset) from settings. i found it was always force closed
Too much drain on the battery, maybe because fingerprints always work without pressing power
The feature for displaying the frame rate needs to be improved because it is less accurate
a little troublesome because I can't enter TWRP maybe because I didn't flash recovery.img from zip
I will be looking forward to improvements of this rom
maybe I will change this comment after getting root access
elmirer said:
If i try to flash it on my XZ Premium (G8141), can it be successfull? XZP is also Yoshino platform
Click to expand...
Click to collapse
I recommend that you only use the rom that matches the codename of the device.
to avoid things that are not desirable
https://forum.xda-developers.com/xz-premium/development
elmirer said:
If i try to flash it on my XZ Premium (G8141), can it be successfull? XZP is also Yoshino platform
Click to expand...
Click to collapse
I don't know, it could but I wouldn't risk it.
starvirus10 said:
I have tried this rom
thank you for your hard work.
In my opinion, this ROM is pretty good with almost no problems
But please fix Eraser All data (factory reset) from settings. i found it was always force closed
Too much drain on the battery, maybe because fingerprints always work without pressing power
The feature for displaying the frame rate needs to be improved because it is less accurate
a little troublesome because I can't enter TWRP maybe because I didn't flash recovery.img from zip
I will be looking forward to improvements of this rom
maybe I will change this comment after getting root access
I recommend that you only use the rom that matches the codename of the device.
to avoid things that are not desirable
https://forum.xda-developers.com/xz-premium/development
Click to expand...
Click to collapse
Thanks for trying it.
I'll try to fix what you told me, but I don't guarantee that I will.
It also happened to me that the twrp did not start.
After re-flashing userdata.img (factory reset) via fastboot, twrp recovery started.
I assume twrp doesn't read the encrypted data and doesn't start.
Any advice is welcome.
Is it treble ready BY ANY CHANCE?
JimKatsanos said:
Is it treble ready BY ANY CHANCE?
Click to expand...
Click to collapse
I don't know, I haven't tried.
@gsep
Thanks for the Great work.
Someone who tried this rom mentioned that fingerprint works without pressing power, which I believe is really useful. I just wanted to know if it's Android 11 feature or you added it yourself?
I just downloaded and compiled the android 11 source code. I didn't make any changes to the code.
sohrab1985 said:
@gsep
Thanks for the Great work.
Someone who tried this rom mentioned that fingerprint works without pressing power, which I believe is really useful. I just wanted to know if it's Android 11 feature or you added it yourself?
Click to expand...
Click to collapse
This is actually a bug , firstly existent in android 10 but devs fixed it there ... so yeah
JimKatsanos said:
This is actually a bug , firstly existent in android 10 but devs fixed it there ... so yeah
Click to expand...
Click to collapse
It should be a feature rather than a bug, like AOF
Of course it's only a feature when it won't affect the battery drain or else it's a bug.
THREAD CLOSED
@gsep Please check your PM.
Regards,
shadowstep
Forum Moderator
EDIT: Thread re-opened.
doesn;twant to connect to wifi
it damn issue
Sorry for overspamming this thread but... Is the screen "lagging" bug still here in 11? Also , what about battery life?
JimKatsanos said:
Sorry for overspamming this thread but... Is the screen "lagging" bug still here in 11? Also , what about battery life?
Click to expand...
Click to collapse
At the moment no changes have been made. I don't know how long the battery life is, I use this device as a second smartphone, and I wanted to try to compile a rom to get the latest security patches. I have to learn a lot to start making changes to the source and I have to find the time to do it. If I don't have any problems I will certainly try to keep the security patches updated.
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:
Code:
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption work
- Otg work
-Vibrator
- Zip Flash
- Mtp/adb
- F2FS support
- Fastbootd
- Adb sideload
- Backup restore and images flash
Not working:
-Tell me
INSTALLATION:
1. Download the TWRP image file to your PC.
2. Put your device into fastboot.
3. Type the following command to flash the recovery:-
Code:
fastboot flash recovery "name_of_recovery.img"
4. On installation of TWRP , to boot the recovery do:-
Code:
fastboot boot "name_of_recovery.img"
The device will automatically reboot into TWRP.
5-A. You are using Xiaomi.eu Miui or custom Rom?
You can enjoy with a functional Data Decrypt
5-B You are using Miui EEA - Global -Cn or any custom rom that doesn't ship custom vbmeta.
6. Download this zip, copy by pc or using otg and flash this zip that will prevent twrp replacing.7. Download VbMeta and flash by fastboot
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
7. Reboot into twrp (Take longer Time)
Code:
fastboot boot "name_of_recovery.img"
8. Format Data and Reboot
NOTES:
By Command fastboot boot, recovery will decrypt everytimes you need, also with Global Rom and without patched vbmeta.
Download:
TWRP
VbMeta
(Version tag will follow vendor, a lower version tag than your vendor does not mean that recovery will not work)
Kernel Source: HERE
Donation:
PayPal: paypal.me/manuelbiancodev
Telegram Group: @MBsRoom
One user reported that MTP doesn't work after formatting data, and reboot back to recovery also doesn't make it work again.
Personally I haven't tried it, but the mentioned issue is kinda similar to the last build of mauro's twrp for the phone, so just want to let you know and hope someone else can confirm.
I didn't find how to decrypt data using schema.
huyhung411991 said:
One user reported that MTP doesn't work after formatting data, and reboot back to recovery also doesn't make it work again.
Personally I haven't tried it, but the mentioned issue is kinda similar to the last build of mauro's twrp for the phone, so just want to let you know and hope someone else can confirm.
Click to expand...
Click to collapse
doesn't work after formatting data
zeduck said:
I didn't find how to decrypt data using schema.
Click to expand...
Click to collapse
there are problem to decrypt with 12.2.4 such as umi have to fastboot boot the recovery to decrypt
Thank you.
thought id give it a try...formatting data does indeed make the sdcard inaccessible via mtp; seems the necessary directories isnt created after formatting. if you have a rom installed, you will need to boot back into the rom then reboot to twrp which will now be mtp accessible. tested only on crdroid.
edit: managed to get mtp to work after formatting. after format data reboot to system but on the poco bootscreen, hold down vol up and power key to re-enter twrp, mtp then seems to work
New instructions for eea and global user, post updated.
Decryption works for both PIN and Pattern on EU weekly beta.
PIN didn't work with TWRP3.4.2b but now it is OK with your TWRP. Thank you!
okay.. finally can use my pin again..
cant mount /vendor /product /ODM
With this recovery we don't need anymore to format internal storage every time we change rom?
Redmi K30 Pro Zoom Edition: longer boot into recovery, than LR.Team's TWRP, but PIN decryption works (on mine it worked with LR.Team's too, but I had to cancel password input).
cerealguy said:
With this recovery we don't need anymore to format internal storage every time we change rom?
Click to expand...
Click to collapse
This is rom dependant, if you flash stock global or eaa for example, Yes is needed
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
manuelbianco said:
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
Click to expand...
Click to collapse
Touchscreen not working on this version.
karnasw said:
Touchscreen not working on this version.
Click to expand...
Click to collapse
Maybe you clicked into download latest but so dowloaded umi version download this https://sourceforge.net/projects/mbroms/files/TWRPLMI/MBTWRP_08-03-2021.img/download
manuelbianco said:
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
Click to expand...
Click to collapse
All fine on my Poco F2 Pro. Touchscreen works.
manuelbianco said:
Maybe you clicked into download latest but so dowloaded umi version download this https://sourceforge.net/projects/mbroms/files/TWRPLMI/MBTWRP_08-03-2021.img/download
Click to expand...
Click to collapse
You're right. I downloaded latest not LMI. My bad, sorry.
Do I have to do something special to backup and restore? I want to try some roms but I hate having to config back everything after rollback to the previous ROM.
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.
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM/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.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
The best thing ever happened for realme ui 2. Great work mate..!
Finally, a proper working Recovery for our device
Wow...Finally Working TWRP for RMX1931 on RUI2.
Thanks alot bro.
Can I flash this, when I'm on Lineage-18.1?
zheka99 said:
Can I flash this, when I'm on Lineage-18.1
Click to expand...
Click to collapse
Technically its possible...but you should do it after roms released based on rui2 firmware. If not , you will endup with broken OS. For now dont flash custom roms with this recovery.
can i flash magysk to optine root, wich version?
Isavar said:
can i flash magysk to optine root, wich version?
Click to expand...
Click to collapse
Magisk-92546e8a(23016) from CANARY all Ok!
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Leozgz85 said:
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Click to expand...
Click to collapse
Hi
was the same for me, had to reinstall everything, only started in TWRP. Would like to install the recovery but I don't feel like this error anymore.
Thanks. It's working.
Doesnt work for me, i cant boot to realme ui after flashing the vbmeta, i got stuck on recovery. (f.14)
This recovery is broken for me, it gives me no space left on sdcard even after a full data reformat, ozip extraction stops after 500mb.
It's just not working as it should 3.4 works best
arnodorian-r said:
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.
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM/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.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
Click to expand...
Click to collapse
I followed this guide and many others in the past 48 hours, with no success. Every time I flash TWRP and the VBMETA, I get stuck in TWRP bootloop.
I started unblocking the bootloader, rolling back to RUI1 - Android 9 and using the Deep-Test App.
After the roll back, I got the phone unblocked right, but then first soft-brick, with only bootloader available and no way to flash a working ROM. After some searches, I've finally managed to unbrick, using OPPO flash tool, and installing stock rom RMX1931_11_F.14_2021102817443142.
This gives me a working phone, RUI.2 - Android 11. Standard recovery.
I tried to flash TWRP and got the phone soft bricked again, in TWRP recovery bootloop.
I'd like to install TWRP and from there going to OrangeFox and finally install Lineage 19.1...
How can i first have a working TWRP recovery??? If you can support also following steps, would be amazing. Thank you!!!
I went few step further... but still I am not able to install a working custom recovery for my realme X2 pro.
I have now also rooted my device with magisk.
I just need a custom recovery to perform 2 actions:
- make a NANDroid backup;
- install a custom ROM.
Any advice? Thank you for your time!
Installed. Working like a charm with lineage 19.1. Only problem: can't access files in storage. Digging into the matter, it seems to be an issue with android 12's new encryption method, which can't be overriden by this version of the recovery. There's a brand new TWRP 3.7.0_9.0 in the official TWRP website which boasts to overcome this problem but, whenever I try to install it (with or without the vbmeta.img provided for version 3.6.0_11), the recovery won't start. Guess a new vbmeta.img is needed as everything goes ok reinstalling TWRP 3.6.0_11 and its corresponding vbmeta. Tried to extract and install vbmeta.img from the lineage zip file without success. Shall we have to patch vbmeta.img? How can we do that? Through Magisk? I've come across some "vbmeta patcher" apk... Am I pointing the right way?
can any one help me to unlock bootloader in realme x2 pro . i am on RUI 10 . i installed in depth tool it said seccesful but no bootloader just keep rebooting and showing fast boot for a moment .. help please i search every where for fix but no way to yet
I'm using the CN variant device, which I understand does not yet have confirmed support, nonetheless sharing the error I'm encountering in case it's a simple or obvious fix I'm missing.
Having followed all above steps, I'm able to flash and get into TWRP recovery, but decryption always failed (even after a dozen tries) with the following:
"Attempting to decrypt FBE for user 0...
Failed to decrypt user 0"
Much obliged for any insight on this. I'm attempting to get back on OF after successfully installing Lineage 19.1, which broke the OF recovery, and since OF needs to be installed as a ZIP, I need to get some version of TWRP working as an intermediary. Specifically this is because I didn't install GAPPS along with Lineage 19.1 (I misread the opening post, which seemed to imply that GAPPS was included in that particular ROM). So alternatively, if there's another way to get GAPPS onto the device without recovery (sideload won't work since I can't decrypt...) then that would be helpful too.
Thanks in advance for any insight on this!
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:
First time installation:
1. Disable AVB with fastboot (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
2. Flash PBRP with fastboot (fastboot flash recovery recovery.img)
3. Reboot to Recovery
4. Wipe Data/Cache
5. Flash the ROM (Could need to unmount system before if it's mounted), then flash GAPPS
6. Format data
7. Reboot to System
Update installation:
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash the ROM and GAPPS
4. Reboot to System
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/realme-kernel-opensource/realme6-kernel-source
Device: https://github.com/TheCloverly/device_realme_RMX2001
Download:
ROM: https://crdroid.net/RM6785
Changelog: https://raw.githubusercontent.com/c..._vendor_crDroidOTA/11.0/changelog_RMX2001.txt
Known issues:
* Night light flickers
Visit official website @ crDroid.net
crDroid RMX2001 Telegram
crDroid Community Telegram
Donate to help our team pay server costs
@TheCloverly
Greetings. Just a friendly FYI, there is no "13" rom version available for the device you listed, and the 7 and 11 versions are no longer available in your DL link.
If you would please fix this ASAP so as this thread is not closed for being a "placeholder," we would be most appreciative.
-Regards: Badger50
Badger50 said:
@TheCloverly
Greetings. Just a friendly FYI, there is no "13" rom version available for the device you listed, and the 7 and 11 versions are no longer available in your DL link.
If you would please fix this ASAP so as this thread is not closed for being a "placeholder," we would be most appreciative.
-Regards: Badger50
Click to expand...
Click to collapse
Thankyou FYI, I have fixed it.
battery is stable?
TheCloverly said:
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:
First time installation:
1. Disable AVB with fastboot (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
2. Flash PBRP with fastboot (fastboot flash recovery recovery.img)
3. Reboot to Recovery
4. Wipe Data/Cache
5. Flash the ROM (Could need to unmount system before if it's mounted), then flash GAPPS
6. Format data
7. Reboot to System
Update installation:
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash the ROM and GAPPS
4. Reboot to System
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/realme-kernel-opensource/realme6-kernel-source
Device: https://github.com/TheCloverly/device_realme_RMX2001
Download:
ROM: https://crdroid.net/RM6785
Changelog: https://raw.githubusercontent.com/c..._vendor_crDroidOTA/11.0/changelog_RMX2001.txt
Known issues:
* Night light flickers
Visit official website @ crDroid.net
crDroid RMX2001 Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
Device RMX2151
Can Android 13 based ROMs for rm6785(rmx2151 in this case) be flashed from RUI2 or RUI1 ?
which custom recovery do you suggest ?
When I flash android 13 ROMs on rmx2151, they don't work, phone reboots at booting animation of the custom rom
I installed this ROM successfully but when I tried to go into my custom recovery "Orangefox"
The device stands on the logo and restarts itself and keeps the device logo
Please any help on this sir
Does this ROM work for Realme 6S (RMX2002)?
ahmedyuu said:
I installed this ROM successfully but when I tried to go into my custom recovery "Orangefox"
The device stands on the logo and restarts itself and keeps the device logo
Please any help on this sir
Click to expand...
Click to collapse
Same problem here, a bump for help!
ahmedyuu said:
I installed this ROM successfully but when I tried to go into my custom recovery "Orangefox"
The device stands on the logo and restarts itself and keeps the device logo
Please any help on this sir
Click to expand...
Click to collapse
I had the same problem. To fix the bootloop I followed this tutorial:
On my PC I had to replace the command "python --version" with "py --version" and later instead of "python -m pip pyusb pyserial json5" I had to run "py -m pip pyusb pyserial json5"
After that I replaced the stock software.
Then enable USB debugging, then do the following:
adb devices
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery TWRP.img
fastboot reboot recovery
You can find vbmeta.img either in the stock firmware or in the rom zip package.
When you are in recovery mode you have to flash Magisk.zip to prevent stock rom from replacing the recovery. After that reboot to recovery, then you can flash the rom.