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.
Related
I need to understand how to update to the new Stock merged partition. Have been reading general advice in various threads that we need to flash new China developer rom. Can someone elaborate regarding how to do this and where to get this rom? Do we need to re-root? Do we need to reflash recovery?
I see that many new MM roms are using this new Stock partition like Matoxxi's newest RR rom. So want to know. Detailed help is highly appreciated... Thanks...
+1
I too would like to see a proper procedure..
This is what I personally did. Was on extended partition. With TWRP as recovery.
1) Flash the cwm r11( or any working cwm) recovery. Needed to flash the repartition zip!! Don't use TWRP. Did this once and had a dead phone. Reboot to recovery. You'll be on CWM.
2) Flash the back to stock partition zip. Choose the one with "el pierro verde" in it.
3) Flash TWRP recovery. Boot to recovery.
4) Flash the 5/12/17 miui zip. This is the ROM which merges the partitions. At this point the partitions are not merged yet!
4.1) Boot the phone up. Reboot to recovery
5) Repeat step 4. Now the partitions are merged.
6) Flash any ROM that you desire.
Of you are on stock partition with TWRP skip steps 1-3.
Good luck.
If you are on MIUI ROM, install 5.12.17 first to merge partitions and then 6.2.4 via Updater app. Xiaomi.eu version is tuned for europe/outside china, Google Apps are included in rom.
https://www.androidfilehost.com/?fid=24369303960690691
https://www.androidfilehost.com/?fid=24415232478676696
Or you can just MiFlash 6.2.4 chinese developer rom factory image from en.miui.com.
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
The only quick way to setup the new partition for now is to fastboot flash the Chinese Dev ROM, as you yourself already stated. You can flash it by fastboot flashing it using Mi PCSuite and choosing the Beta ROM.
On my experience, after the flash I got my bootloader locked ("fastboot oem device-info" resulted in Device unlocked = false), but I can simply unlock it through fastboot without any problem.
From that point, you can easily flash any custom ROM.
Or even MIUI V6, with manual, per partition fastboot flash rather than using MiFlash/Mi PCSuite because of different partition layout; V6 and lower got two boot, modem and system partitions for TDB, while the new has only one.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
Can you boot the phone after the first flashing? Than reboot to recovery and try step 4 again.
Have a look to
http://en.miui.com/thread-209941-1-1.html
there you can find a zip (cancro_merge_partition(2).zip) and the guideline how to use. For me it worked fine.
It does the repartitioning through fastboot by executing 1 shell script. Afterwards you might want to update your recovery rom to an English version.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
Im using Pallmali method to flash, however 1st i try to repeat flash on step 4, it didnt work, then i download MIUI china dev 6.2.4 and flash, wait for a while and it is updated to MIUI 7 MM with merged partition.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
I believe you have to use default Mi Recovery. One time flash of 5.12.17 was enough on my Mi4.
ksloh1 said:
Im using Pallmali method to flash, however 1st i try to repeat flash on step 4, it didnt work, then i download MIUI china dev 6.2.4 and flash, wait for a while and it is updated to MIUI 7 MM with merged partition.
Click to expand...
Click to collapse
It got auto updated? So did you flash stock recovery? Or used twrp
I downloaded 6.2.4 into my phone and then choose the file to update from miui itself, and it will reboot to twrp recovery and install. After fully install and reboot. Only then it will have merged partition and MM miui. And back to stock recovery automatically.
I just fastboot 6.2.4 rom successfully... Now will flash twrp...
And made my first big mistake going in for 6.2.4 beta... It has locked bootloader and a load of Chinese **** you can't make sense of and have to forcefully bear it. Please can anyone help me to unlock the bootloader without begging to the ****ty miui folks?
anshude1 said:
I just fastboot 6.2.4 rom successfully... Now will flash twrp...
And made my first big mistake going in for 6.2.4 beta... It has locked bootloader and a load of Chinese **** you can't make sense of and have to forcefully bear it. Please can anyone help me to unlock the bootloader without begging to the ****ty miui folks?
Click to expand...
Click to collapse
First of all, if you planned to stay on MIUI MM, you don't have any options than requesting an unlock permission to Xiaomi.
If you just want the merged partition and prepared to flash any custom ROM or MIUI V6, enter fastboot then send this command:
Code:
fastboot oem unlock
The reason is that when you unlocks the bootloader through fastboot, it automatically wipes out your phone. IDK why, but possibly inherent to Android's design for security reasons.
rxl.noir said:
First of all, if you planned to stay on MIUI MM, you don't have any options than requesting an unlock permission to Xiaomi.
If you just want the merged partition and prepared to flash any custom ROM or MIUI V6, enter fastboot then send this command:
Code:
fastboot oem unlock
The reason is that when you unlocks the bootloader through fastboot, it automatically wipes out your phone. IDK why, but possibly inherent to Android's design for security reasons.
Click to expand...
Click to collapse
I tried this out, the phone got all wiped but the OEM unlocking button does not work still. So how would I know if the bootloader is unlocked?
anshude1 said:
I tried this out, the phone got all wiped but the OEM unlocking button does not work still. So how would I know if the bootloader is unlocked?
Click to expand...
Click to collapse
OEM Unlocking button? You meant on the Developer Options? That button is currently useless with no function at all. If you want to ascertain if your bootloader is unlocked or not, try sending
Code:
fastboot oem device-info
via fastboot. If the "Device unlocked" comes out as true, then your bootloader is already unlocked.
Ooooor just try to flash any custom recovery/ROM. If it works, then your bootloader is already unlocked.
rxl.noir said:
OEM Unlocking button? You meant on the Developer Options? That button is currently useless with no function at all. If you want to ascertain if your bootloader is unlocked or not, try sending
Code:
fastboot oem device-info
via fastboot. If the "Device unlocked" comes out as true, then your bootloader is already unlocked.
Ooooor just try to flash any custom recovery/ROM. If it works, then your bootloader is already unlocked.
Click to expand...
Click to collapse
Great, big thanks to you... It worked. Device unlocked is True
Funnily it also quoted device tampered is True :laugh:
anshude1 said:
Great, big thanks to you... It worked. Device unlocked is True
Funnily it also quoted device tampered is True :laugh:
Click to expand...
Click to collapse
Yeah, it might be set to true once you had flashed another unsigned image to the eMMC (or when you disconnect the battery, IDK), probably for the warranty checks :q.
knoxwalles said:
Have a look to
http://en.miui.com/thread-209941-1-1.html
there you can find a zip (cancro_merge_partition(2).zip) and the guideline how to use. For me it worked fine.
It does the repartitioning through fastboot by executing 1 shell script. Afterwards you might want to update your recovery rom to an English version.
Click to expand...
Click to collapse
Worked for me
Thank you very much.
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
Download the latest FW files from from http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8/
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled" in developer settings (THIS IS IMPORTANT)
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock command
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.
https://www.thecustomdroid.com/restore-oneplus-5-stock-firmware/
krystyuc said:
https://www.thecustomdroid.com/restore-oneplus-5-stock-firmware/
Click to expand...
Click to collapse
I'm coming from Motorola/Lenovo and I cannot imagine that it is so simple to unlock and relock the bootloader. When you unlock the bootloader on Moto phones you void your warranty. I am so scared from my experience with Motorola that I haven't tried it yet for my OP5.
Can someone please give me some reassurance?
lollyjay said:
I'm coming from Motorola/Lenovo and I cannot imagine that it is so simple to unlock and relock the bootloader. When you unlock the bootloader on Moto phones you void your warranty. I am so scared from my experience with Motorola that I haven't tried it yet for my OP5.
Can someone please give me some reassurance?
Click to expand...
Click to collapse
Yes it's that easy. Done it a few times.
lollyjay said:
I'm coming from Motorola/Lenovo and I cannot imagine that it is so simple to unlock and relock the bootloader. When you unlock the bootloader on Moto phones you void your warranty. I am so scared from my experience with Motorola that I haven't tried it yet for my OP5.
Can someone please give me some reassurance?
Click to expand...
Click to collapse
I can relate to that. I have personally owned two Moto E devices along with the OnePlus One and OnePlus 5, and I can assure that it's way too easy with the latter. I have had really bad experience with Moto, be it updates, unlocking, or downgrading. OnePlus is like a second-Nexus to me, when it comes to such stuff. :good:
deathst said:
Download the latest FW files from from http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8/
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled" in developer settings (THIS IS IMPORTANT)
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock command
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.
Click to expand...
Click to collapse
Thanks for sharing mate.
I`ve alredy rooted with SuperSu and TWRP installed. How do I flash Magisk over SuperSu ?
And I`ve tried to flash latest FW (OOS 4.5.10 Full Zip) with TWRP, but whenever I try to reboot it always says " No OS Installed .......".
I`ve tried several times, but every time it remains the same.
I totally new to OP devices. It would be very helpful, if you share how to revert back to stock OOS and lock the bootloader.
deathst said:
Download the latest FW files from from http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8/
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled" in developer settings (THIS IS IMPORTANT)
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock command
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.
Click to expand...
Click to collapse
It will be good if you can't post exact commands needed to flash stock recovery, relook, etc.
here in this video u can see in detail how to lock bootloader. hope this help
https://www.youtube.com/watch?v=CQYCSdDUdAU
adb sideload fails
deathst said:
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled" in developer settings (THIS IS IMPORTANT)
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock command
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.
Click to expand...
Click to collapse
I have followed the instructions but the adb sideload command fails.
The process stops about 40% and the phone screen shows "failed".
Is there somebody have any guess about why it happens?
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.
Situation:
I tried rooting my phone. I extracted the boot.img with payloaddumper from the latest android 11 Zenfone 8 image from the Asus website (the same version I have on my phone). I patched that image file with Magisk. Flashed that file to my phone with fastboot which succeeded. But after rebooting this is the message I get:
"Your device is corrupted and cannot be trusted and will not boot" and than a link to g.co/ABH
There is no option to "press power to continue" as seen on other screenshots of this problem on YouTube. So I am stuck. I cannot enter recovery. It tries to boot a few times but than stays at the "start" screen while booting.
What I tried to fix this:
Internet states that I have to disable DM check with: adb reboot "dm-verity enforcing". But ADB does not see my device. Fastboot does! So I tried flashing back the original/unpatched boot.img but the result stays the same.
Question:
What can I do to fix this? Also flash Vendor_boot.img? At this moment I rather not do too much but wait for advice/tips in this forum.
And a few "stupid" questions:
- When trying to root the method described here in this forum..... does the bootloader have to be unlocked? My is not.
- IF the bootloader has to be open.... I know I have to use an Asus tool.... but is there a way to do it with ADB/Fastboot?
- When it is necessary to flash my whole device.... is there a way to save my data? (for example flash trwp first and back up data to a thumbdrive)
Any help much appreciated!
>>does the bootloader have to be unlocked
Yes
>>but is there a way to do it with ADB/Fastboot?
No. Only to relock. Or at least I haven't seen such method.
>>When it is necessary to flash my whole device
What do you mean?
>>is there a way to save my data?
If you have root and mean apps data - Swift backup. For me it is failed to restore only few apps (banking + Signal messenger) all other apps are ok.
dron39 said:
>>does the bootloader have to be unlocked
Yes
Click to expand...
Click to collapse
Ok.... bummer..... the device was not unlocked....... So NOT being unlocked did not prevent the flashing I guess. And a locked bootloader is preventing disabling the DM check?
dron39 said:
>>When it is necessary to flash my whole device
What do you mean?
Click to expand...
Click to collapse
If undoing my flash/error (= no unlocked bootloader) is not possible. I have to do a complete reflash I guess. So that would wipe all data. I was wondering if I could flash only parts of the system so some partitions would be spared (so I could save some data..... or install TWRP and maybe save some data)
dron39 said:
>>is there a way to save my data?
If you have root and mean apps data - Swift backup. For me it is failed to restore only few apps (banking + Signal messenger) all other apps are ok.
Click to expand...
Click to collapse
Root was the goal. But that did not happen yet because of the locked bootloader as I understand it now. So no root = no backup/saving data?
If I download the last OTA update my phone recieved, extract boot.img from it and flash that to my phone with fastboot will that restore my phone to a bootable state? If not,what will?