State of root for the XZ3 (EU version) - Sony Xperia XZ3 Questions & Answers

Can anyone tell me if rooting is possible for the XZ3? I only need basic root, I'm fine without any custom ROMs and even TWRP, just want root preferably through SuperSU but magisk can work as well.
Thanks!

no, because Sony won't fix greyed out "oem unlocking" prior to December security patch and Sony has not yet delivered the December patch
supposedly it was a bug, but i doubt it. bet it was intentional
extremely upset at Sony not fixing immediately (it has known about "bug" for a while) instead of forcing us to wait

you think it'll be possible after this feature is enabled? I'm not worried so long as rooting is possible whenever..

yes

looks like today may be possible!

New update fixed this. Oem unlock is not greyed out now. So yes rooting is possible.

But you will loose your camera.
On the XZ2/compact/premium the december patch broke the camera for unlocked devices. It shoot green pictures.
Downgrading to the november patch fixed it.
But we only have a working camera on the XZ2 devices, because we used a drmfix on oreo.
I don't know if the same will be on the XZ3 but if you really need the camera, i would wait for one to test the unlocking first.
At the moment, there is no PIE DRMfix.

Any confirmed working method to root XZ3?

First backup your apps/settings using the Google functionality or Sony's backup and restore functionality.
Then update your phone to the latest OTA available (for me this was 52.0.A.84, after three update cycles as I had held off on updating since I got the phone)
This will enable you to tick the "Enable boot loader unlocking" box in the developer options (tap the build number in Settings->System->About 5 times).
Go to your dialer and dial *#*#SERVICE#*#* for the service menu. In service info -> configuration, make sure "Rooting status" shows that unlocking is allowed. While you are in the service menu anyway, note down the IMEI number.
Now go to unlockbootloader.sonymobile.com, go through all the disclaimers, and enter your email address and IMEI number. You will get an email with an unlock code.
Install the Sony fastboot drivers (can be found on Sony's site) and a version of the adb/fastboot binaries (can be found here on XDA somewhere). While you're fetching drivers it might also be handy to get drivers for flash mode as well (also on Sony's site).
Turn off your phone, hold volume up and plug it into your PC. LED will turn blue and phone is now in fastboot mode. You can let go of any buttons.
Type fastboot oem unlock <the code you got from Sony>
Now unplug the phone and boot it normally. It will take a bit longer because this process master resets the entire phone. You will get a stupid warning about not being able to check your phone for corruption because you've unlocked your boot loader (oh noes).
Now get Xperifirm and download the 52.0.A.126 firmware and tell it to extract the firmware somewhere. Download Newflasher and extract it into the same directory as the extracted firmware.
Turn off your phone, hold volume down (flash mode) and plug it into your PC. Run Newflasher, and it will flash the 52.0.A.126 firmware onto your phone.
Unplug your phone, boot it up normally. The phone will have reset again (Newflasher wipes everything) but this will be the last time, so now you can proceed with setting up and personalising your phone (and putting back the backup you made at the beginning).
Head over to the TWRP thread in the XZ3 development forum and follow the installation procedures exactly. This will involve some usage of fastboot which you should by now be familiar with. Once you have TWRP installed, the touch screen won't work. So get a USB-C to USB-A adapter or a USB-C hub, and connect a PC mouse to operate TWRP. Part of the instructions in the thread are to install Magisk, which will give you root.
Congrats! You now have root and a broken camera and broken DRM.
To fix the camera, install the camera fix linked from the TWRP thread (it's a zip you flash with TWRP). This will replace some system files with files from the 52.0.A.84 firmware which will magically make the camera work again.
To fix the DRM, go to Magisk Manager on your phone and install "liboemcrypto disabler". This will fix Netflix and other apps that use DRM.
That's the state of root on the XZ3!

Nice. You mean that the Magisk trick would fix all the DRM issues, hence no other DRMfix or Xperifix needed?

I can't say anything about "all the DRM issues", but the camera works and denoising seems unaffected by the BL unlock with the fix applied, and Netflix seems to work. If there's anything specific you want me to test just let me know.
View attachment 4702986

Hi.
I got Root on my XZ3. Just install/flash custom made TWRP and flash Magisk Manager and You are good to go. ? ?
Sent from my Sony H9436 using XDA Labs
---------- Post added at 04:37 PM ---------- Previous post was at 04:27 PM ----------
I got root on my XZ3. Download custom made TWRP, flash, reboot in to TWRP and install Magisk Manager. ?
Sent from my Sony H9436 using XDA Labs

mufunyo said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser:
Click to expand...
Click to collapse
Please feel free to report bugs you found.

where can i find this custom twrp? @MurroFX

THANK YOU very much Sir!!

Root is possible. ?
Sent from my Sony H9436 using XDA Labs

had the same problem with H9493 on HK firmware...oem greyed out not fixed after decemeber patch.
Reflashed the latest Taiwan rom 11B using this method; http://www.xperiablog.net/2018/01/28/newflasher-guide-to-install-new-firmware-for-xperia-xz-premium-xz1-and-more/
booted without entering credentials (only network), was able to enable OEM unlock in develeoper options.
Still waiting for drm fix till i unlock, but at least now im able to.

Sorry for late answer But I think IT was on AndroidFileHost. Search on (MartinX3). ?

@MurroFX
Could you please provide us with step by step guide? Also, do you need to unlock bootloader to root the XZ3?
Thanks

mufunyo said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser:
Click to expand...
Click to collapse
Don't understand ? ? ? I am sorry ?
Sent from my Sony G8341 using XDA Labs

Related

Rooting marshmallow b550

First of all i have to say im really glad i got this phone over samsung galaxy J5.
Secondly...for the people who does not know how to root Marshmallow latest version im gonna use some resources i found over the internet.
Step by step if you dont have marshmallow install all the firmwares till you you get B170. Remember you have to be on stock recovery all the time
Then download the B550 from [Official huawei P8 lite marshmallow firmware]
and update your firmware.
Now its time for root...
1. Download this archive <MOD EDIT - Warez Link Removed> and unrar
2. Connect your phone to PC(make sure USB Debugging is checked in developer options) run Install.bat file and follow the instructions. This will install TWRP Recovery for 6.0
3. Copy files zip 1 and zip 2 to internal memory or SD Card
4. Reboot into TWRP (volume+ and volume- and power on button at the same time until TWRP appears.
5. Install zip 1 and reboot.
6. Open once SuperSU then close SuperSU and uninstall it!!(push supersu icon and move to recycle bin)
7. Boot again into TWRP and install zip 2 and then reboot
8. Install root browser from google play ( https://play.google.com/store/apps/details? id=com.jrummy.root.browserfree&hl=en )open and grant superuser rights.
9. Now open /device/data/app and locate folder eu.chainfire.supersu-1 cut and paste in folder /device/system/app with following rights rwx r-x r-x
Reboot your phone and ENJOY full root access
All credits to 4PDA forum members, XDA members for their annoying questions , dkonect, sokkoban PANDEMiC and his blogspot http://huaweip8lite.blogspot.gr/ (and ofc my patience of wasting all night long on updates,formats,wipes, degrades and workarounds with solutions )
PS: If someone feels i didnt gave regards i would be glad to add his name and make him famous
Hi vampirian,
TWRP couldn't be installed.
I got TWRP installation failure error. ( please see attached screenshot )
p8lite boot loader is unlocked with firmware is ALE-L21C185B524
( I use Window 10 with UniversalAdbDriverSetup6.msi installed )
Any suggestion please,
.
aab44 said:
Hi vampirian,
TWRP couldn't be installed.
I got TWRP installation failure error. ( please see attached screenshot )
p8lite boot loader is unlocked with firmware is ALE-L21C185B524
( I use Window 10 with UniversalAdbDriverSetup6.msi installed )
Any suggestion please,
.
Click to expand...
Click to collapse
I would suggest you to update on B550 before you start the procedure. It will still show B524 build but its updated anyway on the last version B550.
Please make sure you have Chipset HiSilicon Kirin 620
and use the ROOT.Android.6.0.P8.Lite to install the TWRP.
For me it seems like a driver problem or not unlocked bootloader.
Try by unlocking your bootloader again
Unlock boot loader on your device.
Type in command without quotes "fastboot devices"
If you can see serial number of your phone you are going the right way.
In the command prompt, enter fastboot oem unlock (bootloader unlocking code) , e.g. fastboot oem unlock 321321321321321”
if that didnt work then make sure your drivers are installed correctly
Re-Start windows with Driver signature off and re-apply your drivers. To do this on windows you have to go All settings--> update and recovery---->Recovery----->Advanced startup---->>restart now and after booting your windows in the blue screen, choose Driver signature OFF option. Then reinstall your drivers and restart your phone on fastboot mode (power on and volume - at the same time ) and run the script again.
I tried this a few mins ago on my brand new BL unlocked P8 Lite, i already installed TWRP and 6.0 Beta for Single Sim model, and
now it's also rooted
thx
fire3d said:
I tried this a few mins ago on my brand new BL unlocked P8 Lite, i already installed TWRP and 6.0 Beta for Single Sim model, and
now it's also rooted
thx
Click to expand...
Click to collapse
great news
im glad it works for you as well
The two variant , i mean ALE-L21 single or double sim have exactly the sames hardware.
The difference between the Two variant for single/double sim is only in the firmware you push in your devices.
(I have Two branded single variant and i use the firmware for single and double without any trouble.i only think the single sim firmware is more battery friendly but just a personal opinion)
Sent from my SM-G900M using XDA-Developers mobile app
dkonect said:
The two variant , i mean ALE-L21 single or double sim have exactly the sames hardware.
The difference between the Two variant for single/double sim is only in the firmware you push in your devices.
(I have Two branded single variant and i use the firmware for single and double without any trouble.i only think the single sim firmware is more battery friendly but just a personal opinion)
Sent from my SM-G900M using XDA-Developers mobile app
Click to expand...
Click to collapse
So far im satisfied for its battery. Ok everyone knows that Facebook and messenger are battery killers...but even with those running, MP3 all day long... my battery lasts for a day on dual sim with the smart battery mode. In any case i will try to update the official B550 spanish version to check the differences (and modify a bit our kernel) .
Marshmallow installed and rooted...
Sent from my ALE-L21 using XDA-Developers mobile app
vampirian said:
I would suggest you to update on B550 before you start the procedure. It will still show B524 build but its updated anyway on the last version B550.
Please make sure you have Chipset HiSilicon Kirin 620
and use the ROOT.Android.6.0.P8.Lite to install the TWRP.
For me it seems like a driver problem or not unlocked bootloader.
Try by unlocking your bootloader again
Unlock boot loader on your device.
Type in command without quotes "fastboot devices"
If you can see serial number of your phone you are going the right way.
In the command prompt, enter fastboot oem unlock (bootloader unlocking code) , e.g. fastboot oem unlock 321321321321321”
if that didnt work then make sure your drivers are installed correctly
Re-Start windows with Driver signature off and re-apply your drivers. To do this on windows you have to go All settings--> update and recovery---->Recovery----->Advanced startup---->>restart now and after booting your windows in the blue screen, choose Driver signature OFF option. Then reinstall your drivers and restart your phone on fastboot mode (power on and volume - at the same time ) and run the script again.
Click to expand...
Click to collapse
Thanks, its rooted now
aab44 said:
Thanks, its rooted now
Click to expand...
Click to collapse
im glad my friend that everything works fine
Had to unlock bootloader and root after that my B550 and almost all the files were on their places (only few files changed place on launcher). Glad i didn't lose anything while unlocking bootloader (watching on you Oneplus)
---------- Post added at 11:06 AM ---------- Previous post was at 10:56 AM ----------
Hmm... One little question. If i understand right. Balong bug should be shown on "Build Number". On me it shows that i have B550 as it should. But when i go to TWRP and backup. The backup pre-generated name says Balongxxxxx
Apparently that's normal its the build reference of the device nothing to worry about
This method patches boot image, so if i get OTA, do I need reflash my boot image before update?
Bazilli said:
This method patches boot image, so if i get OTA, do I need reflash my boot image before update?
Click to expand...
Click to collapse
dude ofc you will have to be fully unrooted and with retail recovery in order to get OTA installation.
vampirian said:
dude ofc you will have to be fully unrooted and with retail recovery in order to get OTA installation.
Click to expand...
Click to collapse
Sorry but i was asking about boot.img, not recovery.img. Sure i know that i must be unrooted.
Bazilli said:
Sorry but i was asking about boot.img, not recovery.img. Sure i know that i must be unrooted.
Click to expand...
Click to collapse
well i managed to keep the original recovery last time and unroot my device and it worked just fine on updating through OTA. If something changed i dont know. All we have to do is to test it.
Rooted with xposed fully working B550 and B551 is good
How to unroot?
Hello
I install TWRP, and rooted B551. How I install the stock recovery?
Rerikh said:
How to unroot?
Click to expand...
Click to collapse
You can unroot inside SuperSU settings.

P9 Bricked (Fastboot, force upgrade not working)

Hey guys so I have a problem.
Tried to upgrade to the Nougat EMUI 5 from EMUI 4.1 on my P9. It installed but it had no camera and no keyboard installed. So I tried to do a factory reset, I did but now I'm stuck in the set up wizard, and can't even complete it because no keyboard (google voice in its place) and if I try to skip step that need input and go to the end it just loops from the beginning.
Next step I took a stock rom of 4.1 and placed it in my external SD card in dload folder and tried to do a force upgrade but no help. It immediately shows 5% and it fails with no error just a red exclamation mark. So next I tried to use fastboot to flash it but get errors saying remote command not allowed (I have HiSuite installed, but the phone doesn't show when I run 'adb devices').
Factory reset fails, erecovery fails to download anything, can't system recover with hisuite as it fails. But when I try it, the fastboot screen on the phone say 'rescue mode entered' so it's being detected.
I'm at my wits end here on how to get it back. Screw latest android, just want to use the phone. Also does this break warranty? I didn't root it or anything but installing unsupported software could be considered warranty void?
Thank you for help in advance
Fybere said:
Hey guys so I have a problem.
Tried to upgrade to the Nougat EMUI 5 from EMUI 4.1 on my P9. It installed but it had no camera and no keyboard installed. So I tried to do a factory reset, I did but now I'm stuck in the set up wizard, and can't even complete it because no keyboard (google voice in its place) and if I try to skip step that need input and go to the end it just loops from the beginning.
Next step I took a stock rom of 4.1 and placed it in my external SD card in dload folder and tried to do a force upgrade but no help. It immediately shows 5% and it fails with no error just a red exclamation mark. So next I tried to use fastboot to flash it but get errors saying remote command not allowed (I have HiSuite installed, but the phone doesn't show when I run 'adb devices').
Factory reset fails, erecovery fails to download anything, can't system recover with hisuite as it fails. But when I try it, the fastboot screen on the phone say 'rescue mode entered' so it's being detected.
I'm at my wits end here on how to get it back. Screw latest android, just want to use the phone. Also does this break warranty? I didn't root it or anything but installing unsupported software could be considered warranty void?
Thank you for help in advance
Click to expand...
Click to collapse
I believe your warranty is still valid since you havent unlocked the bootloader. After upgrading to Nougat you should have downloaded the rollback package from huawei`s page, since you cannot simply go from Nougat back to Marshmallow ( you need to flash two files, first being "an intermediate package", and second one being marshmallow update.app file, both of which can be downloaded from huawei`s official site ). Try this and see if it helps
http://www.carbontesla.com/2016/11/downgrade-rollback-huawei-p9-nougat-to-marshmallow-europe/
Brontok said:
I believe your warranty is still valid since you havent unlocked the bootloader. After upgrading to Nougat you should have downloaded the rollback package from huawei`s page, since you cannot simply go from Nougat back to Marshmallow ( you need to flash two files, first being "an intermediate package", and second one being marshmallow update.app file, both of which can be downloaded from huawei`s official site ). Try this and see if it helps
Click to expand...
Click to collapse
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Fybere said:
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Click to expand...
Click to collapse
You`re welcome. DC Phoenix is good, but you have to pay in order to use it, right ? That`s my problem, I cant pay since all my money comes from my dad . In your case I would probably try to update via huawei updater and HiSuite. As far as I`ve seen, that method has been most reliable for the majority of users.
Fybere said:
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Click to expand...
Click to collapse
I dont know how much research you have done or what you have tried exactly but it sounds like you have made matters worse. I was in your situation before but was able to get past the setup wizard without a keyboard, after this I got ADB working and just installed a keyboard APK.
C900 means you have a cross flashed rom, this can cause all sorts of different issues and I believe when it comes to updates, C900 either gets no updates at all or be the very last in line to get updates. Also, being on C900 could void your warranty.
DC Phoenix worked for me, I found myself in the same position as you (no dload, reocvery, e-recovery only fastboot) and thought my phone was unrecoverable for good. Tried every method possible. in the end bit the bullet paid the fee for DC Phoenix had my phone running in 20 minutes.
Hopefully some smart cookies can develop some freeware that works the same way.
Z-Blade said:
I dont know how much research you have done or what you have tried exactly but it sounds like you have made matters worse. I was in your situation before but was able to get past the setup wizard without a keyboard, after this I got ADB working and just installed a keyboard APK.
C900 means you have a cross flashed rom, this can cause all sorts of different issues and I believe when it comes to updates, C900 either gets no updates at all or be the very last in line to get updates. Also, being on C900 could void your warranty.
Click to expand...
Click to collapse
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Fybere said:
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Click to expand...
Click to collapse
Awesome, good to hear. I highly recommend you upgrade to Nougat (but make sure your camera app and keyboard app is installed and working). You should be able to do this by using HiSuite and Updater 2.0.
In the same situation
Fybere said:
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Click to expand...
Click to collapse
Hi, can you tell me how to use this tool? because unfortunately I'm in the same situation.
mjcaballero said:
Hi, can you tell me how to use this tool? because unfortunately I'm in the same situation.
Click to expand...
Click to collapse
First of all, get your bootloader unlock code. To get it google how to get it (I cant post link as I don't have enough posts to have privileges). If you can't on the English, make a new account on the chinese emui page and use google translate in chrome to navigate. (if the padlock button doesnt give you a form to fill out, clear your cache and cookies or open in incognito mode)
Once you have the code, find the "SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility" thread on XDA and download the latest stable build, should be around 700mb. Also in the thread, the guy posted a video on how to do it.
Step 1: Unlock bootloader
Step 2: install TWRP Recovery
Step 3: Root
These 3 steps are in the video.
Once you successfully rooted, open the tool again and in the Utilities menu (7) there is an option to flash OEMInfo. Select that and choose the OEM info you want. I needed C432. It will use the superuser app to flash it, reboot and you should be on it.
If you are asking how to use DC-Phoenix, again they have both written as well as a video with instructions on how to do it. You don't need an unlocked bootloader as it will use an exploit to circumvent it. Do Method 1, if it doesn't work, do Method 2.
Good luck mate
Z-Blade said:
Awesome, good to hear. I highly recommend you upgrade to Nougat (but make sure your camera app and keyboard app is installed and working). You should be able to do this by using HiSuite and Updater 2.0.
Click to expand...
Click to collapse
I got into this mess in the first place by flashing the B361 and my camera and keyboard didnt work after upgrading it. But now that i know how to fix it, I might give it a shot. Is there a thread with features and testing of the Nougat emui 5 for P9? I saw a lot of threads of people rolling back due to battery issues and other stuff. Don't want to update if its not the best.
Thanks
Fybere said:
First of all, get your bootloader unlock code. To get it google how to get it (I cant post link as I don't have enough posts to have privileges). If you can't on the English, make a new account on the chinese emui page and use google translate in chrome to navigate. (if the padlock button doesnt give you a form to fill out, clear your cache and cookies or open in incognito mode)
Once you have the code, find the "SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility" thread on XDA and download the latest stable build, should be around 700mb. Also in the thread, the guy posted a video on how to do it.
Step 1: Unlock bootloader
Step 2: install TWRP Recovery
Step 3: Root
These 3 steps are in the video.
Once you successfully rooted, open the tool again and in the Utilities menu (7) there is an option to flash OEMInfo. Select that and choose the OEM info you want. I needed C432. It will use the superuser app to flash it, reboot and you should be on it.
If you are asking how to use DC-Phoenix, again they have both written as well as a video with instructions on how to do it. You don't need an unlocked bootloader as it will use an exploit to circumvent it. Do Method 1, if it doesn't work, do Method 2.
Good luck mate
I got into this mess in the first place by flashing the B361 and my camera and keyboard didnt work after upgrading it. But now that i know how to fix it, I might give it a shot. Is there a thread with features and testing of the Nougat emui 5 for P9? I saw a lot of threads of people rolling back due to battery issues and other stuff. Don't want to update if its not the best.
Click to expand...
Click to collapse
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
i have problem to
..
---------- Post added at 12:33 PM ---------- Previous post was at 12:27 PM ----------
please i try to install twrp but not work
---------- Post added at 12:38 PM ---------- Previous post was at 12:33 PM ----------
mjcaballero said:
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
Click to expand...
Click to collapse
what you chose i dont know i buy buy the DC PH..
HOW
---------- Post added at 02:38 PM ---------- Previous post was at 02:33 PM ----------
mjcaballero said:
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
Click to expand...
Click to collapse
PLEASE
---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------
i install tswp last but not work
---------- Post added at 02:44 PM ---------- Previous post was at 02:40 PM ----------
ppppplease
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
oooooooo

P20 Pro Telus Rooting

Hey everyone I'm looking to root my Canada Telus P20 pro. I'm looking to Unlock my phone , install twrp (or on ramdisk) , SuperSU or magik my stock room.
downloaded Tool All In One but it doesn't support my device: CLT-L04. The text in blue means it's "unsupported"
After reading around some more I came across this thread. Which explains you can get the key and unlock the phone yourself, HOWEVER the website does not have CANADA line. I can't pass the sign up screen because it needs to send a text me to verify but the area codes are non-canada.
Also came across this thread. Can some explain how this works?
matthewacbroad said:
Hey everyone I'm looking to root my Canada Telus P20 pro. I'm looking to Unlock my phone , install twrp (or on ramdisk) , SuperSU or magik my stock room.
downloaded Tool All In One but it doesn't support my device: CLT-L04. The text in blue means it's "unsupported"
After reading around some more I came across this thread. Which explains you can get the key and unlock the phone yourself, HOWEVER the website does not have CANADA line. I can't pass the sign up screen because it needs to send a text me to verify but the area codes are non-canada.
Also came across this thread. Can some explain how this works?
Click to expand...
Click to collapse
It does support it, i unlocked bootloader and root my P20 pr0 with it. CLT-L04, Before you run the tool make sure adb its started, phone usb options should beb on transfer files mode.
oriveradel said:
It does support it, i unlocked bootloader and root my P20 pr0 with it. CLT-L04, Before you run the tool make sure and its started, phonebusb options should beb on transfer files mode.
Click to expand...
Click to collapse
you have to excuse me. the last phone I unlocked and rooted is HTC 10.
HTC had unlock site. I flash TWRP , flashed detoxed ROM with exkernel
LOOKING TO DO THIS:
unlock bootloader
flash TWRP
flash superSU or Magik on stock ROM
flash modded kernel for performance/thermal control (exkernel)
is this available
matthewacbroad said:
you have to excuse me. the last phone I unlocked and rooted is HTC 10.
HTC had unlock site. I flash TWRP , flashed detoxed ROM with exkernel
LOOKING TO DO THIS:
unlock bootloader
flash TWRP
flash superSU or Magik on stock ROM
flash modded kernel for performance/thermal control (exkernel)
is this available
Click to expand...
Click to collapse
https://forum.xda-developers.com/ho...sh-official-firmware-recovery-t3769279/page49
matthewacbroad said:
After reading around some more I came across this thread. Which explains you can get the key and unlock the phone yourself, HOWEVER the website does not have CANADA line. I can't pass the sign up screen because it needs to send a text me to verify but the area codes are non-canada.
Click to expand...
Click to collapse
Just pick any country and register with your email and leave phone number blank. Put in your email and beside Email code, use the link for Obtain Code.
hjin said:
Just pick any country and register with your email and leave phone number blank. Put in your email and beside Email code, use the link for Obtain Code.
Click to expand...
Click to collapse
What's the firmware version for telus (firmware finder app)
hjin said:
Just pick any country and register with your email and leave phone number blank. Put in your email and beside Email code, use the link for Obtain Code.
Click to expand...
Click to collapse
It won't allow me to continue unless I verify with a number. that's my problem
oriveradel said:
What's the firmware version for telus (firmware finder app)
Click to expand...
Click to collapse
link? I'll post it
Hey I was able to unlock my bootloader through the website. This laptop had internet explorer and for some reason I wasn't able to pass the sign without providing # verify code.
however installing firefox and you can skip this step. Everythings good I have unlocked the bootloader by command
Also any recommend detoxed stock ROMs ?
I rooted my phone without all in one tool, as it doesn't support my device. Unlocked my bootloader, fastboot flash TWRP through minimal android drivers using command prompt.
matthewacbroad said:
Also any recommend detoxed stock ROMs ?
I rooted my phone without all in one tool, as it doesn't support my device. Unlocked my bootloader, fastboot flash TWRP through minimal android drivers using command prompt.
Click to expand...
Click to collapse
Good stuff. You made it this far. Now there is this one rom but you have to rebrand the phone to L29 using Funky Huawei or something like that but then even if you manage to do that there is only one stock rom and one aosp rom I don't think either are worth losing VoLTE over but that's me.
mrnovanova said:
Good stuff. You made it this far. Now there is this one rom but you have to rebrand the phone to L29 using Funky Huawei or something like that but then even if you manage to do that there is only one stock rom and one aosp rom I don't think either are worth losing VoLTE over but that's me.
Click to expand...
Click to collapse
Thanks,
Here is my problem. Everytime I restart my phone Swift keyboard reinstalls itself.
Root uninstaller pro reports I'm rooted but system partition isn't r+w (read / write) so all I can do is disable applications but some of them re-enable itself apon restart...
Also if I update magik manager to latest version , causes magik manager to close when I tap the icon. Which means any application that requires root also closes when trying to request root. I have to uninstall magik from system settings. Reboot into TWRP and flash old magik version.
matthewacbroad said:
Thanks,
Here is my problem. Everytime I restart my phone Swift keyboard reinstalls itself.
Root uninstaller pro reports I'm rooted but system partition isn't r+w (read / write) so all I can do is disable applications but some of them re-enable itself apon restart...
Also if I update magik manager to latest version , causes magik manager to close when I tap the icon. Which means any application that requires root also closes when trying to request root. I have to uninstall magik from system settings. Reboot into TWRP and flash old magik version.
Click to expand...
Click to collapse
Yes. I noticed that too. So I didn't update from the app again. Just use titanium backup to freeze or uninstall system apps.
matthewacbroad said:
Thanks,
Here is my problem. Everytime I restart my phone Swift keyboard reinstalls itself.
Root uninstaller pro reports I'm rooted but system partition isn't r+w (read / write) so all I can do is disable applications but some of them re-enable itself apon restart...
Also if I update magik manager to latest version , causes magik manager to close when I tap the icon. Which means any application that requires root also closes when trying to request root. I have to uninstall magik from system settings. Reboot into TWRP and flash old magik version.
Click to expand...
Click to collapse
Use magusk 16.0 and DO NoT update magusk manager. Delete apps you do not want straight from System /apps and System/private apks
Thanks, is it worth it to upgrade magik?
I have a small problem. HTC 10 my last phone, when press recent apps or square button and close all apps it would close all of them. Here I click the garbage icon it says closed all apps but minute later they all reappear. Just wondering a way around this.
Same time about 10 sec apart

[GUIDE]Unlocking Bootloader + Magisk Root for Huawei Mate 20 Pro

I read through quite a few post here to get everything sorted out and in order to save every one some time here is a summary of all the info I have gathered so far, and my way to thank the forum for offering me so many helpful tips. I'll try to keep this thread updated as information comes in.
All credit goes to their respective owners, I am only aggregating all the information here.
Current status on BL Unlock:
China version: OEM unlock not greyed out, direct BL unlock possible
EU/NA version (L09/L29/L0C): OEM unlock greyed out in developer options, BL unlock possible via FunkyHuawei method by upgrading to .170.
UPDATE 2019/01/02: Some users reported they have already received the .171 update from carrier (https://forum.xda-developers.com/showpost.php?p=78571337&postcount=6), if that is the case you can skip the FH Method part and go directly to unlock BL.
Note: Currently .170 is not GooglePay certified, so Google Pay won't work on this, if you must have Google pay please wait for your carrier to update to some version that support OEM unlock (tap build number 7x to get Developer Options in Settings -> System -> About Phone and then go to Settings -> System -> Developer Options and see if Enable OEM Unlock option is enabled).
Also current recovery install requires you to boot into recovery (Power and volume up with phone disconnected from USB) every single time if you want root, which is not perfect.
The only time you'd be required to wipe your phone is right after your BL is unlocked with fastboot OEM unlock, please make sure you have a backup before doing that step.
Where to get unlock code?
In order to get BL unlocked, you need both allow OEM unlock option NOT greyed out (i.e., you can enable it) AND a BL unlock code. BL unlock code can only be purchased either from FunkyHuawei (55 USD one time for BL unlock code only or if you buy an unlimited pass 132USD for unlimited flashing + BL unlock code (note that it is locked to your phone and can not be transferred)), or MinistryOfSolutions (30 Euro, https://ministryofsolutions.com/huawei-bootloader-unlock-service-all-new-models-new-firmwares, BL unlock code only).
FunkyHuawei Method (for non-China version)
1. Create an account in https://funkyhuawei.club/membersarea, buy 1 credit (if you just want to download .170 firmware, each credit cost 18USD).
2. Go to Select Firmware tab, use LYA-Global if you don't see the exact model. Then select .171 version.
3. Follow instructions here: https://pastebin.com/raw/Db5ZSyqu, you must download the specific HiSuite version (9.0.2.301)and the specific installer executable. Run the executable FHHiSuiteInstaller.exe as administrator (right-click and choose Run As Administrator) <- must run as admin since it will need to modify your host file. Make sure the script runs without error.
3.1 (Additional step for L0C): Edit the c:\users\YOURHOMEFOLDER\appdata\local\hisuite\userdata\updatedogdev\hisuiteconfig.xml file and change LYA-L29 to LYA-L0C everywhere it occurs and save the file. (Thanks to FunkyHuawei Support for pointing this one out).
4. Put the phone into fastboot mode (adb reboot-bootloader or with the phone off connect the usb cable while holding volume down, or boot the phone holding volume down with USB cable connected to PC).
5. Go to HiSuite on your PC and click on System Recovery (furthest to the right towards the bottom of the main screen), and let it do the magic. You will see some cmd windows pop up however it should get to the download progress with a percentage pretty fast, if you don't see that pop up then please check to make sure you have at least one credit in the FH Select Firmware tab and you have installed the specific versions of HiSuite and ran the installer as admin in Step 3.
6. Once everything is completed please verify to see if your firmware version is .171.
Unlock Bootloader
Again, get the BL code and go to Settings -> System -> Developer Options and make sure Enable OEM Unlock option is enabled. Also check to make sure you have everything backed up. Also enable USB Debugging in the same screen as well.
Rest is pretty standard:
Code:
adb devices (will bring up the authorization window on your phone, click on Always Trust)
adb reboot-bootloader
fastboot devices (make sure the device is in fastboot mode)
fastboot oem unlock *UNLOCK CODE*
at this point there will be a format operation performed on the phone, if it didn't complete successfully don't worry, your phone is wiped. During the boot you should see a black window with yellow text of warnings to tell you your phone is unlocked and not secured.
Go through all the steps to initialize the phone, turn on Developer options again, and enable USB Debugging again.
Root
1. Download and install Magisk Manager from this XDA post: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Switch channel, go to Magisk Manager -> Settings -> Update Channel , set it to Custom, and the URL is https://bit.ly/2N8UVlq (at the moment, per https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337). Go back to main screen and down swipe to refresh, it should say Latest Version > v18.0.
3. You will need to find the stock RECOVERY_RAMDIS.img file, I used HW Firmware Finder (https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146) to help me with the task, however I couldn't find the L0C update file and ended up using L09 update file instead, which appear to work. I also couldn't find the update.zip for .171 so I ended up using the latest full update version that was available to me (http://update.hicloud.com:8180/TDS/...69/g1750/v181585/f1/full/update_full_base.zip).
4. Unzip the file, drag out UPDATE.APP file in the zip package, and opened it with Huawei Firmware Extractor (I used 0.9.9.5 in this thread: https://forum.xda-developers.com/showthread.php?t=2433454). Extract and open the UPDATE.APP in update file. If you get a checksum error make sure to uncheck both of the verify checksum in Settings -> Extract.
5. Now you should see a RECOVERY_RAMDIS.img file, right click and extract it.
6. Send the RECOVERY_RAMDIS.img file back to your phone (anywhere is fine), go back to Magisk Manager -> Install -> Patch boot, get the patched_boot.img file from the phone back to the PC.
UPDATE 2019/01/02: @pvillasuso was kind enough to post the ramdisk image (both original and Magisk modified) for Mate 20 Pro LYA-L09 (Firmware version .171):https://forum.xda-developers.com/showpost.php?p=78575496&postcount=13, obviously use it at your own risk.
7. Go to fastboot mode again:
Code:
adb devices
adb reboot-bootloader
fastboot devices
fastboot flash recovery_ramdisk "PATH_TO_patched_boot.img"
fastboot reboot
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Boot up and if you go to Magisk now you should be able to see Magisk installed with Installed Version same as Latest Version.
Congrats you are now rooted!
In future you will need to boot into recovery each time to maintain root (which requires you to turn phone off and power + vol up), if you prefer not to do so @ThatsJustLogic suggested you can use the app https://forum.xda-developers.com/showpost.php?p=78569733&postcount=2 to add a one-click reboot from your dropdown menu.
Credits:
@ThatsJustLogic - Figured out the installation steps to patch ramdisk: https://forum.xda-developers.com/showpost.php?p=78554707&postcount=125
@duraaraa - Guy behind FunkyHuawei for figuring out the .171 upgrade and make everything works smoothly https://forum.xda-developers.com/mate-20-pro/how-to/unlock-rebrand-unbrick-update-t3855065
@mutahharbashir - Guy behind MinistryOfSolutions for the unlock BL code.
And creators of Magisk, HWFirmwareFinder, HWUpdateExtractor.
zhuanyi said:
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Click to expand...
Click to collapse
To stop you needing to do this on every boot this app: https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials allows you to add a "Reboot Recovery" button to your notification tray so its just a one tap reboot instead of holding volume up when you want to reboot after applying a change or something its something small but it saves some hassle.
Awwsome, thank you so much. Now I can finally use Google pay on global firmware 9.0.0.171. It's working perfectly
This is amazing development
Hi, can someone post his oeminfo?
On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.
Thank you for the guide.
Can we re-brand from Chinese to international now?
thunderpossuem said:
On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.
Click to expand...
Click to collapse
How come? Can you post a screenshot with developer options on yhe screen?? Oh, you have. Can this mean that we will be able to unlock bootloader for free when v168 update arrives to other countries??
Sent from my LYA-L29 using XDA Labs
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
That's just what i thought
Sent from my LYA-L29 using XDA Labs
Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know
pvillasuso said:
Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know
Click to expand...
Click to collapse
The patched file will work for anyone who has the mate 20 pro and the same FW version as you. Theres no extra steps it just removes the finding the FW, extracting and patching the image yourself They will still need magisk and the canary channel.
If you are going to share I would specify Firmware version and attach a non patched one incase people have issues and want to revert.
My phone model : Mate 20 Pro LYA-L09 (Firmware version 9.0.0.211)
patched_boot.img > https://www.mediafire.com/file/fp3jk281d47bh6k/patched_boot.img/file
Apply on your own risk , worked for me !
Hi, glad to hear that even L0C model has to the chance to root. Just wondering after flash the global .171 version which should solve the OEM greyed-out problem, the next step is to purchase a BL unlock code? And is there a chance that after BL and FRP unlocked. My model (LYA-L0C) can be rebrand to another one?
deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
Indeed it is 18 USD saved, also hopefully it is more compatible with your phone.
Can you give an example of your path to "PATH_TO_patched_boot.img"
I must be getting syntax incorrect for the file in internal storage download folder, and I have tried everything with and without / leaving out folders.
is this ota proof?
Some rooting questions....
Hi.
I will try to be brief and on topic. Feel free to remove post if not according to Xda forum rules.
Long story short. I am an heavy iOS user from the apple jailbreak scene. I am no developer (only user) and now I have taken the big step from IOS to Android.
Huawei mate 20 pro broke my curiosity. I have always "jailbroken" my iPhone since 2007 and now I am considering root of my HM20PRO.
I have some questions before I try this and brick my phone.
I have Norwegian model, LYA-L29 with 9.0.0.153 (c432) software. (BL unlock greyed out here as well)
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
Hope that someone can take the time to help me with my questions.
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
sorry for the noob questions, but I am new with this so thanks...
Regards,
Kenneth - Trondheim, Norway
PS:I have to say the switch from iOS to android and Huawei mate 20 pro have been great so far (except new replacement phone on the first day with green screen on BOE screen.) Now all is good.
Main reasons to root android?
I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.
fromiOS2Android said:
Hi.
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
Main reasons to root android? I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.
Click to expand...
Click to collapse
Hi, first of all, welcome to Android
My advice is to NOT root until you got an answer to all your questions
I'll let some pros answer the technical questions on the partitions) but here's what I can tell you:
- Main reason to root for me is adblockers and (not a must though) custom roms.
- There is a function within magisk to hide root from apps.
- On the fixes, yes, 171 is the one that allows root and that's also the latest one with all the fixes.
- Once you root you stay rooted, you don't have to repeat the whole process at every boot.
- From what I read in several threads, right now you can't revert to older firmwares. Also, the 171 seems to be market specific, what I will do is to wait until the update gets rolled out in my market by Huawei, I read that the unlock bootloader option is then available officially.
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)
charliebigpot said:
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)
Click to expand...
Click to collapse
Using Magisk Hide on Google Pay will prevent it from detecting root, however if SafetyNet fails then it probably still won't work.
There are a few Magisk modules that can (apparently) force SafetyNet to pass, however I haven't ever used any of them.

Question MIUI Rollback 13.0.17.0.SKFEUXM to 13.0.16.0.SKFEUXM

Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.
awambawamb said:
Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.
Click to expand...
Click to collapse
Google fastboot flash with PC or recovery flash via custom Recovery.
For both the bootloader has to be unlocked. In my opinion there's no other way to rollback .
I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A
awambawamb said:
....
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide......
Click to expand...
Click to collapse
I advise to search for the right information on XDA and the downloads from Xiaomi servers.
awambawamb said:
I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A
Click to expand...
Click to collapse
Downgrading using the rename trick is not possible now due to OTA validation. But still, downgrading is still possible as long as the bootloader is unlocked (you can re-lock bootloader afterwards btw so no worry about banking apps).
Procedure might be something similar to this:
1. Unlock bootloader
2. Flash any latest OSS ROM (this is just to remove MIUI)
3. Use MiFlash and fastboot method to install old versions (re-lock if you want)
Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.
PS: Just to add, Anti-Rollback is not yet enabled for sweet so no worries with getting bricked while downgrading. Just be careful and flash appropriately.
Thanks for the kind reply, @BigChungus321 . Glad to hear that I can still unlock and lock the bootloader! at least for those 6 months of warranty.
Just one thing, in the step you suggested you said:
1. Unlock bootloader​2. Flash any latest OSS ROM (this is just to remove MIUI)​3. Use MiFlash and fastboot method to install old versions (re-lock if you want)​Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.​​Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?
wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?
awambawamb said:
Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
Click to expand...
Click to collapse
It is the same but I do encounter people who face anti-rollback error rejecting the downgrade if flashing from MIUI to MIUI. But going from OSS to MIUI, this arb check does not seem to occur.
awambawamb said:
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?
Click to expand...
Click to collapse
No clue if that prevents the issue/bug you encounter. I usually just dirty flash the full rom update (not the incremental which is around ~200mb) in recovery and I don't seem to get issue this way, aside from recovery being replaced because dm-verity is getting activated again.
awambawamb said:
wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?
Click to expand...
Click to collapse
I've seen many people who have this issue too. Again, no clue how to fix this. Maybe reboot, and just enable mobile data. Try changing sim card or switching sim card slots. Use other Mi Account for unlocking. I did see discussions about how using the same sim card and same Mi account can on a different device can cause this. I still have no clue how to fix this though so sorry. Might be a good idea to use a fresh sim card and mi account if you still encounter it.

Categories

Resources