I have a Realme U1 that I am trying to root. I already have the patched boot image. When I try to go to fastboot mode, it goes into ColorOS recovery mode. There is no option for fastboot in ColorOS recovery mode. Tutorials say that to go in fastboot mode in Realme, I have to do Power + Volume Up instead of Power + Volume Down. Tried that. Didn't work. Just booted normally. Adb is working as usual. BUT when I tried 'adb reboot bootloader', it doesn't work. But when I try 'adb reboot recovery' IT works. At this point, I don't even know what to do. Please help.
SamanwayK2077 said:
I have a Realme U1 that I am trying to root. I already have the patched boot image. When I try to go to fastboot mode, it goes into ColorOS recovery mode. There is no option for fastboot in ColorOS recovery mode. Tutorials say that to go in fastboot mode in Realme, I have to do Power + Volume Up instead of Power + Volume Down. Tried that. Didn't work. Just booted normally. Adb is working as usual. BUT when I tried 'adb reboot bootloader', it doesn't work. But when I try 'adb reboot bootloader' IT works. At this point, I don't even know what to do. Please help.
Click to expand...
Click to collapse
Hello and good afternoon, @SamanwayK2077
Welcome to XDA! I hope you'll alawys get the support your require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
SamanwayK2077 said:
BUT when I tried 'adb reboot bootloader', it doesn't work. But when I try 'adb reboot bootloader' IT works.
Click to expand...
Click to collapse
it works? so what's the problem here then?
Lol
aIecxs said:
it works? so what's the problem here then?
Click to expand...
Click to collapse
I made the question wrong. It is supposed to be:
When I try 'abd reboot bootloader', it does not work. But when I try 'abd reboot recovery', IT works to get me into RECOVERY mode (which I mention because this is proof adb works).
right, seems fastboot mode is disabled forcefully then.
you can unlock bootloader with mtkclient
Code:
python3 mtk da seccfg unlock
you can dump partitions and flash TWRP + vbmeta_disabled.img
Code:
python3 mtk rl out
python3 mtk w recovery twrp.img
python3 mtk w vbmeta vbmeta_disabled.img
vbmeta_disabled.img can generated from avbtool.py or you use copy of out/vbmeta.bin from phone dump and change a single byte with HxD editor
What is 02 in the magisk patched vbmeta.img?
According to the Additional Info given for rooting the Android device that doesn't have ramdisk but can be rooted via recovery: we need an empty vbmeta.img and I am trying to check what it actually
android.stackexchange.com
aIecxs said:
right, seems fastboot mode is disabled forcefully then.
you can unlock bootloader with mtkclient
Code:
python3 mtk da seccfg unlock
you can dump partitions and flash TWRP + vbmeta_disabled.img
Code:
python3 mtk rl out
python3 mtk w recovery twrp.img
python3 mtk w vbmeta vbmeta_disabled.img
vbmeta_disabled.img can generated from avbtool.py or you use copy of out/vbmeta.bin from phone dump and change a single byte with HxD editor
What is 02 in the magisk patched vbmeta.img?
According to the Additional Info given for rooting the Android device that doesn't have ramdisk but can be rooted via recovery: we need an empty vbmeta.img and I am trying to check what it actually
android.stackexchange.com
Click to expand...
Click to collapse
Gonna try this. I hope this will not wipe my data. Will it?
Edit: I dont wanna do any of the aforementioned things. I want to just root and/or enable fastboot mode. How do I do that?
I don't know how to enable fastboot, but for rooting the aforementioned things are recommended.
factory reset is mandatory for rooting. except you use vulnerabilities that allows rooting on locked bootloader.
on old devices like this it might possible to flash magisk patched boot.img on locked bootloader, as avb/dm-verity implementation was weak on mediatek devices up to Android 7. to try this, you need a flash tool like mtkclient or SP Flash tool.
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
aIecxs said:
I don't know how to enable fastboot, but for rooting the aforementioned things are recommended.
factory reset is mandatory for rooting. except you use vulnerabilities that allows rooting on locked bootloader.
on old devices like this it might possible to flash magisk patched boot.img on locked bootloader, as avb/dm-verity implementation was weak on mediatek devices up to Android 7. to try this, you need a flash tool like mtkclient or SP Flash tool.
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
Click to expand...
Click to collapse
not rlly sure, but i think that after i unlock the bootloader i can enable fastboot mode. ill post an update after i have backuped the phone
[DISCUSSION] A thread to collate and share what is known about unlocking fastboot on Oppo devices
Admin: Please move/delete this thread if it is in the wrong place or against the rules. I wanted to create a thread to discuss unlocking fastboot mode on Oppo devices in general, rather than discussing it in terms of any one device in...
forum.xda-developers.com
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016 I was surprised to not find this information in any of the forums. This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone...
forum.xda-developers.com
Related
root: for A.87 stock rom
Unlock bootloader and place the mentioned two files to Platform tools folder on your pc.
Download "vbmeta.img" and "Magisk_patched.img"
• adb devices
• adb reboot bootloader
•fastboot devices
• fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
• fastboot flash boot magisk_patched.img
• fastboot reboot
+++±+++++++
Guide to flash Recovery
- Connect your phone to PC, Allow USB Debugging. Now Type These Commands.
adb reboot bootloader
fastboot devices
fastboot reboot bootloader
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery recoveryname.img
fastboot reboot recovery
To keep custom recovery flash twrpkeep.zip when's booted to recovery :
Bro my device is a.89 ..is this vbmeta working...?
qeb said:
Bro my device is a.89 ..is this vbmeta working...?
Click to expand...
Click to collapse
Yes it work on all a10 update
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
misiek998 said:
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
Click to expand...
Click to collapse
oh, thank's men. edited.
Hello, Can I use the VBMeta on android 11 or no? thanks!
Ryeeeeel said:
Hello, Can I use the VBMeta on android 11 or no? thanks!
Click to expand...
Click to collapse
Can't root rui 2.0 (Android 11), and can't install custom recovery except "los recovery" but can't do any thing with it just wiping cache and data partition.
do not try to flash custom recovery on realme ui 2.0 , it will brick your device
I need to ask, this guide will work with A88/A89 update?
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
adamuadamu said:
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
Click to expand...
Click to collapse
Yes. Just flash the original firmware using SP Flash-Tools. However, youmust make sure it is the full 7-8 GB ROM, and not an OTA file. Also, ensure that you are flashing the correct ROM for your model. If your model is an RMX2155, you'll need to follow this guide steps 1-through-to-10 (inclusive):
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
If it is any other model, just do what is said to work. Unfortunately, I don't know much about the other versions.
thanks the explanation.
I've found a 2155 ROM or at least a file that's said to be - ie. I've found a file 'RMX2155export_11_C.09_2021070809260000', extracted that, there was a huge file 'RMX2155export_11_C.09_2021070809260000.ofp' inside; using oppo-decrypt from github I've got bunch of files with names that seem to be SPFlashTool ROM.
Assuming it's a proper ROM: if I have already unlocked the bootloader, do I have to flash the rom and do the 10 steps from the tutorial or could I replace recovery.img and magisk-patched boot.img and flash rooted rom immediately? Sorry if it sound noobish, but I don't want to brick the phone.
I'm curious to try to go back to stock ROM for a while, because of call quality (I believe changing it to Vietnam needed for unlock made the call quality worse) and to check the camera and it's libraries - I'm running crdroid, photo quality is disappointing no matter what GCam/settings/tweaks I use and there are only imx682/imx471 libs on the phone there are samsung libs, but diagnose apps like aida show the main sensor is imx682, but the EU version of realme 7 is said to have different back camera sensor (GM1). Not sure if RMX2151 ROMs would include proper GM1 libs if that's true about sensor differences between RMX2151 and 2155.
Hello guys,
I'm looking root options for this device.
Phone's bootloader is probably locked,since there is no fastboot mode.
I have patched boot.img made by magisk manager for A slot(don't know if need for B slot too?)And probably i need patched vbmeta which I don't have it.
I see there is in firmware kdz Efuse image too,I'm wonder if I format this partition in with special transsion tool,could it unlock bootloader?
Thanks forwardly for answers.
How to unlock phone's bootloader is described here:
How To Unlock Bootloader On LG K61? [Official Method]
Do you want to know How To Unlock Bootloader On LG K61 then you are at the right place? Today in this article I will guide you step-by-step on How To
myphoneupdate.com
jwoegerbauer said:
How to unlock phone's bootloader is described here:
How To Unlock Bootloader On LG K61? [Official Method]
Do you want to know How To Unlock Bootloader On LG K61 then you are at the right place? Today in this article I will guide you step-by-step on How To
myphoneupdate.com
Click to expand...
Click to collapse
Hello,
Please read a question carefully above
NO fastboot mode enabled in this phone.
jasmin811 said:
Hello,
Please read a question carefully above
NO fastboot mode enabled in this phone.
Click to expand...
Click to collapse
I'm pretty sure Fastboot works if you installl the matching Android USB Driver provided by LG on computer.
jwoegerbauer said:
I'm pretty sure Fastboot works if you installl the matching Android USB Driver provided by LG on computer.
Click to expand...
Click to collapse
LOL. No fastboot, that is, no device in the device manager - means no fastboot mode ...
LG is a different kind of beast...
CXZa said:
LOL. No fastboot, that is, no device in the device manager - means no fastboot mode ...
LG is a different kind of beast...
Click to expand...
Click to collapse
There is device in "Device manager" but no fastboot,or it is hidden!?!
jwoegerbauer said:
I'm pretty sure Fastboot works if you installl the matching Android USB Driver provided by LG on computer.
Click to expand...
Click to collapse
I installed matched Android USB Driver for sure.
jasmin811 said:
There is device in "Device manager" but no fastboot,or it is hidden!?!
Click to expand...
Click to collapse
No, those drivers would help if there would be a fastboot mode.
But it just isn't available. It just boots to normal mode what ever you try, eh?
That is normal for most of the LG phones...
I'm looking for days on how to unlock bootloader on this phone,but the big problem is there is NO fastboot mode installed.
Is there anyway to workaround to unlock or to enable fastboot mode?
Is there any hidden method with buttons or something to enable bootloader?
This model chipset is mt6765 and what I have tried is I patched both boot.img from A and B slot and flashes back with Transsion program but aftet first start it triggers dm-verity.
I also tried formated Efuse,LAf_a and Laf_b and VBMeta partitions,flashed two boot.img patched and after that it is again trigger dm-verity,but HOW???
I'm having the same problem, i have an LG K51S, when i run
Code:
adb reboot bootloader
its reboots to the normal state, idk what to do, if you have any information please contact me.
Thanks
just subscribing to the thread, I need to root as well. No info yet found. I need root
Commander_Monkey said:
I'm having the same problem, i have an LG K51S, when i run
Code:
adb reboot bootloader
its reboots to the normal state, idk what to do, if you have any information please contact me.
Thanks
Click to expand...
Click to collapse
Adb reboot fastboot and you'll be in fastbootd which removes oem commands but I've been working with the stylo6 and K51 which I have the ability to unlock the bootloaders and flash magisk patched boot.img successfully to gain root access.
I've got a k61 now, I've unlocked bootloader and rooted it, the unlock is done in the seccfg partition, I'm days away from sharing a working method to unlock without a paid tool
Warlockguitarman said:
I've got a k61 now, I've unlocked bootloader and rooted it, the unlock is done in the seccfg partition, I'm days away from sharing a working method to unlock without a paid tool
Click to expand...
Click to collapse
Please share if you do.
kingrise said:
Please share if you do.
Click to expand...
Click to collapse
CHeck the Mt version, mt6765 is mt6762, so the following should work, note it's for 10_ and over... ie, not pie, not a/b, it's a only...
Armor x5 Android 10_Q Mt6765 aka Mt6762 ROOT AT LAST!
This 'tutorial' is a quicky for those yet to figure this fone out. Well it took a bit time for sure, but this is how it went... No matter what recovery or magisk I tried, nothing worked, all ulefone images with twrp were 64mb in size, where-as...
forum.xda-developers.com
Warlockguitarman said:
I've got a k61 now, I've unlocked bootloader and rooted it, the unlock is done in the seccfg partition, I'm days away from sharing a working method to unlock without a paid tool
Click to expand...
Click to collapse
Hi, I have a LG K52 and they have the same chipset as LG K61,
I'm having trouble now trying to root and unlock it, can you please explain how you did ?
The only thing I've been able to so far is to get into fastboot and it's in a very very very dirty way, since adb reboot bootloader won't do the trick I had to type adb sideload radomimage.img to get into recovery menu and finally reach Fastboot, but nothing happens when I try fastboot oem unlock or fastboot flashing unlock or anything else
First the adb command is adb reboot fastboot and you can't unlock the bootloader in fastboot, the tool mtkclient from github will do that, i have a group that I sent you the link to in a message, there are instructions and support in there with now almost 200 members. We are helping unlock nearly every newer LG model and many others.
jasmin811 said:
Hello guys,
I'm looking root options for this device.
Phone's bootloader is probably locked,since there is no fastboot mode.
I have patched boot.img made by magisk manager for A slot(don't know if need for B slot too?)And probably i need patched vbmeta which I don't have it.
I see there is in firmware kdz Efuse image too,I'm wonder if I format this partition in with special transsion tool,could it unlock bootloader?
Thanks forwardly for answers.
Click to expand...
Click to collapse
Please help me with the boot.img
How to unlock bootloader and root the LG Stylo 6 and K51 K61 and other K model LG devices
STYLO 6 MTKCLIENT INSTRUCTIONS FOR FLASHING, BACKING UP, UNLOCKING THE BOOTLOADER, AND ROOTING ON WINDOWS 10/11: !!!WARNING!!! ATTEMPT THIS AT YOUR OWN RISK, READ THE FULL TUTORIAL BEFORE YOU START!!! I AM NOT RESPONSIBLE FOR ANY BRICKED...
forum.xda-developers.com
This process works for the k models and you won't need the sp flash tool or the scatter file for your device to work with this tool
Attached is the stock boot image pulled via payload dumper for the OnePlus Nord N200 5G. It is from the full OTA zip - Official Build 11.0.2.0.DE17AA dated September 2nd 2021.
It seems quite a few folks are trying to get ahold of this. *Download link at the bottom*
I AM NOT A DEVELOPER!! I am just posting this for those who need the image file.
The guide to install this is pretty simple. If you have previously rooted the device then you most likely have installed the partially functional version of TWRP for the device. If you have, then you can use the same method for installing TWRP to install the factory boot image. Keep in mind that if you have installed Magisk to the device then you may encounter problems. The following pre-requisites should be followed prior to flashing.
1.) Do a complete uninstall of Magisk if you wish to no longer retain root. There are no guarantees this will work if you keep Magisk on the device. Since Magisk changes the system binaries, stock recovery may not work properly.
2.) Make sure the bootloader remains UNLOCKED! Attempting to lock the bootloader WILL cause an error message that the "Device is corrupt and will NOT BOOT"
3.) Make sure you have enabled USB debugging and your PC can recognize the device. You can do this by booting up the device normally and use the command prompt
adb devices
If the device is recognized it will return with your device ID and "device". If you see anything other than the ID and device (such as unauthorized) then please check to make sure you have enabled USB debugging, the device is plugged to the PC and the path to your platform tools of ADB and Fastboot tools is proper in your command prompt sequence
HOW TO INSTALL:
1.) With the device on and plugged in, open a command prompt in the path that your ADB and Fastboot platform tools are located and type:
adb devices
If properly read, ADB should return with the device ID and "device" as stated above.
2.) Now execute the ADB command:
adb reboot bootloader
Wait a few seconds. The device should now boot into Fastboot Mode.
3.) Now execute the fastboot command:
fastboot devices
The device should now read like earlier with the device ID and "fastboot". If true, fastboot commands will be accepted. Also please double check the device state on the phone screen. Make sure the device is UNLOCKED. If so, stop reading this step and go to step 4. If it is not unlocked DO NOT proceed and reboot the device using the volume keys when the word "START" is in green letters at the top and pressing the power key. DO NOT proceed any further. If your device is functioning in a locked state then stop reading this guide and go back to playing minecraft or flappy bird or whatever it is you do with your phone.
4.) VERY IMPORTANT!! Execute the following fastboot command:
fastboot getvar current-slot
The device will give a letter, either a or b. PLEASE remember the letter as the next step will require that letter after the underscore in the next fastboot command. If slot a, type a; if slot b, type b after typing the underscore.
5.) Make sure this boot image file is located in the same folder as your adb and fastboot for your platform tools and execute the fastboot command:
fastboot flash boot_a boot.img (this is for those who are on slot a from step 4) OR
fastboot flash boot_b boot.img (this is for those who are on slot b from step 4)
6.) You are welcome to flash to both slots if you like as no harm will come from doing this, but only the current slot is necessary for it to work. You can also flash it as many times as you like but that's just dirty flashing over TWRP over and over. Finally wipe the cache and reboot by typing the following fastboot commands:
fastboot -w (this wipes the cache - not necessary but helpful)
fastboot reboot
7.) Enjoy stock recovery. You can also use the volume keys to navigate to "Start" and reboot the device or even try "Recovery Mode" to ensure it worked. I would highly suggest that you boot into recovery and factory reset the device, wiping everything.
*This has been tested and works on the UNLOCKED US variant (Basically, if you can update via the OnePlus website and the build number is DE17AA you're good to go.) DO NOT ATTEMPT THIS ON ANY OTHER CARRIER LOCKED MODEL!!
**While the device is back to stock recovery, the chances are very high that any future OTA's (Full or partial) may not load or install if binaries were altered by Magisk. The best thing to do here is to wait for a full package and install via Oxygen Updater or attempt a partial via Oxygen Updater.
LINK TO IMAGE FILE:
https://www.androidfilehost.com/?w=files&flid=330195
I know I'm replying to an old thread, sorry. I'm wondering if any has the stock T-Mob boot image for Android 12, I flashed a boot.img for the unlocked one and now my phone is boot looping. Has anyone pulled the stock Android 12 boot image for T-Mob yet? Or have a link for the full T-mob Android 12 OTA?
Replying to my own reply here, but I found a link to the T-Mobile Android 12 OTA here: https://community.oneplus.com/thread?id=1599362
Using this, I flashed the correct boot image which fixed the bootloop and now I've rooted it with Magisk.
Can you use this method to flash to de2117_11_c.15?
Hi this was a good guide. Is there a stock boot image for N200 Unlocked Android 12?
rick909 said:
Hi this was a good guide. Is there a stock boot image for N200 Unlocked Android 12?
Click to expand...
Click to collapse
You need to look at the dates of the messages you are replying to as this is a very old thread.
I maintain a thread with the latest boot image to root with guide here:
Root latest US OEM (DE2117)C_23/T-Mobile-Metro(DE2118) C_21 OTA for dummies
I have posted all the boot.img files for N200 A12 to AFH for DE2117 US OEM firmware and now latest for DE2118 (Tmobile/metro) I have posted both the original file as well as pre-patched with Magisk v25.2 for each. The T-Mobile/Metro image...
forum.xda-developers.com
[GUIDE][WINDOWS] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing FirmwaresIntroducing this GuideHello there and welcome to My Guide for Your Xperia Smartphone. This Guide will walk with You thru the whole Process of installing Drivers, getting an unlock Key for Your Bootloader, rooting with Magisk and even flashing GSI Custom ROMs up to re-locking Your Bootloader and re-flashing Stock for the total Factory Reset. This Thread/Guide is not meant as Wiki n'or will it teach You about Android at all. Inform Yourself using Google to enjoy the total Freedom and Customization of Android... If You can't solve Problems Yourself, by communicating and research, don't touch Your Bootloader!
IMPORTANT:
2020+ Xperias are using fastbootd, and equivalent to fastboot which runs in Userspace (Same as Recoveries).
You can access Your Recovery on Your Xperia by holding VolumeDown (-) & the Powerbutton (Your Device needs to be turned off before ofc). Release the Powerbutton after the Display turned on and hold VolumeDown (-) until You see the Recovery Screen. From there, You can enter fastbootd and fastboot. Labled as "Fastboot" for fastbootd and "Bootloader" which is the old fastboot. You can flash Kernels, Recoveries and other stuff from fastboot. Everything else like System Images (GSIs for example), Product Images, System_ext Images and any Userspace stuff has to be flashed from fastbootd. 2019 Xperias are still using fastboot only...
Fastboot and Fastbootd has nothing to do with SONYs Flashmode on Xperias!
INDEX:
Requirements
Installing Drivers
Firmware Flashing
Bootloader Unlocking & Magisk Root
GSI ROM flashing with Fastboot (Optional)
Bootloader Re-Locking (TheWayBack)
Firmware Restoring after Re-Locking
1. Requirements:
Read! Inform Yourself about the Tools You use...
Xperia Basics:
Your Device is turned Off...
Blue LED=Fastboot (Hold VolumeUp (+) & Connect to USB)
Green LED=Flashmode (Hold VoumeDown (-) & Connect to USB)
Windows 10/11 for Firmware flashing & downloading
Xperia Bootloader Unlock Key (From HERE)
Platform Tools alias ADB and Fastboot (From HERE)
Fastboot and Flashmode Drivers (From HERE and HERE)
EMMA for Firmware Updates (From HERE)
XperiFirm for Firmware Downloads (From XDA)
Unsin to extract the Kernel .sin from XperiFirm (From XDA)
Magisk Manager to patch the extracted Kernel .sin (From GitHub)
A working Android System for the Magisk Kernel patching
GSI & vbmeta Image (From Google) (Optional)
A Backup of Your Internal Devices Storage (Optional)
2. Installing Drivers:
Download the Drivers from the Links above and extract them
Install the downloaded and extracted Drivers by right clicking on the ***.inf Files "Install"
3. Flashing Firmwares with EMMA:
Download EMMA and install it
Start EMMA and connect Your Device to USB (Flashmode)
3.1. Downloading Firmwares with XperiFirm:
Download and extract XperiFirm from the link above
Run XperiFirm and Download the right Firmware for Your Device
4. Bootloader Unlocking and Magisk Root:
Note: Since You are going to unlock Your Bootloader, You may surely want to get Root. So let's start with Magisk or it will take more Time afterwards...
Download UnSin from the link above and extract it somewhere
Download the "Platform Tools" from Google and extract it to the root of Your main Windows Drive
Download and install the Magisk Manager on Your Android Device
Extract the File boot_********.sin (60MB+ File) with the Unsin Exe (Drag and drop the Image on the Exe)
You will get a .img File which You can patch now with the Magisk Manager on Your Android Device
Open the Magisk Manager and Install Magisk by selecting the Image File You just got from UnSin
Copy the magisk_patched.img in /download from Your Device to the Platform Tools Folder
Grab Your Device again, go to "About Phone" in the Settings and tap several Times on the build Version
Go now to the Developer Settings under "System" and enable "OEM-Unlock" and "USB-Debugging"
Use now the Platform Tools with this Commands (In Powershell):
Type now (Step by Step):
Code:
cd\
cd platform-tools
Note: To use the Platform Tools Folder as environment for Fastboot and ADB. Or hold Shift and Make a right Click in the Platform Tools Folder to open the Command prompt there...
Type now:
Code:
adb reboot bootloader
You will get a prompt on Your Xperia Device. Your Device will Reboot afterwards...
Now Your Bootloader Unlock Code:
Code:
fastboot oem unlock 0xYOURKEY
Wait for it... And type now:
Code:
fastboot reboot
Wait for Your Device to Wipe and Start. Once in the Android System, turn Your Device off without USB Connected
Press and hold now the VolumeUp (+) Button while connecting to USB to enable the fastboot Mode
Continue with flashing the Images for Root (Step by Step):
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Wipe and Reboot:
Code:
fastboot -w
fastboot reboot
Note: Your are unlocked and rooted now! Enjoy Your Unleashed Device
{
"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"
}
5. GSI flashing with Fastboot:
Note: GSI ROMs can be found around the Web. Like here...
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
Not all GSIs require the vbmeta change. You can use all GSIs that are made for ARM64 + A/B Devices. Play around. Systems can't damage Your Device since You keep the Stock Vendor & Kernel! You can use any Android Version! Don't forget to make backups if needed. You are going to Format Your Device!
Download a GSI Zip from Google
Extract the system.img and the vbmeta.img to Your Platform-Tools
Connect Your Device in Fastboot Mode and use Fastboot with:
(On 2020+ Xperias run: "fastboot reboot fastboot" first after You booted into fastboot)
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot -w (This does Format Your Device and is needed everytime You change the GSI!)
fastboot reboot
6. Bootloader Re-Lock:
Flash the latest Firmware for Your Device with EMMA
Erase all Userdata before You continue (like with fastboot -w or via Recovery)
Just go into Fastboot mode and type in the command prompt (like before in this Guide):
Code:
fastboot oem lock
Wait for Your Device and disconnect it from USB
Done... Continue with Step 7.
7. Firmware Restoring after Re-Locking:
Download and Install the "Xperia Companion" from SONY
Open the Xperia Companion and select Software Repair
Select that Your Device can't get recognized (or is a Smartwatch 3 lol)
Go to the next Page and select the Xperia Smartphone Option
Continue and wait for the Initialization
Press and hold Volume DOWN while connecting to USB (You will see the Green Flashmode LED again)
Continue once Your Device gets recognized and let the Xperia Companion do his work...
Done. Your Bootloader is locked again and almost all of Your DRMs are restored.
So I haven't rooted a phone in a long time. I have gotten my Xperia 5 IV, and I really want to get back into it. Your post looks like a great place to start. However, I have a question, do you think a custom recovery is needed? If so, would you recommend any? I don't see anything about installing TWRP on the 5 IV, and my quick search online hasn't yielded better results.
Anyone know what models can be unlocked? Previous thread says you can't unlock CQ62 (US). CQ44 (Japan) apparently can be unlocked going by same thread, but what about CQ54 (Europe) and CQ72 (Asia)?
Thanks, that's a very helpful guide! I'm now running the latest available Android 13 image for my phone, happily rooted
As it's in the Sony Xperia 5 IV section of the forum it's important to note that you must use fastbootd or you won't be able to wipe the phone. As such, to summarise, the rooting steps are:
- Unlock bootloader
- Download and extract boot.img (on PC)
- Download Magisk and patch boot.img (on phone)
- Reboot to bootloader (adb reboot fastboot) then to fastboot (fastboot reboot fastboot)
- Flash patched boot.img, wipe phone, and reboot
Once rooted you probably want to:
- Install Displax's safetynet-fix to get Google Wallet, Netflix etc working
- Remove unwated bloatware using something like De-Bloater
asdf2345 said:
what about CQ54 (Europe)
Click to expand...
Click to collapse
You can definitely unlock CQ54, as I have just done it.
SekiGamer said:
do you think a custom recovery is needed?
Click to expand...
Click to collapse
I never use custom recoveries, personally, as they're another potential point of failure without any real benefit (you can backup and perform updates easily by other means).
aricooperdavis said:
You can definitely unlock CQ54, as I have just done it.
I never use custom recoveries, personally, as they're another potential point of failure without any real benefit (you can backup and perform updates easily by other means).
Click to expand...
Click to collapse
Ah, that's very good to know. What are the other means that you prefer?
Just got my Japanese SO-54C and went to follow this guide only to find out "Bootloader Unlock Allowed: No".
However, I just got that changed to "Bootloader Unlock Allowed: Yes" so I will follow this guide tonight and unlock my SO-54C bootloader! Can't wait.
Bootloader is now unlocked. However, no matter what I try, the device is never actually rooted.
I'm using the Docomo firmware (xperifirm) 64.1.C.0.102 and I use UnSin on boot_X-FLASH-ALL-C220.sin to get .img. Then I instal MAGISK and push the img file to the phone. Then I use magisk to patch the img and retrieve it from the /Download folder on the device.
I use adb pull to my desktop and I do the fastboot flash boot_a and boot_b, wipe and reboot. After going through the new phone setup, I use Root Checker and it says my phone is NOT rooted.
Am I missing something?
Edit: couple reboots later and magisk did something (some kind of update) and it says rooted.
Kevbodian said:
Just got my Japanese SO-54C and went to follow this guide only to find out "Bootloader Unlock Allowed: No".
However, I just got that changed to "Bootloader Unlock Allowed: Yes" so I will follow this guide tonight and unlock my SO-54C bootloader! Can't wait.
Click to expand...
Click to collapse
How did you get it changed? The removed guide only worked up to the III series.
asdf2345 said:
How did you get it changed? The removed guide only worked up to the III series.
Click to expand...
Click to collapse
I paid for credits on Infinity Online Service - qUnlockTool. The software didn't work, I notified Infinity Team and they gave me a new exe that changed from NO to YES. Then I followed the guide to BLU and root.
Hmm interesting, wonder if it can be used on American devices for the American 4G/5G bands.
How much was it?
asdf2345 said:
Hmm interesting, wonder if it can be used on American devices for the American 4G/5G bands.
How much was it?
Click to expand...
Click to collapse
$30 USD. But DM me if you want more info as I believe paid stuff is not welcome.
As far as bands, I have no idea. I quickly soft-bricked my device tonight and just got it back (bootloader unlocked but root is gone).
Well I mean unlock American devices for those 4G/5G bands not in the overseas phones. Otherwise a method to unlock the bands of the 256GB overseas model would be better.
I find it funny that $30 for a $1000 (or $700) phone bad, but for the Motorola Droid Razr M where the unlock costs more than the phone itself it's completely fine to talk about.
Kevbodian said:
Edit: couple reboots later and magisk did something (some kind of update) and it says rooted.
Click to expand...
Click to collapse
This is one of the devices that Magsik has to install some early hooks for, so indeed to finish root you'll need to open Magisk and it'll tell you that 'additional setup required' and to reboot your device. Then it'll be rooted.
SekiGamer said:
Ah, that's very good to know. What are the other means that you prefer?
Click to expand...
Click to collapse
I use titanium backup and update directly through Magisk or using fastboot.
i never got into titanium to backup my system like i used to with TWRP.....i loved TWRP
Why doesn't anyone try reverse engineering these paid bootloader unlock methods?
gram-hours said:
[GUIDE][WINDOWS] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing FirmwaresIntroducing this GuideHello there and welcome to My Guide for Your Xperia Smartphone. This Guide will walk with You thru the whole Process of installing Drivers, getting an unlock Key for Your Bootloader, rooting with Magisk and even flashing GSI Custom ROMs up to re-locking Your Bootloader and re-flashing Stock for the total Factory Reset. This Thread/Guide is not meant as Wiki n'or will it teach You about Android at all. Inform Yourself using Google to enjoy the total Freedom and Customization of Android... If You can't solve Problems Yourself, by communicating and research, don't touch Your Bootloader!
IMPORTANT:
2020+ Xperias are using fastbootd, and equivalent to fastboot which runs in Userspace (Same as Recoveries).
You can access Your Recovery on Your Xperia by holding VolumeDown (-) & the Powerbutton (Your Device needs to be turned off before ofc). Release the Powerbutton after the Display turned on and hold VolumeDown (-) until You see the Recovery Screen. From there, You can enter fastbootd and fastboot. Labled as "Fastboot" for fastbootd and "Bootloader" which is the old fastboot. You can flash Kernels, Recoveries and other stuff from fastboot. Everything else like System Images (GSIs for example), Product Images, System_ext Images and any Userspace stuff has to be flashed from fastbootd. 2019 Xperias are still using fastboot only...
Fastboot and Fastbootd has nothing to do with SONYs Flashmode on Xperias!
INDEX:
Requirements
Installing Drivers
Firmware Flashing
Bootloader Unlocking & Magisk Root
GSI ROM flashing with Fastboot (Optional)
Bootloader Re-Locking (TheWayBack)
Firmware Restoring after Re-Locking
1. Requirements:
Read! Inform Yourself about the Tools You use...
Xperia Basics:
Your Device is turned Off...
Blue LED=Fastboot (Hold VolumeUp (+) & Connect to USB)
Green LED=Flashmode (Hold VoumeDown (-) & Connect to USB)
Windows 10/11 for Firmware flashing & downloading
Xperia Bootloader Unlock Key (From HERE)
Platform Tools alias ADB and Fastboot (From HERE)
Fastboot and Flashmode Drivers (From HERE and HERE)
EMMA for Firmware Updates (From HERE)
XperiFirm for Firmware Downloads (From XDA)
Unsin to extract the Kernel .sin from XperiFirm (From XDA)
Magisk Manager to patch the extracted Kernel .sin (From GitHub)
A working Android System for the Magisk Kernel patching
GSI & vbmeta Image (From Google) (Optional)
A Backup of Your Internal Devices Storage (Optional)
2. Installing Drivers:
Download the Drivers from the Links above and extract them
Install the downloaded and extracted Drivers by right clicking on the ***.inf Files "Install"
3. Flashing Firmwares with EMMA:
Download EMMA and install it
Start EMMA and connect Your Device to USB (Flashmode)
3.1. Downloading Firmwares with XperiFirm:
Download and extract XperiFirm from the link above
Run XperiFirm and Download the right Firmware for Your Device
4. Bootloader Unlocking and Magisk Root:
Note: Since You are going to unlock Your Bootloader, You may surely want to get Root. So let's start with Magisk or it will take more Time afterwards...
Download UnSin from the link above and extract it somewhere
Download the "Platform Tools" from Google and extract it to the root of Your main Windows Drive
Download and install the Magisk Manager on Your Android Device
Extract the File boot_********.sin (60MB+ File) with the Unsin Exe (Drag and drop the Image on the Exe)
You will get a .img File which You can patch now with the Magisk Manager on Your Android Device
Open the Magisk Manager and Install Magisk by selecting the Image File You just got from UnSin
Copy the magisk_patched.img in /download from Your Device to the Platform Tools Folder
Grab Your Device again, go to "About Phone" in the Settings and tap several Times on the build Version
Go now to the Developer Settings under "System" and enable "OEM-Unlock" and "USB-Debugging"
Use now the Platform Tools with this Commands (In Powershell):
Type now (Step by Step):
Code:
cd\
cd platform-tools
Note: To use the Platform Tools Folder as environment for Fastboot and ADB. Or hold Shift and Make a right Click in the Platform Tools Folder to open the Command prompt there...
Type now:
Code:
adb reboot bootloader
You will get a prompt on Your Xperia Device. Your Device will Reboot afterwards...
Now Your Bootloader Unlock Code:
Code:
fastboot oem unlock 0xYOURKEY
Wait for it... And type now:
Code:
fastboot reboot
Wait for Your Device to Wipe and Start. Once in the Android System, turn Your Device off without USB Connected
Press and hold now the VolumeUp (+) Button while connecting to USB to enable the fastboot Mode
Continue with flashing the Images for Root (Step by Step):
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Wipe and Reboot:
Code:
fastboot -w
fastboot reboot
Note: Your are unlocked and rooted now! Enjoy Your Unleashed Device
5. GSI flashing with Fastboot:
Note: GSI ROMs can be found around the Web. Like here...
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
Not all GSIs require the vbmeta change. You can use all GSIs that are made for ARM64 + A/B Devices. Play around. Systems can't damage Your Device since You keep the Stock Vendor & Kernel! You can use any Android Version! Don't forget to make backups if needed. You are going to Format Your Device!
Download a GSI Zip from Google
Extract the system.img and the vbmeta.img to Your Platform-Tools
Connect Your Device in Fastboot Mode and use Fastboot with:
(On 2020+ Xperias run: "fastboot reboot fastboot" first after You booted into fastboot)
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot -w (This does Format Your Device and is needed everytime You change the GSI!)
fastboot reboot
6. Bootloader Re-Lock:
Flash the latest Firmware for Your Device with EMMA
Erase all Userdata before You continue (like with fastboot -w or via Recovery)
Just go into Fastboot mode and type in the command prompt (like before in this Guide):
Code:
fastboot oem lock
Wait for Your Device and disconnect it from USB
Done... Continue with Step 7.
7. Firmware Restoring after Re-Locking:
Download and Install the "Xperia Companion" from SONY
Open the Xperia Companion and select Software Repair
Select that Your Device can't get recognized (or is a Smartwatch 3 lol)
Go to the next Page and select the Xperia Smartphone Option
Continue and wait for the Initialization
Press and hold Volume DOWN while connecting to USB (You will see the Green Flashmode LED again)
Continue once Your Device gets recognized and let the Xperia Companion do his work...
Done. Your Bootloader is locked again and almost all of Your DRMs are restored.
Click to expand...
Click to collapse
Many thanks for your guide. Im just about to receive my phone in 2weeks time.
Is it a good idea to update android to the latest one before unlocking the bootloader and rooting the device or doesn't matter?
Make sure the device is up-to-date before rooting.
Note: the arms race between those rooting their devices and Google/app developers is particularly fierce at the moment. This means that you are likely to face issues hiding your rooted status from apps.
For example there is currently no way to root and still use both Google Pay and the Starling banking app. This is because Google Pay requires you to use Displax's Universal Safety Net Fix Mod to pass Play Integrity, whilst Starling detects any use of Zygisk (by means currently unknown) which UNSF relies on.
My Zenfone9 AI2202 (JP) Stopped at bootloader screen.
When I select recovery, it reboots and goes back to "Start" screen.
I used the following as a reference
Rooting Zenfone 9 with Magisk
Guide has been reworked to be more clear and based on comments. [Part One] Backup Data Update phone to latest version [Part Two] Download the Firmware for the Zenfone 9...
forum.xda-developers.com
Steps
- I have implemented the following steps
- Update OTA with Version WW-33.0804.2060.113 (2023/03/31)
- Download Same version of firmware
- dump boot.img using Payload Dumper GUI
- I patched boot.img with Magisk
- Execute the following command.
$fastboot flash boot patched_boot.img
I fell into a bootloop.
It is recognized as a fastboot device by Windows11.
Tried
I flashed boot.img before modifying it with Magisk.
Maybe I had wrong version on my device.
ASUS Flash Tool v2.0.1.0 only recognizes it as State: Fast boot device
I referred to the following
https://www.getdroidtips.com/asus-zenfone-9-ai2202-firmware-flash-file/
It says I can select "apply update from sd card." in Recovery mode,
But when I press the power button in Recovery mode, it reboots and won't let me enter recovery mode.
Question
How do I write the whole firmware?
I wish there was a flash-all.bat in the firmware like in Pixel series...
couldn't start from TWRP
$fastboot oem device-info
Device unlocked: false
The device may not have been successfully unlocked.
But then shouldn't fastboot flash boot boot.img fail?
Can boot.img be written without unlocking?
pompom252 said:
couldn't start from TWRP
Click to expand...
Click to collapse
I couldn't boot twrp after flashing magisk too until i remove magisk completely
pompom252 said:
My Zenfone9 AI2202 (JP) Stopped at bootloader screen.
When I select recovery, it reboots and goes back to "Start" screen.
I used the following as a reference
Rooting Zenfone 9 with Magisk
Guide has been reworked to be more clear and based on comments. [Part One] Backup Data Update phone to latest version [Part Two] Download the Firmware for the Zenfone 9...
forum.xda-developers.com
Steps
- I have implemented the following steps
- Update OTA with Version WW-33.0804.2060.113 (2023/03/31)
- Download Same version of firmware
- dump boot.img using Payload Dumper GUI
- I patched boot.img with Magisk
- Execute the following command.
$fastboot flash boot patched_boot.img
I fell into a bootloop.
It is recognized as a fastboot device by Windows11.
Tried
I flashed boot.img before modifying it with Magisk.
Maybe I had wrong version on my device.
ASUS Flash Tool v2.0.1.0 only recognizes it as State: Fast boot device
I referred to the following
https://www.getdroidtips.com/asus-zenfone-9-ai2202-firmware-flash-file/
It says I can select "apply update from sd card." in Recovery mode,
But when I press the power button in Recovery mode, it reboots and won't let me enter recovery mode.
Question
How do I write the whole firmware?
I wish there was a flash-all.bat in the firmware like in Pixel series...
Click to expand...
Click to collapse
Did you unlock your phone via Asus unlock app tool?
this is the link thread to restore back to stock
ZenFone 9 (AI2202) Repair to bootloader package
Download: Link 🔗 Steps: 1. Only works on EDL mode. 2. Run script 0-8475_update_image_EDL_fh_loader.bat 3. Update Official OTA package in recovery or install UserRAW in bootloader Thanks ASUS Taiwan, @EdwardWu6688 , and don't use it for...
forum.xda-developers.com
and for future reference, do not ever ever EVER
"Fastboot boot twrp.img"
Read the thread below, Asus have boot protection so fastboot boot is blocked and can lead to brick
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 9
Official TWRP is now available: https://twrp.me/asus/zenfone9.html IMPORTANT NOTES: CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6). This device has a recovery partition (2...
forum.xda-developers.com
Jairus980 said:
and for future reference, do not ever ever EVER
"Fastboot boot twrp.img"
Read the thread below, Asus have boot protection so fastboot boot is blocked and can lead to brick
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 9
Official TWRP is now available: https://twrp.me/asus/zenfone9.html IMPORTANT NOTES: CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6). This device has a recovery partition (2...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the reply.
Yes, I used Asus unlock app tool.
However, seeing that it is not locked, it may be that the unlocking was not successful.
I have attached a screenshot.
Is an EDL cable required to enter EDL mode?
pompom252 said:
Thanks for the reply.
Yes, I used Asus unlock app tool.
However, seeing that it is not locked, it may be that the unlocking was not successful.
I have attached a screenshot.
Is an EDL cable required to enter EDL mode?
Click to expand...
Click to collapse
adb dont work while on fastboot mode, you cant do via "adb"
I suggest you read the thread above
"ZenFone 9 (AI2202) Repair to bootloader package"
Take your time to read one by one
Jairus980 said:
adb dont work while on fastboot mode, you cant do via "adb"
I suggest you read the thread above
"ZenFone 9 (AI2202) Repair to bootloader package"
Take your time to read one by one
Click to expand...
Click to collapse
Thank you very much. In the relevant thread, you had the information after exchange about whether "EDL cable" is needed or not.
It is important to read carefully.
I solved the problem by running "flashall_AFT.cmd" with device recognized as fastboot device.
Android 12 is now booted!
I was worried that IMEI would disappear, but I was able to keep IMEI.
My device was purchased in Japan, so it was equipped with Felica, which could also continue to be used.
Thank you very much for your good advice.