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.
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!
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
Download the stock ROM HERE
and unzip it along with the abd fastboot archives (inside it's folder)
put your phone on fastboot mode: volume down + power
open abd + fastboot HERE (shift + right mouse button - open command window)
it will open a command window
write: fastboot devices and hit enter - make sure it shows numbers like serial numbers
past this comand:
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 oem lock
fastboot reboot
hit enter and wait, you are done!
PS:
1. doing this fixed "Your device has failed verification and may not work properly" showing on my brand new phone
2. it is just flashing stock room it is not rooting or unlocking boothloder so it will not make you lose your warranty
3. as for me (I'm from brazil) its working perfectly
CREDITS FOR THE ROOM: stockrom.net
Force close
I'm facing force closes from apps like file manager Moto apps and more. Did you face these?
Are you sure this is the stock rom for the XT1710-07? The stock rom you posted is exactly the same as
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
But good to know that it worked for you. Who knows, maybe now there is only one RETAIL stock rom which works for all variants (except VZW and CN)?
@lexie90
1- Room = quarto, sala. The correct name is "ROM"
2- Original credits to ROM is for Adriana Pignata (Google+) and mirrors.lollinet.
This site stckrom.net simply copying.
Since the origin of this code is unknown and the OP is not a developer, members are advised to exercise due caution - in other words, you take the risk entirely.
I credited the site I got It from, How could I know where they got It from?
Junior Passos said:
@lexie90
1- Room = quarto, sala. The correct name is "ROM"
2- Original credits to ROM is for Adriana Pignata (Google+) and mirrors.lollinet.
This site stckrom.net simply copying.
Click to expand...
Click to collapse
Thanks for the Very important correction
LenAsh said:
Since the origin of this code is unknown and the OP is not a developer, members are advised to exercise due caution - in other words, you take the risk entirely.
Click to expand...
Click to collapse
Yep this note was in the post until the ADM edited and apparently took It off
If my Moto don't have unlock bootloader, I can flash it?
lexie90 said:
I credited the site I got It from, How could I know where they got It from?
Click to expand...
Click to collapse
That's exactly the point I made. Other members NEED to understand the risks this brings.
LenAsh said:
That's exactly the point I made. Other members NEED to understand the risks this brings.
Click to expand...
Click to collapse
Yep I agree! I dont understand why the ADM took the advertising out
this rom stock work with other variants of XT1710, in Mexico we have XT 1710-06, please you can tell me?
XT1710-06 Variant
Does anyone has the XT1710-06 variant? it's the Latin American Retail version.
I'm still on APRIL 1st Security Patch, and I'm really starting to wonder if this version is ever going to upgrade to 8.0 or whatever.
Is there a way to go back to full stock rom in case I mess up in the process of installing a different official rom?
Thanks!
Not exactly the best at all with phone development, and this may be the dumbest question ever, but can I flash this onto a Samsung phone somehow? I am just wondering. Like I said, sorry if it is a dumb question I am not good at all with phone stuff haha
@Junior Passos Were you able to install OTAs after installing this stock retail rom?
gngshpor said:
Not exactly the best at all with phone development, and this may be the dumbest question ever, but can I flash this onto a Samsung phone somehow? I am just wondering. Like I said, sorry if it is a dumb question I am not good at all with phone stuff haha
Click to expand...
Click to collapse
You can't put it on a samsung. You needa put that Samsung's roms on that samsung.
Hi to all. Have a question. I bought Moto z2 play xt 1710-11 with ZUI!!! where can I get working global stock rom?
Yevgeniy1985 said:
Hi to all. Have a question. I bought Moto z2 play xt 1710-11 with ZUI!!! where can I get working global stock rom?
Click to expand...
Click to collapse
Hi, nowhere.
I used 2 stock ROMs to get a clean Nougat with working modems.
KirMit said:
Hi, nowhere.
I used 2 stock ROMs to get a clean Nougat with working modems.
Click to expand...
Click to collapse
Maybe custom? Something with working gapps and Moto mods
Yevgeniy1985 said:
Maybe custom? Something with working gapps and Moto mods
Click to expand...
Click to collapse
Year, just replace with correct modem images.
KirMit said:
Year, just replace with correct modem images.
Click to expand...
Click to collapse
If it possible, could you give me a link to read materials how to do that?
Stock firmware are available on lolinet.
You can find the list of all Motorola Edge Plus firmware here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Select your region and download relevant firmware.
[Prerequisite]
- ADB
- Motorola Drivers
Extract zip into adb folder for convenience.
Paste following command in command prompt:
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 modem NON-HLOS.bin
fastboot erase mdmddr
fastboot flash fsg fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash Bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
These commands are also available in servicefile.xml for reference.
If you plan to relock the bootloader, first flash stock firmware and then relock the bootloader using
fastboot oem lock
Android 11 to Android 10 downgrade
It seems Motorola has disabled bootloader downgrade through Anti-Rollback in Android 11. The latest version of Android 11 (Q1-19-58-30-2) doesn't allow vbmeta to be flashed. Fastboot would return following error:
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 10 vs 16
I have the Verizon Edge plus. I noticed that there is a VZW folder, which I am assuming is the Verizon firmware, and a Retail folder on the lolinet mirror. Can you flash the retail version on the Verizon version of the phone successfully and would it remove the Verizon bloat?
skritch said:
I have the Verizon Edge plus. I noticed that there is a VZW folder, which I am assuming is the Verizon firmware, and a Retail folder on the lolinet mirror. Can you flash the retail version on the Verizon version of the phone successfully and would it remove the Verizon bloat?
Click to expand...
Click to collapse
Also wanna know this
Disillusionedsal said:
Stock firmware are available on lolinet.
You can find the list of all Motorola Edge Plus firmware here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Select your region and download relevant firmware.
[Prerequisite]
- ADB
- Motorola Drivers
Extract zip into adb folder for convenience.
Paste following command in command prompt:
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 modem NON-HLOS.bin
fastboot erase mdmddr
fastboot flash fsg fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs12
fastboot flash Bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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 erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
These commands are also available in servicefile.xml for reference.
If you plan to relock the bootloader, first flash stock firmware and then relock the bootloader using
fastboot oem lock
Click to expand...
Click to collapse
How long is the "fastboot oem fb_mode_clear" command supposed to last? Left it for a lot of time and nothing happens, I check the bootloader logs and last log is erase:ddr. If I select Start from the menu using the up/down keys and the start button, it takes me to a screen where it says no valid firmware detected contact motorola support. Please help
I haven't tried it yet but someone confirmed to me that you can flash the retail firmware on a Verizon variant. Yes it will remove the extra junk. No it will not make the bootloader unlockable
(bootloader) Invalid partition name Bluetooth- can proceed no further. Had to rescue as phone is a necessity
snowman2765 said:
(bootloader) Invalid partition name Bluetooth- can proceed no further. Had to rescue as phone is a necessity
Click to expand...
Click to collapse
anybody?
if i want to downgrade to low version from high version, need to unlock bootloader??
snowman2765 said:
anybody?
Click to expand...
Click to collapse
Try use lowercase bluetooth
tha_mechanic said:
I haven't tried it yet but someone confirmed to me that you can flash the retail firmware on a Verizon variant. Yes it will remove the extra junk. No it will not make the bootloader unlockable
Click to expand...
Click to collapse
if the bootloader is unlocked does that mean it can be used with any carrier? what exactly would an unlocked bootloader enable?
Unlocked bootloader just allows you to flash custom .img on the device
This however wont fix the fingerprint scanner, that even if you did the workaround after unlocking ( https://forum.xda-developers.com/t/fix-fingerprint-not-working-after-bootloader-unlock.4214041/ ) , because you lost root after flashing stock and no way to edit the goodix files.
Anyway to properly return to stock and get fingerprint scanner back ?
EDIT: Nvm, the fix works properly with just skipping all the goodix part and doing all the CQA Menu Mode operations per the instructions.
Hello - it's been about 10 years since I played with any XDA stuff or custom roms. I have a stock Motorola G Power that bricked itself. It will not boot and recovery mode just gives me "No Command". Only option seems to be factory data reset.
Can anyone suggest a procedure to allow me to either re-install the stock software to get into the phone or recover my data? Sadly I had not backed anything up since last summer.
Should I just try to reflash a stock rom to see if i can get in? Will flashing the rom kill the onboard storage?
Cant find the exact same version either:
SOFIA10/QPMS30.80-63-6-8-5
I found 63-6-8-10 and 63-6-8-3 but not the exact same. Phone is Retail US.
Any help would be appreciated.
Ok found the stock rom that matches 63-6-8-5. Do I just try to flash that back to get back into the phone with my existing data?
Uberhare said:
Ok found the stock rom that matches 63-6-8-5. Do I just try to flash that back to get back into the phone with my existing data?
Click to expand...
Click to collapse
You can try flashing the stock from and just skip the erase userdata step.
The firmware contains a file named flash_file.xml contains the flash commands
You can use Online FlashFile Converter to convert the .XML to simple fastboot commands.
You also should check if getvar is-userspace
Code:
fastboot getvar is-userspace
if yes you need to switch between fastboot and fastbootd
If it's no you don't need to worry about fastbootd
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
You can try flashing the stock from and just skip the erase userdata step.
Click to expand...
Click to collapse
Do I need to unlock the bootloader for flashing an original file?
Uberhare said:
Do I need to unlock the bootloader for flashing an original file?
Click to expand...
Click to collapse
No, you shouldn't need to but it's easier if the bootloader is unlocked.
Unlikely, you can unlock the bootloader now anyways.
Unless you enabled OEM Unlocking in Dev Options already.
If you did enable OEM Unlocking, I would Unlock the bootloader.
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Are the steps any different if the bootloader is locked? You mention it is easier if it is unlocked.
Thank you for the tutorial.
Uberhare said:
Are the steps any different if the bootloader is locked? You mention it is easier if it is unlocked.
Thank you for the tutorial.
Click to expand...
Click to collapse
Easier may not be the right word.
If the bootloader is unlocked, you are less likely to have issues flashing.
ADB devices - does not return any devices, although I can see the phone is connected with the Motorola recovery tool.
fastboot getvar is-userspace returns:
is-userspace: no
Finished. Total time: 0.002s
I found where fastbootd is.
C:\Android>fastboot getvar is-userspace
is-userspace: yes
Finished. Total time: 0.002s
Uberhare said:
ADB devices - does not return any devices, although I can see the phone is connected with the Motorola recovery tool.
Click to expand...
Click to collapse
adb devices will not work if the device is in fastboot mode.
Use fastboot devices when it's in fastboot mode.
sd_shadow said:
adb devices will not work if the device is in fastboot mode.
Use fastboot devices when it's in fastboot mode.
Click to expand...
Click to collapse
adb devices does not show anything in either mode. That is why I looked for fastboot mode. Should I trouble shoot that first?
This is what I want with the erase commands deleted at the end? The erase commands are what will kill my data or is there something else I need to remove?
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 radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
echo Press any key to restart the phone!
pause
fastboot reboot
exit
Looks like phone doesn't respond to commands in fastbootd only normal.
I successfully ran the batch file, but the phone still doesn't boot. What is my next step? (besides throwing it against the wall!)
Phone accepts all the files for the current version of software, as well as commands to clear some of the labels. So the userdata is still there, I just can't get to it. Can you read these with a jtag like the older phones?
What if I try to roll it forward to Android 11 through the stock roms?