Develop Bugs

Addison_Row_Cust

Bought my Z Play used and have been really enjoying it! Phone came with TWRP + Root. After the November update came out, I flashed everything except baseband and modem, since I didn't want to lose my imei and couldn't find factory images for my device. I'd really like to flash back to 100% stock so I can relock my bootloader, use Android pay, and accept the upcoming nougat update once it arrives.
Looked through all of the factory images I could find on XDA and did a lot of googling, no luck.

Same situation as you are. I can't find that specific ROM.

Lenovo have not released signed images that you can flash and lock your bootloader with. Your device will always have the software flag : modified in the bootloader. Your best option for Android pay is for Alberto97 to include the SafetyNet kernel flag in LOS 14.1

Really_Rekt said:
Lenovo have not released signed images that you can flash and lock your bootloader with. Your device will always have the software flag : modified in the bootloader. Your best option for Android pay is for Alberto97 to include the SafetyNet kernel flag in LOS 14.1
Click to expand...
Click to collapse
Really, I care more about being able to take the upcoming nougat OTA, but this is good info, thank you!

xxBrun0xx said:
Really, I care more about being able to take the upcoming nougat OTA, but this is good info, thank you!
Click to expand...
Click to collapse
If I'm not mistaken, you should still be able to take upcoming OTA's even with an unlocked bootloader.
As long as you have stock recovery + un-root, you should be good in theory.

luciddreamin92 said:
If I'm not mistaken, you should still be able to take upcoming OTA's even with an unlocked bootloader.
As long as you have stock recovery + un-root, you should be good in theory.
Click to expand...
Click to collapse
True, but my baseband currently doesn't match anything else. To get to the November update, I flashed everything except modem from the latest USA factory ROM. Guess I can just do the same thing once someone posts images for nougat.

xxBrun0xx said:
True, but my baseband currently doesn't match anything else. To get to the November update, I flashed everything except modem from the latest USA factory ROM. Guess I can just do the same thing once someone posts images for nougat.
Click to expand...
Click to collapse
Hey guys, to prevent the loss of your precious data (apks, settings and etc), and "enable" ota on your devices, go to Twrp, wipe System, cache and dalvik cache.
After this, flash the firmware of your device via fastboot with the commands above:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
After that, your phone should be able to install ota's.
Cheers!

W3ND31 said:
Hey guys, to prevent the loss of your precious data (apks, settings and etc), and "enable" ota on your devices, go to Twrp, wipe System, cache and dalvik cache.
After this, flash the firmware of your device via fastboot with the commands above:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
After that, your phone should be able to install ota's.
Cheers!
Click to expand...
Click to collapse
Only if there is a factory image available for your device. Otherwise the OTA is going to brick your phone (OTA updates bootloader and modem, wrong modem will break radios, not sure if bootloader is region specific? If so, taking out of region OTA would hard brick you.)

xxBrun0xx said:
Only if there is a factory image available for your device. Otherwise the OTA is going to brick your phone (OTA updates bootloader and modem, wrong modem will break radios, not sure if bootloader is region specific? If so, taking out of region OTA would hard brick you.)
Click to expand...
Click to collapse
Nice addon!
Thx!

Update to this: spoke with a Level 2 Motorola Representative over the weekend. He did not seem to know anything about fastboot or TWRP or bootloader unlock vs sim unlock. I was pretty disappointed, Moto support has been excellent in past experience. He looked up the device by IMEI and told me it was unlocked US version, but had no idea what I was asking after almost an hour of explanation. The Level 1 tech I spoke to spoke pretty broken english. It's possible the baseband for RETUS is ROW_CUST, but I'm not brave enough to try flashing modem and boot.img.
If you're in the same boat, I'd recommend waiting until someone with a RETUS can confirm their baseband.

xxBrun0xx said:
Update to this: spoke with a Level 2 Motorola Representative over the weekend. He did not seem to know anything about fastboot or TWRP or bootloader unlock vs sim unlock. I was pretty disappointed, Moto support has been excellent in past experience. He looked up the device by IMEI and told me it was unlocked US version, but had no idea what I was asking after almost an hour of explanation. The Level 1 tech I spoke to spoke pretty broken english. It's possible the baseband for RETUS is ROW_CUST, but I'm not brave enough to try flashing modem and boot.img.
If you're in the same boat, I'd recommend waiting until someone with a RETUS can confirm their baseband.
Click to expand...
Click to collapse
I would avoid at all cost flashing any modem, bootloader or baseband related bin file. You can freely flash the sparse chunks and boot.img to your heart's content.
Sent from my XT1635-02 using XDA-Developers Legacy app

xxBrun0xx said:
Update to this: spoke with a Level 2 Motorola Representative over the weekend. He did not seem to know anything about fastboot or TWRP or bootloader unlock vs sim unlock. I was pretty disappointed, Moto support has been excellent in past experience. He looked up the device by IMEI and told me it was unlocked US version, but had no idea what I was asking after almost an hour of explanation. The Level 1 tech I spoke to spoke pretty broken english. It's possible the baseband for RETUS is ROW_CUST, but I'm not brave enough to try flashing modem and boot.img.
If you're in the same boat, I'd recommend waiting until someone with a RETUS can confirm their baseband.
Click to expand...
Click to collapse
I'm on RETUS. Baseband is Addison_RETUS_Cust. No ROW.

dandrumheller said:
I'm on RETUS. Baseband is Addison_RETUS_Cust. No ROW.
Click to expand...
Click to collapse
The plot thickens

How to get back to original STOCK ROM?

Hello,
i am currently running Dedrak Essential 1.3.0 which is a kind of 7.0 Stock ROM. But i want to get the orginal Moto-Stock. How to get that? I know there ist a Service Image of 6.0 and i had to do some fastboot/mfastboot actions. But i am not really sure if would this work or brick my device.
Can anyone give me an advice?
thanks
Peter

Just use RSD lite and flash original FW for youe device.
Here you can get 7.1.1 fully stock ROM (retin or retus - I don`t sure)
I flash it to my XT1635-03 and it works just perfect.
P.S. If you have issues with RSD flashing - just use fastboot with the next commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot

acutally i need reteu. Well i will look for it.
Thanks so far

Keep in mind if you already upgraded your bootloader from the official July Patch and patch you'll hard brick your Moto Z play if you upgrade and downgrade. I'd advise you to flash the ROM and not the actual firmware.

i dont have that july patch. Dedrak was still on January.... so its 7.0 and it this was also the las official update i got changed to dedrak.
So it should work.

Dchoi229 said:
Keep in mind if you already upgraded your bootloader from the official July Patch and patch you'll hard brick your Moto Z play if you upgrade and downgrade. I'd advise you to flash the ROM and not the actual firmware.
Click to expand...
Click to collapse
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
When I get OTA update it will look something like:
Code:
F1: STOCK FIRMWARE V.1
O2: OTA UPDATE V.2
F1O2F1O2O2O2O2F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O2O2O2O2F1F1O2O2O2O2F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Then I downgrade via fastboot and it should look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Why hardbrick?

Zixione said:
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
When I get OTA update it will look something like:
Code:
F1: STOCK FIRMWARE V.1
O2: OTA UPDATE V.2
F1O2F1O2O2O2O2F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O2O2O2O2F1F1O2O2O2O2F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Then I downgrade via fastboot and it should look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Why hardbrick?
Click to expand...
Click to collapse
I honestly can't give you a solid answer. If you look at other threads you can find out why. It definitely has something to do with the bootloader.

Dchoi229 said:
I honestly can't give you a solid answer. If you look at other threads you can find out why. It definitely has something to do with the bootloader.
Click to expand...
Click to collapse
Every other thread (that I found) just states as axiom - "downgrading will hardbrick" without clarification - why. But wouldn't
Code:
fastboot flash bootloader bootloader.img
solve all that "bootloader related stuff"?

Zixione said:
Every other thread (that I found) just states as axiom - "downgrading will hardbrick" without clarification - why. But wouldn't
Code:
fastboot flash bootloader bootloader.img
solve all that "bootloader related stuff"?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492

Dchoi229 said:
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Click to expand...
Click to collapse
Already seen this. The only useful bits of info about downgrading\bricking cause is, again, just statement, that "some updates/flash packages do not allow downgrading", but again without much clarification how exactly some data, sent to flash memory, will block itself from being written:
The thing with failing updates/flash packages is that they usually fail because they do not allow downgrading - even if they allow downgrading of some sort (e.g. OS), they may limit downgrading the second stage bootloader, the signed GPT (partitioning table) etc.
Click to expand...
Click to collapse
Many thanx, anyway !:good: I just need deeper explanation, will search onward myself.

Zixione said:
Already seen this. The only useful bits of info about downgrading\bricking cause is, again, just statement, that "some updates/flash packages do not allow downgrading", but again without much clarification how exactly some data, sent to flash memory, will block itself from being written:
Many thanx, anyway !:good: I just need deeper explanation, will search onward myself.
Click to expand...
Click to collapse
yea.. sorry I'm not much of a developer. You can definitely look inside that thread and see that there are deeper explanations. I believe after a certain update (april security patch i believe) the bootloader is upgraded and when downgrading to a official firmware (MM 6.0.1) the updated bootloader will not work correctly and hard brick the Moto z play. I dont play with the bootloader anymore after hearing of this. Your best option is just to flash stock roms. Best of luck to you my friend. :good:

I am in a similar position wanted to go back to stock deodexed N but I can't because it is rooted with super su and I want to root with magisk which is not possible. Or I think as much anyway.

Zixione said:
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
<snip>
Why hardbrick?
Click to expand...
Click to collapse
As I understand it, the hardbrick comes not when you downgrade, but when you use OTA updates to upgrade your device. The likely reason for this appears to be that the OTA only verifies your system version and whether the system, OEM and other partitions are of the same patch level. It does not necessarily check whether your bootloader and GPT are matching your system before patching. Also, downgrading may not downgrade your bootloader (and sometimes doesn't, where it's blocked by a 'security downgrade' warning), leaving you with a mismatched system. Looking through the OTA scripts for the Moto G4 updates, for example, the checks are mainly: is this the correct build to flash over, and are the system partitions unmodified? If yes to both, then it proceeds to flash and then copies over the bootloader files for that OTA. I've not seen an OTA check to verify your bootloader is of the correct patch level (if someone knows better, feel free to correct me).
To use your illustration:
Code:
F1: STOCK FIRMWARE [B]V.2[/B]
O2: OTA UPDATE V.3
F1O3F1O3O3O3O3F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O3O3O3O3F1F1O3O3O3O3F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
This is after the OTA update to V3, taken after the OTA to V2. We assume that boot is the bootloader (the secondary bootloader, including the TrustZone and other bootloader partitions), and system includes the kernel and other system components.
If you downgrade to V1 from V3:
Code:
F1: STOCK FIRMWARE V.1
F1O3F1O3O3O3O3F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
You'll notice your bootloader has not downgraded (which can occur in fastboot), since the bootloader blocks you from downgrading your bootloader, especially in the newer stock firmwares. You'll also notice that your system is V1 though. Thus, though your system is V1, your bootloader is V3.
If you take an OTA update to V2, therefore, the OTA appears to look at your system, think your device is all V1 (including your bootloader), and proceed to patch to V2. Of course, as your bootloader is V3, then there is a high likelihood of the V2 OTA corrupting your V3 bootloader, leading to a hard brick.
We've seen this with the Moto Z Play (from the 7.1.1 to 7.0), Moto G4/Plus (downgrading from the June 2017 patch), and other Moto devices. Though this behaviour isn't restricted to Moto devices, it seems to more prevalent after the April/May/June 2017 stock patch updates (possibly to stop you reopening the Motorola bootloader vulnerability?). Thus, as others have suggested, do not downgrade if you can, or be careful and do not flash OTA updates. Try to flash the same stock ROM as what was on your device previously.
Hope that explains things a little more clearly.

Whenever I try use any command on fastboot, i get this message
Code:
(bootloader) slot-count : not found
(bootloader) slot-suffixes : not found
(bootloader) slot-suffixes : not found

RoboticBuddy said:
Whenever I try use any command on fastboot, i get this message
Code:
(bootloader) slot-count : not found
(bootloader) slot-suffixes : not found
(bootloader) slot-suffixes : not found
Click to expand...
Click to collapse
I think those messages are normal, as the Moto Z Play doesn't appear to have the A/B partition system found on the Pixel. Thus, those messages are more informational as there's no separate slot to flash to.

echo92 said:
I think those messages are normal, as the Moto Z Play doesn't appear to have the A/B partition system found on the Pixel. Thus, those messages are more informational as there's no separate slot to flash to.
Click to expand...
Click to collapse
Now I'm getting that I cannot write to /data.

echo92 said:
As I understand it, the hardbrick comes not when you downgrade, but when you use OTA updates to upgrade your device.
[snip]
Hope that explains things a little more clearly.
Click to expand...
Click to collapse
Your explanation adds up missing bits and makes everything much more clear to me. Thank you very much!

im not much of a programmer or anything but I can tell you this. my MZP was down for a month due to this. I was on 7.0 custom rom I think either on the april or January patch, wanted the ota for 7.1, sooooooo I figured I would just downgrade to 6 and accept the ota....... Well that was not wise. If I recall upgrading changed the bootloader which is not able to be downgraded so there was a mismatch and the phone could not boot itself to anything. I would advise double and triple checking the threads. before you hard brick. Luckily for that particular problem there is now a method to recover it. just wanted to give you as much info as possible

Zixione said:
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
When I get OTA update it will look something like:
Code:
F1: STOCK FIRMWARE V.1
O2: OTA UPDATE V.2
F1O2F1O2O2O2O2F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O2O2O2O2F1F1O2O2O2O2F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Then I downgrade via fastboot and it should look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Why hardbrick?
Click to expand...
Click to collapse
Where did you get these hex values so I can check my own?

These values are just part of schematic illustration (as a version numbers are) and doesn't meant to have any meaningful sense.

Flash AOSP

Hi
I have Xperia XZ2 Compact with Android 9 with unlocked bootloader. was trying to flash a ROM built from AOSP. I followed this official Sony's instruction: https://developer.sony.com/develop/...build-instructions/build-aosp-android-p-9-0-0. I have just added a field in xml that is used in Information about phone activity. The build was succesfull. In the end I get an information: "Your device is corrupt. It can't be trusted and will not boot". I did wiped the data, system and dalvik before flashing in TWRP. What the hell is going on?

kiubaz said:
Hi
I have Xperia XZ2 Compact with Android 9 with unlocked bootloader. was trying to flash a ROM built from AOSP. I followed this official Sony's instruction: https://developer.sony.com/develop/...build-instructions/build-aosp-android-p-9-0-0. I have just added a field in xml that is used in Information about phone activity. The build was succesfull. In the end I get an information: "Your device is corrupt. It can't be trusted and will not boot". I did wiped the data, system and dalvik before flashing in TWRP. What the hell is going on?
Click to expand...
Click to collapse
Flashed OEM?
Deactivated vbmeta?

MartinX3 said:
Flashed OEM?
Click to expand...
Click to collapse
Yes, OEM was already flashed to the one from XperiFirm.
MartinX3 said:
Deactivated vbmeta?
Click to expand...
Click to collapse
How to do that?

kiubaz said:
Yes, OEM was already flashed to the one from XperiFirm.
How to do that?
Click to expand...
Click to collapse
That's the wrong OEM.
Please follow my instructions in the SonyAOSP thread.
Or step 7 of your linked guide from sony.

So now the following steps to do:
1) download oem.img from https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tama/
2) wipe data/cache/system,
3) from package built from AOSP do this
fastboot flash boot out/target/product/<device>/boot.img
fastboot flash system out/target/product/<device>/system.img
fastboot flash vendor out/target/product/<device>/vendor.img
fastboot flash userdata out/target/product/<device>/userdata.img
and lastly
fastboot flash oem img_from_point_one.img ?

kiubaz said:
So now the following steps to do:
1) download oem.img from https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tama/
2) wipe data/cache/system,
3) from package built from AOSP do this
fastboot flash boot out/target/product//boot.img
fastboot flash system out/target/product//system.img
fastboot flash vendor out/target/product//vendor.img
fastboot flash userdata out/target/product//userdata.img
and lastly
fastboot flash oem img_from_point_one.img ?
Click to expand...
Click to collapse
Just follow my sonyaosp thread fastboot instructions

No files found in android 9 stock firmware https://androidfilehost.com/?w=files&flid=288319.
Allright that's original firmware but what if I want to make my own changes in AOSP? Thats the point.

Unlocked T-mobile to international/root?

T-mobile unlocked my 7T, but is it as simple as using the tool to flash international firmware on it? Do I need to do anything else? Can it than be treated like international and rooted?

trix4rix said:
T-mobile unlocked my 7T, but is it as simple as using the tool to flash international firmware on it? Do I need to do anything else? Can it than be treated like international and rooted?
Click to expand...
Click to collapse
This has been asked at least 3 times a week. Please do a quick search before posting.
Sent from my [device_name] using XDA-Developers Legacy app

OuncE718 said:
This has been asked at least 3 times a week. Please do a quick search before posting.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Where? Don't see this question at all.

trix4rix said:
Where? Don't see this question at all.
Click to expand...
Click to collapse
Check this link. There was other post about the same question and I guess the mod removed them because it's asked so often.
https://forum.xda-developers.com/showthread.php?t=3994931
Sent from my [device_name] using XDA-Developers Legacy app

OuncE718 said:
Check this link. There was other post about the same question and I guess the mod removed them because it's asked so often.
https://forum.xda-developers.com/showthread.php?t=3994931
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, I really don't think you're right here, the only question asked was "can I unlock my 7t from T-mobile"
My question is "it's unlocked, can I use the tools for the non-T-mobile version."
While both questions mention "unlocking" and "T-mobile" they are different questions.

trix4rix said:
T-mobile unlocked my 7T, but is it as simple as using the tool to flash international firmware on it? Do I need to do anything else? Can it than be treated like international and rooted?
Click to expand...
Click to collapse
You need to unlock your bootloader with OnePlus. Takes 1 week after submitting.

That's still not answering the question. Ok, apparently takes 1 week to unlock the boot loader. Is it as simple as using the tool to flash international firmware? Does he need to do anything else?
Wow horrible reading comprehension around here.

pbassjunk said:
That's still not answering the question. Ok, apparently takes 1 week to unlock the boot loader. Is it as simple as using the tool to flash international firmware? Does he need to do anything else?
Wow horrible reading comprehension around here.
Click to expand...
Click to collapse
After unlocking sim and bootloader, you're going to download the latest global ota from OnePlus site or here on xda (I don't think latest is up on op site yet). Then unzip ota. Then dump the payload.bin file. It'll give you boot.img, vendor.img, system.img, etc.
Now flash every file by fastboot flash file.img on both slots
Example:
Fastboot flash dtbo_a dtbo.img
Fastboot flash dtbo_b dtbo.img
Do this with every file in bootloader mode except for system, vendor, product, and tz.img.
Now fastboot reboot fastboot
You'll be in a fastbootd mode now with language selection. Do not select anything.
Now enter fastboot commands for the remaining files in slots a and b
Example:
Fastboot flash system_a system.img
Fastboot flash system_b system.img
Fastboot flash product_a product.img
Etc.. with system, product, and vendor imgs. Do not flash tz.img at all.
Now fastboot -w to wipe data
Fastboot reboot. Done.
Well not actually.. after you boot, go to settings>system>system update. Do a local update (top right drop-down) and update with the latest ota zip you already have. Now update with that and you'll reboot and be good.
If you don't flash the ota zip through system update, you won't have data..

dpryor88 said:
After unlocking sim and bootloader, you're going to download the latest global ota from OnePlus site or here on xda (I don't think latest is up on op site yet). Then unzip ota. Then dump the payload.bin file. It'll give you boot.img, vendor.img, system.img, etc.
Now flash every file by fastboot flash file.img on both slots
Example:
Fastboot flash dtbo_a dtbo.img
Fastboot flash dtbo_b dtbo.img
Do this with every file in bootloader mode except for system, vendor, product, and tz.img.
Now fastboot reboot fastboot
You'll be in a fastbootd mode now with language selection. Do not select anything.
Now enter fastboot commands for the remaining files in slots a and b
Example:
Fastboot flash system_a system.img
Fastboot flash system_b system.img
Fastboot flash product_a product.img
Etc.. with system, product, and vendor imgs. Do not flash tz.img at all.
Now fastboot -w to wipe data
Fastboot reboot. Done.
Well not actually.. after you boot, go to settings>system>system update. Do a local update (top right drop-down) and update with the latest ota zip you already have. Now update with that and you'll reboot and be good.
If you don't flash the ota zip through system update, you won't have data..
Click to expand...
Click to collapse
need help dumping the payload.bin from the international 10.0.6. I finally got my unlock_code.bin. is there a link to the international global 10.0.6 with the payload.bin extracted?

KMHartford said:
need help dumping the payload.bin from the international 10.0.6. I finally got my unlock_code.bin. is there a link to the international global 10.0.6 with the payload.bin extracted?
Click to expand...
Click to collapse
Search Google for payload extractors. There's a bunch of free ones for PC/Mac you can find. I use a Mac so I have a python script I found that I use in terminal to extract all the images from the bin file.

KMHartford said:
need help dumping the payload.bin from the international 10.0.6. I finally got my unlock_code.bin. is there a link to the international global 10.0.6 with the payload.bin extracted?
Click to expand...
Click to collapse
after unlocked with unlock_code.bin from oneplus
Converted. Installed oneplus usb drivers. downloaded Indian 10.0.6 rom, extract. Run the the flash-all.bat with the phone in fastboot. Let the flash-all completely finish. After reboot download global 10.0.6 rom. Copy to the root. Go to system update, local update install global 10.0.6 rom. After its finished conversion complete 10.0.6 international rom on T-Mobile HD1907.

Stock Rom for Motorola G stylus retail

Moto G Stylus USA variant RETUS: XT2043-4
Build Number/DownloadChangelog
QPR30.80-33 Initial Firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Moto G Stylus Retail variant:
Build Number QPR30.80-58 Initial Firmware
https://mega.nz/folder/FxQgTAra#AjfOWfMcZhc_gCDAIAZflw
New build June 2,2020
SOFIAP RETAIL QPRS30.80.58.3
https://mega.nz/file/CBpWgQ7R#...EvQJavU_fVEVU8nnfqI_tXwrRiXRaM
Steps to Install Moto G Stylus Stock Firmware:
Before installing, make sure to follow the pre-requirements and the tools or drivers to download and install properly on your computer.
Pre-Requirements:
This ROM file is only supported for Moto G Stylus (sofiap) device. Don’t try it on other devices.
You will require a PC/Laptop and a USB cable to connect your device with the computer.
Download and install the latest*Motorola USB Drivers*for Windows/MAC PC.
Download and extract the*ADB fastboot tool*on your PC for the Fastboot Method.
Keep your device charged up to 60% at least for a smoother process.
We recommend you to take a*complete backup of device data without root*before doing anything.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot reboot bootloader
Sent from my moto g stylus using Tapatalk

Have you made any changes to the ROM? Did you root it, etc?
PS - No one can access the mega link without the decryption key.

This pure stock if u brick
Sent from my moto g stylus using Tapatalk

dafunk60 said:
Have you made any changes to the ROM? Did you root it, etc?
PS - No one can access the mega link without the decryption key.
Click to expand...
Click to collapse
I fix the link
Sent from my moto g stylus using Tapatalk

Missing command line
fastboot flash super super.img_sparsechunk.14
is missing and needs to be added.
My touch screen quit working when I patched boot.img with Magisk and I was able to go back to a working stock ROM after I flashed this stock ROM and added the addition line.
Thanks for the link.

I need help. I was able to get my bootloader unlocked but after flashing with magisk and patching boot.img my touchscreen no longer works. I cannot figure out how to unbrick it. Any help would be appreciated. Thanks

tatsunn said:
I need help. I was able to get my bootloader unlocked but after flashing with magisk and patching boot.img my touchscreen no longer works. I cannot figure out how to unbrick it. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
U need to find out your stock firmware at
Sent from my moto g stylus using Tapatalk

If I skip the "erase user data" section, will that keep all my files saved on the device? What about apps, will it keep them?

shootinappsinthealley said:
If I skip the "erase user data" section, will that keep all my files saved on the device? What about apps, will it keep them?
Click to expand...
Click to collapse
I ran every command except "erase user data" and all my apps and files were on there and still logged in. However the default apps were all installed back on

New build just dropped
QPRS30.80-58-3

burnsky05 said:
New build just dropped
QPRS30.80-58-3
Click to expand...
Click to collapse
I cannot find this build on lolinet. Also, what is the difference between RETUS and RETAIL? I am on Google FI

burnsky05 said:
New build just dropped
QPRS30.80-58-3
Click to expand...
Click to collapse
Share the link
Sent from my moto g stylus using Tapatalk

god_of_wisdom said:
Share the link
Click to expand...
Click to collapse
Not sure how to share a link, I got the download via the phone and the Lenovo software tool.

The software allow u to download the stock Rom to keep that stock Rom in the safe place use mega or Dropbox to upload it and share link after u done.
Sent from my moto g stylus using Tapatalk

https://mega.nz/file/CBpWgQ7R#B96or6XhHApEnEvQJavU_fVEVU8nnfqI_tXwrRiXRaM
SOFIAP_RETAIL_QPRS30.80_58_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
Hope this helps.

burnsky05 said:
https://mega.nz/file/yIo1zTKS
SOFIAP_RETAIL_QPRS30.80_58_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
Hope this helps.
Click to expand...
Click to collapse
It's asking for a decryption key before downloading.
Edit: It's working now, thanks burnsky05!

burnsky05 said:
https://mega.nz/file/CBpWgQ7R#B96or6XhHApEnEvQJavU_fVEVU8nnfqI_tXwrRiXRaM
SOFIAP_RETAIL_QPRS30.80_58_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
Hope this helps.
Click to expand...
Click to collapse
Can u unlock the bootloader with this one bc the code I have is weird I think the bootloader is mess up on my end
Sent from my moto g stylus using Tapatalk

god_of_wisdom said:
Can u unlock the bootloader with this one bc the code I have is weird I think the bootloader is mess up on my end
Click to expand...
Click to collapse
I haven't tried yet I was just wanting to share what downloaded when I connected my phone to the Lenovo software.

Alright so this is everything that I have from the folder that Lenovo downloaded. Really hope I'm not exposing any information that shouldn't be shared.
https://mega.nz/folder/fRhwVYLa#8BLNgNxriUTA28UVmMDLlg

burnsky05 said:
I haven't tried yet I was just wanting to share what downloaded when I connected my phone to the Lenovo software.
Click to expand...
Click to collapse
Bad news on my end Verizon bootloader won't be unlock
Sent from my moto g stylus using Tapatalk