Database Info

[Root] [guide] Samsung Galaxy A20 rooting guide

Read the first 3 posts before you proceed.
For Android 10 go here
https://forum.xda-developers.com/galaxy-a20/how-to/android-10-q-guide-a20-t4095589
For a20e go here
A20e Root,Kernel, TWRP and custom ROM
Root & TWRP from Xyn XDotnest https://forum.xda-developers.com/galaxy-a20/development/recovery-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767 Orange Fox Recovery from @Royna...
forum.xda-developers.com
WARNING: Rooting your phone may be dangerous.
Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing!

Advantages of rooting:
Once you root your device you can install flashable zip files and custom ROMs.
You can backup all your apps and data using Titanium Backup.
You can customize your device according to your needs by deleting unwanted system apps and using Deathly Adiutor to modify the kernel.
View attachment 4802662
Disadvantages of Rooting:
Once you root your device, your device warranty will be void.
After rooting yourndevice may become unstable.
You may not be able to upgrade OTA in the future.

This method should root your Samsung Galaxy SM-A205X (all models except SM-A205U and SM-A205DL).
It was developed for the U2 bootloader (June 2019 firmware)
This method does not work for the a20s (A207X)
This method can be used to root other Samsung phones including the a20e( post#77 post#180, post#256)
Quick Root and TWRP for A205xx
https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
You'll find it much quicker.
Repair Firmware
This site contains
1. Full repair firmware
2. Combination firmware
3. Fix dm verify
4. Root instructions and unpatched boot images
https://www.full-repair-firmware.com/search?q=A20
More firmware (some are even prerooted)
https://www.needromarab.com/1/122/SAMSUNG
Samfirm Tool for really fast downloads
https://samfirmtool.com/samfirm-v0-5-0

Useful videos
Instructions
A. Prepare boot image
1. Download magisk manager apk
2. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
https://samfw.com/
3. Use zarchiver to copy AP_20xxxxxxxx.md5 to download directory. It will extract it from the zip.
4. Rename AP_20xxxxxxxx.md5 to AP_20xxxxxxx.tar and extract using zarchiver
5. Copy boot.img.Iz4 to download directory and extract (resulting in boot.img)
6. Use magisk manager to patch boot.img (use top install) result magisk_patched.img
(If using Magisk (Canary) patch, options should be remove dm-verity and not via recovery, but allowing Persist Encrypt.)
7. Rename magisk_patched.img to boot.img
9. Use zarchiver to compress boot.img to boot.tar. If you have a A205xx June firmware (U2 bootloader), you can use my one of you're willing to take a risk. View attachment boot.zip. Just unzip it first.
9a. For a20e users, try this boot.img https://forum.xda-developers.com/showpost.php?p=81649257&postcount=260
10. Copy boot.tar to Windows pc or Windows Virtualbox.
11. On phone developer options in settings unlock OEM and enable usb debugging
(If using Linux
9. Don't compress `boot.img`
10. install heimdall flash with `sudo apt install heimdall-flash`, if you want front-end install it with `sudo apt install heimdall-flash-frontend`)
B. Unlock bootloader
Useful video
12. Backup data. It will be wiped.
13. Turn phone off
14. Hold vol- and vol+ and plug in power cable attached to pc then release vol up to enter unlock screen.
15. Follow the instructions to unlock
(You might need to long press vol up to unlock bootloader)
vol + to select yes to confirm.
17. Press power key to unlock bootloader.
18. Reboot and reactivate developer options and enable usb debugging. Don't enter too much data at this stage as you will lose it again later.
C. Flash boot image.
19. Turn phone on in bootloader (download) mode (Hold power and vol+ to enter recovery mode then select bootloader download mode)
20. Connect phone to computer.
21. Use Odin in Windows to add boot.tar to phone. (Select AP). Some people recommend adding the other firmware parts to their slots at the same time.
22. Restart phone
23. select bootloader
24. Select factory reset (this will wipe data)
25. Restart phone
26. install data
26. install magisk manager
27. If green phone is rooted.
View attachment 4802665
28. Of red select install/direct install
29. Advanced tick both.
30. Install root checker and verify root
If Something Goes Wrong
Go here
https://forum.xda-developers.com/galaxy-a20/how-to/crash-recovery-t4068369
If you get a DTBO error after updating Magisk, flash this vbmeta https://drive.google.com/file/d/1-dogButfxKGlx_x2tSROOBDiq90SDlmc/view
(If using Linux
To flash:
20. Detect device with `heimdall detect`
21. Flash the `boot.img` with `heimdall flash --BOOT {location of the boot.img, you can also just drop the file into terminal and terminal should auto-fill it}` ex: `heimdall flash --BOOT '/home/utku/Programlar/ext/boot.img'`
P.S: an easy way to boot into download mode is `adb reboot bootloader`)
If you want to remove the warning messages on the boot screen
try this.
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
The images shown on the A30 thread aren't suitable for the A20 so I have included some better ones here.
View attachment 4803752
{
"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"
}
You can use this param.tar to make these changes easier.
https://forum.xda-developers.com/showpost.php?p=80169262&postcount=91
You can now move on to install TWRP
This TWRP was originally designed for Android 9 but works perfectly with Android 10 and also has MTP built-in.
https://forum.xda-developers.com/ga...overy-twrp-3-3-1-0-galaxy-a10-exynos-t4013481
physwizz collection
A collection of guides, kernels and ROMs. Guides Complete Guide to the A20 GSIs for the A20 Quick Root and TWRP for the A20 Making my First Kernel for the A20 A20 Rooting Guide Making Your Own ROM Making Your Own Version of QwizzROM-a20...
forum.xda-developers.com

Mine
Discussion page.
https://forum.xda-developers.com/t/samsung-galaxy-a20

On the lighter side of rooting....
From the A30 forum:
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
Works for A20 too

jajk said:
On the lighter side of rooting....
From the A30 forum:
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
Works for A20 too
Click to expand...
Click to collapse
Another reason to merge. This is a procedure for removing those annoying error messages on startup screens.

A205U owners complaining about not being able to oem unlock bootloader might want to study this:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
It looks like a way to switch to another unlockable firmware version.

Please, need magisk_patched.img file for SM-A205F.

jajk said:
A205U owners complaining about not being able to oem unlock bootloader might want to study this:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
It looks like a way to switch to another unlockable firmware version.
Click to expand...
Click to collapse
Yeah tried that option. Samsung has our model on a bootloader 2, means our device won't accept flashing from any other firmware but the original non-modded firmware only.
Tried prince Odin,patched Odin all versions, tried Heimdall etc..
Error is ...boot secure check failed..
I've tried to flash firmware a205G only with fail error Everytime.
Psa I've had my a205u for 10 days no OEM unlock option.
Main reason why I'm not buying another Samsung phone.
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .

jhjhjhjhjhjh said:
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^THIS ALL DAY. I swapped mine out for the G7 Power and already done rooted, flashed, and wrote a guide while all the 205u users are waiting for the mythical OEM Unlock to magically appear which it ain't gonna. Sammy can kiss my techie ass...we are officially divorced. I won't even go back and buy an old Sammy like I wanted to (was thinking about getting that S7 edge). It's me and Moto for now.

jhjhjhjhjhjh said:
Yeah tried that option. Samsung has our model on a bootloader 2, means our device won't accept flashing from any other firmware but the original non-modded firmware only.
Tried prince Odin,patched Odin all versions, tried Heimdall etc..
Error is ...boot secure check failed..
I've tried to flash firmware a205G only with fail error Everytime.
Psa I've had my a205u for 10 days no OEM unlock option.
Main reason why I'm not buying another Samsung phone.
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
Click to expand...
Click to collapse
Maybe Samsung has an issue with US tariffs.

Samsung have certainly turned an essentially good piece of hardware into a pile of rubbish with mega-invasive bloatware. I have barely started to strip back the garbage and the phone is springing to life. Need a working TWRP before getting too keen as the path back to functionality is long and arduous without a way of restoring partitions if anything gets screwed up. Here is what the phone looks like with Google Play junk removed plus a bit of Samsung bloat removed - not everyone is ready to kick the Alphabet addiction I know, but it has become an absolute monster that eats battery and cpu cycles....apart from the privacy invasion side of it
I am finding that many unknown, non-visible apps with innocent sounding names or "security" inferred in the name are likely to be ad server or data mining software - I got wise to this with my first and last Xiaomi device

jajk said:
Samsung have certainly turned an essentially good piece of hardware into a pile of rubbish with mega-invasive bloatware. I have barely started to strip back the garbage and the phone is springing to life. Need a working TWRP before getting too keen as the path back to functionality is long and arduous without a way of restoring partitions if anything gets screwed up. Here is what the phone looks like with Google Play junk removed plus a bit of Samsung bloat removed - not everyone is ready to kick the Alphabet addiction I know, but it has become an absolute monster that eats battery and cpu cycles....apart from the privacy invasion side of it
I am finding that many unknown, non-visible apps with innocent sounding names or "security" inferred in the name are likely to be ad server or data mining software - I got wise to this with my first and last Xiaomi device
Click to expand...
Click to collapse
I used titanium backup first. Now I'll debloat.

physwizz said:
Maybe Samsung has an issue with US tariffs.
Click to expand...
Click to collapse
The US doesn't have an issue with South Korea on tariffs, despite Trump's big mouth.
The problem is that Sammy wants to be essentially Apple Android. And that is what's driving this crap in the same of "security". Knox has been like the devil and even sentient since it came to power almost like Skynet. And all of this started when Verizon offered Sammy big bucks to lock it down ala Kyocera with the S5 era - which coincidentially is the last great breath of air they had to give.
They don't care about the developer models either - look in the forums, many of them are just as locked down.
Sammy knows ain't that many phone companies left in the US; Tmobile done bought out half the cell companies and AT&T got the other half in a duopoly, meaning they and other companies can continue this path of nanny phones on the general public that are going for more personalized computers they can't control than actual phones that work. Most Americans aren't going to turn to GooPhone nor will many XDA devs develop any type of TWRP or rom for those types. And that means they can dangle a bells and whistle carrot while their demographic signs their privacy away.
I ain't a fan of Lenovo-Moto, but at least they let half the phone companies unlock the variant to their devices. Sammy, on the other hand, does not and is playing Xiaomi type of games on that bootloader.

Articul8Madness said:
The US doesn't have an issue with South Korea on tariffs, despite Trump's big mouth.
The problem is that Sammy wants to be essentially Apple Android. And that is what's driving this crap in the same of "security". Knox has been like the devil and even sentient since it came to power almost like Skynet. And all of this started when Verizon offered Sammy big bucks to lock it down ala Kyocera with the S5 era - which coincidentially is the last great breath of air they had to give.
They don't care about the developer models either - look in the forums, many of them are just as locked down.
Sammy knows ain't that many phone companies left in the US; Tmobile done bought out half the cell companies and AT&T got the other half in a duopoly, meaning they and other companies can continue this path of nanny phones on the general public that are going for more personalized computers they can't control than actual phones that work. Most Americans aren't going to turn to GooPhone nor will many XDA devs develop any type of TWRP or rom for those types. And that means they can dangle a bells and whistle carrot while their demographic signs their privacy away.
I ain't a fan of Lenovo-Moto, but at least they let half the phone companies unlock the variant to their devices. Sammy, on the other hand, does not and is playing Xiaomi type of games on that bootloader.
Click to expand...
Click to collapse
I find it strange that the US version is the only one that can't unlock the bootloader.
The rest of us are all unlocked and rooted.

physwizz said:
I find it strange that the US version is the only one that can't unlock the bootloader.
The rest of us are all unlocked and rooted.
Click to expand...
Click to collapse
It aint strange, its common. Before it was locked exclusively to Verizon; after the S3 it became more and more carriers. Then the dev models started being locked up but "open".

Articul8Madness said:
It aint strange, its common. Before it was locked exclusively to Verizon; after the S3 it became more and more carriers. Then the dev models started being locked up but "open".
Click to expand...
Click to collapse
Mine is locked to Vodafone but I can still unlock the bootloader.

physwizz said:
Mine is locked to Vodafone but I can still unlock the bootloader.
Click to expand...
Click to collapse
Same here.
Did you mod your param.tar (to change the warnings at startup) file by any chance? Would you be able to attach it at all? I was gonna download the firmware but it's taking 9 hours.
Thanks.

burningcreation said:
Same here.
Did you mod your param.tar (to change the warnings at startup) file by any chance? Would you be able to attach it at all? I was gonna download the firmware but it's taking 9 hours.
Thanks.
Click to expand...
Click to collapse
I've downloaded the 2 pics and I modified one to contain my name.
I will try the mods shortly.

hey guys need help on mi note 10 pro global rom for a mi cc9 pro

I managed to get, mi cc9 pro (china variant) aka mi note 10 pro. for one year without google feeling like missing some comfort.
i have decided to install global rom and unlocked the boot loader too! now for the hard part the I have almost bricked the device.
i seek step by step help to install global rom on Chinese variant. I really like the camera and being an ecologist it really helping me too.
i am not a geek but I follow beyond the neck for this one please consider for this one.
regards
sri

Unlock
Apply for permissions to unlock Mi devices
en.miui.com
A good customer recovery
[TWRP][UNOFFICIAL]OrangeFox recovery for Mi Note 10/CC9 Pro
OrangeFox Recovery Project /* * 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...
forum.xda-developers.com
How to flash a customer recovery
Nice guide
How to Install TWRP Recovery on Xiaomi Phones (Universal method)
The universal guide to Install TWRP Recovery on Xiaomi Phones. We will flash TWRP Recovery using Fastboot mode by unlocking bootloader of the device.
www.xiaomigeek.com
I like the Xiaomi.eu rom
Stable
MIUI 12.0 - MIUI 12.0/12.1/12.2/12.5 STABLE RELEASE
STABLE RELEASE RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Or beta 12.5?
MIUI 12.5 - 21.3.17/18
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu

Unlocking Bootloader guide
0. Log into your Mi Account on phone!
1. Enable Developer Settings -> Enable USB Debugging
2. Enable OEM Unlock in Developer Settings
3. Add device in Mi Unlock status in Developer Settings. From this step you need to wait 168 hours to get unlock permission. If you have done these steps before, you can continue with this tutorial
4. Unpack MIUI Unlock and log into it
5. Shut down your phone
6. Press and hold Vol Down button and Power button at the same time to reboot to Fastboot mode
7. You're now in Fastboot mode. Connect your phone to your PC with Xiaomi's Original USB Cable (to avoid issues)
8. Click Unlock in the MIUI Unlock
9. If you see error that you still need to wait, then just wait and continue with this tutorial
---After 168 hours---
1. Start the MIUI Unlock again and click Unlock and wait till it's done
2. When it says "Unlocked successfully", congratulations, you have unlocked bootloader.

Waiting is randomly. Someone wait 7 days another wait longer or shorter. Mi flash tool will show you how long you have to wait, when you click on unlock

General Covering some misleading theories and issues with our A12

This thread will be updated regularly. If you don't agree with something comment and if I was proven wrong I will update the thread.​Please don't comment or chat here if it isn't releated with something I said. If you need further help with stuff then go here:​
[HELP THREAD] Ask any questions, noob friendly.
Help thread for people that have the Samsung galaxy a12 (any model) Anyone can ask and help others here, but please don't be abusive towards others. No abuse tolerated here! That means: NO TROLLING NO NAME CALLING NO RIDICULING NO FLAMING
forum.xda-developers.com
And remember these are not "how to guides" but rather explenations on some stuff.​​
Spoiler: TWRP
Booting in to stock rom will not work after installing twrp if the stock rom isn't pre rooted (rooted by flashing the whole patched AP file from magisk) or if you don't have a kernel that will automaticly fix that for you, same goes for vbmeta. This is happending because this device uses dm-verify so that means after installing twrp you are allowing modifications of system partiton which then will not let you boot in to system if you haven't done stuff as said above.
I also have guides here explaining how to not get that problem
Installing TWRP and LInageOS
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
​
Spoiler: Rooting
When rooting through magisk and when selecting a file for patching, it is best to select the whole AP file. Before I use to say that was usles and patching just the boot.img was enough, but nowI changed my opinion. When patching the whole AP file you are patching the boot.img and the vbmeta. When patching just the boot.img you may have issues with not booting in to roms, twrp, mods not working and soft bricks. It is allways better to have the whole enviroment patched. But allways be careful to not download magisk from a 3thrd party source, and allways install from official github. And use cannary edition which is latest or you might expirience issues with android 11 and root premissions breaking and etc.
GitHub - topjohnwu/magisk_files at canary
(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.
github.com
Spoiler: Installing custom roms
It is important to have dm-verify disabled before flashing or else(only if the ROM doesn't have full verified boot support) . Always wipe data, cache, old system partiton. Install on SYSTEM_IMAGE in TWRP every time. If in TWRP you get issues with flashing on SUPER partitions make sure to flash DynaPatch or Systemrw to disable SYSTEM_READ_ONLY recovery restrictions.
VBEMTA can disable dm-verify and allow modifcations of a PARTITION you wish to modify.
Spoiler: PERENORMAL MODE
If you get in a situation where you trigger PERENORMAL MODE it is easy to get arround it. If your phone got in to perenormal mode after unlocking the bootloader because you failed to get a conection to samsung servers, or if you flashed unofficial binaries and you trigger perenormal mode. Boot in to download mode and run odin, then flash new fimware.
Clean flashing new fimware useing Odin
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # Your warranty is now void # # You have been warned. # # I will laught at you if you point the finger at me...
forum.xda-developers.com
Spoiler: Screen of death after flash of new fimware (screen black)
If you get a pitch balck screen after flashing new fimware, first check if the os driver is beeing recognized. If yes reboot to download mode blindly by VOL- POWER at the same time and then after the phone vibrates imidietly VOL + VOLD - at the same time, if you were able to get here now it is just up to pressing VOL + to get in to odin mode. From your PC flash newer fimware and don't ever again flash back that fimware you flashed and got black screen.
If OS driver isn't beeing recognized and the preloader is(means hard brick), you are going to have to follow these guides on Hovatek's forum
How to revive a totally dead Mediatek device
There are quite a number of reasons why your Mediatek device could not only be bricked but stay totally dead with no sign of life. In such a situation, pressing the power button will have no effect. T
forum.hovatek.com
How to use MTK Bypass to backup or flash secure boot MTK
This is a step by step guide showing how to flash or backup a Mediatek (MTK) secure boot device without using a custom download agent (DA). This tool disables the SLA / DAA bootrom protection A little
forum.hovatek.com
Credit goes to them for does guide.
Spoiler: OEM unlocking option missing
I don't know if this is a glich in the android 11 UI or samsung locking people out of this. What I think is that samsung is trying to prevent people from unlocking the bootloader for some security/warenty problems people have. To bypass this you might have to flash OLDER android 10 fimware see here:
https://forum.xda-developers.com/t/...ng-odin-samsung-galaxy-a12-any-model.4338021/
After flashing older android 10 fimware, set the date and time to something older and enable Dev. options by taping on build number in about phone 8 times. OEM unlocking should apear now and you will be able to unlock the bootloader:
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
If you are haveing issues with pitch balck screen after flashing older android 10 fimware see above.
Spoiler: Phone doesn't get detected by file explorer LINUX OR WINDOWS OR MACOS
If your phone doesn't get detected by your file explorer after installing a custom rom use ADB PULL and ADB PUSH to transfer files. Example
Code:
adb push twrp.img /sdcard
Code:
adb pull /system/etc/hosts C:\platform-tools
When you pull a fle you need to specify the location where the file will be pulled to, for pushing you can specify the adress of the file that will be pushed if it isn't in the SDK PLATFOR TOOLS install folder.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Spoiler: Patched Odin
Some people say useing a patched version of odin is a risk and is basicly the same as normal odin. I my self use a patched version of odin. It will bypass some errors which is useful (example: SW REV check failed BINARY 1: boot 0), it does help with flashing some not certified fimware images. Some people say they have problems with it, there use to be some glitches but the good dev was working hard and is patching glitches. I recomend to anyone that has problems with odin to try this, but at the end of the day heimdall will always be there.
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
Spoiler: RE-LOOCKING THE BOOTLOADER
Do not even think about re-locking the primary bootloader if you are not on OFFICIAL FIMWARE. Allways make sure that you are running 100% official fimware and not custom. If you are planing on re-locking the bootloader, and if you are not sure you are running official fimware, I recomend re-flashing official fimware and then you can lock the bootloader.
Trust me it is worf re-flashing official fimware and then locking the bootloader, because if you get in trouble because you have been running custom fimware and the bootloader locking was outputed to be successful but it actualy wasn't. You will have to go through a lot to fix what will happend.
Clean flashing new fimware useing Odin
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # Your warranty is now void # # You have been warned. # # I will laught at you if you point the finger at me...
forum.xda-developers.com
Spoiler: SIM/Baseband/IMEI errors
If you have SIM/Baseband/IMEI problems after installing a fimware version newer then BUF9, flash this file from odin in CP. Use common logic, it is a modem file so it's supose to go in to CP...
Modem file can be found in this thread:
SIM/Baseband/IMEI errors since Tuesday 17th
I'm getting a problem where everytime I try to call someone or I receive a call, my SIM cards become undetected, the phone crashes after a short time and then doesn't detect SIM cards again, and Samsung or Google backups stop working, and all...
forum.xda-developers.com
Spoiler: DO NOT USE GOOGLE PLAY STORE, AND OTHER GARBAGE
If you really have to use your google play store, please don't. If you need stuff that you can only find on play store you can use aurora store. It is a google play client play, you don't have to login or do anything, you can dowload your google play bloat right out of the box.
You can use F-DROID. A archive full of repositoreis of open soruce programs. Very recomended for privacy and security in mind.
F-Droid - Free and Open Source Android App Repository
F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.
f-droid.org
Aurora Store | F-Droid - Free and Open Source Android App Repository
A Google Playstore Client
f-droid.org
If you don't see some stuff in F-DROID automaticly, then enable other repositoreis in settings...
Spoiler: GSIs and other ROMs crash on latest fimware, or anything over BUF9
If you get issues on some GSIs or other ROMs and you are running fimware over BUF9 version, well that could be the problem... Some people reported it happending on BUG6, BUI3, BUJ4. I personly did get any reboot issues at all on BUG6, but that could be just me. So if you get any issues on ROMs and etc just switch back to BUF9 fimware.
Clean flashing new fimware useing Odin
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # Your warranty is now void # # You have been warned. # # I will laught at you if you point the finger at me...
forum.xda-developers.com

Reserved #1

natedogwoof said:
people know the warntey voids, they will be fine if they aren't dumb and have a phone case and screen protecter.
Click to expand...
Click to collapse
PLEASE DON'T CHAT HERE AS ALREADY MENTIONED IN THE THREAD. CHATING IS ONLY ALOWED IF YOU HAVE TO SAY SOMETHING AGAINTS WHAT I'V SAID.
Please edit your post to "deleted"

LAST_krypton said:
OEM unlocking option missing
[...]
To bypass this you might have to flash OLDER android 10 fimware
Click to expand...
Click to collapse
that's misleading theory. bootloader is downgrade protected. one can only flash ROM with same/higher bootloader level.

aIecxs said:
that's misleading theory. bootloader is downgrade protected. one can only flash ROM with same/higher bootloader level.
Click to expand...
Click to collapse
I think it is possible tho, SW_REV downgrades if able to obtain TEE1 2 tokens. If you're talking about OEM option missing you do have to downgrade back to A10.

LAST_krypton said:
This thread will be updated regularly. If you don't agree with something comment and if I was proven wrong I will update the thread.​Please don't comment or chat here if it isn't releated with something I said. If you need further help with stuff then go here:​
[HELP THREAD] Ask any questions, noob friendly.
Help thread for people that have the Samsung galaxy a12 (any model) Anyone can ask and help others here, but please don't be abusive towards others. No abuse tolerated here! That means: NO TROLLING NO NAME CALLING NO RIDICULING NO FLAMING
forum.xda-developers.com
​
Spoiler: GSIs and other ROMs crash on latest fimware, or anything over BUF9
If you get issues on some GSIs or other ROMs and you are running fimware over BUF9 version, well that could be the problem... Some people reported it happending on BUG6, BUI3, BUJ4. I personly did get any reboot issues at all on BUG6, but that could be just me. So if you get any issues on ROMs and etc just switch back to BUF9 fimware.
Clean flashing new fimware useing Odin
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # Your warranty is now void # # You have been warned. # # I will laught at you if you point the finger at me...
forum.xda-developers.com
Click to expand...
Click to collapse
But i'm on SWREV 2, and BUF9 fw was on SWREV 1, Samsung "protects" against such a downgrade, any workarounds tailored for SWREV 2 fw based A125F devices?

hd_scania said:
But i'm on SWREV 2, and BUF9 fw was on SWREV 1, Samsung "protects" against such a downgrade, any workarounds tailored for SWREV 2 fw based A125F devices?
Click to expand...
Click to collapse
You need TEE tokens for downgrade, might be able to bypass it with patched odin.

LAST_krypton said:
You need TEE tokens for downgrade, might be able to bypass it with patched odin.
Click to expand...
Click to collapse
Did try with patched Odin. But fails still on binary code

edward0181 said:
Did try with patched Odin. But fails still on binary code
Click to expand...
Click to collapse
Heimdall could work

[ROOT] [GUIDE] How to root UMIDIGI A11 Pro Max

*PLEASE BE SURE TO READ EVERYTHING BEFORE ROOTING YOUR PHONE!!!*
This guide will help you to root your UMIDIGI A11 Pro Max. Aside from my own knowledge, I used many sources (and I’ll add the respective references, of course) to create this specific manual. In that regard, I organized the information in many sections due to its size.
Also, please be aware this is a guide for UMIDIGI A11 Pro Max, not UMIDIGI A11 Pro, or UMIDIGI A11, or UMIDIGI A13, or any similar model. You’re free to adapt this guide to a different UMIDIGI model though, so you can copy nearly everything here (with the necessary changes) if you want to.
DISCLAIMER: ALL I WROTE HERE WORKED PERFECTLY WITH MY UMIDIGI A11 PRO MAX, BUILD NUMBER UMIDIGI_A11_PRO_MAX_V1.0_20220108, WHICH I ROOTED WITH MAGISK 24.3, BUT I’M NOT A PROFFESIONAL. THIS MEANS I CANNOT GUARANTEE YOU THIS WILL ALWAYS WORK WITH ANOTHER BUILD NUMBER OR MAGISK VERSION, ALTHOUGH I HONESTLY THINK THERE SHOULDN’T BE ANY PROBLEM. FINALLY, ROOTING IS YOUR DECISION, AND IT'S OWN YOUR RESPONSIBILITY IN CASE YOU BRICK YOUR DEVICE, AS I’M NOT COERCING YOU TO DO IT.
With that said, let’s begin!
Things you need to know:​• Currently, there is no custom recovery (like TWRP) for this smartphone. This will make the whole process a bit more complex, but it’s still possible to get root.
• While I think the rooting itself doesn’t void your warranty, the previous and unavoidable step—unlocking the bootloader—does.
• Another thing about unlocking the bootloader: the process will make a FACTORY RESET to your device, so better have a back-up ready.
• We’ll use Magisk, so it’ll still be possible to get FOTA, also named OTA, updates. I’ll elaborate more at the end of this guide.
• As I said, I’m not responsible If you brick your device, but I can give you a hand! (More details just below.)
Preparations:​• Identify your build number to find your stock ROM online. Go to “Settings”, now go to the bottom to “About phone”, and then go again to the bottom and you will find something like this: “Build number: UMIDIGI_A11_PRO_MAX_V1.0_20220108”.
• Go to your PC and download your stock ROM in UMIDIGI’s official forum. Remember there are main releases’ variations for specific regions (like Europe), so be sure to check if EACH LETTER of the names match. If you made a mistake, you’ll be trapped in a boot loop (bricked device). Here is the forum:
https://community.umidigi.com/forum.php?mod=forumdisplay&fid=293&page=1
Click to expand...
Click to collapse
*THIS STOCK ROM IS NECESSARY TO UNBRICK YOUR DEVICE BY GETTING A FRESH INSTALATION IN CASE OF EMERGENCY, SO PLEASE DO NEVER DELETE IT, PRESERVE IT EVEN AFTER YOU GET ROOT. IF YOU MESSED UP READING THIS GUIDE OR LATER, READ YOUR RESPECTIVE THREAD TO UNBRICK YOUR PHONE. FROM HERE ONWARDS, YOU’LL BE IN THEIR HANDS*
• Open the RAR and extract vbmeta.img and boot.img (DO NEVER DELETE THE ORIGINALS).
• Now you need to unlock “Developer options” in your device, as the basic permissions aren’t enough to root. Go to: Settings > About phone > Status. Now go to the bottom and tap “Build number” seven or eight times until a message saying that you’re now a developer appears.
• Go to Settings > System > Advanced > Developer options. Active them if they’re “Off”, now activate “OEM unlocking” and “USB debugging”. This will allow you to: move files between your phone and PC, and use your PC to modify your phone (explained just below).
Installing Android Debug Bridge (ADB) on your PC:​This “simple” interface, as it uses a terminal window (like CMD or PowerShell in Windows), will allow you to control your device from a computer by using methods hidden to simple mortals (mostly for their own security, because the average user could easily brick their device by accident).
The process to do this may vary depending on your OS (Windows 10, Windows 11, Linux, etc.) or even between different updates or drivers of said OS, so I cannot give you specific steps. You can use this guide, which I’m sure is better than anything I could ever write about this topic:
https://www.xda-developers.com/install-adb-windows-macos-linux/
Click to expand...
Click to collapse
Feel free to search for all the guides you need until installing ADB. Take your time, we’re not doing anything that could brick your device if you make a mistake… yet.
Unlocking the bootloader:​• Make sure ADB is correctly installed or you won’t be able to do anything from this point onwards.
• Remember, this specific step will make a FACTORY RESET to your device, so better have a back-up ready. You need this extra permission to root your phone, or install a custom recovery or ROM if you want (sadly there is neither of them to date).
• Connect your device to your PC.
• Open your ADB terminal on your PC and write:
Code:
adb reboot bootloader
*If doesn’t work, write ./adb instead adb, or the variation your terminal uses, and keep using it from now on. Your device will reboot and now you’ll be in fastboot mode (make sure to read the small > FASTBOOT mode… message on the bottom left corner of your device).
• Now the time has come, after this you’ll have a factory reset. Write:
Code:
fastboot flashing unlock
*Again, if fastboot doesn’t work, use ./fastboot, etc.) and a new message will appear on your device. Read it, it won’t say anything new if you’re with this guide, and press the Volume up button to unlock your bootloader.
• To reboot your device, write:
Code:
fastboot reboot
While rebooting, you will read this just below UMIGIDI’s logo:
Orange state:
Your device has been unlocked and can’t be trusted
Your device will boot in 5 seconds
*Spoiler: it won’t reboot in 5 seconds, but 1 or 2 minutes.
• Congratulations! Now you have a brand-new unlocked phone! No more factory resets (unless you brick your phone), so feel free to make the initial configuration.
This section was based on these guides:
https://www.mobilewithdrivers.com/download/unlock-bootloader/umidigi-a11-pro-max
https://www.droidwin.com/how-to-unlock-bootloader-on-umidigi/
Click to expand...
Click to collapse
Patching images:​• Now this process is the rooting itself, time to get Magisk, the rooting tool and the future manager of your root permission (under your orders, of course). Download its latest version on your device and install it.
• Connect your device to your PC and send boot.img (you extracted it at the beginning of this tutorial) to your smartphone and open Magisk app. On the Magisk section, tap “Install” and then “Select and patch a file” and search for your boot.img to patch it.
• The installation (flashing) will continue in a terminal-like screen. Once finished, the direction of the patched file will appear, along an All done! message.
• Now send this new patched file and the vbmeta.img (you extracted it at the beginning of this tutorial) to your ADB folder in your computer.
• Now turn off your phone and hold Power button and Volume up button for 5 seconds, and select Fastboot Mode.
• Open your ADB window and DO NOT CLOSE IT BEFORE FLASHING THE NEXT 2 FILES, OR YOU'LL BRICK YOUR DEVICE:
THE FIRST FILE: Write the following command:
Code:
fastboot --disable-verity --disable-verification flash boot (insert here the name of your magisk patched file, don’t forget to add the “.img” extension)
Example: My file is called magisk_patched-24300_UuPmm.img, so I wrote:
Code:
fastboot --disable-verity --disable-verification flash boot magisk_patched-24300_UuPmm.img
Don’t forget, write ./fastboot or any command’s variation you’ve been using so far.
THE SECOND FILE: Write the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
• Write this and you’re done:
Code:
fastboot reboot
Enjoy your rooted UMIDIGI A11 Pro Max!
This section was based on these guides:
https://topjohnwu.github.io/Magisk/install.html
https://forum.xda-developers.com/t/umidigi-a11-pro-max-rooted.4366121/
Click to expand...
Click to collapse
About getting FOTA/OTA updates (PLEASE READ THIS TOO OR YOU MAY LOSE YOUR ROOT SOMEDAY!!!):​First, what are FOTA/OTA updates? In short, you could say their function is similar to Windows updates. Usually, rooting with alternatives to Magisk, or installing a custom recovery, prevents you from getting them.
This a rooting guide so, while I won’t help you to getting those updates, I can still give you this comprehensive guide:
https://www.thecustomdroid.com/install-ota-update-rooted-android-device-guide/
Click to expand...
Click to collapse
Lastly, the true reason I wrote this is to alert you that even if you don’t care about FOTA/OTA you still NEED TO DEACTIVATE THE AUTOMATIC UPDATES, otherwise you may lose your root someday or cause problems to your phone (you can search online for the technical reasons of this if you want). From now on, if you want updates, you’ll do it manually.
To deactivate them, go to Settings > System > Advanced > Developer options and turn off "Automatic system updates".
A useful thread about Magisk:​I’ll also leave you this sticky thread of XDA Developers, I’m sure it’ll help you in the future:
https://forum.xda-developers.com/f/magisk.5903/
Click to expand...
Click to collapse
AND THAT’S ALL, THANKS FOR READING!​

thank you for this tutorial I routed my phone but I have orange state at each start which lasts 30 seconds then starts normally what is the problem please and thank you again

hachelfig said:
thank you for this tutorial I routed my phone but I have orange state at each start which lasts 30 seconds then starts normally what is the problem please and thank you again
Click to expand...
Click to collapse
I've tried to find more about that because it kinda annoyed me too, but at the end, it seems to be some sort of "indicator" that you were able to successfully unlock your phone's bootloader. In any case, I'll keep searching and the guide will be updated if I find a way to remove that message.

I used this tutorial https://www.droidwin.com/how-to-remove-red-and-orange-state-warning-in-mediatek-devices/ and it works well thank you

Which vbmeta.img file am I using, when I unpac the file there are:
vbmeta_product.img
vbmeta-sign.img
vbmeta_system.img
vbmeta_sysem_ext.img
vbmeta_vendor.img
Which one should I be using to root?

Oops galeta, would it not have a custom rom or GSI compatible with the Umidigi A11 pro max? I've been looking for something like this for days and I haven't found anything like this, do you know something like this?

hachelfig said:
Eu usei este tutorial https://www.droidwin.com/how-to-remove-red-and-orange-state-warning-in-mediatek-devices/ e funciona bem, obrigado
Click to expand...
Click to collapse
Usei este método! porém meu smatphone morreu! não da sinal de nada

Patrickcnnp said:
Usei este método! porém meu smatphone morreu! não da sinal de nada
Click to expand...
Click to collapse
Foi tudo coreto! ai dei o FASTBOOT REBOOT e não liga mais

I am just wondering if anybody has managed to root the
Umidigi A13 Pro Max 5G

marisaleh said:
Eu só estou querendo saber se alguém conseguiu enraizar o
Umidigi A13 Pro Max 5G
Click to expand...
Click to collapse
Ainda não tive êxito!

Patrickcnnp said:
Ainda não tive êxito!
Click to expand...
Click to collapse
UMIDIGI A13 Pro Max 5G is it a dual slot device?

Be aware guys,
I followed the same procedure above to root UMIDIGI A13 Pro Max 5G
I adapted the procedure to my phone, obviously
It didn't work, ended up with a completely damaged phone.
The only way to recover it was to flash it with the SPFT tool
using firmware mode of flashing,,,
I am just wondering if anybody has managed to
root UMIDIGI A13 Pro Max 5G YET....

marisaleh said:
Be aware guys,
I followed the same procedure above to root UMIDIGI A13 Pro Max 5G
I adapted the procedure to my phone, obviously
It didn't work, ended up with a completely damaged phone.
The only way to recover it was to flash it with the SPFT tool
using firmware mode of flashing,,,
I am just wondering if anybody has managed to
root UMIDIGI A13 Pro Max 5G YET....
Click to expand...
Click to collapse
marisaleh said:
Be aware guys,
I followed the same procedure above to root UMIDIGI A13 Pro Max 5G
I adapted the procedure to my phone, obviously
It didn't work, ended up with a completely damaged phone.
The only way to recover it was to flash it with the SPFT tool
using firmware mode of flashing,,,
I am just wondering if anybody has managed to
root UMIDIGI A13 Pro Max 5G YET....
Click to expand...
Click to collapse
I believe this might be a dual slot device this work only if it is.

Mchlbenner51 said:
I believe this might be a dual slot device this work only if it is.
Click to expand...
Click to collapse
Yes you are right I have just confirmed that using Treble Check app,
it is a dual slot device.
I will now give it another go, and report back
Thanks for you help

Yes Yes Yes
I have just finally succeeded in rooting the Umidigi A13 Pro Max 5G
Yes it is a dual slot device
I rooted it using this simple procedure:
flashed the latest stock rom from Umidigi
Patched boot.img using the latest version of Magisk Manager (magisk_patched.img)
With the phone unlocked and in fastboot mode, I run the following:
fastboot flash boot magisk_patched.img
Fastboot flash vbmeta vbmeta.img
fastboot set_active a
fastboot reboot
The phone rebooted, I completed Magisk install
I now have full root
The orange state warning that pops up on reboot is annoying
and I don't know how to get rid of it yet.
I will be grateful if anyone can help!!!

marisaleh said:
Yes Yes Yes
I have just finally succeeded in rooting the Umidigi A13 Pro Max 5G
Yes it is a dual slot device
I rooted it using this simple procedure:
flashed the latest stock rom from Umidigi
Patched boot.img using the latest version of Magisk Manager (magisk_patched.img)
With the phone unlocked and in fastboot mode, I run the following:
fastboot flash boot magisk_patched.img
Fastboot flash vbmeta vbmeta.img
fastboot set_active a
fastboot reboot
The phone rebooted, I completed Magisk install
I now have full root
The orange state warning that pops up on reboot is annoying
and I don't know how to get rid of it yet.
I will be grateful if anyone can help!!!
Click to expand...
Click to collapse
Does it say your bootloader is unlocked!

Mchlbenner51 said:
Does it say your bootloader is unlocked!
Click to expand...
Click to collapse
It says your device has been unlocked
and cannot be trusted
I'll be grateful if you can help me
get rid of it, it's annoying

marisaleh said:
It says your device has been unlocked
and cannot be trusted
I'll be grateful if you can help me
get rid of it, it's annoying
Click to expand...
Click to collapse
I don't have this phone yet l.
I was pretty sure how to root it so left directions on how to do that.
I would for know l would leave it alone.
When get this phone I will see what I can do about that.
Do not try the remedy that is in this post it could brick your phone.

Mchlbenner51 said:
I don't have this phone yet l.
I was pretty sure how to root it so left directions on how to do that.
I would for know l would leave it alone.
When get this phone I will see what I can do about that.
Do not try the remedy that is in this post it could brick your phone.
Click to expand...
Click to collapse
Thank you very much
I have rooted it with your help
You can see the procedure I
Followed, it's really easy
It's the orange state warning that
I don't know how to remove
I'll wait for you help on that

Mchlbenner51 said:
I don't have this phone yet l.
I was pretty sure how to root it so left directions on how to do that.
I would for know l would leave it alone.
When get this phone I will see what I can do about that.
Do not try the remedy that is in this post it could brick your phone.
Click to expand...
Click to collapse
Good news, I have just managed to remove the orange state warning
Used a Hex editor, modified the stock lk.img and flashed it in fastboot
fastboot flash lk lk.img
Very simple worked perfectly
I am still having a problem with changing selinux mode from
Enforcing to permissive.
I have tried all existing methods and workarounds
I even tried terminal commands like getenforce and setenforce
Nothing will work to change it to permissive
I think it's android 12 security
I will be grateful if anybody can help
Some mods like viper4android will only work if
selinux is in permissive mode

Question Can the P11 Plus be rooted?

Hi all. I'm new to the Lenovo space, so please bear with me. After some searching, I can't quite seem to figure out what the model number of the P11 Plus is? Can anyone enlighten me?
Tab P11 Plus | 11" Family Tablet
Meet the Lenovo Tab P11 Plus, an Android tablet featuring an 11" 2K display and quad speakers for immersive multimedia, plus Google Kids Space and Entertainment Space for family fun and education.
www.lenovo.com
Knowing that, can this particular model's bootloader be unlocked and the OS rooted? Cheers.

Found the model number: TB-J616F or TB-J616X
Android Upgrade Matrix - Lenovo Support US
support.lenovo.com

molohov said:
Found the model number: TB-J616F or TB-J616X
Android Upgrade Matrix - Lenovo Support US
support.lenovo.com
Click to expand...
Click to collapse
Have you found the answer whether the Lenovo P11 Plus (TB-J616F) model can be rooted?

I am thinking of buying this tab. Is it stock unlocked or is it not?

kanines said:
Have you found the answer whether the Lenovo P11 Plus (TB-J616F) model can be rooted?
Click to expand...
Click to collapse
The answer is yes.
First, using Rescue and Smart Assist, DL the latest rom for this model this model. I used TB_J616F_S000046_220311_ROW.
Next go to C:\ProgramData\RSA\Download\RomFiles\TB_J616F_S000046_220311_ROW and you will find the boot.img files. Copy it to a folder on the tablet. Remember where.... duh.
Install Magisk 25.2 which is the version that I used. Follow Magisk instructions to "patch" the copied boot.img file. When complete, copy the patch boot image file back to your Adb/Fastboot folder, normally X:\platform-tools.
Put your tablet in fastboot mode and run: fastboot flash boot <name of patched boot.img file>.
So, there's no need to ask questions as there are a least a bizzion guides on the internet on how to do a "Magisk boot.img patch and flash".

I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.

levrx said:
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
Click to expand...
Click to collapse
every android ive unlocked bootloader, you click on the build number in settings 7 times, after aprox 3 it shows a count down until its unlocked, then it depends on the device im pretty sure, it was diff between my phone n table so it depends on ur device here is some resources
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
How To: Unlock Bootloader
How To Unlock Bootloader Galaxy A12. *** Disclaimer I am not responsible for any damage you made to your device You have been warned - Go to Settings -> About phone and find your build number. - Tap on your build number 6 times until you see...
forum.xda-developers.com
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
there is a diff between download mode and fastboot, just so u know, you need adb and fastboot from Androids SDK tools, you can find online, depending on ur computers OS. Also, ADB commands work with ur device on n plugged into the computer fastboot is for commands when ur in fastboot mode

levrx said:
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
Click to expand...
Click to collapse
I have the same issue!!! It seems a problem with the Fastboot mode.

19blacktiger77 said:
I have the same issue!!! It seems a problem with the Fastboot mode.
Click to expand...
Click to collapse
I solved!!!
I just had to download the latest version of ABD and Fastboot!

Hi. i rooted with this video.. it is in portuguese, but the codes are in english, 15 minutes and it´s done..

I also want to root this device but I am waiting for their Android 12 update. Is anyone running Android 12 ?

I've successfully rooted my Lenovo P11 Plus (J616F) tablet via the latest stock rom + Magisk 25.2, and it was much more painless than I'd thought it'd be. But I can't figure out how to get TWRP or any other custom recovery, and I'd be happy to hear if anyone has had any success with it...
HackVasant said:
I also want to root this device but I am waiting for their Android 12 update. Is anyone running Android 12 ?
Click to expand...
Click to collapse
Yes...
1.) Install USB drivers (I used this to detect fastboot mode: https://motorola-global-en-uk.custhelp.com/app/usb-drivers/)
>> NOTE: With your tablet in fastboot mode, you might have to go into device manager and manually update the drivers for your "unknown android device", pointing it to the usb drivers from the previous step)
2.) Install the lastest ADB and Fastboot software
3.) Unlock your bootloader!
3a.) Enable developer options -> Enable OEM unlocking
3b.) Enter fastboot mode (turn tablet off then hold power + volume up until just after it vibrates)
3c.) With your device connected to your PC, type fastboot flashing unlock in command prompt
4.) Look for the current latest stock rom TB-J616F_S240138_221026_ROW_SVC.ZIP
5.) Extract it somewhere on your PC, and copy boot.img to somewhere on your device
6.) Install Magisk v25.2 on your device
7.) Follow the rest of the installation instructions here: https://topjohnwu.github.io/Magisk/install.html
If all went well, after rebooting you might get a warning about your device being in "Orange State" and therefore cannot be trusted because the bootloader was unlocked... This is normal, and your instinct might be to run the command fastboot flashing lock to get rid of it, but THS IS A BAD IDEA because it could place your device into a "Red State" requiring you to unlock it again, effectively wiping your device

Can it play Redbox (free video app) OK after rooted?
If it's OK, I think Netflix and Amazon Prime will be OK as well

mingkee said:
Can it play Redbox (free video app) OK after rooted?
If it's OK, I think Netflix and Amazon Prime will be OK as well
Click to expand...
Click to collapse
Yes, but you will need to do the following...
1.) In Magisk, make sure you have Zygisk enabled in the settings
2.) Install this Magisk module, then reboot your device:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
3.) Use YASNAC (from the app store) to verify that you pass the safetynet check (it passes for me)
4.) Uninstall Netflix, then manually download and install the latest Netflix APK from your favorite APK site
I didn't test Redbox or Amazon Prime, but I would imagine it'd just be repeating step 4 for each additional app you wish to install
You can also read this for more detailed information about Magisk & SafetyNet:
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com

SpectreCular said:
Yes, but you will need to do the following...
1.) In Magisk, make sure you have Zygisk enabled in the settings
2.) Install this Magisk module, then reboot your device:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
3.) Use YASNAC (from the app store) to verify that you pass the safetynet check (it passes for me)
4.) Uninstall Netflix, then manually download and install the latest Netflix APK from your favorite APK site
I didn't test Redbox or Amazon Prime, but I would imagine it'd just be repeating step 4 for each additional app you wish to install
You can also read this for more detailed information about Magisk & SafetyNet:
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Click to expand...
Click to collapse
The reason why I asked because A12 can make those video apps don't work even after passed safetynet and play integrity (2/3) and apps installed
However, those apps work on OnePlus N200 and 8T but NOT on Moto Edge 2021

mingkee said:
The reason why I asked because A12 can make those video apps don't work even after passed safetynet and play integrity (2/3) and apps installed
However, those apps work on OnePlus N200 and 8T but NOT on Moto Edge 2021
Click to expand...
Click to collapse
Alright well I decided to take the time to check Redbox, and it works (or at least the Watch Free feature does)... And I don't have a prime account, but the prime video app makes it to the sign in screen, if that helps

SpectreCular said:
Alright well I decided to take the time to check Redbox, and it works (or at least the Watch Free feature does)... And I don't have a prime account, but the prime video app makes it to the sign in screen, if that helps
Click to expand...
Click to collapse
Good!
I will make a backup on mine (I have Yoga 11 and practically they're the same) and unlock the bootloader and root it.
The reason why I root it so I can do adb on other device without laptop.
Actually, I have a lot of experience to root variety of machines, but what happened on Edge 2021 A12 puts me on hold on other Moto/Lenovo
I have Netflix and cable apps (Sling and Philo) and Discovery+.

Well just so we're on the same page, the steps I've posted were specifically for J616F, so your mileage may vary if you're using a different device. Also, I would maybe use a more specific stock ROM, since the one I posted is also specifically for J616F

SpectreCular said:
Well just so we're on the same page, the steps I've posted were specifically for J616F, so your mileage may vary if you're using a different device. Also, I would maybe use a more specific stock ROM, since the one I posted is also specifically for J616F
Click to expand...
Click to collapse
I have to make it clear. I have both P11 plus and Yoga 11

I have the P11 Plus J616F model and cannot get the device to unlock after many attempts with wiping device reinstalling firmware reinstalling device drivers. Does failed (unknown status code) after (bootloader) sysytem-fingerprint:Lenovo/TB-J616F/TB-J616F:12/SP1A.210812.0 mean anything to anyone. I can adb reboot recovery, from recovery I can use the keys to choose fastboot and tab goes into fastbootd and fastboot devices returns my device fashboot flashing unlock starts but ends with the failed message above. fastboot getvar all returns a bunch of information about the device but also stops with same failed message. If I choose reboot bootloader using the keys on my tab while in fastbootd tab reboots to FASTBOOT... shows up in device manager as you would expect but typing fastboot flashing unlock returns waiting for device. Any thoughts or ideas would be greatly appreciated.