Hi
While trying to install the Pure rom on my XT1572...I was facing this issue that I couldnt get any network...during the installation I didnt face any issues which I am aware of...but now when I checked it it says both are missing...am not sure what to do now...did I ruin my phone? Is there any way to check what can be done?
1. I had used the adb to install twrp on the device today itself...and then iinstalled everything using it
Doing some more research I found out that my issue might have been due to not selecting read only in twrp...is that a possibility? any workarounds?
You are absolutely right! When I first tried this method I almost lost my device, since when uncheking "system read only" it some how wiped my baseband, and through rsd I was not been able to flash it back... Had to dig a lot in Google to recover it...
So the good way is: unlock bootloader, install systemless SuperSU via fastboot, boot up, go to bootloader, install TWRP by fastboot, boot in it twice, never uncheking read-only, than you can even install Xposed (I'm using it, it's OK)
msankadi said:
Doing some more research I found out that my issue might have been due to not selecting read only in twrp...is that a possibility? any workarounds?
You are absolutely right! When I first tried this method I almost lost my device, since when uncheking "system read only" it some how wiped my baseband, and through rsd I was not been able to flash it back... Had to dig a lot in Google to recover it...
So the good way is: unlock bootloader, install systemless SuperSU via fastboot, boot up, go to bootloader, install TWRP by fastboot, boot in it twice, never uncheking read-only, than you can even install Xposed (I'm using it, it's OK)
Click to expand...
Click to collapse
Could you please tell me as to how you recovered your IMEI and Baseband?
Flash your efs backup.
lafester said:
Flash your efs backup.
Click to expand...
Click to collapse
If you don't have the phones original efs backup?
WhyKRUM said:
If you don't have the phones original efs backup?
Click to expand...
Click to collapse
Then send it in for repair. Those are the only options allowed here.
Flash the correct modem .
Thank you for the replies/advice
Found the correct modem for my phone, but even after manually flashing with the usual prescribed commands of:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
My MXP/S was still showing "Unknown" baseband and IMEI
I then retried the process with an additional flash modem command (eg. below) and have since had full LTE/4G coverage and perfect Wifi.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Hopefully this info helps anyone else.
@ECHO OFF
ECHO.
ECHO. Script by @evogp ...
ECHO.
ECHO.
ECHO. Flashing Bootloader ...
ECHO.
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
ECHO.
ECHO. Flashing System ...
ECHO.
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
ECHO.
ECHO. Flashing Modem SW ...
ECHO.
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash bluetooth BTFM.bin
ECHO.
ECHO. Wipe Cache and Data ...
ECHO.
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
ECHO.
ECHO. Installation Complete!
ECHO.
PAUSE
mfastboot reboot
EXIT /b 0
I also have problems with the network, no signal, plus my appears the normal imei, Moto X Style Brazil.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WhyKRUM said:
Thank you for the replies/advice
Found the correct modem for my phone, but even after manually flashing with the usual prescribed commands of:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
My MXP/S was still showing "Unknown" baseband and IMEI
I then retried the process with an additional flash modem command (eg. below) and have since had full LTE/4G coverage and perfect Wifi.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Hopefully this info helps anyone else.
Click to expand...
Click to collapse
It did, thanks a lot!
https://www.xsfirmware.com/motorola-moto-x-force-xt1580-firmware-flash-file/
Solution to no baseband xt1580
Related
So I requested the relock information from Motorolla and got access to the firmware. However, some of it is correct. Following these directions:
Next flash the images using fastboot:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock
This came from https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images.
First problem is the first two steps aren't workign as the moto boot isn't even in the firmware provided. Second problem, when i do step oem lock, I'm told to do the oem lock begin command, which I do. Then I get an error message stating my software isn't verified, however on the fastboot screen it states official. So I can't relock the phone, NOR can I get rid of the unlocked bootloaded message.
Next, the phone will not see the Feb security update, says nothing available. When i download it and try to install in the factory recovery, I get an error. I can't recall what it says exactly, but it does try to install.
Any ideas? The phone works, just can't get the phone re-locked or take any software updates, which I'm sure goes right back tot he stupid unlocked bootloader.
Here is the breakdown....
Unlocked does not affect updates.
Logo.bin is really easy to change.
There is a stock rom available to flash with the update included.
lafester said:
Unlocked does not affect updates.
Logo.bin is really easy to change.
There is a stock rom available to flash with the update included.
Click to expand...
Click to collapse
The stock rom with update requires TWRP installed. For some reason I cant get the phone to relock nor take the Feb security update.
So use twrp... Not sure what the issue is here.
Using the lock oem command has never worked for anybody with this phone. Not sure why they added that if it doesn't work at all.
This worked for my Moto G 2015 so I assume its the same for Moto X. Disregard motoboot.img and any others files that do not apply to Moto X 2015.
1. Run oem lock begin
2. Flash stock firmare files
3. Relock bootloader
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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
"........... all sparsechunk files"
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Original Source: http://forum.xda-developers.com/showthread.php?t=2575586
lafester said:
So use twrp... Not sure what the issue is here.
Click to expand...
Click to collapse
Well...if this stupid phone would take TWRP than all be good...but this pos will not. Using WinTools I flash TWRP, says successful, but no die when I try to reboot into recovery. If I do the power and volume truck at "no command" I get the stock recovery not twrp. Starting to really hate this phone. Even wife's S6 is simpler than this.
What happens in fastboot? Not sure what win tools is. Use fastboot then reboot directly into recovery.
First Download ;
mfastboot : https://drive.google.com/file/d/0B5jlU9JnLAZGbVU0UzJ3N3p4X2M/view?usp=sharing
new logo : http://forum.xda-developers.com/mot...o-remove-unlocked-bootloader-warning-t3201141
and only this firmware : http://firmware.center/firmware/Mot...HS24.49-18-3_cid9_subsidy-DEFAULT_CFC.xml.zip
and
mfastboot devices
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash logo logonew.bin --- (new logo name)
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase userdata
mfastboot erase cache
mfastboot oem lock
nxtime said:
First Download ;
mfastboot : https://drive.google.com/file/d/0B5jlU9JnLAZGbVU0UzJ3N3p4X2M/view?usp=sharing
new logo : http://forum.xda-developers.com/mot...o-remove-unlocked-bootloader-warning-t3201141
and only this firmware : http://firmware.center/firmware/Mot...HS24.49-18-3_cid9_subsidy-DEFAULT_CFC.xml.zip
and
mfastboot devices
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash logo logonew.bin --- (new logo name)
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase userdata
mfastboot erase cache
mfastboot oem lock
Click to expand...
Click to collapse
Sir...I LOVE U! That fixed everything! Phone is relocked finally. Phone is right...finally. I owe you a beer!!!
MHB1638 said:
Sir...I LOVE U! That fixed everything! Phone is relocked finally. Phone is right...finally. I owe you a beer!!!
Click to expand...
Click to collapse
im happy for you. thanks
droid turbo 2 RSD lite failed flashing process "gpt.bin"? more details inside
I am using windows 10 64-bit and have installed Motorola End User Driver 6.4.0.
Used 15 seconds ADB installer to install ADB and Fastboot. Also have overwrite fastboot, AdbWinApi.dll and AdbWinUsbApi.dll with moto fastboot.
fixed the detection issue by changing usb port:silly:
but now a new problem has popped up . . .
tried restoring through fastboot and got the same issue on gpt.bin flashing step
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes this is because you cannot downgrade gpt.bin partition. You have to be very careful using the correct gpt.bin. It's the easiest way to hard brick a Motorola phone.
You can upgrade the gpt.bin if you have a newer version.
Normally you should be alright by just skipping this step and flashing bootloader, system etc.
roweboat56 said:
Yes this is because you cannot downgrade gpt.bin partition. You have to be very careful using the correct gpt.bin. It's the easiest way to hard brick a Motorola phone.
You can upgrade the gpt.bin if you have a newer version.
Normally you should be alright by just skipping this step and flashing bootloader, system etc.
Click to expand...
Click to collapse
so in what order i should flash the file? or it would be a real help for me if you could tell me the steps for completely restoring droid turbo 2 as i cannot find it here.
ferolac said:
so in what order i should flash the file? or it would be a real help for me if you could tell me the steps for completely restoring droid turbo 2 as i cannot find it here.
Click to expand...
Click to collapse
Had this handy cuz I just wrote this up for myself & someone else...
Just copy and paste the entire set into command prompt.
mfastboot oem fb_mode_set
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot flash system system.img_sparsechunk.12
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
many times the modem doesn’t flash properly, so simply run these commands again:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
roweboat56 said:
Had this handy cuz I just wrote this up for myself & someone else...
Just copy and paste the entire set into command prompt.
Click to expand...
Click to collapse
just to be clear, should i use mfastboot-v2?
yes ! sorry didn't mention that.
I always recommend using mfastboot (latest version) for all ADB flashing. it's built for motorola, but it can accommodate bigger files than regular fastboot.
roweboat56 said:
I always recommend using mfastboot . . .
Click to expand...
Click to collapse
i ran the above commands and got this. Saved the device from bricking by unplugging it before the script reached the erase commands part.
That simply means your bootloader is already a newer version, you can skip that step as well.
yeah, i figured that much but what i cannot understand is that why it is throwing the same error when flashing sparsechunks, as i am using the official stock nougat for droid turbo 2 downloaded from this thread thread
I'm brazilian and I'dont have a good english, but I'll try explain.
I was using Lineage ROM 7.1 with root and bootload unlock, I wanted comeback to ROM STOCK 6.0. But, after that procedure my network didn't work.
WIFI - Works
Network - NO
IMEI - Blank
I used adb fastbook and flashed LA version Single Sim
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Now, I'm downloading the EU version to try flash modem firmware. Does anyone know how to resolve this issue?
Do it one more time. Like here:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Flash The newest 6.x, check how many sparsechunks do you have after unpack zipfile. @goulartt
dzidexx said:
Do it one more time. Like here:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Flash The newest 6.x, check how many sparsechunks do you have after unpack zipfile. @goulartt
Click to expand...
Click to collapse
Thank you man, I tried flash EU version 6.0.1, but now my WIFi stopped work kk I tried all LA versions too ._.
hello friends I need a little help with this issue it turns out that I have a g4 xt1625 amazon motorcycle to which I unlocked the boockloader and then I became root after all that I installed several rom from 7.1.2 to 8.1. it turns out that I wanted to undo all of that and go back to stock 7.0 but my phone got flushed in the recovery mode and to be able to lock it again I had to reinstall twrp and go back to root, there is the possibility of making my phone back to stock ? I tell them that I'm not interested in doing it as a guarantee, I just want to go back.
If you want to just go back to the stock ROM (no root, no TWRP):
Download the NPJ25.93-14.7 Amazon stock ROM https://androidfilehost.com/?fid=817906626617956922 Unpack the stock ROM (this is the September 2017 security patch) and extract to your ADB folder.
Ensure your key files are backed up from your device's internal storage.
Boot your device to the bootloader, connect to your computer via USB (preferably the original USB cable).
Open the ADB terminal and use the following flashing 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 dsp adspso.bin
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
That should restore your device to stock. If you wish to re-lock your bootloader, you may wish to follow the OEM locking flashing commands here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Ensure you only use the Amazon stock ROM (NOT NPJS25.93-14-13).
echo92 said:
If you want to just go back to the stock ROM (no root, no TWRP):
Download the NPJ25.93-14.7 Amazon stock ROM https://androidfilehost.com/?fid=817906626617956922 Unpack the stock ROM (this is the September 2017 security patch) and extract to your ADB folder.
Ensure your key files are backed up from your device's internal storage.
Boot your device to the bootloader, connect to your computer via USB (preferably the original USB cable).
Open the ADB terminal and use the following flashing 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 dsp adspso.bin
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
That should restore your device to stock. If you wish to re-lock your bootloader, you may wish to follow the OEM locking flashing commands here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Ensure you only use the Amazon stock ROM (NOT NPJS25.93-14-13).
Click to expand...
Click to collapse
Try something very similar with these commands that as I can see have some differences both at the beginning and at the end and I had no luck you think it had something to do and that's why it did not work...
fastboot oem fb_mode_set
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 dsp adspso.bin
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
This screen sends me after doing everything you tell me this same thing happened to me before I really do not know what is happening
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
flako72 said:
This screen sends me after doing everything you tell me this same thing happened to me before I really do not know what is happening
Click to expand...
Click to collapse
Can you confirm that the firmware you're flashing is the Amazon firmware and not the retail firmware? The extracted firmware in your ADB folder should have AMZ in the description.
echo92 said:
Can you confirm that the firmware you're flashing is the Amazon firmware and not the retail firmware? The extracted firmware in your ADB folder should have AMZ in the description.
Click to expand...
Click to collapse
if it says ATHENE_AMZ_NPJ25.93-14.7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml I downloaded the one you mentioned but I think I already had it and it has been with this probe today and it still leaves me in the original recovery
flako72 said:
if it says ATHENE_AMZ_NPJ25.93-14.7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml I downloaded the one you mentioned but I think I already had it and it has been with this probe today and it still leaves me in the original recovery
Click to expand...
Click to collapse
Hmm, that's odd - can you check that the firmware in your ADB folder is the NPJ25.93-14.7 Amazon firmware?
Did you flash retail firmware onto your device at any point?
echo92 said:
Hmm, that's odd - can you check that the firmware in your ADB folder is the NPJ25.93-14.7 Amazon firmware?
Did you flash retail firmware onto your device at any point?
Click to expand...
Click to collapse
If this is the system that I have in the folder, I know I am going to try again because I thought I had seen an error in the powershell window at the time it was being installed so that I could tell you more clearly in a moment check if and thanks for the time that you are taking to help me,
You think that the bootloader version has something to do with that error because I read that after being in Android 8.1 it was updated and that it was not possible to return to a lower Rom but that is information that I have not confirmed.
Hello fellow XDA enthusiasts!
I have been scavaging the forums on how to relock my bootloader after flashing this custom rom and a custom TWRP recovery.
Nothing worked to get me back to STOCK! (Sources):
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-oreo-bootloader-to-stock-t3784621
However... I managed to modify existing methods to make one that DID work… for me. (XT1635-02)
Here it is:
DISCLAIMER: I HAVE NO RESPONSIBILITY IN ANY WAY IF SOMETHING GOES TERRIBLY WRONG WITH YOUR DEVICE.
Step 1:
Install Motorola Drivers.
Step 2:
Install ADB Minimal.
or
ADB Tiny.
Step 3:
Download this latest signed image (Oreo, August 1, 2018).
Copy all of its contents into the directory where you installed your ADB Minimal (C:\ if portable).
Mirror ( only if AFH down use this link! )
Step 4:
Plug the Moto Z Play into your computer and HOLD DOWN 'volume down' + 'power' buttons.
Open up ADB Minimal and type
Code:
cd..
cd..
cd ADB
fastboot devices
(you should see your device!)
Alternatively, if you are booted on your phone, make sure ADB is enabled in developer mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(see here)
and device is authorized on PC, type:
Code:
cd..
cd ADB
adb reboot bootloader
adb devices
Once confirmed you see your device. Copy & paste the following commands:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
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 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 boot boot.img
fastboot oem lock
Step 5:
You will may have to manually press 'enter' on your keyboard to enter the last command which will reboot your device and Voilà La!
You should have relocked bootloader.
I've tried this method, but on booting screen the problem is persistent that your device has been unlocked and not tusted please visit care center:; I'm hectic, even in my device oem lock option is under gray colour and it's not clicking. How i can get rid from this issue???