Related
LAST PERSONALLY Verified as working and "stable"*: GAPPS, 8/19 GAPPS
First and foremost, I'm simply compiling this for the OnePlus 6 and am making some small tweaks to include Opengapps and not only Go Apps in the builds.
The parent for this by phhusson can be found at [Resurrection Remix] [Unofficial] [2018-05-19] Phh-Treble
Next the most important information where to get the most current build of the ROM: Google Drive
For now I suggest the version ending in -go such as: 'rr_6_1_180616_system-arm64-ab-go.img.xz' as the '-gapp' is in development, I expect a number of builds over the next few days as I finally the build scripts and then the rate to tapper off to every two weeks or as there are changes that seem to warrant it, I'm not building nightly for no reason, as RR 6.1 is reasonable stable at this time.
Note: Attached (build.sh) is the build script currently being used, it is a work in progress. and will be updated in case you more regular builds. You will need 12GB of Ram Ubuntu 16.04+ (I'm using 18.04 now, but I started with 16.04) and at least 360GB (SSD recommended) to build, and upto 6 hours for the initial run and then 2 for ever additional run.
Many thanks to phhusson for allowing me to post this based off of his work.
Changes, when I have something to report. Not all build will:
The 7/7 build includes a number of patches recommended by DocRambone.
Overlay support to force Apps fullscreen, Under Display->Advanced
Some cleanups to the UI for the round corners
Better LED support
The 7/8 build is the same as 7/7, but includes July security patches, I built it in order to match the official release.
The 7/24 build is again to match the official release
The 8/19 build is again to match the official release, note regression in status bar height I'm looking into.
Second post: will have details on what is working and not
Third Post: will have full instructions on installation, backup restore based on my experiences
* Stable is relative, for me if I consider it usable from day to day it is stable.
As of 8/11/2018
In the GAPPS version
Working:
Fingerprint
Camera (Front and Back) + Flash (Also got the OnePlus Camera working*)
Speaker
Wifi (Some cut outs seen, this is not unique to this ROM and is dependent on the access port some are worse than others, no clue why)
Bluetooth
GPS
Brightness
Slider for Notifications as of 6/18 build
Mobile Data/Voice (tested dual SIMM is working)
Google Apps
Root (using magisk 16.3), told but have not personally tested that 16.4 without changes works as well
Ambient (works serious effect on battery see next post)
Full Screen Aspect Ratio Display->Advanced 7/07/2018 build+
More fully functional LED Improved for at least mounting USB sticks in 7/7 build
USB Host - Fixed for at least mounting USB sticks in 7/24 build
Bluetooth Phone audio is on the local headset. - Fixed in 7/24 build
Seems working NFC working 5.1.11 Vendor and Boot, not working with previous to 5.1.9 Vendor and Boot I have nothing to connect to to fully test
Not Working:
The Notch hides content (need to wait for P)
Unknown:
Camera Quality: I do little with the camera and am no photographer, so I can say nothing about quality, only it installed and took pictures
VaSU# said:
volte kinda works you can receive messages and calls and can send messages but cant call "out"
Click to expand...
Click to collapse
Please let me know if anything is missing, or needs to be added
Instructions to flash, backup ...
WARNING: With 5.1.8 I had no WIFI, so I suggest sticking to 5.1.6 to 5.1.7 FOR THE MOMENT
Instructions to flash, backup ...
Total time required about 90 minutes
Pre-Reqs:
First and foremost:
Start with at least 5.1.6 (or greater, as of writing 5.1.7 was the lastest), there are Treble fixes in 5.1.6 we need.
Second
verify you have a good USB cable (the Red one shipped with the phone is best)
Three
download the oneplus drivers and abd
- USB Drivers: OnePlus 6 USB Drivers for Windows
- ADB/Fastboot: ADB/Fastboot latest mini
Install both to your local system
Four
Download the latest TWRP (get both the img and zip files)
TWRP for OnePlus 6
Five
Download the files(Treble OP6 Files 5.1.6) from:
GUIDE] How to flash Treble roms on OnePlus 6
Extract and keep: vbmeta.img (if you are on 5.1.X where is the boot version you can keep the boot.img as well, if not discard).
Six
Download the lastest Oxygen OS ZIP and bootloader from:
[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates
As of writing this is:
5.1.6 full image: OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip
5.1.6 boot: OnePlus6Oxygen_22_OTA_010_all_1806070151_boot.img
Seven
Download Device ID:
Device+ID APK
Eight
Download Magisk for Treble:
Magisk modified for treble
Since as of 6/2018 the default magisk does not support Treble we need a special version I suggest: Magisk-v16.3-factory-faizauthar12-20180406.zip as teh latest I could find with support.
Nine
Recommended download fastboot installable 5.1.6 (or latest build):
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Ten
Include Overlay/Ambient Display.
Download APK at: [Overlay] Enable Night Light, Auto-Brightness, Ambient Display & more on Treble ROM
Eleven
OnePlus Camera:
OnePlus Camera APK's
Finally
Download RR 6.0 for Treble compiled after 7/08/2018:
Either download the gapps or go version (gapps is still a work in progress when I wrote this)
ROMs Google Drive
Getting Ready:
WARNING: you will loss all data on your phone, backup anything you want or need, first.
Make sure you can get to fastboot (enable "Advanced Reboot" in developers options and make sure that you can enter on a reboot by pressing volume-down and power at the same time)
Make sure you are on 5.1.6+ (5.1.6 was the latest firmware upon writing this)
Remove Any security you have set (just to be safe)
Reboot to fastboot (bootloader)
run:
Code:
fastboot oem unlock
"You will be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection, allow your device to reboot"
Backup EFS
If you have not already I'd recommend backing up EFS (to do so you need to be rooted, or else use TWRP):
Preferred, if rooted simply open a terminal and run:
Code:
su
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
Copy these files someplace safe!
If not rooted reboot to fastboot (bootloader):
Ensure that the latest twrp is in the same directory as fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot) and run (3.2.1 was the lastest as of writing this):
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select backup
select only EFS and Modem
enter a meaningful name
swipe to backup
click "Reboot System" -> "Do not Install" for TWRP if asked.
You can now locate the backup under /storage/TWRP/BACKUPS and move it to a safe location off the phone.
Backup the Phone
Recommended if you care: Backup your entire phone using TWRP as well:
Ensure that the latest twrp is in the same directory as fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot) and run (3.2.1 was the lastest as of writing this):
- fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select backup
Select Everything except EFS and Modem
enter a meaningful name
swipe to backup
click "Reboot System" -> "Do not Install" for TWRP if asked.
You can now locate the backup under /storage/TWRP/BACKUPS and move it to a safe location off the phone.
Installing RR:
Finally we are ready to install RR (or any other Treble ROM), on the OnePlus 6. You will need a build from 6/7/2018 or later to have the required Vender-Hal to be present.
You will need to locate and install the AB version for the OnePlus 6.
Note: I'm using RR from 6/13 as the base for the guide: system-arm64-ab-gapps.img
SEE FIRST POST FOR CURRENT DOWNLOAD LOCATION I compiled this using phhusson's (Orginial Build Scripts)
instructions and a bit of setup on Linux. However most Treble base ROM's should work so long as they are from after 6/7/2018 in a similar manor.
* Remember this will wipe your device and you will loss all data *
First
boot in to fastboot (bootloader):
We need to go back to TRWRP and wipe internal storage and data to be safe, as the -w option to do so when flashing is not working for me.
- fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select Wipe
Advanced Wipe
Select Cache, Data and "Internal Storage"
Swipe to Wipe
Click back until you are at the main menu
Click on Reboot
Click on Bootloader -> "Do not Install" for TWRP if asked.
Second
Flash the new ROM:
Flash vbmeta.img to remove validation
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
To be safe flash a default boot image (5.1.6 in this case)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Next reboot into recovery (you need to do this with volume down +Power, or selecting from bootload):
In stock recovery select English
Select Wipe Data and Cache
Reset system settings->yes->done
Wipe Cache->Yes->done
Erase everything->Thiscan not be undone, continue->done
back
Advanced
Reboot to fastboot->Reboot to fastboot
Now flash a the new ROM:
- fastboot flash system_a system-arm64-ab-gapps.img
- fastboot flash system_b system-arm64-ab-gapps.img
Three
reboot:
Code:
fastboot reboot
You will see the "andorid" boot screen (this is different that the Oxygen one) and being the first boot it could take a while. If you see no boot screen or it does not boot (give 10 minutes), then you likely need to repeat these steps again. If you boot into RR then continue.
You may get a Vender image mistake error ignore it it only appewars on boot.
Skip the Setup by clicking all four corners top left->top right->bottom right->bottom left (it my take more than one try), at this point you have no networking, that is what we want.
Suggestion make backup here as you have a working OS! -- Instructions to follow
Four
Move over required files: You now have RR installed and working:
Enable developer mode and then enable Advanced Reboot
Then copy over gapps-nano, Device+ ID.apk, magisk-manager apk and magisk installer zip to the phone
To get the magisk manager you need to extract it from the zip as I cloud not get the normal one to install. Extract the zip: Magisk-v16.3-factory-faizauthar12-20180406.zip copy common\magisk.apk to the phone
Five
Deal with: "Play Services not Certified by Google":
Install Device+ID (APK downloaed above) and Open
Once done open the second line shows the GSF ID for this device
Android Register GSF
Login using a gmail account (I suggest the one you use for the playstore)
Enter the GSF in the field, now we wait about 5 to 10 minutes for it to propigate
Reboot the phone as we want paly services to start fresh
First add a wIFI network.
Critical do not let any apps update until you have registered playstore, so if you see a notification saying downloading, select and click pause. Doing so with the updated 6/17 paystore resulted in a black screen where you would enter your password, no know work around other than reset if this happens.
click on playstore it should now start
Now login to your account and you should be go (it may take more than one attempt no idea why).
Now enable the update if previously paused
Update all Apps from the playstore before continuing, this may take a while give it 10 minutes
Optional: If you want remove Device+ID now (but I leave it as it is an easy way to get information).
You now have a working Playstore, if you have hung downloads then you may need to clear the cache for play services and the playstore I assume the unregistered might be the cause of them getting messed up.
Five
Install magisk:
Ensure you copied magisk zip and also the magisk manager apk to your phone, do not open, but click Done
Install the magisk manager, by locating the file in filemanager and selecting it.Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Install
Select the magisk zip from the filesystem and flash
clear cache
Reboot->System (If asked about installing TWRP swipe to install)
Allow the phone to fully boot
Suggested: Reboot the phone
Suggested: disable checks for updates as 5.7 does not work with this build.
Root is now setup.
Six
Installer th onPlus camera:
Many people want the one plus camera, copy the apk downloaed above to the phone.
Open and install via a file manager
Seven
resize Data (as it will be only 11GB), the partitioon will be larger, depending on your devide se we will use TWRP and resize2fs to grow it.
Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Advanced->Terminal
Code:
resize2fs /dev/block/sda17
Reboot System
Eight
Recommended, make a backup of your hard work:
Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select backup
Select Everything except EFS and Modem (as I'm unsure exactly which you need)
enter a meaningful name
swipe to backup
click "Reboot System" -> Swipe to reboot
Once back in RR copy the backup off the phone
Eight
Start using your OnePlus 6 with RR 6.0, rooted and with GAPPS
Nine
Upgrading:
Upgrading is simply replacing the system partitions and only these paritions (tested going from 6/13->6/16->6/17 builds)
Boot into fastboot (advanced reboot options)
Now flash the new system files:
- fastboot flash system_a new_system-arm64-ab-gapps.img
- fastboot flash system_b new_system-arm64-ab-gapps.img
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select Wipe
Advanced Wipe
Select Cache (and only Cache)
Swipe to Wipe
Reboot System
Ten
Restoring a Backup from TWRP
*This is a work in progress I can not work out how to do so safely*
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select Restore
Select the backup
Select Everything (other than EFS and Modem!)
Got to the main menu
Select Wipe
Advanced Wipe
Select Cache (and only Cache)
Swipe to Wipe
Reboot Fastboot
Eleven
Night Light, Ambient Display, requires Root:
My suggestion is not to do this if you care abut battery as I've seen major drain (even with Ambient display disabled, testing this).
Copy the apk downloaded framework-res__auto_generated_rro.apk to /vendor/overlays
Code:
mount -o rw,remount -t ext4 /vendor
cp <location of file> /vendor/overlay
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
Reboot
Comments:
TWRP does not boot if flashed onto RR (the TWRP logo appears but it will not boot), this is currently only go to protect you from using the OnePlus Recovery and messing up RR. Flashing TWRP does not affect booting into RR.
TWRP DOES handle encryption without an issue, even a wrong first pin is not an issue
TWRP making a backup of Treble ROM, backup everything for now: Data, Boot, System, System Image, Vendor, Vendor Image.
If you have problems with hung downloads from the Playstore: Pending hung PlayStore
Wifi can be flaky (appearently this is a more general issue as even stock had some issues, I fixed them by only using either 2.4 or 5Mhz wireless, if I had both active I had constant disconnects.
Worst case, to recovery, back to Oxygen 5.1.6 if you end up in a boot loop stuck booting to rtecovery, etc:
- flash-all.bat
Reboot into recovery (you need to do this with volume down +Power, or selecting from bootload):
In stock recovery select English
Select Wipe Data and Cache
Reset system settings->yes->done
Wipe Cache->Yes->done
Erase everything->This can not be undone, continue->done
back
Advanced
Reboot to fastboot->Reboot
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Copy the Oxygen full ROM back to the phone
Code:
adb push OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip /sdcard
In TWRP
Install
Select OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip
Go back to the root and select Advanced Wipe
Select Wipe
Advanced Wipe
Select Cache, Data and "Internal Storage"
Click on Reboot->Recovery (select Do not Install)
English
Wipe Cach and Data
Wipe Everything
Reboot
The phone will reboot same as the day it was made
If it does not then please refer to:
Mega Unbrick Guide for A Hard Bricked OnePlus 6
Note: Always boot fully at least once (I suggest twice and the first one is configuring android) before trying any steps above again.
Best of Luck, see a typo let me know
ERIC
thank you for this
[emoji102][emoji102][emoji102][emoji102][emoji102]
Sent from my ONEPLUS A6003 using Tapatalk
Thank you for putting so much hard work on this. Really much appreciated, will give it a try.
Might be a noob question, but due to treble, is the camera quality the same with the OnePlus app?
saintxseiya said:
Might be a noob question, but due to treble, is the camera quality the same with the OnePlus app?
Click to expand...
Click to collapse
No.
Great rom, I especially like the fact that I can choose to install without gapps (prefer fdroid). One thing that is missing is ambient display, hopefully it will be fixed sooner or later.
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Abaddon said:
No.
Click to expand...
Click to collapse
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
same quality here
Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
Never said anything about results, only that it could be installed and works, (takes pictures), personally I do little with the camera and am not photographer, but it can be installed (link above) and installed.
Updated the working to remove any confusion.
Maibol said:
same quality here
Click to expand...
Click to collapse
Could you post some comparison pics? Including portrait shots.
Would be awesome.
saintxseiya said:
Could you post some comparison pics? Including portrait shots.
Would be awesome.
Click to expand...
Click to collapse
sorry bro celebrating today with the family too much beer .....
So seeing this not even a month after the release of the op6 makes me happy and hopeful that we get a fully working RR-OS for the OP6 in the near future !
Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
because Oneplus doesnt release blobs for camera
Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
It will never be the same as OOS stock. Because aside from there is no device tree provided by OnePlus, they will never release the camera blobs due to licensing issues. Once we get a stable and proper gcam port. It'll be better than the stock OOS cam or close
is a beautiful Rom, will there be an adaptation for twrp? I have to use the gapps, because at the go version Wear OS does not work. and in the gapp version would be nice if the smartbar was running. Unfortunately, the kill app does not work ( I can not use xposed, then my bank app will not work anymore
unix2208 said:
is a beautiful Rom, will there be an adaptation for twrp? I have to use the gapps, because at the go version Wear OS does not work. and in the gapp version would be nice if the smartbar was running. Unfortunately, the kill app does not work ( I can not use xposed, then my bank app will not work anymore
Click to expand...
Click to collapse
TWRP not for now as treble is build as an image, but you should be able to flash using twrp just switch to img (though I have not tested that).
The GApps version is posted the 6/18 is working great, see second post.
As for Banking I'm unsure if any Treble based ROM passed the checks, as with or without root, as they appear as unsigned.
As for smartbar, I'll give it a try when I get a chance, as I do not use it personally.
ERIC
So safetynet won't pass?
This version of TWRP works on the Lenovo TB-X505F (wifi).
For the TB-X505X, see this thread. For the TB-X605F/L, see this thread.
For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC.
Code:
#include <std_disclaimer.h>
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Working:
AFAIK, everything is working including:
data decryption
MTP
Known issues:
time not adjusting for Daylight Saving
OTA (for a workaround see this post)
Before installing TWRP
Before you install TWRP, upgrade your tablet to the Android 9 (Pie) or Android 10 (Q) stock ROM.
This tablet shipped with Android 8 (Oreo), in which the bootloader did not allow unlocking. When you tried to unlock the bootloader, it gave this error message:
Code:
fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Installation
It is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download magisk.apk to your MicroSD or OTG device. Get the latest Magisk apk file here. Rename the filetype from apk to zip (for example Magisk-v22.0.zip)
if your bootloader is already unlocked, go to step 4. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot oem unlock-go
fastboot reboot
flash the twrp image:
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
if you haven't loaded Magisk yet, go to step 6. If you have already loaded Magisk, you can just reboot and you're finished:
Code:
fastboot reboot
adb reboot recovery
load Magisk (step one): reboot to recovery. Do not reboot into the system, because it will over-write TWRP with stock recovery. If that happens, go back to step 4 and start again. When you issue the reboot command (below), you have to immediately press the button combination to reboot to recovery (TWRP). Here are the steps:
issue the reboot command:
Code:
fastboot reboot
immediately press and hold all three buttons (Pwr+VolUp+VolDown). The tablet might reboot twice. Release all the buttons when you see the TWRP screen, or hear your PC acknowledge that ADB is connected.
load Magisk (step two): flash Magisk. In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the "Reboot System" button
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
01/03/2023 - bug fix: data partition again backs up and restores correctly
20/01/2023 - add TW_EXTRA_LANGUAGES and TB_X505F_S001149_221115_ROW kernel (credit to @Tonyha7 )
30/12/2022 - add system partition to AdvancedWipe (TB_X505F_S001147_220830_ROW firmware only)
15/11/2022 - TWRP 3.7.0-0 update
- support for TB_X505F_S001147_220830_ROW
18/12/2021 - TWRP 3.6.0-0 update
- support for A12 decryption (keymaster)
27/03/2021 - TWRP 3.5.1-0 update
- change to landscape mode for tablets
01/01/2021 - TWRP 3.5.0-0: initial release
Downloads
TWRP 3.7.0-0 for X505F: twrp-X505F_11.img (for TB_X505F_S001147_220830_ROW and above)
TWRP 3.6.0-0 for X505F: twrp-X505F_11_2021.img (for earlier stock ROMs)
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
https://github.com/Yahoo-Mike/recovery_device_lenovo_X505F/tree/android-11.0
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
Contributors
Yahoo Mike
Tonyha7
Last Updated 2023-03-01 (fix /data backup/restore)
Created 2021-01-01
reserved
Thanks for useful post,
Possible to reboot into recovery from fastboot?
zubair1836 said:
Thanks for useful post,
Possible to reboot into recovery from fastboot?
Click to expand...
Click to collapse
Not that I know of. The bootloader accepts the command fastboot reboot recovery, but boots to system anyway.
Hello there, I've been looking how to install this on my slow tablet for almost like an hour. Could there be some tutorial or extended explanation to the process and installation, I'm such a noob, sorry.
This worked for me. Thank you for your effort and the TWRP!
Worked for me too - many thanks!
Can't wait for a custom ROM!
TWRP Recovery Installation Steps
1. Download android platform tools
2. Unlock developer mode on the M10
3. Enable USB debugging on the M10
3. OEM unlock enable on the M10
4. XDA download TWRP copy to sd
5. Download Magisk app (from Github!!! johnwu), change extension to .zip
6. Adb to fastboot
7. fastboot flash recovery [filename.img]
8. Turn off device
9. Turn on device holding all 3 buttons, release when see Lenovo splash screen
10. In TWRP find Magisk zip
11. Install Magisk
Stock ROM Recovery
1. Download qualcomm drivers 64 bit install
2. Download Lenovo recovery and image tool windows app from Lenovo support website
3. Fastboot oem edl
4. Turn off M10
5. Start recovery windows app, wait till instructions
6. Hold volume up (up is the side of the button closest to the front camera) and insert cable
7. Release button after windows app detects device
8. Troubleshoot by checking windows device manager for the M10 appears as a Qualcomm device
I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.
Heeni said:
I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.
Click to expand...
Click to collapse
Confirmed working normally.
zubair1836 said:
Confirmed working normally.
Click to expand...
Click to collapse
Many thanks.
Thank you! TWRP is working fine!
Stupid me flashed before I installed the Android 10 OTA, so I had to temporarily go back to stock recovery. Unfortunately beamingbadger's method didn't work for me.
This is how it worked for me:
Download the OTA via Lenovo's "Rescue And Smart Assistant"
The stock recovery image will be in the Download folder (default path: C:\ProgramData\LMSA\Download\RomFiles) called "recovery.img"
Flash the recovery.img the same way as you would with the twrp img (adb reboot bootloader -> fastboot flash recovery recovery.img)
fastboot reboot
Install OTA
Flash TWRP recovery + Magisk again (follow the steps from the first post, skip bootloader unlock)
The method I use to install OTAs is:
open Magisk App
select "Uninstall Magisk", then the "Restore Images" option
reboot to Android (you will have no root access and stock recovery is restored)
apply OTA
re-flash twrp and install Magisk
NOTE 1: if you've unencrypted your data partition, it will be re-encrypted by this process.
NOTE 2: the new Magisk App (v22) can be installed in TWRP by renaming the *.apk to *.zip. See the new install instructions.
What's involved with running gsi ROMs on this device? It's got the same SoC as my Samsung Tab, which runs them well, so I'm assuming that this tab will also, but I'd like to know if there are any traps that I need to be aware of.
I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.
Heeni said:
I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
Click to expand...
Click to collapse
That's great news. Well done.
Heeni said:
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.
Click to expand...
Click to collapse
On my X605F I do this in twrp for a new GSI install:
format (not wipe) data partition. This is the option where you have to confirm by swiping.
factory reset. This clears the caches.
restore the stock boot and vendor partitions (from a backup I made). This is because Magisk can touch these partitions.
install the GSI system image
install anything else I need like disable_Dm-Verity, Magisk, gapps etc
I don't know what LOS R Mod //LiR does to your system. If it touches any other partitions, you should restore those to stock too.
Thanks for that. It gives me something to go on with. I've downloaded the stock ROM from lolinet, so I can grab the boot and vendor images from that.
I was able to try a couple of other GSI ROMs and I've settled on AndyYan's LineageOS 17.1 for now. The only serious installation issue I had - which I can laugh about in hindsight - was thinking I'd got myself into a very bad bootloop, when all I needed to do was let go of the power button after the Lenovo logo appeared.
On this tablet, there is no navigation capability at all (no navbar, no gestures, no setting to configure them) on installation, and I have to set it using adb. I suspect it goes back to PHH basic ROMs, but I don't feel like doing yet another install and testing right at this moment. Is this happening on the other tablets that you're testing, or is it unique to this one?
I just posted the v3.5.1 update to twrp.
It's also changed to landscape mode, as many of you requested.
Quick question, how do i apply new system updates with twrp installed? Should i not bother? Also, i forgot how to block check for updates!
will this allow flashing of stock roms download from lenovo recovery? ive been stuck on an ancient android 9 version because the ota updater fails.
NOTICE: crDroid 7.x (Android 11) is now in maintenance-only release mode, and will probably be End-Of-Life'd soon.
I'll be merging monthly Android Security Bulletins from upstream as they're available, and pushing releases, but they're blind builds at this point and I don't have time to troubleshoot them any longer.
Please consider updating to crDroid 9.x (Android 13):
crDroid 9.x XDA thread - OP 6/6T
{
"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"
}
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring you many of the best features in existence today.
Features
A quick glossary and primer on flashing & slots for A/B devices (like ours):
Spoiler: Show/Hide
- "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
- "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
- "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
- "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
- "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
- "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
- Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
- "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
- Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
- The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
- You can install multiple OTA zip packages one after the other without rebooting in both the stock recovery and TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
- We don't use what are called "delta" updates, which can patch existing partitions by block or by file; we use full filesystem images. So for us, OTA zip packages are really just a bunch of partition filesystem image files all wrapped up into a "payload.bin" with some extra instructions & metadata/checksums, so when you flash a ROM, it overwrites entire partitions at a time instead of individual files or filesystem blocks within that partition. So if you've changed something in a partition like system that gets written as part of flashing an OTA zip, all your changes are gone. The only thing in the system partition afterward will be what was in the system.img that was included in the ROM zip payload.
- The partitions that crDroid, LineageOS, and most custom ROMs for OnePlus 6 & 6T install to when flashing are boot (contains recovery & kernel), dtbo, system, and vbmeta. Some ROMs (like Syberia) build the vendor partition from source instead of just trying to work with the existing OEM vendor partition, so they flash that one too when installing. So you definitely need to flash stock vendor before switching from Syberia or another source-built vendor ROM to one like Lineage or crDroid that uses prebuilt.
- "Prebuilt vendor" vs. "source-built" vendor partitions: when first trying to get a custom ROM working on a new device now that we have separate system & vendor partitions & Google's "Project Treble" is a thing, you'll often just leave the contents of the vendor partition alone, because that's where all the proprietary or device-specific stuff lives (manufacturer specific hardware drivers & interfaces, any DRM libraries, custom frameworks & selinux policies for talking to them), and you make a compatibility map of what framework versions you're compiling against in system and what vendor version they're compatible with or supersede or you overlay updated things that should replace stuff in the vendor partition and keep it in system_ext instead. But you're also limited in that if there are some things in vendor, you CAN'T work around it from the ROM side (like, OnePlus Camera working correctly). So often, once the basics are functioning, the goal is to move to building the contents of the vendor partition from source, because you then have the freedom to fix problems with sepolicy, library/framework mismatches, etc. and make things work with the custom ROM instead of only working with the OEM's flavor of Android, and you can still copy individual pre-compiled files from the stock vendor filesystem image if needed (like if there's no open-source equivalent for some driver). Unfortunately, OnePlus SDM845 (enchilada & fajita, the OP6 & OP6T) never got a proper source-built vendor bringup by the LineageOS team (upon which crDroid is based). And while Syberia has had source built vendor in Android 11 (possibly 10?), it was only done for enchilada and NOT fajita, it's not trivial to unroll & commonize what they've done to apply to other ROMs, and some of the proprietary files they keep are imported from other similar devices/similar chipsets rather than source-built (presumably because the OnePlus ones are modified in a weird way that the open-source components can't hook into, but still not ideal). So for fixing a lot of the issues we still face with lack of things working quite right, or hardware features not available in custom ROMs (especially compared to newer OnePlus devices like the 7, 8, or 9 series), we're kinda stuck, because you can't just implement it against the stock prebuilt vendor.
- "Updating firmware" simply means we're flashing updated contents from the manufacturer into all the OTHER partitions besides the ones that the ROM OTA zip touches. There are another dozen or more of those, besides system & boot, that the full OxygenOS OTA zip would normally write to when you install it. The contents of the system partition in custom ROMs for our device are generally built against a particular version of OxygenOS (mostly the contents of the OEM vendor partition), and we've recently had an entire major Android version update come through from OxygenOS. Some people are still on older firmware that is now dramatically different than what the current custom ROM was intended to deal with (that is, all the stuff from OxygenOS is still based on Android 10, while the ROM is expecting compatibility with Android 11), and while I tend to agree that OxygenOS 10 was better than the current state of OOS 11, that doesn't matter when you're talking about installing the custom ROM over it. So please, keep an eye out in the release notes for what the recommended/required firmware versions are, and remember to update (procedure below).
Notes on custom recoveries with OxygenOS 11 firmware:
Spoiler: Show/Hide
- My understanding (from people smarter than me) is that the android-11 tree of TWRP is kind of a mess at the moment. I had made some 3.6.0_11-0 unofficial builds for both enchilada & fajita, but now they don't even seem to boot and I don't know why. TWRP android-11 tree refuses to mount the system partition where it belongs, and so addon.d OTA survival scripts don't work correctly any longer (which means you're hosed if you use NikGapps and update while booted from a TWRP version ending in "11-0", or if you have Gapps installed as a module and forget to reboot recovery & re-flash Magisk after flashing an update from TWRP).
- Trying to `fastboot boot` an Android 9-based TWRP image (like official 3.5.2_9-0 twrp.img) after installing OxygenOS 11 doesn't work, and will drop you into Qualcomm Crash Dump mode. Don't try to flash it as your boot partion, either.
- Meanwhile, stock LineageOS-based recovery, for all its shortcomings, has working fastbootd (aka "Userspace fastboot", which is what happens when you go to "Advanced", then choose "Enter fastboot" and the background colors go from purple to orange) that lets you flash both slots at once and unlocks critical partitions, while the OnePlus OEM bootloader (where it says "Fastboot Mode" in a square, then goes to the big green "START" text over white & dark red terminal font type text) can't be used to flash every partition to update firmware. Personally, I still think of it as wannabe-class and not a "real" custom recovery until the Lineage team 1) implements userdata decryption so you can manage files in /data and install updates from internal storage, and 2) allows for a factory reset the way we've always all understood it ("wipe data") WITHOUT nuking the contents of internal storage for no good reason ("formatting data"). But since crDroid is LineageOS-based, it's what we've got, and fastbootd is the best way to update firmware.
- With all that being said, since it's likely TWRP will only get MORE broken with Android 12 looming large, we're officially only going to support the built-in LineageOS-based recovery & OTA updater moving forward, until things change dramatically. If you want to try different custom recoveries (new builds of TWRP, OrangeFox, PBRP, whatever), feel free; and let us know how it works! But you're on you're own doing that.
- And on the system update side, applying system OTA updates seems to work correctly using the built-in Updater tool (Settings > System > Updater) both with new OTA releases and when choosing a file from "Local Installation". It executes OTA survival scripts correctly from /system/addon.d/ as well. I've personally tested and it correctly preserved Magisk v23 canary and MindTheGapps & NikGapps (on tester fajita) and MinMicroG "system" install package on my daily driver enchilada.
- ...however it has an accidental dependency on Magisk, due to things beyond my control upstream in the ROM. Whoops. Won't work if you don't have Magisk installed.
- FLASHING the old official TWRP 3.5.2_9-0 INSTALLER zip (or newer) on top of OOS 11.x DOES seem to work for now, but you need to be in a recovery environment that allows you to flash that installer in the first place (either by booting into an already-installed TWRP recovery before updating firmware, or by having an Android 11 compatible recovery boot.img to be able to `fastboot boot`). I don't know if it'll keep working in Android 12 or with crDroid 8.
- Look, if you really want to stick with TWRP, I don't blame you. I made bootable Android 11 compatible TWRP images for enchilada & fajita back at 3.5.2, and they still work well enough to `fastboot boot` them and then flash the old official 3.5.2_9-0 installer zips. Look at the attachments at the end of post #2. Also, you may want to try one of Siddhesh's custom recoveries; they probably work even better.
- TL;DR: I prefer TWRP too but current official releases are kinda broken and it's a chore to get the old version installed correctly, so built-in LineageOS-based recovery and Updater app are the supported way to install & update moving forward.
Prerequisites:
- Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
- Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
- Make sure you've downloaded the most recent full OxygenOS OTA installer zip (11.1.2.2), crDroid zip, matching crDroid boot.img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
- Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
Let's get started!
Updating firmware:
- Reboot to bootloader (with no USB cable connected).
- If you're not already using the stock (LineageOS-based) recovery, you'll need to `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
- Reboot to bootloader again (actually loads new bootloader that you just flashed).
- Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot stock recovery (white & purple on black color scheme, LineageOS logo in the middle).
- Tap "Advanced", then tap "Enter fastboot" (the already-selected first option), and color scheme should change from purple to orange.
- Follow the instructions for extracting the partition images from the official OxygenOS Updater full OTA zip you already downloaded using the "payload-dumper-go" utility, and flashing them one at a time, from https://wiki.lineageos.org/devices/fajita/fw_update, except for the very last command ("fastboot reboot").
- Since those instructions were updated for Android 12, and this is still Android 11-based & depends on using the OxygenOS prebuilt vendor partition contents, you'll also need to run fastboot flash --slot=all vendor vendor.img at the end of the list of commands in the linked LineageOS Wiki article above.
- If you're only updating firmware and were already on crDroid, you can just "fastboot reboot" which will go back to system. If this is part of coming to crDroid from another ROM, continue with the instructions below.
First time installing crDroid to your OP6T, coming from stock OxygenOS 11.x or another ROM (stock LOS-based recovery):
- Update to OxygenOS 11.1.2.2 firmware as described above if you haven't already.
- At the end of that procedure, (re)flash the crDroid boot.img to the `boot` partition of both slots, then reboot to recovery.
- Once you're rebooted into stock recovery (and lo, it was most purple), ADB sideload the crDroid installation zip. It might prompt you with "Install anyway?" on the phone, so don't just walk away from it.
- After the adb sideload has finished and the purple menu at the top comes back, hit the back arrow, then choose "Wipe data" (which WILL format internal storage -- you backed up as noted above, right?).
- Reboot to recovery (causes it to switch slots so any further installations will be on top of the slot that it just installed crDroid into).
- ADB sideload Magisk and/or any GApps packages you want to use. Please note that any time you install something via ADB sideloading, that the install file is technically renamed "sideload.zip" in transit by the ADB protocol, which might cause problems with installers that try to get too clever for their own good and alter behavior based on renaming the installation zip (like MinMicroG), so you might have to get even MORE clever with changing up installation order (like flash MinMicroG/GApps before Magisk so it won't install as a module. I dunno, talk to the package installer authors to get them to just build multiple packages or talk to the LineageOS devs to allow you to decrypt internal storage, copy stuff to internal storage via MTP, and install stuff from internal storage like a proper custom recovery (or at least maybe `adb push` to an unencrypted temp dir in the data partition).
- Reboot system.
- ???
- Profit!
OTA updating from Updater app with OOS 11.x firmware (recommended):
- This is the preferred way now. You just go to Settings > System > Updater, and... install an update. It processes addon.d OTA survival scripts correctly (tested with Magisk, MinMicroG, MindTheGapps, and NikGapps).
- Please note that there's currently an accidental depencency on Magisk being installed for this to work. I don't know if this will get fixed; that's definitely above my pay grade. This appears to have been fixed; huzzah!
- If you're trying to do a "Local Install" of the downloaded zip, please note you NEED to download on a computer & transfer to internal storage via USB cable; downloading files from an app on the phone associates it with a particular app thanks to Android 11+ Scoped Storage/SAF bull**** and will cause the file to be unreadable to the updater app process.
-- Old TWRP-based instructions below the fold (not recommended, but keeping for historical value... probably not accurate but I'm not going to update them more) --
Spoiler: Show/Hide
OTA updating from TWRP with OOS 11.x firmware:
You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
- Boot into TWRP recovery.
- Choose install, then select crDroid.zip, select additional zips, choose the TWRP installer zip, then slide to confirm flash.
- Reboot recovery.
- Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
- Please keep off of the grass, shine your shoes, wipe your... dalvik.
- Reboot system.
OTA updating from TWRP with OOS 10.x firmware:
- Don't. Update firmware to 11.1.2.2 first.
Reporting bugs:
I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
- Logs/screenshots/recordings or it didn't happen. Either the built-in Matlog app, or Syslog (free, open source, available on Play store and F-droid) are your friends here.
- I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
- I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
- Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.
It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
- didn't do a clean flash.
- aren't using the built-in kernel.
- are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
- immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
- are running decrypted.
- re-locked your bootloader for some reason... you're on a custom ROM; don't do that.
crDroid Website - Download here!
Donate - Support development!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_fajita/tree/11.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/11.0
- hardware/oneplus/ HALs: https://github.com/crdroidandroid/android_hardware_oneplus/tree/11.0-op6
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/11.0
Notes:
- crDroid 7.x (based on Android 11 & LineageOS 18.1) is no longer being actively developed, and I don't know how long someone on the dev team will keep merging monthly security updates. I'll try to keep building releases as long as there are updates, but all my limited time is focused on 9.x/Android 13 bringup now. We're in maintenance mode now, so any outstanding bugs are likely to just remain for perpetuity.
- Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
- Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
- Requires OOS 11.1.2.2 firmware (last official release). You should consider using an Android 10 ROM if you want to continue using Android 10 firmware.
- Tested against latest Magisk 24 (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 7.30 - May 2023 ASB release notes/changelog:
Changelog since v7.29 official release:
- Merged May 2023 Android Security Bulletin from upstream.
- Whatever the ROM dev team changed upstream in LineageOS and crDroid sources (not much? they're busy with Android 13).
- No changes to device-specific files.
Known issues:
Fajita-specific:
- If you use App Lock and/or Face Unlock, you'll likely run into issues with the FOD circle view starting to flicker randomly into view when it shouldn't be there (like it's not dismissing properly because one part of the security handling is fighting with or doesn't notify the other part that it's done and doesn't need to try to accept a fingerprint any longer). As a knock-on effect, this will also cause "Disable Night Light when FOD is visible" to freak out. I have one person who doesn't use either report that they were getting the random FOD circle anyway, so... if you're having this problem, please make sure you've given MatLog permission to manage files so that it can actually save logs to internal storage and capture a logcat & send it to me. Logs or it didn't happen, etc etc.
Common:
- No f2fs-formatted userdata support, sadly. Doesn't work with the prebuilt vendor partition required for this version of Android. You'll need to reformat data to ext4 before being able to boot (you can fastboot flash the crDroid 8.x or 9.x boot.img if you need a recovery that will let you choose).
- Google Hotword recognition might be kinda broken right now (on more than one custom ROM/device, not just us), and may cause some screw-up that prevents microphone audio from being allowed to go anywhere else if it's enabled.
- If you are stuck at "Android is starting..." looping endlessly, then press power, reboot to bootloader, and follow the instructions for updating firmware to OxygenOS 11.1.2.2 in the first post. It doesn't wipe data, you shouldn't lose anything.
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
Helpful links:
Download ROM
Android platform tools (adb & fastboot)
OxygenOS 11.1.2.2 Full OTA
Firmware update instructions (LineageOS Wiki)
(Please note that since crDroid 7.x/Android 11 for this device depends on the prebuilt OxygenOS vendor partition, you'll also need to add fastboot flash --slot=all vendor vendor.img to the list of commands in the instructions, just before the final fastboot reboot.
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)
Magisk (use latest)
Official TWRP 3.5.2_9-0 install zip (good luck)
MaWalla99 said:
Download: coming soon!
Click to expand...
Click to collapse
will this work with verizon?
Tomkumato said:
will this work with verizon?
Click to expand...
Click to collapse
I don't know since I'm not in the US.
MaWalla99 said:
I don't know since I'm not in the US.
Click to expand...
Click to collapse
Thanks
hi dev thanks for this rom i have successfully installed now, so there is a small info i like to share, that is installing any version of nikgapps apart from core nikgapps will result in bootloop or after even format the data, rom will boot but set up screen says it crashed, so i have installed with core version of nikgapps, rom booted successfully. that's all i have info to share now.
Hi dev ROM is working fantastically after installed all the application I used before, so thanks for it, it has enough customization thanks for it too.
Does NOT work on Verizon.
Hi devs i don't know the reason why this happening, the problem is when i change default launcher to nova launcher system ui automatically crashes, i can't specifically pinpoint the reason, but after launching the Paytm app for first time then paytm also crashed so i don't know what to do now. I have attached logcat from matlog so I think I have captured required info.
Thanks for the ROM. Where is the best place to get A11 gapps?
wangdak said:
Thanks for the ROM. Where is the best place to get A11 gapps?
Click to expand...
Click to collapse
nik gapps
hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks
autologic said:
hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks
Click to expand...
Click to collapse
1 - remove any passwords used to unlock screens - 2 - Backup all your important data, - 3 - Make sure you're on latest TWRP for Fajita and that you have latest OOS firmware, Gapps, TWRP installer and the ROM you want to install (zip files) copied to your "Downloads " directory, then reboot into recovery mode, - 4 - make sure you're on slot A (tap "reboot", tap slot "A" and reboot to recovery again), 5 - tap "Wipe", "advanced wipe" and select " Dalvick Art/Cache", " data" and "system", - 6 - swipe to wipe, 7 - tap "install" and select OOS, then swipe to install, 8 - install TWRP zip file, 9 - reboot to recovery, - 10 - install OOS on the second slot, 11- install TWRP, 12 - reboot to recovery, 13 - install the new ROM, 14 - tap "Wipe", advanced Wipe", "Dalvick Art/Cache" and "Data", 15 - swipe to wipe, 16 - install TWRP and reboot to recovery, 17 - install GAPPS, - wipe " Dalvick Art/Cache and reboot to system. That's it!
autologic said:
hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks
Click to expand...
Click to collapse
Boot in latest TWRP
Flash latest OOS 10
Flash CR Droid Zip
Flash Finalize.zip
Flash latest TWRP
Format data -type Yes to confirm
Reboot to recovery
Flash Gapps & Magisk (Optional)
Coming from a different version of Android, format data is recommended. Backup your data before you do this
Hi LiveDisplay color profile doesn't work ,setting a profile ,once you exit it resets back to normal again
Excellent ROM.
Thanks!
Hi dev i attached a video, in which i try to explain a problem, i can't pinpoint say amazon app only having this kind of problem, but i can say irresponsible of which app suddenly ui will have some kind of problem, it will appear from nowhere after that phone will hang and i need to restart the phone or else battery drains very fast. Kindly look into it. I reinstalled the rom two time freshly, even though it having same kind of problem presist, but i really loved one good feature that is finger print working fantastic even after reboot. OS is not crashing and reboot by itself, app also not crashing but suddenly some part is acting wired. Anyway i will upload the video for proof. I have attached gif file as per xda rules.
I have one last idea in my head instead of using app called migrate to take back up of application installed in my phone and restore to newly installed rom. Better use play store to install all app one by one and see there is any difference, i really love this rom thats why i reinstalling freshly again and again to see any difference possible
I've never used micro g a whole lot in the past but I'm all for it now due to the unbelievable amount of permissions apps ask for and while I love Android I'm no Google person either. I flashed 7.2 CrDroid two days ago and didn't install gapps. Then I went back in twrp and flashed micro g and fdroid from (stable) nano droid installer thread here on XDA. Going to read up more about micro g ..etc.. Op, if you are testing anything that has to do with this or anything feel free to msg me anytime. Ill run whatever through everything possible and gather logs if need be and send them to you properly. Thanks for this rom!! Great job!! Always loved CrDroid! Think i 1st used CrDroid back in 2013 or so. Fantastic rom!! My Screen time on 7.2 CrDroid.
flash713 said:
I've never used micro g a whole lot in the past but I'm all for it now due to the unbelievable amount of permissions apps ask for and while I love Android I'm no Google person either. I flashed 7.2 CrDroid two days ago and didn't install gapps. Then I went back in twrp and flashed micro g and fdroid from (stable) nano droid installer thread here on XDA. Going to read up more about micro g ..etc.. Op, if you are testing anything that has to do with this or anything feel free to msg me anytime. Ill run whatever through everything possible and gather logs if need be and send them to you properly. Thanks for this rom!! Great job!! Always loved CrDroid! Think i 1st used CrDroid back in 2013 or so. Fantastic rom!! My Screen time on 7.2 CrDroid.
Click to expand...
Click to collapse
Yeah I feel you I'm right where you are I think it's time to ditch Google and get a similar setup. Wonder if there's a thread in the 6t section yet? Google still my friend she'll teach me how to set it up, lol
WARNING + DISCLAIMER:
By installing this custom ROM, you are VOIDING your warranty. Also, installation of this ROM WILL TRIP KNOX PERMANENTLY, and render apps such as Samsung Health, Private Folder, (+ any apps that depend on KNOX) useless until you get the phone's motherboard replaced at the Samsung C/S center.
Although this software is released in the hope that it will be useful, there is NO GUARANTEE that installing this will not cause any harm to your device. I TAKE NO RESPONSIBILITY FOR ANY BRICKED DEVICES, DAMAGED HARDWARE, OR ANY OTHER PROBLEMS CAUSED BY THIS ROM. You are using this ROM at YOUR OWN RISK. I strongly recommend that you DO NOT continue to the steps below UNLESS YOU FULLY UNDERSTAND WHAT YOU ARE DOING.
While this ROM has been tested with South Korean variant of Galaxy A21s (SM-A217N, CSC changed from LUC->SKC), please keep in mind that it hasn't been tested on any other variant (such as A217F, A217M.)
Click to expand...
Click to collapse
I would like to express special thanks to all the developers who contributed to the LineageOS port for Galaxy Tab S6 Lite + all the other developers who contributed to sepolicy & hardware parts for Samsung SLSI (Exynos) devices. Porting LineageOS to A21s would have been much harder without them.
Click to expand...
Click to collapse
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser app is not installed by default. Installing Firefox or Chrome from Google Play is recommended
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6/U7, please use the recovery tar for U6/U7.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img. boot.img, dtbo.img, recovery(U5), recovery(U6), recovery(U7)
- ADB and Fastboot
- Odin
- Kernel Source
- Google Apps(Flame)
WARNING: A BUG WHICH CAN POTENTIALLY LEAD TO BOOT LOOP ON U7 WAS FOUND. IF YOU ARE ON U7, PLEASE DO NOT FLASH THIS ROM UNTIL THIS IS FIXED.
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
Changelogs:
2021-10-19: Initial Release (AOSP 12.0.0_r2)
2021-10-21: Updated to AOSP 12.0.0_r3
2021-11-03: Updated to AOSP 12.0.0_r13 & added U7 support
2021-11-22: Fixed graphics issue, fixed battery issue (when battery level sometimes dropped by more than 2-3% on reboot), and fixed force crash when choosing Battery Manager in Settings
2021-11-25: Updated to AOSP 12.0.0_r15, changed battery mechanism to make it more accurate
2021-11-27: Kernel GPU driver update (R33P0 -> R34P0), LTE is now enabled by default
2021-12-10: Updated to AOSP 12.0.0_r16, removed the annoying search box widget on the home screen
2022-01-01: EGL graphics driver update to improve performance, minor bug fixes related to some apps.
SCREENSHOTS:
{
"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"
}
EDIT: the boot issue has been fixed, and you can now download the ROM.
This is great!
Do you working on this ROM for A21s, or you working on LineageOS 18 A11, paralel with this ROM?
grccorps said:
EDIT: the boot issue has been fixed, and you can now download the ROM.
Click to expand...
Click to collapse
instead of fastboot can we sideload super,boot etc?
Zdivan said:
This is great!
Do you working on this ROM for A21s, or you working on LineageOS 18 A11, paralel with this ROM?
Click to expand...
Click to collapse
Yes. I am also working on Lineage 18. Actually, the source code for this ROM is based on the source code for the Lineage 18. (of course, along with some modifications)
NuzzaimStark said:
instead of fastboot can we sideload super,boot etc?
Click to expand...
Click to collapse
I'm really sorry, but it is not possible to adb sideload images.
i got this when type and enter "fastboot flash boot boot.img"
C:\Users\nussa\Downloads\platform-tools>fastboot flash boot boot.img
< waiting for any device >
nothing showing in phone log
grccorps said:
I'm really sorry, but it is not possible to adb sideload images.
Click to expand...
Click to collapse
I am a bit sad because gaming time screen is flickering... Grrcorps pls check in your phone
grccorps said:
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
It has been only 2 weeks since Android 12 came out, so there may be some instability / bugs. I will try to work it out as time goes by. Also, when Lineage 19 is released, I will try to port it too. (Shouldn't be too hard though, as Lineage is quite similar to AOSP)
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
The network is set to 3G by default, so in order to use LTE, you should go to Settings->Network and Internet->Internet and change the default network setting from 3G to LTE.
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser and Music/Video Player apps are not installed by default. Installing Chrome and YouTube music from Google Pay is recommended
The search bar on the home launcher is useless until "Google" app or "Google Go" app is installed.
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img, boot.img, dtbo.img (Download all three)
- Recovery(for U5) / Recovery(for U6) / Recovery(for U7: coming soon)
- Google Apps
- ADB and Fastboot
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
SCREENSHOTS:
View attachment 5436707View attachment 5436709View attachment 5436711View attachment 5436713View attachment 5436731
Click to expand...
Click to collapse
only 1 sim card is work or 2 sim cards is working ?
( A217F ) , EGY
NuzzaimStark said:
I am a bit sad because gaming time screen is flickering... Grrcorps pls check in your phone
Click to expand...
Click to collapse
I'm really sorry, but could you please tell me which game it is?
ayman9321 said:
only 1 sim card is work or 2 sim cards is working ?
( A217F ) , EGY
Click to expand...
Click to collapse
As of now, this ROM is for single sim variant...
grccorps said:
As of now, this ROM is for single sim variant...
Click to expand...
Click to collapse
how can i fix it or can you help me to make 2 sim cards work ?
i install pit file for my country from the csc.tar from the android 11 firmware but not work after i install the stock android 11 firmware that is says your sim cards is changed restart to apply the changes .
grccorps said:
I'm really sorry, but could you please tell me which game it is?
Click to expand...
Click to collapse
Watch my gameplay I screen recorded it
NuzzaimStark said:
Watch my gameplay I screen recorded it
Click to expand...
Click to collapse
It said EXPERIMENTAL.
This ROM is not good enough for daily driver.
Wait for new version or install Lineage 18, or continue use this rom for testing.
Can anyone guide me how to root this rom?
Is this the s
grccorps said:
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
It has been only 2 weeks since Android 12 came out, so there may be some instability / bugs. I will try to work it out as time goes by. Also, when Lineage 19 is released, I will try to port it too. (Shouldn't be too hard though, as Lineage is quite similar to AOSP)
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
The network is set to 3G by default, so in order to use LTE, you should go to Settings->Network and Internet->Internet and change the default network setting from 3G to LTE.
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser and Music/Video Player apps are not installed by default. Installing Chrome and YouTube music from Google Pay is recommended
The search bar on the home launcher is useless until "Google" app or "Google Go" app is installed.
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img, boot.img, dtbo.img (Download all three)
- Recovery(for U5) / Recovery(for U6) / Recovery(for U7: coming soon)
- Google Apps
- ADB and Fastboot
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
SCREENSHOTS:
View attachment 5436707View attachment 5436709View attachment 5436711View attachment 5436713View attachment 5436731
Click to expand...
Click to collapse
Is this the stock Samsung Android 12 ROM?
NuzzaimStark said:
Can anyone guide me how to root this rom?
Click to expand...
Click to collapse
Patch the boot.img with magisk, same as how you root any other ROM
Maxis89 said:
Is this the s
Is this the stock Samsung Android 12 ROM?
Click to expand...
Click to collapse
No it is AOSP, it is written in the OP and also the screenshots are quite clearly AOSP
Do you need any logs or bug reports? If so, how to get them? Will the Lineage OS method work?
Add.: Gapps installation error: !Wrong android version detected. This package is for android 10.0 only. Your ROM is Android: 12. Blame, blind.
I tried rooting. There is no option ( root permission for usb debugging ) developer setting.
And I get these
NuzzaimStark said:
I tried rooting. There is no option ( root permission for usb debugging ) developer setting.
And I get these
Click to expand...
Click to collapse
Patch the boot.img with magisk app. Then reboot fastboot and flash the patched.img with fastboot.
This is, and will always be, the recommended way of installing magisk and getting root.
<Moderator Edit>: Combined four How To Guide threads into one.
Post #2 - LATEST FLASHING GUIDE FOR TWRP AND OTHER RECOVERY [Spes/Spesn] Redmi Note 11[WINDOWS-Only]
Post #3 - LATEST FLASHING GUIDE FOR TWRP AND OTHER RECOVERY [Spes/Spesn] Redmi Note 11[LINUX-Only]
Post #4 - UNIVERSAL ROM FLASHING GUIDE FOR ALL ROMS [Windows-Only]
Post #5 - UNIVERSAL ROM FLASHING GUIDE FOR ALL ROMS [Linux-Only]
{
"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"
}
Before following this guide, make sure you have followed the rom flashing guide below the post below or xiaomi.eu rom flashing guide.
If you have followed the flashing guide then you may continue.
Hello Amigos,
You can use this guide to install other recovery than TWRP also.(Other recoveries are listed in the guide itself)
Steps to install
First of all unlock bootloader of your device . Search net for more info.
After this install adb drivers from here: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/
Choose skip install for adb and install google drivers.
Connect your device in fastboot mode to your pc.
Go into device manager , right click on unrecognized android device , choose update drivers , let me pick from a list of drivers , select adb drivers , android bootloader interface and click install.
Then go to your custom rom download thread and check the date of rom file(In this case derpfest).
Download the latest platform-tools from the Android developer site and extract the zip in an easily accessible folder
Download the recovery image file
Restart your device to fastboot mode
Method 1:
Using this adb command if you have USB debugging active on your device:
adb reboot bootloader
Method 2:
- Turn off your device
- After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" with orange letters comes out
Method 3:
- Turn off yout device
- Press and hold Vol - button
- Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" with orange letters comes out
Connect your device to the PC
Open a cmd window in the folder where you extracted the binaries from the zip from step 1
Easy method: Open the folder, and without leaving it, type "cmd" in the address bar of the file explorer and press enter. Command promt will open a window directly in the folder location
Verify that your device is recognized by fastboot using this command:
fastboot devices
If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the drivers are installed correctly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.
- Because this device uses A/B partitions, there is no recovery partition as such, but it is integrated into the "boot" partition. So, first we must boot using the TWRP image.
Type this command in the cmd window, but don't press Enter yet, just type it and leave a space at the end:
fastboot boot_
Don't write the "_". This only indicates the space you should leave at the end.
This is how it should look when you write it:
Now, drag the image file (yourrecoveryhere.img) to the command window and drop it above the window. This will make you copy your exact location for convenience.
- The result should be this:
Code:
fastboot boot "C:\location\to\your\file\yourrecoveryhere.img"
Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.
Press Enter and wait a few seconds. The MI logo will come out, and then the TWRP logo.
DONE! You've started perfectly in recovery
From the device
NOTE: Only use these steps if you want to have TWRP installed semi-permanently
I said "semi-permanent" because when flashing any ROM, and knowing that the "recovery" is integrated into the "boot" partition, it will be lost after leaving TWRP, so you can follow these steps if you want to avoid loss of TWRP.
If you have easy access to a PC, you can be fine with the boot method. If you don't have easy access to a PC, you can follow these steps.
Method 1(For TWRP)
While in the TWRP menu, tap the Advanced button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default
You can use a USB OTG too
Now tap on the option "Install recovery ramdisk"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storages
"Swipe to confirm" and the TWRP installation process will begin
Method 2(For TWRP)
While in the TWRP menu, tap the Install button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too
Tap on the option "Install image"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
Method 3(For SHRP)
1. While booted in SHRP,under essentials section, tap advanced button.
2. Then click on flash current shrp button and click on tick button to flash shrp.
Method 4(For SHRP)
While booted in SHRP menu , tap flash button under the essentials section.
Copy the shrp image or zip file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too.
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash" if its img file or click on zip file of shrp , then click on tick button to flash.
Method 5(For OrangeFox)
1. While booted in Ofox, click on menu at the bottom right of the screen.
2. There you will see manage partitions, reboot , mount as such . The last thing in menu column you will
see will be more. Click on more, then below fix contents you will see flash current orange fox. Swipe to confirm flash.
Method 6(For OrangeFox)
While booted in ofox , tap files button at the bottom left of the screen.
Copy the ofox image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too.
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
Remember that with the three methods mentioned above you will lose root access (Magisk), so do not forget to flash it again. These steps are also valid to update TWRP or other recovery if you already had it previously installed.
Credits: NeoSDAP (Original Post)
Jabieff,dblenk9(TWRP)
I have just reposted here to circulate the great work.
TWRP Download:
A11/A12:
[SHARED][RECOVERY] TWRP 3.6.2 UNOFFICIAL STABLE [A11/A12] [Spes/Spesn] Redmi Note 11
Hello Amigos, TWRP v3.6.2 - UNOFFICIAL | Android 11. Updated: 30/03/'22 Download Link Changelog: • Shipping with prebuilt kernel • Sync with latest source • MTP fixed • NOTE: Flashing Guide: GUIDE If mtp not working or device not...
forum.xda-developers.com
[RECOVERY]TWRP 3.6.1 Spes Android 11 only STABLE [SHARED]
TWRP v3.6.1 - UNOFFICIAL | Android 11. Updated: 30/03/'22 ▪️Download Changelog: • Shipping with prebuilt kernel • Sync with latest source • Decrypted(Does not support encryption,so format data is necessary to use recovery for A12) Notes: •...
forum.xda-developers.com
[RECOVERY] Shrp Android 11 only STABLE Spes [SHARED]
SHRP - UNOFFICIAL | Android 11. Updated: 06/03/'22 ▪️Download zip ▪️Download img Known Bugs: • /Data Can't Be Mounted On MIUI • MTP Notes: • Flash .Zip As Normal Zip In Other Recovery • Use .Img Through Fastboot Like Other Recovery Credits...
forum.xda-developers.com
A12/A13:
[SHARED] - [RECOVERY] TWRP 3.7.0 UNOFFICIAL STABLE [A12-Only/Supports Flashing A13] Spes/Spesn Redmi Note 11
Hello Amigos, TWRP 3.7.0 | Android 12.1 Updated: 06/11/'22 Download Link Changelog: • Synced latest TWRP 12.1 source • Fixed Android 13 ROM flashing issue (source side) , supports a12/a13 decryption. NOTE: Flashing Guide: GUIDE If mtp...
forum.xda-developers.com
[RECOVERY] Shrp 3.1 Android 12/13 Only STABLE [SHARED]
SKYHAWK Recovery - UNOFFICIAL 3.1 Device: Spes/Spesn (Redmi Note 11/11 NFC) Released : 03/01/23' ▪️DOWNLOAD (Changelog : • Initial Unofficial Build • Sync Latest Source • Based on TWRP 3.7.0-12.1 • MTP Fix • Supports Android 13 decryption...
forum.xda-developers.com
[RECOVERY] Orange Fox Recovery Android 12/13 Only Stable Spes [SHARED]
OrangeFox Recovery R11.1_A12 - UNOFFICIAL | Android 12 Updated: 08/10/'22 ▪️Download • Synced latest OrangeFox sources • Supports Android 11/12/13 decryption • MTP working NOTE: Flashing Guide: GUIDE If mtp not working or device not getting...
forum.xda-developers.com
NOTE:
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can brick your device
If your rom mentions to use a specific recovery then use that instead
Enjoy !
Before following this guide, make sure you have followed the rom flashing guide below or xiaomi.eu rom flashing guide.
If you have followed the guide then you may continue.
Hello Amigos,
You can use this guide to install other recovery than TWRP also.(Other recoveries are listed in the guide itself)
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
Steps to install
Make sure you have the bootloader unlocked before you start. There are many guides on the internet for that.
From PC:
Download the latest platform-tools for linux from the Android developer site and extract the zip in an easily accessible folder
Download the recovery image file
Restart your device to fastboot mode
Method 1:
Using this adb command if you have USB debugging active on your device:
adb reboot bootloader
Method 2:
- Turn off your device
- After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" with orange letters comes out
Method 3:
- Turn off yout device
- Press and hold Vol - button
- Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" with orange letters comes out
Connect your device to the PC
Open a terminal window in the folder where you extracted the binaries from the archive from step 1
Easy method: Open the folder, and open a terminal in the folder itself. Terminal will open a window directly in the folder location
Verify that your device is recognized by fastboot using this command: fastboot devices If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the device is connected properly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.
- Because this device uses A/B partitions, there is no recovery partition as such, but it is integrated into the "boot" partition. So, first we must boot using the TWRP image.
Type this command in the terminal window, but don't press Enter yet, just type it and leave a space at the end:
fastboot boot_
Don't write the "_". This only indicates the space you should leave at the end.
Now, drag the image file (yourrecoveryhere.img) to the terminal window and drop it above the window. This will make you copy your exact location for convenience.
- The result should be this:
fastboot boot "home/user/location/to/your/file/yourrecoveryhere.img"
Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.
Press Enter and wait a few seconds. The MI logo will come out, and then the TWRP logo.
DONE! You've started perfectly in TWRP
From the device
NOTE: Only use these steps if you want to have TWRP installed semi-permanently
I said "semi-permanent" because when flashing any ROM, and knowing that the "recovery" is integrated into the "boot" partition, it will be lost after leaving TWRP, so you can follow these steps if you want to avoid loss of TWRP.
If you have easy access to a PC, you can be fine with the boot method. If you don't have easy access to a PC, you can follow these steps.
Method 1(For TWRP)
While in the TWRP menu, tap the Advanced button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default
You can use a USB OTG too
Now tap on the option "Install recovery ramdisk"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storages
"Swipe to confirm" and the TWRP installation process will begin
Method 2(For TWRP)
While in the TWRP menu, tap the Install button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too
Tap on the option "Install image"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
Method 3(For SHRP)
1. While booted in SHRP,under essentials section, tap advanced button.
2. Then click on flash current shrp button and click on tick button to flash shrp.
Method 4(For SHRP)
While booted in SHRP menu , tap flash button under the essentials section.
Copy the shrp image or zip file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too.
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash" if its img file or click on zip file of shrp , then click on tick button to flash.
Method 5(For OrangeFox)
1. While booted in Ofox, click on menu at the bottom right of the screen.
2. There you will see manage partitions, reboot , mount as such . The last thing in menu column you will
see will be more. Click on more, then below fix contents you will see flash current orange fox. Swipe to confirm flash.
Method 6(For OrangeFox)
While booted in ofox , tap files button at the bottom left of the screen.
Copy the ofox image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too.
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
Remember that with the three methods mentioned above you will lose root access (Magisk), so do not forget to flash it again. These steps are also valid to update TWRP if you already had it previously installed.
Credits: NeoSDAP (Original Post)
Jabieff,dblenk9(TWRP)
TWRP Download:
A12/A11:
[RECOVERY] TWRP 3.6.2 UNOFFICIAL STABLE [A12/A11] [Spes/Spesn] Redmi Note 11Hello Amigos, TWRP v3.6.1 - UNOFFICIAL | Android 11. Updated: 30/03/'22 Download Link Changelog: • Shipping with prebuilt kernel • Sync with latest source • Decrypted Notes: • Flash stock boot.img before flash twrp.img • Reinstall twrp...
forum.xda-developers.com
[RECOVERY]TWRP 3.6.1 Spes Android 11 only STABLE [SHARED]
TWRP v3.6.1 - UNOFFICIAL | Android 11. Updated: 30/03/'22 ▪️Download Changelog: • Shipping with prebuilt kernel • Sync with latest source • Decrypted(Does not support encryption,so format data is necessary to use recovery for A12) Notes: •...
forum.xda-developers.com
[RECOVERY] Shrp Android 11 only STABLE Spes [SHARED]
SHRP - UNOFFICIAL | Android 11. Updated: 06/03/'22 ▪️Download zip ▪️Download img Known Bugs: • /Data Can't Be Mounted On MIUI • MTP Notes: • Flash .Zip As Normal Zip In Other Recovery • Use .Img Through Fastboot Like Other Recovery Credits...
forum.xda-developers.com
A12/A13:
[RECOVERY] TWRP 3.7.0 UNOFFICIAL STABLE [A12/A13] Spes/Spesn Redmi Note 11Hello Amigos, TWRP 3.7.0 | Android 12.1 Updated: 06/11/'22 Download Link Changelog: • Synced latest TWRP 12.1 source • Fixed Android 13 ROM flashing issue (source side) , supports a12/a13 decryption. Flash instructions: • Download and...
forum.xda-developers.com
[RECOVERY] Shrp 3.1 Android 12/13 Only STABLE [SHARED]
SKYHAWK Recovery - UNOFFICIAL 3.1 Device: Spes/Spesn (Redmi Note 11/11 NFC) Released : 03/01/23' ▪️DOWNLOAD (Changelog : • Initial Unofficial Build • Sync Latest Source • Based on TWRP 3.7.0-12.1 • MTP Fix • Supports Android 13 decryption...
forum.xda-developers.com
[RECOVERY] Orange Fox Recovery Android 12/13 Only Stable Spes [SHARED]
OrangeFox Recovery R11.1_A12 - UNOFFICIAL | Android 12 Updated: 08/10/'22 ▪️Download • Synced latest OrangeFox sources • Supports Android 11/12/13 decryption • MTP working NOTE: Flashing Guide: GUIDE If mtp not working or device not getting...
forum.xda-developers.com
NOTE:
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can brick your device.
If your rom mentions to use a specific recovery then use that instead
Enjoy !
First of all unlock bootloader of your device . Search net for more info.
After this install adb drivers from here: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/
Choose skip install for adb and install google drivers.
Connect your device in fastboot mode to your pc.
Go into device manager , right click on unrecognized android device , choose update drivers , let me pick from a list of drivers , select adb drivers and click install.
Then go to your custom rom download thread and check the date of rom file(In this case derpfest).
Check the date of file.
Then go to xiaomifirmwareupdater.com and select rom archive and select your device.
Then MIUI downloads page will appear. type fastboot in search and look for a MIUI global version released
as the same or very close to the Custom ROM date (in this case it is this)
Download the fastboot version according to the date.
Go into the stock rom folder and double click on flash_all.bat(all data will be lost) .
Or open cmd in the folder and type flash_all.bat in cmd and hit enter.(This method allows to look for errors)
A cmd window will popup with fastboot commands automatically and after complete flashing of rom will close automatically. (approx. 20-25 mins)
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
Then follow the twrp flashing guide from here
Then flash the ROM according to the instructions.
NOTE:
Make sure to always extract and move the stock rom folder in root of C: drive (this helps avoid flashing errors)The path should look something like this:
C:\spes_global_images_YourVersionhere
Then flash the stock rom.
Clean Flashing a ROM:
I hope you have followed the entire guide above before doing this step.
Reboot to recovery.
Format data.
Flash ROM file.
Wipe Dalvik Cache.
Reboot and enjoy.
Everytime you do a clean flash, you must redo all the steps above.
If a rom does not include flashing instructions, it requires a clean flash.
If rom mentions clean flash and not wiping of anything else then dont be smart to wipe anything unecessary.
If you get a error like this: assert failed _dynamic partitions package_extract_file(dynamic_partitions_op_list) ERROR 1
Then re do this guide from start and re do all the steps in the guide and when it comes to flashing twrp, then use twrp 3.6.1 to flash rom(if your rom mentions to use a specific recovery then use that instead)
Always flash magisk after the first boot of your rom
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can brick your device
Enjoy!
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
First of all unlock bootloader of your device . Search net for more info.
Then go to your custom rom download thread and check the date of rom file(In this case derpfest).
Check the date of file.
Then go to xiaomifirmwareupdater.com and select rom archive and select your device.
Then MIUI downloads page will appear. type fastboot in search and look for a MIUI global version released
as the same or very close to the Custom ROM date (in this case it is this)
Download the fastboot version according to the date.
Go into the stock rom folder and right click in empty area then select open terminal here then type this command:
./flash_all.sh
A terminal window will popup with fastboot commands automatically and after complete flashing of rom will close automatically. (approx. 20-25 mins)
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
Then follow the twrp flashing guide from here
Then flash the ROM according to the instructions.
NOTE:
Make sure to always extract and move the stock rom folder in root of home directory (this helps avoid flashing errors)The path should look something like this:
home\spes_global_images_YourVersionhere
Then flash the stock rom.
Clean Flashing a ROM:
I hope you have followed the entire guide above before doing this step.
Reboot to recovery.
Format data.
Flash ROM file.
Wipe Dalvik Cache.
Reboot and enjoy.
Everytime you do a clean flash, you must redo all the steps above.
If a rom does not include flashing instructions, it requires a clean flash.
If rom mentions clean flash and not wiping of anything else then dont be smart to wipe anything unecessary.
If you get a error like this: assert failed _dynamic partitions package_extract_file(dynamic_partitions_op_list) ERROR 1
Then re do this guide from start and re do all the steps in the guide and when it comes to flashing twrp, then use twrp 3.6.1 to flash rom(if your rom mentions to use a specific recovery then use that instead)
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Always flash magisk after the first boot of your rom
Do not replace the recovery or try to update recovery that comes with roms. This can brick your device.
Enjoy!
Title: Windows-only
Prerequisites: Linux-based OS
What?
NeoSDAP said:
Title: Windows-only
Prerequisites: Linux-based OS
What?
Click to expand...
Click to collapse
edited thanks!
@LolFlasherNoob Please see the PM I just sent you and let me know your response.
@notBradPitt Please help us in the future by using the "Report" button near the bottom right corner of a post.
Thank you,
@roirraW "edor" ehT
after i just flash TWRP. can i just install the magisk there?
xiasanx said:
after i just flash TWRP. can i just install the magisk there?
Click to expand...
Click to collapse
What do you mean ?
Does this work on Android 11?
My last phone became a brick.
Waltuh said:
Does this work on Android 11?
My last phone became a brick.
Click to expand...
Click to collapse
what twrp ? yes
Twrp no mtp no detect SD card intall conecting pendrive with USB c yo USB adapter
luistro said:
Twrp no mtp no detect SD card intall conecting pendrive with USB c yo USB adapter
Click to expand...
Click to collapse
which twrp , sd card must be formatted as fat32. yeah mtp works check mtp fix link in twrp.sd detect work on my spes.
Hi, I have a remdi note 11 unlocked bootloader, flashed MIUI13 (android 12) and then fastbooted to twrp . From there I tried to flash TWRP 3.7 (for android 12) using Method 2 , it flashed ok but now phone only boots to fastboot , and when I do again fastboot boot twrp.img it goes to TWRP but says no OS installed.
Could you guide me on what I have ****ed up??
wasteoinc said:
Hi, I have a remdi note 11 unlocked bootloader, flashed MIUI13 (android 12) and then fastbooted to twrp . From there I tried to flash TWRP 3.7 (for android 12) using Method 2 , it flashed ok but now phone only boots to fastboot , and when I do again fastboot boot twrp.img it goes to TWRP but says no OS installed.
Could you guide me on what I have ****ed up??
Click to expand...
Click to collapse
AFAIK, this phone doesn't have a Recovery partition and TWRP has to be booted from Fastboot. Maybe that's what's causing the problem?
notBradPitt said:
AFAIK, this phone doesn't have a Recovery partition and TWRP has to be booted from Fastboot. Maybe that's what's causing the problem?
Click to expand...
Click to collapse
But in the guide which is for this phone it clearly states you can "semi-permanently¨ install TWRP. Booting from bootloader is no deal breaker for me, but know Im getting concerned about magisk and other stuff I want to install
wasteoinc said:
But in the guide which is for this phone it clearly states you can "semi-permanently¨ install TWRP. Booting from bootloader is no deal breaker for me, but know Im getting concerned about magisk and other stuff I want to install
Click to expand...
Click to collapse
Sorry for inconvenience! I suggest that you boot twrp 3.6.2 from fastboot and then flash 3.6.2 instead from method 2 as some MIUI roms and custom roms have problems with 3.7.0 which can brick your device. Hope that resolves your issue !
Regards,
LolFlasherNoob
LolFlasherNoob said:
View attachment 5812057
Before following this guide, make sure you have followed the rom flashing guide below the post below or xiaomi.eu rom flashing guide.
If you have followed the flashing guide then you may continue.
Hello Amigos,
You can use this guide to install other recovery than TWRP also.(Other recoveries are listed in the guide itself)
Steps to install
First of all unlock bootloader of your device . Search net for more info.
After this install adb drivers from here: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/
Choose skip install for adb and install google drivers.
Connect your device in fastboot mode to your pc.
Go into device manager , right click on unrecognized android device , choose update drivers , let me pick from a list of drivers , select adb drivers , android bootloader interface and click install.
Then go to your custom rom download thread and check the date of rom file(In this case derpfest).
Download the latest platform-tools from the Android developer site and extract the zip in an easily accessible folder
Download the recovery image file
Restart your device to fastboot mode
Method 1:
Using this adb command if you have USB debugging active on your device:
adb reboot bootloader
Method 2:
- Turn off your device
- After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" with orange letters comes out
Method 3:
- Turn off yout device
- Press and hold Vol - button
- Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" with orange letters comes out
Connect your device to the PC
Open a cmd window in the folder where you extracted the binaries from the zip from step 1
Easy method: Open the folder, and without leaving it, type "cmd" in the address bar of the file explorer and press enter. Command promt will open a window directly in the folder location
Verify that your device is recognized by fastboot using this command:
fastboot devices
If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the drivers are installed correctly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.
- Because this device uses A/B partitions, there is no recovery partition as such, but it is integrated into the "boot" partition. So, first we must boot using the TWRP image.
Type this command in the cmd window, but don't press Enter yet, just type it and leave a space at the end:
fastboot boot_
Don't write the "_". This only indicates the space you should leave at the end.
This is how it should look when you write it:
Now, drag the image file (yourrecoveryhere.img) to the command window and drop it above the window. This will make you copy your exact location for convenience.
- The result should be this:
Code:
fastboot boot "C:\location\to\your\file\yourrecoveryhere.img"
Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.
Press Enter and wait a few seconds. The MI logo will come out, and then the TWRP logo.
DONE! You've started perfectly in recovery
From the device
NOTE: Only use these steps if you want to have TWRP installed semi-permanently
I said "semi-permanent" because when flashing any ROM, and knowing that the "recovery" is integrated into the "boot" partition, it will be lost after leaving TWRP, so you can follow these steps if you want to avoid loss of TWRP.
If you have easy access to a PC, you can be fine with the boot method. If you don't have easy access to a PC, you can follow these steps.
Method 1(For TWRP)
While in the TWRP menu, tap the Advanced button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default
You can use a USB OTG too
Now tap on the option "Install recovery ramdisk"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storages
"Swipe to confirm" and the TWRP installation process will begin
Method 2(For TWRP)
While in the TWRP menu, tap the Install button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too
Tap on the option "Install image"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
Method 3(For SHRP)
1. While booted in SHRP,under essentials section, tap advanced button.
2. Then click on flash current shrp button and click on tick button to flash shrp.
Method 4(For SHRP)
While booted in SHRP menu , tap flash button under the essentials section.
Copy the shrp image or zip file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too.
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash" if its img file or click on zip file of shrp , then click on tick button to flash.
Method 5(For OrangeFox)
1. While booted in Ofox, click on menu at the bottom right of the screen.
2. There you will see manage partitions, reboot , mount as such . The last thing in menu column you will
see will be more. Click on more, then below fix contents you will see flash current orange fox. Swipe to confirm flash.
Method 6(For OrangeFox)
While booted in ofox , tap files button at the bottom left of the screen.
Copy the ofox image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too.
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
Remember that with the three methods mentioned above you will lose root access (Magisk), so do not forget to flash it again. These steps are also valid to update TWRP or other recovery if you already had it previously installed.
Credits: NeoSDAP (Original Post)
Jabieff,dblenk9(TWRP)
I have just reposted here to circulate the great work.
TWRP Download:
A11/A12:
[SHARED][RECOVERY] TWRP 3.6.2 UNOFFICIAL STABLE [A11/A12] [Spes/Spesn] Redmi Note 11
Hello Amigos, TWRP v3.6.2 - UNOFFICIAL | Android 11. Updated: 30/03/'22 Download Link Changelog: • Shipping with prebuilt kernel • Sync with latest source • MTP fixed • NOTE: Flashing Guide: GUIDE If mtp not working or device not...
forum.xda-developers.com
[RECOVERY]TWRP 3.6.1 Spes Android 11 only STABLE [SHARED]
TWRP v3.6.1 - UNOFFICIAL | Android 11. Updated: 30/03/'22 ▪️Download Changelog: • Shipping with prebuilt kernel • Sync with latest source • Decrypted(Does not support encryption,so format data is necessary to use recovery for A12) Notes: •...
forum.xda-developers.com
[RECOVERY] Shrp Android 11 only STABLE Spes [SHARED]
SHRP - UNOFFICIAL | Android 11. Updated: 06/03/'22 ▪️Download zip ▪️Download img Known Bugs: • /Data Can't Be Mounted On MIUI • MTP Notes: • Flash .Zip As Normal Zip In Other Recovery • Use .Img Through Fastboot Like Other Recovery Credits...
forum.xda-developers.com
A12/A13:
[SHARED] - [RECOVERY] TWRP 3.7.0 UNOFFICIAL STABLE [A12-Only/Supports Flashing A13] Spes/Spesn Redmi Note 11
Hello Amigos, TWRP 3.7.0 | Android 12.1 Updated: 06/11/'22 Download Link Changelog: • Synced latest TWRP 12.1 source • Fixed Android 13 ROM flashing issue (source side) , supports a12/a13 decryption. NOTE: Flashing Guide: GUIDE If mtp...
forum.xda-developers.com
[RECOVERY] Shrp 3.1 Android 12/13 Only STABLE [SHARED]
SKYHAWK Recovery - UNOFFICIAL 3.1 Device: Spes/Spesn (Redmi Note 11/11 NFC) Released : 03/01/23' ▪️DOWNLOAD (Changelog : • Initial Unofficial Build • Sync Latest Source • Based on TWRP 3.7.0-12.1 • MTP Fix • Supports Android 13 decryption...
forum.xda-developers.com
[RECOVERY] Orange Fox Recovery Android 12/13 Only Stable Spes [SHARED]
OrangeFox Recovery R11.1_A12 - UNOFFICIAL | Android 12 Updated: 08/10/'22 ▪️Download • Synced latest OrangeFox sources • Supports Android 11/12/13 decryption • MTP working NOTE: Flashing Guide: GUIDE If mtp not working or device not getting...
forum.xda-developers.com
NOTE:
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can cause problems such as reboots, apps crashing,etc as recovery is integrated into boot partition in which kernel
Click to expand...
Click to collapse
LolFlasherNoob said:
<Moderator Edit>: Combined four How To Guide threads into one.
Post #2 - LATEST FLASHING GUIDE FOR TWRP AND OTHER RECOVERY [Spes/Spesn] Redmi Note 11[WINDOWS-Only]
Post #3 - LATEST FLASHING GUIDE FOR TWRP AND OTHER RECOVERY [Spes/Spesn] Redmi Note 11[LINUX-Only]
Post #4 - UNIVERSAL ROM FLASHING GUIDE FOR ALL ROMS [Windows-Only]
Post #5 - UNIVERSAL ROM FLASHING GUIDE FOR ALL ROMS [Linux-Only]
Click to expand...
Click to collapse
I seem to be having issues with the bootloader unlocking, I am not receiving verification SMS to my number to associate my device and number with xiaomi account before using the unlock tool. I have tried the official help checklist, and have asked support, however even though my issue is about verification SMS for adding my number to my xiaomi account, they said that because I am trying to unlock the device, that basically they refuse to give me support at all, even with association of my number to mi account. Quite the FU from xiaomi! Any advice about how to receive the verification SMS so i can continue with unlocking the bootloader, or any additional methods for bootloader unlocking would be appreciated.
LolFlasherNoob said:
View attachment 5798031
Before following this guide, make sure you have followed the rom flashing guide below or xiaomi.eu rom flashing guide.
If you have followed the guide then you may continue.
Hello Amigos,
You can use this guide to install other recovery than TWRP also.(Other recoveries are listed in the guide itself)
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
Steps to install
Make sure you have the bootloader unlocked before you start. There are many guides on the internet for that.
From PC:
Download the latest platform-tools for linux from the Android developer site and extract the zip in an easily accessible folder
Download the recovery image file
Restart your device to fastboot mode
Method 1:
Using this adb command if you have USB debugging active on your device:
adb reboot bootloader
Method 2:
- Turn off your device
- After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" with orange letters comes out
Method 3:
- Turn off yout device
- Press and hold Vol - button
- Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" with orange letters comes out
Connect your device to the PC
Open a terminal window in the folder where you extracted the binaries from the archive from step 1
Easy method: Open the folder, and open a terminal in the folder itself. Terminal will open a window directly in the folder location
Verify that your device is recognized by fastboot using this command:
fastboot devices
If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the device is connected properly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.
- Because this device uses A/B partitions, there is no recovery partition as such, but it is integrated into the "boot" partition. So, first we must boot using the TWRP image.
Type this command in the cmd window, but don't press Enter yet, just type it and leave a space at the end:
fastboot boot_
Don't write the "_". This only indicates the space you should leave at the end.
This is how it should look when you write it:
Now, drag the image file (yourrecoveryhere.img) to the command window and drop it above the window. This will make you copy your exact location for convenience.
- The result should be this:
Code:
fastboot boot "home/user/location/to/your/file/yourrecoveryhere.img"
Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.
Press Enter and wait a few seconds. The MI logo will come out, and then the TWRP logo.
DONE! You've started perfectly in TWRP
From the device
NOTE: Only use these steps if you want to have TWRP installed semi-permanently
I said "semi-permanent" because when flashing any ROM, and knowing that the "recovery" is integrated into the "boot" partition, it will be lost after leaving TWRP, so you can follow these steps if you want to avoid loss of TWRP.
If you have easy access to a PC, you can be fine with the boot method. If you don't have easy access to a PC, you can follow these steps.
Method 1(For TWRP)
While in the TWRP menu, tap the Advanced button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default
You can use a USB OTG too
Now tap on the option "Install recovery ramdisk"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storages
"Swipe to confirm" and the TWRP installation process will begin
Method 2(For TWRP)
While in the TWRP menu, tap the Install button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too
Tap on the option "Install image"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
Method 3(For SHRP)
1. While booted in SHRP,under essentials section, tap advanced button.
2. Then click on flash current shrp button and click on tick button to flash shrp.
Method 4(For SHRP)
While booted in SHRP menu , tap flash button under the essentials section.
Copy the shrp image or zip file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too.
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash" if its img file or click on zip file of shrp , then click on tick button to flash.
Method 5(For OrangeFox)
1. While booted in Ofox, click on menu at the bottom right of the screen.
2. There you will see manage partitions, reboot , mount as such . The last thing in menu column you will
see will be more. Click on more, then below fix contents you will see flash current orange fox. Swipe to confirm flash.
Method 6(For OrangeFox)
While booted in ofox , tap files button at the bottom left of the screen.
Copy the ofox image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too.
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
Remember that with the three methods mentioned above you will lose root access (Magisk), so do not forget to flash it again. These steps are also valid to update TWRP if you already had it previously installed.
Credits: NeoSDAP (Original Post)
Jabieff,dblenk9(TWRP)
TWRP Download:
A12/A11:
[RECOVERY] TWRP 3.6.2 UNOFFICIAL STABLE [A12/A11] [Spes/Spesn] Redmi Note 11Hello Amigos, TWRP v3.6.1 - UNOFFICIAL | Android 11. Updated: 30/03/'22 Download Link Changelog: • Shipping with prebuilt kernel • Sync with latest source • Decrypted Notes: • Flash stock boot.img before flash twrp.img • Reinstall twrp...
forum.xda-developers.com
[RECOVERY]TWRP 3.6.1 Spes Android 11 only STABLE [SHARED]
TWRP v3.6.1 - UNOFFICIAL | Android 11. Updated: 30/03/'22 ▪️Download Changelog: • Shipping with prebuilt kernel • Sync with latest source • Decrypted(Does not support encryption,so format data is necessary to use recovery for A12) Notes: •...
forum.xda-developers.com
[RECOVERY] Shrp Android 11 only STABLE Spes [SHARED]
SHRP - UNOFFICIAL | Android 11. Updated: 06/03/'22 ▪️Download zip ▪️Download img Known Bugs: • /Data Can't Be Mounted On MIUI • MTP Notes: • Flash .Zip As Normal Zip In Other Recovery • Use .Img Through Fastboot Like Other Recovery Credits...
forum.xda-developers.com
A12/A13:
[RECOVERY] TWRP 3.7.0 UNOFFICIAL STABLE [A12/A13] Spes/Spesn Redmi Note 11Hello Amigos, TWRP 3.7.0 | Android 12.1 Updated: 06/11/'22 Download Link Changelog: • Synced latest TWRP 12.1 source • Fixed Android 13 ROM flashing issue (source side) , supports a12/a13 decryption. Flash instructions: • Download and...
forum.xda-developers.com
[RECOVERY] Shrp 3.1 Android 12/13 Only STABLE [SHARED]
SKYHAWK Recovery - UNOFFICIAL 3.1 Device: Spes/Spesn (Redmi Note 11/11 NFC) Released : 03/01/23' ▪️DOWNLOAD (Changelog : • Initial Unofficial Build • Sync Latest Source • Based on TWRP 3.7.0-12.1 • MTP Fix • Supports Android 13 decryption...
forum.xda-developers.com
[RECOVERY] Orange Fox Recovery Android 12/13 Only Stable Spes [SHARED]
OrangeFox Recovery R11.1_A12 - UNOFFICIAL | Android 12 Updated: 08/10/'22 ▪️Download • Synced latest OrangeFox sources • Supports Android 11/12/13 decryption • MTP working NOTE: Flashing Guide: GUIDE If mtp not working or device not getting...
forum.xda-developers.com
NOTE:
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can cause problems such as reboots, apps crashing,etc as recovery is integrated into boot partition in which kernel is also integrated.
Enjoy !
Click to expand...
Click to collapse
I seem to be having issues with the bootloader unlocking, I am not receiving verification SMS to my number to associate my device and number with xiaomi account before using the unlock tool. I have tried the official help checklist, and have asked support, however even though my issue is about verification SMS for adding my number to my xiaomi account, they said that because I am trying to unlock the device, that basically they refuse to give me support at all, even with association of my number to mi account. Quite the FU from xiaomi! Any advice about how to receive the verification SMS so i can continue with unlocking the bootloader, or any additional methods for bootloader unlocking would be appreciated.