Related
Frequently Asked Questions
Motorola Moto X(2014)
Guys this is a FAQ for Moto X(2014). Please read this here before posting it in the developmental section or creating a thread anywhere.
I am sure it will help.
Thank You
A big thanks goes to @matmutant for providing FAQ templates and his own FAQ from I have copied some things.Here is the original guide
[SIZE=+1]Q1: How to access Fastboot?[/SIZE]Hold PowerButton and VolDown during boot.
[SIZE=+1]Q2: How to unlock Bootloader?[/SIZE]Boot to Fastboot and follow my guide
or Motorola guide on Motorola's website
[SIZE=+1]Q2: How to relock Bootloader?[/SIZE]Boot to Fastboot and give the command "fastboot oem lock"
[SIZE=+1]Q3: How do i get adb and fastboot drivers ?[/SIZE]For windows, follow this guide or this one
although, it seems Motorola Device Manager works ok for win7x86-32 (but not for win7x64-64?) i cannot answer this i'm under linux
other USB drivers if first method failed, source
For Linux, get fastboot files here also, adb and fastboot can be installed using repos for ubuntu-based distros packages needed are : android-tools-adb and android-tools-fastboot (android-tools-fsutils may be useful too)
eg:
Code:
sudo apt-get install android-tools-fastboot
[SIZE=+1]Q4: How to flash Stock Firmware?[/SIZE]Please Follow this Guidehere.
[SIZE=+1]Q5: How to Root my device ?[/SIZE]First you'll need to unlock your bootloader,
then follow this [TO BE UPDATED] guide[/URL]
[/URL]
[SIZE=+1]Q6: Where can i find a Custom recovery ?[/SIZE][TO BE UPDATED]
[SIZE=+1]Q7: How to access bootloader?[/SIZE]- Via ADB :
Code:
adb reboot bootloader
- The hard(ware) way :
With the phone powered off, press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
[SIZE=+1]Q8: How to access recovery?[/SIZE]
using terminal, if the device is already rooted
Code:
su
reboot recovery
via adb
Code:
adb reboot recovery
via bootloader
boot to bootloader (see Q11) and select recovery (use Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select)
[SIZE=+1]Q9: How to force reboot my frozen device?[/SIZE]
Press and hold the Power button for 10 - 20 seconds, the device will restart and go through the boot-up sequence [source]
(VOL DOWN hold + a quick tap on POWER should force reboot when in bootloader) [source]
[SIZE=+1]Q10: How to charge my device and extend battery life?[/SIZE]Follow Motorola tips:
How do I properly charge my device?
How can I extend my battery life?
[SIZE=+1]Q11: Does rooting/unlocking your phone invalidate its warranty? (In EU)[/SIZE]In short: No. Just the fact that you modified or changed the software of your device, is not a sufficient reason to void your statutory warranty. As long as you have bought the device as a consumer in the European Union.
For Indian customers, The warranty is void if you unlock/root your device. Motorola also reserves the right to maintain the records of unlocked bootloader devices. So you may not even get the warranty by relocking the device
[source]
[SIZE=+1]Q12: What to do if my battery is fully discharged and not re-charging?[/SIZE][source]
[SIZE=+1]Q13: Lost IMEI ? : How to backup / restore PDS partition and why?[/SIZE]On Motorola devices the 'pds' partition contains information specific to your machine: IMEI, MAC address, serial number, etc. This partition can be lost by accidental format or over time due to filesystem corruption. If you have made a backup, there is a good chance you can bring your handset back to life.
==> PDS backup will help to restore lost IMEI. It is a situation when the phone reports that the IMEI is unknown. ; This works like a vaccine, apply before having issue with IMEI, after it will be too late !
Instructions:
**Root Required**
Using ADB you can make a copy of the partition and move it to a safe place (Google Drive?):
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/pds of=/sdcard/pds.img
To restore in the event of corruption or loss:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds(assuming you've pushed pds.img to internal SDcard storage first)
If for some reason this doesn't work, maybe your IMEI isn't destroyed but only not "readable" by system (file system issue? misread cluster reading frame ? no idea), in that case you may read the following story : http://forum.xda-developers.com/showthread.php?p=52648789
[SIZE=+1]Q14: How to disable/enable auto On/Off screen with Flip Shell?[/SIZE]
for stock rom : (disabling, since it's enabled by default)
install Xposed framework (and reboot)
install and enable MotoMagnetOff (and reboot)
Follow this FAQ
[SIZE=+1]Q15: How to remove the 'unlocked warning' message?[/SIZE]Follow this Method and default Motorola logo will be back .
[SIZE=+1]Q16: How to reboot into 'safe mode'?[/SIZE]
Press power button, on the pop up, either keep pressing 'shut down' [stock] or 'reboot' [AOSP based]
more infos about this feature
[SIZE=+1]Q17: What are the Moto X(2014) tech specs[/SIZE]
XT1092 [SINGLE SIM, GSM]
[SIZE=+1]Q18: How to get OTA updates even after Rooting and Flashing a custom Recovery[/SIZE]
Use the full unroot option from the Super Su
Flash the stock recovery Use Code : mfastboot flash recovery recovery.img
Now you'll be able to get OTA updates as before
[SIZE=+1]Q1: How to Unlock Advanced Camera Settings?[/SIZE]
Refer to this thread
Reserved---2
Reserved ---3
Can I use Googles android SDK version of adb to make a complete backup of my phone (all partitions)? I followed Motorola instructions to unlock the boot loader successfully, but I'm not feeling confident going any further like I did with Nexus phones, because Nexus devices had complete support with the factory images, custom recoveries, and active custom ROM community. I miss the full immersive screen mode, but have reservations about corrupting a sensor driver and not being able to get the phone back to stock. Maybe I'm out of my league, and should just sit on the bench for this tweak.
Sent from my XT1095 using Tapatalk
OP Updated
This thread is ready to use. Please make it a sticky
Do all these apply to all versions of the 2014 Moto X? Specifically can I unlock the bootloader / root my Verizon Moto X (regular edition)?
l0aded said:
Do all these apply to all versions of the 2014 Moto X? Specifically can I unlock the bootloader / root my Verizon Moto X (regular edition)?
Click to expand...
Click to collapse
Unlocking boot loader is only supported by the pure version
Falcon G said:
Unlocking boot loader is only supported by the pure version
Click to expand...
Click to collapse
Does this mean there is no way to unlock the regular (Verizon) version (and as such, no way to root on 4.4.4/new purchase)?
Usquanigo said:
Does this mean there is no way to unlock the regular (Verizon) version (and as such, no way to root on 4.4.4/new purchase)?
Click to expand...
Click to collapse
Correct Verizon is locked down. Don't know about root.
Sent from my XT1095 using XDA Free mobile app
Usquanigo said:
Does this mean there is no way to unlock the regular (Verizon) version (and as such, no way to root on 4.4.4/new purchase)?
Click to expand...
Click to collapse
Not as of now
at&t android 5.0 update
Does anyone know when at&t models get android 5.0
What's the latest / recommended baseband version to use? I upgraded my XT1095 to 5.0 from TWRP backup and my baseband in settings is MSM8974BP_2147.127.04.57R,VICTARA_TMO_CUST . If I had to guess I think this is the 4.4.4 baseband without the additional LTE freqs. If I'm on an old baseband, is there a thread I've missed that explains upgrading it?
Thanks!
What is the model # for the US GSM Pure Edition Moto X..
XT10??
Waiting on the N6 64GB availability.. but will probably order a Moto X next week, and wanna study up on the model #..
Thank you..
sent by my:
5.0.1_22.21.16 Titan Prime
v1.2 BETA retus
Thanks: Shawn5162
XT1064 Moto G (2nd Gen.)
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
NWKENT said:
What is the model # for the US GSM Pure Edition Moto X..
XT10??
Waiting on the N6 64GB availability.. but will probably order a Moto X next week, and wanna study up on the model #..
Thank you..
sent by my:
5.0.1_22.21.16 Titan Prime
v1.2 BETA retus
Thanks: Shawn5162
XT1064 Moto G (2nd Gen.)
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Click to expand...
Click to collapse
XT1095
From this it looks like it should be possible to unroot on Lollipop and apply an OTA; hoping this is correct! I am on .11 right now and rooted but stock recovery. Would hate to have to wipe to apply the next OTA whenever it comes out.
Is there a custom kernel for the Moto X 2014?
Is there a way to reduce the sensitivity of the Moto display? It turns on with the slightest movement (in a bag or pocket its always on) I switched it to ambient display so it won't keep going off. I like the moto display but its draining the battery with the erratic behavior.
Pilz said:
Is there a way to reduce the sensitivity of the Moto display? It turns on with the slightest movement (in a bag or pocket its always on) I switched it to ambient display so it won't keep going off. I like the moto display but its draining the battery with the erratic behavior.
Click to expand...
Click to collapse
Same here, started a thread though.
Hello guys,
Like many of you my Moto G XT1068 is dead because of downgrading from XT1069 MM 6.0 SOAK test Firmware to 4.4.4 and OTA update to 5.0.2 leaving it to "QualComm Emergency Download Mode" a.k.a Qualcomm Hs Usb Qdloader 9008 . For past several days I was experimenting with Blank-Flash Method available for Moto G (1st gen only). I am a full Linux/Ubuntu Guy. What I have found is that there are two files to construct, Programmer.mbn and Singleimage.bin for XT1068.
I am experimenting with possible replacement of SBL1 in Programmer.mbn and tz, rpm, DDR,and SBL1 partitions found in the singleimage.bin. But what I don't know as my device is hard-bricked is the full partition layout.
Is there anybody (rooted) willing enough to give the following info+dump of partition layout for XT1068 variant then I can try to integrate it those two files.
What you need to do is simple enough, just follow the instructions:
Requirements: Rooted XT1068
App: Partitions Backup & Restore
Instructions:
Start the app with root permission.
Backup All the partitions except SYSTEM (If you have enough space)
Upload the partitions to somewhere (If possible try Mega or Google Drive for faster speed)
Provide Screenshots of the partitions from that app screen.
You can also create 100mb of partitions dump. Click on the options in the app and click "Backup first partitions".
Please mention which Firmware you are using for instance 4.4.4 or 5.0.2 or 6.0, If possible give a Screenshot of Settings >> "About device".
If you know how to use adb then please provide the partition info, follow this wonderful instructions from this XDA thread [GUIDE] Making Dump Files Out of Android Device Partitions. Provide Screenshots like this post and if possible you can also provide me the dump data.
PS:
## I know the programmer.mbn and singleimage.bin is checksum protected, I will try to look into that later.
## Its quite impossible to accomplish what I am trying to do to help me and so many of other left there device as a paper weight, but you will never know if you don't try.
## Please don't raise your hope yet and please comment only technical info if you wanna help, so that moderator won't close this thread.
## This is my first post, so If I break any posting rules, forum moderator please let me know and If it is on wrong forum then move this thread to the right one.
I am looking forward to your help. Thanks in advance.
[Reserved]
I will post my findings related to blank-flash in future here.
UPDATE: 1
Creating singleimage.bin is easy enough. Its basically a gtp partition disk image with four patitions - Aboot, DDR, tz and rpm. If you have linux(ubuntu/Centos) editing this partition to include Aboot(emmc_appsboot), tz and rpm from OTA(4.4.4/5.0.2/6.0) update of Moto G 2014 is easy enough using gdisk tools in linux. I have already created that but the problem is that qboot utility doesn't pass to send singleimage.bin to phone. If anyone want I will give a full guide to create singleimage.bin.
Problem: The main problem is creating the programmer.mbn file. Recreating it is quite impossible if we don't get it from leak. I guess the existing programmer.mbn from Moto G (1st gen) is that it possibly check for bootloader, device id etc. There are a lot of posts about these topics in XDA, If anyone interested just search for the keywords singleimage.bin, mprg8226, Sahara protocol, PBL, Qualcomm qDloader 9008 commands etc.
Status:
with all the informations I gathered this week is that the unbricking a Hard-Brick Qualcomm device process is like follows:
flasher send the Flash Programmer (file) to phone in 9008 mode.
send signal to restart(possibly) phone and execute Flash Programmer (programmer.mbn in our case). It is a bootloader for rescuing phone to flash gpt partion containing second bootloader SBL1 and fastboot in aboot partition.
If you want to see what exactly is sent to your phone and the response the moto g gives after using qboot, use this command to execute qboot:
In Windows (Edit blank-flash.bat )
qboot.exe --debug=2 blank-flash
pause
In Ubuntu (from terminal)
./qboot --debug=2 blank-flash
you will see in the verbose debug output that phone stuck at executing programmer.mbn before accepting singleimage.bin.
Linux guy here too.
So, roughly you want to know every partition's size and content to make a new partition table? Dumping every partition with adb should be relatively easy. I'd like to help you, but I'm on Minimal OS 5.1.1, XT1063, with Lollipop bootloader. I don't know if the hardbrick problem is only related to XT1068 phones though, as I tried before to downgrade to kitkat's bootloader and nothing happened.
[HELP] Need Partition Layout Info+Dump of XT1068 for re-creating blank-flash
Hello
I have a blocked xt1068. And I want to participate, I start working with Qualcomm QPST.
I'm missing some information for a used wisely.
I am French. sorry for bad English.
DepressedDead said:
Linux guy here too.
So, roughly you want to know every partition's size and content to make a new partition table? Dumping every partition with adb should be relatively easy. I'd like to help you, but I'm on Minimal OS 5.1.1, XT1063, with Lollipop bootloader. I don't know if the hardbrick problem is only related to XT1068 phones though, as I tried before to downgrade to kitkat's bootloader and nothing happened.
Click to expand...
Click to collapse
hardbrick problem is not related to XT1068. It happened for Moto G(1st gen also) also for downgrading from Lolliop => Kitkat or MM => Kitkat then OTA update to Lollipop. I looked at the OTA, contains bootloader update and gpt partition. maybe updating a bootloader through OTA from a downgrade caused the problem though sounds silly.
previously I flashed XT1063 Lollipop SOAK test to my XT1068 and it worked like charm, though I didn't flash the bootloader. SO, I think it wouldn't be much problem to use XT1063's partition layout. I guess they wouldn't be much different.
If you have time please provide me your partition info + dump. At least I would get some idea about the gpt partition map
Finger Slensh said:
Hello
I have a blocked xt1068. And I want to participate, I start working with Qualcomm QPST.
I'm missing some information for a used wisely.
I am French. sorry for bad English.
Click to expand...
Click to collapse
QPST won't work I guess. LG, ONEPLUS, HTC have same mechanism but motorolla have different implementation of Qualcomm emergency download mode. Read these links are useful.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload/
and
http://www.androidbrick.com/unbrick-all-qualcomm-snapdragons-from-qualcomm-hs-usb-qdloader-9008-if-you-have-the-right-kind-of-rom-qhsusb_dload/
@kernelpanic.bd
There's some info about the partitions. I'll upload 34 (out of 39) images of almost every partition in a few hours, or maybe minutes. Except for recovery, userdata, system, boot, and cache. Ya' know, they're pretty useless since there are already images of those partitions, although if you want I could upload them (it would take me an eternity), or you could ask to someone else with better bandwith to dd those partitions since they're pretty large (500mb+).
Please hold on.
[EDIT]
What I've backed up: abootBackup, aboot, cid, clogo, ddr, deviceinfo, dhob, fsc, fsg, ftmlog, hob, kpan, logo, logs, misc, modem, modemst1, modemst2, padA, padB, pds, persist, rmp, rpmBackup, sbl1, sdi, sdiBackup, sp, ssd, tz, tzBackup, utags, utagsBackup, mmcblk0rpmb (this one isn't shown in parted).
What I didn't back up: boot, cache, recovery, system, userdata
Here's the link.
Please note that even if the .tar.gz is only around 25mb it'll be 130mb once you extract it. I've added detailed outputs in .txt files and a checksums.md5 file, so don't forget md5sum -c checksums.md5 to check all the files. As I don't know which extension should be used for every partition I left them all without extension, which I don't think that could be a big deal. If it is, then I'll be using FlashFire (I didn't use it because it only shows 20 partitions, when really there are more than 39 in our device).
If there's any corrupted dd'ed file please tell me.
More info: XT1063, Minimal OS 5.1.1, Lollipop bootloader.
DepressedDead said:
@kernelpanic.bd
There's some info about the partitions. I'll upload 34 (out of 39) images of almost every partition in a few hours, or maybe minutes. Except for recovery, userdata, system, boot, and cache. Ya' know, they're pretty useless since there are already images of those partitions, although if you want I could upload them (it would take me an eternity), or you could ask to someone else with better bandwith to dd those partitions since they're pretty large (500mb+).
Please hold on.
[EDIT]
What I've backed up: abootBackup, aboot, cid, clogo, ddr, deviceinfo, dhob, fsc, fsg, ftmlog, hob, kpan, logo, logs, misc, modem, modemst1, modemst2, padA, padB, pds, persist, rmp, rpmBackup, sbl1, sdi, sdiBackup, sp, ssd, tz, tzBackup, utags, utagsBackup, mmcblk0rpmb (this one isn't shown in parted).
What I didn't back up: boot, cache, recovery, system, userdata
Here's the link.
Please note that even if the .tar.gz is only around 25mb it'll be 130mb once you extract it. I've added detailed outputs in .txt files and a checksums.md5 file, so don't forget md5sum -c checksums.md5 to check all the files. As I don't know which extension should be used for every partition I left them all without extension, which I don't think that could be a big deal. If it is, then I'll be using FlashFire (I didn't use it because it only shows 20 partitions, when really there are more than 39 in our device).
If there's any corrupted dd'ed file please tell me.
More info: XT1063, Minimal OS 5.1.1, Lollipop bootloader.
Click to expand...
Click to collapse
You completely rock . Yes, I don't need cache, recovery, system, userdata but if possible please upload boot.img, motoboot.img and gpt.bin of the firmware you flashed and using now.
bro issue the parted command on mmcblk0
parted /dev/block/mmcblk0
then in the parted menu write "p" to print partition layout with size info and gimme an screenshot of that or the output in a text file. I will possibly update my post with my theory and screenshots of my findings maybe tomorrow or the next day. Thanks again, much appreciated.
If you guys get this right and fix all these bricked xt1068 phones I'll give you a million thanks here !!
@kernelpanic.bd
I used this to update my bootloader, then flashed again the whole stock 4.4.4 rom because there was no mobile signal. What's strange is that it didn't let me downgrade the bootloader and there was a warning about mismatched partitions (idk), but the bootloader was indeed updated.
https://mega.nz/#F!wtlQGQoK!bOrNQEpvYzIKmB68V3qPEg!58tSmQyI
boot (KK), motoboot (KK), gpt.bin (KK) from my stock 4.4.4 carrier rom used to recover mobile signal + current dde'ed boot image.
https://mega.nz/#!y9xCWYgL!6d8biMw1OXOjJqr-wyEgUI2P2grYJiEJX7rnx2bYEFY
Thanks. Downgrading to 4.4.4 doesn't create any issue. If you then upgrade to 5.0.2 through ota that's cause the hradbrick. Mine was fine flashing 4.4.4 from 6.0 xt1069 SOAK test fw. But when I update from 4.4.4 to 5.0.2 ota through the default recovery, it was hard bricked.I guess the bootloader and gpt.bin in the 5.0.2 OTA causes this issue.
kernelpanic.bd said:
Thanks. Downgrading to 4.4.4 doesn't create any issue. If you then upgrade to 5.0.2 through ota that's cause the hradbrick. Mine was fine flashing 4.4.4 from 6.0 xt1069 SOAK test fw. But when I update from 4.4.4 to 5.0.2 ota through the default recovery, it was hard bricked.I guess the bootloader and gpt.bin in the 5.0.2 OTA causes this issue.
Click to expand...
Click to collapse
I concur completely.. That's exactly what happen to my phone too.
same
garyben60 said:
I concur completely.. That's exactly what happen to my phone too.
Click to expand...
Click to collapse
I'm in the same case
I found files here ....but they are moto g 2013
https://mega.nz/#!rgoSGS7B!d2LKiBm29aSSy9dYxy-4aQutjcA5Vwy6bcAE9Sh3nLY https://mega.nz/#!rgoSGS7B!d2LKiBm29aSSy9dYxy-4aQutjcA5Vwy6bcAE9Sh3nLY
updated my findings in the second post.
kernelpanic.bd said:
updated my findings in the second post.
Click to expand...
Click to collapse
.. Sorry I saw one update on #2. Is there anything further? I Wish I knew more about this so I could also help
when you guys solve the problem . can tell me ? My gmail- [email protected] thank you...
no solution......
We still waiting :crying::crying::crying:
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
kernelpanic.bd said:
updated my findings in the second post.
Click to expand...
Click to collapse
plz check out this link bro.. is it working for xt1068 or not..?
and jst wanted to know that are u still working for the blankflash or started waiting for a superman to come with a solution jst like us
c_/\/\_k said:
plz check out this link bro.. is it working for xt1068 or not..?
and jst wanted to know that are u still working for the blankflash or started waiting for a superman to come with a solution jst like us
Click to expand...
Click to collapse
Not working for my moto g.
Good luck guys.
I hope they get a solution, my case was that too, to soak 6.0 4.4.4 downgrade.
Hi!. I recently received my new Moto E5 XT1944-1 and i wanted to root, unlock bootloader and everything. For that reason i enter this forum and get the TWRP recovery from de Moto E5 (James), but i dont know that the James (5,2 inch screen) is not the same that my Moto E5 (5,7 inch screen), and now the recovery seems to be corrupt and cant enter, only enter on fastboot mode. I need to say that the smartphone boots normally, but i fear the day that i need to make a full wipe and cant enter recovery. What can i do to reflash the original recovery?. Thanks to all help given.
Edit: I need to say that the bootloader is successfully unlocked, but still the problem with the recovery.
intherior said:
Hi!. I recently received my new Moto E5 XT1944-1 and i wanted to root, unlock bootloader and everything. For that reason i enter this forum and get the TWRP recovery from de Moto E5 (James), but i dont know that the James (5,2 inch screen) is not the same that my Moto E5 (5,7 inch screen), and now the recovery seems to be corrupt and cant enter, only enter on fastboot mode. I need to say that the smartphone boots normally, but i fear the day that i need to make a full wipe and cant enter recovery. What can i do to reflash the original recovery?. Thanks to all help given.
Edit: I need to say that the bootloader is successfully unlocked, but still the problem with the recovery.
Click to expand...
Click to collapse
Because the Moto E5 series is so young in terms of both its recent release and its limited support within the Android community, finding factory firmware packages is not easy right now. Typically, in your situation, simply extracting a stock recovery image from a firmware package and flashing it in fastboot would be your best remedy by far. But, if you have corrupted your recovery partition and are unable to locate a stock image, I would recommend first that you ask some members and devs on the furum to dump a stock recovery image that you could flash to fix your issue. Second, if you are rooted, make an immediate dump of your /system, /boot, /oem and /vendor partitions. That way, if your OS does decide not to boot, you can restore your partition dumps via fastboot (as long as your bootloader is unlocked). If you are not rooted and are thus unable to dump your key partitions, I'd advise to just be really careful in terms of modding or tweaking your stock OS. Firmware packages will likely be available by September, maybe sooner. Until then, reach out and ask some members & devs if they can provide you with a stock recovery image. Good luck...
First, thanks for your fast reply. My phone isn't rooted yet, i stop doing the guide of the James version because i think i do it worst. I can test the Kingroot app o whetever it names, but i prefer to wait and stop installing apps (only the basic: Telegram, Youtube, etc for daily use). I dont know who Devs or Members have this system. But i will stay reading this section of forum everyday to stay update of the news. Thanks for all pal!.
Edit: Sorry for my bad english, i'm spanish and dont know so much
intherior said:
First, thanks for your fast reply. My phone isn't rooted yet, i stop doing the guide of the James version because i think i do it worst. I can test the Kingroot app o whetever it names, but i prefer to wait and stop installing apps (only the basic: Telegram, Youtube, etc for daily use). I dont know who Devs or Members have this system. But i will stay reading this section of forum everyday to stay update of the news. Thanks for all pal!.
Edit: Sorry for my bad english, i'm spanish and dont know so much
Click to expand...
Click to collapse
It's ok friend. I understand you good. I am currently developing for the James xt1921-5 (Boost/Virgin/Sprint) variant and, as such, I am keeping a close watch for factory firmware to be released for the James. I will contact you as soon as I can confirm a firmware source for your particular model (xt1944-1). Currently, there are only paid subscription-type repositories which offer firmware downloads online. I don't recommend or support sources that charge a fee for firmware. But, it won't be long. September at the latest, possibly sooner.
MotoJunkie01 said:
It's ok friend. I understand you good. I am currently developing for the James xt1921-5 (Boost/Virgin/Sprint) variant and, as such, I am keeping a close watch for factory firmware to be released for the James. I will contact you as soon as I can confirm a firmware source for your particular model (xt1944-1). Currently, there are only paid subscription-type repositories which offer firmware downloads online. I don't recommend or support sources that charge a fee for firmware. But, it won't be long. September at the latest, possibly sooner.
Click to expand...
Click to collapse
Thank you so much!. I will stay update to any news here. I know that this model is so soon, my network provider offers me this, and cause i allways use Motorola (Moto E1, Moto G, Moto G2014), then i accept thinking that the scene was more advanced. My surprise when i see that this version was recently released...
Well, then it's time to wait to see how the scene grow up.
Regards pal!.
intherior said:
Thank you so much!. I will stay update to any news here. I know that this model is so soon, my network provider offers me this, and cause i allways use Motorola (Moto E1, Moto G, Moto G2014), then i accept thinking that the scene was more advanced. My surprise when i see that this version was recently released...
Well, then it's time to wait to see how the scene grow up.
Regards pal!.
Click to expand...
Click to collapse
Great news @intherior -- Motorola Mobility has leaked some factory firmware packages for yours and a few other variants. I'll be posting a thread with download links by tomorrow evening. In fact, here is you a link to the specific file you need -- the stock recovery image for the xt1944-1. You can flash this via fastboot mode by:
fastboot flash recovery recovery.img
Link: https://drive.google.com/file/d/17sgV8t6jYgahml6Huv3Hq2IgygqJZnsH/view?usp=drivesdk
Yeah!!! That's really very good news!. I'm not at home now, but this night i Will download and comment if it fix my problem. Thank u so much bro!
Edit: One picture is better that thousand words xD
Thank u bro!. Finally was fixed with the recovery u posted!. Now i take care from do something stupid. I will wait to a stable and probed version of TWRP to finally get my Moto E5 Xt1944-1 rooted. But for now i will take it easy.
Regards my friend! :fingers-crossed:
intherior said:
Yeah!!! That's really very good news!. I'm not at home now, but this night i Will download and comment if it fix my problem. Thank u so much bro!
Edit: One picture is better that thousand words xD
Thank u bro!. Finally was fixed with the recovery u posted!. Now i take care from do something stupid. I will wait to a stable and probed version of TWRP to finally get my Moto E5 Xt1944-1 rooted. But for now i will take it easy.
Regards my friend! :fingers-crossed:
Click to expand...
Click to collapse
Very glad the stock recovery worked for you. I have an entire stock firmware package for your device if you ever need it to restore your device to factory state. Just let me know and I'll upload and post a link. Cheers...
Sure bro!. Will be good to keep that firmware safe if I have any problem. Give me the download link when you have time. Thanks again!
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
dmilz said:
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
Click to expand...
Click to collapse
Sorry for mb inappropriate question: Do you have a physical device? If you do, did you unlock and root it (cos i have some issues with that)?
irewer said:
Sorry for mb inappropriate question: Do you have a physical device? If you do, did you unlock and root it (cos i have some issues with that)?
Click to expand...
Click to collapse
Yes i do..
I unlocked bootloader and rooted
dmilz said:
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
Click to expand...
Click to collapse
Have you figured the problem out yet? Is there any other known custom ROMs working on Pomelo? Also how did you do it? I don't see Montana in Downloads section for the ROM.
sixtheninth said:
Have you figured the problem out yet? Is there any other known custom ROMs working on Pomelo? Also how did you do it? I don't see Montana in Downloads section for the ROM.
Click to expand...
Click to collapse
No, i didnt get the chance to figure it out as i broke my moto screen completely. There are no custom roms for the xt-1799-2, wish i had shared it. But if you are interested you can easily port the roms for any moto g5s over to your xt-1799-2
dmilz said:
No, i didnt get the chance to figure it out as i broke my moto screen completely. There are no custom roms for the xt-1799-2, wish i had shared it. But if you are interested you can easily port the roms for any moto g5s over to your xt-1799-2
Click to expand...
Click to collapse
Yeah, I am very interested. I tried RR, LineageOS, Viper for other montanas, all crashed after boot back into bootloader. Also I'd be interested getting Oreo based ROMs. So far I m stuck with chinese ZUI 3.1 which prevents me from flashing or installing Gapps.
sixtheninth said:
So far I m stuck with chinese ZUI 3.1 which prevents me from flashing or installing Gapps.
Click to expand...
Click to collapse
You can unclock (XT1799-2 may be 'secretly' unlocked already), root your device, flash custom TWRP (escpecially for Moto G5S XT1792/1794 and Green Pomelo XT1799-2) - and then you'll be able to install Open GApps via TWRP/root.
Also you can simply open special Lenovo App Store on your ZUI-based phone (look for it carefully!), install Google Store's apk from out there - and be enjoying with any GApps and other official apk's.
sixtheninth said:
Also I'd be interested getting Oreo based ROMs.
Click to expand...
Click to collapse
If you will flash bootloader version 07 (not 06 as you have on any available ZUI stock ROMs), you'll be able to flash distinct Oreo firmware (XT1792 for Brasil/India/EU) in straight way (thread 1; thread 2). BUT YOU'RE GOING TO LOSE NFC and SELFIE-CAMERA in cause of special drivers lack!!! And you will have no way for downgrading of firmware in cause higher version bootloader.
* also you would prefer to flash Moto G5s' stock Android 7.1.1 firmaware (XT1794) on your Green Pomelo (XT1799-2), using this manual.
** stock Green Pomelo's ZUI-based Android 7.1.1 firmware you can find here
irewer said:
You can unclock (XT1799-2 may be 'secretly' unlocked already), root your device, flash custom TWRP (escpecially for Moto G5S XT1792/1794 and Green Pomelo XT1799-2) - and then you'll be able to install Open GApps via TWRP/root.
Also you can simply open special Lenovo App Store on your ZUI-based phone (look for it carefully!), install Google Store's apk from out there - and be enjoying with any GApps and other official apk's.
If you will flash bootloader version 07 (not 06 as you have on any available ZUI stock ROMs), you'll be able to flash distinct Oreo firmware (XT1792 for Brasil/India/EU) in straight way (thread 1; thread 2). BUT YOU'RE GOING TO LOSE NFC and SELFIE-CAMERA in cause of special drivers lack!!! And you will have no way for downgrading of firmware in cause higher version bootloader.
* also you would prefer to flash Moto G5s' stock Android 7.1.1 firmaware (XT1794) on your Green Pomelo (XT1799-2), using this manual.
** stock Green Pomelo's ZUI-based Android 7.1.1 firmware you can find here
Click to expand...
Click to collapse
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
---------- Post added at 10:31 AM ---------- Previous post was at 10:23 AM ----------
sixtheninth said:
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
Click to expand...
Click to collapse
Update, I just fastboot flashed the Firmware from the links provided, but managed to hard brick my phone!!!!!! ((( Don't know what to do now.
careful with flashing other moto g5s model roms on the xt-1799-2, its different and so you might get a brick. The best you can do is port like i said. You can unlock bootloader by "fastboot oem flashing" if that doesnt work for you try "fastboot oem unlock". I will be back on the pomelo xt-1799-2 soon as i am planning to order another one. Infact you guys will need a section dedicated to the xt-1799-2
sixtheninth said:
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
---------- Post added at 10:31 AM ---------- Previous post was at 10:23 AM ----------
Update, I just fastboot flashed the Firmware from the links provided, but managed to hard brick my phone!!!!!! ((( Don't know what to do now.
Click to expand...
Click to collapse
Hope this helps to unbrick
http://motog5szuirom.blogspot.com/2018/01/zui-31-for-moto-g5s-stock-rom.html
dmilz said:
careful with flashing other moto g5s model roms on the xt-1799-2, its different and so you might get a brick. The best you can do is port like i said. You can unlock bootloader by "fastboot oem flashing" if that doesnt work for you try "fastboot oem unlock". I will be back on the pomelo xt-1799-2 soon as i am planning to order another one. Infact you guys will need a section dedicated to the xt-1799-2
Click to expand...
Click to collapse
I agree, a since it is a slightly different phone a independent section can be great. Now, I am not a developer, so things like porting ROMs is not in my skillset, but I understand that selfie cam and nfc will not work on any custom ROM even if ported simply due to driver issue. I have rooted my phone previously, so I was past unlocking. Problem was that I soft bricked moment I pressed 'factory reset' - the phone would just endlessly keep booting into recovery mode, which was strange as it had stock ROM updated by reseller into a global version. Then I tried to flash various custom ROMs without any luck. Pretty much tried any Montana ROM I could find, but as I said, I don't know how to port so I got stuck in recovery loop. Then I found out about Oreo project and tried to fastboot flash that. That was a major mistake. It upgraded bootloader to 7 without me realising this. I found out nfc and selfie camera not working, so I wanted to downgrade to stock chinese firmware and just install gapps manually. After I fastboot flashed the nougat firmware - my phone hard bricked and won't even respond it seems dead. Thus your link will not help. Anyway I am already on a mission to try to revive it using following method: https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1
Thank you anyway and if by chance you stumble upon some cool compatible ROM or to be honest a ROM that works really good - I don't really need NFC, but fingerprint scanner, turbo charger, selfie camera and reasonable battery management (some ROMs apparently drain it too quickly) would surely be features to keep. Also, if you have at hand a guide on how to port these roms which I can learn, I'd be very grateful.
Thank you
Six
sixtheninth said:
Problem was that I soft bricked moment I pressed 'factory reset' - the phone would just endlessly keep booting into recovery mode ...
Click to expand...
Click to collapse
At the moment you could use TWRP menu* 'Reboot - Bootloader' to boot in Fastboot Flash Mode (yes, it's bootloader) - and then press Power button (with 'START' tag in front of it).
But you have preferred to experiment ... You lost bootloader in due of custom 'chinese suppliers' firmware (non-original ROM) and forbidden factory reset with it.
* if you had stock recovery, you need to change mode with Volume buttons to Fastboot Flash Mode - and do the next steps in the same way; also you would be able directly to boot in Fastboot mode (bootloader) using long press Power button + Volume Down button
sixtheninth said:
... Then I found out about Oreo project and tried to fastboot flash that. That was a major mistake. It upgraded bootloader to 7* without me realising this ... I wanted to downgrade to stock chinese firmware ... my phone hard bricked and won't even respond it seems dead ...
Click to expand...
Click to collapse
I warned you in straight way at that my post with a load of links to instructions and threads ('... you will have no way for downgrading of firmware in cause of higher version bootloader ...'). But you are bustler and illiterate, pardon me. By the way... do you know English or just use Google Translate?
* I have some unapproved info that OPP28.65-37[-2] firmware even uses bootloader version 12 (BL: BC12)
sixtheninth said:
Anyway I am already on a mission to try to revive it using following method: https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1
Click to expand...
Click to collapse
Yes, it may be will help you to boot in Fastboot menu. Please, read all method instructions carefully (RTFM!!!), don't experiment on your own risk/luck.
On Russian forum we have some examples of 'reviving' XT1799-2 with XT1794 mmcblk0.img - but it's the question of bootloader version and disk partition. May be now you have either bootloader version 06 and partition again or corrupted/mixed software or something else, so may be you'll be need to use distinct XT1799-2 mmcblk0.img. I have it ('Repair' folder), but there aren't any proved mentions of it's compatibility / applicability / integrality - all our XT1799-2 'bricks' were re-covered with XT1794 mmcblk0.img finally.
If you know Russian language or wanna risk to translate with Google Tranlsate (omg, please, don't do that ) - you may use Russian 4pda forum because at this very moment it has the most full load of info about XT1799-2 flashing and repairing (yes, all Slavs are misers and adventurers) not in Chinese language.
dmilz, I sincerely beg your pardon for messing up in your RR port thread
irewer said:
At the moment you could use TWRP menu* 'Reboot - Bootloader' to boot in Fastboot Flash Mode (yes, it's bootloader) - and then press Power button (with 'START' tag in front of it).
But you have preferred to experiment ... You lost bootloader in due of custom 'chinese suppliers' firmware (non-original ROM) and forbidden factory reset with it.
* if you had stock recovery, you need to change mode with Volume buttons to Fastboot Flash Mode - and do the next steps in the same way; also you would be able directly to boot in Fastboot mode (bootloader) using long press Power button + Volume Down button
I warned you in straight way at that my post with a load of links to instructions and threads ('... you will have no way for downgrading of firmware in cause of higher version bootloader ...'). But you are bustler and illiterate, pardon me. By the way... do you know English or just use Google Translate?
* I have some unapproved info that OPP28.65-37[-2] firmware even uses bootloader version 12 (BL: BC12)
Yes, it may be will help you to boot in Fastboot menu. Please, read all method instructions carefully (RTFM!!!), don't experiment on your own risk/luck.
On Russian forum we have some examples of 'reviving' XT1799-2 with XT1794 mmcblk0.img - but it's the question of bootloader version and disk partition. May be now you have either bootloader version 06 and partition again or corrupted/mixed software or something else, so may be you'll be need to use distinct XT1799-2 mmcblk0.img. I have it ('Repair' folder), but there aren't any proved mentions of it's compatibility / applicability / integrality - all our XT1799-2 'bricks' were re-covered with XT1794 mmcblk0.img finally.
If you know Russian language or wanna risk to translate with Google Tranlsate (omg, please, don't do that ) - you may use Russian 4pda forum because at this very moment it has the most full load of info about XT1799-2 flashing and repairing (yes, all Slavs are misers and adventurers) not in Chinese language.
dmilz, I sincerely beg your pardon for messing up in your RR port thread
Click to expand...
Click to collapse
Well as irony had it, I did the operation literally seconds before I have read your warning. I was desperate of being stuck in either chinese rom or recovery loop. Anyway, I am amidst of transferring mmcblk0.img for XT1795 to my SD drive via Rufus. Problem is that it won't let me to choose GPT only MBR, so I hope that can still work. Another problem is that I don't how to check the actual bootloader version I am having there installed right now should I manage to get there.
sixtheninth said:
Another problem is that I don't how to check the actual bootloader version I am having there installed right now should I manage to get there.
Click to expand...
Click to collapse
The version of installed bootloader you can check in Fastboot Flash Mode (bootloader as actually, Power + Volume Down buttons pressing and so on).
The version of non-installed firmware you can find into special '.info' file, for example: file 'MONTANA_RETCN_NZS26.68-108_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC_montana_retcn.info' inside ZUI-based MONTANA_RETCN_NZS26.68-108 ROM has this line:
Code:
MBM Version: BC.06
I used Win 10 and Rufus on XT-1799-2 using XT-1794 and 95 files, both holding power button for over 1min but screen remained black (
sixtheninth said:
I used Win 10 and Rufus on XT-1799-2 using XT-1794 and 95 files, both holding power button for over 1min but screen remained black
Click to expand...
Click to collapse
Because there were Android 7.1.1 images of mmcblk0 with corresponding partition and bootloader version (BC.07; and you may be need BC.08-BC.12 at this moment :shrugging: ).
Have you tried XT1799-2 mmcblk0.img (7.1.1)?
Have you ever found XT1794 Android 8.1.0-based mmcblk0.img ?
[/COLOR]
irewer said:
Because there were Android 7.1.1 images of mmcblk0 with corresponding partition and bootloader version (BC.07; and you may be need BC.08-BC.12 at this moment :shrugging: ).
Have you tried XT1799-2 mmcblk0.img (7.1.1)?
Have you ever found XT1794 Android 8.1.0-based mmcblk0.img ?
Click to expand...
Click to collapse
The results so far are underwhelming. I did the operation in Linux following https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1 . Dowloaded both .img XT1794 and 95, checked the MD5 and flashed them on my sd card. Neither of them worked. Light was flashing at various intervals, but even after two minutes of holding the power button screen remained pitch black. I downloaded your image file for 1799-2, but ended with the very same result. I have not found XT1794 Android 8.1.0-based mmcblk0.img, yet. Would you know anything about it?
1799-2
Hello. I installed OREO 8.1 on MOTO 1799-22. The front camera and NSF do not work. No one will tell you the solution? Thank you friends.
nikolaiderho said:
Hello. I installed OREO 8.1 on MOTO 1799-22. The front camera and NSF do not work. No one will tell you the solution? Thank you friends.
Click to expand...
Click to collapse
But did you recover it from hard brick by using mmcblk0.img based on Oreo?
Have you done with your RR port for xt1799 yet?
I have purchased the xt1799 Green Pomelo,unlocked bootloader,and installed the twrp. I tried to flash many 7.1 Roms that were intended for g5s and always failed. please notify me if you are still working on the port.
Hey folks. I got a new Moto G7 Plus (XT1965-T) and wanted to install TWRP and custom ROM, as done on my G5 Plus. Long story short... I accidentally flashed a recovery image for my G5 Plus, and hard-bricked the phone. I managed to unbrick, thanks to luiz_neto's "[ULTIMATE GUIDE] How To Unbrick your Moto G7 Plus" post (BIG shout out). However, when in drop to Recovery Mode, TWRP v3.2.1-0 as was installed on the G5+, is displayed. The screen then locks up requiring a hard reset. I can boot to the Factory ROM and the phone functions normally, however am unable to figure out how to reinstall the OEM recovery. All procedures to revert back to full OEM seem to reference flashing a factory "Image". I can only find .zip files on the stock ROM. Any clues out there as to how I can fix this problem would be greatly appreciated?
My recommendation: Re-flash Stock ROM to get rid off of all modifications you applied so far.
jwoegerbauer said:
and incompleteMy recommendation: Re-flash Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
My thoughts too, but stock ROMS are in xml.zip fromat, and I have no idea how to install. Some guidance indicates that extracted files are manually flashed in sequence. This seems odd and instructions are incomplete. Where can the stock ROM, what will be the format, and where can I find accurate and complete instructions?
I previously had a Motorola G7 Power device and I know that's not the same device you have here but I do recall our factory images were on a server and you had to really be careful which one you installed. There were six or seven different Moto G7 power device models and that many stock rom/ images. I can help you look and try and see if there is anything out there.
What is the exact model of your device or just post a screenshot of your "about phone" in settings if you'd like.... Please tell me your build number in phone settings when you get a minute I'm trying to figure out exactly what model device you have. Sometimes Motorola can be kinda tricky.
I'm not saying these links are to firmware that is made for your device. I need to know exactly what model you have to determine that but you may want to check out these:
Sidenote: I had a Moto that had the same exact XTxxxx number as another model is why I want to be for sure about this .
[Flash ROM.bat][Android 9] Flash Stock ROM of your MOTO G7 PLUS!!!
FOR MOTO G7 PLUS ONLY!!! Hello, everyone. I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus. Just put it in the stock Rom folder along with the fastboot files and run the file. For those who...
forum.xda-developers.com
If there is anything out there I, like others here have already commented would suggest flashing the factory image /stock rom, whatever you want to call it that's made for your device and also at some point formatting data. fastboot -w
flash713 said:
I previously had a Motorola G7 Power device and I know that's not the same device you have here but I do recall our factory images were on a server and you had to really be careful which one you installed. There were six or seven different Moto G7 power device models and that many stock rom/ images. I can help you look and try and see if there is anything out there.
What is the exact model of your device or just post a screenshot of your "about phone" in settings if you'd like.... Please tell me your build number in phone settings when you get a minute I'm trying to figure out exactly what model device you have. Sometimes Motorola can be kinda tricky.
I'm not saying these links are to firmware that is made for your device. I need to know exactly what model you have to determine that but you may want to check out these:
Sidenote: I had a Moto that had the same exact XTxxxx number as another model is why I want to be for sure about this .
[Flash ROM.bat][Android 9] Flash Stock ROM of your MOTO G7 PLUS!!!
FOR MOTO G7 PLUS ONLY!!! Hello, everyone. I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus. Just put it in the stock Rom folder along with the fastboot files and run the file. For those who...
forum.xda-developers.com
If there is anything out there I, like others here have already commented would suggest flashing the factory image /stock rom, whatever you want to call it that's made for your device and also at some point formatting data. fastboot -w
Click to expand...
Click to collapse
Device is a Moto G7 Plus model: XT1965-T. It is/was Android 10. I thought I had a good stock rom and flash procedure, but following a latenight attempt, I was obviously wrong. I am now stuck in a boot-loop. I can still get to fastboot and it is recognized adb tools., but that is it. Step one, get the build number before 'zucking' with it. Blew that! Would understand if you walked. Anyway, if your still here, I think the ROM is correct, Motorola_Moto_G7_Plus_XT1965-T_RETUS_LAKE_QPWS30.61-21-18-7-3_10.zip from motostockrom.com. If so, I obviously have no idea how to flash using adb tools and fastboot. Also, I see ROMs ending in .xml.zip, vice .zip. Just packaging? Where to from here? Frame it and find a wall? I'll hold off a couple of days before zucking with it some more. I have a septic tank lid to fix. Way more fun and greater chance of success!
cliffgi said:
Device is a Moto G7 Plus model: XT1965-T. It is/was Android 10. I thought I had a good stock rom and flash procedure, but following a latenight attempt, I was obviously wrong. I am now stuck in a boot-loop. I can still get to fastboot and it is recognized adb tools., but that is it. Step one, get the build number before 'zucking' with it. Blew that! Would understand if you walked. Anyway, if your still here, I think the ROM is correct, Motorola_Moto_G7_Plus_XT1965-T_RETUS_LAKE_QPWS30.61-21-18-7-3_10.zip from motostockrom.com. If so, I obviously have no idea how to flash using adb tools and fastboot. Also, I see ROMs ending in .xml.zip, vice .zip. Just packaging? Where to from here? Frame it and find a wall? I'll hold off a couple of days before zucking with it some more. I have a septic tank lid to fix. Way more fun and greater chance of success!
Click to expand...
Click to collapse
RETUS is retail US model device. On my G7 Power there were multiple firmwares that could be used. Idk if this is it but check out "RETAIL" from here: https://mirrors.lolinet.com/firmware/motorola/lake/official/RETAIL/
I didn't see a RETUS firmware. G7 Plus is codename "LAKE" correct ?
Yes. Aaccording to multiple references, LAKE is the codename for the XT1965-T. My OEM box clearly states XT1965-T. It is an unbranded unlocked, full price phone, new out of the box. When I search for "stock ROM", I only find _LAKE_ along with the words "_RETAIL_" or "_RETUS_" in the zip name. Not certain of that though.
cliffgi said:
Yes. Aaccording to multiple references, LAKE is the codename for the XT1965-T. My OEM box clearly states XT1965-T. It is an unbranded unlocked, full price phone, new out of the box. When I search for "stock ROM", I only find _LAKE_ along with the words "_RETAIL_" or "_RETUS_" in the zip name. Not certain of that though.
Click to expand...
Click to collapse
I think RETUS means Retail US. Again, just wagging.
cliffgi said:
I think RETUS means Retail US. Again, just wagging.
Click to expand...
Click to collapse
Maybe check the RETAIL firmware on Lake device section and see if you can find anything that resembles the firmware that you are currently on. Look at dates of the firmware packages. Download a few and unpack them and look inside. That's what I would do. When I look up your model it shows two models .. The T-Mobile Moto G7 Plus and the Unlocked G7 Plus. I'd scope out the contence of the RETAIL firmware and see what all is inside once unpacked.. You should be able to tell by that if the retail is indeed RETUS which is yes retail US.
Where the RIVER firmware is at the link I pasted here in the thread , if you scroll down there is a telegram group link: https://t.me/lolinet
Maybe someone there knows more about all this. Worth a shot.
One last thing, inside the firmware, once it's unpacked I believe there is a script for flashing it. Open it to see order of partitions flashed.. If you do NOT already have a backup of your IMEI you should most definitely back them up as soon as you are able to. Then if you end up with no signal and your IMEI disappears you can fastboot the backed up files and your good. If not and you lose them, you're SOL and you have a paperweight. i remember on my G7 Power I messed mine up and luckily had a backup of them or I would have been screwed.
Once you get up and running again to copy your efs you can use termux terminal or another terminal emulator app and type: su then grant root once it pops up on your phone screen. Them type these two lines, one at a time and it will backup your efs to your sdcard and you can transfer them to your PC, a cloud or USB drive where they're safe.
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048 (then push enter)
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048 (enter)
Edit added: This guy knows about Motorola. His thread(s) may be helpful https://forum.xda-developers.com/t/guide-using-fastboot-exe-with-motorola-devices.4042039/
cliffgi said:
I think RETUS means Retail US. Again, just wagging.
Click to expand...
Click to collapse
flash713 said:
Maybe check the RETAIL firmware on Lake device section and see if you can find anything that resembles the firmware that you are currently on. Look at dates of the firmware packages. Download a few and unpack them and look inside. That's what I would do. When I look up your model it shows two models .. The T-Mobile Moto G7 Plus and the Unlocked G7 Plus. I'd scope out the contence of the RETAIL firmware and see what all is inside once unpacked.. You should be able to tell by that if the retail is indeed RETUS which is yes retail US.
Where the RIVER firmware is at the link I pasted here in the thread , if you scroll down there is a telegram group link: https://t.me/lolinet
Maybe someone there knows more about all this. Worth a shot.
One last thing, inside the firmware, once it's unpacked I believe there is a script for flashing it. Open it to see order of partitions flashed.. If you do NOT already have a backup of your IMEI you should most definitely back them up as soon as you are able to. Then if you end up with no signal and your IMEI disappears you can fastboot the backed up files and your good. If not and you lose them, you're SOL and you have a paperweight. i remember on my G7 Power I messed mine up and luckily had a backup of them or I would have been screwed.
Once you get up and running again to copy your efs you can use termux terminal or another terminal emulator app and type: su then grant root once it pops up on your phone screen. Them type these two lines, one at a time and it will backup your efs to your sdcard and you can transfer them to your PC, a cloud or USB drive where they're safe.
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048 (then push enter)
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048 (enter)
Edit added: This guy knows about Motorola. His thread(s) may be helpful https://forum.xda-developers.com/t/guide-using-fastboot-exe-with-motorola-devices.4042039/
Click to expand...
Click to collapse
A BIG THANKS FOR ALL THE HELP.
Did what you suggested. Extracted and located a "Flashfile.bat"... runs a long list of fastboot cmds, as I'm sure you are familiar. Similar to but more involved than the mannual I ran last night(did not work, broke to boot-loop. Also located a file called LAKE_QPWS30.61-21-18-7-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt Contents are as follows:
BUILD REQUEST INFO:
SW Version: lake-user 10 QPWS30.61-21-18-7-3 284d4d release-keysM636_21.71.02.66R
Modem Version: M636_21.71.02.66R
FSG Version: FSG-660-10.108
MBM Version: MBM-3.0-lake_retail-efaf0cccb-210129
Build Fingerprint: motorola/lake/lake:10/QPWS30.61-21-18-7-3/284d4d:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 30.201.3.lake.retail.en.US
Model Number: moto g(7) plus
Android Version: 10
Build Id: QPWS30.61-21-18-7-3
SW Display Build ID: QPWS30.61-21-18-7-3
Build Date: Fri Jan 29 08:46:03 CST 2021
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
eLabel SHA1: da39a3ee5e6b4b0d3255bfef95601890afd80709
Blur Version: Blur_Version.30.201.3.lake.retail.en.US
Version when read from CPV: lake-user 10 QPWS30.61-21-18-7-3 284d4d release-keys
AB Update Enabled: True
Full Treble Enabled: True
Seems obvious that RETUS stand for Retail US, and all appears to be all correct for my device.
As for a the IMEI it is printed on the box. I have no softcopy.
Very familiar with dd. Excellent idea. Will do, as well as get a full TWRP backup, when get it running.
The unzipped ROM file creates directories: Driver, Firmware, and RSD Flash Tool, as well as credits.txt and How to Flash.txt. How to Flash.txt simply says to install drivers, I have already done; connect device which I know how to do (fastboot devices confirmation), and run the previously mentioned flashfile.bat from the Firmware directory.
Questions:
What It does not say is that this zip was designed for Windows, not Linux (as I ran last night). I also assume that it should be run as administrator. The Windows machine already has Adb Tools and Fastboot installed. I haven't really touched a Windows machine in ten years (TG), but from what I recall, unlike Linux/UNIX, the current working directory is automatically added to the search path. Is this stil the case for Win10 and will the current working directory be searched first, or is there a possibility that there might be a cmd/file version mismatch between the two installs? I have no idea what the directory of RSD Flash Tools is for. ? Any additional thought before I take the pill? A BIG THANKS FOR ALL THE HELP.
On Moto G7 power device the devs changed the firmware install commands and lefts out a few that they said weren't needed. Check out G7 power guides section of xda. There are fastboot guides there. Having a physical backup of your efs is important. It's not the same as just knowing your imei. The only way your imei can be restored is if you backup the efs partitions and if/when you have issues, (many do!) you can fastboot flash them back to your device.
I can't stand Windows. I'm a Linux guru and wish I would have discovered it sooner. I have a Asus Chromebook that I use now and i immediately installed crouton and Ubuntu same day it arrived from Amazon. ChromeOS is actually not bad but fact that its a MAJOR Target for malware and viruses is an issue for me. I'm quite sure the files are for windows. Things still usually are that way much of the time in my experience.. I hope you get it resolved and fixed. I came across more links earlier. I'll go grab them and add them to my post here after I post this. I actually found a G7 Plus fastboot firmware flash guide too. Idk if it's correct or not but lemme go get the links.
This may or may not be helpful. Careful what all you fastboot flash. These Moto devices, the G7, G7+, Power...They can be confusing as far as correct firmware. I also remember on G7 Power our stock firmware, not all of the stock rom partitions would flash.. Some would work for some people and not for others.. See this is a danger zone for the possibility of messing up your efs and losing IMEI.. If anything is flashed that doesn't belong it can screw that up and then you'd lose data and not be able to restore them to fix device.. That's why I mentioned it earlier..
The Complete Noob Guide to Rooting MetroPCS XT1955-5 Qualcomm Variant
This tutorial is for people like me than ran into problems rooting the Moto G7 Power XT-1955-5 (MetroPCS Qualcomm Variant) running on stock Pie. I got two of these literally today brand new in the box after swapping out that mess Samsung Galaxy...
forum.xda-developers.com
The guide on that thread with the fastboot directions is how we flashed our firmware on G7 Power.
May want to read here: https://lineageosroms.com/lake/
The G7 Plus is codename LAKE. I keep thinking RIVER but RIVER is codename for the regular Moto G7 device.
Edit added:
Didn't you mention something about attempting to install recovery TWRP before you bricked? You can try flashing stock boot.img to both slots and reboot system and see if device boots up. Just open terminal and get a stock firmware boot.img from extracted firmware for LAKE device and in terminal and while phones in bootloader mode: sudo fastboot flash boot boot.img --slot all
That will get boot.img on both slot A&B and should fix anything you did with TWRP and boot partition,, if there is anything in your boot partition that's causing phone not to boot. Just make sure boot.img is from LAKE firmware.
When you connect to your PC and open terminal and do: adb reboot bootloader
And then : sudo fastboot getvar all
does anything appear to be not okay? Definitely check that out. I would if I were you. Good luck man. I had found a thread that had firmware fastboot directions. It was dated 19 months ago but "if" it was correct im quite sure it would still apply now . Good luck man.
Well tried to flash stock ROM and got error messages/failure. See attached screenshot.
jwoegerbauer said:
My recommendation: Re-flash Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
flash713 said:
On Moto G7 power device the devs changed the firmware install commands and lefts out a few that they said weren't needed. Check out G7 power guides section of xda. There are fastboot guides there. Having a physical backup of your efs is important. It's not the same as just knowing your imei. The only way your imei can be restored is if you backup the efs partitions and if/when you have issues, (many do!) you can fastboot flash them back to your device.
I can't stand Windows. I'm a Linux guru and wish I would have discovered it sooner. I have a Asus Chromebook that I use now and i immediately installed crouton and Ubuntu same day it arrived from Amazon. ChromeOS is actually not bad but fact that its a MAJOR Target for malware and viruses is an issue for me. I'm quite sure the files are for windows. Things still usually are that way much of the time in my experience.. I hope you get it resolved and fixed. I came across more links earlier. I'll go grab them and add them to my post here after I post this. I actually found a G7 Plus fastboot firmware flash guide too. Idk if it's correct or not but lemme go get the links.
This may or may not be helpful. Careful what all you fastboot flash. These Moto devices, the G7, G7+, Power...They can be confusing as far as correct firmware. I also remember on G7 Power our stock firmware, not all of the stock rom partitions would flash.. Some would work for some people and not for others.. See this is a danger zone for the possibility of messing up your efs and losing IMEI.. If anything is flashed that doesn't belong it can screw that up and then you'd lose data and not be able to restore them to fix device.. That's why I mentioned it earlier..
The Complete Noob Guide to Rooting MetroPCS XT1955-5 Qualcomm Variant
This tutorial is for people like me than ran into problems rooting the Moto G7 Power XT-1955-5 (MetroPCS Qualcomm Variant) running on stock Pie. I got two of these literally today brand new in the box after swapping out that mess Samsung Galaxy...
forum.xda-developers.com
The guide on that thread with the fastboot directions is how we flashed our firmware on G7 Power.
May want to read here: https://lineageosroms.com/lake/
The G7 Plus is codename LAKE. I keep thinking RIVER but RIVER is codename for the regular Moto G7 device.
Edit added:
Didn't you mention something about attempting to install recovery TWRP before you bricked? You can try flashing stock boot.img to both slots and reboot system and see if device boots up. Just open terminal and get a stock firmware boot.img from extracted firmware for LAKE device and in terminal and while phones in bootloader mode: sudo fastboot flash boot boot.img --slot all
That will get boot.img on both slot A&B and should fix anything you did with TWRP and boot partition,, if there is anything in your boot partition that's causing phone not to boot. Just make sure boot.img is from LAKE firmware.
When you connect to your PC and open terminal and do: adb reboot bootloader
And then : sudo fastboot getvar all
does anything appear to be not okay? Definitely check that out. I would if I were you. Good luck man. I had found a thread that had firmware fastboot directions. It was dated 19 months ago but "if" it was correct im quite sure it would still apply now . Good luck man.
Click to expand...
Click to collapse
Got it 100% fixed. Principle problems in recovery from this zuck-up were scoping the problem, locating the proper Stock ROM, figuring out fastboot, and lastly, identifying a defective adb fastboot install on the Windows 10 system I was using. Switched to my primary Linux system and life got a whole lot better.
MANY MANY THANKS to you ( flash713) for suffering through my stupidity without insult, and helped me ID the correct ROM and provide good links that helped me figure out what to do with it once I had it. Seriously, I could not have done without your help. For the Moto G7 Plus XT1965-T, the stock ROM is LAKE_RETAIL_10_QPWS30.61-21-18-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. The image below was from my first attempt with the correct ROM. I discovered that ADB Tools and Fastboot install on my Windows10 system was corrupt. GO LINUX!!!
I use Lubuntu (a lightweight Ubuntu) on Chromebook. My regular laptop died so I use my CB all the time now. Linux most definitely #1 always imo!! Really glad you got it going!!