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

Downgrading from Pie(pixel exp) to Stock.

Hello Everyone!
I am a total noob. I have rooted many phone but never once reversed the process. Plus with stock moto being 32bit and customs being 64 it is even more complicated for me. And plus all this post about lost IMIE numbers and lost GPT makes me scared.
If i may, can I get step by step guide to relock my bootloader and get OTAs.
I have read most of the tutorials here but couldnt get the confidence to move forward(they all sound a little different)
I have moto G5 plus XT1686 indian version 4Gb/32GB currently running PE 9.0 (GTRCraft). I dont remember which version I had when I unlocked the bootloader. I do have a backup of my persist/efs.
I did see one tutorial but it is for 8.1.0 to stock and IDK if that works for me.
Thanks in advance.

reganEZ said:
Hello Everyone!
I am a total noob. I have rooted many phone but never once reversed the process. Plus with stock moto being 32bit and customs being 64 it is even more complicated for me. And plus all this post about lost IMIE numbers and lost GPT makes me scared.
If i may, can I get step by step guide to relock my bootloader and get OTAs.
I have read most of the tutorials here but couldnt get the confidence to move forward(they all sound a little different)
I have moto G5 plus XT1686 indian version 4Gb/32GB currently running PE 9.0 (GTRCraft). I dont remember which version I had when I unlocked the bootloader. I do have a backup of my persist/efs.
I did see one tutorial but it is for 8.1.0 to stock and IDK if that works for me.
Thanks in advance.
Click to expand...
Click to collapse
Just wipe everything from twrp and then use LMSA OR manually flash the stock ROM and then go for bootloader lock procedure. Then you are done. And you won't lose any IMEI or Persist, so you will be safe.

riyan65 said:
Just wipe everything from twrp and then use LMSA OR manually flash the stock ROM and then go for bootloader lock procedure. Then you are done. And you won't lose any IMEI or Persist, so you will be safe.
Click to expand...
Click to collapse
So just download a TWRP flashable 8.1.0 rom and i m good?

reganEZ said:
So just download a TWRP flashable 8.1.0 rom and i m good?
Click to expand...
Click to collapse
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0

Wolfcity said:
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
Click to expand...
Click to collapse
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?

reganEZ said:
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?
Click to expand...
Click to collapse
+ i tried the method and it says "slot not found" error

reganEZ said:
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?
Click to expand...
Click to collapse
You have to use the firmware you were on before you changed to a custom ROM or a newer one.
Never use an older one, downgrading can brick your device.
reganEZ said:
+ i tried the method and it says "slot not found" error
Click to expand...
Click to collapse
The "slot not found" error is normal, it's related to A/B devices with more than one recovery slot like Pixel phones. The commands should work nevertheless. Ignore the message.

I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damned thing.
Everything works fine, excpet for Netflix that can't be installed no more and my bank software who keeps complaining.
I just dunno what to do to relock, any advice ?

Wolfcity said:
You have to use the firmware you were on before you changed to a custom ROM or a newer one.
Never use an older one, downgrading can brick your device.
The "slot not found" error is normal, it's related to A/B devices with more than one recovery slot like Pixel phones. The commands should work nevertheless. Ignore the message.
Click to expand...
Click to collapse
Hello, Thank you for your reply.
I understand I cannot use an older firmware. I remember I unlocked my BL when I was in 7.0 itself, but when I installed the Arrow 9.0, I flashed the 8.1 firmware zip to get the NFC and Fingerprint working. So now my ro.build fingerprint doesnt tell me which firmware build i am on it just says "8.1"
I am confused what to do. Should I download the latest 8.1 moto rom and flash it? I tried the TWRP flashable rom but the phone just goes upto Hello Moto bootscreen and then bootloops.
I erased everything and flashed PE 9.0 again.

reganEZ said:
Hello, Thank you for your reply.
.....Should I download the latest 8.1 moto rom and flash it?.......
Click to expand...
Click to collapse
That's what I would do. If you flash the latest firmware it can't be older as the one you're originally coming from.
Follow my previous post:
Wolfcity said:
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.batflashallO.bat?dl=0
Click to expand...
Click to collapse

Wolfcity said:
That's what I would do. If you flash the latest firmware it can't be older as the one you're originally coming from.
Follow my previous post:
Click to expand...
Click to collapse
Hello Sir, i was on OPSS28.85-13-5 when i flashed custom rom. The link you provided lists OPSS28.85-13-3 as the latest firmware. Should i install that? I am from India if that helps. Help please.

MrAshuBrar said:
Hello Sir, i was on OPSS28.85-13-5 when i flashed custom rom. The link you provided lists OPSS28.85-13-3 as the latest firmware. Should i install that? I am from India if that helps. Help please.
Click to expand...
Click to collapse
Take this one:
85-13-5
https://forum.xda-developers.com/g5-plus/how-to/official-oreo-coming-soon-t3779098/post78844908

CanadianGixxerman said:
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damned thing.
Everything works fine, excpet for Netflix that can't be installed no more and my bank software who keeps complaining.
I just dunno what to do to relock, any advice ?
Click to expand...
Click to collapse
Flash all the system files while locking. (0-8). Older locking guides have only 0-4. Newer firmware has 9 system files.

Wolfcity said:
Take this one:
85-13-5
https://forum.xda-developers.com/g5-plus/how-to/official-oreo-coming-soon-t3779098/post78844908
Click to expand...
Click to collapse
Thank you so much ?

[GUIDE] [OREO 8.0] ROOT + TWRP + DRM Fix | AU KDDI SOV34 | 41.3.C.1.147

NOTE :
I created this guide for the Sony Japan AU KDDI version of Xperia XZ Oreo 8.0 users and i have difficulty installing the global version and many that do not support such as NFC Japan are very different from global. Please report this text before you root SOV34 check your sim lock if (x) Network Subset [5] = this is a Carrier Restriction that only allows certain SIM cards. In Japan, CDMA are dominant networks. I think since this is a GSM network, they set a Network Subset lock to restrict exporting. If you already unlock your bootloader, then sim not detected again. So please check this sim lock from dial *#*#7378423#*#*. Forget about root if your Network Subset is locked.
Since there is no ftf file for XZ AU KDDI's, here is the guide from me for rooting it.
You need backup your TA.img. Downgrade your android to Marshmallow for FTF file you can find from this link [url]https://ftf.andro.plus/[/URL] you may use the version 39.0.C.0.282 and for guide step how to backup TA you can use this link [url]https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236[/URL].
Update your SOV34 to Oreo 8.0 via Xperia Companion (since no ftf for Oreo) and unlocked your bootloader. For Unlock booloader you can use Flashtool or from ADB. Make sure that the OEM Unlocking in Developer Option is ON
Make your phone plugin to pc to Fastboot Mode ( Power Up + Volume Up ) and go to ADB and flash Recovery.
Code:
fastboot flash recovery twrp.img
you can download TWRP from my drive [url]https://drive.google.com/open?id=1IlisSeKaMhvCQkUddgyLOdDSg_988zvZ[/URL] and factory reset via TWRP[to eliminate the password entry during bootup]
Flash the created from me for boot.img using fastboot and restart to TWRP
Code:
fastboot flash boot boot.img
Flash instal Zip Magisk, DRM Fix and Safetynet Patch. ( Put this Zip in SD Card) you can find this zip in my drive [url]https://drive.google.com/open?id=1IlisSeKaMhvCQkUddgyLOdDSg_988zvZ[/URL]
All done.
Credit :​ @donedos ( For inspiration to me make this guide )​
You can see my attached Screenshot for already to be root My SOV34. If you need Q & A you can send me email [email protected] or you can PM.

seyrarms said:
Finally I could make this guide for Sony SOV34 a few months to learn the difference between this system and the global system. Actually, in a case that might have never happened for Sony Japan is to open the Unlock Bootloader because by default it always says: "Unlock Bootloader Allowed: NO". One day I read in a Forum and finally, I found a bright spot about this bootloader. And finally my phone bootloader is allowed yes. If you need ask about how to change this bootloader from Japan Smartphone just PM me.
NOTE :
I created this guide for the AU KDDI version of Xperia XZ Oreo 8.0 users and i have difficulty installing the global version and many that do not support such as NFC Japan are very different from global.
Since there is no ftf file for XZ AU KDDI's, here is the short guide for rooting it.
You need backup your TA.img. Downgrade your android to Marshmallow for FTF file you can find from this link https://ftf.andro.plus/ you may use the version 39.0.C.0.282 and for guide step how to backup TA you can use this link https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236.
Update your SOV34 to Oreo 8.0 via Xperia Companion (since no ftf for Oreo) and unlocked your bootloader. For Unlock booloader you can use Flashtool or from ADB. Make sure that the OEM Unlocking in Developer Option is ON
Make your phone plugin to pc to Fastboot Mode ( Power Up + Volume Up ) and go to ADB and flash Recovery.
Code:
fastboot flash recovery twrp.img
you can download TWRP from my drive https://drive.google.com/open?id=1IlisSeKaMhvCQkUddgyLOdDSg_988zvZ and factory reset via TWRP[to eliminate the password entry during bootup]
Flash the created from me for boot.img using fastboot and restart to TWRP
Code:
fastboot flash boot boot.img
Flash instal Zip Magisk, DRM Fix and Safetynet Patch. ( Put this Zip in SD Card) you can find this zip in my drive https://drive.google.com/open?id=1IlisSeKaMhvCQkUddgyLOdDSg_988zvZ
All done.
Credit :​ @donedos ( For inspiration to me make this guide )​
You can see my attached Screenshot for already to be root My SOV34. If you need Q & A you can send me email [email protected] or you can PM.
Click to expand...
Click to collapse
This it's very help me thanks and working. Are you have project again for about this device?

Mervell said:
This it's very help me thanks and working. Are you have project again for about this device?
Click to expand...
Click to collapse
IDK. I will try about this, since no custom rom full support for this device SOV34

seyrarms said:
IDK. I will try about this, since no custom rom full support for this device SOV34
Click to expand...
Click to collapse
I look forward to it, you have reccom for tweak gaming for like PUBG ?

Mervell said:
I look forward to it, you have reccom for tweak gaming for like PUBG ?
Click to expand...
Click to collapse
For me just delete file config thermal in folder system/vendor/etc
Find this file and delete and instal kernel auditor for tweak

I got this problem while im trying to flash au mm rom
Any help?

Muurica said:
I got this problem while im trying to flash au mm rom
Any help?
Click to expand...
Click to collapse
Your device? single or dual?
or use other version of flashtool.

J.M.Siyath said:
Your device? single or dual?
or use other version of flashtool.
Click to expand...
Click to collapse
Single,
And what version can i use for it ?

Muurica said:
Single,
And what version can i use for it ?
Click to expand...
Click to collapse
I use flashtool 0.9.26 but now already released latest version 0.9.27.

Muurica said:
I got this problem while im trying to flash au mm rom
Any help?
Click to expand...
Click to collapse
You need update that's flashtool

How can I install adb driver for sony xperia xz sov34? I try install sony companion but It is not work.

seyrarms said:
NOTE :
I created this guide for the Sony Japan AU KDDI version of Xperia XZ Oreo 8.0 users and i have difficulty installing the global version and many that do not support such as NFC Japan are very different from global.
Since there is no ftf file for XZ AU KDDI's, here is the guide from me for rooting it.
You need backup your TA.img. Downgrade your android to Marshmallow for FTF file you can find from this link https://ftf.andro.plus/ you may use the version 39.0.C.0.282 and for guide step how to backup TA you can use this link https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236.
Update your SOV34 to Oreo 8.0 via Xperia Companion (since no ftf for Oreo) and unlocked your bootloader. For Unlock booloader you can use Flashtool or from ADB. Make sure that the OEM Unlocking in Developer Option is ON
Make your phone plugin to pc to Fastboot Mode ( Power Up + Volume Up ) and go to ADB and flash Recovery.
Code:
fastboot flash recovery twrp.img
you can download TWRP from my drive https://drive.google.com/open?id=1IlisSeKaMhvCQkUddgyLOdDSg_988zvZ and factory reset via TWRP[to eliminate the password entry during bootup]
Flash the created from me for boot.img using fastboot and restart to TWRP
Code:
fastboot flash boot boot.img
Flash instal Zip Magisk, DRM Fix and Safetynet Patch. ( Put this Zip in SD Card) you can find this zip in my drive https://drive.google.com/open?id=1IlisSeKaMhvCQkUddgyLOdDSg_988zvZ
All done.
Credit :​ @donedos ( For inspiration to me make this guide )​
You can see my attached Screenshot for already to be root My SOV34. If you need Q & A you can send me email [email protected] or you can PM.
Click to expand...
Click to collapse
how are you able to unlock the bootloader on SOV34 if it says "bootloader unlocked allowed:no" , really need your help here, the thermal throttling is driving me mad

hi! can you please make the same tutorial for softbank 601so?

Hendii said:
hi! can you please make the same tutorial for softbank 601so?
Click to expand...
Click to collapse
I'm use too 601SO but for me. I'm use global rom, since Softbank not release Oreo update OTA so i'm use from global

seyrarms said:
I'm use too 601SO but for me. I'm use global rom, since Softbank not release Oreo update OTA so i'm use from global
Click to expand...
Click to collapse
you haven't answered my question for days, how did you able to unlock the bootloader if it said "unlock bootloader allowed:no" ?

seyrarms said:
I'm use too 601SO but for me. I'm use global rom, since Softbank not release Oreo update OTA so i'm use from global
Click to expand...
Click to collapse
seriously dude? is this guide legit or not? can't give a simple answer?

Enrico Vialli said:
you haven't answered my question for days, how did you able to unlock the bootloader if it said "unlock bootloader allowed:no" ?
Click to expand...
Click to collapse
You need use S1 Tools Network for unlock thats

Hendii said:
hi! can you please make the same tutorial for softbank 601so?
Click to expand...
Click to collapse
I'm use too 601so but you need flash to global cause from softbank haven't updated oreo.

seyrarms said:
You need use S1 Tools Network for unlock thats
Click to expand...
Click to collapse
it took you over a month to answer my question, and your answer is that tool, which i need to pay £35(which is big amount in my country) just to use it to unlock bootloader... totally not worth it
time wasted, very dissapointed

Enrico Vialli said:
it took you over a month to answer my question, and your answer is that tool, which i need to pay £35(which is big amount in my country) just to use it to unlock bootloader... totally not worth it
time wasted, very dissapointed
Click to expand...
Click to collapse
Sorry for late answer i'm very busy, yeah if you need unlock for use that. If not worth it don't root you device or change your device.

[GUIDE] For those having trouble ROOTING their OnePlus 8T (All Variants)

I have only *SUCCESSFULLY* tried this on my KB2003 Variant. It will work for all other variants as well, it's just that I haven't tested it (I don't have all variants on hand!)
If you're having some issues rooting your 8T, I'm here to guide you on how to root correctly. I have tried many ways but none have worked. This is the only way I know that actually works. I want to get some thanks out of the way first.
topjohnwu for his amazing Magisk creation!
DroidFreak32 for the boot images required for this method
For this method, we're gonna skip all of the Payload Dumper part of DroidFreaks' Guide (unless your variant of the 8T doesn't have a public boot image). All you need is your phone on hand and your STOCK boot image, which for the purposes of this guide, you can grab from DroidFreaks' guide, or from below (all thanks to him)
KB2001 - Indian Variant - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
https://drive.google.com/file/d/1Ct7IJWWXJlIZX9ekIrTKLC9G6KZLD2eq/view
KB2003 - EU Variant - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
https://www.androidfilehost.com/?fid=10763459528675568456
KB2005 - US Variant
https://androidfilehost.com/?fid=10763459528675569233
You have to have your bootloader unlocked at this point, but this isn't a guide for that, just Google it.
Next, you'll wanna download the latest magisk canary apk. https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk . After this, make sure you have your specific boot image on your phone. Open Magisk Manager, and go to install, beside "magisk". Next, choose "select and patch a file" and choose your specific boot image to patch. For me, it was the KB2003 one. Once it spits out the file, go ahead and move it back over to your PC.
Reboot into the bootloader and use fastboot to BOOT the patched image that you just moved over to your PC.
Code:
fastboot boot magisk_patched.img[/INDENT]
Once you're booted, head over to the Magisk app again. You want to go back to the install page "mentioned earlier" and instead of clicking the patch button, you want to click the new DIRECT INSTALL button, this will "save" magisk and fully install it. After it's done, go ahead and reboot, and you should be rooted!​
Let me know how it goes for you guys down below!​

I am on KB2000 running Oxygen OS 11.0.1.2.KB05DA. Any advise on how to get the stock boot image?

deepuvijay said:
I am on KB2000 running Oxygen OS 11.0.1.2.KB05DA. Any advise on how to get the stock boot image?
Click to expand...
Click to collapse
KB05DA is the Indian variant OxygenOS, so your stock boot image should be the one below:
KB2001 - Indian Variant - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
https://drive.google.com/file/d/1Ct7IJWWXJlIZX9ekIrTKLC9G6KZLD2eq/view

Thanks @zellleonhart, @fxz
Worked just fine. I am now rooted on KB2000 running Oxygen OS 11.0.1.2.KB05DA.

Worked for me. Thank you very much!
First attempt failed cause I failed to set magisk to canary resulting in a patched .img of only 46mb.
Check safetynet was successfull but Netflix doesn't work and does not appear in magiskhide (preinstalled systemapp?).

bernie012 said:
Netflix doesn't work and does not appear in magiskhide (preinstalled systemapp?).
Click to expand...
Click to collapse
Just tick - Show system apps - in magisk hide search. it ll show Netflix as well.
Sent from my KB2000 using Tapatalk

deepuvijay said:
Just tick - Show system apps - in magisk hide search. it ll show Netflix as well.
Click to expand...
Click to collapse
You're amazing! Thank you. I somehow missed that option.
Cleared Netflix and playstore cashe but still wasn't able to start it but after rebooting the device I was able to update Netflix and succesfully watch movies.

zellleonhart said:
KB05DA is the Indian variant OxygenOS, so your stock boot image should be the one below:
KB2001 - Indian Variant - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
https://drive.google.com/file/d/1Ct7IJWWXJlIZX9ekIrTKLC9G6KZLD2eq/view
Click to expand...
Click to collapse
I have the exact same question as the person you replied to, as I bought mine in Hong Kong and is the KB2000 China version.
Phone comes preloaded with Oxygen OS KB05DA version, which you said is the Indian variant. I can assume then there is no relation between the regional variant of OxygenOS and the regional variant of the phone itself?

emzee.mc said:
I have the exact same question as the person you replied to, as I bought mine in Hong Kong and is the KB2000 China version.
Phone comes preloaded with Oxygen OS KB05DA version, which you said is the Indian variant. I can assume then there is no relation between the regional variant of OxygenOS and the regional variant of the phone itself?
Click to expand...
Click to collapse
Same here too. Ordered it online and came from HK. KB2000 with Hydrogen OS also exist. So i guess it's safe to assume that there may be various OS build on the same Physical variant depending on the region.

emzee.mc said:
I have the exact same question as the person you replied to, as I bought mine in Hong Kong and is the KB2000 China version.
Phone comes preloaded with Oxygen OS KB05DA version, which you said is the Indian variant. I can assume then there is no relation between the regional variant of OxygenOS and the regional variant of the phone itself?
Click to expand...
Click to collapse
I am not sure why yours come with KB05DA, but based on OnePlus' own post in their forum, the OxygenOS versions for the 11.0.1.2 update are as follows:
IN: 11.0.1.2.KB05DA
EU: 11.0.1.2.KB05BA
NA: 11.0.1.2.KB05AA​
SourceL https://forums.oneplus.com/threads/oxygenos-11-0-1-2-for-the-oneplus-8t.1324900/

deepuvijay said:
Thanks @zellleonhart, @fxz
Worked just fine. I am now rooted on KB2000 running Oxygen OS 11.0.1.2.KB05DA.
Click to expand...
Click to collapse
Hmm, I took the KB2001 - Indian Variant - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110 boot image and patched it on magisk. Went into fastboot and booted the patched file fine.
That said, when I go back to Magisk, I don't see the option to do direct install. Wonder what the issue is there. Did you encounter this?

emzee.mc said:
Hmm, I took the KB2001 - Indian Variant - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110 boot image and patched it on magisk. Went into fastboot and booted the patched file fine.
That said, when I go back to Magisk, I don't see the option to do direct install. Wonder what the issue is there. Did you encounter this?
Click to expand...
Click to collapse
Strange. It went just fine for me. Did you use the boot image linked in Reply #3?

boot looped on tmobile variant

rtown195 said:
boot looped on tmobile variant
Click to expand...
Click to collapse
How in the **** did you get your boot unlock token from 1+?

Btw i had a doubt once im rooted and there is a new update for oos the root will be lost right or can i just use the install to inactive slot option i had this doubt cuz the boot img i used was specific to my current build

zeusofyork said:
How in the **** did you get your boot unlock token from 1+?
Click to expand...
Click to collapse
i didnt a wizard unlocked my bl

Thanks. Worked fine run the 1st time with KB2003 on Oxygen OS 11.0.1.2KB05BA after some fails yesterday. :good:

rtown195 said:
i didnt a wizard unlocked my bl
Click to expand...
Click to collapse
..... You uhhhhh, know where I can meet him?

zeusofyork said:
..... You uhhhhh, know where I can meet him?
Click to expand...
Click to collapse
PM me

Hi Guys, i tried to root my 8T today. Unlocking the bootloader worked finde. After that i updated tu 11.0.2.3.KB05BA. I extracted the boot.img and did the "installing procedure" at magisk. But even if i flash the magisk image i get no root access. I think the problem is, the stock boot.img is around 96 MB und my magsik boot.img is only 42,87 MB. I tried several version of magisk. Why is my magisk image that small?
EDIT: Okay i did every step a second time and got a function working image with the correct size.

OnePlus 8T Firmware Updates For Custom ROMS

Hello OnePlus 8T Users,
We created a unified firmware update package for custom roms so that you don't have to flash oxygen os again to update the firmware.
[Firmware Update][Global-India-Europe]
Update firmware on kebab
OnePlus 8T OxygenOS 11.0.8.13/11.0.8.14
How to flash?
1. You can use TWRP to flash this Firmware Update or
2. You can also sideload the firmware.zip package via PE Recovery or LOS Recovery.
3. On PE/LOS Recovery, select “Apply Update”, then “Apply from ADB” to begin sideload.
4. On the host machine, sideload the package using:
adb sideload <filename.zip>.zip
Credits:
- @yshalsager
- @EmperorEye1993
- @_abhi.jit__

Might be better to put this in the 8T forum. Tested and worked on global with TWRP. Does this account for the DDR0 vs DDR1 difference?

fates13 said:
Might be better to put this in the 8T forum. Tested and worked on global with TWRP. Does this account for the DDR0 vs DDR1 difference?
Click to expand...
Click to collapse
I'll post 8/8Pro firmware package too so I created this thread here.

_abhi.jit__ said:
I'll post 8/8Pro firmware package too so I created this thread here.
Click to expand...
Click to collapse
Gotcha. What about DDR type 0 vs DDR type 1? Requires different xbl and xbl_config files per https://wiki.lineageos.org/devices/kebab/fw_update

fates13 said:
Gotcha. What about DDR type 0 vs DDR type 1? Requires different xbl and xbl_config files per https://wiki.lineageos.org/devices/kebab/fw_update
Click to expand...
Click to collapse
This is ddr0

After installing this. my phone seems dead.
Do not start anymore, nothing happens even by long press power button for force restart.
Also can't enter EDL mode for use msmtool....
Any help?

vivmar said:
After installing this. my phone seems dead.
Do not start anymore, nothing happens even by long press power button for force restart.
Also can't enter EDL mode for use msmtool....
Any help?
Click to expand...
Click to collapse
What's your device ? On which rom you flashed this firmware update ? Which was the previous version of your oos before coming to custom rom? Read carefully this update is only for custom rom for OnePlus 8T (Global/India/Eu)

_abhi.jit__ said:
What's your device ? On which rom you flashed this firmware update ? Which was the previous version of your oos before coming to custom rom? Read carefully this update is only for custom rom for OnePlus 8T (Global/India/Eu)
Click to expand...
Click to collapse
Device is 8T EU - i was on pixelexperience rom. My last OOS was the 11.0.7
I have managed after some hour to restore from brick with msmtool.

vivmar said:
Device is 8T EU - i was on pixelexperience rom. My last OOS was the 11.0.7
I have managed after some hour to restore from brick with msmtool.
Click to expand...
Click to collapse
Probably DDR type 1. This is exactly why I asked about it. Anyone on DDR type 1 is gonna end up bricking their phone and needing msmtool unless you flash the correct files for type 1.

just flashed this while on crdroid works fine 8t china variant do i need to do this if i flash a different custom rom ie havoc?

How do I find out if I have "DDR0 or DDR1"?
Important reminder (Before Flashing):
Firmware builds are using DDR 0 by default, since the OnePlus 8T device is LPDDR4X.
Check your DDR type using ADB with the following command:
adb shell getprop ro.boot.ddr_type
Click to expand...
Click to collapse
I came from OOS 11.0.8.14 and am now on HavocOS 4.6....
I think that keeps me up to date.
Click to expand...
Click to collapse
Do I even need this firmware update?
What exactly are the benefits of this firmware?
I was again too quick with the asking. It updated all the drivers, Bluetooth, WiFi, GPS, etc.
Click to expand...
Click to collapse

To be sure, can i flash to aicp rom with twrp on both slots or simply press install? then do i have to reflash aicp? or just restart.
sorry noob question but I still don't fully understand a / b slot