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
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void... Well, probably not.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* A lot.
*
* Tl;dr: if your device crashes and burns, I'm sorry, but I'm not to be blamed.
*/
Hey guys.
This is a guide on how to install official Android 8.1.0 "Oreo" on our beloved, forgotten, poor Moto G5s (montana). As you all may know, Lenovorola still hasn't released Oreo for everyone worldwide. Only a few Latin American countries are receiving the update, with Brazil due to receive it Soon™, since we've already received the August security patch (still Nougat though :/).
Update 2018.09.29: Brazil and India have also started receiving Oreo, but with a different build (OPP28.65-37-2).
However, this is Lenovorola we're dealing with, so I went ahead, captured the OTA and created a TWRP flashable zip, by patching the June firmware (NPPS26.102-49-11) with said OTA. And also, there's the standard .xml.zip to be used with fastboot, directly from Moto.
For those of you who want to keep everything stock, locked bootloader and all, I recommend going with the fastboot zip. For those who already have unlocked their phone's bootloaders and have TWRP installed, or are coming from a custom ROM but don't want to fiddle around with fastboot, you should use the TWRP flashable zip.
I can't stress this enough. ALWAYS BACK UP YOUR STUFF!!!! Do a TWRP backup (data, system, boot). I recommend backing up the contents of your internal storage as well. And for those willing to downgrade at some point, back up your persist and efs partitions, otherwise you'll lose IMEI!
Oh, and I assume you already have adb, fastboot and the Motorola USB drivers installed. In case you don't...
Motorola USB Drivers
Android SDK Platform Tools (includes adb & fastboot)
If you use Linux, you don't need to install any drivers, but you may have to configure udev to allow fastboot to detect your device. But that, along with telling how to configure adb and fastboot, is beyond the scope of this thread.
I don't know how things work in the Apple side, so kindly don't ask me how to do that on macOS.
This firmware should work on all Moto G5s models (XT1791/2/3/4/5/7). I can't tell if it works on model XT1799-2 (aka Green Pomelo / Qingyou).
A few warnings:
1. Forced encryption has not been disabled. So, if your phone is not encrypted, it will be encrypted again upon the very first boot. Don't interrupt the process, otherwise you'll lose ALL of your data! (You can flash @Zackptg5's dm-verity / forced encryption disabler if you want to)
2. Xposed doesn't work, whether it's installed to /system or via Magisk (systemless). I've already opened an issue on GitHub and am awaiting a reply.
3. (Fastboot only) Updating to this firmware will also update your bootloader and partition table. If you're unsure about that and/or afraid of a possible hard brick, skip the gpt and bootloader lines.
4. Please install the proper build for your software channel. For retbr and retin, use OPP28.65-37-2. For the other channels, go with OPP28.65-37.
5. If your phone's software channel is retbr or retin and you have already flashed the -37 build, you can simply dirty flash the -37-2 build over it. No need to factory reset / fastboot erase userdata.
With that out of the way, let's get to what matters most.
Downloads:
Build OPP28.65-37 (retla):
Fastboot ZIP (Android File Host | MEGA)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Build OPP28.65-37-2 (retbr & retin):
Fastboot ZIP (Android File Host)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Installation Guide:
Fastboot ZIP:
1. Download (obviously)
2. Extract the contents to a folder of your choice
3. Go to the folder which you extracted the files to
3. Inside the folder, open a command prompt, PowerShell, terminal or whatever you use as a command line interface
4. Put your device into fastboot mode if you haven't already done that (just hold Vol Down + Power for a while) and connect it to your PC
5. Execute the following commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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 DDR
fastboot oem fb_mode_clear
reboot
6. Have fun
Click to expand...
Click to collapse
TWRP Flashable ZIP:
1. Download (duh)
2. Put the file at the root of your internal storage (/sdcard)
3. Reboot to TWRP
4. Do a factory reset (optional if coming from stock Nougat) and then format /system
(If your device is encrypted and you want to remove encryption, you will have to format /data and then flash the forceencrypt disabler I mentioned above after flashing the ROM)
5. Flash the zip
6. Reboot
7. Have fun
Click to expand...
Click to collapse
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
@Cesarcami53 for telling us that the update was out for retla
@erfanoabdi for his Motorola OTA Link Generator and IMG Patch Tools
@lohanbarth for mirroring the fastboot zips to AFH / Mega
In case I forgot someone, please do let me know.
F.A.Q. (Read this before crying!!!!)
Q: Why did you come up with this?
A: Because Lenovorola is pulling a Samsung, taking forever to officially deliver the Oreo update to everyone.
Q: ERMAHGERD DIS ROM SUCKZ, MAH BATTERY IS DEAD IN 30 MINS, PLZ HALP!
A: Please do blame Motorola, or yourself, or your apps' developers, but not me. I haven't got anything to do with that. I haven't changed anything.
Q: What works and what doesn't?
In theory, everything should work, and nothing should be broken, since this is a stock ROM.
Q: Will you add feature xyz?
A: No.
Q: Why no inbuilt root/Magisk/xyz/abc?
A: Because not. 1. There's something called freedom of choice, and that must be respected. / 2. I want to keep everything as bit-perfect as possible, and as close as possible to what you would get by flashing a real OTA.
Q: How do I report bugs?
A: If you wanna report a bug, send me a logcat. In case of a kernel panic, /proc/last_kmsg will help.
Q: How do I flash this?
A: I suggest you scroll up and read the OP. The instructions are there.
Q: How do I tweak this ROM?
A: For theming, there's full OMS/Substratum support. Xposed doesn't work, so no extra tweaks for now.
Q: This kid is such a n00b!
A: Oh well then, why don't you go do something like this yourself, instead of criticizing my work and wasting your time?
Reserved again
Oh look! Another reserved post!
And as a bonus, have this nice little dark boot logo from me, which hides that dreaded "N/A" and also "bad key" things. Extract the zip file and flash the logo3.bin file inside using fastboot:
Code:
fastboot flash logo logo3.bin
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Which security pet
Official or Soak test?
Kamin4ri said:
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
[/SIZE]
Click to expand...
Click to collapse
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
I can tell you that this build work very well in european distribution (reteu).
Basicly everything work including sim and nfc(paying not tested yet)
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Also not able to download, please offer another download Location!
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
ilovepanda said:
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Click to expand...
Click to collapse
No. Your bootloader will be updated if, and only if, you install via fastboot and actually execute the respective command.
[email protected] said:
Official or Soak test?
Click to expand...
Click to collapse
This is the official firmware released for retla (Latin America). However, the soak tests in Brazil haven't finished yet. I'll update the OP with the link for the Brazilian firmware as soon as it's available.
NZedPred said:
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
Click to expand...
Click to collapse
Thank you, friend! I'll be definitely using that guide again.
7opex0 said:
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
Click to expand...
Click to collapse
Only if you're flashing via TWRP. If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
giugiura said:
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Click to expand...
Click to collapse
dau999 said:
Also not able to download, please offer another download Location!
Click to expand...
Click to collapse
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Kamin4ri said:
If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
Click to expand...
Click to collapse
Okay then! Thanks for information.
7opex0 said:
Okay then! Thanks for information.
Click to expand...
Click to collapse
Not at all!
Kamin4ri said:
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Click to expand...
Click to collapse
Please upload it on some other cloud so that we can download it thanks for help sir
In advance
Hey Guys,
I´m using a Motorola One xt1941-4. I tried to flash my phone since extensive googling suggested that this would be the only remedy for the issue of my phone only charging in fastboot mode.
I tried to do this with a locked bootloader since the $ fastboot oem get_unlock_data return failed: Unlock data unavailable. I flashed with what was the newest update from the lolinet servers via the sequence of commands given in the servicefile. During that i was unable to flash the boot.img though, which is, I imagine due to the locked bootloader. i still went through with the flashing.
Obviously it didn´t work though since my phone is now alwys going directly into fastboot showing this:
AP Fastboot Flash Mode (Secure)
SSM: boot image roll back: 11,12
failed to validate boot image
I thought this might be because i have to flash the exact firmware update i had installed preflash. I´m not sure which one that was though. I tried to flash all the available firmware on lolinet for my xt1941-4 to get the correct one- unsuccessfully. Help?
PirxRaumpilot said:
Hey Guys,
I´m using a Motorola One xt1941-4. I tried to flash my phone since extensive googling suggested that this would be the only remedy for the issue of my phone only charging in fastboot mode.
I tried to do this with a locked bootloader since the $ fastboot oem get_unlock_data return failed: Unlock data unavailable. I flashed with what was the newest update from the lolinet servers via the sequence of commands given in the servicefile. During that i was unable to flash the boot.img though, which is, I imagine due to the locked bootloader. i still went through with the flashing.
Obviously it didn´t work though since my phone is now alwys going directly into fastboot showing this:
AP Fastboot Flash Mode (Secure)
SSM: boot image roll back: 11,12
failed to validate boot image
I thought this might be because i have to flash the exact firmware update i had installed preflash. I´m not sure which one that was though. I tried to flash all the available firmware on lolinet for my xt1941-4 to get the correct one- unsuccessfully. Help?
Click to expand...
Click to collapse
Try fastboot getvar all command.
It should at least give you info about which update channel you're on and probably fingerprint as well. This would hopefully help in finding the right firmware for your device.
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
UPDATE: ive gotten everything sorted. no more bootloop. touchscreen working. connecting to lmsa. and rooted. Thank you for all the responses.
I think what happened is that when i started all this i was not using the latest adb. That seemed to not be an issue for unlocking bootloader, but a major issue for rooting. When i tried to root,i got the no touchscreen. So I followed directions and went to manually flash the stock firmware. I didnt know how to do this and couldnt find instructions for the g power. but did find instructions for the g8 power and assumed it would be the same...its almost the same, but not, so i got the bootloop.
These are the instructions:
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
I added fastboot flash super super.img_sparsechunk.15, because the g8 power only has 14 sparsechunks and thats why i kept getting the bootloop. very stupid mistake that was driving me nuts! Once i added that 15th line the phone booted up and touchscreen worked again.
Then i installed magisk manager. Took the boot.img file from my stock rom and put it on my phone. back in magisk i clicked on install a patch file, chose the boot.img and created a magisk_patched.img which i put back into the adb folder i previously used to flash the firmware.
Then went back to fastboot and flashed the magisk_patched.img and the phone is now working and rooted...THANK GOD
cnoevl21 said:
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
Click to expand...
Click to collapse
Flash stock ROM manually, it will fix the problem
riyan65 said:
Flash stock ROM manually, it will fix the problem
Click to expand...
Click to collapse
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
cnoevl21 said:
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
Click to expand...
Click to collapse
I just ran into the same problem and asked you about it in the other thread. Right after, I tried the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC and got my touchscreen back.
https ://mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
haanjamin said:
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
Click to expand...
Click to collapse
good info to know. but now ive gone i screwed my phone up even worse. cuz now im stuck in boot loop. i was trying 105-5, but ill try 51-5, then -8. maybe one of them is the right stupid firmware for my phone
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
mingkee said:
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
Click to expand...
Click to collapse
ive tried this. i either dont have (and dont know) which is the correct rom. or some other issue. i can get into fastboot mode, no problem. but when i type fastboot reboot fastboot i get that long list of commands, as if im typing in a bad command. and it does not go into fastbootd. i can, however, get into fastbootd through recovery. but every time i try to flash something there, it fails (no file or directory).
And i cant use LMSA cuz when i try to connect, it says the phone has incorrect firmware.