I had a dabble with the GPE ext4 lollipop on my GB XT1032 but found I cannot re lock my bootloader so would like to go back to stock f2fs 4.4.4 kitkat.
Im currently downloading XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip and was planning to go back with fastboot with the following 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
mfastboot erase userdata
mfastboot reboot
After reading up before attempting this i'm understanding that if you go back to 4.4.3 you will brick on the next ota.
If I was to flash the gpt and bootloader from 4.4.4 as above i'm guessing that if it succeeds then the next ota being lollipop should go ok?
If anyone has tried the above and then got the 5.x ota and it worked out fine would be helpful to hear how you got it to work.
Thanks!
Before anything else, try formatting 'Data' to f2fs in custom recovery and flashing this: http://forum.xda-developers.com/moto-g/development/rom-titan-rom-single-sim-t3004757
I'll install twrp and have a go at formatting f2fs.......
Is there a reason for flashing the rom in the link first?
hmmm? I was thinking if i was to flash the gpt.bin from a stock moto rom then this would setup the partitions as f2fs anyway before proceeding onto the next components to flash?
Yes, you are correct; flashing gpt.bin will do as you say. I was suggesting you avoid fastboot if possible - to minimize the risk of bricking.
lost101 said:
Yes, you are correct; flashing gpt.bin will do as you say. I was suggesting you avoid fastboot if possible - to minimize the risk of bricking.
Click to expand...
Click to collapse
I had a go at flashing and everything went ok and it boots up fine but the display is acting like it has a scan line scrolling down the screen!
When I flashed everything flashed ok apart from motoboot.img which gave me the following error:-
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.105s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.368s
I'm guessing this is for the kernel and i'm now left running the lollipop kernel with kitkat, yeah?
Is there anyway I can get motoboot.img to flash?
rockyrobin said:
I'm guessing this is for the kernel and i'm now left running the lollipop kernel with kitkat, yeah?
Is there anyway I can get motoboot.img to flash?
Click to expand...
Click to collapse
motoboot.img is the Bootloader. Don't try flashing it again.
boot.img is the Kernel. Does the scan-line go away if you turn screen off and on?
lost101 said:
motoboot.img is the Bootloader. Don't try flashing it again.
boot.img is the Kernel. Does the scan-line go away if you turn screen off and on?
Click to expand...
Click to collapse
I'll leave the bootloader alone then like you recommend. Would be just my luck to invoke the straw that broke the camels back!
I performed all my updates with the play store and found an update for 'Motorola boot services' which I applied. Don't know if this is related but when I rebooted everything is now OK with the scan line gone.
Im going to leave alone for now, and when the lollipop update turns up will look again at relocking my bootloader.
Thanks for your help!
rockyrobin said:
I'll leave the bootloader alone then like you recommend. Would be just my luck to invoke the straw that broke the camels back!
I performed all my updates with the play store and found an update for 'Motorola boot services' which I applied. Don't know if this is related but when I rebooted everything is now OK with the scan line gone.
Im going to leave alone for now, and when the lollipop update turns up will look again at relocking my bootloader.
Click to expand...
Click to collapse
Every time you apply an OTA Update there is a risk of brick. I would suggest you are ready, flash a ROM zip for Lollipop instead via Custom Recovery. They are available in beta form at the moment in /Development - and Final ROMs will be available in the near future.
Related
Hello, so i have a Moto G XT1032 from Telus. Not too long ago i decided to root it (bad idea). Later on i decided that i don't want the root anymore and decided to unroot it. I thought i succeeded but when time came to update from Android 4.4.4 to 5.0 i proved myself wrong. When Android 5.0 started to install, it was installing through CWM and it was ending up giving me a error. I wanted to get rid of CWM and searched up some tutorials and ended up finding out that i have to flash my phone back to stock firmware. I flashed the wrong firmware and ended up converting my XT1032 to XT1033 Dual-Sim. I then found the good Telus firmware for my XT1032 but when i flashed it and connect my phone to my pc, my pc says that a XT1033 is connected. I'm also not able to lock bootloader, it gives me "bootloader sst lock failure". So please help me!
-Thank You
Did you flash the 4.4.4 firmware? Did you flash all partitions manually? No need to lock the bootloader to get the OTA update.
audit13 said:
Did you flash the 4.4.4 firmware? Did you flash all partitions manually? No need to lock the bootloader to get the OTA update.
Click to expand...
Click to collapse
Yes i flashed the 4.4.4 firmware XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml.
By flashing all partitions manually, do you mean this?
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
Then yes.
Which bootloader version is on your phone? All partitions flashed without issue?
audit13 said:
Which bootloader version is on your phone? All partitions flashed without issue?
Click to expand...
Click to collapse
How do i check the version? and yes all partitions flashed without any issue
Boot into fastboot on the phone and look at the top. It will be 41.xx
audit13 said:
Boot into fastboot on the phone and look at the top. It will be 41.xx
Click to expand...
Click to collapse
41.18
dystieguy said:
41.18
Click to expand...
Click to collapse
With TWRP installed wipe data, cache and system partitions, and then reinstall with mfastboot again. :good:
Feche said:
With TWRP installed wipe data, cache and system partitions, and then reinstall with mfastboot again. :good:
Click to expand...
Click to collapse
I lost you over here, what's TWRP and how do i wipe data, cache and system partitions? (Sorry, i'm a noob in this)
dystieguy said:
I lost you over here, what's TWRP and how do i wipe data, cache and system partitions? (Sorry, i'm a noob in this)
Click to expand...
Click to collapse
TWRP is a custom recovery (like CWM) that will let you flash .zips, and do other things like wipe data partition, system partition, etc.
You can download it here
If you have TeamViewer I can help you :highfive:
You have the LP bootloader which is 41.18.
You didn't get an error trying to flash the motoboot.img file?
Feche said:
TWRP is a custom recovery (like CWM) that will let you flash .zips, and do other things like wipe data partition, system partition, etc.
You can download it here
If you have TeamViewer I can help you :highfive:
Click to expand...
Click to collapse
I need ROOT for this but i already removed root from my phone.
audit13 said:
You have the LP bootloader which is 41.18.
You didn't get an error trying to flash the motoboot.img file?
Click to expand...
Click to collapse
I think i did actually, it said in purple downgraded something.
dystieguy said:
I need ROOT for this but i already removed root from my phone.
Click to expand...
Click to collapse
You don't need to be rooted, just bootloader unlocked.
Feche said:
You don't need to be rooted, just bootloader unlocked.
Click to expand...
Click to collapse
Wait, i don't need to download the android app?
dystieguy said:
I think i did actually, it said in purple downgraded something.
Click to expand...
Click to collapse
If it downgraded the bootloader while flashing KK, you would not have a 41.18 bootloader.
audit13 said:
If it downgraded the bootloader while flashing KK, you would not have a 41.18 bootloader.
Click to expand...
Click to collapse
Should i try re-flashing it and tell you if i get any issues?
Try flashing just the motoboot file and let me know if it goes through. If it does and you are still on the 41.18 bootloader, that indicates to me that you're re-flashing the same bootloader.
audit13 said:
Try flashing just the motoboot file and let me know if it goes through. If it does and you are still on the 41.18 bootloader, that indicates to me that you're re-flashing the same bootloader.
Click to expand...
Click to collapse
it gives this:
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.078s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.328s
The bootloader is not flashing because you are trying to downgrade from 41.18 to 41.13.
Do you receive any error messages when flashing the rest of the ROM?
Hey guys. I got a telus moto g xt1032. It was on official 5.0.2. I flashed TWPR 2.8.5.0, and encountered the bootloop bug. I proceeded to flash the only stock telus firmware i could find- 4.4.4. I followed the guide on XDA to the tee and resulted in my moto go being stuck at the "Warning, boot loader unlocked" screen. I have no idea what to do and would really appreciate some help, as I am new to this. Am even willing to donate if it results in me fixing my phone. Thank for taking the time to read
Try doing the following Fastboot commands manually:
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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
Provide a log of what happens, if this does not work.
lost101 said:
Try doing the following Fastboot commands manually:
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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
Provide a log of what happens, if this does not work.
Click to expand...
Click to collapse
I also have this problem. I am trying to downgrade to 4.4.4 stock firmware (from 5.02) and I'm getting an this error:
$ fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.042s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.336s
Click to expand...
Click to collapse
All the other commands are successful but the device remain stucked on the boot screen after the reboot :crying:
I have this problem too, trying to factory reset my phone but it's still stuck on the bootloader. CWM says can't mount sd card now aswell so any help would be appreciated
I got the stock Telus 4.4.4 firmware from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
lost101 said:
Try doing the following Fastboot commands manually:
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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
Provide a log of what happens, if this does not work.
Click to expand...
Click to collapse
hey man, ok ill try that again. The only thing is, there is no boot.img in the telus file I downloaded. Its named "motoboot." Should i replace that with the boot img part? Also, i recently read somewhere trying to downgrde from 5.0.2 to 4.4.4 will mess my phone up. Is that true?
EDIT- I do remember the first time i tried this after sparsechunk.1, is sad "image file is too large" but kept on goiing anyways
audit13 said:
I got the stock Telus 4.4.4 firmware from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
Click to expand...
Click to collapse
theres 2 telus ones. How do you know which one to use? Also i tried flashing one of them im pretty sure and am stuck at the screen in OP
butthurtlocker said:
hey man, ok ill try that again. The only thing is, there is no boot.img in the telus file I downloaded. Its named "motoboot." Should i replace that with the boot img part? Also, i recently read somewhere trying to downgrde from 5.0.2 to 4.4.4 will mess my phone up. Is that true?
EDIT- I do remember the first time i tried this after sparsechunk.1, is sad "image file is too large" but kept on goiing anyways
Click to expand...
Click to collapse
motoboot.img and boot.img are not the same thing. Be careful renaming these files, or else you will destroy your phone. If there is no boot.img included then that zip has been messed with by someone.
The 'image file is too large' message should not be ignored - it means the firmware has not flashed at all. Nothing has changed on your phone; flash has not been successful.
butthurtlocker said:
theres 2 telus ones. How do you know which one to use? Also i tried flashing one of them im pretty sure and am stuck at the screen in OP
Click to expand...
Click to collapse
I used this one: XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml
Then I updated Motorola Apps via Play store, then get the OTA update to 5.02.
lost101 said:
motoboot.img and boot.img are not the same thing. Be careful renaming these files, or else you will destroy your phone. If there is no boot.img included then that zip has been messed with by someone.
The 'image file is too large' message should not be ignored - it means the firmware has not flashed at all. Nothing has changed on your phone; flash has not been successful.
Click to expand...
Click to collapse
good to know thanks. theres only 2 stock telus files, and one didnt have the boot.img. so ill have to hope the other does. I managed to get my phone booted on GpE 4.4. now im just trying to get back to stock motorola. Is there a guide you could link me to?
audit13 said:
I used this one: XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml
Then I updated Motorola Apps via Play store, then get the OTA update to 5.02.
Click to expand...
Click to collapse
did that file have a boot.img?
butthurtlocker said:
good to know thanks. theres only 2 stock telus files, and one didnt have the boot.img. so ill have to hope the other does. I managed to get my phone booted on GpE 4.4. now im just trying to get back to stock motorola. Is there a guide you could link me to?
Click to expand...
Click to collapse
Fastboot Tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
Yes, the boot.img file is included.
Hi everyone,
I follow this awesome forum for several years now. Unfortunately, I currently have a problem which I do not get solved on my own and hope for your support:
My xt1032 (non GPE, non LTE) is stuck at bootlogo no matter what rom I flash! :crying:
Background:
Some time ago I successfully converted my device to the GPE edition using MotoTool. After Lollipop was finalized and penetrated me to update, I did him the favor. As some apps were no longer compatible, I restored my nandroid backup and lived with the ongoing update message.
Now that I leave the device to my wife, I'm trying to flash a factory image of desirably 5.1 GPE.
First I tried to flash GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip using fastboot:
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
... stuck in Google bootlogo.
Then I tried to flash XT1032_FALCON-RETEU_5.0.2_LXB22.46-28.1_1_cid7_CFC_1FF.xml.zip also using fastboot:
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
.. stuck in Motorola unlocked bootloader warning.
I also tried to flash GPE_XT1032_KTU84P.M003_CFC.xml.zip again using fastboot:
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
.. stuck in Google bootlogo again.
I even tried to 'convert to GPE' in MotoTool as I did before using the same image as it was then. Unfortunately with the same result...
I'm a bit desperate right now! My research into threads with similar problems have led to no result. Solutions like flashing gptfix.bin didn't to the trick. What am I doing wrong? Can anyone point me to the right direction please?
Thanks in advance!
*nikon
*push*
I tried this and that in the meantime... all I get are bootscreens in multiple versions. After all I still have fastboot access.
My wife is getting nervous and so am I! Do I have a brick now?
Thanks in advance!
*nikon
I'm gonna make an educated guess its probably formation the GPE-rom uses ext4 in /data and the motorala uses F2FS (those are linux file-systems). GPE doesn't work with F2FS and Moto doesn't work with EXT4.
And assuming you use the TWRP as your recovery? If not install it with Mototools or fastboot to recover your phone (I'm not 100% sure if this is the only method but is the only method I can think of).
Step 1) Download the right recovery from this thread. If you want GPE-rom download GPE otherwise download falcon. Instructions are given in this thread.
Step 2) Start your recovery via fastboot and than choose recovery (use sound button down to scroll, up to select). If everything is allright your booting to a recovery menu with touchbuttons.
Step 3) Choose wipe -->> Advanced wipe -->> select data -->> Repair or Change File System -->> Choose F2FS or Ext4 depending on your choose for moto (F2FS) or an GPE rom. (Ext4). Repeat this steps for /system and /cache.
Step 4) Do a factory reset just to be sure (not sure if necessary, better safe than sorry)
Step 5) Flash your rom of choose
Step 6) Report back to me when succeeded if not report back with more information.
I like this thread its friendly and much information is given and your seem very polite (Learn from this man you screamy panicking kids). There is how ever some essential information missing.
-Which recovery did you use?
-What is your bootloader version?
-From which rom are you coming?
P.s. I never used Fastboot to flash an complete rom only for recovery's (except for my oldskool G1, but that was long ago). I like flashing via recovery most roms are tested and made for flashing via TWRP or CWMR (mostly specified from dev).
P.s.s. I tried my best English! Its not my first language.
@*nikon - provide a fastboot log of the entire flashing process. I want to see any message fastboot is presenting.
Also, you do not need to change the format of /data manually - flashing the gpt.bin does that automatically.
EDIT: Using TWRP to flash a custom ROM is much safer than flashing fastboot images. A flashable GPE 5.1 ROM is available here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Shortly beforehand: thanks a lot for your responses! Very nice to have some feedback!
After being quite busy this weekend, I now have the time to dig into this again.
@Xacky: My apologies for the missing information.
I've tried different recoveries, mainly stock recovery or TWRP depending on my current flash try. Thank you that you have pointed out to me on the recovery thread where I became aware of the GPE edition of TWRP. I'll take this one in the future if I get this hopefully running sometime.
My current bootloader version is 41.18 because last time I tried to downgrade again to 4.4.4. But I also had version 41.19 running with my Lollipop tries.
Concerning the rom I was coming from, I thought my description was relatively detailed. The original was a (NON-GPE) Moto rom, upgraded to 4.4.4 GPE by Moto Tool, then OTA upgraded some time to 5.0.1, downgraded by naindroid backup restore and then tried to flash a 5.1 GPE factory image via fastboot. Then the journey began...
@lost101: Thanks for the information that the format is no issue since it is defined by gpt.bin. I'll give the images from your thread a try and get back in when my battery is ready for flashing again. I also try to save a log which I can post here, if necessary by hand.
Greetz
*nikon
I'm back with good news! :victory:
Unfortunately I still don't know what the problem was (and I really can't stand this!!), but it seems to be solved. I successfully managed to downgrade to 4.4.4 with the image from this thread and then I was able to flash GPE 5.1 as stated in this tutorial.
Afterall kind of weird because I am firm conviction that I've not done anything else manually in the beginning.
Nonetheless, thanks for listening!
Greetz
*nikon
Hey Nikon,
I'm running into the same issue as you. My only question is: is there still screen flickering once you've updated to 5.1? thx
Hey pables69,
sry for beeing late - I was quiet busy the last few days.
To answer your question:
No, fortunately screen flickering is also gone since the upgrade! :good:
Greetz
*nikon
Hi,
I was running CM12(5.0.2) on my xt1032 US GSM. I read in some thread for moto G 2014 that erasing modemst1 and modemst2 from bootloader fixed the no GPS fix. so i tried it in my moto g 2013 and after rebooting there is no network status. when i insert other sims, it shows no sim card. How can i fix this?
Thanks in advance
Download XT1032 Retail US 5.0.2 Lollipop Firmware image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Use only the following fastboot commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
Report back how it goes.
lost101 said:
Download XT1032 Retail US 5.0.2 Lollipop Firmware image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Use only the following fastboot commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
Report back how it goes.
Click to expand...
Click to collapse
Sir, I flashed CM 12 on top of 4.4.4 stock. I never updated my bootloader. Would it be okay to flash XT1032 Retail US 5.0.2 Lollipop Firmware's NON-HLOS.bin?
gearguy365 said:
Sir, I flashed CM 12 on top of 4.4.4 stock. I never updated my bootloader. Would it be okay to flash XT1032 Retail US 5.0.2 Lollipop Firmware's NON-HLOS.bin?
Click to expand...
Click to collapse
You can use the XT1032 Retail US 4.4.4 Firmware files instead to be safe.
I did that but it didnt solve the problem
Just FTR, erasing modemst1/2 can lead to problems: https://github.com/CyanogenMod/android_device_motorola_victara/issues/1#issuecomment-96288956
The method mentioned in the link above worked for me in this situation:
- newly bought xt1039
- ota updated to 5.1
- no gps activation in stock rom ever
- unlocked bootloader, flashed twrp
- backup of stock rom
- flashed cm12.1
- no gps lock
- restored stock rom from backup
- activated gps and got a lock
- re-flashed cm12.1
- gps works
gearguy365 said:
I did that but it didnt solve the problem
Click to expand...
Click to collapse
@gearguy365 - are you using mfastboot? Please provide a fastboot log if you still have problems.
mfastboot: https://www.androidfilehost.com/?fid=23578570567719065
lost101 said:
@gearguy365 - are you using mfastboot? Please provide a fastboot log if you still have problems.
mfastboot: https://www.androidfilehost.com/?fid=23578570567719065
Click to expand...
Click to collapse
I have the complete android SDK, so i am using the ADB provided in its platform tools. So only fastboot commands should work right?
gearguy365 said:
I have the complete android SDK, so i am using the ADB provided in its platform tools. So only fastboot commands should work right?
Click to expand...
Click to collapse
adb and fastboot are not the same thing. Put phone into fastboot mode and use mfastboot and the commands I stated.
lost101 said:
adb and fastboot are not the same thing. Put phone into fastboot mode and use mfastboot and the commands I stated.
Click to expand...
Click to collapse
I downloaded mfastboot and repeated the process, I have attached the cmd log and image of the phone's screen while in fastboot mode:
Code:
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 1.900s]
writing 'modem'...
OKAY [ 2.258s]
finished. total time: 4.166s
C:\mfastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.167s]
finished. total time: 0.170s
C:\mfastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.027s]
finished. total time: 0.031s
C:\mfastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (707 KB)...
OKAY [ 0.073s]
writing 'fsg'...
OKAY [ 6.819s]
finished. total time: 6.897s
C:\mfastboot>mfastboot reboot
rebooting...
finished. total time: 0.005s
The result is same. Still no network. My phone is even detecting the network name i'm in, but the signal bar is absolutely empty. Pressing and holding the power button gives the impression that its on ariplane mode, but turning the airplane mode off from there makes no effect. Please check the attached images. I'm really puzzled at this moment.....
gearguy365 said:
The result is same. Still no network.
Click to expand...
Click to collapse
Did you have Network connectivity in CM12.1 prior to flashing the GPS fix? Link me to the zip if possible.
I thought recent versions of CM12 required the Lollipop Bootloader to even boot?
lost101 said:
Did you have Network connectivity in CM12.1 prior to flashing the GPS fix? Link me to the zip if possible.
I thought recent versions of CM12 required the Lollipop Bootloader to even boot?
Click to expand...
Click to collapse
Yes, prior to attempting to solve that GPS problem i had full network/data connectivity on both GSM and HSPA on my operator. Only after trying to do modemst 1 & 2 clearing i am facing this problem. And yes, my CM 12 version is quite old. 20150322-NIGHTLY to be specific.
I didnt update to the later nightlys which required the up to date bootloader.
gearguy365 said:
Yes, prior to attempting to solve that GPS problem i had full network/data connectivity on both GSM and HSPA on my operator. Only after trying to do modemst 1 & 2 clearing i am facing this problem. And yes, my CM 12 version is quite old. 20150322-NIGHTLY to be specific.
I didnt update to the later nightlys which required the up to date bootloader.
Click to expand...
Click to collapse
Can you try doing a clean install of the ROM? Alternatively flash via mfastboot the entire Stock 4.4.4 Firmware files, excluding: motoboot.img and recovery.img - you could then wipe and flash CM12 if all was working.
lost101 said:
Can you try doing a clean install of the ROM? Alternatively flash via mfastboot the entire Stock 4.4.4 Firmware files, excluding: motoboot.img and recovery.img - you could then wipe and flash CM12 if all was working.
Click to expand...
Click to collapse
Okay, i will try to flash the 4.4.4 image i have, but i have never updated bootloader. Should i still avoid motoboot and recovery?
gearguy365 said:
Okay, i will try to flash the 4.4.4 image i have, but i have never updated bootloader. Should i still avoid motoboot and recovery?
Click to expand...
Click to collapse
It's dangerous to repeatedly flash the Bootloader (motoboot.img) - even if it is the KitKat one. And skipping recovery will mean you remain with current custom recovery.
lost101 said:
It's dangerous to repeatedly flash the Bootloader (motoboot.img) - even if it is the KitKat one. And skipping recovery will mean you remain with current custom recovery.
Click to expand...
Click to collapse
makes sense! i will try to revert back to 4.4.4 and keep things posted...
Flashing stock 4.4.4 brought back the network!
but when i was flashing the stock firmware, first i avoided flashing motoboot.img. That resulted in failing to erase userdata later on and ultimately resulting in "utag flash fail" and stuck in bootloader. Eventually flashing everything resulted in restoring stock firmware and now i have network again!
gearguy365 said:
Flashing stock 4.4.4 brought back the network!
but when i was flashing the stock firmware, first i avoided flashing motoboot.img. That resulted in failing to erase userdata later on and ultimately resulting in "utag flash fail" and stuck in bootloader. Eventually flashing everything resulted in restoring stock firmware and now i have network again!
Click to expand...
Click to collapse
I should have stated to do the commands manually, one at a time - rather than using the included script.
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Download XT1032 Retail US 5.0.2 Lollipop Firmware image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Use only the following fastboot commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
Report back how it goes.
Click to expand...
Click to collapse
Just saved my a**! Had a dead baseband. I somehow wrecked my modem on my XT1039. I downloaded a stock rom and used your commands and it worked like a charm! THANK YOU VERY MUCH!
Hello. I have the same issue... No sim/ network. I used mfastboot commands and fully restored to an unrooted stock XT1032 lollipop ROM. The confusing thing is that I still have no network. Does anyone have any suggestions?
Edit:
I used the downgrade to 4.4 thread... Ran the bat file and I'm back in business. The quick YouTube video walks you through the steps.
http://forum.xda-developers.com/showthread.php?t=2969729
Sent from my iPad using Tapatalk
Device: XT1031 converted to XT1028 for use on Page Plus. Bootloader unlocked. Rooted with SuperSU 2.46 Running Stock Verizon 5.1 ROM 221.26.7.falcon_cdma.Verizon.en.US
Recovery: TWRP 2.8.7.0
I accepted the new security update - http://forum.xda-developers.com/moto-g/general/moto-g-1st-gen-actually-security-update-t3362323
and when it tried to install the update, the phone just rebooted into TWRP Recovery.
So I flashed stock recovery from the Verizon 5.1 ROM and then tried the update again. This time it completed the update and rebooted but is now stuck at the Motorola bootlogo.
I'm able to reboot into fastboot.
I tried flashing system.img_sparsechunk.0, .1, .2, and .3, and rebooted but there is no change.
What can I try to get past this?
Before starting this I made a backup using TWRP Recovery, can I reinstall TWRP and restore that backup?
it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If the TWRP backup is still on phone, it might be worth transferring it to a PC / external OTG usb drive, as using the following fastboot command will erase it, along with everything else on internal storage:
fastboot command erase userdata
lost101 said:
it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If the TWRP backup is still on phone, it might be worth transferring it to a PC / external OTG usb drive, as using the following fastboot command will erase it, along with everything else on internal storage:
fastboot command erase userdata
Click to expand...
Click to collapse
The TWRP backup was saved to an external OTG USB drive, so that's safe.
I was originally going to do the same as I did for the last update - http://forum.xda-developers.com/showpost.php?p=63976723&postcount=109 but tried it first and when it went straight to recovery, I figured I needed to flash stock recovery. I also figured I needed to flash system also, but it through me off when the sparsechunks were numbered 0 - 3 instead of 1 - 4.
I didn't see any errors when I did the flashes.
Right now my battery is drained all the way to 0%. Hopefully it charges back up.
I appreciate the response. Thanks.
Do all fastboot commands including erase userdata. Change sparsechunk names to match the files in the firmware folder you have downloaded. Phone should charge on fastboot screen, but probably not if at a very low percentage.
lost101 said:
Do all fastboot commands including erase userdata. Change sparsechunk names to match the files in the firmware folder you have downloaded. Phone should charge on fastboot screen, but probably not if at a very low percentage.
Click to expand...
Click to collapse
I'm using this stock ROM: XT1028_FALCON_VERIZON_5.1_LPB23.13-33.7_cid2_CFC.xml.zip
The sparsechunk files in that zip are named:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
and I need to rename them:
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
system.img_sparsechunk4
Correct?
Then I would run the following commands one at a time and checking for an OK on each, correct?
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_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
After that I can check that I can boot into the OS and then I can flash TWRP and restore my saved backup.
Does that sound right?
Thanks.
Don't rename the sparsechunk files. I said change the name when doing the fastboot commands.
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
Edit: Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
Don't rename the sparsechunk files. I said change the name when doing the fastboot commands.
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
Edit: Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
OK, I got an error on the first one I tried:
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>mfastboot devices
TA965000I5 fastboot
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.318s
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>
And on the Moto G's screen:
cmd: getvar:max-sparse-size
cmd: download:00008000
cmd: flashartition
version downgraded for primary_gpt
Is that a problem?
Try flashing the latest available XT1028 Verizon 5.1 Factory Firmware Image:
XT1028_FALCON_VERIZON_5.1_LPBS23.13-33.7-2_cid2
lost101 said:
Try flashing the latest available XT1028 Verizon 5.1 Factory Firmware Image:
XT1028_FALCON_VERIZON_5.1_LPBS23.13-33.7-2_cid2
Click to expand...
Click to collapse
OK, that worked. I was able to flash back to the stock ROM.
I'm wondering if there would be any issue if I were to flash TWRP recovery and restore my saved backup?
Thanks for your help.
bw 1 said:
I'm wondering if there would be any issue if I were to flash TWRP recovery and restore my saved backup?
Click to expand...
Click to collapse
I don't personally restore TWRP backups because of bad experiences, but as long as you are using the latest available TWRP you should be okay.
lost101 said:
I don't personally restore TWRP backups because of bad experiences, but as long as you are using the latest available TWRP you should be okay.
Click to expand...
Click to collapse
I decided to start over and not try to recover from the saved file. I don't think there was anything on there that I really needed anyway. All my pictures and stuff was synced to Google.
I'm guessing that I ran into a problem by not flashing the 4 system sparsechunks from the stock ROM to remove root and I wasn't able to flash the same 5.1 that I had on there since it was updated. Flashing the latest newer build Verizon ROM worked because it was the same as what was contained in the update.
I didn't receive another OTA update and system update shows my phone as up to date with:
Android version: 5.1
Android security patch level: 2016-03-01
System version: 221.201.2.falcon_cdma.Verizon.en.US
Build number: LPBS23.13-33.7-2
I'm back to having a working phone. Thanks for your help. Hopefully this will help others too.