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.
Related
Hello all.
So, this morning I recieved 2 OTA updates, one was ~ 2MB, the other was around 9MB.
I decided to take them. I knew for a fact that it may break root, that's not an issue, as I will re-root it again.
Before the updates, I was on:
Android Version: 4.0.1
Baseband Version: I9250UGKK7
Kernel: 3.0.1-ge2433f2 [email protected] #1
Build Number: ITL41D.I9250UGKK7
Now, after the updates:
Android Version: 4.0.2
Baseband Version: I9250UGLA4
Kernel: 3.0.8-ggaaa2611 [email protected] #1
Build Number: ITL53F.I9250UGLA4
The thing is, it also broke my TWRP (recovery) and my ability to use NFC.
I was reading up on other forums, and I cannot see anyone having issues with recovery being broken after an OTA.
By broken, I mean no longer the CWM/TWRP, but back to stock android recovery (with the little android laying down, with an open hatch and a red triangle exclamation mark).
So, my question is; is this normal? (after an OTA update), and will installing (flashing) the TWRP maguro 2.2.2.0 image (http://teamw.in/project/twrp2/90) + re-rooting fox the issue?
Alternatively, I think I will just flash JB on the Nexus using efrants guide (http://forum.xda-developers.com/showthread.php?t=1626895) (Thanks!)
Is there a requirement when doing this, I mean can I be on any version of any (maguro/GSM) build? (I am guessing yes)
Thanks!
OTA will replace anything that is not stock.
Beamed from my Maguro
It's rather strange the ota installed since you modified system apps & partitions. It asserts if these are stock before allowing the ota to install.
Sent from my Galaxy Nexus using Tapatalk 2
And yes, software version does not matter.
Beamed from my Maguro
Thanks!
I guess I will flash the takju-jro3c factory 4.1.1 image on my Nexus tonight.
By the way, how important is it to update the bootloader/radios for 4.1.1 flashing?
In the guide that efrant posted, it says that n00bs are supposed to do it (while I am a Android noob, not a Linux noob), I am wondering, is it absolutely imparative that I update it?
And lastly. The flashing, when I run the "fastboot flash xxxx" command, what is the system procesess that interprets these? i.e. if I erase everything, bootloader, recovery, userdata, system, xloader (and so on...), will I still be able to fastboot -> flash?
I am guessing not. I believe (correct me if I am wrong, because I very well may be?) the bootloader loads fastboot, so no bootloader = no fastboot?
I believe fastboot is bootloader mode, I may be wrong on this one though. Fastboot is relatively safe, you won't be able to erase the bootloader and radio.
Beamed from my Maguro
vlambrecht said:
Thanks!
I guess I will flash the takju-jro3c factory 4.1.1 image on my Nexus tonight.
By the way, how important is it to update the bootloader/radios for 4.1.1 flashing?
In the guide that efrant posted, it says that n00bs are supposed to do it (while I am a Android noob, not a Linux noob), I am wondering, is it absolutely imparative that I update it?
And lastly. The flashing, when I run the "fastboot flash xxxx" command, what is the system procesess that interprets these? i.e. if I erase everything, bootloader, recovery, userdata, system, xloader (and so on...), will I still be able to fastboot -> flash?
I am guessing not. I believe (correct me if I am wrong, because I very well may be?) the bootloader loads fastboot, so no bootloader = no fastboot?
Click to expand...
Click to collapse
No need to update bootloader or radios.
And yes, without bootloader access you won't have fastboot access. That's the only part that needs to be operational.
Jubakuba said:
No need to update bootloader or radios.
And yes, without bootloader access you won't have fastboot access. That's the only part that needs to be operational.
Click to expand...
Click to collapse
Actually, many people were having issue trying to run/install stock JB with bootloaders older than LA03, so, while technically not required, I would recommend flashing LC03 (or at least LA03) before trying to flash a stock JB ROM.
vlambrecht said:
Thanks!
I guess I will flash the takju-jro3c factory 4.1.1 image on my Nexus tonight.
By the way, how important is it to update the bootloader/radios for 4.1.1 flashing?
In the guide that efrant posted, it says that n00bs are supposed to do it (while I am a Android noob, not a Linux noob), I am wondering, is it absolutely imparative that I update it?
And lastly. The flashing, when I run the "fastboot flash xxxx" command, what is the system procesess that interprets these? i.e. if I erase everything, bootloader, recovery, userdata, system, xloader (and so on...), will I still be able to fastboot -> flash?
I am guessing not. I believe (correct me if I am wrong, because I very well may be?) the bootloader loads fastboot, so no bootloader = no fastboot?
Click to expand...
Click to collapse
It is the sbl (which is part of the bootloader) that interprets the fastboot commands. I would not ever erase the sbl or xloader partitions on your device, or it's possible you may end up with a brick.
Just a quick question. Say if someone would completely wipe the Nexus (all partitions, xloader, bootloader, etc), how would someone recover that? Is there some JTAG meathod that you can use or ICSP to re-flash the stock partitions using low-level hardware operation? (Essentially reflash the NAND Flash)?
PS: On 4.1.1 now with the help of your guide, thanks efrant!
vlambrecht said:
Just a quick question. Say if someone would completely wipe the Nexus (all partitions, xloader, bootloader, etc), how would someone recover that? Is there some JTAG meathod that you can use or ICSP to re-flash the stock partitions using low-level hardware operation? (Essentially reflash the NAND Flash)?
PS: On 4.1.1 now with the help of your guide, thanks efrant!
Click to expand...
Click to collapse
Well, you could try OMAP Flash. (It is linked to near the end of the first post in the "Basics" link in my signature.) I'm not entirely sure how it works, but based on my limited knowledge, I believe the it uses a driver to communicate directly with the OMAP 4460 chip and flashes (part of?) the xloader and the sbl, which then allows you to use Odin to flash the other images.
EDIT: There must be a JTAG option as well. I'm not very knowledgeable about these things though. AdamOutler would be a better person to ask.
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
This Article Will Guide You to how to relock the bootloader of your moto g5 plus (Indian Variant) It should work on other Variants to but tested only on the indian variant.
Things You Need:-
1.Minimal ADB
2.Moto Stock Rom Link:- (https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)
Download the last file that has brasil in file name
Steps To Relock The Bootloader:-
1.Install Minimal ADB
2.Download And Extract Moto Stock Rom to any folder
3.Open The folder where you extracted the stock rom and copy all file to Minimal ADB folder.
4.Now Connect Your Device In Fastboot Mode
5.Open Minimal ADB And Type each command one by one
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
Then it will restart your Device. And You Will Get Locked Bootloader.
After locking bootloader, flash full Rom to get ota
https://pastebin.com/ZWTaWuyr
This are the commands to flash full rom.
Thanks To Telegram Group for the commands link.
Nirbhay2 said:
This Article Will Guide You to how to relock the bootloader of your moto g5 plus (Indian Variant) It should work on other Variants to but tested only on the indian variant.
Things You Need:-
1.Minimal ADB
2.Moto Stock Rom (Available In The Moto G5 Plus forum)
3.Nothing Else
Steps To Relock The Bootloader:-
1.Install Minimal ADB
2.Download And Extract Moto Stock Rom to any folder
3.Open The folder where you extracted the stock rom and copy all file to Minimal ADB folder.
4.Now Connect Your Device In Fastboot Mode
5.Open Minimal ADB And Type each command one by one
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
Then it will restart your Device. And You Will Get Locked Bootloader.
*Don't Skip Any Command.
Click to expand...
Click to collapse
The process worked I could reblock the bootloader of my G5 Plus XT1680
Knight sparda said:
The process worked I could reblock the bootloader of my G5 Plus XT1680
Click to expand...
Click to collapse
Nice. Means it working for other Variant also
I don't think you will receive OTA updates even after locking the bootloader again.
Sent from my Moto G (5) Plus using Tapatalk
You have forget for flashing Recovery too.
matrixzone said:
I don't think you will receive OTA updates even after locking the bootloader again.
Click to expand...
Click to collapse
After locking bootloader, if u flash the whole rom again then u will be able to get OTA updates as normal. 100% Tested by me
Schrotty35 said:
You have forget for flashing Recovery too.
Click to expand...
Click to collapse
Flash full Rom after locking the bootloader.
After? You mean bevor.
Schrotty35 said:
After? You mean bevor.
Click to expand...
Click to collapse
Yes. After locking the bootloader you can flash full rom.
Nirbhay2 said:
Yes. After locking the bootloader you can flash full rom.
Click to expand...
Click to collapse
Can you elaborate?
Do we need to do something else after executing these commands to get otas
Rajul said:
Can you elaborate?
Do we need to do something else after executing these commands to get otas
Click to expand...
Click to collapse
You have to flash full rom to get ota.
Commands are here:- Taken From Telegram Group.
https://pastebin.com/ZWTaWuyr
Nirbhay2 said:
You have to flash full rom to get ota.
Commands are here:- Taken From Telegram Group.
https://pastebin.com/ZWTaWuyr
Click to expand...
Click to collapse
Now that my bootloader is locked,cqn these commands be executed?
Rajul said:
Now that my bootloader is locked,cqn these commands be executed?
Click to expand...
Click to collapse
Yes
I ran in the rom Brazil latam Mexico did not work, and also tested other roms and to no avail, always asks for the signed system image.
reuber said:
I ran in the rom Brazil latam Mexico did not work, and also tested other roms and to no avail, always asks for the signed system image.
Click to expand...
Click to collapse
You have done something wrong. This method is working 100%. Explain the error. Which build you are trying to flash...?
I am using the stock XT1681-XT1683_POTTER_BRASIL_latam_MEXICO (NPNS25.137-15) and following all the commands and in the end returns the message (still requires signed boot.img) will it be due to my device being Brazilian?
I get same error on my EU Version.
everything works perfectly in indian variant
1.download the brazillian variant of stock rom
2.follow these steps
3.flash whole stock rom using commands posted.
4.you will get ota as soon as you start device
Schrotty35 said:
I get same error on my EU Version.
Click to expand...
Click to collapse
In fact this is not a bug, but a bootloader requirement to flash a signed system image, I think!
---------- Post added at 08:27 PM ---------- Previous post was at 07:40 PM ----------
Rajul said:
everything works perfectly in indian variant
1.download the brazillian variant of stock rom
2.follow these steps
3.flash whole stock rom using commands posted.
4.you will get ota as soon as you start device
Click to expand...
Click to collapse
Should only work then in the Indian variant
reuber said:
In fact this is not a bug, but a bootloader requirement to flash a signed system image, I think!
---------- Post added at 08:27 PM ---------- Previous post was at 07:40 PM ----------
Should only work then in the Indian variant
Click to expand...
Click to collapse
The full rom is already signed.
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Nobody got the same problem? Maybe phone is damaged?
messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse
messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse
1. It's always hard to help without logs. Error codes are too unspecific
2. Check the mount settings, under the partition list there is an option for mounting /system as read only. It has to be disabled for installing custom ROMs.
Found something intresting,when I flash twrp without any problem and boot to system...then again tomorrow recovery via hardbuttons over bootloader there comes stock recovery????what ist that? Not able to go to twrp,only after new flash in fastboot.
Then you didn't flash it but just boot it
Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.
tiago1966 said:
Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.
Click to expand...
Click to collapse
Current firmware is 118-22-2-17! Older builds could lead to downgrade issues!
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.