Database Develop

Need help upgrading to 5.1, Tired of flashing all the things.

My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.

Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.

I tried using tge NRT to flash it back to stock but it didn't work.

I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.

http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1

When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...

celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!

Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!

You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.

prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.

rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again

kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.

Nexus 6 - Can't unlock bootloader, ROM wiped, only have TWRP and bootloader. Help?

I've got one you've never heard of before. A Nexus 6 with TWRP loaded. Phone will boot to Recovery or Bootloader, but 'System' boot goes to "Google" and never loads. ROM is gone. Bootloader is locked. Do I have a 3-week-old brick? Phone was previously rooted and functioning, but change from Sprint to Google Fi required the stock ROM. Somehow the bootloader got locked and there was no option to enable developer mode in the ROM. So now we're here. What options do I have, other than buying another phone? I can't RMA, since it's been rooted and unlocked. I'm just screwed out of my $300 phone.

Wipe userdata and cache in TWRP. While in TWRP, hook up to your computer and transfer over a ROM zip (whatever custom ROM). Flash in TWRP.
Voila!

Didgeridoohan said:
Wipe userdata and cache in TWRP. While in TWRP, hook up to your computer and transfer over a ROM zip (whatever custom ROM). Flash in TWRP.
Voila!
Click to expand...
Click to collapse
Bootloader is locked...it won't install the ROMs. I have no way to unlock it at this point.

mightymichelob said:
Bootloader is locked...it won't install the ROMs. I have no way to unlock it at this point.
Click to expand...
Click to collapse
Have you tried? 'Cause the method I describe above have been known to work when people mess up their phones by locking the bootloader without a bootable system.

can you fastboot flash in the bootloader? if so, try Nexus Root Toolkit to try and unlock the bootloader/restore stock/do a thing to get your device back to a useful state.

SamsonIncorporated said:
can you fastboot flash in the bootloader? if so, try Nexus Root Toolkit to try and unlock the bootloader/restore stock/do a thing to get your device back to a useful state.
Click to expand...
Click to collapse
Do tell me which magic toolkit can unlock anything without you enabling Enable OEM Unlocking in settings.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
mightymichelob said:
Bootloader is locked...it won't install the ROMs. I have no way to unlock it at this point.
Click to expand...
Click to collapse
So you didn't try to flash, e.g. cyanogenmod 13 withy TWRP, then boot it up, enable OEM unlocking, and unlock bootloader?

istperson said:
Do tell me which magic toolkit can unlock anything without you enabling Enable OEM Unlocking in settings.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
So you didn't try to flash, e.g. cyanogenmod 13 withy TWRP, then boot it up, enable OEM unlocking, and unlock bootloader?
Click to expand...
Click to collapse
he said he can't install any ROM at this point due to the bootloader being locked. If he can't install a ROM, he can't get into Settings to enable OEM Unlocking. As for being able to flash, whether through toolkit or command line, any suggestion is better than nothing. Ultimately just trying to help a fellow user out.

SamsonIncorporated said:
he said he can't install any ROM at this point due to the bootloader being locked. If he can't install a ROM, he can't get into Settings to enable OEM Unlocking. As for being able to flash, whether through toolkit or command line, any suggestion is better than nothing. Ultimately just trying to help a fellow user out.
Click to expand...
Click to collapse
1. Any valid suggestion, yes, but a shot in the dark doesn't help much, does it now. More so, if we know that toolkits are nothing more than graphical frontends to comandline tools. So if typing fastboot oem unlock gives you error, then executing the same command from the toolkit will give you the same error.
2. There is not enough information on how @mightymichelob tried to flash a rom. Because fastboot flash will fail, while flashing a zip, e.g. cm-13.0 should not.

He has twrp installed what's the big deal, move a rom to SD card from twrp and flash it, am I missing something?

if you have twrp installed, then your bootloader IS unlocked, period. you can not flash twrp with a locked bootloader.
edit.. nevermind, assuming op locked his bootloader. format cache and userdata via fastboot then flash a rom.

Bootloader *was* unlocked. I screwed up and locked it, which then wiped my system settings. I could no longer get in to turn Developer Mode on so I could unlock it again because it said my user didn't have permission. After using NRT, and scouring Google for hours, I ended up with a wiped ROM and an MRT that will no longer mount. I have a ROM pushed to the device, but when trying to install, it fires off error after error about the data partition not existing (it won't mount, either). I have rooted a dozen phones or more in my life...I have no idea why this one decided to brick hard. I have no partitions, no bootloader unlock, and no way to recover. It was a long shot, but I thought maybe there was some magical solution. If it's going to exist, it would be on XDA forums.

Have you tried the repair option in twrp?

mightymichelob said:
Bootloader *was* unlocked. I screwed up and locked it, which then wiped my system settings. I could no longer get in to turn Developer Mode on so I could unlock it again because it said my user didn't have permission. After using NRT, and scouring Google for hours, I ended up with a wiped ROM and an MRT that will no longer mount. I have a ROM pushed to the device, but when trying to install, it fires off error after error about the data partition not existing (it won't mount, either). I have rooted a dozen phones or more in my life...I have no idea why this one decided to brick hard. I have no partitions, no bootloader unlock, and no way to recover. It was a long shot, but I thought maybe there was some magical solution. If it's going to exist, it would be on XDA forums.
Click to expand...
Click to collapse
nope, nothing "magical" exists. the only way to unlock your bootloader is to enable the option in developer settings first. formatting cache and userdata in fastboot should let you flash a rom via twrp.

How to move to new Stock partition?

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.

Big problems after bootloop

Hi all
Unfortunately, I'm having serious problems with my new Mi8, which arrived yesterday. It arrived with Global ROM and opened Bootloader.
Switch On, set up, data from the Mi6 pulled by NFC, all tutti. the Mi account I have connected here too.
Then I wanted to play the xiaomi.eu. TWRP installed via "Minimal adb and fastboot", installed via TWRP then the xiaomi.eu-ROM (newest). Has also worked. When setting up the point that I can play back via NFC what was not displayed, or I have overlooked him. Okay, again from the beginning, I thought. Have then reset the phone to factory settings to repeat the device.
Then the phone stuck in the bootloop. Again and again the Mi logo appeared and "unlocked", disappeared and came back, disappeared and came back. I did not get into the TWRP anymore, just into the fastboot.
On advice of different users on FB and another forum I should flash the Global ROM again over the MiFlash tool, which I did then also. Unfortunately I carelessly chose "Flash-and-Lock" and closed the boot loader. Unfortunately, this flash did not work and the phone now only starts in recovery mode 3.0
Due to the closed boot loader, it is not possible for me to install TWRP again, to flash another ROM with MiFlashTool. Also, the Unlock tool does not work, because I get the error message that the device is not linked to my account. I have also tried to install a recovery mod on the Xiaomi PC suite, as the bar remains on the PC but at 0%, on the phone remains the image with the pictured Mi8, after I in the recovery menu "Connect with MiAssistent "selected. Otherwise nothing happens.
With the latest version of the PC suite flashing works, but still boots the box in the recovery mode and the red font remains. Another user in the other forum said that I need the CN version, because on the CN device no EU-Rome is allowed. The CN version is rejected by the PC suite not get verified.
What else can I do. Do you have an idea that helps me getting the phone back on track?

This, for me, is the biggest joke of Xiaomi! Many users are getting stuck in this new policy! That does not exist! A total lack of respect for brand lovers. Let the developers figure out how to reverse this.

try CN Dev version, is latest and best,
forget xiaomi.eu rom lol, almost all they do you can do by yourself within minutes, uninstalling few chinese apps and get google works with googleinstaller_v3. and dev rom have root. just suggestion.

I tried the last cn-version, but the pc-suite dont verify this ROM and dont flash it.

Rantanplan12345 said:
I tried the last cn-version, but the pc-suite dont verify this ROM and dont flash it.
Click to expand...
Click to collapse
use mi flasher

This is Mi 8 thread not Mi 6.

​
altvolt74 said:
use mi flasher
Click to expand...
Click to collapse
Miflasher dont work, because the bootloader is locked.

To OP and the issue at hand, have you tried the fastboot image to install chinese stable or developer rom? That should flash and allow you to unlock bootloader again.
To the people whining about this policy of Xiaomi, you are buying a product for a different market. There is nothing wrong with their policy and you should wait for global version of the phone if you want global image with locked bootloader. It's a little like complaining that the chinese MMO you play over vpn doesn't have english menus. Well no, it's not for that market.

Superbia said:
To OP and the issue at hand, have you tried the fastboot image to install chinese stable or developer rom? That should flash and allow you to unlock bootloader again.
Click to expand...
Click to collapse
I tried only the chinese recovery rom for flashing with the pc-suite. The fastboot image, I can only flash with twrp or miflashtool, right? TWRP dont work, I cant boot in it. And miflashtool says, as I tried to flash the global rom, that it isnt allowed to erase a locked device.

Rantanplan12345 said:
I tried only the chinese recovery rom for flashing with the pc-suite. The fastboot image, I can only flash with twrp or miflashtool, right? TWRP dont work, I cant boot in it. And miflashtool says, as I tried to flash the global rom, that it isnt allowed to erase a locked device.
Click to expand...
Click to collapse
Nah, the fastboot image flashes best in my experience if you unpack it, all the way. You will get some folders and .bat files. make sure you have fastboot in either PATH or same directory make sure fastboot detects the image and after that run the flash_all.bat and it should flash it.

​
Superbia said:
Nah, the fastboot image flashes best in my experience if you unpack it, all the way. You will get some folders and .bat files. make sure you have fastboot in either PATH or same directory make sure fastboot detects the image and after that run the flash_all.bat and it should flash it.
Click to expand...
Click to collapse
That dont work, because the bootloader is locked. Fastboot says too, that it isnt allowed because the lock, same when I try to install twrp on the locked phone.

Rantanplan12345 said:
​
That dont work, because the bootloader is locked. Fastboot says too, that it isnt allowed because the lock, same when I try to install twrp on the locked phone.
Click to expand...
Click to collapse
Hmm you tried "fastboot oem unlock" also right?

Yes, I tried. Result in a failef, I remember.
Token verify failed

Question???

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.