Yesterday afternoon my phone decided to throw a fit. I was listening to a podcast via AUX, and all of the sudden my phone reboots. No big deal. However, the phone never booted. So I enter TWRP to restore a backup. Restoration completes fine, however my backup bootloops (uh oh).
LONGG story short, my phone will not boot. Fastboot tells me "Baseband: Not Available" which is...unpleasant. I have tried manually flashing firmware, no dice, bootloops. I finally decided to try RSD Lite, but when it gets to the modem (NON-HLOS.bin) the flash fails. For the record, I'm using the full firmware from the May Security Update, XT1575.
Im starting to become worried this is a real issue. Any help or experience with this type of issue is greatly appreciated!
Are you wiping data?
lafester said:
Are you wiping data?
Click to expand...
Click to collapse
After originally bootlooping, i tried restoring a good nandroid. When that also bootlooped, i reentered TWRP and tried a fresh install of an CM nightly. That install began, but wouldn't progress nor fail. I eventually encountered an error regarding the data partition, so i rebooted TWRP again and formatted data, and again tried installing CM.
When that also failed, I began attempting to flash stock firmware via fastboot.
Sent from my m8wl using Tapatalk
Can you manually push the firmware via fastboot?
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Some people have noted doing the erase command before the flash commands helps, or make 2-3 attempts at flashing the NON-HLOS.bin file are required to get an OK.
Otherwise try flashing the full factory firmware, but expect gpt.bin to fail, that is normal, when you get to NON-HLOS.bin flash execute the command up to 3 times to try to get it to go.
If you continue to get failures, it is possible that your emmc chip is corrupt or defective. :/
acejavelin said:
Can you manually push the firmware via fastboot?
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Some people have noted doing the erase command before the flash commands helps, or make 2-3 attempts at flashing the NON-HLOS.bin file are required to get an OK.
Otherwise try flashing the full factory firmware, but expect gpt.bin to fail, that is normal, when you get to NON-HLOS.bin flash execute the command up to 3 times to try to get it to go.
If you continue to get failures, it is possible that your emmc chip is corrupt or defective. :/
Click to expand...
Click to collapse
Yes, multiple times. The modem would always flash on second attempt. Still wouldn't ever boot.
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
Yes, multiple times. The modem would always flash on second attempt. Still wouldn't ever boot.
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
Dumb question... is it looping, or just sitting at the boot logo after the initial boot animation appears? First boot can take what seems like a really long time, over 20 minutes sometimes.
acejavelin said:
Dumb question... is it looping, or just sitting at the boot logo? First boot can take what seems like a really long time, over 20 minutes sometimes.
Click to expand...
Click to collapse
I was getting bootloops originally, since flashing firmware each time I try to boot it sits at the unlocked bootloader screen for a couple seconds, then the blue M for a couple seconds, then the screen turns off and immediately returns to the unlocked bootloader message.
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
I was getting bootloops originally, since flashing firmware each time I try to boot it sits at the unlocked bootloader screen for a couple seconds, then the blue M for a couple seconds, then the screen turns off and immediately returns to the unlocked bootloader message.
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
So it is truly bootlooping... And you tried the full factory images?
acejavelin said:
So it is truly bootlooping... And you tried the full factory images?
Click to expand...
Click to collapse
I believe so! I'm using the following:
XT1575_CLARK_RETUS_6.0_MPHS24.49-18-4_cid9_subsidy-DEFAULT_CFC.xml.zip
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
I believe so! I'm using the following:
XT1575_CLARK_RETUS_6.0_MPHS24.49-18-4_cid9_subsidy-DEFAULT_CFC.xml.zip
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
Did you manually flash all 8 sparsechunks? According to the file contents and service.xml file, the appropriate way to flash this image is:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- May fail, if fails twice, just continue
fastboot flash bootloader bootloader.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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
EDIT: Also note that after flashing the factory images it is known to fail to boot if you do not do a factory reset with the stock recovery prior to flashing the images... fastboot flash the recovery image, do a factory default, then go through the full list above, step by step, and verify you get an OK after every step, if you don't repeat the step before continuing. I would suggest using the above method manually.
acejavelin said:
Did you manually flash all 8 sparsechunks? According to the file contents and service.xml file, the appropriate way to flash this image is:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- May fail, if fails twice, just continue
fastboot flash bootloader bootloader.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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
EDIT: Also note that after flashing the factory images it is known to fail to boot if you do not do a factory reset with the stock recovery prior to flashing the images... fastboot flash the recovery image, do a factory default, then go through the full list above, step by step, and verify you get an OK after every step, if you don't repeat the step before continuing. I would suggest using the above method manually.
Click to expand...
Click to collapse
Those were the instructions i was following, but i did not know about this stock recovery issue.
You're saying flash stock recovery, enter recovery and perform a factory reset, and then fastboot flash the firmware package as instructed?
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
Those were the instructions i was following, but i did not know about this stock recovery issue.
You're saying flash stock recovery, enter recovery and perform a factory reset, and then fastboot flash the firmware package as instructed?
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
Yes... Failure to do so has caused bootloop on the Moto G 2015, another 3rd gen Moto device
Sent from my XT1575 using Tapatalk
acejavelin said:
Yes... Failure to do so has caused bootloop on the Moto G 2015, another 3rd gen Moto device
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Got it, thank you, I'll try this as soon as i get home
Sent from my m8wl using Tapatalk
acejavelin said:
Yes... Failure to do so has caused bootloop on the Moto G 2015, another 3rd gen Moto device
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Just followed this step by step, the only thing that failed on first try was the modem, second attempt flashed okay. After sending the "fastboot reboot" command, I get the unlocked bootloader message for a few seconds, the stock blue Moto M for about 10 seconds, and then the screen remains on but blank (black). Its been sitting there for a few minutes and nothing is happening..
Edit: Fastboot is now showing "Not found" under baseband instead of "Not available", as it had been previously.
DonKilluminati23 said:
Just followed this step by step, the only thing that failed on first try was the modem, second attempt flashed okay. After sending the "fastboot reboot" command, I get the unlocked bootloader message for a few seconds, the stock blue Moto M for about 10 seconds, and then the screen remains on but blank (black). Its been sitting there for a few minutes and nothing is happening..
Click to expand...
Click to collapse
Give it at least 20-25 minutes without touching it... too early to make a call yet.
acejavelin said:
Give it at least 20-25 minutes without touching it... too early to make a call yet.
Click to expand...
Click to collapse
After a few more minutes it returned to the unlocked bootloader message and is now back to cycling back and forth between that screen and the blue M..
DonKilluminati23 said:
After a few more minutes it returned to the unlocked bootloader message and is now back to cycling back and forth between that screen and the blue M..
Click to expand...
Click to collapse
Hmm... I am at a loss for what to do then. Sorry.
Sent from my XT1575 using Tapatalk
acejavelin said:
Hmm... I am at a loss for what to do then. Sorry.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
So I decided to try again from scratch, this time its actually staying on the boot screen (the blue M) and has been sitting just like that for almost 30 minutes? WTF. All I can think to do at this point (after letting it set there for another 30 minutes) is letting the phone charge for a few hours to guarantee low battery isnt an issue.
Regardless, I really appreciate your help!! At this point Im hoping I can send it to Motorola to see if they can successfully flash factory software.
DonKilluminati23 said:
So I decided to try again from scratch, this time its actually staying on the boot screen (the blue M) and has been sitting just like that for almost 30 minutes? WTF. All I can think to do at this point (after letting it set there for another 30 minutes) is letting the phone charge for a few hours to guarantee low battery isnt an issue.
Regardless, I really appreciate your help!! At this point Im hoping I can send it to Motorola to see if they can successfully flash factory software.
Click to expand...
Click to collapse
i have the same problem like you
my base band in fastboot says NOT FOUND
even after flashing stock and cutom rom my phone con not recognize simcard signal.
did you solve your problem?
if yes, how?
ehsan_991 said:
i have the same problem like you
my base band in fastboot says NOT FOUND
even after flashing stock and cutom rom my phone con not recognize simcard signal.
did you solve your problem?
if yes, how?
Click to expand...
Click to collapse
I sent it to Motorola to have it "repaired". Basically they just reflashed stock software. I was not under warranty, but they fixed it for free so i didn't bother trying to fix it over and over.
Sent from my XT1575 using Tapatalk
Related
I need to relock my bootloader and it won't do so. I have tried Fastboot oem lock and it says it finishes it but changes nothing on the device. I need to return, PLEASE HELP!
jdellingson7 said:
I need to relock my bootloader and it won't do so. I have tried Fastboot oem lock and it says it finishes it but changes nothing on the device. I need to return, PLEASE HELP!
Click to expand...
Click to collapse
Why do you need to return?
I bought the 16gb because I couldn't not find a 32gb anywhere. Amazon had the 32 available yesterday so I bought one
You can lock it back up. However it will still give you the unlocked bootloader screen, and it will show status 2 in the bootloader menu.
There is no way to reset it without leaving flags that it was unlocked
Sent from my Nexus 6 using Tapatalk
I wouldn't worry about it, if I were you. Flash the stock logo.bin, relock it, and don't worry about what it says in the recovery menu. I'm not making any promises, but that's the way I would play it.
jaben2 said:
You can lock it back up. However it will still give you the unlocked bootloader screen, and it will show status 2 in the bootloader menu.
There is no way to reset it without leaving flags that it was unlocked
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Is there a physical fuse that pops a la modern Samsung phones? Or are we still waiting for developers to figure out how to reset the flags on this particular model? I know that I've seen threads for other devices that walk you through resetting flags, so if it is only done with software on this device, we should be able to restore to 100% stock soon enough.
Here is Motorola's page on re-locking:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Unfortunately they don't have the stock image available yet for the Moto X 2015 (scroll down).
I'm returning mine due to a damage claim and wanted to re-lock but we can't yet, at least officially. Moto still records when you unlocked, now listed under 'My Support History' in my Profile, so there's no way to hide that you unlocked if you did it through their site. The good news is it didn't affect my warranty claim in talking to a few support staff, and of course made sure not mention it myself but nobody there brought it up, so I tend to doubt it will affect your return. I did use the Restore to Stock tool (worked great!) and then removed the Unlocked warning, so it's just as if it had a factory reset.
I just relocked mine, no white screen on boot.
but it says
Device is LOCKED. Status Code: 2
Software status: Modified
Here's how I did it.
download this
open cmd, navigate to the folder extracted from the zip in the link above, this will erase your entire phone, reset to stock firmware and relock the bootloader
boot into bootloader pwr+vol down
run these commands
Code:
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Now If I can figure out how to remove the status code and make the software status official.
It's probably impossible, for now at least.
Thanks this worked but it didn't remove the bootloader unlock warning. So I just flashed the boot logo and it's good to go. I'm pretty sure Best Buy is no educated on these things.
tylerwatt12 said:
I just relocked mine, no white screen on boot.
but it says
Device is LOCKED. Status Code: 2
Software status: Modified
Here's how I did it.
download this
open cmd, navigate to the folder extracted from the zip in the link above, this will erase your entire phone, reset to stock firmware and relock the bootloader
boot into bootloader pwr+vol down
run these commands
Code:
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Now If I can figure out how to remove the status code and make the software status official.
It's probably impossible, for now at least.
Click to expand...
Click to collapse
jdellingson7 said:
Thanks this worked but it didn't remove the bootloader unlock warning. So I just flashed the boot logo and it's good to go. I'm pretty sure Best Buy is no educated on these things.
Click to expand...
Click to collapse
Lol I'll be very surprised if someone knows lol. Most of them probably use iPhone anyway. It feels good being a geek ?
if they can change the software status on an M9 i see no reason why they couldn't on the MXP
jdellingson7 said:
Thanks this worked but it didn't remove the bootloader unlock warning. So I just flashed the boot logo and it's good to go. I'm pretty sure Best Buy is no educated on these things.
Click to expand...
Click to collapse
I tried flashing the logo.bin, but that didn't replace the bootloader unlock warning. Where did you get the boot logo to replace the warning and to what partition did you flash it?
http://forum.xda-developers.com/mot...o-remove-unlocked-bootloader-warning-t3201141
Tanker Bob said:
I tried flashing the logo.bin, but that didn't replace the bootloader unlock warning. Where did you get the boot logo to replace the warning and to what partition did you flash it?
Click to expand...
Click to collapse
jdellingson7 said:
http://forum.xda-developers.com/mot...o-remove-unlocked-bootloader-warning-t3201141
Click to expand...
Click to collapse
Thank you! That worked perfectly.
Good deal, sending mine back this week this will come in handy
Just to let you know, I returned mine unlocked. Unlocked has more to do with warranty claims, it doesn't void returns. That's a mandated law. Moto will just relock it and restore it to stock.
Sent from my Nexus 7 (2013) using XDA Free mobile app
sent mine back, wasn't completely locked, still had the flag set. I got my money back, just wanted to let everyone know.
Will this restore the stock bootloader as well? In rooting mine it called for installing twrp...so wondering if this is a method back to complete stock?
Also, anyone know if rooted twrp will get ota's?
mcdonsco said:
Will this restore the stock bootloader as well? In rooting mine it called for installing twrp...so wondering if this is a method back to complete stock?
Also, anyone know if rooted twrp will get ota's?
Click to expand...
Click to collapse
The email you get with the unlocked bootloader contract says no OTA's
tylerwatt12 said:
sent mine back, wasn't completely locked, still had the flag set. I got my money back, just wanted to let everyone know.
Click to expand...
Click to collapse
nikeman513 said:
Just to let you know, I returned mine unlocked. Unlocked has more to do with warranty claims, it doesn't void returns. That's a mandated law. Moto will just relock it and restore it to stock.
Sent from my Nexus 7 (2013) using XDA Free mobile app
Click to expand...
Click to collapse
I'm returning mine as well and was stressing over this my bootloader being unlocked. Thank you both for your feedback on what happened after you returned it. People tend to forget to give details about the outcome on threads like this. So I give :good::good: to you guys
Don't worry too much about the unlocked bootloader status messages, especially if you flash the logo.bin to remove the giant notice on bootup.
When you return a phone, the RMA department is interested in just processing the return as fast as possible, and moving on to the next return. They are not in the business of checking every single individual device for voided warranties, for purposes of playing "gotcha" to find reasons to reject a return.
The fact of the matter is that it is a very small minority of people that will unlock / root a phone, and return it. And an even smaller portion of that minority that cause warranty-vouding damage as a result of those software-related changes.
Will there be people that abuse this return policy, and process illegitimate returns? Yes, of course. But it will cost Motorola (or Amazon) more time/money to individually check each return for voided warranties, than it would to just process the RMA as fast as possible and move on.
Sometimes, even if you KNOW people are stealing from you, it's still cheaper to just let then steal, than to take the time to try and stop that theft.
Sent from my XT1575 using Tapatalk
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
try http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
then flash android 6.0 maybe trupure 2.9 and then get the modem from trupure and flash it
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
---------- Post added at 04:06 PM ---------- Previous post was at 04:00 PM ----------
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
Check all the files that u have flashed
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Find 18-4 firmware, it's newer anyway... the sparse chunk size error is the problem, the system.img file in that firmware file is too large for the phone to flash via fastboot (thus, it probably isn't an official image, or it's an image for the engineering flash tool, not fastboot). The proper image file with have 6-11 sparce chunks you need to flash individually.
acejavelin said:
Find 18-4 firmware, it's newer anyway... the sparse chunk size error is the problem, the system.img file in that firmware file is too large for the phone to flash via fastboot (thus, it probably isn't an official image, or it's an image for the engineering flash tool, not fastboot). The proper image file with have 6-11 sparce chunks you need to flash individually.
Click to expand...
Click to collapse
I think i made it worse lol... Because I was getting many errors (random reboots), I decided to do a full wipe to install a ROM fresh. When wiping in TWRP, I accidentally wiped "internal" too. I'm guessing that I need to do something to correct this before I can flash 18-4 firmware. Please let me know if you know what I need to do. Thank you.
goldentequila said:
I think i made it worse lol... Because I was getting many errors (random reboots), I decided to do a full wipe to install a ROM fresh. When wiping in TWRP, I accidentally wiped "internal" too. I'm guessing that I need to do something to correct this before I can flash 18-4 firmware. Please let me know if you know what I need to do. Thank you.
Click to expand...
Click to collapse
TWRP shouldn't be a part of this, nor should it matter whats on your internal storage, this is all done with fastboot.
Factory reset in stock recovery, reboot to bootloader, then flash the complete image with fastboot.
Sagar_1401 said:
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
---------- Post added at 04:06 PM ---------- Previous post was at 04:00 PM ----------
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
Check all the files that u have flashed
Click to expand...
Click to collapse
The instruction in that post said to not worry about the sparse error message, so I went with it. This is what the post said.
"You may notice a "sparse header error" when flashing at the beginning. Don't worry about it, all is well. The current AutoFlashFirmware.bat file doesn't work with this Firmware file. Flash the files manually!"
Also, i posted above too, but I just accidentally wiped internal via TWRP too. Do you know what I need to do now in order to get my phone back? I've found solutions for other phones regarding this situation, but I haven't come across one for Moto X Pure. This is what happens when you work on your phone all day long and some more into late night lol...
acejavelin said:
TWRP shouldn't be a part of this, nor should it matter whats on your internal storage, this is all done with fastboot.
Factory reset in stock recovery, reboot to bootloader, then flash the complete image with fastboot.
Click to expand...
Click to collapse
Thank you for your ongoing support. I just want to make sure I'm doing this right. I found this firmware: http://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Could you please tell me if you think that's what I should flash?
Also, if you don't mind, will you please share exact fastboot commands/process? I just don't want to make any more mistakes and make things worse. I apologize for being needy.
goldentequila said:
Thank you for your ongoing support. I just want to make sure I'm doing this right. I found this firmware: http://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Could you please tell me if you think that's what I should flash?
Also, if you don't mind, will you please share exact fastboot commands/process? I just don't want to make any more mistakes and make things worse. I apologize for being needy.
Click to expand...
Click to collapse
Yes, look in my signature and use the non-relock option: http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
acejavelin said:
Yes, look in my signature and use the non-relock option: http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thank you very much for that. You mentioned that I would need to factory reset in stock recovery first. Do I just fastboot flash a stock recovery from the firmware zip file from 18-4, boot into its recovery, reset, and then follow the instruction above?
goldentequila said:
Thank you very much for that. You mentioned that I would need to factory reset in stock recovery first. Do I just fastboot flash a stock recovery from the firmware zip file from 18-4, boot into its recovery, reset, and then follow the instruction above?
Click to expand...
Click to collapse
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
acejavelin said:
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
Click to expand...
Click to collapse
Oh ok. Thanks again. I'll report back if I succeed (or not) later today. I appreciate your help.
acejavelin said:
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
Click to expand...
Click to collapse
Thank you so much for your help. It worked perfectly. Now I have my phone back :victory:
goldentequila said:
Thank you so much for your help. It worked perfectly. Now I have my phone back :victory:
Click to expand...
Click to collapse
Glad I could help. You're welcome.
Lol it was sparsechunk i just got confused with it and said spunk??
I have a second Moto G4 and I was curious if anyone got a fix for these issues? it happened a while back when I was trying to go back to factory image. there was a lot of errors. I cant seem ti find the screenshots of the errors that I got at the time. This was around January or so.There is no Mac Address in settings and theres no ip no way to turn data on and when I try wifi. it automatically shuts off. Doesn't detect my Sim Card or Service. says Emergency calls only
I have the same problem, I have got the sim working but no wifi or bluetooth yet.
When I load adb shell and grep the wireless module it says "WCNSS DRIVER NOT FOUND" even though it is there.
I found fix. Delete the old os completely and have the right stock os ready to adb flash. Id say google ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml .. then put it in your minimal adb and fastboot file. go to bootloader and then back to computer to do the shift right click in the file on pc and get terminal up and copy and paste this
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Fastboot flash logo logo.bin
The fastboot restart the device and you should be back with the wifi and data. I bought a new phone in feb or march because of this issue and couldn't find a fix till I googled constantly.
I had to delete the os completely and then flash the factory boot image with
AArnold2 said:
I have the same problem, I have got the sim working but no wifi or bluetooth yet.
When I load adb shell and grep the wireless module it says "WCNSS DRIVER NOT FOUND" even though it is there.
Click to expand...
Click to collapse
NeroCZA said:
I found fix. Delete the old os completely and have the right stock os ready to adb flash. Id say google ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml .. then put it in your minimal adb and fastboot file. go to bootloader and then back to computer to do the shift right click in the file on pc and get terminal up and copy and paste this
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Fastboot flash logo logo.bin
The fastboot restart the device and you should be back with the wifi and data. I bought a new phone in feb or march because of this issue and couldn't find a fix till I googled constantly.
I had to delete the os completely and then flash the factory boot image with
Click to expand...
Click to collapse
What are the proper steps to completely remove your entire OS safely? Do you mean to just overwrite the current one?
This procedure overwrites your current or completely. You will lose the contents of the internal SD card
Sent from my LG-LS980 using Tapatalk
dayne.rhoades said:
What are the proper steps to completely remove your entire OS safely? Do you mean to just overwrite the current one?
Click to expand...
Click to collapse
Save what you want and it should be safe to just completely wipe your phone cache and all no overwrite.. Then have the stock ready to flash in the file on computer and do the the above steps. Ive done it on both my moto g4's because on my main one which I'm sending off to Motorola for screen repairs, I wiped my phone without thinking about the stock os. panicked but remembered the back to stock steps and attempted them. Ive always gotten errors or wifi and data wipe from over writing with the codes. So I just flashed on the one I deleted OS off of and it worked.
tekweezle said:
This procedure overwrites your current or completely. You will lose the contents of the internal SD card
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Yeah sadly you will lose everything unless you have it all saved. I was mad about losing a lot of things but I was having screen issues and data wifi issues to try to fix. I do have data and wifi now. I just wish I saved what I could.
Would the android data recovery program recover anything? Ive been searching how to recover wiped data. Internet is full of info on how wiped data can be recovered. I just want the text messages and stuff. I had important things in some the text messages I lost
You should save to the external SD card.
Sent from my LG-LS980 using Tapatalk
Delete the old OS via twrp?
You should have made a backup with twrp. Then you could restore your os as it was.
Sent from my Moto G (4) using Tapatalk
Nope the firmware linked above caused the phone to go in to a boot loop.
AArnold2 said:
Delete the old OS via twrp?
Click to expand...
Click to collapse
Yeah that's what I did. Then I flashed the stock rom I googled. Ive been trying to update to nougat for past 2 days since I got back to proper stock rom.
you can;t flash any of the official firmwares via TWRP. You can flash a custom rom or restore a backup of your OS though.
to flash/reload an official firmware, you need ADB and fastboot running from a computer.
Exactly. Don't try with TWRP.
tekweezle said:
you can;t flash any of the official firmwares via TWRP. You can flash a custom rom or restore a backup of your OS though.
to flash/reload an official firmware, you need ADB and fastboot running from a computer.
Click to expand...
Click to collapse
TLR: Phone boots up and says. Launcher has stopped working, contacts has stopped working and etc.
Ok so i bought Moto G4 XT1625, yesterday. Was very happy with the device. It came with Android 6.0.1, i updated it to nougat 7.0.
But in android 6.0 and 7.0 both i noticed the phone giving random apps freezes and randomly even restarting on 7.0. The problem was minimal so i rebooted the phone 2,3 times and made it working. Then i received another update "NPJS25.93-14-4" on that update the phone got successful but bootlooped when booting for the first time on that update. I thoughts its ok so rebooted to bootloader and booted the phone from bootloader. the phone booted. after that another update came "NPJS25.93-14- (5 or 8) i dont remember properly" in this update the update failed during the installation. Keep in mind that i did not touch anything before this update. The phone was totally stock with stock recovery and everything. On this update the phone failed the update and i got constant bootloop no matter if i factory reset or erase cache it kept bootlooping, now i unlocked the bootloader and installed twrp and flashed a custom stock rom it crash on the boot. Again the random app has stopped working error came continously making the phone unusable. Then i flashed the stock rom correct firmware and everything it bootlooped again, then i rebooted numerous times the phone booted fine. Installed apps. This time did not get any app has stopped working error. Then rebooted the phone to install the sim card phone bootlooped again. Im 99% sure this is a hardware issue. Can somebody enlighten me? Whats going on in here? Thanks. I never faced this kind of problem ever in my life, i have bought more than 100 devices.
@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.
strongst said:
@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.
Click to expand...
Click to collapse
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!
whizinc said:
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!
Click to expand...
Click to collapse
Good luck:good:
UPDATE
It did not get past the "Checking Network" thing and after pressing the power button screen went black but i could see nav bar and status bar only. The phone has faulty hardware. Im now sure. Going to get it back tomorrow from where i bought it. Lets hope i get a refund or replacement. I bought it from a local mobile mall.
strongst said:
Good luck:good:
Click to expand...
Click to collapse
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working
whizinc said:
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working
Click to expand...
Click to collapse
Have you installed any third-party apps or restored them?
strongst said:
Have you installed any third-party apps or restored them?
Click to expand...
Click to collapse
nope, not a single app. Everything is clean and properly flashed.
whizinc said:
nope, not a single app. Everything is clean and properly flashed.
Click to expand...
Click to collapse
Snapchat is pre-installed?
strongst said:
Snapchat is pre-installed?
Click to expand...
Click to collapse
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.
whizinc said:
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.
Click to expand...
Click to collapse
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
posted in a new thread because the problem did not belong to the rom's thread, im sorry did i do something wrong? No. I did not flash the stock custom rom before all of this. I never wanted to flash a custom rom. The thing is the phone failed an OTA update which let me to come to this decision. The phone failed ".5" update and after that it bootlooped. So i thought flashing twrp and flash a custom rom with a clean install would fix it but even the custom rom the " xxx app stopped working error" came continously.
After that i followed echo92's guide and flashed the whole stock rom through fastboot. Still same issue. Random apps crashing.
I think this is hardware issue. Because every idea has been fail till now.
What do u say?
edit: note: when the phone failed ".npj25.93-14-5" update it was completely stock and i did not even touch anything, i dont know why it failed on the first place?
strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.
I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.
echo92 said:
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.
Click to expand...
Click to collapse
No no, You got the story wrong. Let me make it correct.
1: Bought the phone from a local mobile mall i have 3 days warranty left. (Phone was on Android 6.0 update)
2: Did not touch the phone. Just installed my daily apps. i.e: whatsapp,facebook and stuff.
3hone started doing odd things like auto touch while charging and apps saying "force stopped" error
4:Then i thought that this is Android 6.0 bug on Moto g4, so i should update it via OTA.
5: Updated to 7.0 same issues.
6:I saw another update did it as well 14-4 update. This update caused bootloop but i managed to make it through by booting from bootloader.
7: Then saw another update 14-5 and that update failed. (WHILE THE WHOLE PHONE WAS ON STOCK STATE) Why did the update fail? I didnt even touch the recovery or anything at that time.
8: Then i flashed the custom rom and the rest of the story goes on as u mentioned in the post.
And yes i cleaned flash the rom with the OEMlock.bat script that the guy above gave to me. It included all things such as boot,modem and all stuff. So it was def a clean install.
"fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot"
This was the script i used to flash the fastboot rom which is 14-4.
Then again got force stop errors and the 14-5 update failed causing bootloop again.
I just have 2 hours to check the devices further or else im gonna return it today. Thanks
MisterSteve said:
I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.
Click to expand...
Click to collapse
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.
whizinc said:
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.
Click to expand...
Click to collapse
Oh, you didn't mention that you have bought a used device! Bring it back to the shop and buy another/new one. Who knows what's wrong with that device or which history it has...
Apologies for getting the story mixed up, the information you provided in your corrected post and subsequently makes the situation worse though. Sounds like you bought a device exhibiting ghost touching or the beginnings of ghost touch and possibly was hard bricked/had the incorrect firmware flashed previously. As strongst mentioned, return that device. It sounds like it'll be more trouble than it's worth... especially for a used device.
UPDATE
I returned the handset to the shop guy, he was skeptical at first but then he gave it to another guy who said that the phone would go in used market claim and then after that he'll either return me the money or give me a new G4 device. I'll have to wait till monday. It sucks. Anyways Thanks alot guys for the help i appreciate it alot.
Feel free to lock the thread @ moderators.
Hii !! How long will it take for the fastboot rom to arrive for Moto g4 plus Indian retail xt1643 ... With 1st Feb 2018 security patch ???
Vs1607 said:
Hii !! How long will it take for the fastboot rom to arrive for Moto g4 plus Indian retail xt1643 ... With 1st Feb 2018 security patch ???
Click to expand...
Click to collapse
https://drive.google.com/file/d/1qR9MUUQCNUQ6sAivz2OTkc4TW88vmszv/edit
Already available since a month.
smog2699 said:
https://drive.google.com/file/d/1qR9MUUQCNUQ6sAivz2OTkc4TW88vmszv/edit
Already available since a month.
Click to expand...
Click to collapse
Where'd you find it ?? I mean I've been searching this whole time and couldn't find it ?
.
.
.
Just curious ! ?
Vs1607 said:
Where'd you find it ?? I mean I've been searching this whole time and couldn't find it Just curious ! ?
Click to expand...
Click to collapse
It was posted in the forum at least three times.
thorin0815 said:
It was posted in the forum at least three times.
Click to expand...
Click to collapse
Hi thorin0815, Vs1607,
Just a off thread question. If a flash this image it will wipe the data? My issue is described on below link. Please help me.
https://forum.xda-developers.com/moto-g4-plus/help/stock-moto-g4-plus-getting-rebooted-t3781480
hardythaker said:
Hi thorin0815, Vs1607,
Just a off thread question. If a flash this image it will wipe the data? My issue is described on below link. Please help me.
https://forum.xda-developers.com/moto-g4-plus/help/stock-moto-g4-plus-getting-rebooted-t3781480
Click to expand...
Click to collapse
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
echo92 said:
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
Click to expand...
Click to collapse
Okay thanks for your comments. I will give it a try. Just one question is that the latest firmware. Because I had recently updated the ROM.
hardythaker said:
Okay thanks for your comments. I will give it a try. Just one question is that the latest firmware. Because I had recently updated the ROM.
Click to expand...
Click to collapse
NPJS25.93-14-15 as of writing is the latest firmware, Feb 2018 security patch. What ROM did you update to?
echo92 said:
NPJS25.93-14-15 as of writing is the latest firmware, Feb 2018 security patch. What ROM did you update to?
Click to expand...
Click to collapse
April ota is the last , but no one have it
leap_ahead said:
April ota is the last , but no one have it
Click to expand...
Click to collapse
Yeah the update note appears to be up but as you mentioned it's not been released yet to any channel. So for now the latest firmware we have is the Feb 2018 build.
echo92 said:
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
Click to expand...
Click to collapse
Can i use this below commands. Also my bootloader is already locked, I have not unlocked the bootloader. Should I have to add any addtional command to above script like fastboot oem lock begin command.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
[STRIKE]fastboot erase userdata[/STRIKE]
fastboot erase customize
fastboot erase clogo
fastboot reboot
hardythaker said:
Can i use this below commands. Also my bootloader is already locked, I have not unlocked the bootloader. Should I have to add any addtional command to above script like fastboot oem lock begin command.
<Snip>
Click to expand...
Click to collapse
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
echo92 said:
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
Click to expand...
Click to collapse
Thanks mate. Am going to flash this tomorrow. Will surely let you know the outcome. Anyway if all this allow me to use my phone at least for an hour, I will take the backup of the necessary data and then will proceed with wipe data/factory reset.
echo92 said:
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
Click to expand...
Click to collapse
Okay so I have flash the phone using above commands, but no luck, exact same issue is persists and even nothing has been changed on the phone, not even lock screen wallpaper.
So now do you have any more suggestion please let me know if not will proceed with Data Wipe. Also Even if I wipe user data and after that can I recover files using some Andrioid File Recovery Tools out there.
Waiting for your reply and will proceed as you will suggest. Thanks.
hardythaker said:
Okay so I have flash the phone using above commands, but no luck, exact same issue is persists and even nothing has been changed on the phone, not even lock screen wallpaper.
So now do you have any more suggestion please let me know if not will proceed with Data Wipe. Also Even if I wipe user data and after that can I recover files using some Andrioid File Recovery Tools out there.
Waiting for your reply and will proceed as you will suggest. Thanks.
Click to expand...
Click to collapse
That's not good, if a flash doesn't fix things.
1)Try to wipe your data via a factory reset. I think you can try to keep your internal storage by selecting to only wipe userdata in the stock recovery (boot to recovery, hold the power key then press the volume up key to get past the 'No Command screen', then under wipe data/factory reset, there should be an option to wipe userdata only). Then wipe cache/Dalvik in that same menu, and see if your device boots. I do not know if file recovery tools will work on non-rooted devices (due to restrictions on reading the data partition).
2)If that doesn't work, your device may have a serious hardware fault that only a service centre can resolve.
echo92 said:
That's not good, if a flash doesn't fix things.
1)Try to wipe your data via a factory reset. I think you can try to keep your internal storage by selecting to only wipe userdata in the stock recovery (boot to recovery, hold the power key then press the volume up key to get past the 'No Command screen', then under wipe data/factory reset, there should be an option to wipe userdata only). Then wipe cache/Dalvik in that same menu, and see if your device boots. I do not know if file recovery tools will work on non-rooted devices (due to restrictions on reading the data partition).
2)If that doesn't work, your device may have a serious hardware fault that only a service centre can resolve.
Click to expand...
Click to collapse
Okay so seems like am in serious trouble.
1) Done wipe data (user data only) with no luck.
2) Done wipe data with userdata and personalized content, still...
3) Flash stock ROM along with "Fastboot Erase userdata", but no joy.
Should I unlock the bootloader now and try to install TWRP and from there if I can go some where
And now I have kept the phone on Welcome Screen, its not getting rebooted, Am able to go till Select WIFI, even am able to connect to WIFI. Then on next screen it is asking me to "Accept Moto T&C", after that it will show me Checking Connectivity > Checking For Update > Checking Info.......and this is the point where it get restarted. Can you guess what is the issue, seems like its some network or connectivity hardware issue.
hardythaker said:
Okay so seems like am in serious trouble.
1) Done wipe data (user data only) with no luck.
2) Done wipe data with userdata and personalized content, still...
3) Flash stock ROM along with "Fastboot Erase userdata", but no joy.
Should I unlock the bootloader now and try to install TWRP and from there if I can go some where
And now I have kept the phone on Welcome Screen, its not getting rebooted, Am able to go till Select WIFI, even am able to connect to WIFI. Then on next screen it is asking me to "Accept Moto T&C", after that it will show me Checking Connectivity > Checking For Update > Checking Info.......and this is the point where it get restarted. Can you guess what is the issue, seems like its some network or connectivity hardware issue.
Click to expand...
Click to collapse
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
echo92 said:
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
Click to expand...
Click to collapse
Tried with mobile data too, but still same issue. Anyway am in service center now let's see what they say.
echo92 said:
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
Click to expand...
Click to collapse
Okay so after one-month of stupidity from service center and some other guys finally I myself resolved the issue.
1) Service center tried to flash the rom but didn't resolved the issue.
2) They changed the battery, but still the same issue.
3) They said that this is motherboard issue and it will cost 5200 INR.
Then gave my phone on yaantra .com to repair it they kept the phone for 5 days and said the same thing that it is a motherboard issue as network circuit is not working properly.
( In between this I end up buying OnePlus 6 :victory: :victory: )
Then I bought one new damaged phone in which motherboard was working fine. I replaced that motherboard with mine and still the same issue. After this I started disconnecting parts one by one which are there on display pannel. After checking speaker, vibrator, flash, when I disconnected the fingerprint sensor and rebooted the phone it was totally fine and no more reboots.
I never thought that a corrupted/damaged fingerprint scanner can do this kind of wired issue to a phone. .Now this will be a spare phone without fingerprint scanner. Thanks for your help @echo92