Related
ATTENTION!
You MUST read all the guide BEFORE doing it, if you do it without reading all of it first you may ends up bricking your phone!
Prerequisites:
Asus ZE500KL (may work on ZE500KG, but haven't tested, do it on your own risk) on Marshmallow, NOT LOLLIPOP!
Also, it must have fully booted AT LEAST one time, otherwise, you'll soft-brick it.
If your phone is not on Marshmallow, you can use THIS guide insteadDownload and put the unlocker zip file and the SuperSu zip file in the phone
How To:
1 - Install adb and fastboot driver (follow THIS guide)
Now you can connect the phone to your computer2 - Reboot in fastboot mode with one of the following method:
a -Volume Up while booting upb -With adb, after enabling USB debugging in developer settings, using:
Code:
adb reboot bootloader
Now that you are in bootloader, you have to boot in TWRP,
download THIS recovery (is the twrp one) and boot in to it, using this command:
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
Code:
fastboot boot TWRP-x-x-x-x.img
(Obviusly the recovery name must be the one you downloaded)
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
It should automaticaly enter in recovery.
Now you MUST flash FIRST ZE500KL_BootloaderUnlock.zip, otherwise you'll brick your phone
Btw, the recovery will mount your phone's memory, so you can put now the files in the phone, if you forgot to do it before
AFTER you installed the unlocker zip, you can install the SuperSu zip
When the install is complete, clear the cache and reboot your phone, now you can enjoy your root!
Downloads:
Latest @MiauLightouch TWRP - 3.0.0.2 Mirror
Latest SuperSu zip - 2.65 Mirror
Bootloader Unlocker (from @MiauLightouch original post) - Mirror
Credits:
@MiauLightouch for pretty much everything
@LuK1337 , @luca020400 and everyone on #titandev for being awesome
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
MuzgontarAco said:
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
Click to expand...
Click to collapse
I would recommend Z00L/T, you will get cm13, official unlock at least.
You Say " May Work On ZE500KG" Is ze500kg already receive Marshmallow Update?
MiauLightouch said:
I would recommend Z00L/T, you will get cm13, official unlock at least.
Click to expand...
Click to collapse
thanks for the advice but my choices are poor with about 5 phones in this price range with this one looking waay better.. getting it via contract so yeah..
How to install supersu zip? Tia.
Working! Have you tried to flash Viper4Android? On lollipop this will break Call recording and FM Radio, maybe this will not be a problem on MM?
Seanjhon027 said:
How to install supersu zip? Tia.
Click to expand...
Click to collapse
Inside TWRP there is a big "Install" button, press it and select the zip
what is the meaning of booted
mohamedelkholy said:
what is the meaning of booted
Click to expand...
Click to collapse
context?
until you saw the lock screen, that's what "booted".
stuck waiting for device
C:\Users\Clynt\Desktop\Android M>adb reboot bootloader
C:\Users\Clynt\Desktop\Android M>fastboot boot twrp.img
< waiting for device >
Ok I don't know where I get wrong but I got this error.
Img file name is ok because I renamed it.
Drivers were installed already.
Developers mode is enabled already.
Windows 7 64bit
Tried rooting this using lollipop and everything went well.
thanks!
UPDATE: i got it. it has something to do with the drivers.
Without opening the bootloader.
Notice. I have not tried it.
http://www.asus-zenfone.com/2016/05/how-to-root-asus-zenfone-2-laser-ze50kl-marshmallow.html?m=1
thanl you man i have rooted my zenfone 2 laser
Thanks very much for this guide and your work.
Can I install the new update v13.10.7.1 when I opened bootloader.
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
thanks
thks TS
now my phone its rooted
Muminek111 said:
Without opening the bootloader.
Notice. I have not tried it.
No... when trace a perequisite link Given..
you really need to unlock bootloader first
wulfe13 said:
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
Click to expand...
Click to collapse
i think isnt permanent, this step is needed to boot into twrp then flashing a unlockBL..
to make permanent.. the command must "fastboot flash recovery twrp_X.X.X.X.img"
but make sure to unlock bootloader first...
CMIIW
Click to expand...
Click to collapse
Is it me or everytime I reboot the device after rooted, it's going back to unrooted?
Root is a success tho, great job, OP!
Edit: okay, not every reboot, but after several reboots, then it went back unrooted
So, I have decided on rooting my Xperia Z3 Compact so that I can finally move OBB to SD card, however I have no knowledge of how roots work (not a programmer much), or which one to pick. I have seen quite a few options for different roots, and previously used Kingo root, but seeing the post about it I am avoiding it like a forest fire. Anyone got good suggestions on which one to pick for my Xperia z3 compact?
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Erm can you explain it so that I will understand it? XD
I kind of understand what you mean but I am still confused here and there....
GarrusN7 said:
Erm can you explain it so that I will understand it? XD
I kind of understand what you mean but I am still confused here and there....
Click to expand...
Click to collapse
Your phone has a recovery. When you bought it, it came with the factory (or stock) recovery. Stock recoveries will only let you flash certain signed zip files and not all (for example - your ota updates). So you need to shift to a custom recovery that will let you flash any file you want. Custom recoveries are device specific. Search how to flash it in your phone. Common ones are - TWRP, cwm, philz.
Once you have your new recovery set up, you are ready to root it. All you have to do is use the recovery to flash the supersu file (i recommend chainfire). If you have twrp installed, the flashable su file is a part of it, and it will guide you.
Reboot after done, and supersu will prompt you to update your su binaries, done. you are all set. Dont forget to unlock the bootloader.
Your warranty will be void unless you revert all changes. Not at all complicated, you do it once and get the hang of it.
A short note on flashing: Flashing is replacing (or installing) certain system files. You can tweak your system in any way you like (overclocking, changing animations, installing apps or scripts, changing the os, etcetera ). Just make sure the zips you flash are compatible.
RealWelder said:
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
dev.kasibhatla said:
Your phone has a recovery. When you bought it, it came with the factory (or stock) recovery. Stock recoveries will only let you flash certain signed zip files and not all (for example - your ota updates). So you need to shift to a custom recovery that will let you flash any file you want. Custom recoveries are device specific. Search how to flash it in your phone. Common ones are - TWRP, cwm, philz.
Once you have your new recovery set up, you are ready to root it. All you have to do is use the recovery to flash the supersu file (i recommend chainfire). If you have twrp installed, the flashable su file is a part of it, and it will guide you.
Reboot after done, and supersu will prompt you to update your su binaries, done. you are all set. Dont forget to unlock the bootloader.
Your warranty will be void unless you revert all changes. Not at all complicated, you do it once and get the hang of it.
A short note on flashing: Flashing is replacing (or installing) certain system files. You can tweak your system in any way you like (overclocking, changing animations, installing apps or scripts, changing the os, etcetera ). Just make sure the zips you flash are compatible.
Click to expand...
Click to collapse
Is chain fire part of Super Su or do you mean instead of it? And what do you mean unlock bootloader???
GarrusN7 said:
Is chain fire part of Super Su or do you mean instead of it? And what do you mean unlock bootloader???
Click to expand...
Click to collapse
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the mazimum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
Thanks. Tho I am sure once I get hands on to it, I will know what to do. Can't wait to move those damned OBB Xd
Just be aware that by unlocking the bootloader you are going to lose camera quality. That's because the keys for image processing are deleted. I think it's only noticeable in low light situations, but still important to know, because once lost those keys will never come back. Therefore I'd rather recommend this rooting method:
https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
fab_ben said:
Just be aware that by unlocking the bootloader you are going to lose camera quality. That's because the keys for image processing are deleted. I think it's only noticeable in low light situations, but still important to know, because once lost those keys will never come back. Therefore I'd rather recommend this rooting method:
https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Click to expand...
Click to collapse
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
fluffi444 said:
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
Click to expand...
Click to collapse
What he/she says. Sorry, I totally forgot about that method, it's much easier, thank you!
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
Well ****....my root doesn't work. I am using SuperSu and TWRP but for some reason a ram disk extraction fails and no install...is it because I have systemless version of my phone or whatever keeps popping up???? And how do I fix that crap???
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
fluffi444 said:
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
Click to expand...
Click to collapse
I unlocked the boot loader the official way (Sony guide and ****). I didn't want to brick my phone accidently.
GarrusN7 said:
I unlocked the boot loader the official way (Sony guide and ****). I didn't want to brick my phone accidently.
Click to expand...
Click to collapse
You wouldn't have bricked your phone
If you followed instructions on their site and contacted them, like unlocking htc bootloader, congratulations, your warranty is officially void.
If you didn't contact them in any wau or uploaded your phone's mac/imei, if you re lock, warranty valid again.
dev.kasibhatla said:
You wouldn't have bricked your phone
If you followed instructions on their site and contacted them, like unlocking htc bootloader, congratulations, your warranty is officially void.
If you didn't contact them in any wau or uploaded your phone's mac/imei, if you re lock, warranty valid again.
Click to expand...
Click to collapse
At least I did this the safe way. Oh well, I never send my phones for repairs as the repairs are always overpriced, my dad fixes everything himself if actually fixable XD.
But my root issue still remains!
GarrusN7 said:
At least I did this the safe way. Oh well, I never send my phones for repairs as the repairs are always overpriced, my dad fixes everything himself if actually fixable XD.
But my root issue still remains!
Click to expand...
Click to collapse
Here's a link from another post. Follow it and check. It should work.
(you've already performed a few of those steps)
link
I was wondering is there any RP2 ROMS like Lineage os or other ROMS? Or not yet or it's not possible to make for this kind of phone or maybe i didn't search more to know what's going on??
No specific ROM for RP2 but you can install GSI ROM after unlocking your bootloader.
Peace
chris5s said:
No specific ROM for RP2 but you can install GSI ROM after unlocking your bootloader.
Peace
Click to expand...
Click to collapse
Okay Thanks for the info, But i'm trying to root my phone on mr2 i can't find any thread that shows how to root mr2 with steps ??
I'm on MR 2 as well. Follow these steps :-
Unlock bootloader.
Flash Arter's kernel from bootloader mode. Then boot into TWRP recovery (comes with Arters kernel) and from there flash latest Magisk zip to get root.
Peace
chris5s said:
I'm on MR 2 as well. Follow these steps :-
Unlock bootloader.
Flash Arter's kernel from bootloader mode. Then boot into TWRP recovery (comes with Arters kernel) and from there flash latest Magisk zip to get root.
Peace
Click to expand...
Click to collapse
Doesn't work on MR2 December realeas i tried and it bricked my phone any other way?
AssyrianHero said:
Doesn't work on MR2 December realeas i tried and it bricked my phone any other way?
Click to expand...
Click to collapse
Yes it does you have to flash the global version NOT the AT&T version.
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3123-user-full.zip
JDBarlow said:
Yes it does you have to flash the global version NOT the AT&T version.
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3123-user-full.zip
Click to expand...
Click to collapse
Yes this is what i'm flashing "aura-p-release-3123-user-full" its global version and i think i'm doing something wrong can you explain step by step instructions? cause i'm new to RP2 and i'm used to old simple root method
Have you tried flashing Arter's kernel then reboot into system before trying to root?
If that works then maybe it's the rooting that's bricking the phone?
Which version of Magisk are you trying to flash?
chris5s said:
Have you tried flashing Arter's kernel then reboot into system before trying to root?
If that works then maybe it's the rooting that's bricking the phone?
Which version of Magisk are you trying to flash?
Click to expand...
Click to collapse
The problem there is no steps that shows what to do I'm just using my own steps, and I'm not using any Magisk I'm just trying to flash Arter's kernel.
Maybe explain what steps you are doing and what errors you are getting then?
Can you put the phone into bootloader mode? Is it unlocked? Do you have adb and do you know how to use it?
Peace.
AssyrianHero said:
Yes this is what i'm flashing "aura-p-release-3123-user-full" its global version and i think i'm doing something wrong can you explain step by step instructions? cause i'm new to RP2 and i'm used to old simple root method
Click to expand...
Click to collapse
Honestly it's easier to root phones today than it ever has especially the RP2.
If you are truly unlocked this should only take you minutes to do.
First things first. Open a terminal where you have ADB / FASTBOOT installed or if you setup the attributes properly just open a terminal.
Type adb devices and it should give you your serial number of your phone. If not adb isn't installed properly.
If so, type adb reboot bootloader and phone will boot to bootloader.
Type fastboot devices and again it should give you the phones ID. If not fastboot isn't installed properly.
If so, type fastboot flash boot and the name of your arter97 file.img this will also install TWRP.
After installation from bootloader menu scroll down to reboot recovery and it should boot to TWRP.
Click cancel then swipe to allow modifications. In TWRP menu select INSTALL then choose where you've saved the magisk 20.3 file on your SD or internal drive.
After installation reboot system then install magisk manager if not already installed. At this point you're rooted. Have a great weekend!!
Good luck! :good:
Make sure you have unlocked your phone, suggest following razer official instruction.(new xda user cant post outside link, search it)
1.Unlock the Bootloader 2.Unlock the Bootloader Critical Partitions 3.Flash official System Image
And please note unlock will erases all user data on the Phone!
After unlocked your phone you can flash arter97 kernel or f(x)THaxxorX TrinityKernel. Both of them contain TWRP, install Magisk Manager and flash Magisk in TWRP. Get rooted.
chris5s said:
Maybe explain what steps you are doing and what errors you are getting then?
Can you put the phone into bootloader mode? Is it unlocked? Do you have adb and do you know how to use it?
Peace.
Click to expand...
Click to collapse
The bootloader is unlocked i do have adb and i i know how to use it I've been rooting all my phones HTC M9 Samsung S7-8-9 and OnePlus 7 I've rooted too many phones but this one is little bit different than others i tried my own steps like i used to do:
I reboot my phone into bootloader and type fastboot devices and it gives me the Serial number and i then i type fastboot boot boot.img i don't know if this command works with this phone it actually worked with other phones this one not..
finixs said:
Make sure you have unlocked your phone, suggest following razer official instruction.(new xda user cant post outside link, search it)
1.Unlock the Bootloader 2.Unlock the Bootloader Critical Partitions 3.Flash official System Image
And please note unlock will erases all user data on the Phone!
After unlocked your phone you can flash arter97 kernel or f(x)THaxxorX TrinityKernel. Both of them contain TWRP, install Magisk Manager and flash Magisk in TWRP. Get rooted.
Click to expand...
Click to collapse
How to unlock the Bootloader Critical Partitions? I think i missed this step i have the bootloader unlocked..
Look on the Razer website for the specific instructions to unlock bootloader/critical.
The fastboot command to flash a boot img is
fastboot flash boot boot.img
Peace
AssyrianHero said:
How to unlock the Bootloader Critical Partitions? I think i missed this step i have the bootloader unlocked..
Click to expand...
Click to collapse
"fastboot flashing unlock" unlock bootloader
"fastboot flashing unlock_critical" unlock the bootloader critical partitions
Also, make sure you're using the Razer recommended USB cord and ADB/Fastboot.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Cables
When connecting your Razer Phone to a computer for any development, it is advised by Razer to not use the in-box USB Type-C to Type-C charging cable for flashing. The supplied cable is specifically engineered for fast power delivery, not for data transfer. Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Upgrade your ADB/Fastboot here.
We got our first recovery for Samsung M40 (SM-M405F). This one is ported using Samsung Auto TWRP recovery porter by Team Hovatek
Please try and let everyone know if it works for you or not.
(If you want to do it yourself for any other Android OS version, you can refer to the original Hovatek post.)
You must disable dm_verity before flashing TWRP.
TWRP based on version: 3.5.*
Details of base recovery used for porting:
Source: Extracted from downloaded firmware
Version: Android 11
Build Date: Mon, 12 Apr 2021 07:54:43 +0000
Security Patch Level: 2021-04-01
Product code: INS
PDA: M405FDDU2CUD2
CSC: M405FODM2CUD2
If this works for you, please post here so everyone will know.
If something goes wrong you need and any stock img/file let me know, I will share that too.
Update 1 =>
NOTE: Unfortunately, I can not test this recovery for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Update 2 =>
Instructions for NON-Rooted and Bootloader locked device-
Unlocking Bootloader:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press Volume Up + Volume Down and plug in your device to a PC to boot into download mode.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Disable DM_Verity (Android Verified Boot):
Copy the vbmeta.img (download from attachments) into your adb and fastboot folder
You can now flash the vbmeta.img using fastboot to remove dm_verity from your device
// Enable USB Debugging and enter following commands in CMD/Terminal after connecting device to computer.
adb devices
// You should see your device listed
adb reboot-bootloader
// Device should reboot to bootloader
fastboot devices
// You should see your device listed
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
// OR if the command above doesn't work, try below
fastboot flash vbmeta vbmeta.img
// DONE
////////////////////////////////++++++++++++++++++++++++++////////////////////////////////
Note: For Magisk Rooted devices above steps are not required, as Magisk already patches vbmeta.img and disabled dm_verity (Android Verified Boot)
Flash TWRP with/without Root using Odin
1. Download and install Odin on your PC
2. Download the attached recovery.img, convert it into .tar
3. Reboot to download mode: power off your device and press Volume Up + Volume Down and plug in your device to a PC to boot into download mode.
4. Select recovery.tar under AP_ and Uncheck “Auto Reboot” in Options!
5. Flash the device
6. Now do not power on to System, enter into Recovery/TWRP mode using key combination.
Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
*DONE*
Enjoy TWRP!
Can you tell step by step procedure for flashing twrp in m40.
How to disable dm-verity?
I guess this didn't work in my device.
"reason recovery: error verifying vbmeta image: invalid vbmata header" error is coming.
Shashvatsawar said:
I guess this didn't work in my device.
"reason recovery: error verifying vbmeta image: invalid vbmata header" error is coming.
Click to expand...
Click to collapse
You must disable dm_verity before flashing TWRP.
Is your device rooted?
How did you flash this TWRP?
Please share your device info.
did you already tested it on your device??
rohitrss said:
You must disable dm_verity before flashing TWRP.
Is your device rooted?
How did you flash this TWRP?
Please share your device info.
Click to expand...
Click to collapse
My Product code : SM-M405FZBDINS
My device is rooted using magisk patch.
I flashed twrp before root using odin.
I didn't disable dm_verity.
How can I disable dm_verity?
deadinside322 said:
did you already tested it on your device??
Click to expand...
Click to collapse
Unfortunately no, I can not do any testing for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Thread title and note updated.
Shashvatsawar said:
My Product code : SM-M405FZBDINS
My device is rooted using magisk patch.
I flashed twrp before root using odin.
I didn't disable dm_verity.
How can I disable dm_verity?
Click to expand...
Click to collapse
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.
rohitrss said:
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.
Click to expand...
Click to collapse
I tried it But I am not able to boot into recovery then.
It just reboots.
Shashvatsawar said:
I tried it But I am not able to boot into recovery then.
It just reboots.
Click to expand...
Click to collapse
Did you try key combination or adb command?
Also, could you please share what all have you tried/done so far so I will have better idea?
I unlocked the bootloader, then booted my device to download mode.. change .img file extension to .tar then tried to flashing it using oden and selected recovery.tar in AP slot.. but it's stuck on file analysis.
Any help? Any step I did wrong? Let me know
Akhil137 said:
I unlocked the bootloader, then booted my device to download mode.. change .img file extension to .tar then tried to flashing it using oden and selected recovery.tar in AP slot.. but it's stuck on file analysis.
Any help? Any step I did wrong? Let me know
Click to expand...
Click to collapse
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.
rohitrss said:
Did you try key combination or adb command?
Also, could you please share what all have you tried/done so far so I will have better idea?
Click to expand...
Click to collapse
I followed this thread to root my device
https://forum.xda-developers.com/t/root-sm-m405f-galaxy-m40.3951491/
There was no option of dm verity while patching stock rom using magisk.
Though My phone was successfully rooted.
I can't use fastboot as it's not showing my device in devices list ( tried a lot).
Finally I flashed your recovery using odin but after going to recovery mode it rebooted only. For recovery mode I tried key combination first and then a root app after device booted.
Updated post with detailed flashing instructions.
rohitrss said:
Updated post with detailed flashing instructions.
Click to expand...
Click to collapse
did the recovery work for you?
Is there any update?
When i try to go to bootloader, my device always go to download mode. how can i fix this???
rohitrss said:
Unfortunately no, I can not do any testing for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Click to expand...
Click to collapse
Bro, I am going to use twrp in my main phone M40.
And I don't care if it gets bricked :>
Hi all,
After multiple issues with this phone, I finally opt out and pass to Pixel 7 Pro.
So, i would like to know how to relock bootloader avoiding the problems of bootloop.
I've uninstall Magisk with option "complete uninstall".
I saw it's better to flash stock image before relock bootloader but how ?
Simply by flashing boot.img on the two slot OR flashing full.zip generated by Oxygen Updater OR other method ?
Thanks a lot for your help !
fma388 said:
Hi all,
After multiple issues with this phone, I finally opt out and pass to Pixel 7 Pro.
So, i would like to know how to relock bootloader avoiding the problems of bootloop.
I've uninstall Magisk with option "complete uninstall".
I saw it's better to flash stock image before relock bootloader but how ?
Simply by flashing boot.img on the two slot OR flashing full.zip generated by Oxygen Updater OR other method ?
Thanks a lot for your help !
Click to expand...
Click to collapse
+1 for leaving OnePlus lol
You need to do both, flash the boot.img, then flash the full zip from oxygen updater
And then after a full reset and full boot up you can relock the bootloader.
zopostyle said:
+1 for leaving OnePlus lol
You need to do both, flash the boot.img, then flash the full zip from oxygen updater
And then after a full reset and full boot up you can relock the bootloader.
Click to expand...
Click to collapse
This phone was promising on paper but the user experience was much less so...
Thank you for the answer !!
For the full zip of Oxygen Updater, I flash it with "fastboot flash full.zip" or how? (I've never flashed a full zip )
fma388 said:
This phone was promising on paper but the user experience was much less so...
Thank you for the answer !!
For the full zip of Oxygen Updater, I flash it with "fastboot flash full.zip" or how? (I've never flashed a full zip )
Click to expand...
Click to collapse
You can use the Local installation system, from the update screen and it that does not support use the OPLocalUpgrade app that Oxygen Updater provides.
zopostyle said:
You can use the Local installation system, from the update screen and it that does not support use the OPLocalUpgrade app that Oxygen Updater provides.
Click to expand...
Click to collapse
Ok thanks !
zopostyle said:
+1 for leaving OnePlus lol
You need to do both, flash the boot.img, then flash the full zip from oxygen updater
And then after a full reset and full boot up you can relock the bootloader.
Click to expand...
Click to collapse
Dear sir, i'm using Ne2213_11_C.30 (Newest Rom). Can u give me the Instructions to relock the bootloader (step by step). I don't know how to flash the boot.img. Thank so much.
hoaianh1505 said:
Dear sir, i'm using Ne2213_11_C.30 (Newest Rom). Can u give me the Instructions to relock the bootloader (step by step). I don't know how to flash the boot.img. Thank so much.
Click to expand...
Click to collapse
If you're on the latest rom there is no need to relock the bootloader
But if you want to, download this https://gauss-componentotacostmanua...23/03/21/b6cfe6d4ec4f4cf7bcb316891f9f8db9.zip
It's the full NE2213 C30 zip file.
Than download https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Intall it on you phone, It will show a new app Local Upgrade, using this tool you will install the above zip file.
After the installation complete, it's recommended to full wipe your device.
Than using adb and fastboot that you can download from here https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
plug you device into your computer
reset it to fastboot mode (turn off, hold power, vol + and vol - until the device start than release power button, once the screen shows the options you can release all buttons and choose fastboot mode if its not there)
on the command prompt type:
Fastboot flashing lock
And that's it.
zopostyle said:
If you're on the latest rom there is no need to relock the bootloader
But if you want to, download this https://gauss-componentotacostmanua...23/03/21/b6cfe6d4ec4f4cf7bcb316891f9f8db9.zip
It's the full NE2213 C30 zip file.
Than download https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Intall it on you phone, It will show a new app Local Upgrade, using this tool you will install the above zip file.
After the installation complete, it's recommended to full wipe your device.
Than using adb and fastboot that you can download from here https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
plug you device into your computer
reset it to fastboot mode (turn off, hold power, vol + and vol - until the device start than release power button, once the screen shows the options you can release all buttons and choose fastboot mode if its not there)
on the command prompt type:
Fastboot flashing lock
And that's it.
Click to expand...
Click to collapse
Thank you so much. Your advice's no need to relock the bootloader, i just worry about the information security. Eg: Banking app can work normal?
After updated to oxygen 13, my phone appear the warning: "phone has been unlocked and cant be trusted ..." each time i boot my device. How can i turn off this warning?
hoaianh1505 said:
Thank you so much. Your advice's no need to relock the bootloader, i just worry about the information security. Eg: Banking app can work normal?
After updated to oxygen 13, my phone appear the warning: "phone has been unlocked and cant be trusted ..." each time i boot my device. How can i turn off this warning?
Click to expand...
Click to collapse
There is no reason to worry about that warning. As your bootloader is not locked the only breach is that a user can manually flash another firmware.
But as he will not have the device on hand there is no problem.
My advice is to not relock, many users bricked their devices doing that.
Also everything works just fine, so no need to relock.
zopostyle said:
There is no reason to worry about that warning. As your bootloader is not locked the only breach is that a user can manually flash another firmware.
But as he will not have the device on hand there is no problem.
My advice is to not relock, many users bricked their devices doing that.
Also everything works just fine, so no need to relock.
Click to expand...
Click to collapse
Thanks for your helpful advice.