Database Users

Guide to switch from Vendor ROM to EU ROM

This is for people who have received their phone with a pre-installed Vendor ROM (MIUI Global Stable 8.0.8.0) and wants to switch to the Unofficial EU ROM. In my opinion, the EU ROM is currently the best ROM without any Chinese bloatware or popups until Xiaomi decides to release an actual Global ROM.
For those who are already on a China Stable ROM, there is already an excellent guide to install TWRP, ROOT, compiled by @underlines. This is only intended for switching from a Vendor ROM as I wasn't able to switch from a Vendor ROM to an official build using the previous guide. You need to be on an official build to be able to use TWRP and flash the EU ROM.
EDIT : The reason why I have mentioned to flash an official build at first is because, TWRP can be unresponsive with some Vendor ROMS. You'll be able to boot TWRP but touch would be frozen. I've tried with both versions of TWRP and it wouldn't work with the Vendor ROM installed on my device. TWRP over the Vendor ROM may work for some users.. For some builds like the one which came installed on my phone, it may not work. If TWRP works for you without being on an official build, you can skip the part where you have to flash an official ROM.
1. You need to have an unlocked bootloader. Please follow instructions on the other guide on how to do this.
2. You need the older version of MiFlash found on this link. Thanks to @Thorin78 for this link.
3. Download and extract fastboot Stable or Dev ROM and extract ROM folder to the C:\ Drive. This is because MiFlash may show a "cannot find file" error if you have a lot of subfolders. To avoid this, its best if the folder is C:\ROM Folder.
4.In the older version of MiFlash, click advanced and change the fastboot script location to the flash_all.bat in your unzipped rom folder.
5.Connect your phone in fastboot mode, click "Refresh" in MiFlash. Once your phone is detected, click "Flash" and it should now successfully flash the official ROM of your choice.
If you wish to be on a Xiaomi Official Stable or Dev ROM, Stop here! If you wish to continue installing the EU ROM proceed with the steps below.
6. Now that you have successfully flashed Official Stable or Dev ROM, use Minimal ADB and flash TWRP RC2 using the instructions in the other guide.
7. Once you are in TWRP, Swipe right to allow System Modifications and copy the forced encryption disabler using MTP. Flash this file to ensure that there are no bootloops.
8. After this step, go to WIPE, Format Storage, type "yes" and then Reboot Recovery. Copy SuperSU and EU ROM to storage and flash. Phone may take a few minutes to boot up and you will successfully boot the EU ROM.
For everything else, please follow the guide posted by underlines.
TWRP EU RC2 works with the China Dev ROM as well. Once you Swipe to Right to allow modifications, don't forget to flash the latest dm-verity and forced encryption disabler script from here. This is to prevent the device going into a bootloop.
These are the steps I followed and I am on EU ROM. Hope this helps people who wish to switch to the EU ROM from the Vendor ROM.

The link to miflash takes you DL minimal adb?

jazz452 said:
The link to miflash takes you DL minimal adb?
Click to expand...
Click to collapse
Corrected. Thanks for letting me know! Cheers!

satishp said:
Corrected. Thanks for letting me know! Cheers!
Click to expand...
Click to collapse
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/

jazz452 said:
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/
Click to expand...
Click to collapse
I guess it also depends on the Vendor ROM and customization which comes installed on your device. Not all Vendor ROMs for this device are the same. I tried everything under the sun with the latest miflash. It would detect device and even give a "success" output but the ROM was never actually flashed. The phone would still be on the Vendor ROM. Its as if some Vendor ROMs have some form of write protection baked in.
I could only get it working with the older miflash.

I'm not saying it was easy, the hard thing was making the unpack ING of the file. Sort of did it twice never had that problem before.

Why is it required to flash the official rom before flashing the EU rom?

nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This for people who don't want TWRP, root and dm-verify, just genuine Xiaomi rom with OTA updates and remove vendor rom.

QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?

geubes said:
QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?
Click to expand...
Click to collapse
Wouldn't worry about it the vendor ROMs aren't poison, not sure about dm-verify if you kept read only. I would of swiped then flashed dm-verify but didn't mean I know what I'm doing.

nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This is because some Vendor ROMS have some compatibility issues with TWRP. Touch screen wouldn't work on TWRP. I tried both TWRP versions and couldn't get touch to work.
Finally, I flashed the China Dev ROM and then used TWRP RC2 and touch functionality worked.
As some users below have pointed out that they could get to EU without flashing the one of the official builds, I guess it depends on the amount or type of vendor customizations applied on your device.

Which version do you own? I was wondering if this would work with the 6GB as well.

dbesada said:
Which version do you own? I was wondering if this would work with the 6GB as well.
Click to expand...
Click to collapse
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.

satishp said:
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.
Click to expand...
Click to collapse
Thank you. It worked. I fastboot twrp then factory reset the device and flashed the eu rom. All good. My bootloader was unlocked by the vendor.

Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks

SantinoInc said:
Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks
Click to expand...
Click to collapse
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU

Razorbacktrack5535 said:
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU
Click to expand...
Click to collapse
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?

SantinoInc said:
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?
Click to expand...
Click to collapse
Yes, you have to use Fastboot Mode

Razorbacktrack5535 said:
Yes, you have to use Fastboot Mode
Click to expand...
Click to collapse
I'm not unlocked right? Hope they approve my unlock request soon

SantinoInc said:
I'm not unlocked right? Hope they approve my unlock request soon
Click to expand...
Click to collapse
Yes, you have to wait

[FIX][OP3/OP3T] DM-Verity warning fix. Works on 4.1.0!!

Hi, i discovered a fix for this problem and made 2 flashable zips. Follow the steps.
If you have 4.0.2 or older just do steps 3 and 4.
1- Download the 4.0.2 firmware and the firmware of your current version:
OP3T files:
Oxygen 4.1.1:https://drive.google.com/open?id=0Bzko1towAti5XzNCRVVwUVYzRms
Oxygen 4.1.0:[url]https://drive.google.com/open?id=0Bzko1towAti5WW1rUThrb3lHUWs[/URL]
Oxygen open beta 3:[url]https://drive.google.com/open?id=0Bzko1towAti5d3BtOEtXdk9hVTA[/URL]
Oxygen 4.0.3:[url]https://drive.google.com/open?id=0Bzko1towAti5NzU5b3lDaEZfZ3M[/URL]
Oxygen 4.0.2:[url]https://drive.google.com/open?id=0Bzko1towAti5NGVsTUtfd2VUY2M[/URL]
OP3 files:
Oxygen 4.1.1:https://drive.google.com/open?id=0Bzko1towAti5eXpXOXRUcXRoeXc
Oxygen 4.1.0:[url]https://drive.google.com/open?id=0Bzko1towAti5WEtoYXd0NW1qUVk[/URL]
Oxygen open beta 12:[url]https://drive.google.com/open?id=0Bzko1towAti5aVVvNkIwTURjaE0[/URL]
Oxygen 4.0.3:[url]https://drive.google.com/open?id=0Bzko1towAti5SW5FdE1EczQybUU[/URL]
Oxygen 4.0.2:[url]https://drive.google.com/open?id=0Bzko1towAti5eDFmZzZPQVI2OXc[/URL]
2- Flash in TWRP the 4.0.2 firmware zip.
3- Reboot to bootloader and connect your phone to the pc.
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
5- Reboot to recovery
6- Flash in TWRP the firmware of your current OOS version.
And you are done! :highfive:

Migdilu said:
Hi, i discovered a fix for this problem and made 2 flashable zips. Follow the steps.
1- Download the two files:
[url]https://drive.google.com/open?id=0Bzko1towAti5Uld0cWp1YWdfLXM[/URL]
[url]https://drive.google.com/file/d/0Bzko1towAti5LXFUbEJwYUFFbGc/view?usp=sharing[/URL]
2- Flash in TWRP the 4.0.2 firmware zip.
3- Reboot to bootloader.
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
5- Reboot to recovery
6- Flash in TWRP 4.0.3 firmware zip.
And you are done! :highfive:
Click to expand...
Click to collapse
thanks for the fix
but 4.0.3 firmware says 3.5.3 firmware for 3t.Is that a updater script error??

kunal1540 said:
thanks for the fix
but 4.0.3 firmware says 3.5.3 firmware for 3t.Is that a updater script error??
Click to expand...
Click to collapse
Exactly, I'm uploading a new file correcting that. But don't worry, you flashed the 4.0.3 firmware. Thanks for the report!

Worked for me as well. Thank you.

thanks worked at my 1+3T.

working for me also on A3010.
thanks.

Please add
Code:
getprop("ro.display.series") == "OnePlus 3T" || abort("E3004: This package is for \"OnePlus 3T\" devices; this is a \"" + getprop("ro.display.series") + "\".");
as first line in your updater-script which prevents bricked devices.

Nice to see it's working!
sniperle said:
Please add
as first line in your updater-script which prevents bricked devices.
Click to expand...
Click to collapse
I'll check that later, thanks!

I just flashed 4.0.2 firmware zip.
Then choose Reboot to bootloader.
Phone just goes off.
Now wont power at all. Even if I plug in to power it up, the light doesnt lit up.
It's comepletly dead now
Oh, god, I just killed my phone beacouse that verity thing! I should leave it alone.

done it with 4.0.2 rooted and without succes

Is this only for OnePlus 3T?
I fuc..d my device beacouse I flashed this on my OnePlus 3?
I didn't look the topic name before. And in post it didnt stated taht its for OP3T only.

nitramcek said:
I just flashed 4.0.2 firmware zip.
Then choose Reboot to bootloader.
Phone just goes off.
Now wont power at all. Even if I plug in to power it up, the light doesnt lit up.
It's comepletly dead now
Oh, god, I just killed my phone beacouse that verity thing! I should leave it alone.
Click to expand...
Click to collapse
You did something wrong. Do you have 3 or 3t?

nitramcek said:
Is this only for OnePlus 3T?
I fuc..d my device beacouse I flashed this on my OnePlus 3?
I didn't look the topic name before. And in post it didnt stated taht its for OP3T only.
Click to expand...
Click to collapse
Its on oneplus 3t forum.. Can you boot to booloader?

madmax28011980 said:
done it with 4.0.2 rooted and without succes
Click to expand...
Click to collapse
Just do step 3 and 4 if you are on 4.0.2 or older. Now flash 4.0.2 firmware and then do 3 and 4 and you are done.

off topic I know, but can someone explain why people are getting this error? If you root correctly you don't this error.

Migdilu said:
Its on oneplus 3t forum.. Can you boot to booloader?
Click to expand...
Click to collapse
No. It's compleatly dead.
I got in this forum thru link on other forum about DM-verity and didnt really look on what forum I landed until i bricked device.

nitramcek said:
No. It's compleatly dead.
I got in this forum thru link on other forum about DM-verity and didnt really look on what forum I landed until i bricked device.
Click to expand...
Click to collapse
I'm sorry. Make a thread on oneplus 3 forum explaining that you accidentally flashed 3T firmware, maybe someone has a solution for this.
EDIT: Take a look at the unbrick guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

Snappiestjack said:
off topic I know, but can someone explain why people are getting this error? If you root correctly you don't this error.
Click to expand...
Click to collapse
Not sure what/if I've done wrong TBH... still, I had the message

I reflashed op3t recovery i then reflashed oxygen 4.0.2 but still getting the error then i flashed twrp 3. and then the su after that i have flashed your 4.0.2. Img and gave the fastboot commands still the error is there maybe i do something wrong! The weird is that when i enter twrp it asks me for a pattern... Should i remove security locks from oxygen 4.0.2 and try again! Anyway.. Goodnight for now.

It's worked!!!
thx a lot!!!

Downgrade is it allowed?

I'm using Rn7 4gb 64gb PFGMIXM global version. I wonder if i will unlock bootloader and install TWRP or Orange it will allow me to downgrade version without bricking or any problem?

On global rom the ARB is activated, if you want to downgrade to older version you can use miui.eu instead because there is no ARB on miui.eu

Hi there, you can downgrade between MIUI 10.X without the need of use of TWRP/ORANGE, you just need the Bootloader unlocked and the MI Flash Tool with any Fastboot Miui ROM (But if you want to, you can still use the custom recoveries for Recovery ROMs) I Downgraded from 10.3.6.0 to 10.2.7.0 with fastboot rom and everything went smooth. (Be aware that after using MI Flash tool the Bootloader will be relock)

BlackGarnett said:
Hi there, you can downgrade between MIUI 10.X without the need of use of TWRP/ORANGE, you just need the Bootloader unlocked and the MI Flash Tool with any Fastboot Miui ROM (But if you want to, you can still use the custom recoveries for Recovery ROMs) I Downgraded from 10.3.6.0 to 10.2.7.0 with fastboot rom and everything went smooth. (Be aware that after using MI Flash tool the Bootloader will be relock)
Click to expand...
Click to collapse
Can you give instruction? After bootloader unlock? I read other comment from other thread it can brick the device. Do we have the same device? 48mp cam and PFGMIXM? Can you post here your screenshot of your current Rn7 version?
If i'm going to install TWRP is it safer than downgrade using MI flashtool?

gAracUh said:
Can you give instruction? After bootloader unlock? I read other comment from other thread it can brick the device. Do we have the same device? 48mp cam and PFGMIXM? Can you post here your screenshot of your current Rn7 version?
If i'm going to install TWRP is it safer than downgrade using MI flashtool?
Click to expand...
Click to collapse
Hi sure, I'm on 10.3.5.0 right now, found it as the better ROM for my personal using, and yes I have global version PFGMIXM, after testing what I needed to, between 10.3.6.0-10.2.7.0 I stayed up in 10.3.5.0. (I can't post any screenshot right now but maybe later I might attach to this post --- Update, attached the screenshot)
-About the brick, I actually can't explain what it triggers but most of the time I belive has been happening to others RN7 versions.
-About the TWRP safety, is the same I believe (as long as you know what you are doing), I prefered to try the downgrade my first time using MI flashtool cuz it's official and less possibilities of problems, you can always unlock again the bootloader after the flash doing the same steps and w/o waiting time cuz already did that phase.
-The instructions are simple and they are the same given by Xiaomi in their ROM site.
On here: Fastboot Method
Instructions via Fastboot method:
-Download and install the Adb+fastboot drivers or xiaomi drivers for rn7 (that I believe you already have if you unlocked the bootloader)
-Download and install the Mi FlashTool (The link above)
-Download the FASTBOOT ROM for you need, remember it to be PFGMIXM (On internet you can find the 10.2.7.0/10.2.8.0 and the 10.3.5.0 FASTBOOT ROM -- On Xiaomi site you can find the 10.3.6.0 lastest fastboot ROM)
-Turn off the device. Press the Volume– key and the Power button at the same time to enter Fastboot mode. Then connect the device to the Windows PC/laptop via a micro USB cable.
-Double click on the downloaded ROM file to decompress it. Open the file folder for the decompressed ROM pack, and copy its path .
-Open the MI flashtool and you can either click "select" to search the folder of the uncrompressed ROM or just paste the path if you copied it early (example: C:\User\User1\Desktop\complete_folder_rom).
-Click Refresh and the device will be detected automatically.
-Then just click flash and wait the process that will take some minutes
-After the flash is done, the status will say "flash done" and will appear a "success" message, then the phone will reboot itself and start as it was out-of-the-box for the first config
Same instructions are with pictures in the link.
I didn't tried the downgrade in TWRP/Orange but I believe is the same as flashing any ROM, wipe dalvik, cache, data, system and then flash the ROM - for TWRP/Orange the ROM is the "Recovery" version ones, not the Fastboot as the steps above (TWRP will always mark you an error for MIUI Recovery ROMS so erase "compatibility.zip" in the ROM, this usually is not needed in Orange as I belive i've read it)
My recommendation is to use the Fastboot Method
Also PFGMIXM ver only have the ROM versions mentioned, 10.2.3.0 (10.2.3.0 PFGMIXM not the EEA one, it's rare to see and only come in stocks phones) it's a rare out-of-the-box-rom-version I saw, and the 10.2.1.0 was deleted from Xiaomi servers long time ago, so to downgrade you are only going to find the 10.2.7.0 ROM.

BlackGarnett said:
Hi sure, I'm on 10.3.5.0 right now, found it as the better ROM for my personal using, and yes I have global version PFGMIXM, after testing what I needed to, between 10.3.6.0-10.2.7.0 I stayed up in 10.3.5.0. (I can't post any screenshot right now but maybe later I might attach to this post --- Update, attached the screenshot)
-About the brick, I actually can't explain what it triggers but most of the time I belive has been happening to others RN7 versions.
-About the TWRP safety, is the same I believe (as long as you know what you are doing), I prefered to try the downgrade my first time using MI flashtool cuz it's official and less possibilities of problems, you can always unlock again the bootloader after the flash doing the same steps and w/o waiting time cuz already did that phase.
-The instructions are simple and they are the same given by Xiaomi in their ROM site.
On here: Fastboot Method
Instructions via Fastboot method:
-Download and install the Adb+fastboot drivers or xiaomi drivers for rn7 (that I believe you already have if you unlocked the bootloader)
-Download and install the Mi FlashTool (The link above)
-Download the FASTBOOT ROM for you need, remember it to be PFGMIXM (On internet you can find the 10.2.7.0/10.2.8.0 and the 10.3.5.0 FASTBOOT ROM -- On Xiaomi site you can find the 10.3.6.0 lastest fastboot ROM)
-Turn off the device. Press the Volume– key and the Power button at the same time to enter Fastboot mode. Then connect the device to the Windows PC/laptop via a micro USB cable.
-Double click on the downloaded ROM file to decompress it. Open the file folder for the decompressed ROM pack, and copy its path .
-Open the MI flashtool and you can either click "select" to search the folder of the uncrompressed ROM or just paste the path if you copied it early (example: C:\User\User1\Desktop\complete_folder_rom).
-Click Refresh and the device will be detected automatically.
-Then just click flash and wait the process that will take some minutes
-After the flash is done, the status will say "flash done" and will appear a "success" message, then the phone will reboot itself and start as it was out-of-the-box for the first config
Same instructions are with pictures in the link.
I didn't tried the downgrade in TWRP/Orange but I believe is the same as flashing any ROM, wipe dalvik, cache, data, system and then flash the ROM - for TWRP/Orange the ROM is the "Recovery" version ones, not the Fastboot as the steps above (TWRP will always mark you an error for MIUI Recovery ROMS so erase "compatibility.zip" in the ROM, this usually is not needed in Orange as I belive i've read it)
My recommendation is to use the Fastboot Method
Also PFGMIXM ver only have the ROM versions mentioned, 10.3.4.0 (10.3.4.0 PFGMIXM not the EEA one, that's why it's rare to see and only come in stocks phones) it's a rare out-of-the-box-rom-version I saw, and the 10.2.1.0 was deleted from Xiaomi servers long time ago, so to downgrade you are only going to find the 10.2.7.0 ROM.
Click to expand...
Click to collapse
Thank you very much for detailed instructions the reason why i want to downgrade is the battery life. I noticed after two consecutive update within one month the battery backup is not good like before. I am pretty sure about that because it has been 1 month since i bought this.
Even the power saver is always activated I'm not satisfied with the battery backup now. I'm thinking if i will flash Havoc, Lineage or Lower version of miui what do you think? which of these is good for battery?

gAracUh said:
Thank you very much for detailed instructions the reason why i want to downgrade is the battery life. I noticed after two consecutive update within one month the battery backup is not good like before. I am pretty sure about that because it has been 1 month since i bought this.
Even the power saver is always activated I'm not satisfied with the battery backup now. I'm thinking if i will flash Havoc, Lineage or Lower version of miui what do you think? which of these is good for battery?
Click to expand...
Click to collapse
Yes I did it due the same thing, for battery and ram management, but most of it perfomance, and I got it balanced on 10.3.5.0, not the best but it does the job for me. I haven't tested Havoc neither Lineage, but if just battery your concern, you can take a read to LionHeart90's Guide ON THIS LINK or you can go and try by yourself each ROM till you find the most one that suit for you :good:

BlackGarnett said:
Yes I did it due the same thing, for battery and ram management, but most of it perfomance, and I got it balanced on 10.3.5.0, not the best but it does the job for me. I haven't tested Havoc neither Lineage, but if just battery your concern, you can take a read to LionHeart90's Guide ON THIS LINK or you can go and try by yourself each ROM till you find the most one that suit for you :good:
Click to expand...
Click to collapse
Thank you for your response and for the link you gave. I think this is the day that i have been waiting for 78hrs to unlock bootloader. I guess i go with the Havoc. Thank you very much and God bless??
Update: Thank you again, I downgraded my Rn7 form 10.3.6 to 10.2.7.0

gAracUh said:
Thank you for your response and for the link you gave. I think this is the day that i have been waiting for 78hrs to unlock bootloader. I guess i go with the Havoc. Thank you very much and God bless?
Update: Thank you again, I downgraded my Rn7 form 10.3.6 to 10.2.7.0
Click to expand...
Click to collapse
Glad to know it helped you, Good luck and bless for you too. :good:

Razer 2 Global MR2 Sept 2019 Release Magisk Root & Arter97 Kernel / TWRP ?

Can someone confirm these steps will work..
MR1 that has Arter97 Kernel with TWRP and is rooted with Magisks
----------------------------------------------------------------------------------
1. Flash back to factory P-MR1-RC003-RZR-190305.3110 using instructions on Razer Develope Portal
https://developer.razer.com/razer-phone-dev-tools/factory-images/
2. Lock the Bootloader Critical Partitions
command: fastboot flashing lock_critical
3. Locking the Bootloader
command: fastboot flashing lock
4. Reboot phone and let it setup
5. Enable OEM locking
6. Wait/Take OTA for MR2
Re-Root MR2
----------------
1. FLash MR2 rooted image via FASTBOOT
https://forum.xda-developers.com/showpost.php?p=80553681&postcount=57
2. Flash Arter97 Kernel & TWRP via FASTBOOT
3. Reboot
??????????????????????????????????
Is the above the best way? Can we just flash the factory MR1 bootloader and recovery and take the OTA, then install Arter97/TWRP and then install Magisks?
Please advise...
Thanks,
RJR

I'm in the same boat, waiting for confirmation before installing September update.
I need root, and if we can't root the new September release, then I rather stay in the current version.

1. install factory images
2. update
3. flash arter and root
if you notice any bootloop i recommend u use gsi because i had once bootloop for no reason on stock but gsi is just fine

RKBD said:
1. install factory images
2. update
3. flash arter and root
if you notice any bootloop i recommend u use gsi because i had once bootloop for no reason on stock but gsi is just fine
Click to expand...
Click to collapse
Sorry but I have seen in another thread that to get root on latest September update, we had to flash the modded boot provided. So if we root after arter, we will loose arter?
Sorry if it's a noob question but rooting last update isn't clear to me.

This Works I've done it on my razor phone 2 Global
This does work
rrusek said:
Can someone confirm these steps will work..
MR1 that has Arter97 Kernel with TWRP and is rooted with Magisks
----------------------------------------------------------------------------------
1. Flash back to factory P-MR1-RC003-RZR-190305.3110 using instructions on Razer Develope Portal
https://developer.razer.com/razer-phone-dev-tools/factory-images/
2. Lock the Bootloader Critical Partitions
command: fastboot flashing lock_critical
3. Locking the Bootloader
command: fastboot flashing lock
4. Reboot phone and let it setup
5. Enable OEM locking
6. Wait/Take OTA for MR2
Re-Root MR2
----------------
1. FLash MR2 rooted image via FASTBOOT
https://forum.xda-developers.com/showpost.php?p=80553681&postcount=57
2. Flash Arter97 Kernel & TWRP via FASTBOOT
3. Reboot
??????????????????????????????????
Is the above the best way? Can we just flash the factory MR1 bootloader and recovery and take the OTA, then install Arter97/TWRP and then install Magisks?
Please advise...
Thanks,
RJR
Click to expand...
Click to collapse

macjunkie said:
This does work
Click to expand...
Click to collapse
OK thanks I'll do that!
But the download link doesn't work anymore...

http://arter97.com/browse/aura/kernel/ latest 12r kernel won't bootloop so.
1. flash untouched RP2 mr1 firmware (latest for now in razer factory images)
2. update it to mr2
3. fastboot flash boot [arter r12 kernel]
4. then root or whatever you want

RKBD said:
http://arter97.com/browse/aura/kernel/ latest 12r kernel won't bootloop so.
1. flash untouched RP2 mr1 firmware (latest for now in razer factory images)
2. update it to mr2
3. fastboot flash boot [arter r12 kernel]
4. then root or whatever you want
Click to expand...
Click to collapse
Root before flashing GSI or after?

EMJI79 said:
Root before flashing GSI or after?
Click to expand...
Click to collapse
after.
it doesn't matter tho because it's on boot partition not system. but you won't need to reboot twice if you install it after flashing gsi.

RKBD said:
http://arter97.com/browse/aura/kernel/ latest 12r kernel won't bootloop so.
1. flash untouched RP2 mr1 firmware (latest for now in razer factory images)
2. update it to mr2
3. fastboot flash boot [arter r12 kernel]
4. then root or whatever you want
Click to expand...
Click to collapse
Well bad luck for me: it says device is corrupt after flashing mr1.
Maybe it has to do with I didn't unlock critical Bootloader. Will try.

EMJI79 said:
Well bad luck for me: it says device is corrupt after flashing mr1.
Click to expand...
Click to collapse
don't worry it's because you are on A/B device and you installed it on B partition instead of A
fastboot set_active a
then flash mr1 again

RKBD said:
don't worry it's because you are on A/B device and you installed it on B partition instead of A
fastboot set_active a
then flash mr1 again
Click to expand...
Click to collapse
Off topic: you said you wanted to have gestures, there's even better than Q gestures, with the app fluid navigation gestures you can set gestures to whatever you want. For example you could get close to Oxygen OS gestures which are great.

EMJI79 said:
Off topic: you said you wanted to have gestures, there's even better than Q gestures, with the app fluid navigation gestures you can set gestures to whatever you want. For example you could get close to Oxygen OS gestures which are great.
Click to expand...
Click to collapse
i know that app. but they're not that smooth and integrated with system

so no flawless alternative rom here?
Resurection get some issue with bluetooth audio(car audio HFP), and some trouble with fingerprint (works some times)
and havoc 2.9 GSI same issue
i don't know, leave original one?
now i've rolled back the MR1, but get persistent error upgrading MR1 (all restored to original one, boot and system )

igiolo said:
so no flawless alternative rom here?
Resurection get some issue with bluetooth audio(car audio HFP), and some trouble with fingerprint (works some times)
and havoc 2.9 GSI same issue
i don't know, leave original one?
now i've rolled back the MR1, but get persistent error upgrading MR1 (all restored to original one, boot and system )
Click to expand...
Click to collapse
Nope, no solid alternative. Unfortunately, development for the RP2 (and most Android phones these days) has been almost non-existent. Our options are either stay stock, or use one of the GSI's that all have issues of various kinds with our phone.

Hey everyone,
Apologies on the redundancy - but for someone who just scored this phone from Razer for 299 and took the MR2 update the minute it got on wifi, would these steps work to just get root/magisk going?
Enable OEM unlock
reboot to the bootloader
use fastboot command to unlock bootloader
flash mr2 rooted image via fastboot
flash arter97 and twrp via fastboot
reboot
profit?
I'm just looking to get root/magisk, no ROMS or anything.
Thanks all

shokxdauser said:
Hey everyone,
Apologies on the redundancy - but for someone who just scored this phone from Razer for 299 and took the MR2 update the minute it got on wifi, would these steps work to just get root/magisk going?
Enable OEM unlock
reboot to the bootloader
use fastboot command to unlock bootloader
flash mr2 rooted image via fastboot
flash arter97 and twrp via fastboot
reboot
profit?
I'm just looking to get root/magisk, no ROMS or anything.
Thanks all
Click to expand...
Click to collapse
1 enable oem unlock
2 reboot to bootloader via power down and click bootloader unlock
3 flash kernel via fastboot (twrp is inside kernel)
4 flash magisk

RKBD said:
1 enable oem unlock
2 reboot to bootloader via power down and click bootloader unlock
3 flash kernel via fastboot (twrp is inside kernel)
4 flash magisk
Click to expand...
Click to collapse
As always, much appreciated.

shokxdauser said:
As always, much appreciated.
Click to expand...
Click to collapse
Hmm. I thought maybe using the fastboot flash boot_a command would help but I am still getting this error when I try to flash the kernel when I try this full command:
fastboot flash boot_a arter97.img
gets me -
error: failed to identify current slot
I'm guessing I missed something obvious..?
---------- Post added at 11:49 PM ---------- Previous post was at 11:23 PM ----------
Just to note from my previous post about the error - failed to identify current slot -
I am able to see the device when I type fastboot devices. Still trying to figure out why it's saying failed to identify current slot..

shokxdauser said:
Hmm. I thought maybe using the fastboot flash boot_a command would help but I am still getting this error when I try to flash the kernel when I try this full command:
fastboot flash boot_a arter97.img
gets me -
error: failed to identify current slot
I'm guessing I missed something obvious..?
---------- Post added at 11:49 PM ---------- Previous post was at 11:23 PM ----------
Just to note from my previous post about the error - failed to identify current slot -
I am able to see the device when I type fastboot devices. Still trying to figure out why it's saying failed to identify current slot..
Click to expand...
Click to collapse
Let us know if you get it. I have this phone coming to me and want only TWRP/Magisk.
Thanks.

11.0.8.8 Rooting Issue

I am on the latest 11.0.8.8 EU version. I had patched the boot.img using magisk 23 app, but when i try to flash the patched boot.img using adb fastboot, keep getting "com.android.phone" crashes. Need to flash stock boot.img to get the sim cards working. Any suggestion to get root ?

Remove oos native call recorder module if you have it, if not just remove all modules.

MrEvilPanda said:
I am on the latest 11.0.8.8 EU version. I had patched the boot.img using magisk 23 app, but when i try to flash the patched boot.img using adb fastboot, keep getting "com.android.phone" crashes. Need to flash stock boot.img to get the sim cards working. Any suggestion to get root ?
Click to expand...
Click to collapse
Have you been on my guide mate?? It's all laid out for you..
Don't flash anything, you want to boot first as this is not permanent.
Stable 23 is the correct version..

dladz said:
Have you been on my guide mate?? It's all laid out for you..
Don't flash anything, you want to boot first as this is not permanent.
Stable 23 is the correct version..
Click to expand...
Click to collapse
I am on the stable 23 version. Disabling the native OOS call recording module solved the issue. @gsser Thanks mate.

MrEvilPanda said:
I am on the stable 23 version. Disabling the native OOS call recording module solved the issue. @gsser Thanks mate.
Click to expand...
Click to collapse
Ah yes, always disable Magisk modules prior to upgrading firmware.
As they may not be compatible, this is also in the guide.
Glad you're up and running mate
Nice one

So idk if this is the correct place to post questions but i have a OnePlus 8 pro 11.0.8.8IN11BA, i want to root it, but i can't find the stock rom for this version. Can anyone help me??

Arksuga said:
So idk if this is the correct place to post questions but i have a OnePlus 8 pro 11.0.8.8IN11BA, i want to root it, but i can't find the stock rom for this version. Can anyone help me??
Click to expand...
Click to collapse
Hi, see this thread:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com

galaxys said:
Hi, see this thread:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much!!!! So now in order to root it i should unlock the bootloader, and then patch the IMG i downloaded with the magisk manager app, connect the phone to the PC with USB debugging on, reboot in fastboot mode, and type on the windows command thing this ( the commands in the image attached ):

Arksuga said:
Thank you so much!!!! So now in order to root it i should unlock the bootloader, and then patch the IMG i downloaded with the magisk manager app, connect the phone to the PC with USB debugging on, reboot in fastboot mode, and type on the windows command thing this ( the commands in the image attached ):
Click to expand...
Click to collapse
Yep I've got guides for unlocking the bootloader and rooting in the guides sections.
Both called as such accordingly.
Tbh there are a few guides all should be fine.
Just read through the root guide.
Unlocking the bootloader it's easy.
Code: fastboot OEM unlock
Agree on phone.
Rooting:
Obtain patched image
Fastboot boot Magisk patched
Don't flash it, just wait for boot then open Magisk and click install / direct install.
Again this is all in the guides.