Moto G 4G LTE (XT1039) Stock Motorola ROM - Moto G Q&A, Help & Troubleshooting

Greetings,
I've been silly and managed to soft-brick my XT1039. Would anyone be able to point me towards the stock ROM for this device?
(Alternatively, any ROM that works on it. Heh.)
Many thanks.

ayleid said:
Greetings,
I've been silly and managed to soft-brick my XT1039. Would anyone be able to point me towards the stock ROM for this device?
(Alternatively, any ROM that works on it. Heh.)
Many thanks.
Click to expand...
Click to collapse
hey, you need to provide more information on the nature of your soft-brick. what happens when you try to turn on the phone? is it bootloader unlocked? can you atleast turn the phone on to recovery mode?
I am not aware of any released xt1039 firmware. but you can give a shot to the xt1045 firmware, should be fairly similar.
download the firmware image from here. http://www.firmware-team.com/showthread.php?t=1146
and carefully follow these instructions to flash the stock firmware. http://forum.xda-developers.com/showthread.php?t=2542219

suhridkhan said:
hey, you need to provide more information on the nature of your soft-brick. what happens when you try to turn on the phone? is it bootloader unlocked? can you atleast turn the phone on to recovery mode?
I am not aware of any released xt1039 firmware. but you can give a shot to the xt1045 firmware, should be fairly similar.
download the firmware image from here. http://www.firmware-team.com/showthread.php?t=1146
and carefully follow these instructions to flash the stock firmware. http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Thanks for the reply.
So, if I try to turn on the phone it takes me to the Bootloader screen. The Bootloader is unlocked.
If I try to do a normal powerup, it says "Boot up failed".
If I try to enter Recovery, it gives me an Android-lying-on-its-back with a red warning triangle coming from it.
I've already followed the instructions to put the XT1045 firmware on my phone, and that's the state in which my phone is now (i.e. it didn't work).

Related

[SOLVED] Can flash 4.4 over 4.3 without unlocking?

I want to get the 4.4 update on my new Moto G. But also i want to avoid unlocking the bootloader. I read somewhere that the system will let you flash a signed image without unlocking the bootloader, but i want to be sure, so i don't end with a soft bricked phone and have to unlock it anyways.
Can you help me?
EDIT: You can! Just flash the upgrade via fastboot and your phone will have the last iteration of Android witthot unlocking anything.
tatazeuz said:
I want to get the 4.4 update on my new Moto G. But also i want to avoid unlocking the bootloader. I read somewhere that the system will let you flash a signed image without unlocking the bootloader, but i want to be sure, so i don't end with a soft bricked phone and have to unlock it anyways.
Can you help me?
Click to expand...
Click to collapse
you don't have to unlock it if you are updating it through the update option inside the phone itself.
digitalmahdi said:
you don't have to unlock it if you are updating it through the update option inside the phone itself.
Click to expand...
Click to collapse
I know, but the phone comes with a carrier firmware that will take some time to roll the update, and I want to replace it.
tatazeuz said:
I know, but the phone comes with a carrier firmware that will take some time to roll the update, and I want to replace it.
Click to expand...
Click to collapse
then the answer is no, in order to load any custom rom you have to unlock your bootloader.
digitalmahdi said:
then the answer is no, in order to load any custom rom you have to unlock your bootloader.
Click to expand...
Click to collapse
But I'm not trying to load a custom ROM, I'm trying to load an official firmware.
Which is a ROM itself
Sent from my XT1032 using xda app-developers app
Faruko said:
Which is a ROM itself
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
But certainly isn't custom, and its signed.
tatazeuz said:
But certainly isn't custom, and its signed.
Click to expand...
Click to collapse
I think you should refer to this video - http://youtu.be/-L44JqysUy8
It shows how to flash a rom without unlocking the bootloader. There are retail ROMS available from http://sbf.droid-developers.org/phone.php?device=14
voosh710 said:
I think you should refer to this video - http://youtu.be/-L44JqysUy8
It shows how to flash a rom without unlocking the bootloader. There are retail ROMS available from http://sbf.droid-developers.org/phone.php?device=14
Click to expand...
Click to collapse
Thanks!
I flashed retail.GB over my tesco firmware without unlocking bootloader
Motorola Moto G (XT1032), Android 4.4.2

[HELP] Soft-bricked my cricket XT1032 moto g.

Could someone help me restore 4.4.2 stock firmware?
MY BOOT LOADER IS LOCKED
When I turn on my phone I get this:
version downgraded for boot
failed to validate boot image
Fastboot reason: fall-through from normal boot mode
ImAustin366624 said:
Could someone help me restore 4.4.2 stock firmware?
When I turn on my phone I get this:
version downgraded for boot
failed to validate boot image
Fastboot reason: fall-through from normal boot mode
Click to expand...
Click to collapse
Flash the 4.4.4 image.
pfufle said:
Flash the 4.4.4 image.
Click to expand...
Click to collapse
My moto g never received the 4.4.4 update so do you think it will still work? Where could I find the 4.4.4 firmware?
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
It's downloading now, will report back when i'm done Thanks for helping!
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
I will have to do this later in the day, my crappy satellite internet is acting up right now
I had this problem and sadly, after trying countless times with different firmwares the only solution I could find is to unlock the bootloader.
Then it stops giving you an error when you try to flash boot.img.
Your mileage may vary, but that is a potential fix, so keep that in mind.
ianxblog said:
I had this problem and sadly, after trying countless times with different firmwares the only solution I could find is to unlock the bootloader.
Then it stops giving you an error when you try to flash boot.img.
Your mileage may vary, but that is a potential fix, so keep that in mind.
Click to expand...
Click to collapse
The only way to unlock the bootloader with AIO moto g's is to use Jcases sunshine app and you have to be in the operating system for that
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My parents use the same exact phone as me on the same carrier, could I dump the firmware from their phones and then flash it onto mine?
You can take a system image via a nandroid backup and the flash it on your device

Rooting locked bootloader

Hello! I have an Xperia M2 and I want to root it. As far as my phone is branded and the bootloader is locked, I can't downgrade to JB (4.3) because I can't find the FTF for Orange RO. I tried all the methods listed on how to root locked bootloader but without succes. Can someone guide me somehow? Android without root is useless for me, thanks in advance!
Vlad01 said:
Hello! I have an Xperia M2 and I want to root it. As far as my phone is branded and the bootloader is locked, I can't downgrade to JB (4.3) because I can't find the FTF for Orange RO. I tried all the methods listed on how to root locked bootloader but without succes. Can someone guide me somehow? Android without root is useless for me, thanks in advance!
Click to expand...
Click to collapse
Not sure how it works with branded phones, but I would try this nonetheless:
http://forum.xda-developers.com/xperia-m2/help/qa-rooting-locked-bootloader-ota-method-t2999665
use the attached kernel (it's for M2). If it gets flashed you are all setup. Just be sure to have downloaded and updated first your phone to its latest FTF. From the downloaded FTF you can flash back its original kernel after the rooting.
Thanks for reply!
Not sure how it works with branded phones, but I would try this nonetheless:
http://forum.xda-developers.com/xper...ethod-t2999665
use the attached kernel (it's for M2). If it gets flashed you are all setup. Just be sure to have downloaded and updated first your phone to its latest FTF. From the downloaded FTF you can flash back its original kernel after the rooting.
Click to expand...
Click to collapse
I tried but rootkitxperia is not working.. Says waiting for device or the thing with "daemon started", no effect, can you help me? Kernel had been flashed and it is bootlooping.
Vlad01 said:
I tried but rootkitxperia is not working.. Says waiting for device or the thing with "daemon started", no effect, can you help me? Kernel had been flashed and it is bootlooping.
Click to expand...
Click to collapse
So does that mean that you could flash JB kernel? In that case your phone can be rooted with that method. Just make it sure you follow the guide step by step. If rootkitXperia/adb isn't working make it sure that adb debug is enabled in the phone and that you didn't wipe the data while flashing the kernel.
Now I don't remember well, but I think that other people had issues with rootkitXperia. So they used another rootkit. Don't ask me which one. You'll have better chance to get help asking it in the thread.

Bootloop, oem, many problems

Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Jaszka said:
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Click to expand...
Click to collapse
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
MotoJunkie01 said:
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
Click to expand...
Click to collapse
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
acejavelin said:
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
Click to expand...
Click to collapse
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
MotoJunkie01 said:
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
Click to expand...
Click to collapse
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
purplefruity said:
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
Click to expand...
Click to collapse
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
MotoJunkie01 said:
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
Click to expand...
Click to collapse
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
purplefruity said:
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
Click to expand...
Click to collapse
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
MotoJunkie01 said:
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
Click to expand...
Click to collapse
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
purplefruity said:
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
Click to expand...
Click to collapse
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
MotoJunkie01 said:
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
Click to expand...
Click to collapse
O well I guess my device was different then. Won't turn on at all now . Gonna sell it for parts so at least I get some money back.

my maxx xt1225 br is hard brick help please!!!

hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys
Is your bootloader locked or unlocked?
ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock
kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me
kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so
kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593
ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh:

Categories

Resources