Is unlocking your bootloader a prequisite to flashing recovery.img? I have (from what I've gathered) a soft bricked XT 1032, and I forgot which Lollipop version it was running (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files, and got the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooting my phone either. I was running pure OTA stock when my phone suddenly stopped booting up, and went into a boot loop.
You have to unlock the bootloader.
n0ts0smart said:
You have to unlock the bootloader.
Click to expand...
Click to collapse
Ok, so I unlocked BL. I did not really get a clean unlocked message. But now in BL menu, it says in yellow, "Device is UNLOCKED. Status Code: 3". I checked some posts about it, and while ideally Status Code should be 1 (or 0?), a 3 is not necessarily bad. Is that true?
Anyway, I still cannot flash anything into it. I'm mostly getting the "Preflash validation failed" error, or in some cases, the "Failed to erase partition" error.
Am I doomed?
Don't worry. Code 3 is fine. Have you tried to flash custom recovery? Unlocking bootloader is the most time consuming part of getting root. No reason stopping now.
But no your not doomed. Moto pretty difficult to brick IMO. It can be done but you have to mess up pretty bad
---------- Post added at 04:29 AM ---------- Previous post was at 04:07 AM ----------
Go to the TWRP thread and download the recovery image for an XT1032. Then through fastboot flash the recovery image you got from the twrp thread. Let's see how that goes. A working recovery is the goal. You can't do much without one.
The last thing you want to do though is flash random files though so make sure the twrp you download is the one for your phone.
If you need me to be more specific just pm me.
btw long ago I was reluctant to root my device but it turned out to be the best thing I ever did. No warranty means no downside if you ask me. And at this point as I said why stop now?
n0ts0smart said:
Don't worry. Code 3 is fine. Have you tried to flash custom recovery? Unlocking bootloader is the most time consuming part of getting root. No reason stopping now.
But no your not doomed. Moto pretty difficult to brick IMO. It can be done but you have to mess up pretty bad
---------- Post added at 04:29 AM ---------- Previous post was at 04:07 AM ----------
Go to the TWRP thread and download the recovery image for an XT1032. Then through fastboot flash the recovery image you got from the twrp thread. Let's see how that goes. A working recovery is the goal. You can't do much without one.
The last thing you want to do though is flash random files though so make sure the twrp you download is the one for your phone.
If you need me to be more specific just pm me.
btw long ago I was reluctant to root my device but it turned out to be the best thing I ever did. No warranty means no downside if you ask me. And at this point as I said why stop now?
Click to expand...
Click to collapse
Thanks for the encouraging words @n0ts0smart. I have already tried flashing both stock, and now custom (TWRP) recovery images. I keep getting the "Failed to erase partition... Failed to flash partition..." error regardless of the recovery image I try to flash. I have tried flashing partition gpt.bin too, and that gave me the "Preflash vaidation failed" error.
I am at my wit's end, I don't where to go from here. Any help will be much appreciated.
Just so we don't get ahead of ourselves, when you are at the bootloader screen what version does it say? Right below the "Fastboot flash" text?
---------- Post added at 07:24 PM ---------- Previous post was at 06:54 PM ----------
Also are you using fastboot or moto fastboot (mfastboot). I will say in the past I have had a few problems when not using mfastboot. See this link and it goes into some detail. http://mark.cdmaforums.com/MotoX-mFastboot.htm
n0ts0smart said:
Just so we don't get ahead of ourselves, when you are at the bootloader screen what version does it say? Right below the "Fastboot flash" text?
---------- Post added at 07:24 PM ---------- Previous post was at 06:54 PM ----------
Also are you using fastboot or moto fastboot (mfastboot). I will say in the past I have had a few problems when not using mfastboot. See this link and it goes into some detail.
Click to expand...
Click to collapse
Bootloader version is 41.1A. And yes, I am using mfastboot. I will admit though that in the beginning I was using fastboot. But I never got to the part where I would flash large files, so I'm not sure if that is the cause of my trouble. The results have been same with both fastboot and mfastboot for the steps that I have performed.
I really appreciate your help @n0ts0smart, you are the sane voice in my life right now.
Hi
What firmware did you have before flashing the recovery?
Gpe or stock motorola?
You can't flash a gpe recovery in a stock firmware or viceversa, is always going to show an error.
The best thing is flash the 5.0.2 or 5.1 retail firmware or gpe firmware but you have to flash all the files not just the recovery and gpt.bin
Also when you flash 5.1 it upgrades your bootloader to 41.1a so maybe you had 5.1
Hope this helps you
samuelcr93 said:
Hi
What firmware did you have before flashing the recovery?
Gpe or stock motorola?
You can't flash a gpe recovery in a stock firmware or viceversa, is always going to show an error.
The best thing is flash the 5.0.2 or 5.1 retail firmware or gpe firmware but you have to flash all the files not just the recovery and gpt.bin
Also when you flash 5.1 it upgrades your bootloader to 41.1a so maybe you had 5.1
Hope this helps you
Click to expand...
Click to collapse
Thanks @samuelcr93, it actually helps. What you say makes sense. If 41.1A is the 5.1 bootloader, then I must have had 5.1 right? I know I got on the 5 sometime early this year, then I took whatever Motorola offered OTA. I must have thaken 5.1 and I don't remember for sure.
My phone came with 4.2 from the factory, I remember taking 4.4 OTA, then 5 OTA. I have never manually upgraded to any modified version, my phone isn't even rooted. Clearly I was confused about the version, I must have the retail version all the way through.
I am going to find the retail 5.1 and see if that works.
Your welcome, we are here to help
Yes probably you updated to 5.1 and that's why you have that bootloader.
I think flashing stock will fix everything, please let me know if it worked.
I might be wrong on this but I believe taking the ota soak test would also leave you with that version of bootloader. I am reluctant to give advice on something that could potentially put you in a worse position.
With that being said I would download the factory L firmware and try to flash it. If you go that route you mightl still get errors on the motoboot and/or gpt flash command. I would flash the rest or just omit those two all together and flash everything else.
samuelcr93 said:
Your welcome, we are here to help
Yes probably you updated to 5.1 and that's why you have that bootloader.
I think flashing stock will fix everything, please let me know if it worked.
Click to expand...
Click to collapse
I'm on 5.0.2 and I have 41.1A bootloader. so this can't be right
Sent from my Moto G using Tapatalk
bublz654 said:
I'm on 5.0.2 and I have 41.1A bootloader. so this can't be right
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Dont worry 5.0.2 is compatible with 5.1 bootloader, so it wont be a problem.
Maybe when you tried to flash gpt.bin it upgraded the bootloader.
Is your phone working know?
samuelcr93 said:
Dont worry 5.0.2 is compatible with 5.1 bootloader, so it wont be a problem.
Maybe when you tried to flash gpt.bin it upgraded the bootloader.
Is your phone working know?
Click to expand...
Click to collapse
you got the wrong person [emoji14] look at my name
Sent from my Moto G using Tapatalk
bublz654 said:
you got the wrong person [emoji14] look at my name
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
lol youre right sorry bro
samuelcr93 said:
Your welcome, we are here to help
Yes probably you updated to 5.1 and that's why you have that bootloader.
I think flashing stock will fix everything, please let me know if it worked.
Click to expand...
Click to collapse
n0ts0smart said:
I might be wrong on this but I believe taking the ota soak test would also leave you with that version of bootloader. I am reluctant to give advice on something that could potentially put you in a worse position.
With that being said I would download the factory L firmware and try to flash it. If you go that route you mightl still get errors on the motoboot and/or gpt flash command. I would flash the rest or just omit those two all together and flash everything else.
Click to expand...
Click to collapse
@n0ts0smart did you mean the factory Lollipop firmware? Pardon me, I'm a noob and still learning the lingo. If yes, what version of Lollipop would you suggest?
@samuelcr93 Thanks for your suggestion. I found what I think is the 5.1 factory firmware linked here. The instructions to flash assume a working phone, I think, and I'm not sure how to flash it to a phone that wouldn't boot up, or let me flash recovery.img. I thought installing a working recovery.img was the first step before I could do anything meaningful. Hence my post title.
The GPE firmwares I have found (.xml.zip format) have the files recovery.com, motoboot.img, boot.img, gpt.bin, etc. The stock firmware I found at the link above has only boot.img in the root folder. That is the only file I see that I can flash manually. I don't know if I should flash it and risk bricking my phone totally. On the other hand, I am so desperate that I am ready to try anything with even small odds of success.
If you know how to flash this firmware, can you please tell me how? The only tool I have that I can use is the mfastboot. I have ADB but I can't use it. I cannot boot into recovery or flash any kind of recovery image it seems. Are there any other tools that could be useful?
Dont worry im going to help you until your phone is 100% working :good:
If you can boot in fastboot mode then no problem
the firmware that you posted is 5.1 but you have to flash it with a custom recovery so we are not going to use it.
i found the 5.1 US retail here https://mega.nz/#!uwR2wYAI!91LHxqsBFTxZ0U7s8Pzxt5l3EUhvpABZ7jC4Cwv9DUE
Also download mfastbootv2 here https://www.dropbox.com/s/nlbrn71wfqyup4u/mfastboot-v2.zip?dl=0
now to install it follow this steps:
1. extract the 5.1 retail firmware
2. extract mfastboot into the same folder of retail
3.put the phone in fastboot mode and connect it
4. open Command prompt in the folder (shift + right click and select "open command window here" )and run the commands:
mfastboot flash partition gpt.bin
mfastboot reboot-bootloader
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
it should take 10-15 minutes to boot
if everything goes well now your phone will work normally :highfive:
please let me know if it worked
samuelcr93 said:
Dont worry im going to help you until your phone is 100% working :good:
If you can boot in fastboot mode then no problem
the firmware that you posted is 5.1 but you have to flash it with a custom recovery so we are not going to use it.
i found the 5.1 US retail here
:
:
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
it should take 10-15 minutes to boot
if everything goes well now your phone will work normally :highfive:
please let me know if it worked
Click to expand...
Click to collapse
Ok, I downloaded the 5.1 factory firmware and mfastboot from your links, :good:thanks for those. I followed your instructions, and when I started issuing commands, I got errors starting with the very first one. This is what I got...
{
"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 gotta say, this is a new one for me. While it didn't work before, whenever I tried this step before, I had invariably got the "Preflash validation failed" error. This is the first time I'm seeing this error. Progress? I'm not so sure.
The second command to reboot did not boot into to the bootloader menu, it just turned off the phone. So I started it back up in bootloader mode. Starting with flash motoboot, I started getting "failed to erase partition" error...
... until the last command, when I felt it didn't make sense to keep going. I'm not sure what to do at this point.
Can't thank you enough for all you're help.
Mmm can you send me a picture of the phone un fastboot mode?
Sent from my XT1032 using Tapatalk
samuelcr93 said:
Mmm can you send me a picture of the phone un fastboot mode?
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Well, I didn't take any pictures of the phone when I tried your instructions. Let me do it again, and I'll get pictures of the phone.
Related
Hi all,
After flashng several recoveries and ROMs yesterday, my MOTO G 8GB XT1032 (GER) has no WiFi any more.
I can nor turn it on, even if I use the slider for that. After some seconds it goes to OFF again.
I have tried to flash stock 4.4.2 German retail. Rom works perfect, but no WiFi.
What can I do?
I think while flashing, I have overwritten some settings...
Please help a frustrated stupid from Germany....
Edit: What I did and what might be important:
In CWM Touch I formated all what is formatable. Also "none". I thought, that my new installation will be "cleaner".
Thank you all so much in advance!!!!
Maybe there is a ROM I can flash that brings WiFi back?
Is there a way to restore the phone to factory regarding the partitions and relevant files?
How did you flash 4.4.2?
Directly 4.4.2. Stock? Or first 4.3 and then update to 4.4.2?
If 4.4.2 then like this?
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
Click to expand...
Click to collapse
Maybe you can also read here.
Post 3
mokkami said:
How did you flash 4.4.2?
Directly 4.4.2. Stock? Or first 4.3 and then update to 4.4.2?
If 4.4.2 then like this?
Maybe you can also read here.
Post 3
Click to expand...
Click to collapse
Thank you.I will give that a try, too.
I flashed from 4.4.2 GPE to CM11 unofficial and back again.
Something during these steps went wrong...
In recovery I did some stupid formating and wifi was gone.
After my "cool action" I tried flashing nearly every ROM I cold get. No success...
If you really wanna thank me, then hit thanks
mokkami said:
How did you flash 4.4.2?
Directly 4.4.2. Stock? Or first 4.3 and then update to 4.4.2?
If 4.4.2 then like this?
Maybe you can also read here.
Post 3
Click to expand...
Click to collapse
Thanks a lot. The link with Post 3 fixed my the problem.
You are my hero of the day!!!
mokkami said:
If you really wanna thank me, then hit thanks
Click to expand...
Click to collapse
I did that!
Sir, geetings also from Germany. I will open a new thread for that. The solution is quite easy. Give me a short PM
JX
Who are you talking to?
Hi, i saw, that this issue is currently solved. Thanks
Hello Guys,
after a week using Paranoid Android my moto g xt1032 acted weird, so I reinstalled stock using fastboot.
I am pretty familiar with the use of fastboot and flashing and so on (Guess I've flashed, and fixed over 20 different phones)
But now I've come to the point I can't even fix my own phone.
What does it do?
Well, when I start my phone, it will only show the "warning bootloader unlocked" message, and just restarts and does the same.
Sometimes it even gives a blue screen > restarts.
I can boot into fastboot mode, I tried to flash a RETAIL UK 4.4.2 And RETAIL UK 4.3 stock firmware, even though I am from The Netherlands,
but UK or German roms are the closed to mine, and as far as my knowledge goes, EU firmware are usually the same.
I managed to go into stock recovery, but when I flash philz or twrp, it just stays at the "warning bootloader unlocked" screen.
Going to try XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip right now.
same result.
bump
bump
Try this - http://forum.xda-developers.com/moto-g/help/guide-recover-xt1032-gpe-4-4-4-t2824377
While my situation below may not be yours, at least this may get you back to a stable and functional device. I hope it helps. And as you are aware this will COMPLETELY wipe your phone. If you can, backup any pictures or files you want to keep before doing this.
My situation was like many others that had flashed a 4.4.4 GPE or custom ROM and ended up with a mini wifi tablet as the radio was off (as stated by dialing 8#8#4626#*#*). I have gone two days with no cell signal due to this. Trying to flash a stock image (http://sbf.droid-developers.org/phone.php?device=14) resulted in boot loops. I believe that is what everyone else is calling it. I never saw the loop as it stayed on the initial logo screen before the animation begins. Maybe it is looping fast and just showing the same screen again instead of it simply not changing. Oh well. I'm fixed now but on EU ROM. Now I'm attempting to install Blur_Version.174.44.1.falcon_umts.Retail.en.US. The EU ROM currently installed is 176.44.1, and while it works I simply want to be stock US version for now. I mention this because there is also a 174.44.4 US ROM on SBF-DROID-DEV. I tried that one (among many others) when trying to revive my phone. None of the stock images worked and I'm currently not happy with any of the custom ROMs. Stock or rooted stock will be good for me. On a tangent but I have a XT1032 purchased from AIO Wireless (now Criket but still part of ATT). Well AIO tweaked Motorola's ROM to disable tethering. I actually use Red Pocket for service (another ATT MVNO) and only bought from AIO becausse they had a sweet deal. Wasn't so sweet after I found I could not tether and after 6 months found a way to unlock bootloader, which cost another $25. In short it spent just as much money and had much frustration that could have been avoided if I had purchased directly from Motorola and got a FULLY stock and unlockable device.
---------- Post added at 11:51 PM ---------- Previous post was at 11:42 PM ----------
Pass this along also to anyone looking: theroot.ninja worked for me to unlock the bootloader (I've not posted enough to XDA so posting true URL is disabled. Google "sunshine bootloader unlock"). I found a vague reference on XDA somewhere but don't recall thread. Basically, certain carriers (like ATT and its MVNOs) have agreement with Motorola to restrict bootloader unlocking on devices they resell. Like I said, cost me $25, but it worked and I've wasted more $$ on less.
My bootloader is unlocked, I can't get into recovery, only fastboot.
and it stays at the "warning bootloader unlocked screen" aka logo screen, and it restarts so now and then.
When I start it up for the first time, the screen turns blue right away, and restarts, after a couple of restarts, it stays stuck on the logo screen :S
I tried lots of stock firmware, but none of them worked, I wonder if it's a hardware fault, but I reassembled everything, without success.
http://sbf.droid-developers.org no longer has the latest firmware images. You need to read through this thread instead:
http://forum.xda-developers.com/showthread.php?t=2546251
4.4.4 Recovery flashable Stock Motorola zips available here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Regarding fastboot and the 4.4.4 firmware image - you are obviously not doing all the necessary commands. Please state the commands you have used. Since you have updated your bootloader, ensure you are actually attempting to flash a 4.4.4 image, as a 4.4.2 image will result in an error.
lost101 said:
http://sbf.droid-developers.org no longer has the latest firmware images. You need to read through this thread instead:
http://forum.xda-developers.com/showthread.php?t=2546251
4.4.4 Recovery flashable Stock Motorola zips available here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Regarding fastboot and the 4.4.4 firmware image - you are obviously not doing all the necessary commands. Please state the commands you have used. Since you have updated your bootloader, ensure you are actually attempting to flash a 4.4.4 image, as a 4.4.2 image will result in an error.
Click to expand...
Click to collapse
I am pretty sure I am using 4.4.4
I used these commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
I suggest you add the follow command which will entirely wipe any remaining files your phone.
mfastboot erase userdata
lost101 said:
I suggest you add the follow command which will entirely wipe any remaining files your phone.
mfastboot erase userdata
Click to expand...
Click to collapse
Tried it, no change.
Jur13n said:
Tried it, no change.
Click to expand...
Click to collapse
The system flashing commands are wrong. They should be:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
See if that fixes it for you.
meekrawb said:
The system flashing commands are wrong. They should be:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
See if that fixes it for you.
Click to expand...
Click to collapse
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
To be exactly, I know what I am doing
Jur13n said:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
To be exactly, I know what I am doing
Click to expand...
Click to collapse
Okay. Good luck!
Jur13n - did you try http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.
e.martin.howell said:
Jur13n - did you try http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.
Click to expand...
Click to collapse
http://sbf.droid-developers.org/phone.php?device=14 is offline atm, I'll try it.
What do you mean with three downloads o.o?
I only see him saying Blur_Version.174.44.1.falcon_umts.Retail.en.US
Your issue could be due to older images. Here is the EU Retail 4.4.4 image. It doesn't matter where you are in the world, it will work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
lost101 said:
Your issue could be due to older images. Here is the EU Retail 4.4.4 image. It doesn't matter where you are in the world, it will work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
Click to expand...
Click to collapse
Tried it, didn't work.
Going to try the Blur_Version.174.44.1.falcon_umts.Retail.en.US one right now.
-- edit --
no result, also tried to convert it to gpe, no result either.
I guess it's a hardware problem somehow (maybe reading the harddisk fails?)
If you still have the box that the phone came in look at it and it will tell you which Moto G you have.
Hi,
after an apparently failed attempt to install the 5.0 OTA update my XT1032 now will boot to a droid lying on its back.
I went to the recovery from there (by pressing VolUp+Power) and did the "factory reset/wipe data" and rebooted.
Same result.
I did "wipe chache". Same result: Droid lying on its back, saying "Kein Befehl" (I guess that means "no command")
I can get into recovery mode (CWM was installed before all this*) so I could try to flash stuff from outside.
But what should I try to flash? I tried flashing a (supposedly) stock system but as soon as I start with "fastboot flash boot boot.img" the phone starts booting again. So I am not really sure what to do now.
Something is seriously wrong with this phone and I would like to restore it to stock settings. I bought it on amazon.DE - so if any one of you guys knows where I could find a truly original stock image for this phone and what to do with it, please let me know.
PS: Right now I can't even get into recovery anymore. The thing just keeps booting and booting. Can't even turn it off.
* meaning: before I flashed the supposed stock recovery that apparently, in combination with the OTA update, got me into this mess
I now followed this guide:
http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I used option 3b with a 4.4.4 rom ( RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF )
I excuted all these commands. However, upon flashing the boot.img the phone immediately boots (and gets stuck).
So I re-entered fastboot again to finish the job. Everything else went fine.
But the problem persists: When booting, the phone now displays the "Warning: Bootloader unlocked" message for a long time, with a kind of water ripple effect from bottom to top, repeating.
When I switch it off, it switches back on automatically, trying to boot and getting stuck at this screen. Sometimes I get to the droid lying on its back with a red !-Triangle on top. Poor little bugger. Soft bricked.
What can I do to fix this?
I can still enter fastboot.
I assume that yet again I grabbed the wrong ROM.
Is this supposed to be dead? http://sbf.droid-developers.org/phone.php?device=14
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
legolas06 said:
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
Click to expand...
Click to collapse
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
fertchen said:
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
Click to expand...
Click to collapse
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
audit13 said:
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
Click to expand...
Click to collapse
The problem here is that the phone will boot as soon as I flash the boot.img and the whole thing fails.
Do you see a way out of this situation?
Any way to do this with a .zip ROM?
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
@Fretchen
That might be because you are on lollipop bootloader & you are trying to flash kitkat bootloader?But I may be wrong. Previously you told that you tried restoring to kitkat & that boot.img is kitkat bootloader. Try with this lollipop firmware.
audit13 said:
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
Click to expand...
Click to collapse
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
fertchen said:
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
Happy that I could help.
You flashed the stock firmware so everything should work again. OTA updates if available would work.
fertchen said:
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
I don't know if you can apply OTA updates. Before the OTA update will work, you may need to update all Motorol apps via Play store.
You could wait until a fulkl stock lollipop pop is released for your phone and flash it using fastboot.
You can try different ROMs but stick to the ROMs made for your model. I have an xt1032 and I have installed US Retail, stock Telus, and GPE.
worked for me too, thank you soo much. give this solution a try
legolas06 said:
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
Click to expand...
Click to collapse
these steps look soo similar that the ones you can find in other blogs/discussions, but for me, in my case the main difference was the firmware, I tried with a loot of them, but the one that is mentioned in this post, installed smoothly, and with no issues, thank you so much, to post your experience and this solution.
My Best Regards,
Esteban
Greetings,
Just sharing this info, if you install verizon stock firmware on at&t iusacell Mexico, you will be able to update till nougat. I already tried with success, you just need unlocked bootloader and the moto z verizon stock firmware (wich is on this forum).
Wold like to upload a photo but i dont know how.
Flashing stock verizon will not relock your bootloader, and you will get the 2.2 ghz cpu and 610 mhz gpu from verizon rom.
You willl find the software at:
http://forum.xda-developers.com/moto...loads-t3449837
Choose the verizon version. You may also search:
"XT1650_GRIFFIN_VERIZON_MCL24.203-22_cid2_subsidy-DEFAULT_CFC.xml.zip"
on google for improved download speeds.
After you downloaded the firmware, flasht it over fastboot.
You may try this instructions over cmd to flash it (just like i did):
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
after that:
- Let the phone make the first boot (your may signup with with your google account, because you will not loose the information over the updates)
- Go to settings and search for updates
- Keep updating till Nougat (think i updated the phone like 3 times, till it get to Nougat).
- Enjoy
will flashing verizon rom relock your bootloader ?
and which verizon rom did u flash - can u link to the message ?
reiteravi said:
will flashing verizon rom relock your bootloader ?
and which verizon rom did u flash - can u link to the message ?
Click to expand...
Click to collapse
Flashing stock verizon will not relock your bootloader, and you will get the 2.2 ghz cpu and 610 mhz gpu from verizon rom.
You willl find the software at http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837
Choose the verizon version. You may also search "XT1650_GRIFFIN_VERIZON_MCL24.203-22_cid2_subsidy-DEFAULT_CFC.xml.zip" on google for improved download speeds.
imagen jpg
And... By the way, no bugs at all.
- ALL MODS WORKING
- CALLING WORKING
- WIFI, DATA WORKING
been using it on my moto z almost 12 hours without any crash or issue at sight
Thanks man
i have this file
how did u flash it ? using twrp ?
U think works on two sim mexican moto z?
reiteravi said:
Thanks man
i have this file
how did u flash it ? using twrp ?
Click to expand...
Click to collapse
I flash it using fastboot commands, if you want it i will upload the full instructions, just hold me 2 hours, im far from my computer and i dont wanna write the flash file again xD.
estanenmi said:
U think works on two sim mexican moto z?
Click to expand...
Click to collapse
I think it will works on any moto z, but if anything goes wrong you may reflash the stock retail mexican rom again (cause you buy it directly from motorola, isnt?) .
90dfx said:
Greetings,
Just sharing this info, if you install verizon stock firmware on at&t iusacell Mexico, you will be able to update till nougat. I already tried with success, you just need unlocked bootloader and the moto z verizon stock firmware (wich is on this forum).
Wold like to upload a photo but i dont know how.
Click to expand...
Click to collapse
Have you "Verizon flashers" doublechecked if the supported LTE bands are reduced this way?
Verizon's models support a lot less bands than international models...
enetec said:
Have you "Verizon flashers" doublechecked if the supported LTE bands are reduced this way?
Verizon's models support a lot less bands than international models...
Click to expand...
Click to collapse
Yes, i know this is something really strange, but.... It works! 4g lte! No issue at all.
It's a kind of contradictorious stuff, verizon rom being compatible and useful for anothers xD
{
"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"
}
90dfx said:
Yes, i know this is something really strange, but.... It works! 4g lte! No issue at all.
It's a kind of contradictorious stuff, verizon rom being compatible and useful for anothers xD
Click to expand...
Click to collapse
Yes, but check how many of them are still supported using Network Signal Guru...
Sorry, dont know how to use that tool :/ why dont you try it and see??
By the way, day dream crash after welcome screen... But i think this is something related to the app, because thats the only crash i had on 24 hours using this rom
Worked like a charm on my Bell Moto Z up here in Canada. Now all we need to do is unencrypt the storage and get root
EDIT - Went back to stock 6.0.1 worked ok, then for some reason I cannot boot now into any type of rom or software. The only thing I can think of are these three commands did something?
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
I've never used those on any other rom or going back to stock in Fastboot ever before.
Happened to me the same a few hours back.
Cant go back to 6.0, its something related to nougat partitions.
Only way to boot is installing nougat again and thats is installling last update from verizon before nougat:
https://drive.google.com/open?id=0ByioJuadKHC6MjJDXzhJSXlBaDA
And them install the OTA to nougat over stock recovery using adb sideload from your pc.
Thats how i did and finally boot. Lets see if someone find some workaround to this issue
90dfx said:
Sorry, dont know how to use that tool :/ why dont you try it and see??
...
Click to expand...
Click to collapse
No way...!
If you want to check you have to: start Network Signal Guru, grant root, press magic wand, then select bands locking, then LTE... you will see all the LTE bands supported by phone at the moment. Then *cancel* and select Exit on three dot menu.
Simple enough?
enetec said:
No way...!
If you want to check you have to: start Network Signal Guru, grant root, press magic wand, then select bands locking, then LTE... you will see all the LTE bands supported by phone at the moment. Then *cancel* and select Exit on three dot menu.
Simple enough?
Click to expand...
Click to collapse
Well.. it sounds easy but how do i root, to grant permission
Tried with turbo kernel to disable encryption and them installing supersu(system mode) (just booting from twrp), but it doesn't boot... And it takes like age's to get it back to a bootable nougat xD
90dfx said:
Well.. it sounds easy but how do i root, to grant permission
Tried with turbo kernel to disable encryption and them installing supersu(system mode) (just booting from twrp), but it doesn't boot... And it takes like age's to get it back to a bootable nougat xD
Click to expand...
Click to collapse
Try like it worked on MM: disable encryption (fully, not only by flashing kernel or patch...), flash Magisk v.9 and then SuperSU official/stock v.2.78... (NOT forced 2 system one...)
Reboot to system after every step...
Hi guys I just wanna to say it's really dangerous to flash Verizon OTA on non Verizon device
Because on this OTA and firmware we have some images like partition (gpt), modem and other firmwares like Bluetooth..
This may affect on your device modem.
Personally i suggest you guys not to install it on your devices and I have only one request to who did this and got nought on unlocked device.
Please get system image and boot partition backup with TWRP and share it to public or me.
I promise I'll create flashable zip to not flash modem and gpt, .. for safety
And you can back to marshmallow whenever you want
Thanks a lot
I 100% agree...
estanenmi said:
U think works on two sim mexican moto z?
Click to expand...
Click to collapse
Yes. You can flash any system of any version because the hardware is the same. You will lose two SIM options because ia software related and Verizon only has one SIM version. My advice is not to flash this because maybe you won't be able to use two SIM in the future. And I think that Verizon and AT&T are only 32 GB not 64 like the unlock versions.
Sent from my XT1650 using XDA-Developers mobile app
enetec said:
Try like it worked on MM: disable encryption (fully, not only by flashing kernel or patch...), flash Magisk v.9 and then SuperSU official/stock v.2.78... (NOT forced 2 system one...)
Reboot to system after every step...
Click to expand...
Click to collapse
How did you disable encryption?... Flashing boot image and them wipe data, dalvik and cache?...
Would like to try it but dont i dont think it will work cause that was the boot image of marshmallow, and feel to much lazy to recover a brickphone xD..... So maybe at weekend xD
erfanoabdi said:
Hi guys I just wanna to say it's really dangerous to flash Verizon OTA on non Verizon device
Because on this OTA and firmware we have some images like partition (gpt), modem and other firmwares like Bluetooth..
This may affect on your device modem.
Personally i suggest you guys not to install it on your devices and I have only one request to who did this and got nought on unlocked device.
Please get system image and boot partition backup with TWRP and share it to public or me.
I promise I'll create flashable zip to not flash modem and gpt, .. for safety
And you can back to marshmallow whenever you want
Thanks a lot
Click to expand...
Click to collapse
Sure, no problem but yesterday after flashed and use twrp, my moto z didnt boot. Do you think that if i just "boot" (fastboot boot twrp.img) i will be able to boot after made the backup?
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Code:
fastboot devices
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Thanks for posting this. I was actually going to upload it myself. You save me from having to do the work
weakNPCdotCom said:
Thanks for posting this. I was actually going to upload it myself. You save me from having to do the work
Click to expand...
Click to collapse
Not a problem.... I actually found most of the firmwares that MotoJunkie01 had posted, I might repost his firmware post (copy and paste) and replace the links after i upload them to my own Gdrive, when I have time....
AesopRock127 said:
Not a problem.... I actually found most of the firmwares that MotoJunkie01 had posted, I might repost his firmware post (copy and paste) and replace the links after i upload them to my own Gdrive, when I have time....
Click to expand...
Click to collapse
sweet. sounds great man. thank you
NM connection working now
https://mirrors.lolinet.com/firmware/moto/ look here for firmware and make sure its correct one and up to date before flashing it.
AesopRock127 said:
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Click to expand...
Click to collapse
How did you get your phone to work meaning when I call some one they can't hear me but I can hear them .I re-flashed so many ROMs already that I'm staying on GSI Rom 8.1.0 Hanna metro PC's also I did flash stock Rom and still the see problem maybe it's time for replacement. It's been 3 days searching and asking for help. Maybe device to new idk ..
skullkid383 said:
https://mirrors.lolinet.com/firmware/moto/ look here for firmware and make sure its correct one and up to date before flashing it.
Click to expand...
Click to collapse
dude this link is worth money. amazing. thank you so much.
weakNPCdotCom said:
dude this link is worth money. amazing. thank you so much.
Click to expand...
Click to collapse
Yeah I used it on my Perry before I got hannah so it was first place looked when I needed Hannah fw
Googleme35 said:
How did you get your phone to work meaning when I call some one they can't hear me but I can hear them .I re-flashed so many ROMs already that I'm staying on GSI Rom 8.1.0 Hanna metro PC's also I did flash stock Rom and still the see problem maybe it's time for replacement. It's been 3 days searching and asking for help. Maybe device to new idk ..
Click to expand...
Click to collapse
I got mine to work because I have a James device.... You mention Hannah device so guessing you flashed the wrong firmware and that's the issue. I have the James xt1921-3
AesopRock127 said:
I got mine to work because I have a James device.... You mention Hannah device so guessing you flashed the wrong firmware and that's the issue. I have the James xt1921-3
Click to expand...
Click to collapse
Ok Thanks
I'm glad i could be of assistance,i was actually hunting down root methods for my GFs samsung and saw a video that linked to the user who uploaded it to AFH, rootjunkie was the channel if i recall,so i can't take all of that sweet credit. Yall have fun,but not too much fun
AesopRock127 said:
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Code:
fastboot devices
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Click to expand...
Click to collapse
PLEASE tell me how you fixed the IMEI/SIM not recognized issue. I can't figure this out at all. Thanks!
OMG!!!! This was a god send. Thank you guys for putting this together for us. I thought all hope was lost. My phone is back and running. YaY!!!!!!
weakNPCdotCom said:
dude this link is worth money. amazing. thank you so much.
Click to expand...
Click to collapse
I keep getting unsecured network... Is this an issue from my end?
How do you backup IMEI in TWRP?
EFS?
Mine won't mount data for backup and cache in red
Or should I do it another way?
I have XT1924-2 AND I TOO HAVE IMEI=0 ANY FIXES?
Thank you!
This was very helpful, thanks!
TheLastAlphaUK said:
I have XT1924-2 AND I TOO HAVE IMEI=0 ANY FIXES?
Click to expand...
Click to collapse
Flash most up-to-date software
skullkid383 said:
Flash most up-to-date software
Click to expand...
Click to collapse
That's a weird Necro-Response. Also updating doesn't fix IMEI, (even though this was over a year ago, they would need an IMEI flasher and the box/numbers found somewhere else)