Database Info

[Solved] motog recovery not working in bootloader

Hi, my 1st post, halloworld
I rooted my xt1032 using Paul O’Brien metod : r1-motog-modifiedrecoveryroot, with a modified recovery.
I'm rooted but when I try to go to recovery from bootloader the phone just normally boots.
So no way to make a nandroid backup, a wipe cache and so on...
I suppose it's becouse I followed a guide for 4.3 while I was already updated to 4.4
My question is, could I have any problem flashing the correct version of cwm for kitkat, after the modified recovery I used for rooting?
welcome suggestiones

When your in boot loader select the recovery option and press the up volume to get to recovery
Sent from my XT1034 using xda app-developers app

That's what I did(100times...), with vol.up yes, not with power button. What I get is a normal reboot. No way to go in recovery, event tried from adb or fastboot in a windows shell.
No one having this problem with recovery?

fatechand said:
That's what I did(100times...), with vol.up yes, not with power button. What I get is a normal reboot. No way to go in recovery, event tried from adb or fastboot in a windows shell.
No one having this problem with recovery?
Click to expand...
Click to collapse
I had this problem with recovery during rooting,
but I was rooted anyway, so now my moto g is running ok

fatechand said:
That's what I did(100times...), with vol.up yes, not with power button. What I get is a normal reboot. No way to go in recovery, event tried from adb or fastboot in a windows shell.
No one having this problem with recovery?
Click to expand...
Click to collapse
It's probably caused by the recovery not being compatible with your bootloader.
What version of the bootloader are you on? That custom recovery might only work with 4.3 only.
You can easily change your bootloader with the mfastboot and extracting the motoboot.img from the (correct) stock rom image.

well, my bootloader should be the one of Kitkat, for I upgraded from 4.3 just before rooting.
I could change bootloader as you told me, but what about compatibility with 4.4 rom?
My idea was just to change the recovery, with cwm 6.0.4.7 that's now compatible with motog 4.4,
but what about my actual root configuration?
I don't actually know what I risk doing this way, or if I need a wipe data.
Which are the right steps?

fatechand said:
well, my bootloader should be the one of Kitkat, for I upgraded from 4.3 just before rooting.
I could change bootloader as you told me, but what about compatibility with 4.4 rom?
My idea was just to change the recovery, with cwm 6.0.4.7 that's now compatible with motog 4.4,
but what about my actual root configuration?
I don't actually know what I risk doing this way, or if I need a wipe data.
Which are the right steps?
Click to expand...
Click to collapse
I think the best way is to flash a compatible recovery via fastboot. No need to wipe anything. Your root won't be broken afaik.

fatechand said:
well, my bootloader should be the one of Kitkat, for I upgraded from 4.3 just before rooting.
I could change bootloader as you told me, but what about compatibility with 4.4 rom?
My idea was just to change the recovery, with cwm 6.0.4.7 that's now compatible with motog 4.4,
but what about my actual root configuration?
I don't actually know what I risk doing this way, or if I need a wipe data.
Which are the right steps?
Click to expand...
Click to collapse
Yes, I would try flashing CWM 6.0.4.7-falcon as well. It works for both 4.3 and 4.4 bootloader (I tried myself.)
If just flashing the bootloader, you don't need to wipe anything ..

Well, I'll do it with cwm, after weekend. Thanks for suggestions

fatechand said:
Well, I'll do it with cwm, after weekend. Thanks for suggestions
Click to expand...
Click to collapse
All so good - very nice
I flashed recovery.img from my stock reatil en-GB xml.zip , now from fastboot i can go to recovery, that actually in kitkat is just the green robot with red warning -> from here pressing VOL UP and Clicking POWER button I can get stock recovery menu.
What's good that I tried and finally could INSTALL last minor 176.44.1 UPDATE !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm now going to flash cwm or Philz touch
Thanks forum

last KitKat compatibile version of CWM installed like a charme, no problems with root so now my moto g is rooted and running last updated stock ROM.
solved post

fatechand said:
last KitKat compatibile version of CWM installed like a charme, no problems with root so now my moto g is rooted and running last updated stock ROM.
solved post
Click to expand...
Click to collapse
:thumbup:

moto g anble to boot up
can u plz help me .... i have a problem with my moto g...
actually i unlock the bootloder..
after that its working with CM11
but now mobile stuck in unlock bootloader screen ..
recovery menu also not working..
when i was trying to instal stock firmware.. everything installing OK... but no results
same thing happen again... stuck in unlock bootloader screen ..
wat is my mobile problem ...
plz suggest me

vardhanram said:
can u plz help me .... i have a problem with my moto g...
actually i unlock the bootloder..
after that its working with CM11
but now mobile stuck in unlock bootloader screen ..
recovery menu also not working..
when i was trying to instal stock firmware.. everything installing OK... but no results
same thing happen again... stuck in unlock bootloader screen ..
wat is my mobile problem ...
plz suggest me
Click to expand...
Click to collapse
Did you found solution?

jayrocky11 said:
Did you found solution?
Click to expand...
Click to collapse
no not yet..................

vardhanram said:
no not yet..................
Click to expand...
Click to collapse
How did you flash? I've flashed GPE, Downgrade to JB and different versions of Ktikat e.g. Retail and O2 Uk and nothing has happened.

[SCRIPT] Moto E XT1023 super easy ROOT, RECOVERY, & RESTORE

This is a little script tool I made up for the Moto E XT1023 The Firmware restore will only work on the XT1023 but all other options should work on all the variants of the Moto E
It is really simple. But requires a unlocked bootloader video HERE If you need help with bootloader unlock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the Moto E Super Tool
extract the tool to your desktop
Turn on usb debugging mode on the device
install the Motorola drivers
Run the Moto E 1 Moto-E-Restore-XT1023.bat file
then just select what you want to do
1. Root your Moto E
2. Flash TWRP Recovery
3. Flash Stock Android Recovery
4. Flash CWM recovery
5. Remove the unlocked bootloader warning
6. Fully restore the Moto E to stock
7. Fully restore plus Relock the bootloader
Newest release V2
Change Log
Vision 1 first release
Version 2
updated TWRP
Updated Supersu.zip
DOWNLOAD SUPER TOOL
WIll add more to this if i have time
Hope this will help out some noobs

Is it for all the models like xt1021 nd xt1022??

zoneofSAM said:
Is it for all the models like xt1021 nd xt1022??
Click to expand...
Click to collapse
the first line of thread answers your question. variants=models

zoneofSAM said:
Is it for all the models like xt1021 nd xt1022??
Click to expand...
Click to collapse
I have tested it on the xt1023 but from what i am told it should work on all models because supersu.zip is universal and same with TWRP if i am not mistaken.

doesn't reboot into recovery
Everything seems ok during the process but when the phone reboots it stays in the Motorola logo/Android screen, never moving on to TWRP. This also happened when I tried the normal Fastboot method. Bootloader is unlocked and usb debugging is checked, of course.
Any ideas?
edit:
More info-
1. The only command that seems to work on my phone is when I install stock recovery.
2. When I go into bootloader and try to restart in any mode but normal restart I get a blank screen
3. I previously bricked my phone by doing something stupid so I reflashed one of the factory firmwares-
RETUAWS_XT1023_4.4.2_KXC20.82-15_cid9_CFC.xml
Could this be the source of my problem?
Thanks in advance!

Hi,
Thanks for your script, mate...just used it for SuperSu installation and made the rest by other way, but worked flawlessly for that, and that's the point !!! :good:
Cheerz

satanas17 said:
Hi,
Thanks for your script, mate...just used it for SuperSu installation and made the rest by other way, but worked flawlessly for that, and that's the point !!! :good:
Cheerz
Click to expand...
Click to collapse
updated tool with newest twrp and supersu

Cannot upgrade to 4.4.4
Thanks for the nice video; however I just have a problem when trying to go back to stock recovery to install the 4.4.4 update that is recently pushed to Moto E devices; I want to go back to stock recovery as it does not gets installed with any custom recovery.
I tried the said method 4-5 times but it gives me with a dead android icon when trying to get to stock recovery..
Please help me to get 4.4.4 on my device.

Yeah that is normal you have to press volume up and power on that screen to get to options

Tomsgt said:
Yeah that is normal you have to press volume up and power on that screen to get to options
Click to expand...
Click to collapse
Thanks!! it worked for me and I see the options now.. however the update still does not work :crying:
and searching and experimenting to get 4.4.4

_SGY said:
Thanks!! it worked for me and I see the options now.. however the update still does not work :crying:
and searching and experimenting to get 4.4.4
Click to expand...
Click to collapse
Update won't work if you have modded system partition in any way. Even if its just blotware uninstalled. Just flash system partition only and it should work. The .1 .2 .3 file extension files I mean

Deadly said:
Update won't work if you have modded system partition in any way. Even if its just blotware uninstalled. Just flash system partition only and it should work. The .1 .2 .3 file extension files I mean
Click to expand...
Click to collapse
You mean system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2 right??
Done that already with no success.. I don't know what I am doing wrong here

No more wallpaper crashes after wipe data and cache

_SGY said:
You mean system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2 right??
Done that already with no success.. I don't know what I am doing wrong here
Click to expand...
Click to collapse
Updated Yippeeeeee...
The issue was my rooted device, I had to unroot, install stock ROM as I had removed plenty of bloatware..update success, re-root and enjoy!!!!
Posting steps to benefit someone who may be facing the same issue as I was..

Hey guys. My little brother just got a Moto E, and I'm trying to get it rooted/Recovery'd.
I'm using your toolkit, but so far, no luck. Doesn't want to root, nor install recovery. It's stuck on "waiting for device".
I don't know what's wrong. I checked that USB debugging was on, and he unlocked his bootloader earlier. Everything should be fine.
But, it doesn't work.
Could someone provide some help, please ?
Thanks.

Did you extract the zip to your desktop? And are the right drivers installed also try using a different USB cable or port.

Demonseye said:
Hey guys. My little brother just got a Moto E, and I'm trying to get it rooted/Recovery'd.
I'm using your toolkit, but so far, no luck. Doesn't want to root, nor install recovery. It's stuck on "waiting for device".
I don't know what's wrong. I checked that USB debugging was on, and he unlocked his bootloader earlier. Everything should be fine.
But, it doesn't work.
Could someone provide some help, please ?
Thanks.
Click to expand...
Click to collapse
Did u connected mobile in bootloader ? Try t

sham4u2sam said:
Did u connected mobile in bootloader ? Try t
Click to expand...
Click to collapse
Yeah, I tried it. Weird thing is that we reconnected it to his computer, and the script recognized his phone, while my PC did not. Everything went smooth. Thanks.

Recovery.img is for 4.2(for option stock recovery)
But my moto e is 4.4.4
Will it work???
And also
One advice
Plz include flash stock firmware to your your script
And don't add drivers to in your zip file make a separate link for driver.
Hope you like my suggestions and include it in your next update
Any how i looked your bat file
You looks a good programmer
---------- Post added at 11:01 PM ---------- Previous post was at 10:20 PM ----------
Request for new menu
1.root your phone
2.flash twrp
3.flash stock recovery 4.4.4
4.unlock boot loader(where it only ask to enter unlock key)
5.remove bootloader unlocked warning
6.install stock firmware or rom(where it flash frimware placed in frimware folder)
7.lock your boot loader and install orignal 4.4.4 recovery to get warranty back
Hit thanks if you like to include these options in next update

hard91 said:
Recovery.img is for 4.2(for option stock recovery)
But my moto e is 4.4.4
Will it work???
And also
One advice
Plz include flash stock firmware to your your script
And don't add drivers to in your zip file make a separate link for driver.
Hope you like my suggestions and include it in your next update
Any how i looked your bat file
You looks a good programmer
---------- Post added at 11:01 PM ---------- Previous post was at 10:20 PM ----------
Request for new menu
1.root your phone
2.flash twrp
3.flash stock recovery 4.4.4
4.unlock boot loader(where it only ask to enter unlock key)
5.remove bootloader unlocked warning
6.install stock firmware or rom(where it flash frimware placed in frimware folder)
7.lock your boot loader and install orignal 4.4.4 recovery to get warranty back
Hit thanks if you like to include these options in next update
Click to expand...
Click to collapse
challenge excepted LOL Moto E Super Tool
Your Option 4 isnt going to happen

[XT1033] GPE to Stock problems

Hi Guys! (sorry about bad english... i hope you understand)
I have followed this thread: http://forum.xda-developers.com/showthread.php?t=2661022
Now my phone don't boot.
I only have access to Bootloader mode (unlocked).
Questions:
• How can i convert back to stock 4.4.3 ?
• I tried to flash many versions of GPT.BIN or MOTOBOOT.IMG, but all failed. Now i dont have partitions in my device... How to proceed?
• I tried flash stocks like 4.4.3, 4.4.2, 4.3 GPE and not work for me. What should I do?
- When I try to flash stock 4.4.3, the device shows a message: IMAGE IS TOO BIG (in System flash step)
- I ran the command: "fastboot erase all" and "fastboot erase system"
- Now I can not flash the system partition and can not flash the motoboot.img.
When i try to flash motoboot, shows me a message on phone: "VERSION DOWNGRADE FOR TZ"
Please, can someone help me?

GuiSouza said:
Hi Guys! (sorry about bad english... i hope you understand)
I have followed this thread: http://forum.xda-developers.com/showthread.php?t=2661022
Now my phone don't boot.
I only have access to Bootloader mode (unlocked).
Questions:
• How can i convert back to stock 4.4.3 ?
• I tried to flash many versions of GPT.BIN or MOTOBOOT.IMG, but all failed. Now i dont have partitions in my device... How to proceed?
• I tried flash stocks like 4.4.3, 4.4.2, 4.3 GPE and not work for me. What should I do?
- When I try to flash stock 4.4.3, the device shows a message: IMAGE IS TOO BIG (in System flash step)
- I ran the command: "fastboot erase all" and "fastboot erase system"
- Now I can not flash the system partition and can not flash the motoboot.img.
When i try to flash motoboot, shows me a message on phone: "VERSION DOWNGRADE FOR TZ"
Please, can someone help me?
Click to expand...
Click to collapse
Why do you play with your phone, if you don't know how to fix it?
Help comes only if you can help yourself in first place.
Quick tip, you don't need to flash gpt nor motoboot.There is one more thing that will actually make your phone working, but you need to learn your lesson.
Good luck.

liveroy said:
Why do you play with your phone, if you don't know how to fix it?
Help comes only if you can help yourself in first place.
Quick tip, you don't need to flash gpt nor motoboot.There is one more thing that will actually make your phone working, but you need to learn your lesson.
Good luck.
Click to expand...
Click to collapse
I know I should not be flashing GPT, but I learned too late.
The question now is how to find out which version of GPT is (as did the procedure for your version of Google Play) and how to flash motoboot.img.
thanks for helping

GuiSouza said:
I know I should not be flashing GPT, but I learned too late.
The question now is how to find out which version of GPT is (as did the procedure for your version of Google Play) and how to flash motoboot.img.
thanks for helping
Click to expand...
Click to collapse
I think you ain't reading well, you DON"T need to flash gpt.bin or motoboot.img.These will do well even if downgrade (as in your case).Get a 4.4.2 ROM and flash it, make sure you erase userdata.

liveroy said:
I think you ain't reading well, you DON"T need to flash gpt.bin or motoboot.img.These will do well even if downgrade (as in your case).Get a 4.4.2 ROM and flash it, make sure you erase userdata.
Click to expand...
Click to collapse
I tried to flash now but i get message on phone: "Image is too large" when system flash begins. What is this?

GuiSouza said:
I tried to flash now but i get message on phone: "Image is too large" when system flash begins. What is this?
Click to expand...
Click to collapse
It means you're trying to flash a single system image instead of one broken in chunks (3) and since "fastboot flash system" is limited to 256 MB, you get this error, because your image is larger than 256MB.

liveroy said:
It means you're trying to flash a single system image instead of one broken in chunks (3) and since "fastboot flash system" is limited to 256 MB, you get this error, because your image is larger than 256MB.
Click to expand...
Click to collapse
Take a look... i have 3 files. Now you know my problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try this way:
mfastboot -S 256M flash system system.img_sparsechunk.0
Also put up a screenshot of the error you get.

liveroy said:
Try this way:
mfastboot -S 256M flash system system.img_sparsechunk.0
Also put up a screenshot of the error you get.
Click to expand...
Click to collapse
In CMD returns OKAY but in phone show the same message: "Image is too large" and when I start the phone, does not boot

GuiSouza said:
In CMD returns OKAY but in phone show the same message: "Image is too large" and when I start the phone, does not boot
Click to expand...
Click to collapse
Can you flash CM11 for example?

liveroy said:
Can you flash CM11 for example?
Click to expand...
Click to collapse
Cm11 Works! But how can i can back to Stock?

That means your partitions are fine and your phone is also overall in good shape.Download a different Stock image and try again with it.As a last resort find a cwm/twrp backup of your type of device and use that to get back to stock.

liveroy said:
That means your partitions are fine and your phone is also overall in good shape.Download a different Stock image and try again with it.As a last resort find a cwm/twrp backup of your type of device and use that to get back to stock.
Click to expand...
Click to collapse
No he has to flash a 4.4.4 retail Brazilian image. And don't say that he is stupid or that he should fix it by himself without asking for help... Why are there sites called 'forums' and member trying to help?
GuiSouza said:
Cm11 Works! But how can i can back to Stock?
Click to expand...
Click to collapse
https://mega.co.nz/#!kQo1UAQY!nJA7Vc94DBfGFWGk1krcI5I2cKrJNGHnr_YekCBscwQ
Here you are mate!

This method is known to work... http://forum.xda-developers.com/moto-g/general/xt1033-t2821556

GI0\/\NNI said:
No he has to flash a 4.4.4 retail Brazilian image. And don't say that he is stupid or that he should fix it by himself without asking for help... Why are there sites called 'forums' and member trying to help?
https://mega.co.nz/#!kQo1UAQY!nJA7Vc94DBfGFWGk1krcI5I2cKrJNGHnr_YekCBscwQ
Here you are mate!
Click to expand...
Click to collapse
I don't think I've said he's stupid anywhere.
Also by the time he posted this, there were no stock 4.4.4 images available.
Actually I got no idea why you guys revive a 2-3 months old topic at all....

liveroy said:
I don't think I've said he's stupid anywhere.
Also by the time he posted this, there were no stock 4.4.4 images available.
Actually I got no idea why you guys revive a 2-3 months old topic at all....
Click to expand...
Click to collapse
Because he sent me a PM with his problem, I'm reviving this thread to finish this thread for reading people.

GI0\/\NNI said:
Because he sent me a PM with his problem, I'm reviving this thread to finish this thread for reading people.
Click to expand...
Click to collapse
I could help with this problem
http://forum.xda-developers.com/moto-g/help/moto-g-logo-motorola-t2858483
Rarely does not change anything I flash

No Cellular Connectivity After Flashing Stock ROM on Google Play Moto G

I had the Google Play edition of the Moto G running the nightly builds of Cyanogenmod, and all things considered, it was going pretty well. However, after a while I noticed that my GPS seemed unable to get a lock. Later, it seemed unable to connect to mobile data, though all the other cellular functions worked just fine. I assumed this must have something to do with the CM nightlies.
The real trouble came when I tried restoring Motorola's stock firmware. Considering there aren't really any releases of the Google version of the Moto G firmware, I thought that was my best bet. I followed the instructions found here, rebooted, and found I was unable to use any of the cellular features, along with a helpful "No Service" icon in my status area. I have since reinstalled Cyanogenmod, and still have all the same issues.
Here is the About and About > Status pages for your reference:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have read that similar issues can be caused by having a corrupted IMEI. However, I've pulled the pds partition off the device, mounted it, and found the following files:
Code:
batt_health bt camera factory lost+found pds_formatted_v10 public security whisper wifi wmdrm
and I see an IMEI in the phone status, so I would assume that it is fine.
Is it possible the firmware for the modem is not functioning properly? As a rather low priority, any tips on debugging GPS would be helpful too.
Thanks!

You probably haven't reflashed the correct GPE firmware...On XDA, there are many GPE firmwares most of which are modified to convert xt1032 and xt1033 to GPE by changing the radios and the fsg.bin file...Make sure you choose the original GPE firmware...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------

pfufle said:
You probably haven't reflashed the correct GPE firmware...On XDA, there are many GPE firmwares most of which are modified to convert xt1032 and xt1033 to GPE by changing the radios and the fsg.bin file...Make sure you choose the original GPE firmware...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
Click to expand...
Click to collapse
I flashed "fsg_gpe.img" from this thread and still get the same issue. Will I have to do a factory reset or flash any other components?

You do get an original GPE firmware somewhere on XDA, flash that...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------

pfufle said:
You do get an original GPE firmware somewhere on XDA, flash that...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
Click to expand...
Click to collapse
I've reflashed the stock firmware and I still have the same issue. I should mention that under Status, it says Radio off. There seem to be others having the same issue:
http://forum.xda-developers.com/showthread.php?t=2755011
My status readout is the exact same as the above poster's.

MetaNova said:
I've reflashed the stock firmware and I still have the same issue. I should mention that under Status, it says Radio off. There seem to be others having the same issue:
http://forum.xda-developers.com/showthread.php?t=2755011
My status readout is the exact same as the above poster's.
Click to expand...
Click to collapse
That is because you haven't flashed the stock GPE firmware...You might have flashed a different firmware
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------

pfufle said:
That is because you haven't flashed the stock GPE firmware...You might have flashed a different firmware
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
Click to expand...
Click to collapse
Sorry, I have a lot of tabs open and linked to the wrong thread. I got the stock GPE firmware from here: http://forum.xda-developers.com/showthread.php?t=2633272 and then even updated to 4.4.4 using the official OTA update which contained an fsg among other things.
Partitions BOOT, RECOVERY, LOGO, FSG (fsg_gpe.img) and MODEM are same as flashed on GPE devices.
Click to expand...
Click to collapse

MetaNova said:
I got the stock GPE firmware from here: http://forum.xda-developers.com/showthread.php?t=2633272 and then even updated to 4.4.4 using the official OTA update which contained an fsg among other things.
Click to expand...
Click to collapse
Obviously the flashing process has not been complete. Since there is currently no 4.4.4 GPE image, you could try the 4.4.4 Retail EU image: http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
Do all of the fastboot commands manually and report back any errors. In particular, ensure the following commands are included:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2​

lost101 said:
Obviously the flashing process has not been complete. Since there is currently no 4.4.4 GPE image, you could try the 4.4.4 Retail EU image: http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
Do all of the fastboot commands manually and report back any errors. In particular, ensure the following commands are included:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2​
Click to expand...
Click to collapse
I have written(/erased) and rewritten everything several times with fastboot, especially NON-HLOS.bin and modemst(1|2) parts. I begrudgingly did it one more time as you requested, and..... it worked. You seriously have the magic touch or something.
Thank. You.
thankyouthankyouthankyou. Whatever you did. XD
Second question: Even after the above fix, my mobile data didn't work until I manually added an APN with the data on my provider's website. One of the reasons I had started flashing roms in the first place, before I managed to break it, was that one day my mobile data stopped working.
When I set up my phone, the APN's seemed to pop up out of nowhere and everything worked just fine. Why did I manually have to add one now?
Thanks again!

I haven't had any APN issues personally. The app Tweakker is one option that you might find useful:
https://play.google.com/store/apps/details?id=com.tweakker&hl=en​
EDIT: 4.4.4 GPE Firmware Image now available: (Perhaps a solution to your APN issue)
http://forum.xda-developers.com/showpost.php?p=54912538&postcount=366​

[Guide] How to flash Factory Image using RSD Lite

DO AT YOUR OWN RISK!!!
I WILL NOT HELD RESPONSIBLE!!!
****BACKUP IMPORTANT DATA FIRST****
Download and Install RSD Lite 6.2.4 and Drivers
Extract the firmware.
****(Don't use USB Hub/Front USB Port/USB 3.0/3.1 Port)****
Now connect your phone to your PC (preferably Bootloader/Fastboot Mode).
Keep your phone connected with the PC and launch RSD Lite as an admin. (Run as administrator).
Click on the three-dot browser file button and select the .xml file.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
****flashfile.xml will erase everything****
****servicefile.xml will not erase your Data****
IT IS RECOMMENDED TO ERASE EVERYTHING
Once done, click on Start to initiate the flashing process.
When the firmware is successfully flashed, your smartphone will automatically reboot.
Feel free to enhance this guide
Fastboot Guide (Advanced Users Only) by @The jOkEr!
https://forum.xda-developers.com/showthread.php?p=64101049

Thanks a lot. Very informative.

Do I need to have an unlocked bootloader for that?

I have enough time not to use rsd lite, I feel more secure with the command method
Enviado desde mi XT1563 mediante Tapatalk

derchrome said:
Do I need to have an unlocked bootloader for that?
Click to expand...
Click to collapse
I don't think so.
Sent from my XT1562 using Tapatalk

flopezm said:
I have enough time not to use rsd lite, I feel more secure with the command method
Enviado desde mi XT1563 mediante Tapatalk
Click to expand...
Click to collapse
Yes I agree with you!! But it is not noob friendly.
Sent from my XT1562 using Tapatalk

derchrome said:
Do I need to have an unlocked bootloader for that?
Click to expand...
Click to collapse
No! If you're flashing same build or newer build!
Sent from my XT1562 using Tapatalk

I've been using rsdlite since non-smartphone era (my first moto was the c390) and it had saved my bricked phones countless time.

gbt.bin file failed
pijes said:
I've been using rsdlite since non-smartphone era (my first moto was the c390) and it had saved my bricked phones countless time.
Click to expand...
Click to collapse
gbt.bin file failed
---------- Post added at 06:32 AM ---------- Previous post was at 06:29 AM ----------
kumeipark said:
DO AT YOUR OWN RISK!!!
I WILL NOT HELD RESPONSIBLE!!!
****BACKUP IMPORTANT DATA FIRST****
Download and Install RSD Lite 6.2.4 and Drivers
Extract the firmware.
****(Don't use USB Hub/Front USB Port/USB 3.0/3.1 Port)****
Now connect your phone to your PC (preferably Bootloader/Fastboot Mode).
Keep your phone connected with the PC and launch RSD Lite as an admin. (Run as administrator).
Click on the three-dot browser file button and select the .xml file.
****flashfile.xml will erase everything****
****servicefile.xml will not erase your Data****
IT IS RECOMMENDED TO ERASE EVERYTHING
Once done, click on Start to initiate the flashing process.
When the firmware is successfully flashed, your smartphone will automatically reboot.
Feel free to enhance this guide
Fastboot Guide by @The jOkEr!
(Advanced Users Only)
https://forum.xda-developers.com/showthread.php?p=64101049
Click to expand...
Click to collapse
i flashed a rom then my 2nd sim of xt1562 was not working so i decided to flash stock rom using rsd lite but when i am flashing then gbt.bin failed everytime
i am from india i am trying to flash stock rom XT1562_LUX_RETASIA_DS_6.0.1_MPD24.107-52_cid7_subsidy-DEFAULT_CFC.xml

sonubisht said:
gbt.bin file failed
---------- Post added at 06:32 AM ---------- Previous post was at 06:29 AM ----------
i flashed a rom then my 2nd sim of xt1562 was not working so i decided to flash stock rom using rsd lite but when i am flashing then gbt.bin failed everytime
i am from india i am trying to flash stock rom XT1562_LUX_RETASIA_DS_6.0.1_MPD24.107-52_cid7_subsidy-DEFAULT_CFC.xml
Click to expand...
Click to collapse
gpt.bin usually related to partition table and your phone probably has an updated partition table newer than the one in the stock rom. If possible, get the latest stock rom, I heard that x play has received stock Nougat update probably you could flash that

pijes said:
gpt.bin usually related to partition table and your phone probably has an updated partition table newer than the one in the stock rom. If possible, get the latest stock rom, I heard that x play has received stock Nougat update probably you could flash that
Click to expand...
Click to collapse
Thats the problem , stock 7.1.1 images for Moto X Play not released till now

[email protected] said:
Thats the problem , stock 7.1.1 images for Moto X Play not released till now
Click to expand...
Click to collapse
Try flashing the other stock rom with number 107-70. I believe this is the latest for marshmallow

[email protected] said:
Thats the problem , stock 7.1.1 images for Moto X Play not released till now
Click to expand...
Click to collapse
pijes said:
Try flashing the other stock rom with number 107-70. I believe this is the latest for marshmallow
Click to expand...
Click to collapse
7.1.1 Out Now!!
Look here: https://forum.xda-developers.com/mo...o-x-play-india-brazil-official-final-t3691100

I know this is an old thread but I am trying to flash my 1926-7 Moto G4 Plus Retail Latin version.
I am able to reboot it using RSD Lite and then the phone goes into fastboot mode:
AP Fastboot Flash Mode (secure)
OEM_Locked
Console: Null
TRansfermode : USB connected
I must be missing a step, I also noticed that the RSD Lite Vanishes and yet in the task manager it still shows SDL.exe running for a while then vanishes.
But in the program it changes state:
I'm using the latest Version of RSD
Thanks in advance.