Related
I tried to flash a downgrade image to my moto e 2nd gen. Now Im stuck in bootloader and a warning message for unlocked bootloder. Ive tried to flash logo.bin, and other images aswell with no luck. It keeps asking me to install a valid signed images, I don't know where to find these images. Please help!
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
pemhak said:
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
Click to expand...
Click to collapse
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder: https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
I got my device back!! I did succeed to flash it with this rom "surnia_stock_5.0.2.zip" with TWRP. I did not have the patience to wait at the Motorola logo when booting, I have to wait 2-3 min and 2-3 min for services to start. for the device to boot. But now it doesn't register any sim card when at desktop?!?
squid2 said:
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder:
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
Click to expand...
Click to collapse
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
pemhak said:
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
Click to expand...
Click to collapse
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
squid2 said:
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
Click to expand...
Click to collapse
Ok, thanks. I will wait for download to complete and flash that image.
pemhak said:
Ok, thanks. I will wait for download to complete and flash that image.
Click to expand...
Click to collapse
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Noeljunior said:
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Click to expand...
Click to collapse
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
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 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 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 oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
pemhak said:
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
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 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 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 oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
Click to expand...
Click to collapse
And I'm back with my Moto E! Thank you! I wasn't doing some of those commands and with all those commands it works! Thank you!
I've done lots of research on flashing firmware and still have some questions + notes to share.
First off the popular topics on this are often full of incomplete / bad info and broken links.
So RSDLite is the preferred method ? ..instead of manually doing it line by line in a fastboot/mfastboot console or with a .bat file (on Windows)
So.. some misc stuff now that i hope is useful
I noticed the config file for flashing this, XT1527_SURNIA_RETCA_5.0.2_LXI22.50-24.1_cid14_subsidy-TELUS_CFC.xml
loads, "slcf_rev_b_telus_v1.1.nvm" which holds carrier specific data.
Which would be ignored *I think doing it manually.
Also every guide on the web says this line,
mfastboot oem config carrier vzw
vzw is the carrier code for Verizon.. so why do people always flash Verizon info on all stock firmware packages ?
My carrier has code tkpca for Telus.
The info shared across the web (comes from this forum) is sloppy and inaccurate.
For example guides say back up the PDS partition before flashing but you can't.
And i think it's sym linked to a folder called persist (that resides on root)
(you can back it up by using RootExplorer to zip the folder up then copy it out)
There is lots of issues / problems to watch out for..
For example i encountered an error trying to flash Firmware packages with RSDLite.
It would always say "flashing failed on gpt.bin" (the first file to flash)
(supposedly the fix for that is to delete the getvar line)
Also most guides tell you to flash with fastboot or mfastboot (almost the same)
problem is some oem's have an extra sparsechunk file and others don't.
this could lead to some huge problems i bet.. like maybe a bricked phone.
The main problem i encountered was losing my signal after i flashed what some guy here advised.
I got the firmware package installed manually (after RSDLite failed)
But no matter what i couldn't get my phone setup with Telus.
Every time the phone started it launched some activating phone dialog for 30 minutes then fail.
I seen one guy here say he managed to upgrade like what i wanted to do from 5.0.2 to 5.1.1
But he was sort of vague.. saying he did not update the Radio.
So i had tried to use the radio from the stock Telus firmware posted online inserted into the USC or US v5.1 firmware folder but it made no difference re-flashing.
I think what "Radio" means is these two files in the firmware package..
fsg.mbn + NON-HLOS.bin
So i think that other guy i seen here on Telus removed those lines to flash those two radio files then he manually flashed the rest of them i am guessing..
So this is suppose to be my stock package..
XT1527_SURNIA_RETCA_5.0.2_LXI22.50-24.1_cid14_subsidy-TELUS_CFC.xml
It says in, "factory_version_info_cfc.txt"
Build Fingerprint: motorola/surnia_retca/surnia_umts:5.0.2/LXI22.50-24.1/2:user/release-keys
What does the "surnia_umts" part mean guys ?
Because i was told to flash,
SURNIA_USC_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml
(So i could upgrade to v5.1 stock)
And after poking around in the files i think the USC part means USA & Canada ?
But my radio wouldn't work on that for LTE/cdma/auto prl
And this one says
motorola/surnia_usc/surnia_cdma:5.1/LPI23.29-15/18:user/release-keys
notice how it says "surnia_cdma" ?
Then,
SURNIA_RETUS_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml
motorola/surnia_retus/surnia_umts:5.1/LPI23.29-15/19:user/release-keys
Then,
XT1528_SURNIA_VERIZON_5.1_LPI23.29-17_cid2_subsidy-DEFAULT_CFC.xml
motorola/surnia_verizon/surnia_cdma:5.1/LPI23.29-17/18:user/release-keys
So... does the build fingerprint info i posted above indicate different types of Radio connections maybe ?
surnia_cdma -vs- surnia_umts
Because i am suspicious this may be why i failed to fully update to v5.1 (my radio didn't work)
Here is a link to get Firmwares for 5.0.2 and 5.1.1 (for Otus + Surnia)
https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
Here is the commands to flash with mfastboot..
Code:
mfastboot oem fb_mode_set
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot oem config carrier vzw
mfastboot oem fb_mode_clear
Note1:
I think you can add the line (below) to above (code/quote) to restart the phone when flashing finishes,
mfastboot reboot
What i like to do is add the following to the last line..
@pause
Then if you put the quoted lines into a windows .bat file it will pause for you
when it's finished so you can read what happens or save it to file etc
Note2: Some stock firmware use another line so you would need to add below to above code lines.
mfastboot flash system system.img_sparsechunk.6
Open the firmware file you download to see if there is 5 or 6 "sparsechunk" files.
and about this line below..
mfastboot oem config carrier vzw
"vzw" i think means for Verizon so look for your own code.. i think ? (mine is tkpca)
If you want to flash only the radio related files ? it's this below.. i am pretty sure.
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
There is a lot more i learned while trying to flash my phone with stock Firmware.
I would like us to have a list of MD5 hash's to verify the downloaded .zip's we are sharing too.
Incomplete downloads happen.. always check and always back up as much as you can before flashing !
I used TWRP to make a backup ..it was quick and easy and i needed it and it worked
Here is some hash's i made.. post more if you got 'em guys
- 5.1
SURNIA_RETEU_EU_5.1_xt1524_LPI23.29-15.zip = MD5: b7bae69012df7c47ee370635a49de2d1
SURNIA_RETUS_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml = MD5: 623419f42075a9b8b74c2d833bc4fa2d
SURNIA_USC_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml = MD5: 6053bd6007214b4eb59c5e96c5dd4d7a
XT1528_SURNIA_VERIZON_5.1_LPI23.29-17_cid2_subsidy-DEFAULT_CFC.xml = MD5: 57196e77d89e04a3c6d6358a42563edc
- 5.0.2
XT1527_SURNIA_RETCA_5.0.2_LXI22.50-24.1_cid14_subsidy-TELUS_CFC.xml = MD5: 04f658169a5bc35c295973054ba85b67
There is also a bunch of codes you can enter in the dialer to open hidden menus
(i tested most of them)
*#*#759#*#* = RLZ
*#*#4636#*#* = INFO
*#06# = IMEI
Moto G Hard Reset
How to hard reset Wipe/Reset Data/Profile & internal storage, please use this code: *#*#786#*#*
Open Superuser App
*#*#1234#*#* or *#*#7873778#*#*
Manual Check Update
*#*#2432546#*#*
Motorola Service Menu (CQA Test)
*#*#2486#*#*
Click to expand...
Click to collapse
Lastly people need to be careful with downgrading versions or having locked bootloaders.
I'll try to answer more of your questions when I get off work tonight or tomorrow but in regards to UMTS that is required to get a GSM signal.
[email protected]
As the title says.
Does anybody have any updated Radio / bootloader zips that I can flash via TWRP ?
I have an old Moto E Condor and I can't get the phone to recognize the Sim so was wondering if updating the radio / bootloader would help ?
I'm running out of ideas.
I have tried Android 6 & 7 tried different Sims.
I'm not sure how I would find out if it's a hardware issue rather than software ?
Any ideas ?
Thanks
Check this link for Radio file
https://forum.xda-developers.com/devdb/project/dl/?id=13877
I didn't got what bootloader you are talking about. But if you want latest twrp then check this link
https://dl.twrp.me/condor/twrp-3.1.0-0-condor.img.html
Ankit_29 said:
Check this link for Radio file
https://forum.xda-developers.com/devdb/project/dl/?id=13877
I didn't got what bootloader you are talking about. But if you want latest twrp then check this link
https://dl.twrp.me/condor/twrp-3.1.0-0-condor.img.html
Click to expand...
Click to collapse
Thanks mate.
I will give it a go
I had the same problem with my condor ,but flashing the "radio files" didn't help the case ,it always failed in my case ,so the best advice I can give you is to not flash isolated radio files ,but to backup your data and flash stock ROM for your device,trust me it'll save you a lot of headache
Akshay_92 said:
I had the same problem with my condor ,but flashing the "radio files" didn't help the case ,it always failed in my case ,so the best advice I can give you is to not flash isolated radio files ,but to backup your data and flash stock ROM for your device,trust me it'll save you a lot of headache
Click to expand...
Click to collapse
Thanks for that info.
You say that you had the same problem? Have you sorted it out now ?
When you flashed the stock ROM
Did you have to do this via fastboot ??
Thanks again
johnhux7 said:
Thanks for that info.
You say that you had the same problem? Have you sorted it out now ?
When you flashed the stock ROM
Did you have to do this via fastboot ??
Thanks again
Click to expand...
Click to collapse
Yes,my device is good as new,I'm writing this message from it so haha...you can find the appropriate stock ROM to flash here
https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
If you don't know which ROM to download, got to your phones settings >about phone>build number
And download the specific ROM with that build number,now be absolutely sure to not flash a KitKat ROM on a device that was upgraded to lollipop earlier, its absolutely essential as it 100% will brick your device,
As for your question, yes you will need to be in fastboot to flash the ROM,and the program that you'll need to flash the ROM with is called mfastboot-v2 you can find it here
https://forum.xda-developers.com/general/rooting-roms/using-mfastboot-exe-to-unbrick-motorola-t3203518
Now after downloading both the ROM and mfastboot ,extract both of them into the same folder of your PC ,after doing that ,go into that folder and hold shift+right mouse key and select "open new command window here" from the dialogue box ,now assuming that you have downloaded the drivers for your phone , switch off your phone ,go into mfastboot mode by holding power key + volume down key for about 5-7seconds, now connect your phone to the PC with the help of USB cable and in the command window type "mfastboot devices" if everyw is done correctly it will show your device's name in an alphanumeric format under "list of devices" after that follow these commands in the ORDER! that they are written and you will be good to go :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
NOTE:- number of sparsechunk files may be different for your version (check the files extracted from the ROM inside the same folder to see the order of numbers) so if the numbers are like 0,1,2,3,4 flash them in that order ,I have named it 1,2,3 in the command above for illustrations, good luck if you will do this correctly, you'll be back to a facotory version of your phone,with the imei problem fixed , another thing though, you'll lose your custom recovery so after you flash this stock ROM ,you'll have to flash the custom recovery again,
Cheers!!
Akshay_92 said:
Yes,my device is good as new,I'm writing this message from it so haha...you can find the appropriate stock ROM to flash here
https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
If you don't know which ROM to download, got to your phones settings >about phone>build number
And download the specific ROM with that build number,now be absolutely sure to not flash a KitKat ROM on a device that was upgraded to lollipop earlier, its absolutely essential as it 100% will brick your device,
As for your question, yes you will need to be in fastboot to flash the ROM,and the program that you'll need to flash the ROM with is called mfastboot-v2 you can find it here
https://forum.xda-developers.com/ge...ng-mfastboot-exe-to-unbrick-motorola-t3203518
Now after downloading both the ROM and mfastboot ,extract both of them into the same folder of your PC ,after doing that ,go into that folder and hold shift+right mouse key and select "open new command window here" from the dialogue box ,now assuming that you have downloaded the drivers for your phone , switch off your phone ,go into mfastboot mode by holding power key + volume down key for about 5-7seconds, now connect your phone to the PC with the help of USB cable and in the command window type "mfastboot devices" if everyw is done correctly it will show your device's name in an alphanumeric format under "list of devices" after that follow these commands in the ORDER! that they are written and you will be good to go :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
NOTE:- number of sparsechunk files may be different for your version (check the files extracted from the ROM inside the same folder to see the order of numbers) so if the numbers are like 0,1,2,3,4 flash them in that order ,I have named it 1,2,3 in the command above for illustrations, good luck if you will do this correctly, you'll be back to a facotory version of your phone,with the imei problem fixed , another thing though, you'll lose your custom recovery so after you flash this stock ROM ,you'll have to flash the custom recovery again,
Cheers!!
Click to expand...
Click to collapse
Thanks so much for taking the time to write this for me.
I'm new to using fastboot I got spoiled by using ODIN with Samsung whist I was learning.
Just one question.
Do you put in each of those commands and press enter after each one ?
johnhux7 said:
Thanks so much for taking the time to write this for me.
I'm new to using fastboot I got spoiled by using ODIN with Samsung whist I was learning.
Just one question.
Do you put in each of those commands and press enter after each one ?
Click to expand...
Click to collapse
Yes!!...And wait till it returns as [OKAY],then move ahead with the next one
Sent from my Moto G (4) using Tapatalk
---------- Post added at 06:43 PM ---------- Previous post was at 06:39 PM ----------
Akshay_92 said:
Yes!!...And wait till it returns as [OKAY],then move ahead with the next one ...It's alright man,we all are new to some stuff at one point,do let me know if you come into a hiccup
Cheers!
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Sent from my Moto G (4) using Tapatalk
Akshay_92 said:
Yes!!...And wait till it returns as [OKAY],then move ahead with the next one
Click to expand...
Click to collapse
I though so.
Was just checking.
I'm going to have some fun doing this
Love learning some thing new
The Moto is my spare phone so I can practice on that before getting stuck into fastboot on my Honor 8
johnhux7 said:
I though so.
Was just checking.
I'm going to have some fun doing this
Love learning some thing new
The Moto is my spare phone so I can practice on that before getting stuck into fastboot on my Honor 8
Click to expand...
Click to collapse
[emoji1] yep absolutely,
Sent from my Moto G (4) using Tapatalk
Akshay_92 said:
[emoji1] yep absolutely,
Click to expand...
Click to collapse
Thank you so much for sharing your knowledge.
It's what I love about this XDA community
Few days ago, imei number on my brother's moto e xt1022 disappeared out of nowhere. Phone used to boot to working state but didn't accept any sim cards nor connect to WiFi. The bootloader was locked and phone was not rooted.
So I visited official motorala service centre. They "softwared" the phone (probably flashed stock firmware). After that, the imei no was replaced with new numbers. Bootloader was unlocked automatically. The phone booted once. But after I switched off to insert sim card and then tried to boot, its not getting past this screen. What should I do to restore the phone to its working condition? Please help.
ramsut said:
Few days ago, imei number on my brother's moto e xt1022 disappeared out of nowhere. Phone used to boot to working state but didn't accept any sim cards nor connect to WiFi. The bootloader was locked and phone was not rooted.
So I visited official motorala service centre. They "softwared" the phone (probably flashed stock firmware). After that, the imei no was replaced with new numbers. Bootloader was unlocked automatically. The phone booted once. But after I switched off to insert sim card and then tried to boot, its not getting past this screen. What should I do to restore the phone to its working condition? Please help.
Click to expand...
Click to collapse
Flash stock/custom ROM
ramsut said:
Few days ago, imei number on my brother's moto e xt1022 disappeared out of nowhere. Phone used to boot to working state but didn't accept any sim cards nor connect to WiFi. The bootloader was locked and phone was not rooted.
So I visited official motorala service centre. They "softwared" the phone (probably flashed stock firmware). After that, the imei no was replaced with new numbers. Bootloader was unlocked automatically. The phone booted once. But after I switched off to insert sim card and then tried to boot, its not getting past this screen. What should I do to restore the phone to its working condition? Please help.
Click to expand...
Click to collapse
Hmm....Well this is certainly not professional and quite unfortunate,on the part of the service center employees,but since I assume that it's no longer under warranty and they won't take back the Devi because it's unlocked now and also because they won't take responsibility for it ,the best you can do is flash stock ROM,I have explained that earlier in this thread ...
Cheers!! And let me know how it went
Sent from my Moto G (4) using Tapatalk
Akshay_92 said:
Hmm....Well this is certainly not professional and quite unfortunate,on the part of the service center employees,but since I assume that it's no longer under warranty and they won't take back the Devi because it's unlocked now and also because they won't take responsibility for it ,the best you can do is flash stock ROM,I have explained that earlier in this thread ...
Cheers!! And let me know how it went
Click to expand...
Click to collapse
I got the SIM working.
Followed your instructions.
Got the phone back to stock
All good thanks for your help
John
Disclaimer: I am not responsible for anything that happens as a result of flashing these files.
Latest Build Nougat: 7.1.1_NPSS26.118-19-18
Latest Build Oreo: 8.0.0_OPSS27.76-12-25-15
Note: Motorola doesn't allow downgrading so once u flash O via OTA/Fastboot it isn't recommended to go back to N or any older build than the latest .
Downloads:
Stock N: ALBUS_RETAIL_7.1.1_NPSS26.118-19-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Stock O: ALBUS_RETAIL_8.0.0_OPSS27.76-12-25-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You must already have ADB and fastboot setup, check here if you haven't already as using adb/fastboot isn't within the scope of this thread.
How to Install ADB on Windows, macOS, and Linux
1. Download the file and extract the zip archive
2. Extract all the files to your fastboot folder. (Not needed if you have adb and fastboot added to the path, if you want to know how to do this, check this guide: How to Use ADB or Fastboot From Any Directory on your Windows/Linux PC)
3. Restart the device in fastboot/bootloader mode and connect to your PC.
4. Make sure the system detects the device in fastboot mode, to verify this your command window/terminal shows a serial number when you type:
Code:
fastboot devices
5. Use the following commands now or you can use the flash scripts provided as attachments to this post:
NOTE: SKIP the oem lock begin and the oem lock commands if you dont want to lock your bootloader
Linux users will need to change the extension to .sh and add sudo before each command or directly run it as a root user .
To simply flash, run the "OEM Flash" file; to lock the bootloader, run "OEM Lock" file.
Manual method:
Code:
fastboot oem lock begin
fastboot oem lock begin
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 (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
Credits:
JuniorPassos
TeamReviver
Motorola Mobility LLC
Sourceforge
XDA-Developers
So wait... you can fastboot unlock the Verizon model???
Help please.
Hello,
Could you provide complete stock firmware for the Moto Z2 play (Indian unit), while flashing the TWRP 3.1.10 , it is stuck on boot logo, I again go back to your verizon recovery image flash but now it is looping on the boot phase . Please help me , If you find any useful link please provide me. my region is India.
If I do complete flash of your Verizon's model Z2 on my Indian Z2 unit , whether it will work for me ??? If you have any idea for the Z2 play (General Global unit) , please share us, we will be very thankful to you. Main thing is this it is the new phone so very difficult to find and remedy so far. Thanks
niteshpant said:
Hello,
Could you provide complete stock firmware for the Moto Z2 play (Indian unit), while flashing the TWRP 3.1.10 , it is stuck on boot logo, I again go back to your verizon recovery image flash but now it is looping on the boot phase . Please help me , If you find any useful link please provide me. my region is India.
If I do complete flash of your Verizon's model Z2 on my Indian Z2 unit , whether it will work for me ??? If you have any idea for the Z2 play (General Global unit) , please share us, we will be very thankful to you. Main thing is this it is the new phone so very difficult to find and remedy so far. Thanks
Click to expand...
Click to collapse
Verizon operates in US and you flashed that for Indian version.Why?There is no official ROM out yet.
Most importantly you did not backup the ROM.
My advice would be try clearing the cache,factory reset.
Moto by Lenovo doesn't provide regular updates.
It is better to wait until Lineage OS pays a visit.
Cheers
wait how did you unlock the verizon version？
Update
New firmware BUILD NPSS26.118-19-4 for RETAIL models is added to the downloads.
https://www.androidfilehost.com/?fid=889964283620756684
Hi, do you know if is possible to flash the retail firmware to single sim version? (Vodafone, unlocked)
Hello,
I've accidentally did the oem lock...
What can I do to reverse this?
Do I have to send the smartphone back to Motorola?
Says boot image not signed, it does flash the firmware however it does not have fastboot flash system system.img_sparsechunk.7 in the zip folder so it doesn't actually flash it. However it does boot up and work like normal.
any word on this working on the canadian version?
it reads as XT1710-01 in fastboot
in the OS my current build number reads as NPSS26.118-19-11 ... i assume thats just a slightly newer version
and so, installing this would return the phone to pure stock - allow OTA and all that fun stuff?
unerds said:
any word on this working on the canadian version?
it reads as XT1710-01 in fastboot
in the OS my current build number reads as NPSS26.118-19-11 ... i assume thats just a slightly newer version
and so, installing this would return the phone to pure stock - allow OTA and all that fun stuff?
Click to expand...
Click to collapse
FYI, XT 1701-01 is the US unlocked for any carrier version.
Does this work for the xt1710-09 reteu version?
Can't flash this on xt1710-09 reteu. Says boot.img is not signed. I SO DESPERATELY want to relock my bootloader.. but it doesn't seem to work Any ideas?
I can confirm XT1710-01 works for Freedom Mobile in Canada.
I was rooted and the Motorola got into a Recovery bootloop after a security update. Makes me miss the peace of mind of Cyanogen. Hopefully LinageOS will come here soon.
cal800 said:
I can confirm XT1710-01 works for Freedom Mobile in Canada.
I was rooted and the Motorola got into a Recovery bootloop after a security update. Makes me miss the peace of mind of Cyanogen. Hopefully LinageOS will come here soon.
Click to expand...
Click to collapse
I use Titanium Backup to freeze the Motorola Update App. No more update notifications.
Help! First time trying to flash a ROM and it doesn't go well So far
I got my hand on a chinese Model of the phone. It says XT1710-11. From the first day I was fed up with their safecenter telling me everything on my phone was a virus. Then I realised I could not remove it because it was part of the "Firmware". Things got really bad when I could not use Pinterest or Twitter on the phone. I still dont know why.
So I remembered there was this thing called root that might be helpful. I started experimenting on it and I was finally able to root and installed magisk. But I still didnt know what to do so I decided it will be better to just flash a new ROM and found this trhread....
As I am writing this my phone doesnt have a OS, Back up was wiped at a point I even had to reflash TWRP and remount Data to be able to do anything with it.
I have an old iphone5 lying around that I will go back to in the mean time. But guys please help a poor lost soul. Is there a solution to my trouble?
tywinlannister7 said:
Retail Variant
BUILD: NPSS26.118-19-4
https://www.androidfilehost.com/?fid=889964283620756684
Click to expand...
Click to collapse
Add new Retail version.
https://androidfilehost.com/?fid=889964283620776139
NPSS26.118-19-1-2
Patch - December 1, 2017
Junior Passos said:
Add new Retail version.
https://androidfilehost.com/?fid=889964283620776139
NPSS26.118-19-1-2
Patch - December 1, 2017
Click to expand...
Click to collapse
Hello its compatibilty in Reteu 1710-09 ? Very thanks
Regards
Enviado desde mi Moto Z2 Play mediante Tapatalk
iron maiden said:
Hello its compatibilty in Reteu 1710-09 ? Very thanks
Regards
Enviado desde mi Moto Z2 Play mediante Tapatalk
Click to expand...
Click to collapse
Probably. I believe so, because it's a Retail version.
Junior Passos said:
Probably. I believe so, because it's a Retail version.
Click to expand...
Click to collapse
hello the ota that you climbed December gives me error in my reteu with November patch then I do not know if it is compatible with the firmware that you uploaded thanks
regards
Just got the edge+ (2023) from Boost Mobile, but they don't enable the esim usage. Currently running build T1TR33.43-48-21, model #XT2301-1
Does anyone know a way to enable this? Is the Edge+ 2023 rootable yet?
fatmanSings said:
Just got the edge+ (2023) from Boost Mobile, but they don't enable the esim usage. Currently running build T1TR33.43-48-21, model #XT2301-1
Does anyone know a way to enable this? Is the Edge+ 2023 rootable yet?
Click to expand...
Click to collapse
Is the device carrier locked? Haven't heard of anyone else not having esim, my converted Edge 40 Pro has it. If you can unlock the bootloader you can root the device; since you just got it you may have to wait around a week or so in order to actually be able to enable it in developer options but idk what the situation is for the US variant.
gibberishman said:
Is the device carrier locked? Haven't heard of anyone else not having esim, my converted Edge 40 Pro has it. If you can unlock the bootloader you can root the device; since you just got it you may have to wait around a week or so in order to actually be able to enable it in developer options but idk what the situation is for the US variant.
Click to expand...
Click to collapse
Great thanks! I'll wait a week and see. Do you know the firmware version I should be using for the US variant?
fatmanSings said:
Great thanks! I'll wait a week and see. Do you know the firmware version I should be using for the US variant?
Click to expand...
Click to collapse
I don't think the firmware has been uploaded yet. You can use ADB commands to extract the boot.img file and use magisk to patch it then flash patch boot, or wait to see if the full firmware gets uploaded. Unless the Edge+ has a different codename from the other Edge variants ( I don't think that's the case ) I couldn't find the full firmware.
gibberishman said:
I don't think the firmware has been uploaded yet. You can use ADB commands to extract the boot.img file and use magisk to patch it then flash patch boot, or wait to see if the full firmware gets uploaded. Unless the Edge+ has a different codename from the other Edge variants ( I don't think that's the case ) I couldn't find the full firmware.
Click to expand...
Click to collapse
Thanks for your help!
The codename should be rtwo, correct? You think I could flash to the RETAIL version? or should I just wait for the RETUS?
fatmanSings said:
Thanks for your help!
The codename should be rtwo, correct? You think I could flash to the RETAIL version? or should I just wait for the RETUS?
Click to expand...
Click to collapse
The model number in those firmware files don't match the model number for the US variant. I'm assuming the firmware hasn't been dumped yet since the phone has only been out a few weeks in the states.
gibberishman said:
The model number in those firmware files don't match the model number for the US variant. I'm assuming the firmware hasn't been dumped yet since the phone has only been out a few weeks in the states.
Click to expand...
Click to collapse
How long does it usually take for the firmware files to get dumped? A month or so?
fatmanSings said:
How long does it usually take for the firmware files to get dumped? A month or so?
Click to expand...
Click to collapse
Maybe a couple weeks if that. It just depends. Not really sure how they dump the firmware and if they need the physical device or not.
gibberishman said:
Maybe a couple weeks if that. It just depends. Not really sure how they dump the firmware and if they need the physical device or not.
Click to expand...
Click to collapse
I unlocked the bootloader and flashed stock firmware, but the software channel is still 'dish wireless' and esim settings are still hidden. Do you know of any other possible solutions to enable e-sim capabilities?
I tried to change the oem config carrier to retus and that didn't work either
fatmanSings said:
I unlocked the bootloader and flashed stock firmware, but the software channel is still 'dish wireless' and esim settings are still hidden. Do you know of any other possible solutions to enable e-sim capabilities?
I tried to change the oem config carrier to retus and that didn't work either
Click to expand...
Click to collapse
You did "fastboot oem config carrier retus" ?
gibberishman said:
You did "fastboot oem config carrier retus" ?
Click to expand...
Click to collapse
yes, it changed the value, but there are no changes to the software channel. Is there a way to change the ro.carrier value?
Do you think I can flash to the RETEU Edge 40 Pro firmware?
fatmanSings said:
yes, it changed the value, but there are no changes to the software channel. Is there a way to change the ro.carrier value?
Do you think I can flash to the RETEU Edge 40 Pro firmware?
Click to expand...
Click to collapse
You may be able to root the device and change the value. Don't thing there's a file you can flash to override the carrier. I wouldn't recommend flashing the EU firmware. The hardware is slightly different, don't know if it would affect anything.
Any updates? In the same situation. Tried flashing retail US firmware and FASTBOOT oem config carrier but it didn’t seem to work.
DeSlaye said:
Any updates? In the same situation. Tried flashing retail US firmware and FASTBOOT oem config carrier but it didn’t seem to work.
Click to expand...
Click to collapse
I tried flashing with the RSA Motorola tool and the MotoFlashPro, but neither worked with the US firmware. I haven't tried anything else yet, since I'm scared I'm going to mess something up. But if you would like to try, you could try rooting and patching some of the files, or try flashing the RETAIL firmware, although it's designed for xt2301-4 and not xt2301-1.
Flashing the RETAIL firmware may work since others have been able to convert from other regions as well. But as @gibberishman mentioned the hardware is slightly different and there have been reports of nfc not working, etc.
fatmanSings said:
I tried flashing with the RSA Motorola tool and the MotoFlashPro, but neither worked with the US firmware. I haven't tried anything else yet, since I'm scared I'm going to mess something up. But if you would like to try, you could try rooting and patching some of the files, or try flashing the RETAIL firmware, although it's designed for xt2301-4 and not xt2301-1.
Flashing the RETAIL firmware may work since others have been able to convert from other regions as well. But as @gibberishman mentioned the hardware is slightly different and there have been reports of nfc not working, etc.
Click to expand...
Click to collapse
I downloaded the RETAIL firmware and attempted to 'spoof' the Boost software by removing the MD5 checks in the flash script but no luck. Half the items didn't flash due to protected partitions so unless I have an unlocked bootloader, it doesn't flash. What's odd is these are legitimate firmware files straight from Motorola. I'm guessing there is a different signature for these from the standard unlocked variant vs Boost/Dish.
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.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 init_boot init_boot.img
fastboot flash vendor_boot vendor_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 erase apdp
fastboot erase apdpb
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
EDIT: Flashing the RETAIL on locked BL caused my device to soft-brick, I had to restore via Motorola Rescue and Smart assistance software which worked like a charm. If open BL, you may be able to change the software/carrier channel then attempt to restore through Motorola tool although YMMV.
Ascertion said:
I downloaded the RETAIL firmware and attempted to 'spoof' the Boost software by removing the MD5 checks in the flash script but no luck. Half the items didn't flash due to protected partitions so unless I have an unlocked bootloader, it doesn't flash. What's odd is these are legitimate firmware files straight from Motorola. I'm guessing there is a different signature for these from the standard unlocked variant vs Boost/Dish.
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.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 init_boot init_boot.img
fastboot flash vendor_boot vendor_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 erase apdp
fastboot erase apdpb
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
EDIT: Flashing the RETAIL on locked BL caused my device to soft-brick, I had to restore via Motorola Rescue and Smart assistance software which worked like a charm. If open BL, you may be able to change the software/carrier channel then attempt to restore through Motorola tool although YMMV.
Click to expand...
Click to collapse
Were you able to unlock the bootloader? Usually you have to unlock the bootloader before flashing.
fatmanSings said:
Were you able to unlock the bootloader? Usually you have to unlock the bootloader before flashing.
Click to expand...
Click to collapse
No, when I go to the unlock site it just gives me a 404 error page after submitting my unlock token. I gave up and decided to just use the Boost firmware. The device is sim-unlocked and supports AT&T/T-Mobile.