Database Users

[HOWTO][FAQ] From untouched stock mocha to Shield ROMs

{
"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"
}
TUTORIAL - FROM UNTOUCHED STOCK MOCHA TO SHIELD ROMS | LINK TO FAQ
-------------------------------
Introduction​
Hi,
As I see even today new members in Mi Pad community looking for a way to have a decent Mi Pad on latest blobs on Nougat and leave KitKat MIUI, I think that a proper detailed tutorial is needed, as this transition needs a lot of steps.
-------------------------------
Before starting​
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this thread
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Therefore, if you have any problem at any step, read the FAQ and if your problem is not solved, you can ask in this topic or join Telegram group : https://t.me/MiPad1
I will not answer you if you haven't read the topic properly !
Finally, my tutorial is not optimised but is the safest way to avoid bootloops or other bricks. You can avoid steps if you consider some as not important, but I will not help you.
-------------------------------
Pre-requisites​
To make you MiPad shiny (or close to), you will need :
The "Mi Pad to Shield Starter Pack" (All-In-One ZIP or separate downloads). This pack includes :
mocha_repartition_1_2GB_RahulTheVirus.zip, allowing you to repartition the two partitions of original mi pad to only bigger one
mocha_repartition_stock_by_RahulTheVirus.zip, to restore original partitioning
BootBlobs-SHIELD-mocha.zip, to flash blobs from shield device and run ROM based on Shield Blobs,
BootBlobs-STOCK-mocha.zip, to restore your MiPad from Shield Blobs to Original Blobs.
twrp-3.2.1-0-mocha-shield.img, latest version (date of the upload) of TWRP for Shield Version
twrp-3.2.1-0-mocha-stock.img, latest version (date of the upload) of TWRP for Stock Version
15 seconds ADB installer
[RECOMMANDED] The "I Messed Up Pack" (All-In-One ZIP or separate downloads). in case of hard-bricking device. This pack includes :
Best Mi Flash Tool version for Mi Pad compatibility
Latest (date of the upload) Official China Dev MIUI ROM
-------------------------------
Summary​
STEP 1 : Boot TWRP via Fastboot : Begin here if you have stock Xiaomi recovery and never flashed TWRP yet on your MiPad.
STEP 2 : Repartitioning : Begin here if you never have flashed custom ROM on your MiPad.
STEP 3 : Flash Shield Blobs : Begin here if you already flashed custom ROMs on your MiPad.
STEP 4 : Flash Shield Based ROMs : Begin here if you already flashed Shield based ROMs ... Wait, why are you here ?
-------------------------------
STEP 1 : Boot TWRP via Fastboot​
Requires :
15 seconds ADB Installer installed.
twrp-3.2.1-0-mocha-stock.img from the Mi Pad to Shield Starter Pack in your ADB Folder (default : C:\ADB, will be created after the installation of 15 seconds ADB Installer).
Steps :
Shutdown your Mi Pad.
Power on your tab with a small press and just after releasing the button, hold Power and Volume Down buttons to enter into fastboot mode. You should see a little rabbit messing up with an android logo.
Plug your MiPad into your computer. You should see a notification saying Configuring "Fastboot".
Go in your ADB folder, click on the folder logo at the top left (just aside the path) and write cmd to start a cmd terminal directly in the right folder. You should see the good path in your terminal.
Enter the command fastboot devices to make appear one device which is your MiPad.
Enter the command fastboot flash recovery twrp-3.2.1-0-mocha-stock.img to install TWRP in your MiPad.
Shutdown manually your MiPad to reboot it directly into recovery, holding Power and Volume Up at start up.
-------------------------------
STEP 2 : Repartitioning​
Original thread
Requires :
TWRP booted on your MiPad.
mocha_repartition_1_2GB_RahulTheVirus.zip in your MiPad
Steps :
[RECOMMANDED] Make a backup of your current software setup (Backup --> Boot,Data, System).
Wipe your MiPad : Wipe --> Advanced Wipe --> Check Dalvik, Cache, System and Data --> Swipe to Wipe
When done, go to Install --> Select Storage, select the storage where you put your zip file then go to the folder
Click on mocha_repartition_1_2GB_RahulTheVirus.zip and Swipe to confirm flash
The script will reboot your MiPad twice. To make sure it reboots well to recovery, you can hold Power and Volume Up at the moment of the reboot.
After the double reboot, you can check if the script worked well going in Wipe --> Advanced Wipe, check System and then click on Repair or Change File System. If the parameter Size equals to 12XXMB, repartition worked well
-------------------------------
STEP 3 : Flash Shield Blobs​
Requires :
BootBlobs-SHIELD-mocha.zip in your MiPad
Steps :
Boot to latest TWRP if not done already. I also consider TWRP is configured to focus on the right folder (if not, check step 2.3)
Wipe your MiPad if not done already : Wipe --> Advanced Wipe --> Check Dalvik, Cache, System and Data --> Swipe to Wipe
Go to Install, select BootBlobs-SHIELD-mocha.zip then Swipe to confirm flash
After flash is complete, go back to original TWRP menu, select Reboot --> Recovery. Your MiPad will boot into Shield's 3.1.1.0 TWRP recovery. To make sure it reboots well to recovery, you can hold Power and Volume Up at the moment of the reboot.
-------------------------------
STEP 4 : Flash Shield Based ROMs​
Requires :
twrp-3.2.1-0-mocha-shield.img and any ROM based on Shield's LOS. Examples :
Nougat :
Lineage OS by Smoke Team
Resurrection Remix by twu2
AospExtended by twu2
dotOS by twu2
Android Ice Cold Project by jpg3927
...
Oreo :
Lineage OS by Smoke Team
Resurrection Remix by twu2
AospExtended by twu2
dotOS by twu2
...
Steps :
Boot to latest TWRP if not done already. I also consider TWRP is configured to focus on the right folder (if not, check step 2.3)
Go to Install, select Install Image, choose twrp-3.2.1-0-mocha-shield.img, select Recovery and then Swipe to confirm flash
After flash is complete, don't reboot, go back again to the install menu
Go to Install, select Install Zip, choose the ROM you want to install, Gapps, Magisk / SuperSU, anything you want, then Swipe to confirm flash
After flash is complete, you can boot to system and enjoy your new brand MiPad !
-------------------------------
Credits​
HighwayStar, for his huge work on Stock LOS
Artemka and Smoke Team, for porting LOS to Shield Blobs for MiPad
RahulTheVirus, helping MiPad users since the beginning and providing homemade scripts including new repartitioning tool
MiPad Community, for helping MiPad users :
LuckyMeAgain
Abhayy
More that I can't remember
twu2 and nazunamoe/jpg3927, building ROMs based on Shield's LOS
Snoop05, providing 15 seconds ADB install
zardMi3, providing original repartitioning tool
Others that I can't remember

Reserved for the upcoming FAQ

Reserved

Reserved

Hi, thanks for taking effort to provide a new lease of life for Mi Pad 1. I have a stock Mocha, and as luck would have it, I failed in the first step itself. I got into fastboot mode, and successfully flashed the stock twrp recovery. But after that it would not allow me to get into twrp by volume+ and power buttons. I tried different things including directly pressing both the keys after flashing, nothing helped. Am I missing anything. It boots normally alright. Thanks

manisvs said:
Hi, thanks for taking effort to provide a new lease of life for Mi Pad 1. I have a stock Mocha, and as luck would have it, I failed in the first step itself. I got into fastboot mode, and successfully flashed the stock twrp recovery. But after that it would not allow me to get into twrp by volume+ and power buttons. I tried different things including directly pressing both the keys after flashing, nothing helped. Am I missing anything. It boots normally alright. Thanks
Click to expand...
Click to collapse
Hi,
That's not my work, but Smoke one's. I just made the tutorial ^^
The way to go to recovery is the same that fastboot. You just need to press Power & Vol Up instead of Power & Vol Down
If you don't succeed, you can reboot to recovery via ADB

Hello there
I need your help
I just messed up my mi Pad
But as you suggested, I used I messed up pack to switch back to miui using fastboot via mi flash tool
But it's getting failed by the end every time,
Now my mi pad is just sometimes blink LED but then goes off.
Any help would be great....

Sorry, was really busy recently.
Will need more info :
What message do you have at the end of Mi Flash Tool script ?
What color the LED blinks ?
Did you try via Download (EBL) mode instead of Fastboot mode ?
In the future, you'll have faster answer in Telegram group. I'm more active and not alone.

Thanks for the great guide! Really helpful
Had just one issue in step 4.3, tried installing ROM without rebooting. TWRP gave error 7. Then i rebooted into recovery again and the rom installed. Otherwise flawless... thanks again

Sad to say, the shield blob does not work. It does not boot at all, had hard time get into Fastboot. Need to wait for above 5mins and noticed the device was still pretty hot on the top right corner, could be firmware still running/jamming with shield blob. Had been previously using latest 4.4 Xiaomi Firmware to-date, suspect this could be the main reason shield blob don't work. Confirmed 1.2GB partition all right. Though flash shield RR on stock blob works, but you want keep it alert all time though otherwise it will suspend (jam) itself after 2mins.

bertnii said:
Sad to say, the shield blob does not work. It does not boot at all, had hard time get into Fastboot. Need to wait for above 5mins and noticed the device was still pretty hot on the top right corner, could be firmware still running/jamming with shield blob. Had been previously using latest 4.4 Xiaomi Firmware to-date, suspect this could be the main reason shield blob don't work. Confirmed 1.2GB partition all right. Though flash shield RR on stock blob works, but you want keep it alert all time though otherwise it will suspend (jam) itself after 2mins.
Click to expand...
Click to collapse
Dude, I did exactly what I wrote cuz that's the way I learned from everyone who flashed shield blobs.
I don't even understand where **** happened : What did you do after flashing Shield Blobs ZIP ?
FYI, that's not because of "latest 4.4 Xiaomi Firmware" as Xiaomi abandoned development for Mi Pad for years. I can surely say that we are barely all with last firmware on our Mi Pad.

WiMiOP said:
Dude, I did exactly what I wrote cuz that's the way I learned from everyone who flashed shield blobs.
I don't even understand where **** happened : What did you do after flashing Shield Blobs ZIP ?
FYI, that's not because of "latest 4.4 Xiaomi Firmware" as Xiaomi abandoned development for Mi Pad for years. I can surely say that we are barely all with last firmware on our Mi Pad.
Click to expand...
Click to collapse
Thanks for your reply. After flash shield blob, Incident 1: I cannot boot into shield recovery anymore, try very hard after more than 5mins, only could get into fastboot. Incident 2: Only 1 attempt was successful that got me into shield recovery, flash the latest shield blob 3.2.1 and wipe all system,data,cache to flash lineage shield. After setup lineage shield, shut down, and never able to power up or get into recovery (same like incident 1). Freak me out. Tried very hard for long time again to get into fastboot and use fastboot boot recovery.img command based to get back into recovery and roll back to Stock Blob again. Now running latest shield based RR on stock Blob, all seems fine except don't let the device sleep. If it is not device firmware issue I do not what else causes such mischievous behavior on the firmware. Anyway truly appreciate you guys for such great custom ROM effort! Had been using custom ROMs for all my xiaomi devices for years, still like it a a lot.

bertnii said:
Thanks for your reply. After flash shield blob, Incident 1: I cannot boot into shield recovery anymore, try very hard after more than 5mins, only could get into fastboot. Incident 2: Only 1 attempt was successful that got me into shield recovery, flash the latest shield blob 3.2.1 and wipe all system,data,cache to flash lineage shield. After setup lineage shield, shut down, and never able to power up or get into recovery (same like incident 1). Freak me out. Tried very hard for long time again to get into fastboot and use fastboot boot recovery.img command based to get back into recovery and roll back to Stock Blob again. Now running latest shield based RR on stock Blob, all seems fine except don't let the device sleep. If it is not device firmware issue I do not what else causes such mischievous behavior on the firmware. Anyway truly appreciate you guys for such great custom ROM effort! Had been using custom ROMs for all my xiaomi devices for years, still like it a a lot.
Click to expand...
Click to collapse
That's not possible, ROM based on Shield cannot be booted with stock blobs. Dunno what you did, but if you really have stock blobs, you would be getting bootloop
If you really booted a ROM based on Shield, then congratz, you successfully have Shield Blobs. In your way.

WiMiOP said:
That's not possible, ROM based on Shield cannot be booted with stock blobs. Dunno what you did, but if you really have stock blobs, you would be getting bootloop
If you really booted a ROM based on Shield, then congratz, you successfully have Shield Blobs. In your way.
Click to expand...
Click to collapse
Really weird, I flashed Shield Blob and cannot even reboot into shield TWRP or boot up. Then I re-flash it back to Stock Blob and reboot recovery again (which works instantaneously with Vol Up + Pwr), Wipe All, and flash shield RR and everything works.

bertnii said:
Really weird, I flashed Shield Blob and cannot even reboot into shield TWRP or boot up. Then I re-flash it back to Stock Blob and reboot recovery again (which works instantaneously with Vol Up + Pwr), Wipe All, and flash shield RR and everything works.
Click to expand...
Click to collapse
Dude, if you don't believe me, tell your story to the dev in Telegram group. You'll see that's impossible.

WiMiOP said:
Dude, if you don't believe me, tell your story to the dev in Telegram group. You'll see that's impossible.
Click to expand...
Click to collapse
Hi, please do not get me wrong. I trusted you. I followed your steps but my mocha can not boot after flash Shield Blob. But I do not know why after re-flash the given Stock Blob, reboot recovery and flash given shield RR would work. Ultimately this is what I ended with. So I just post my steps here as feedback as well as reference point. I truly appreciate your content and reply here as future checkpoint, when there is new mocha ROM releases. :good:

good job mate, this should be pinned :good:

*deleted*

I'm struck at MI logo and even if I shutdown it is restarting at struck at mi logo. If I hold volume and power button, I can see fastboot screen but nothing happens after that. Kindly help how to reset my mi pad

I am stuck at Mi boot logo. I followed every step of the guide.
First I tried to flash RR 8.1.0 ROM, stuck at Mi log on rebooting after flashing everything (ROM, Gapps, SuperSU)
Then wiped System, delvic cahce, data, (all excecpt internal storage) and started again..
This time I tried flashing Lineage 14.1 with gapps. Same result.
Should I flash the Shield blobs again?
What to do? Stuck at Mi logo. I can boot into recovery via vol up + power.
Kindly help. Thank you

[OFFICIAL][R10.0][Stable] OrangeFox Recovery Mi A3 [laurel_sprout]

OrangeFox Recovery Project
{
"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"
}
Redwolf fork​
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
OrangeFox is FREE SOFTWARE​
Supports Treble, Miui, Custom Roms
Download:
Stable Builds
OrangeFox Recovery R10.0_2.1 [Latest]
INSTALLATION:
1- How to install OrangeFox Recovery ?
Method-1=
1. Download the OrangeFox zip file and copy it to your device (internal or external storage)
2. Extract the recovery.img from the zip and store it, on the folder where you have adb and fastboot files, on your PC
3. Open a cmd line and execute these commands (being on that folder, of course):
- adb devices (to make sure your device is detected)
- adb reboot bootloader (to reboot into fastboot mode)
- fastboot getvar current-slot (to check what's your current active slot)
- fastboot set_active b (if your active slot was a, if it was b then change it to a)
- fastboot erase boot
- fastboot flash boot recovery.img
- fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)
4. When OrangeFox recovery boots, if you have the stock boot.img that matches the build on this "currently active" slot, flash it into boot partition. If you don't have, then just ignore this step...(it's not mandatory)
5. Install the OrangeFox zip (always install the latest build available)
6. Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
7. Reboot to System
8. Enjoy!
Method-2=
0. Backup your ROM and all your files
1. Download the OrangeFox zip file to your device
2. Reboot to your custom TWRP-based Recovery
3. Install the OrangeFox zip file as a normal zip
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
2 -How to flash rom(s) using OrangeFox Recovery:
1. Format data (TIPPING YES).
2. Flash rom zip (PE, BEAST, ATOM
ETC...)
3. Flash OrangeFox-Recovery.zip again. ( INSTALLER, THE PHONE WILL REBOOT TO ORANGE RECOVERY (IF YOU DONT FLASH THIS AGAIN, RECOVERY WILL DISAPPEAR)
4. Flash Magisk v20.
5. Flash Gapps (optional).
6. Flash Patch_no_fde.
Frequently Asked Questions, MIUI OTA, Troubleshooting, and Sundry Information:
* See https://forum.xda-developers.com/showpost.php?p=76885728&postcount=3
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* ATG and Dadi11 - for Redwolf
* Kirillmaster4 - for graphics
* z31s1g - for TWRP theme
* @mauronofrio - for the decryption on Mi A3
* All our helpers and testers ( @prakaship78 , @nelinthon_Kekis , @Dvyhrs , @ihsaneDZ and the others ) - for your patience and help
FEATURES:
* Supports Treble and non-Treble ROMs
* Up-to-date Oreo kernel, built from sources
* Increased compatibility with TWRP
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM [only for some devices]
* Password
* Support for Miui and Custom ROMs
* Better language support
* Optimized versions of community scripts
* Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Screenshots - see below
Visit to https://orangefox.tech/

Finally,now we can see some roms for this device
Thanx alot to all creators and supporters

Any rom there for orange fox or still only fastboot Roms?
And big thx for the recovery works like a charm
But i don't flash any rom for now

dennis46419 said:
Any rom there for orange fox or still only fastboot Roms?
And big thx for the recovery works like a charm
But i don't flash any rom for now
Click to expand...
Click to collapse
Pixel experience now has a recovery flashable zip

trkzmn said:
...bla bla bla...
INSTALLATION:
Method-1=
1. Download the OrangeFox zip file, copy to your computer and your device.
2. Unpack the zip and input recovery.img to your pc desktop.
3. Open cmd and give this command "fastboot flash boot recovery.img"
4. Reboot to recovery.
5. When boot orangefox recovery install > OrangeFox-R10.0_2-laurel_sprout.zip [Download Latest Build] .
6. Enjoy
...bla bla bla...
Click to expand...
Click to collapse
Hello!
Thanks for your work, truly appreciate it.
Could you update the OP with the install method that I'm going to describe next? It's just to avoid future complications (lost of Wi-Fi, sound, etc...) for Noob users.
Download the OrangeFox zip file and copy it to your device (internal or external storage)
Extract the recovery.img from the zip and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (being on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot getvar current-slot (to check what's your current active slot)
fastboot set_active b (if your active slot was a, if it was b then change it to a)
fastboot erase boot
fastboot flash boot recovery.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)​
When OrangeFox recovery boots, if you have the stock boot.img that matches the build on this "currently active" slot, flash it into boot partition. If you don't have, then just ignore this step...(it's not mandatory)
Install the OrangeFox zip (always install the latest build available)
Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
Reboot to System
Enjoy
Why do I suggest this? Well, please read the hidden content:
By doing this method (which seems more complicated but I've tried my best to explain it as if I were explaining it to a 4 years old kid...) we will flash the recovery.img into the "inactive" slot, thus, not breaking anything on the "currently active" slot. When OrangeFox boots, it will patch both slots boot ramdisks. But the thing is, on the "currently active" slot (the one inactive on the beginning) it will patch the recovery.img but, on the "currently inactive" slot (the one that was active on the beginning), it will patch the stock boot.img, thus, no bug will happen that usually appears when a user accidentally flashes the wrong boot.img into boot partition. On the other hand, if we have the stock boot.img, that matches the build on the "inactive" slot, we could flash it into boot partition before installing the zip that patches ramdisk. By doing this we will patch both stock boot.img present on both slots (instead of patching recovery.img and boot.img).
Cheers!
---------- Post added at 12:04 ---------- Previous post was at 11:16 ----------
Hello....again...
I've just tested the install method that I've explained but, unfortunately, it's not working.
OrangeFox recovery only boots if the installer zip is run through TWRP...don't really know why since I've tested a lot of times doing this exact same method with TWRP recovery, and it's working. It should be working here as well.
Anyway the OF recovery boots but I think that it does not decrypt data. It doesn't gets frozen on the welcome screen (like before) but it doesn't decrypt (I see all the files with the "weird" names). This, of course, is only bad for those who want to remain on stock ROM. For anyone who wants to move on to custom ROMs, just format user data and your set to go.
Cheers!

OrangeFox Recovery R10.0_2.1 Changes
* Fix stuck in fastboot mode after flashing OrangeFox with fastboot

Post Changes
1. OrangeFox recovery installation made easier with explanations (Thanks to @Typhus_)
2. Custom rom install method added (Thanks to @nelinthon)

Hi all, can we do a backup of all data (system, boot...) And restore with orangefox?
I'm afraid to test any rom and not to be able to return to the original configuration... I have the 5 october update

Shineali said:
Hi all, can we do a backup of all data (system, boot...) And restore with orangefox?
Click to expand...
Click to collapse
Yes you can.
Shineali said:
I'm afraid to test any rom and not to be able to return to the original configuration... I have the 5 october update
Click to expand...
Click to collapse
Follow the install custom rom steps. If you still have problem with it take recovery.log and send me

trkzmn said:
Yes you can.
Follow the install custom rom steps. If you still have problem with it take recovery.log and send me
Click to expand...
Click to collapse
Ok thanks!!!

Anyone fix this error

There is recovery.img
I already changed name to .img and then try..but nothing happened

RJ- said:
Anyone fix this error
Click to expand...
Click to collapse
RJ- said:
There is recovery.img
I already changed name to .img and then try..but nothing happened
Click to expand...
Click to collapse
On the first image your running commands on "C:\Program Files\Minimal ADB and Fastboot" folder.
On the second image your showing the files on "C:\adb" folder.
You must run the commands on the folder where you have the img file stored! Rename the file!!? WTF!?
Besides, you didn't read the instructions carefully, not only your running the command to change slot wrong but, also, you've tried to flash recovery.img into currently active slot before trying to change slot (based on your command history on first image).
PLEASE!
If you're not comfortable doing these simple steps, or if you don't have patience to read all instructions carefully, then just DON'T DO ANYTHING!!
People with this kind of behavior are the main reason why most devs often just drop development. How will you be able to successfully flash a ROM and/or report true bugs, if you're not able to just execute simple commands that have been explained step by step? Maybe my instructions weren't clear enough....perhaps I should have start the steps with:
"Turn on your computer";
"Put your hands on your keyboard and mouse";
"Login to your account";
etc....
ALSO, the recovery on the OP has been updated. Even if you did everything correctly you would end up on fastboot since your trying to flash the wrong OF version!
Please, search, please read, please...USE YOUR BRAIN!

Thanks

Hi I tried to install but i get an error during orangefox first boot there's no option to install orangefox....zip ot seems like the files were encrypted. They have a strange names...
It could be that didn't give permission to write? O do the steps again bit didn't ask me for permission.
Thanks in advance.

Shineali said:
Hi I tried to install but i get an error during orangefox first boot there's no option to install orangefox....zip ot seems like the files were encrypted. They have a strange names...
It could be that didn't give permission to write? O do the steps again bit didn't ask me for permission.
Thanks in advance.
Click to expand...
Click to collapse
Seems files are encrypted.
- Format data
- Flash OrangeFox.zip

RJ- said:
Anyone fix this error
Click to expand...
Click to collapse
Don't use minimal adb, try to use platform tools for windows.

Can Orangefox recovery support for OTA updates in MiA3???

ricky9779 said:
Can Orangefox recovery support for OTA updates in MiA3???
Click to expand...
Click to collapse
No rom for this device has ota support yet anyway. And if you mean ota for stock rom then definitely not as you need stock boot.img for stock ota or it won't work

Website and download link down at the moment or it is just for me?

[RECOVERY][A9/A10] [UNOFFICIAL]SHRP 3.0 (20/01/15)

{
"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"
}
Standard Disclaimer:-
* Your warranty is... still valid?
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
SHRP is inspired by Material Design 2 to bring the newest design to TWRP. SHRP provides much more features alongside it's rich UI experience. New and improved dashboard makes it very easy to interact with TWRP. SHRP also got some extra cool features like whole new theming section , flash Magisk (root or unroot), Camera2API enabler directly from dashboard, password protection etc. It's all only just started , a lot more to come.
- Themes
- List view mode along with grid dashboard
- Status bar customization
- New rounded icons added on dashboard
- Notch mode with toggle to disable
- Dark mode or pure white, it's on you
- Navigation bar customization
- Settings + Advanced Settings
- Flash Magisk
- Clear fingerprints.
- Flash ViperFX
- Recovery Locking , Pin or Pattern lock
- CPU core lock/unlock
- Language changing
- HAL3 / CameraAPI2 enabling/disabling
- Oreo+ reboot menu style
- Redesigned lock screen interface
- Flashlight
- Magisk manager - Enable, disable or delete magisk modules right from SHRP
- and many more, flash right now to find out
1. Make sure you have a custom recovery installed
2. Download the latest SHRP recovery for your device
3. Boot into recovery
4. Flash SHRP recovery zip
5. Reboot to recovery.
6. Done
or
Fastboot flash boot shrp.img (currently only for stock vendor ROMs)
Recovery asks for decryption password every boot (You can say that this is a feature that increases security or just an inconvenient bug, i prefer the former)
File Manager back button dosent work, have to press home button to exit
Loading time is slightly longer than SHRP2 on boot
Thanks to @Master_L at the Telegram group for pointing out these small bugs
https://drive.google.com/drive/folders/12MDRsmJWtbQDCoAXlp1D3U0gHPYA4PSr?usp=sharing
Github
Website
Telegram Group
SHRP Team:
EpicX
DNI9
Giovix92
TeamWin
osmOsis
VR25
Topjohnwu
Mauronofrio
DarthJabba9
Pritish
Kirill
Burak D.
ZJRDroid
LayeardDevMod
Olek & Oliwier
Special Thanks:
@Nikesh001 (for TWRP trees)
@oddlyspaced (for SHRP trees)
@HarukeyUA (for LineageOS trees from which i took kernel and dtbo for recovery)
@AlaskaLinuxUser (for his amazing tutorials for building recoveries)
The Arch Wiki for helpming me deal wih pesky python building errors
Docker Inc. for Docker which helped me to finally compile this in Manjaro ( I don't like Ubuntu)
Please inform if I forgot to mention your name here , thanks !
Maintainer: NanduPV
Based On: TWRP
Source: SHRP 3_9.0
Screenshots:
​

is this able to flash it over Android 11 so in order to be able installing a Custom Rom? (Pixel Experience, EvolutionX)

Vicro2821 said:
is this able to flash it over Android 11 so in order to be able installing a Custom Rom? (Pixel Experience, EvolutionX)
Click to expand...
Click to collapse
No, only A9/A10 till TWRP supports A11

Is there any difference between this and my official builds?

oddlyspaced said:
Is there any difference between this and my official builds?
Click to expand...
Click to collapse
Just ported to new version 2.3.2 to 3.0, same trees. Many thanks for your contributions to our device

I don't ever see a clear guide how to install this recovery to a stock a10 unrooted device with bootloader unlocked... Step by step with any bricking risc. It's the first Time in ten year that i ever don't undsterstand the correct way to do this

wetito said:
I don't ever see a clear guide how to install this recovery to a stock a10 unrooted device with bootloader unlocked... Step by step with any bricking risc. It's the first Time in ten year that i ever don't undsterstand the correct way to do this
Click to expand...
Click to collapse
It is a bit complicated due to A/B system-as-root and new fastboot security restrictions
But, once you understand and do it, it is pretty simple.
Installing / Flashing TWRP (or any other recovery) on A/B devices:
Since all known A/B devices do not have a separate recovery partition, you will eventually have to flash TWRP to the boot partition. On the Pixel 1 and 2, and some other devices, we use fastboot boot to temporarily boot TWRP without flashing TWRP. We then flash a zip installer to to flash TWRP to both slots.
The Mi A3 unfortunately does not support fastboot boot. Instead, users have to determine their currently active boot slot using
Code:
fastboot getvar all
then use,
Code:
fastboot set_active_a
or
fastboot set_active_b
to switch slots to the inactive slot. From here, the user can
Code:
fastboot flash boot twrp.img && fastboot reboot
to get into TWRP. Once in TWRP they can then go to the reboot page and change back to their originally active slot, make a backup, then install TWRP. Using the inactive slot allows users to get a good, unmodified backup of their device before installing TWRP.
Hopefully this helps!
Taken from @Dees_Troy guide on all things TWRP @https://forum.xda-developers.com/t/dev-how-to-compile-twrp-touch-recovery.1943625/post-32965389
Note: To get TWRP or in this case SHRP image file, just extract SHRP installer zip and find recovery.img, this is the Image file you need.

NanduxXxPV said:
It is a bit complicated due to A/B system-as-root and new fastboot security restrictions
But, once you understand and do it, it is pretty simple.
Installing / Flashing TWRP (or any other recovery) on A/B devices:
Since all known A/B devices do not have a separate recovery partition, you will eventually have to flash TWRP to the boot partition. On the Pixel 1 and 2, and some other devices, we use fastboot boot to temporarily boot TWRP without flashing TWRP. We then flash a zip installer to to flash TWRP to both slots.
The Mi A3 unfortunately does not support fastboot boot. Instead, users have to determine their currently active boot slot using
Code:
fastboot getvar all
then use,
Code:
fastboot set_active_a
or
fastboot set_active_b
to switch slots to the inactive slot. From here, the user can
Code:
fastboot flash boot twrp.img && fastboot reboot
to get into TWRP. Once in TWRP they can then go to the reboot page and change back to their originally active slot, make a backup, then install TWRP. Using the inactive slot allows users to get a good, unmodified backup of their device before installing TWRP.
Hopefully this helps!
Taken from @Dees_Troy guide on all things TWRP @https://forum.xda-developers.com/t/dev-how-to-compile-twrp-touch-recovery.1943625/post-32965389
Note: To get TWRP or in this case SHRP image file, just extract SHRP installer zip and find recovery.img, this is the Image file you need.
Click to expand...
Click to collapse
Tnx a lot!

Great contribution! I'm looking forward to unlock bootloader, install recovery and a custom rom on my friend's mi A3. I have done my research but I still have one question. If I wanna keep the recovery after I install the custom rom, do I have to do anything? Or just flashing the zip before installing the rom will do the job? Thanks!

Batpope said:
Great contribution! I'm looking forward to unlock bootloader, install recovery and a custom rom on my friend's mi A3. I have done my research but I still have one question. If I wanna keep the recovery after I install the custom rom, do I have to do anything? Or just flashing the zip before installing the rom will do the job? Thanks!
Click to expand...
Click to collapse
Just make sure to flash the Recovery installer zip after the ROM you flash.

LineageOS starts booting, but then phone goes to Qualcomm Crash Dump Mode

Hello,
I am new to phone rooting/modding, this is my first time trying to install a custom ROM (lineageOS) to my OnePlus 8 Pro.
First, I followed this guide for rooting, installing TWRP and then Magisk. The only different thing that I did was, when flashing TWRP, not usingfastboot flash recovery twrp-image-filename.img, but fastboot flash recovery_a/b twrp-image-filename.img, because I read that the former may lead to a boot loop.
Everything worked. Then I proceeded to Install LineageOS on instantnoodlep, where it said I needed to upgrade my stock OS to Oxygen 11/Android 11 first (it came with O10/A10). I did that successfully.
However, it turned out that O11/A11 had overwritten TWRP with the stock recovery. So I flashed TWRP again. This too was successful.
I decided not to install the LineageOS with the LineageOS recovery, as in the official guide, but through TWRP. I copied the LineageOS image to phone memory, booted to TWRP, selected Wipe and did a Factory Reset - Wipes Data, Cache and Dalvik (DID NOT choose Advanced Wipe, probably this was the problem?)
After the reset, I selected the LineageOS ZIP file and installed it.
After booting to system, LineageOS starts loading, but after 4-5 mins I see
QUALCOMM CrashDump Mode
--------------------------------------------------
Panic requested on external modem boot failure
mdm_force_reset
Any help for getting out of this?
It will be MUCH appreciated.

Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.

Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.

MaybeDontAsk said:
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
Click to expand...
Click to collapse
The unlock command would be:
Code:
fastboot flashing unlock

Thanks for the suggestions, I will try them when I get to my home PC, I'm at work now.
In the meantime: can someone explain to me what is the exact procedure for installing LineageOS with the latest TWRP image? More specifically, which options in "Advanced Wipe" should be checked, because in all the tutorials I found they were using old versions of TWRP which did not include the "system" option. Mine had it, so I decided not to use Advanced Wipe at all and use the default wipe options (this is also what they did in one of the tutorials). Could this be the cause for the crash dump error?
Also, I am kind of reluctant to re-lock the bootloader and go back to stock OxygenOS. I still have access to the (LineageOS) recovery mode (it overwrote TWRP). Can I try doing something from there, like maybe overwriting it with TWRP again, then wiping everything (the right way) and installing LineageOS again?

Well when ever I get a Qualcomm crash dump error I always like to go back to stock and re do everything fresh just in case something else goes wrong but if you just don't wanna go back to stock you can do this:
If you wanna overwrite lineage os recovery you can reboot into the bootloader, and just do fastboot flash recovery (drag and drop twrp image here)
So it will be something like:
Code:
fastboot flash recovery C:\Users\YourUsername\Desktop\(recovery name).img
Or if you have the twrp image in the same place at platform-tools you can do:
Code:
fastboot flash recovery (recovery.img)
Or a one time twrp boot:
Code:
fastboot boot C:\Users\YourUsername\Desktop\(recovery name).img
Or:
Code:
fastboot boot (recovery name).img
But like I said it's probably better to re-lock the bootloader to start fresh then you can unlock it again and do anything else. Good Luck.
Anyways in TWRP Navigate To:
Wipe>Advanced Wipe> Dalvik/Cache>Data>swipe to wipe
Go back to TWRP home
Advanced>Adb Sideload
Now in PC cmd do:
Code:
adb sideload (drag and drop lineage os zip here)
Hit Enter And Wait Until It Finishes Flashing
Now For The Google Apps (GAPPS):
Download Nik GAPP From:
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
Select "Download"
Then look through all packages and read what each one contains, I would go with either core or basic. But you may need another apps so just read and choose.
Once you choose, click "download now"
Navigate To Folder
Releases>NikGAPPS R if lineage is 18.1(Android 11)>Latest Version>then choose from here and download.
Back to TWRP
If the download for gapps Finished:
Navigate to:
Advanced>adb sideload
Back On CMD:
Flash Gapps:
Code:
adb sideload (drag and drop NikGAPPS zip)
once it finishes:
On TWRP go back to home menu and navigate to:
Wipe>Format Data>Type "yes">Hit Enter>Go Back To TWRP Menu>Reboot>System if it says "no rom is installed" just swipe to confirm reboot, Lineage OS Is Actually Already Flashed. Good Luck!
I know this is long but it's really not lol.

@MaybeDontAsk
Thanks a lot! I will try again via TWRP first. I don't want to re-lock the bootloader just yet, because I fear something may go wrong in the process and I may end up with a bricked phone AND a locked bootloader, and that will really be the worst scenario, from what I've read in forums.
As for the GAPPS part - I don't plan to install them. Just a LineageOS image will be fine.

Alright well hope everything goes well and yeah I also feared I may end up bricking my device with the msm download tool but I've already done it multiple times.
It has fixed a lot of issues for me wether it is that the device is booting straight into recovery or fastboot or that it's not even booting up!

Just something about TWRP: when I tried just booting to it, the phone froze on the "Fastboot Mode" splash screen and stopped there. So I had to use the flash option.
Also, about flashing: I should use
Code:
fastboot flash recovery (recovery.img)
and not
Code:
fastboot flash recovery_a (recovery.img)
fastboot flash recovery_b (recovery.img)
right?
Just double checking to make sure.

Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
{
"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"
}
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?

freeride01 said:
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
View attachment 5543241
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
Click to expand...
Click to collapse
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.

MaybeDontAsk said:
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
Click to expand...
Click to collapse
Alright.
I gotta find a Windows PC though, I am on Linux/Fedora.
My OxygenOS before the wipe was 11.0.10.10.IN11BA, I guess from the list I should download "OOS 11.0.4.4", because its the latest.
I'll post again when there is some progress.

MaybeDontAsk said:
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Click to expand...
Click to collapse
OK, I got my hands on a Windows 10 PC. I downloaded and extracted the MSM tool and watched the video you linked.
There is no Win7 version of the .exe file, so I guess I'll use the "normal" one anyway.

Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?

freeride01 said:
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
Click to expand...
Click to collapse
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.

MaybeDontAsk said:
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
Click to expand...
Click to collapse
Hi again,
I did the whole process again and when I did adb sideload I got this:
Code:
[[email protected] phone root]$ adb sideload lineage-18.1-20220214-nightly-instantnoodlep-signed.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Now what? There's a slide in TWRP that says "Swipe to start sideload", should I swipe it?
EDIT: Maybe Ishould use adb install as described here?

No, you need to reinstall the adb interface drivers, search up on how to do it on Linux.
Tht link you put is for installing apk directly from adb and not roms.

But adb seems to work, adb devices returns my phone ID.

It says something like "(Device ID) | Sideload?
If yes then reboot both the laptop/pc and phone.

Code:
[[email protected] phone_root]$ adb devices
List of devices attached
19356f32 recovery
(changed some digits in serial no. for privacy)

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note 20 & Note 20 Ultra Exynos

{
"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"
}
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 Ultra​Only for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu

Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection

FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version or Rollback protection might kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards

well done sir

Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!

edsoedso said:
Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!
Click to expand...
Click to collapse
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards

corsicanu said:
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards
Click to expand...
Click to collapse
Nothing changes in the screen phone. Attached is odin screen. Thank you!

edsoedso said:
Nothing changes in the screen phone. Attached is odin screen. Thank you!
Click to expand...
Click to collapse
Can you please check Kg state line from download mode? What's written there?

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
I installed twrp but it seems that it does not read the internal storage.

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
And how to flash the multidisabler? it seems that everything is encrypted and is impossible to locate it in twrp?

I found it!
1. enter into TWRP (after flashing twrp.tar and Vbmeta.tar via odin), format data and reboot again in TWRP
2. Being in TWRP, transfer from PC to your phone multidisabler.zip and magisk zip.
3. flash them both
4. reboot system
That is all!

i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system

Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?

m7mdo_93 said:
i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system
Click to expand...
Click to collapse
edsoedso said:
Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?
Click to expand...
Click to collapse
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
yeah , after flashing multidisabler second time my mobile able to working .. thanks for your help

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
Thank You very much. It worked!

A big thank you, it works fine.

hey.
i did everything from this guide, and i got root access+twrp installed.
the problem that i am facing, is that i canot install anything from twrp, due to insufficient space.
the system size that twrp is reading is only 8384kb, so every installation of gapps is failed.
i tried to wipe ,format data, and changing the file system, but nothing helped.
please give me an idea how to solve it.
thanks.

Good day
Does this work for Android 13 One UI 5.1?