Database Info

TWRP3.0.2 for EMUI 4.1 with One Click Root Built In

This TWRP can decrypt data partition and you can find 1 click to root function in "advanced" menu (bottom left).
This TWRP is for EMUI 4.1 only!
Instructions:
1. Unlock bootloader and keep your unlock code in record (force flash stock ROM will re-lock the phone)
2. Turn off "Find My Phone"
3. Download the file below and unzip
4.1 Run the exe, it's Chinese UI, but you can see "...bootloader" button for unlock, "...recovery" button is for flash bootloader.
4.2 Or manually flash recovery files via fastboot
5. Root function is located at Advanced menu at bottom left button.
Download (MEGA)
or
http://www.mirrorcreator.com/files/12YBC2XZ/
Source: http://club.huawei.com/forum.php?mod=viewthread&tid=11334720&page=1&authorid=6362185

Wow, tried?
Sent from my Nexus 6 using XDA-Developers Legacy app

siggey said:
Wow, tried?
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Got my device soon, but I see screenshots of TWRP is working.

The link appears to be dead, but in the meantime I'll try a download from the forum you linked.
---------- Post added at 08:09 AM ---------- Previous post was at 07:18 AM ----------
Just flashed it, and succesfully rooted the device. Thanks for sharing.

Mvs1989 said:
The link appears to be dead, but in the meantime I'll try a download from the forum you linked.
---------- Post added at 08:09 AM ---------- Previous post was at 07:18 AM ----------
Just flashed it, and succesfully rooted the device. Thanks for sharing.
Click to expand...
Click to collapse
Glad to hear that.
I just put up the link this morning and I'll check it up after work.

If anyone was also wondering if Xposed works, I can only say that it does install, it does boot, but the phone 'settings' force closes (no message, just returns to previous window).
Steps taken:
Installed Xposed installer 3.1.1
Installed version 87 (not from recovery)
Rebooted
Reboot takes a long time, but eventually boots. Seems to work fine until I went to the phone settings and it wouldn't open.
Opened the Xposed installer again
Uninstalled (not from recovery)
Maybe results will vary with an older xposed or doing it properly from recovery, not risking it at the moment.

Mvs1989 said:
The link appears to be dead, but in the meantime I'll try a download from the forum you linked.
---------- Post added at 08:09 AM ---------- Previous post was at 07:18 AM ----------
Just flashed it, and succesfully rooted the device. Thanks for sharing.
Click to expand...
Click to collapse
I've updated the link, thanks for pointing out the error.

Just tried flashing Xposed 86 (tried 87 before) through the recovery, also disabled resource hooks in the xposed installer app.
Now everything seems to work.
For anyone that is interested .

Thank you. This worked for me.
What I did:
- unlock bootloader
- access phone bootloader with phone connected to computer
- click app's "...recovery" button and select TWRP recovery file provided with app (the installation is almost instantaneous)
- boot phone into recovery (TWRP will be in Chinese but English is available)
- root phone from TWRP advanced menu (clicking the "root" button will install supersu)

Where was this, when the 5x started development? I already flashed, and rooted my 5x, but would this tool work on that? If so, I can archive it for later use, if needed, or change it, so it could work with the 5x, since they both(at this time) have EMUI 4.1. Is it possible?
---------- Post added at 05:00 AM ---------- Previous post was at 04:55 AM ----------
Mvs1989 said:
If anyone was also wondering if Xposed works, I can only say that it does install, it does boot, but the phone 'settings' force closes (no message, just returns to previous window).
Steps taken:
Installed Xposed installer 3.1.1
Installed version 87 (not from recovery)
Rebooted
Reboot takes a long time, but eventually boots. Seems to work fine until I went to the phone settings and it wouldn't open.
Opened the Xposed installer again
Uninstalled (not from recovery)
Maybe results will vary with an older xposed or doing it properly from recovery, not risking it at the moment.
Click to expand...
Click to collapse
I heard that EMUI has a problem with xposed, it's at the start of the honor 5x forums, in development.

Is it easy to unlock bootloader?
I have not yet gotten a 6x, but will soon. Trying to plan custom rom and etc in advance. Its really great that the device has such activity!
In G7, bootloader unlock requires getting a code from Huawei website and took some time before the phone model was on the website. It also did a factory reset after applying the code for which it gave no warning for.
I imagine its similar bit Honor, seeing as Huawei is their parent.
Sent from my Huawei Ascend G7 using XDA Labs

drakenabarion said:
Is it easy to unlock bootloader?
I have not yet gotten a 6x, but will soon. Trying to plan custom rom and etc in advance. Its really great that the device has such activity!
In G7, bootloader unlock requires getting a code from Huawei website and took some time before the phone model was on the website. It also did a factory reset after applying the code for which it gave no warning for.
I imagine its similar bit Honor, seeing as Huawei is their parent.
Sent from my Huawei Ascend G7 using XDA Labs
Click to expand...
Click to collapse
Yes, it's almost the same for 6x to unlock.

reggjoo said:
Where was this, when the 5x started development? I already flashed, and rooted my 5x, but would this tool work on that? If so, I can archive it for later use, if needed, or change it, so it could work with the 5x, since they both(at this time) have EMUI 4.1. Is it possible?
---------- Post added at 05:00 AM ---------- Previous post was at 04:55 AM ----------
I heard that EMUI has a problem with xposed, it's at the start of the honor 5x forums, in development.
Click to expand...
Click to collapse
For 5X, there is only TWRP, not with the 1-click root function.

Anyone done this on a BLN-L24 yet?
I was gonna wait a while to mess with this thing but I just switched carriers and I need to try and get around the hotspot provisioning check.

jerryhou85 said:
For 5X, there is only TWRP, not with the 1-click root function.
Click to expand...
Click to collapse
Yes, but you simply have to flash SuperSU zip to root.

Andromeda_Station said:
Anyone done this on a BLN-L24 yet?
I was gonna wait a while to mess with this thing but I just switched carriers and I need to try and get around the hotspot provisioning check.
Click to expand...
Click to collapse
This one should work on all models of Honor 6x, but again, you have to take the risk...

jerryhou85 said:
This one should work on all models of Honor 6x, but again, you have to take the risk...
Click to expand...
Click to collapse
Success
Was able to find the offending files in system/app that were initiating the carrier hotspot/tethering check...deleted them and now I'm in business.
Also, if anyone is having trouble getting viper4android working (I was), there is a flashable zip in this thread that works. :good:

Andromeda_Station said:
Success
Was able to find the offending files in system/app that were initiating the carrier hotspot/tethering check...deleted them and now I'm in business.
Also, if anyone is having trouble getting viper4android working (I was), there is a flashable zip in this thread that works. :good:
Click to expand...
Click to collapse
Glad it works!

How can I lock the bootloader in case I have to use warrancy?

hanset said:
How can I lock the bootloader in case I have to use warrancy?
Click to expand...
Click to collapse
WinDroid Toolkit v3.1

[GUIDE] Debranding to C432 and updating to B361 (Nougat) for EVA-L09

Like many people here, I was eager to get onto Android 7 but the issue I faced was the fact that I got a branded phone and a long wait till I officially get the Android 7 update. Looking through this forum I was very put off on manually updating it to Android 7 with so many threads about bricked phones. However, the urge to get onto Android 7 was too great so ultimately, I decided to do my research and just do it. I am not new to flashing and custom roms but I am new to Huawei but I had confidence that I will recover if I do brick my new P9. In the end (after a few bricks and a couple of mild heart attacks), I got there and to get there, I needed to grab information from multiple threads. So I have decided to put together this guide so people have a singular guide to debrand and get onto Android 7. Below are steps and threads I took to debrand my C34 to C432 and update it to B361.
What listed below is what I did to get onto Android 7, this may or may not work for you so use this guide at your own risk.
Using this Guide - Please read through this guide BEFORE attempting it. There is a lot of large files to download so I recommend that you download everything you need before you make a start and a fast and reliable internet is strongly recommended.
Prep Work
- Backup all your data because your phone will get wiped.
- Make sure you have the stock recovery already flashed and make sure your phone is not rooted (may not be necessary but this was the state my phone was in).
- Get yourself a bootloader code from Huawei. Go to http://www.emui.com/en/plugin/hwdownload/download, you will need to create a Huawei ID if you haven't already done so. Click on the Unlock Bootloader link and fill out the form, you should get a bootloader code almost instantly after submitting the form.
- Download and install HiSuite (http://consumer.huawei.com/minisite/HiSuite_en/index.html).
- Download the SRK Tool from here: https://forum.xda-developers.com/showpost.php?p=66737472&postcount=2
Now lets make a start.
1. Download and flash the dload-huawei-p9-eval09-eva-b136.zip from this thread: https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818. Instructions on how to flash this is in the first post. After flashing, you should be on the L09C900B136 firmware. NOTE: If it boots up to a white screen asking you to enter password, reboot into recovery by holding volume up when you powering up your phone, do a wipe partition and factory reset. You may need to reboot your phone a number times before the phone boots up correctly.
2. After flashing and booting into the L09C900B136 firmware, you will need to unlock your bootloader and install TWRP. You can use the SRK Tool to do this, please have a look at this thread (https://forum.xda-developers.com/showpost.php?p=66737472&postcount=2) and watch the video on how to do this. NOTE: You only need to unlock bootloader and install the TWRP recovery.
3. After your phone has been unlocked with TWRP recovery installed, download oeminfo-huawei-p9-eval09-c432.zip from this thread: https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903 and flash it via TWRP. To get into TWRP, power off your phone and go into recovery by powering up your phone while holding volume up.
4. Once you flashed the oeminfo file via TWRP, power off your phone and repeat step 1. So you need to flash the dload-huawei-p9-eval09-eva-b136.zip file again via the dload method (power on the phone while holding volume up and volume down). NOTE: When you flash this firmware again, it will lock your bootloader (Fastboot will tell you that the phone is unlocked but I assure you, your bootloader is locked) and restore to stock recovery.
5. Once your phone has booted back up, go into the phone settings and you should see that your phone is now on the EVA-L09C432B136 firmware. To test that the firmware is working as intended, go into the phone settings and go into Updater, updater should pick up the B182 firmware and you should be able to update it to B182 without an issue.
UPDATE: A number of people has reported that they are getting the B166 update instead of B182, if this happes, do a wipe partition and a factory reset after updating to B166. When you get back in, you should be able to update to B182 via Updater in the Settings menu. If this method does not work, you can manually update to B182 by following the steps here: http://www.carbontesla.com/2016/11/download-huawei-p9-b182-marshmallow-update-europe/
6. After your phone has rebooted and you are on the B182 firmware, you need to now update the firmware to B361 via Huawei Updater 2.0 using this guide: https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2.
After all that is done, you should now have a debranded UK C432 P9 running EMUI 5.0.
Special thanks to @paulobrien, @somboons and @KrAzYtHeBoY for their guide, tools, files and video to make this update possible.

Props to you sir. I will try this when I get back. I don't have any doubts now after reading this guide.

Does debranding will affect warranty of the device? Mine is quite new.

zoold3vil said:
Does debranding will affect warranty of the device? Mine is quite new.
Click to expand...
Click to collapse
Its very likely that debranding will void your warranty since you will need to unlock the bootloader and flash a firmware that is not the same as your original model.

Z-Blade said:
Its very likely that debranding will void your warranty since you will need to unlock the bootloader and flash a firmware that is not the same as your original model.
Click to expand...
Click to collapse
Thanks for the feedback!

Thanks for the guide. I've recently been battling away trying to go from C34 to C636 - still never got to the bottom of it.
Is that a typo in your post for your original model number - C43? Or did you come from Optus AU C34?
Either way - have you had any network issues in Australia with the new firmware?
Cheers.

halliday77 said:
Thanks for the guide. I've recently been battling away trying to go from C34 to C636 - still never got to the bottom of it.
Is that a typo in your post for your original model number - C43? Or did you come from Optus AU C34?
Either way - have you had any network issues in Australia with the new firmware?
Cheers.
Click to expand...
Click to collapse
Yep, its a typo, thanks for pointing it out. I have no issues what so ever, everything works perfectly fine and there has been no drop in cellular reception, wifi reception, GPS accuracy and etc. Apart from the build saying L09C432, you wouldnt be able to tell the difference.

Z-Blade said:
Yep, its a typo, thanks for pointing it out. I have no issues what so ever, everything works perfectly fine and there has been no drop in cellular reception, wifi reception, GPS accuracy and etc. Apart from the build saying L09C432, you wouldnt be able to tell the difference.
Click to expand...
Click to collapse
Legend. Appreciate the reply - it was tough to find experienced Aussies on the same starting build/carrier.
Now I just wish I hadn't wasted the time going for the Asia Pacific variant!
Will get stuck into it this evening.
Thanks!

Great guide! Reading through it seems easier for it to be managed through hisuite/windows but I have a big issue. For some reason my computer won't recognize my phone! I installed the beta and am on build number EMUI-A168-L09C900B040SP11-log and since doing this stupid move I have been unable to connect to a computer nor install other builds or rollbacks directly on the device so I just feel like smashing it and claiming the insurance. Is there any advise that could be offered to maybe force a firmware upgrade?

Nawor81 said:
Great guide! Reading through it seems easier for it to be managed through hisuite/windows but I have a big issue. For some reason my computer won't recognize my phone! I installed the beta and am on build number EMUI-A168-L09C900B040SP11-log and since doing this stupid move I have been unable to connect to a computer nor install other builds or rollbacks directly on the device so I just feel like smashing it and claiming the insurance. Is there any advise that could be offered to maybe force a firmware upgrade?
Click to expand...
Click to collapse
How did you get onto that build? Have you tried following the guide I put up?

Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!

Nawor81 said:
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Click to expand...
Click to collapse
I cant promise you that the guide I put together will work for you. If its a Nougat beta firmware then you would be technically doing a rollback to MM. Just a bit of a warning, a lot of people who try to roll back to MM, usually encounter problems, annoying problems. Unfortunately, I dont have much experience with this phone or how Huawei does things so I cant help you much. If I am in your shoes, I wouldn't attempt to debrand and flash Nougat using this guide.

Z-Blade said:
I cant promise you that the guide I put together will work for you. If its a Nougat beta firmware then you would be technically doing a rollback to MM. Just a bit of a warning, a lot of people who try to roll back to MM, usually encounter problems, annoying problems. Unfortunately, I dont have much experience with this phone or how Huawei does things so I cant help you much. If I am in your shoes, I wouldn't attempt to debrand and flash Nougat using this guide.
Click to expand...
Click to collapse
That's not the news I wanted to hear! I guess I'll keep this guide in mind and do some more research, hopefully find someone in love with Huawei that might be able to assist. Thanks

SmartPhonesFan said:
Hi z-blade I flashed B136 but it didn't put icons and themes back .. I flashed B182 and STILL didn't put icons and themes back
BUT only B166 gave me proper theme and icons back.. ! After that I flashed I had to flash B182 and so on.. B166 is the key important
Click to expand...
Click to collapse
I got theme and icon on mine but it may have came through when I flash B361. I went from a full factory reset on B136 to B182 to B361, not once did I stop to check to make sure all of the apps are installed, I only started setting up my phone and have a browse once I was on EMUI 5.0. It may be un-necessary to flash B166 if flashing B361 give you themes and icons.
If someone could double check on this when following this guide and report in, that would be great. I am not willing to test it out by rolling back to mushmellow.

Nawor81 said:
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Click to expand...
Click to collapse
Are you on an unbranded device?
If so, the official Huawei support page offers a rollback package if you updated to the Nougat beta.
Make sure you go to the page specific to your country.
---------- Post added at 02:42 AM ---------- Previous post was at 02:34 AM ----------
Z-Blade said:
I got theme and icon on mine but it may have came through when I flash B361. I went from a full factory reset on B136 to B182 to B361, not once did I stop to check to make sure all of the apps are installed, I only started setting up my phone and have a browse once I was on EMUI 5.0. It may be un-necessary to flash B166 if flashing B361 give you themes and icons.
If someone could double check on this when following this guide and report in, that would be great. I am not willing to test it out by rolling back to mushmellow.
Click to expand...
Click to collapse
Broken themes/icons seem to be caused by missing assets in the /CUST/ partition. I managed to get around it on my broken C900 firmware by separately flashing the /hw/normal/ package specific to the build. These can be found in the filelist.xml in the [WAREHOUSE] post - but you need to change the URL manually to grab the file.

SmartPhonesFan said:
So B361 will? Didn't know that.. Didn't want to risk it it took ages to download.. I had 3 folders in B136 but I flashed it via dial pad options.. Not 3btn..maybe if I would flash via 3btn it will give it back then and I wouldn't need B166..
Cannot be bothered.. It's done now..
Nougat best..
Click to expand...
Click to collapse
It makes no difference if you use the 3 button method or via the dial menu, both does exactly the same thing. I am only assuming that Themes could be installed when I flashed B361, I was not paying attention to the apps that was installed but I think this may be the case because I believe the Theme app was updated for EMUI 5.0, again all assumptions here.

Can I jump directly from b136 to b361?
Thanks in advance.

halliday77 said:
Are you on an unbranded device?
If so, the official Huawei support page offers a rollback package if you updated to the Nougat beta.
Make sure you go to the page specific to your country.
Click to expand...
Click to collapse
It's from Vodafone unfortunately

I've followed the guide as far as step 5. When I got there, I ended up getting an update for L09C432B166 which installed fine, but I'm not getting the B182 update. Anyone else run into an issue like this?

trouble2000 said:
Can I jump directly from b136 to b361?
Thanks in advance.
Click to expand...
Click to collapse
No you cant, you need to get to B182 before flashing B361.
d_mouse81 said:
I've followed the guide as far as step 5. When I got there, I ended up getting an update for L09C432B166 which installed fine, but I'm not getting the B182 update. Anyone else run into an issue like this?
Click to expand...
Click to collapse
Try wiping partition and a factory rest and see if you get the B182 update. If not, you can download the B182 update and flash it via dload but if that does not work, you can try doing it via the Hisuite and Updater method.

[OTA] NPH25.200-15 [Retasia_Ds] [XT1572]

link :HERE
For XT1572 (Indian Variant Only)
tested works fine.
ADB Sideload
1. Place the ZIP file in your adb/fastboot directory
2. Reboot to the bootloader and start (stock) recovery
3. At the "dead Andy" with a red exclamation, press POWER+VolUp to get to the stock recovery menu
4. Select "Apply update from ADB"
5. On computer, enter "adb sideload <filename>" but replace <filename> with the OTA ZIP image
6. Wait for the process to finish...
There is other sd card method also but i don't recommend you to follow that as it is a bit tricky.
Edit: this will only work for Blur_Version.24.231.16.clark_retasia_ds.retasia.en .03
Do not attempt to flash or your device will be hard bricked

Thanks a lot. Will try flashing this tomorrow

Working for XT1575?

I have a Moto X Style (XT1572) Double SIM Android 6.0.1 Rom Stock (24.231.13.clark_retasia_ds.retasia.en.03 retmea).
Does it fit for this version?

Sagar_1401 said:
link :HERE
tested works fine.
ADB Sideload
1. Place the ZIP file in your adb/fastboot directory
2. Reboot to the bootloader and start (stock) recovery
3. At the "dead Andy" with a red exclamation, press POWER+VolUp to get to the stock recovery menu
4. Select "Apply update from ADB"
5. On computer, enter "adb sideload <filename>" but replace <filename> with the OTA ZIP image
6. Wait for the process to finish...
There is other sd card method also but i don't recommend you to follow that as it is a bit tricky.
Click to expand...
Click to collapse
Why is the SD card method trickier? You put the OTA(blur) file on your SD card and in stock recovery select "apply update from sd card" and you don't even need a computer. What's so tricky in this?

Javi_Racing said:
I have a Moto X Style (XT1572) Double SIM Android 6.0.1 Rom Stock (24.231.13.clark_retasia_ds.retasia.en.03 retmea).
Does it fit for this version?
Click to expand...
Click to collapse
It does not correspond to my version, I have to keep waiting. :crying:

oliake said:
Working for XT1575?
Click to expand...
Click to collapse
Not sure, but I think if you do use the OTA for the style it will change your phone model in "about phone". Not sure if it changes anything else or if that negatively affects anything though

redemptionx11 said:
Not sure, but I think if you do use the OTA for the style it will change your phone model in "about phone". Not sure if it changes anything else or if that negatively affects anything though
Click to expand...
Click to collapse
The only thing I want to know is if it can boot. I see you don't have an answer for that but let's hope someone dares to try before me

oliake said:
The only thing I want to know is if it can boot. I see you don't have an answer for that but let's hope someone dares to try before me
Click to expand...
Click to collapse
Well, I tried to use one of the first style nougat updates that came out. Couldn't get it to boot. Ended up having to wipe everything and revert to stock 6.0, then reflash the ROM I wanted. It was enough trouble that I'm waiting for some solid answers before I try again. Lol.

redemptionx11 said:
Well, I tried to use one of the first style nougat updates that came out. Couldn't get it to boot. Ended up having to wipe everything and revert to stock 6.0, then reflash the ROM I wanted. It was enough trouble that I'm waiting for some solid answers before I try again. Lol.
Click to expand...
Click to collapse
Unlucky you You flashed it on the XT1575 right?

oliake said:
Unlucky you You flashed it on the XT1575 right?
Click to expand...
Click to collapse
The one I did was that nandroid restore thing.

redemptionx11 said:
The one I did was that nandroid restore thing.
Click to expand...
Click to collapse
Yea but what I meant was what the actual version of the phone you have

Because this always comes up, I downloaded and looked at this OTA...
Your device MUST have the following release keys to work:
motorola/clark_retasia_ds/clark_ds:6.0/MPHS24.49-18-16/12:user/release-keys, also know as Blur_Version.24.231.16.clark_retasia_ds.retasia.en.03
That is the ONLY version this OTA will work on, you must be on build MPHS24.49-18-16 retasia dual SIM, this OTA cannot be applied to ANY OTHER DEVICE or BUILD... don't do it, don't try, don't force it... if it does somehow magically work (or you figure how to force it) you device will be inoperable, possibly hard bricked.
Moto OTA's are differential files, so each piece for each file only includes what is different than the known value from the previous build, that is why these OTA's are so dangerous, they do not replace entire file but patch existing ones with the specific bits that are different only... if it fails or the files are not as expected bad things can and will happen.
BTW, the informtion to decipher what build you have to be on and what it will go to is inside the OTA zip file, in a file called metadata.json

acejavelin said:
Because this always comes up, I downloaded and looked at this OTA...
Your device MUST have the following release keys to work:
motorola/clark_retasia_ds/clark_ds:6.0/MPHS24.49-18-16/12:user/release-keys, also know as Blur_Version.24.231.16.clark_retasia_ds.retasia.en.03
That is the ONLY version this OTA will work on, you must be on build MPHS24.49-18-16 retasia dual SIM, this OTA cannot be applied to ANY OTHER DEVICE or BUILD... don't do it, don't try, don't force it... if it does somehow magically work (or you figure how to force it) you device will be inoperable, possibly hard bricked.
Moto OTA's are differential files, so each piece for each file only includes what is different than the known value from the previous build, that is why these OTA's are so dangerous, they do replace entire file but patch existing ones... if it fails or the files are not as expected bad things can and will happen.
BTW, the informtion to decipher what build you have to be on and what it will go to is inside the OTA zip file, in a file called metadata.json
Click to expand...
Click to collapse
Exactly I have "I have a Moto X Style (XT1572) Double SIM Android 6.0.1 Rom Stock (24.231.13.clark_retasia_ds.retasia.en.03 retmea)" so I could not perform the update of this OTA

Javi_Racing said:
Exactly I have "I have a Moto X Style (XT1572) Double SIM Android 6.0.1 Rom Stock (24.231.13.clark_retasia_ds.retasia.en.03 retmea)" so I could not perform the update of this OTA
Click to expand...
Click to collapse
Yes, as long as you are on the correct build stated previously, and you are unmodified stock, no root, stock recovery, untouched /system, radio, and /boot partitions, then you can just install with adb sideload and go.
Was I unclear in my previous post?

acejavelin said:
Because this always comes up, I downloaded and looked at this OTA...
Your device MUST have the following release keys to work:
motorola/clark_retasia_ds/clark_ds:6.0/MPHS24.49-18-16/12:user/release-keys, also know as Blur_Version.24.231.16.clark_retasia_ds.retasia.en.03
That is the ONLY version this OTA will work on, you must be on build MPHS24.49-18-16 retasia dual SIM, this OTA cannot be applied to ANY OTHER DEVICE or BUILD... don't do it, don't try, don't force it... if it does somehow magically work (or you figure how to force it) you device will be inoperable, possibly hard bricked.
Moto OTA's are differential files, so each piece for each file only includes what is different than the known value from the previous build, that is why these OTA's are so dangerous, they do not replace entire file but patch existing ones with the specific bits that are different only... if it fails or the files are not as expected bad things can and will happen.
BTW, the informtion to decipher what build you have to be on and what it will go to is inside the OTA zip file, in a file called metadata.json
Click to expand...
Click to collapse
Should have added that but now I've added this.. Thank you

@Sagar_1401 thanks for capturing and uploading the OTA
Though it's really sad there is no VoLTE support

aakashverma0007 said:
@Sagar_1401 thanks for capturing and uploading the OTA
Though it's really sad there is no VoLTE support
Click to expand...
Click to collapse
yeah we need volte feature

Sagar_1401 said:
yeah we need volte feature
Click to expand...
Click to collapse
Could you explain me why it's so important to you? What are real benefits of Volte
Sent from my XT1572 using XDA-Developers Legacy app

2be3_80 said:
Could you explain me why it's so important to you? What are real benefits of Volte
Sent from my XT1572 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Last year one of the biggest Mobile Service Provider launched 4G/LTE Services with Free Internet for about 6-7months straight. Also with Free Unlimited International over VoLTE feature. Currently the Free Data Services has ended but the Free Calling is still there.
It was kinda Wreaking Ball for other providers. Basically VoLTE is important for Indian users.
Hope they give us update for Modem supporting VoLTE.
P.S: It's Reliance Jio, Google it.

8.1 Oreo Factory Image

For anyone who hasn't been able to sideload the update or wants the factory images, it is now on the Razer Development Portal

thanks! i've been waiting for this to update

So does this mean that maybe custom Rom/Kernel development may start?

Anyone know if it's safe to update to global 8.1 straight from the Three UK branded 7.1.1 version?
Sent from my Phone using Tapatalk

How do I install this on a three branded handset only got phone today so if Any one could post a guide I'd be most appreciated

patient81 said:
Anyone know if it's safe to update to global 8.1 straight from the Three UK branded 7.1.1 version?
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
Yes it is mate. I'm running 8.1 from 7.1.1 on my three razer phone

Strangeland16 said:
How do I install this on a three branded handset only got phone today so if Any one could post a guide I'd be most appreciated
Click to expand...
Click to collapse
Download the Global Rom and unzip it. Make sure ADB and fastboot drivers are installed on your PC. Open command prompt with Administrator Privileges. Change directory to where you unzipped your rom, type ADB reboot bootloader, run the command flash_all.
Edit: make sure you have usb debugging enabled on your phone

Thanks for this do I need to delete anything off phone first does the bootloader need to be unlocked first sorry complete noob to razor though flashed recoveries and roms on my galaxy s8 .once I've done this will the phone be rebranded orndo I need to do that first.will I be able to download updates after ??
---------- Post added at 09:33 PM ---------- Previous post was at 09:31 PM ----------
Thanks do i need to debrand or unlock bootloader first will this then update from razer not three after ??

Strangeland16 said:
Thanks for this do I need to delete anything off phone first does the bootloader need to be unlocked first sorry complete noob to razor though flashed recoveries and roms on my galaxy s8 .once I've done this will the phone be rebranded orndo I need to do that first.will I be able to download updates after ??
Click to expand...
Click to collapse
This will show you the exact process mate. Yes this will update with razer instead of three. You won't have to hang around for three to release updates
https://developer.razer.com/razer-p...6.2088813517.1524083559-1692679314.1524083559

Thanks I'll gather some courage and have a go

Love this phone but Substratum/Andromeda still doesn't work on 8.1, still a conflict with Razer theme engine? Any way to disable Razer theme engine under root and enable substratum?!?! Or any other way short of flashing LOS, which I tried and failed to do?

Hi
Strangeland16 said:
Thanks I'll gather some courage and have a go
Click to expand...
Click to collapse
Doing this will void your warranty ! Just a heads up. ?

arnookie said:
Doing this will void your warranty ! Just a heads up.
Click to expand...
Click to collapse
Very true but you just need to relock bootloader to make a RMA claim through Razer. Had to do that with my first phone. Surprised this phone doesn't have a tamper flag on it.

I can't open Netflix does anyone have the same problem?
bootloader and critical unlocked but I use Magisk and safety net is ok double true

kaze2295 said:
I can't open Netflix does anyone have the same problem?
bootloader and critical unlocked but I use Magisk and safety net is ok double true
Click to expand...
Click to collapse
Yes I did. I downloaded the latest APK. Just search Google to find it and all is working.

kaze2295 said:
I can't open Netflix does anyone have the same problem?
bootloader and critical unlocked but I use Magisk and safety net is ok double true
Click to expand...
Click to collapse
Did you hide the Netflix app in Magisk?

silvercat said:
Did you hide the Netflix app in Magisk?
Click to expand...
Click to collapse
No. I literally downloaded the Netflix APK and installed it. Presume it installed over the top.

Guys .. Is there any plan for any custom ROMs?!
Thanks.

Mulham82 said:
Guys .. Is there any plan for any custom ROMs?!
Thanks.
Click to expand...
Click to collapse
Just thought GSI, seems like the new wey to do it.

has Android 11 been rooted?

Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?

Wait for the beta's
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Hi,
from what I have read, no, its not a daily driver, yet. I'd wait till the beta's are available in`May, to give it a try.
Though you could always just flash the update & see if it is OK for you. If not revert back to 10.

ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Not rootable yet. Lots of changes to it that Mr. Wu is going to have to work on. He said he knows what to do, just going to take a bit of time.

ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
I am on it and it is definitely stable enough to use as a DD but unfortunately no root yet

I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?

atembleque said:
I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?
Click to expand...
Click to collapse
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.

wangdaning said:
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.
Click to expand...
Click to collapse
Thanks!

Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.

Vanschtezla said:
Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.
Click to expand...
Click to collapse
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.

sliding_billy said:
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.
Click to expand...
Click to collapse
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?

Vanschtezla said:
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?
Click to expand...
Click to collapse
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).

sliding_billy said:
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).
Click to expand...
Click to collapse
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?

Vanschtezla said:
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?
Click to expand...
Click to collapse
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img

sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!

Vanschtezla said:
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!
Click to expand...
Click to collapse
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
Click to expand...
Click to collapse
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.

sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.
Click to expand...
Click to collapse
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.

Vanschtezla said:
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.
Click to expand...
Click to collapse
I do not use that module, but it definitely sounds like it could be an issue since you weren't actually boot looped and were able to remove it. I try to keep my module use minimal (and use well vetted ones only) to avoid wondering whether they are the root cause of issues when they happen. Best of luck. Just glad you are up and running.

sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Are you on Android 11 and have root?

Zehlek said:
Are you on Android 11 and have root?
Click to expand...
Click to collapse
No, this was OT from the original thread title when the question was asked about 10.

sliding_billy said:
No, this was OT from the original thread title when the question was asked about 10.
Click to expand...
Click to collapse
Sorry to stay OT, but since you mentioned EX kernel, does using it also not hide the unlocked bootloader in our "new and improved" SafetyNet world? I'm one of those for whom everything is still working so far--Pay, banking apps, device is certified, etc. I'd hate to lose all that, though, because I'm not going to unroot. I guess if I have to I can use Pay on my watch and use the banks' Web sites instead of their apps.