Database Info

[GUIDE][PAGE PLUS] Easy Method To Flash Boost Moto G To Page Plus w/ Voice, MMS + 3G

I stumbled across this method while I was trying to flash my Boost Moto G over to Page Plus the traditional way with DFS/CDMA Workshop. I was having some trouble with it and ran into some issues flashing CM11 and bootlooping so I ended up needing to flash back to stock firmware. I decided to give the stock Verizon G firmware a try, hoping it wouldn’t brick my brand new phone, and it works beautifully. Everything works including stock OTA programming so there’s no need to mess around too much with flashing tools (except for one or two easy steps). A big plus to this method is the 3G data settings/keys get programmed properly OTA so you don’t need a donor phone or to pay someone $$ to flash it for you. It’s a little bit of a process but if you can follow the steps properly it’s fairly easy. Note: These are just the steps I took to make this work. Some may not be necessary but follow them anyway if you aren’t 100% sure of what you’re doing.
Edit: I've tested PAC ROM and Pink Kernel after flashing the Verizon firmware and voice and 3g still work and the rom is stable so far so most custom ROMs that work with the boost moto g should be fine to flash.
Disclaimer:
I am not responsible for anything you do. If you brick your phone or it explodes, don’t blame me. This method was tested by me and worked for me but if you choose to follow this guide you do so at your own risk. If you’re not somewhat technically savvy or are very unsure about any of the steps below please have someone else help you or consider paying for a flash.
Edit (3/16): If you end up with a bootloop/brick please try to flash the stock Boost firmware again as this should bring your device back. You can get version 4.3 here and version 4.4.2 here.
Requirements:
Your Phone’s MEID Activated With Page Plus
Unlocked Bootloader (See Motorola Bootloader Unlock Site)
Minimal ADB and Fastboot
DFS Demo
Verizon Stock Firmware Image (Check your "Android version" under Settings -> About Phone)
> Android 4.3
> Android 4.4.2
> Firmware Flashing Guide (Written for version 4.3, see below for an additional step for 4.4.2 and automated scripts that are safer to use)
Motorola USB Drivers
Your Phone’s MSL/SPC Code (From Boost Activation or MSL Reader App)
Edit: For activating your MEID with Page Plus I recommend going through Kitty Wireless. They currently have a promotion going where you'll receive a free "The $12" plan with any new activation or port in and the service is free as well.
Steps:
1) Go to the Boost Mobile website and activate your phone. You can do this without actually paying for the first month. The only reason we do this is to get the MSL/SPC code for your phone that is listed on the last page of the activation process. Make sure you save this code somewhere safe. Now I did the Hands Free Activation on my phone, and I don’t think you really need to, but it can’t hurt so I’d suggest you do it as well.
Edit (3/16): Apparently it's not necessary to OTA activate with Boost before flashing your phone so you can simply install this MSL Reader on your phone to get your SPC code without activating with Boost. Copy the apk to your SD card and then open and install it with a file manager or push it from your PC with "adb install SPCUtility.apk".
2) Unlock your bootloader. Go to Motorola’s bootloader unlocking site and follow their instructions. They tell you to install the Android SDK but it can be a large download so just get the Minimal ADB and Fastboot zip as that’s all you need to complete this process. Make sure you install the Motorola USB drivers as instructed because we’ll need them later on for DFS.
3) Now we need to reset your phone’s SPC to “000000” so Verizon OTA programming will work properly. You’ll need to start your phone in Fastboot mode (power off then hold the volume down and power button together until you boot into a system menu) then select the “BP Tools” option in that menu. This will boot your phone with the diagnostic port needed for DFS enabled. If the drivers fail to install automatically you’ll need to manually install them by going into Device Manager, finding the one with the red X called “Motorola QC Diagnostic Interface”, right-clicking and selecting “Update Driver Software…”, clicking “Browse my computer for driver software” then “Let me pick…”, choose the device type “Ports (COM & LPT)” and click next, then selecting the manufacturer “Motorola” and the driver “Motorola QC Diag Port” from the list. This is the only one we actually need so if there are others with a red X you can leave them as they are. Now, open DFS. Click “Ports” on the top left. Double-click on the port named “Motorola QC Diag Port”. DFS will automatically connect to your phone. Next we need to send the MSL code we got from the Boost activation. Type it into the “SPC” box under the “Ports” button and click the arrow to the left of the box. The log window should show “DEVICE UNLOCKED”. Now go to the “Programming” tab and click “Read” in the SPC section. It’ll show the MSL code you used and you need to change it to “000000” then click “Write”. Finally, click the “Reset” button on the top right and your phone will reboot. Make sure you do this because the changes won’t stick unless you do.
4) The next step is to flash the stock Verizon firmware to your phone. There’s already an excellent guide on that process so just download the Verizon image and follow those instructions.
Edit (3/16): The flashing guide linked here references version 4.3 of the firmware. If you're installing version 4.4.2 following the guide there are additional commands you need to execute. Here are all the commands necessary for 4.4.2:
fastboot flash aboot emmc_appsboot.mbn

This needs to be stickied. Would have gone with a Boost Mobile Moto G if I'd known it was this simple. I'm stuck with a Verizon Moto G.

thanks Heranthius! Super useful info!
Makes me wonder if flashing Verizon firmware is necessary. Or if you could just upload a pageplus /Verizon PRL to your phone and reset your SPC to 000000 and then try the ota programming?
Super interesting! Wish I had the money to buy another to play with!
edit: typos. kinda hate typing on phones at times.
Sent from my XT1031 using Tapatalk

I can say for sure it won't work that way. I tried it that way before I discovered this method. You can get voice and SMS but the way Sprint programs the data settings is completely different from Verizon so you won't get 3G or MMS working properly without manual flashing and a donor phone.

this is exactly what I was going to try out, but you beat me to it I had already changed my SPC to 000000 but my Boost mobile didn't end until yesterday, I was also surprised that no one else had tried this yet either. Thanks for the guide too! Cheers.

Heranthius said:
I can say for sure it won't work that way. I tried it that way before I discovered this method. You can get voice and SMS but the way Sprint programs the data settings is completely different from Verizon so you won't get 3G or MMS working properly without manual flashing and a donor phone.
Click to expand...
Click to collapse
I see. Thanks again for the post! I got mine working the manual way but had tried so many different things. I had no idea how to write a tutorial. Seems like this could be a simple fool proof way for people!
Sent from my XT1031 using Tapatalk

Heranthius said:
I'd also recommend that you also install CWM/TWRP recovery and root your phone because the Verizon firmware has a ton of bloat pre-installed.
Click to expand...
Click to collapse
So, do you have a CM11 Moto G nightly installed to get away from the bloatware? or just the basic moto g android? also, thanks for this. I was wondering if I could get the OTA to do a few things for me. and yet i'm almost thru the manual way.
glad to see all this work and sharing on the moto g to selectel and pageplus

@cedarknoll - No problem, this was my first attempt at writing a guide too. I just wanted to make sure everyone knows there's a really easy way to do this without wasting $35 on a professional flash or spending hours manually flashing. There's definitely a lot of research to do when trying to flash by hand and I know it took me many hours to get my G set up the way I wanted. Even if you have a working manual flash I would still recommend going with the Verizon firmware because it's less of a hack, you can update your PRL and profile OTA if necessary, and most importantly for me the voicemail notifications work as intended so you don't need the Voicemail Notifier apk from Viper's thread.
Sent from my Page Plus Moto G using Tapatalk

I followed this guide to the letter. I got it to activate with talk and text, but no data. Looks like it still needs manual tweaking after the fact - which I will do this weekend.

@Flinkly - Right now I'm just running the stock Verizon rom. All I did was use Rom Toolbox to freeze all of the bloat apps. Like I said in the OP, the first time I flashed CM11 I had a bootlooping issue and I haven't had time yet to try and sort it out. I love this phone though so far and I hope some devs start coming out with Verizon roms soon. The Moto G is amazing for the price and one of the best prepaids available right now I think.
Sent from my Page Plus Moto G using Tapatalk

@micallen - That's odd. When you look in the DFS settings did it write any of the Verizon information under Data and Mobile IP? What version of Android are you on? I did the OTA update to 4.4.2 before flashing my phone. Also, did you do the Boost hands free activation before flashing the Verizon firmware? I read somewhere in another thread that you may need to do that in order to unlock/make writable the NV items for the data settings.
Sent from my Page Plus Moto G using Tapatalk

Heranthius said:
...and most importantly for me the voicemail notifications work as intended so you don't need the Voicemail Notifier apk from Viper's thread.
Click to expand...
Click to collapse
that's some super good info to know!! That apk doesn't seem to work on the moto g anyway. I think most people are using the youmail app as an alternative. Even some of the paid flashers just put you mail on there for people.
Sent from my XT1031 using Tapatalk

Nice job man!
Sent from my XT907 using Tapatalk

Heranthius said:
@micallen - That's odd. When you look in the DFS settings did it write any of the Verizon information under Data and Mobile IP? What version of Android are you on? I did the OTA update to 4.4.2 before flashing my phone. Also, did you do the Boost hands free activation before flashing the Verizon firmware? I read somewhere in another thread that you may need to do that in order to unlock/make writable the NV items for the data settings.
Sent from my Page Plus Moto G using Tapatalk
Click to expand...
Click to collapse
4.2.2
I tweaked the settings (couldn't wait) in DFS and have 3G now. 1.3 down and 1.0 up. Thanks for the guide !

Nice method, I don't have a moto g with me at the moment but I am wondering if only some of the images from verizon package need to be flashed.
Is only:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
required? the other image seemed more related to just the android system, recovery and booting. I'l be nice if someone that had a boost motog with them could test out which ones are actually required.

@micallen - Awesome, I'm glad it worked for you. You're welcome! Could you post the settings you had to tweak so people trying this method can know what they need to change in DFS? When I flashed my phone I had to tweak the "Primary & Secondary HA Address" and "Min HA & AAA SPI set" boxes on the "Mobile IP" tab.
Sent from my Page Plus Moto G using Tapatalk

@imkey - I think you need to flash the whole system because it's the setup/activation apk of the rom that actually programs the data settings and that's why you need the one from the Verizon firmware in order to OTA program the 3G settings successfully.
Sent from my Page Plus Moto G using Tapatalk

OK I'm a noob at this and this is where I'm stuck any help would be greatly appreciated The next step is to flash the stock Verizon firmware to your phone. There’s already an excellent guide on that process so just download the Verizon image and follow those instructions.
It won't let me open up mfastboot. It just flashes and disappears
I have all the files in falcon_boost_user_4.3_14.10.0Q3.X-84-9_11_release-keys-cid9.xml folder. I just can't figure out how to load the V Firmware on this phone. I'm actually surprised I got this far LOL I have the phone in "fastboot mode" and I'm here in .cmd mode F:\MOTO G\Minimal ADB and Fastboot>

@blueyzfr6 - I'm not near my computer right now but I can try to help from memory. It sounds like you have the Boost firmware downloaded from the "boost" in that folder title. You need to check what version of android you have under settings -> about phone and download the Verizon firmware for that version. It'll either be 4.3 or 4.4.2 and the 4.4.2 one is called "Blur_Version.173.44.20.falcon_cdma.Verizon.en.US" on the download page. Once you get that and extract it there should be a .bat file inside the folder with the firmware title as the file name (I think). Open it in notepad (right click -> edit) and after the line that says "%fastboot% reboot-bootloader" add "pause" on a new line then save it. Double click the bat file to run it. If you get an error that it can't find fastboot.exe there's a sub-folder in there that has fastboot.exe and 2 .DLL files. Copy those into the folder with the .bat file and run it again. Your phone should reboot right away and the console window will say press any key to continue. Wait for the phone to get back into the fastboot menu then press enter. Now it should flash all the image files and when your phone reboots you should have the Verizon firmware and then just perform the activation steps as instructed.
Sent from my Page Plus Moto G using Tapatalk

Thank you so much for this mini-guide. I followed it all and everything seems to work until activating. I did DL the regular verizon firmware, not the Blue one. Don't know what that is for or the difference. I live out of reception, so it's a bit more challenging for me to see what works. I drove to a place with reception, tried to activate it (while showing roaming) and it failed to activate it. I did have the phone already activated on Boost so am not sure if this actually needs to happen. I did submit an ESN change and it went through, though when i checked the ESN verification, it came back "Unknown"
More to come once I try making a phone call and try the internet.

FRD-AL10 / Full Stock Rom needed

Hey Guys,
can somebody upload a full-zip from Honor FRD-AL10.
I damaged my micro-SD and lost all my backups.
Actually I am on FRD-AL10C00B135.
I know there is B136 available, but I don't get it offer.
Also I found out, other things are not working well.
I would like to do a full reset, which won't work via erecovery.
Thanks a lot for help!

[email protected] said:
Hey Guys,
can somebody upload a full-zip from Honor FRD-AL10.
I damaged my micro-SD and lost all my backups.
Actually I am on FRD-AL10C00B135.
I know there is B136 available, but I don't get it offer.
Also I found out, other things are not working well.
I would like to do a full reset, which won't work via erecovery.
Thanks a lot for help!
Click to expand...
Click to collapse
http://pan.baidu.com/share/home?uk=403023305#category/type=0
Sent from my HUAWEI VIE-L29 using XDA Labs

Baidu is full of bloatware and b*s, I have uploaded this file to Mega, hope this is the one you are looking for.
FRD-AL10_C00B135_Firmware_China_Nonspecific_Android 6.0_EMUI 4.1_05013LBP.zip
https://mega.nz/#!ZgU22BYa!FP8UYXghy0dXxOYFeSf4BKdlF5_8AbVMKQ0ONkV5VpQ

jerryhou85 said:
Baidu is full of bloatware and b*s, I have uploaded this file to Mega, hope this is the one you are looking for.
FRD-AL10_C00B135_Firmware_China_Nonspecific_Android 6.0_EMUI 4.1_05013LBP.zip
https://mega.nz/#!ZgU22BYa!FP8UYXghy0dXxOYFeSf4BKdlF5_8AbVMKQ0ONkV5VpQ
Click to expand...
Click to collapse
Many thanks.
This helped me!
Baidu die Not Start my download, yesterday.

[email protected] said:
Many thanks.
This helped me!
Baidu die Not Start my download, yesterday.
Click to expand...
Click to collapse
Baidu is notorious for its download software for big files. If you have problems with that, you can install Firefox and a plugin called User Agent Switch, switch your Firefox user agent to IE3.0 and visit baidu again, then you can use download software, like IDM to download big files freely, without its b*s download manager...

jerryhou85 said:
Baidu is full of bloatware and b*s, I have uploaded this file to Mega, hope this is the one you are looking for.
FRD-AL10_C00B135_Firmware_China_Nonspecific_Android 6.0_EMUI 4.1_05013LBP.zip
https://mega.nz/#!ZgU22BYa!FP8UYXghy0dXxOYFeSf4BKdlF5_8AbVMKQ0ONkV5VpQ
Click to expand...
Click to collapse
Hi,
I am not a dev and my knowledge on flashing and rooting is only from reading posts. Can I ask for a little advice and maybe instructions? Is it possible the rom from link can help with my situation described below?
I bought honor 8 frd al10 from china. The sim doesn't initiate. I firstly loaded android wear from play store to pair with my Huawei Watch. A message popped up saying 'this phone was flashed with unsupported config for companion. you must reflash it as either signed/user or unsigned/userdebug'. I tried to get help from seller but that's no use and they referred me to xda. They say my rom is EU. In the settings, the build is FRD-C900B120. IMEI and MEID are showing as unknown. There is no Baseband version showing. I am not an expert but I know this ain't right. After watching some of the videos, I used ADB to get to fastboot. It says device unlocked. This is where i get stuck and don't know what else to do. I simply want this phone to work as it is intended to. Help, please.
Edit: I forgot to add that reset to factory settings does not work. goes to 13% and says failed.
Also, when I type in a code in dialler to get product ID to get bootloader unlock code from Huawei, nothing happens so I am stuck if the bootloader is not unlocked.
There is no OEM unlock option in the dev options.

ptwarecki said:
Hi,
I am not a dev and my knowledge on flashing and rooting is only from reading posts. Can I ask for a little advice and maybe instructions? Is it possible the rom from link can help with my situation described below?
I bought honor 8 frd al10 from china. The sim doesn't initiate. I firstly loaded android wear from play store to pair with my Huawei Watch. A message popped up saying 'this phone was flashed with unsupported config for companion. you must reflash it as either signed/user or unsigned/userdebug'. I tried to get help from seller but that's no use and they referred me to xda. They say my rom is EU. In the settings, the build is FRD-C900B120. IMEI and MEID are showing as unknown. There is no Baseband version showing. I am not an expert but I know this ain't right. After watching some of the videos, I used ADB to get to fastboot. It says device unlocked. This is where i get stuck and don't know what else to do. I simply want this phone to work as it is intended to. Help, please.
Edit: I forgot to add that reset to factory settings does not work. goes to 13% and says failed.
Also, when I type in a code in dialler to get product ID to get bootloader unlock code from Huawei, nothing happens so I am stuck if the bootloader is not unlocked.
There is no OEM unlock option in the dev options.
Click to expand...
Click to collapse
It looks like your phone and your ROM are in some twisted status: they are not match.
If you really use AL10 from China, there is a method to fully restore your phone to original status (AL10 original ROM). But I have to remind you the risk first, backup all your contacts to PC/GoogleContacts/Exchange before you proceed.
If you are ready, go to this post below, follow the instructions on 2nd post.
http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039
1. Download AL10 stock rom from my Mega link.
2. Extract necessary files using method above.
3. Follow the rest of instructions.
Now you fully go back to Stock AL10 phone as when it was sold in China and you can start to work from there.
If you don't like China stock ROM, what you can do is Debrand/Rebrand your phone which means, in simple, you change some parameters in your phone, to let your phone and ROM thinks it is from some other region, like EU/ME.
You can find details about Debrand/Rebrand method and video guide in following 2 posts:
http://forum.xda-developers.com/honor-8/development/tool-srk-tool-huawei-bootloader-root-t3470823
http://forum.xda-developers.com/honor-8/how-to/vdo-guide-unlock-bootloader-twrp-root-t3472584

jerryhou85 said:
It looks like your phone and your ROM are in some twisted status: they are not match.
If you really use AL10 from China, there is a method to fully restore your phone to original status (AL10 original ROM). But I have to remind you the risk first, backup all your contacts to PC/GoogleContacts/Exchange before you proceed.
If you are ready, go to this post below, follow the instructions on 2nd post.
http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039
1. Download AL10 stock rom from my Mega link.
2. Extract necessary files using method above.
3. Follow the rest of instructions.
Now you fully go back to Stock AL10 phone as when it was sold in China and you can start to work from there.
If you don't like China stock ROM, what you can do is Debrand/Rebrand your phone which means, in simple, you change some parameters in your phone, to let your phone and ROM thinks it is from some other region, like EU/ME.
You can find details about Debrand/Rebrand method and video guide in following 2 posts:
http://forum.xda-developers.com/honor-8/development/tool-srk-tool-huawei-bootloader-root-t3470823
http://forum.xda-developers.com/honor-8/how-to/vdo-guide-unlock-bootloader-twrp-root-t3472584
Click to expand...
Click to collapse
Wow. First of all, thank you kindly. Looks like a load of work. I will try it and I really appreciate your help and your time.
The device is AL10 as per box/back of the device itself. There is nothing on this phone I would care to loose. Its like this straight out of the box. I don't mind what software I am using as long as I can make calls, use internet, pair my watch, download apps from play store (i understand this may be the issue with Chinese rom). I think what seller was intending to do is the debranding to make it EU.
If you don't mind, I will contact you (quote) if I encounter issues on the way.

ptwarecki said:
Wow. First of all, thank you kindly. Looks like a load of work. I will try it and I really appreciate your help and your time.
The device is AL10 as per box/back of the device itself. There is nothing on this phone I would care to loose. Its like this straight out of the box. I don't mind what software I am using as long as I can make calls, use internet, pair my watch, download apps from play store (i understand this may be the issue with Chinese rom). I think what seller was intending to do is the debranding to make it EU.
If you don't mind, I will contact you (quote) if I encounter issues on the way.
Click to expand...
Click to collapse
Most HUAWEI's phones come with Google Play Services installed, what you need is Google Play Store, if I didn't remember it wrong.
From what I read, a proper debrand should never put your phone in a mess up status, but I haven't done that myself. If you can take time, maybe can study that SRK tool and debrand it yourself. Anyway, now you know you will have the final restore weapon.

jerryhou85 said:
It looks like your phone and your ROM are in some twisted status: they are not match.
If you really use AL10 from China, there is a method to fully restore your phone to original status (AL10 original ROM). But I have to remind you the risk first, backup all your contacts to PC/GoogleContacts/Exchange before you proceed.
If you are ready, go to this post below, follow the instructions on 2nd post.
http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039
1. Download AL10 stock rom from my Mega link.
2. Extract necessary files using method above.
3. Follow the rest of instructions.
Now you fully go back to Stock AL10 phone as when it was sold in China and you can start to work from there.
If you don't like China stock ROM, what you can do is Debrand/Rebrand your phone which means, in simple, you change some parameters in your phone, to let your phone and ROM thinks it is from some other region, like EU/ME.
You can find details about Debrand/Rebrand method and video guide in following 2 posts:
http://forum.xda-developers.com/honor-8/development/tool-srk-tool-huawei-bootloader-root-t3470823
http://forum.xda-developers.com/honor-8/how-to/vdo-guide-unlock-bootloader-twrp-root-t3472584
Click to expand...
Click to collapse
I am either doin something wrong or this is not fixable.
I've tried and force update by putting update.app into dload on internal storage on phone. updating stopped after 3 % failed and asked to reboot.
I've tried reboot in bootloader and in adb typed 'fastboot flash recovery recovery.img' which i first extracted from update.app. I get: sending recovery OKAY, writing recovery FAILED <remote: command not allowed>

ptwarecki said:
I am either doin something wrong or this is not fixable.
I've tried and force update by putting update.app into dload on internal storage on phone. updating stopped after 3 % failed and asked to reboot.
I've tried reboot in bootloader and in adb typed 'fastboot flash recovery recovery.img' which i first extracted from update.app. I get: sending recovery OKAY, writing recovery FAILED <remote: command not allowed>
Click to expand...
Click to collapse
It feels like your phone is not properly unlocked or somehow relocked, maybe you should try to unlock your phone again.
Here is the post for your reference:
http://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946
You may have troubles in finding these in your phone according to your previous post, try the code below.
1. Your phone serial number (this can be found in Settings -> About -> Status)
open dial pad and enter *#*#2846579#*#*, should be some options called "board basic info", and then "others" (I translate from Chinese website, maybe not accurate)
Click to expand...
Click to collapse
2. Your phone IMEI1 (this can be found in Settings -> About -> Status)
*#06#, if you have dual sim, key in main IMEI/MEID
Click to expand...
Click to collapse
3. Your phone product ID (to find this, open the dialler and enter *#*#1357946#*#*)

jerryhou85 said:
It feels like your phone is not properly unlocked or somehow relocked, maybe you should try to unlock your phone again.
Here is the post for your reference:
http://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946
You may have troubles in finding these in your phone according to your previous post, try the code below.
1. Your phone serial number (this can be found in Settings -> About -> Status)
2. Your phone IMEI1 (this can be found in Settings -> About -> Status)
3. Your phone product ID (to find this, open the dialler and enter *#*#1357946#*#*)
Click to expand...
Click to collapse
Thank you again.
The last is not possible as it returns nothing at all. I'll attempt Huawei live chat support on Monday in hope they can help with unlock code.
First two are printed on the box and the back of phone. There is also a sticker on the back of it with Chinese writing and some combination of letters and numbers. I doubt they are the product ID.

ptwarecki said:
Thank you again.
The last is not possible as it returns nothing at all. I'll attempt Huawei live chat support on Monday in hope they can help with unlock code.
First two are printed on the box and the back of phone. There is also a sticker on the back of it with Chinese writing and some combination of letters and numbers. I doubt they are the product ID.
Click to expand...
Click to collapse
If you can take a picture of them and post it here, maybe I can help, since I'm Chinese.

the best thing to do is getting a someone backup without efs and restore . ( just rename one folder and replace phone serial no .

Romiui said:
the best thing to do is getting a someone backup without efs and restore . ( just rename one folder and replace phone serial no .
Click to expand...
Click to collapse
Hi,
Thank you, although as previously, my knowledge is basic, practice even less. If you are able to instruct, I will give it a try.

jerryhou85 said:
If you can take a picture of them and post it here, maybe I can help, since I'm Chinese.
Click to expand...
Click to collapse
That's the box and back. I also added the message from launching android wear and settings screen

ptwarecki said:
That's the box and back. I also added the message from launching android wear and settings screen
Click to expand...
Click to collapse
listen lets fix things one by one !
First Problem is : This phone has been flashed with an unsupported configuration for companion
u should be rooted other wize this cant be fixed .
Install Rootexplorer.apk
navigate to system / build prop . open it with text editor and change this line
ro.build.type=userdebug
to
ro.build.type=user
Save and restart . this issue will go .
if u still need more things to do inform me .

Romiui said:
listen lets fix things one by one !
First Problem is : This phone has been flashed with an unsupported configuration for companion
u should be rooted other wize this cant be fixed .
Install Rootexplorer.apk
navigate to system / build prop . open it with text editor and change this line
ro.build.type=userdebug
to
ro.build.type=user
Save and restart . this issue will go .
if u still need more things to do inform me .
Click to expand...
Click to collapse
I also have a china version of a 128GB FRD AL10 its all working fine but i would like to go to a europe ROM if i can? the seller said Huawei told him if he flashed the device it would break and not work with an EU ROM? i cant set encryption and this is an issue for me as i need it for my work email to work. i also have quite a lot of Chinese text still on some areas, any help greatly appreciated

hi, you can install a European rom instead of the Chinese version in the FRD-AL10? Best regards

Hey, got the same question as albertazzi65 and cwpaters, can I install another ROM on the Al10? And will that enable another bands fot lte?

[ROOT] [N9600] Verizon Full Rooting Guide + Detonator [WIFI Calling etc]

PREWARNING
THIS GUIDE IS !!ONLY!! FOR N9600 (INTERNATIONAL Snapdragon Model)
DO NOT ATTEMPT ON SPRINT, VERIZON, T-MOBILE, AT&T, OR ANY OTHER US (United States) MODEL PHONE.
BEWARE!! N960U or N960U1 HAS A LOCKED BOOTLOADER WHICH CAN NEVER BE UNLOCKED!
IF YOU ATTEMPT TO ROOT ON ANY US MODEL, YOU WILL BRICK YOUR PHONE!
If you have an N9600 international snapdragon model, please proceed. If not, read for your pleasure or future consideration but DO NOT attempt on a US model.
This guide can also be useful for N960F or N960FD international Exynos models, but you would have to change some things like use the right links.
==================================================================================================
Intro Notes:
I REPEAT: THIS GUIDE IS !!ONLY!! FOR N9600 (INTERNATIONAL Snapdragon Model)
If you have an N9600 international snapdragon model, please proceed. If not, read for your pleasure or future consideration but DO NOT attempt on a US model.
After much thought, research, reading, and contemplation, between Note 8, Galaxy S9+, and Note 9, I have decided on the Note 9.
Out of the available options for rooting, there are the devices, N960F, N960FD, and N9600.
Of course, N960F N960FD are Exynos. Unfortunately, these will not work on Verizon, so I would have to switch to T-Mobile. To stay on Verizon it would have to be N9600.
Ultimately, I decided on N9600. Why? Because with Detonator, I can root the N9600 on Verizon, and it's the only model that I can use on Verizon fully rooted. (There is a partial root on N960U, the US Snapdragon variant, but the root is only partial and will have bugs or may not wok.) I could root with a partial root the Note 8 US version, but it is not that much cheaper and it would only be a partial root, so I decided on N9600.
You can root fine on the Exynos versions, but you could not use Detonator for WIFI calling and other features on Verizon.
Rooting Guide
0. Battery must be above 82% before rooting.
1. Root N9600 using TWRP method (Beta)
PLEASE READ ALL INSTRUCTIONS THERE FOR ROOTING.
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-note9-snapdragon-t3845536
(Official XDA Magisk Install Guide, don't follow directly just reference)
2. RMM State Fix (Prevent "Prenormal")
IMMEDIATELY after getting into TWRP, flash the RMM-State_Bypass_Mesa_v2.zip (linked below).
If you do not, then you will get locked out for 7 days in the event you flash anything or flash a new OS or downgrade to Oreo, etc.
You have to do this EVERY TIME you flash something to prevent RMM state to going to "Prenormal" which means wait 7 days before you can flash any non-samsung firmware.
3. How to fix: Stuck on Prenormal and didn't bypass, OEM Unlock missing
You might be stuck because you didn't do the RMM bypass above. In this event, you will be blocked from flashing custom binaries including TWRP. The only thing you will be able to flash is original Samsung firmware.
How to bypass now? There are two solutions for solving Prenormal RMM state. I have done both successfully. There is a third but it rarely seems to work (date hack, available at many sites.)
METHOD 1: Long way around. Wait 7 days.
First wipe your whole device again and reflash your original OS in ODIN. If you don't do this then it's possible that after 7 days, OEM unlock will not show up.
Now wait 7 days.
Do not reboot your device, just for good measure. I did reboot my device, several times, and it still appeared after 7 days and a reboot. Don't know if you'll have the same luck.
The second time after turning on OEM Unlock, however, when it wiped my device, I did NOT reflash the whole OS again. And, after 7 days again, it did NOT show up.
METHOD 2: I waited 7 days, but no OEM unlock! Solution: Chimera application for windows. NOT FREE!
I was tired of waiting so I decided to try it, and it worked.
Activate Developer options
Activate USB Debugging (in Developer Options)
DISABLE "Verify apps via USB" (in Developer Options)
Go to https://chimeratool.com/
Buy the 3 days trial.
Download after paying in PayPal.
Install full application and all drivers. Don't customize it just install full.
Put your phone into Download mode
Turn off phone.
Hold Bixby & Volume Down
Plug phone into PC.
Press volume up at prompt. Download mode will be activated.
Now in Chimera application in Windows it will find your phone.
Choose the option "UNLOCK".
Choose the sub option, "RMM Unlock".
SUCCESS!! NO WAITING!! OEM Unlock activated. Worth every penny in my opinion (because it wasn't too many pennies).
Proceed to install TWRP and DO NOT FORGET TO INSTALL RMM BYPASS AFTER EVERY SINGLE FLASHING OF ANYTHING!!
4. After rooted, flash Detonator
File: Verizon EFS/CSC Detonator: Detonator v3 for Oreo 8.1 (linked in file list below)
(There is no Detonator for Pie on Verizon as of this writing, only Oreo)
0. Download DETONATOR_XXX_OREO_VZW_EFS-CSC_vx.x_INT_TEKHD.zip to your phone.
Maybe just copy to your SD card, easiest way.
In order to flash detonator, in TWRP select every box on the Mount screen (OTB will not be available unless you have one connected, but everything else).
Backup all partitions via TWRP.
Then go to Install (in TWRP) and flash the zip file for Detonator which applies to you. (Do NOT flash right after flashing a ROM!; First boot ROM at least one time… then go back to TWRP and flash Detonator)
After you successfully flash detonator and there are no errors, now if you want to remove the Verizon boot screen now go ahead and flash (through Install screen in TWRP) the Samsung BootAnimation zip on the Detonator website. This will replace your boot with the stock black samsung boot.
After doing these, please remember to flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Detonator features (from the website):
*With the Verizon Detonator you will get:
– VoLTE, Wifi-Calling /4G/LTE/ONLINE services & features.
– AdAway
– AppLock
– OperaMax (VPN/Data Saving)
– Caller ID & Spam Protection
– Phone and messaging Firewall
– Floating Messages
– Screencast/ScreenRecorder
– Ultra Data Saving Mode
– When booting for the first time… turn off “Confirm Network Connection” Under Settings -> Connections… (*IF AVAILABLE*) (see image below)
Changelog for Verizon Detonator:
v3 – CSC Features added / Wi-Fi Calling APK Update
vPRE-2.2 – Smart Manager Device Security Fix
vPRE-2.1 – Added Mobile Data Toggle to Power Menu.
vPRE-2 – Fixed XML Code / Features Added
vPRE-1 – Initial Release. (Test Phase)
NOTE: After installing Detonator, WIFI Calling button disappeared. I confirmed that I do NOT have WIFI calling, sadly. It doesn't work.
Test it by turning on airplane mode, then connecting to WIFI, then try to make a call. You will get a popup with option to turn on WIFI calling. If you try, it will result in an error, "Unable to activate WIFI Calling at this time, please try again later".
There is presently no solution I am aware of, but maybe someone else knows how, search the forums. Also maybe it has to do with the particular OS I decided to use. I could start over from scratch and try again, but it would be a lot of work and I am out of time for now.
Keep in mind you have to activate on Verizon (see below) before trying to make a call.
5. ACTIVATE ON VERIZON:
Activating on Verizon cannot be done through their site, it will result in an error that your device is incompatible, so don't bother with that.
0. In order to activate you just need an already working SIM card.
Activate a new Verizon SIM card on your PREVIOUS device.
If you need an excuse say you need it for your new phone and YOU will activate it yourself right in the store. Then say it's not working let's try activating on my old phone first.
After the new SIM is working on your OLD phone, leave the store and go home. Now, at your leisure remove the SIM from your old phone and now insert it into your N9600.
Reboot. Now you will be activated on Verizon! (NOTE: YOU MUST ALREADY HAVE DONE DETONATOR, FOLLOW ALL STEPS ABOVE FIRST.)
After you do the rooting below, you'll get messages from SecurityLogAgent saying "security error your device was modified, reboot to revert the changes". You can eliminate this by going into Titanium Backup and FREEZE the following:
SecurityLogAgent
Security policy updates
Software update
Configuration Update
6. Magisk Manager
Boot into phone. If you see Magisk Manager it means you are rooted, probably.
To check it open the Magisk Manager app on your phone.
Feel free to update Magisk. I updated it in the app to 19.3 for Magisk and the installer (flashed from the zip in TWRP) is 7.2
Tap to start safetynet, and accept all prompts.
Reboot
Test if rooted by installing Titanium Backup. If it asks for SuperSU permission then Grant, and it means you are rooted!
7. After rooted, install Xposed
Download xposed from the link in the files section below. If you have a Note 9 on Oreo 8.1 then your file is the SDK 27 for Arm64.
In TWRP, flash the zip file.
Now flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Backup if desired.
Boot your phone.
Go to the xposed links and get the APK file for xposed. This will be the app you use to manage xposed.
WARNING:
One or more of the settings in the xposed module GravityBox [O] causes bugs and removes your Verizon compatibility. In order to solve the error "No SIM card inserted" (but it is inserted!), what you have to do is to go back into TWRP, and do all steps for the Detonator instructions that I wrote above (it will NOT wipe your device, so don't worry). Once you re-flash Detonator, your Verizon will work again and the SIM card message will be gone.
WARNING 2:
There was another xposed module that caused a similar issue but worse. The issue in reference is you get a black screen at the lock screen but nothing can come up but the reboot menu. You cannot get into the phone. I was about to consider having to factory reset before I solved the issue. Since the issue was an xposed module, then the solution is to:
Download the most recent arm64 xposed uninstaller .zip file from here: https://dl-xda.xposed.info/framework/uninstaller/
Boot into TWRP, flash the xposed uninstaller zip.
Clear the cache and dalvik cache like it suggests using that button on the screen there.
Now flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Reboot into your phone, your problem is now solved!
Finally, go into Xposed Installer and find the Module that was causing the issue, long-press on it and choose uninstall. I know you want to keep it, but it's too bad, you can re-download it later, you will be unable to simply unselect it. You have to uninstall it.
Now you can go back into TWRP and reinstall xposed.
Last step: flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Files Needed
ODIN: https://odindownload.com/
- Odin 13.3.1
TWRP: https://forum.xda-developers.com/devdb/project/?id=29220#downloads
- TWRP_3.2.3-0_N9600_beta3.tar.md5
- boot.img (he recommends to use this, see tutorial)
- Encryption disabler.zip
MAGISK: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- Magisk 16.7 19.3 (can I use latest version 19.3? Answer: YES, I used 19.3 without any problems.)
USB DRIVERS: https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
- SAMSUNG_USB_Driver_for_Mobile_Phones.zip
BYPASS RMM STATE: https://forum.xda-developers.com/showpost.php?p=75360965
- RMM-State_Bypass_Mesa_v2.zip
DETONATOR: http://tekhd.com/detonator-o/
- DETONATOR_N9_OREO-8.x_VZW_EFS-CSC_v3_INT_TEKHD.zip
DIRECT LINK (VZW v3): https://androidfilehost.com/?fid=11410963190603842742
MIRROR: https://mega.nz/#!cP52EYKS!L9Oc7nihQ2RoXddZPAPXCPdVLvzhXq3VZtaZXGzBtDQ
(link is was down but I have the file which I uploaded for you: [EDIT: TekHD link is back up now! The domain was expired but I spent some time on the phone with GoDaddy trying to renew their domain for them, maybe the dev was able to see it since I told them to reach out to him specifically. GoDaddy refused to let me donate to renew his domain for him. Again update it appears the site is down again. But not expired this time, it just says "pageok". I do have all the data from that site so I will upload it for the community sometime.]
XPOSED (for Oreo 8.1): https://dl-xda.xposed.info/framework/sdk27/arm64/
- xposed-v90-sdk27-arm64-beta3.zip
XPOSED UNINSTALLER (to fix a bad module. See Warning 2.): https://dl-xda.xposed.info/framework/uninstaller/
- xposed-uninstaller-20180117-arm64.zip
OREO 8.1 FIRMWARE (for downgrade):
- N9600ZHS1ASB1 / N9600OWA1ARL5 (N9600 8.1 Oreo 2019-02-01 Chile) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/CHL/download/N9600ZHS1ASB1/259310/
- N9600ZHU1ARG6 / N9600OWA1ARG6 (N9600 8.1 Oreo 2018-07-01 Dom Rep) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/CDR/download/N9600ZHU1ARG6/231741/
- N9600ZHU1ARG6 / N9600OWE1ARG6 (N9600 8.1 Oreo 2018-07-01 Ecuador) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/ALE/download/N9600ZHU1ARG6/231755/
** These three files have been removed from sammobile as of today 2019-05-25, because they were there yesterday. You can still view directly but they will no longer show on the page for the N9600 because sammobile is no longer showing any Oreo (8.0, 8.1) firmwares for the N9600 on their site, only Pie firmwares (9). It's likely these will be removed soon, so I will upload mirrors to the firmwares once they are finished downloading.
(NOTE: DO NOT download firmware N9600ZHS1ASA7_N9600OWT1ARK1_SAM because it will after initializing forcefully change your boot branding to a bright baby blue screen with Movistar carrier branding instead of a normal black samsung boot screen. This will be removed by re-flashing so it's harmless, just annoying. Instead use the above linked. So far I have only tested N9600ZHS1ASB1 above which is fine, it is on the Clara carrier and installs minimal carrier bloat which can be removed after rooting. I linked the other two which I will try as they use pre-August 2018 firmware so hopefully I can get the OEM Unlock to show since I didn't know about the RMM state fix before flashing Pie down to Oreo.)
UPDATE:
This guide is now completed and released. The steps are fully working to get your N9600 working on Verizon.
Someone asked me if regular calling works if they don't have WIFI. Of course. Your phone will fully work on Verizon as normal. In addition to fully working, WIFI calling also works (for some firmwares).
UPDATE 2:
DEAR EVERYONE:
Sorry it took so long for me to upload the files. It appears that TekHD website is now dead for good. It's been down for months. So, since I already had downloaded all the content from the website, including the website pages themselves, I'm now uploaded everything from TekHD for your use. I'm also including all of my rooting files for your use and enjoyment.
Will update the links here when the uploads complete. Enjoy!
EDIT: Here's the link!
https://mega.nz/#F!UbZFSAwC!FObELw39ZmADygAJOFVlyw
-

[moved content from here into original post]
[reserved]

I used a exynos S9+ and I'm using a note 9 exynos on Verizon. You don't need to flash anything because if you use shortcutmaster to bring up Ims settings, with root of course, you can enable all you need.

But you don't have wifi calling or several other things right?

I also had to do a RMM state flash. But I didn't know and now I am blocked from doing anything for a week after downgrading OS. Wish someone would have told me ahead of time. The hacks to change date to bypass and re-enable OEM lock DOES NOT WORK. Trying many things, wasted my whole saturday needlessly.

I finally got the OEM unlock to show.
STEPS:
1. Using Odin flash the whole OS from sammobile. I used 8.1 which is compatible with Detonator.
2. During setup, DO NOT CONNECT TO INTERNET.
3. Choose a date some time in the past like a month or even a year ago. I chose a year ago.
4. finish setup disabling everything.
5. General Management → Date and time. DISABLE Automatic date and time.
6. Enable developer options.
a. Settings > About phone
b. tap seven times on ‘Build number’
7. Settings > Developer options > DISABLE Auto update system
8. It will not work unless you also log into a samsung account.
a. Connect to internet now.
b. Cloud and accounts > Accounts > Add account
c. Sign in or create a new Samsung account.
d. You have to log in and add the account, go back and it should say added.
9. DISCONNECT FROM INTERNET
10. Go to date and time. Choose a date in the future. I chose a few months in the future.
11. Settings > Software update > tap on Download updates automatically (it will error because not connected. It's fine. Don't connect!)
12. REBOOT
13. Settings > Developer options. The OEM unlock option should be visible now.
I think the above is what I did. I might have the order above wrong because I tried so many times I can't remember if that's the exact order. I think it is, but if it doesn't work try a few different ways and eventually you'll get it.
EDIT: When I tried again, above does not work so I must not have remembered what I did perfectly, OR for some reason it just didn't work the second time.

[.]

Before I bust out the Type-C cable, I must ask, will this work on the Sprint variant?

Any plan to ad sprint to the list

eastside08 said:
Before I bust out the Type-C cable, I must ask, will this work on the Sprint variant?
Click to expand...
Click to collapse
NO!!! BEWARE, N960U or N960U1 HAS A LOCKED BOOTLOADER.
IF YOU ATTEMPT TO ROOT ON ANY US MODEL, YOU WILL BRICK YOUR PHONE!
The ONLY Snapdragon model that can be rooted is the INTERNATIONAL N9600. I specifically bought the N9600 for this. This N9600 has an unlocked bootloader.
I was planning on running Detonator on the Oreo 8.1 since the developer TekHD has not yet developed a Detonator for Pie on Verizon. Plus, I read that many people prefer Oreo over Pie. Moreover, Oreo will have more dev support than Pie since Pie is still very new.
I am still working on this so will continue progress updates.
Right now I am stuck because I didn't know about the RMM State so I am stuck on Prenormal, which means 7 days waiting. I had gotten the OEM unlock to show because I was going to disable and re-enable OEM unlock, and when I proceeded it wiped, and then changed to Prenormal preventing from installing TWRP again.
If I had known ahead of time, I could have flashed the RMM fix zip while I had TWRP on there and could have avoided this fiasco. If I get OEM unlock to show again then I will use that to avoid future lockouts.
Right now I am downloading a July 2018 version of Oreo 8.1. I tried flashing several Oreo 8.1 and that is easy with Odin, but could not get the OEM unlock to show up again no matter what I tried. According to this page** (link below), the method of switching the time doesn't work on pre- August 2018 firmwares. That's not entirely accurate as I got it to show up the first time, but I may be stuck now.
So in an effort to try anything, I am downloading and will flash the earlier version of 8.1 from July. Then will try the date method to try to get it to show up. Hopefully it works.
** NOTE: link from above is https://www.thecustom droid.com/prenormal-rmm-state-on-samsung-galaxy-guide/ (remove the space between custom and droid)

For future reference, guides go in the guides section, not development.

Update: I can't get OEM unlock to show up and ran out of time. So, I have to take the long way around and wait a week for it to show up. So, I'll be back on Sunday if OEM unlock shows up.

Im guessing this trips knox ?

why put 'Verizon Full Rooting Guide' when rooting has nothing to do with carriers.
the guide is to get verizon csc on a n9600. you should change the way you named the thread if you dont want to get a gazilion questions from n960u uers.

i sure am confused.
are you able to root a international note9 and use it on verizon network in the usa, or not?
i know elliwigy is working on getting root for a specific model of note9, i think for the usa unlocked or verizon locked model, but it's not useable on stock firmware yet.

UPDATE:
After 7 days, a reboot, and pressing check for updates (but not updating), then checking for the OEM unlock, it did in fact show up.
Unfortunately, enabling OEM unlock also factory resets your phone which AGAIN puts the 7 day lock - which is f*ing ridiculous.
So now I have to wait ANOTHER 7 days before proceeding, so that Prenormal will be able to go to Normal and I can flash TWRP and custom binaries.
Will update again in another week.

bober10113 said:
why put 'Verizon Full Rooting Guide' ... if you dont want to get a gazilion questions from n960u uers.
Click to expand...
Click to collapse
Please note the tag [N9600], if N960U users fail to read the full title, that's their fault. I put all the disclaimers in red anyway just in case, so they can know.
This indeed is about using an international N9600 on Verizon in the USA. I am still working on this and as per my previous post, in another week once the 7 day wait period is over again so I can finish the root and flashing, then I will continue to update about how to get the N9600 working on Verizon.
It is worth noting that you are required to root the N9600 in order to use Detonator.
siriom said:
Im guessing this trips knox ?
Click to expand...
Click to collapse
The answer to this is Yes. It trips Knox. You cannot root without tripping Knox.
dumbfone said:
are you able to root a international note9 and use it on verizon network in the usa, or not?
i know elliwigy is working on getting root for a specific model of note9, i think for the usa unlocked or verizon locked model, but it's not useable on stock firmware yet.
Click to expand...
Click to collapse
The answer to this is hopefully yes, and I have known others to get the N9600 working on Verizon. But I have to wait another week before I can proceed, so please check back next week to see my progress and additional instructions.

Hello everyone,
I have wonderful and amazing news. I have completed fully rooting my Note 9 N9600 and also getting it fully working on Verizon. I am updating the original post now with the details and remaining steps.
It's worth noting that after the second 7 days, OEM unlock would NOT show up. I waited hours more, but still no luck. Instead, I used an application called Chimera which I actually paid for in order to get OEM unlock to finally show up, and it worked.

Update: See the above completed and updated guide.

zxzxzxzxzxzxzxzxzx said:
Update: See the above completed and updated guide.
Click to expand...
Click to collapse
so the way to do it is just flashing the latest detonator?
http://tekhd.com/detonator/
(apparently with full wifi calling support too..)
http://tekhd.com/detonator-o/#vzwdetonator
(or go to detonator telegram channel for possibly modded comunity version...rumor i heard)
implicitly, people probably already know how to root by following the steps outlined from the snapdragon thread..

[STOCK ROM] Stock Android 10 ROM

Hi i found official stock rom
mirrors.lolinet.com/firmware/moto/troika/official/RETAIL/TROIKA_RETAIL_10_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Will this work on the reteu devices (being from a different channel)?

FelixNevorsky said:
Hi i found official stock rom
mirrors.lolinet.com/firmware/moto/troika/official/RETAIL/TROIKA_RETAIL_10_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
What Does The Letter QSB Mean?
In The Previous Rom Are PSB Or PSBS

takoa said:
What Does The Letter QSB Mean?
In The Previous Rom Are PSB Or PSBS
Click to expand...
Click to collapse
My guess is that QSB is for Android 10 (it was called Q for some time). And PSB is 9.0 (aka Pie)

I mean the letters sbs and sb. thanks

takoa said:
I mean the letters sbs and sb. thanks
Click to expand...
Click to collapse
ummmm......Stable build.....maybe

Was Anyone able to root this version?

Wintershade said:
Will this work on the reteu devices (being from a different channel)?
Click to expand...
Click to collapse
Yes, it should. It's been already tested here on the forum with pretty good results. So yeah, I'd say it will. But if you're not in a hurry, maybe you can wait for a bit longer to get the official build for RETEU.

Channel Signification Firmware
Is a list exist for channel signification for https://mirrors.lolinet.com/firmware/moto/troika/official/
or a way to knows the signication ?
RETEU = Europe
RETUS = USA
RETCA = Canada
RETRU = ???
etc ...
Compatibility Variant / Firmware
Is exists a thumb rule for compatibility firmwares in between XT2013-1, XT2013-2, XT2013-3, XT2013-4.
Actually, I have a XT2013-4 device and I would like flash another firmware variant.
Thanks

RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.

arsradu said:
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
Click to expand...
Click to collapse
Thanks for your answer, I have a XT2013-4 and I can confirm that's is a Single SIM.
For info, on my XT2013-4 I tried two différents android 10 firmware made for XT2013-2 and they both runs very smooth but time will tells if there's any issues
- TROIKA_RETAIL_10_QSBS30.62-17-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
- XT2013-2_TROIKA_RETRU_10_QSB30.62-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
/Regards

arsradu said:
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
Click to expand...
Click to collapse
There's an interesting channel listing on a XDA TREAD "Identify Software Channel"
https://forum.xda-developers.com/moto-z-play/help/identify-software-channel-t3555285
/Thanks

Gypsy said:
There's an interesting channel listing on a XDA TREAD "Identify Software Channel"
https://forum.xda-developers.com/moto-z-play/help/identify-software-channel-t3555285
/Thanks
Click to expand...
Click to collapse
that is very good to know. thank you!

Gypsy said:
Thanks for your answer, I have a XT2013-4 and I can confirm that's is a Single SIM.
For info, on my XT2013-4 I tried two différents android 10 firmware made for XT2013-2 and they both runs very smooth but time will tells if there's any issues
- TROIKA_RETAIL_10_QSBS30.62-17-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
- XT2013-2_TROIKA_RETRU_10_QSB30.62-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
/Regards
Click to expand...
Click to collapse
Hi..
I have one action with xt2013-4 too.. and wait update to android 10 for long time.. ?
Will you give me an information if my phone model may get OTA android 10? If yes when? If you know.. ?
Otherwise, if I want to flash android 10 to my device, will you give me a guidance how to flash with another ROM model TROIKA, but it compatible with my device like you information before..
Thanks for the feedback
?

zaqiezsbelelzsinski said:
Hi..
I have one action with xt2013-4 too.. and wait update to android 10 for long time..
Will you give me an information if my phone model may get OTA android 10? If yes when? If you know..
Otherwise, if I want to flash android 10 to my device, will you give me a guidance how to flash with another ROM model TROIKA, but it compatible with my device like you information before..
Thanks for the feedback
?
Click to expand...
Click to collapse
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.

arsradu said:
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Click to expand...
Click to collapse
arsradu said:
@zaqiezsbelelzsinski
I can't and more to @arsradu's answers, but just in case you decide to unlock your bootloader for whatever reason, it voids your warranty., there's the link:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Good luck, if you have any difficulty, please ask!
Click to expand...
Click to collapse
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.[/QUOTE]

One thing I forgot to mention: simply requesting the bootloader unlock code will void your warranty. You don't even need to use it. Once you requested it, it's done.
Now, if you're super careful with that security patch I mentioned above, you might not need to request it in the first place, since you might not need to unlock your bootloader in the first place. Cool, huh?
Unfortunately I don't have so much experience with this. And it's not like I have a bunch of Moto One Actions I can test with. I only have my own. ) But in theory, if you don't update/downgrade your security patch, if you only flash ROMs with the exact same security patch, you could (again, this is just a theory, based on my own experience) go from Android 9 to 10 and back, without unlocking the bootloader. Because it looks like it's not the Android downgrade that's causing the issues. It's the security patch downgrade that forces you to unlock the bootloader.
And I wish I had this piece of knowledge before I requested my unlock code. )) But I didn't. So I'm just happy it wasn't for nothing and I learned a lot in the process.

arsradu said:
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.
Click to expand...
Click to collapse
Thank you for the feedback
Yes, I understand about the risk. Many years ago I always flashing my device (Nexus 5) while it was release update, but that was then ?. Now, Maybe I will be waiting till my device get update to android 10.
The problem is, there is no valid information from Motorola especially TROIKA XT2013-4 about update to android 10.
Thanks for your advice about flashing ROM..
Cheers ???

You could try to contact your local Motorola Support team. I don't think they will give you an actual ETA. But maybe they can tell you wether or not there will be an update to Android 10 for this particular model (XT2013-4). I think there should be. I see no reason why this particular model would be an exception. But you could double check that. Just in case.
Logic would suggest that there should be one soon. XT2013-1 and XT2013-2 already got the update. So it would make sense for the "-4" model to follow.
Sent from my motorola one action using Tapatalk

arsradu said:
One thing I forgot to mention: simply requesting the bootloader unlock code will void your warranty. You don't even need to use it. Once you requested it, it's done.
Now, if you're super careful with that security patch I mentioned above, you might not need to request it in the first place, since you might not need to unlock your bootloader in the first place. Cool, huh?
Unfortunately I don't have so much experience with this. And it's not like I have a bunch of Moto One Actions I can test with. I only have my own. ) But in theory, if you don't update/downgrade your security patch, if you only flash ROMs with the exact same security patch, you could (again, this is just a theory, based on my own experience) go from Android 9 to 10 and back, without unlocking the bootloader. Because it looks like it's not the Android downgrade that's causing the issues. It's the security patch downgrade that forces you to unlock the bootloader.
And I wish I had this piece of knowledge before I requested my unlock code. )) But I didn't. So I'm just happy it wasn't for nothing and I learned a lot in the process.
Click to expand...
Click to collapse
@arsradu
I notice you have experience with security patches, tanks you to had shared!
IF I REALLY NEED TO DOWNGRADE MY SECURITY PATCH ! EVEN with all amounts of troubles, IS THERE A WAY doing it?
Thanks

Yu Yutopia (Yu5050) (Sambar) Stock engineering rom, rooted (Android 5.1)

For those interested, this is exactly engineering rom, with added modified patched boot, so it is rooted with magisk. v23
This is the detailed install procedure:
You need to download the following:
1. YU_Yutopia_YU5050_V1_24.12.15 rom, link give below.
2. Qfil tools
3. Qualcomm driver.
How to Flash:​1. Extract All Files From Zip File.,
2. Install Qualcome drivers (search through the web), Install QPST Tool and Run Qfil.exe File
3. Select the flat build option after the tool is open
4 . After that click on the select programmer’s path to browse and select the file “prog_emmc_firehose_8xxx.mbn”.
5. Then click on load.xml and select the “rawprogram0” file.
6. Then select the file patch0.
7. After selecting all the files with the flash tool, the phone has to be connected to the tool
8. For that, turn off the phone and press the Volume Up and Volume Down buttons simultaneously.
9. And then connect the data cable with the phone
10. After connecting, click on the select port in the tool and select Qualcomm HS-USB QDLoader 9008
11. Then click on the download button.
12. Keep the up and down buuton pressed until start downloading some files, the you can remove you fingers.
13. Wait until flashing finishes.
14. After First boot download Magisk apk, (I ve downloaded magisk v23, & its working perfectly).
No need to flash GAPP, its already present. Infact, the bootloader is locked & dont know how to unlock it, there is no option in developer mode to enable unlocking it. The rom is fast, not laggy, battery discharge is very good.
Download link:
1.37 GB file on MEGA
mega.nz
YU5050_SW_V46_User.zip | by kurdiak for Yutopia
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Attached files are screen shots of Qfil file setting & rom.

{Mod edit: Quoted post has been deleted}
I didnt understand what you mean. can you clarify your question.

kurdiak said:
{Mod edit: Quoted post has been deleted}
I didnt understand what you mean. can you clarify your question.
Click to expand...
Click to collapse
Sorry sir a simple typos.... (Due to autocorrect)
Real question...will flashing this firmware with flat building, nullify my phone's imei number.??
More over will i be able to write or rewrite imei on this rooted magisk phone without bootloader unlocked? As given in this procedure(of yu 5050)

CHAMPIONGAMERS said:
Sorry sir a simple typos.... (Due to autocorrect)
Real question...will flashing this firmware with flat building, nullify my phone's imei number.??
More over will i be able to write or rewrite imei on this rooted magisk phone without bootloader unlocked? As given in this procedure(of yu 5050)
Click to expand...
Click to collapse
No it will not nullify imei numbers, but it is safer to back up your imei (although i did not, and i have no problem with imei no.) As it is rooted already, you can do whatever you want. the only problem with this rom is that I could not unlock bootloader.

kurdiak said:
No it will not nullify imei numbers, but it is safer to back up your imei (although i did not, and i have no problem with imei no.) As it is rooted already, you can do whatever you want. the only problem with this rom is that I could not unlock bootloader.
Click to expand...
Click to collapse
Thank you a lot sir for ur kind replay...
Sir please please can u give me an easy procedure to restore or change (qcn) IMEI number if something goes wrong..cause i tried to repair imei of yu4711 through shell terminal but unable to do so without super su....
So please please gimmi a good easy procedure to change or repair imei if something goes weong...thanks in advance sir...and happy rakhi

CHAMPIONGAMERS said:
Thank you a lot sir for ur kind replay...
Sir please please can u give me an easy procedure to restore or change (qcn) IMEI number if something goes wrong..cause i tried to repair imei of yu4711 through shell terminal but unable to do so without super su....
So please please gimmi a good easy procedure to change or repair imei if something goes weong...thanks in advance sir...and happy rakhi
Click to expand...
Click to collapse
I used mobile unkle tools, I had lost my imei on another phone, and I could retain my imei using that tools easily. so if you take a picture shot or write down your number, you can rewrite it again. I dont write my imei no, because i had it on my phone box already written.

kurdiak said:
I used mobile unkle tools, I had lost my imei on another phone, and I could retain my imei using that tools easily. so if you take a picture shot or write down your number, you can rewrite it again. I dont write my imei no, because i had it on my phone box already written.
Click to expand...
Click to collapse
Sir yu 5050 is a qualcomm smartphone...as probably mobile unkle tools won't work...btw can i change the root provider from magisk to supersu without bootloader unlocked??...

CHAMPIONGAMERS said:
Sir yu 5050 is a qualcomm smartphone...as probably mobile unkle tools won't work...btw can i change the root provider from magisk to supersu without bootloader unlocked??...
Click to expand...
Click to collapse
I dont know. The most important thing for me is root, wether its magisk or supersu.
with this rom, my battery issues become much better, it can withstand a good period of time, the rom is smooth.

hello there . my flex ribbon cable appear to be broken . i wonder if someone knows the edl point for this device . thanks