Database Users

permanent CyanogenMod boot logo

Hi there,
sorry, if this was answered before, but I couldn't find the correct answer:
After trying to flash a custom ROM (CMOD) I'm stuck now at the Cyanogen Mod boot animation.
If pressing "Power" button for a while the phone reboots, but gives me again the same boot animation (after ZUK logo).
If pressing "Power" + "Volume +" + "Volume -" buttons for a while the phone reboots, but gives me again the same boot animation (after ZUK logo).
The phone is not recognized via USB on a computer.
Anybody has still an idea what I could do?
Many thanks in advance for hints
best regards
m

What are the steps you followed before you ended up in this situation? What rom were you previously on? Provide as much details as you can without being redundant.

KKaushal said:
What are the steps you followed before you ended up in this situation? What rom were you previously on? Provide as much details as you can without being redundant.
Click to expand...
Click to collapse
I was coming from latest stock. The attempt was to flash CM14.
1.) flash in the thread linked twrp
2.) flash CM14 and Nougat GAPPS micro
3.) reboot ok
4.) fingerprint didn't react, so went back to recovery and flashed both again, causing this loop
many thanks again for any help/hint
best regards
m

If the first time boot with the rom and gapps was okay, maybe you should try wiping /system, /data, /dalvik and /cache and reflash the rom again.. Since you were in stock cmos 12.1, I think it'll be better if you flash official cm13 first, and then jump to cm14 from there to minimize sensor issues such as with the fingerprint like you experienced.

meikelrix said:
any help/hint
Click to expand...
Click to collapse
Mate if you think you're done with everything and nothing seems to help, just search around here how to flash ZUI using QPST. That's the last resort which saves your device from the gravest issues.
However, let me know if you can or can't find that thread or anything else, I'll be happy to help. :good:

KKaushal said:
If the first time boot with the rom and gapps was okay, maybe you should try wiping /system, /data, /dalvik and /cache and reflash the rom again.. Since you were in stock cmos 12.1, I think it'll be better if you flash official cm13 first, and then jump to cm14 from there to minimize sensor issues such as with the fingerprint like you experienced.
Click to expand...
Click to collapse
thank you, but I did wiping and reflash => causing the loop
best regards
m

sahu.prashant said:
Mate if you think you're done with everything and nothing seems to help, just search around here how to flash ZUI using QPST. That's the last resort which saves your device from the gravest issues.
However, let me know if you can or can't find that thread or anything else, I'll be happy to help. :good:
Click to expand...
Click to collapse
many thanks for offering. Any chance to provide a link, in order to spare some time?
best regards
m

meikelrix said:
I did wiping and reflash => causing the loop
Click to expand...
Click to collapse
There are many reasons for a bootloop. Start from scratch once again. Flash stock cos12.1 (or restore if you have a backup), flash cm13 from there after you load twrp, go from cm13 to cm14. I think this should be the way to go to avoid sensor issues. Once in stock, you can go from there. Good luck.

http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
This is the thread link right here explaining all the steps (although it's a little tricky to follow )
That was the good part....
The worst part is that the download links are dead
I'll try snooping around more and see if I can find anything else and you should try too since the thread will give you an idea what to look for.
If the search comes up empty, I'll upload the files tomorrow by all means
Fortunately found a link....
http://forum.xda-developers.com/showpost.php?p=64202059&postcount=14

sahu.prashant said:
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
This is the thread link right here explaining all the steps (although it's a little tricky to follow )
That was the good part....
The worst part is that the download links are dead
I'll try snooping around more and see if I can find anything else and you should try too since the thread will give you an idea what to look for.
If the search comes up empty, I'll upload the files tomorrow by all means
Fortunately found a link....
https://www.androidfilehost.com/?w=files&flid=40618
Click to expand...
Click to collapse
Heya
many thanks again for your much appreciated help!
I'll try to figure and provide the outcome...
best regards
m

KKaushal said:
There are many reasons for a bootloop. Start from scratch once again. Flash stock cos12.1 (or restore if you have a backup), flash cm13 from there after you load twrp, go from cm13 to cm14. I think this should be the way to go to avoid sensor issues. Once in stock, you can go from there. Good luck.
Click to expand...
Click to collapse
thank you, but I can't start from scratch, since the loop won't let me in

Happy to help and hopefully, outcome will be desirable.

meikelrix said:
thank you, but I can't start from scratch, since the loop won't let me in
Click to expand...
Click to collapse
Power button + volume up gets you into recovery mode.
(I think) Power button + volume down gets you into fastboot mode. Not sure about this one, you can search around for the key combo to get into specific modes. From fastboot mode, you can flash the stock cos 12.1 provided from the official support page of cyanogen. Make sure you download the zip compatible with fastboot mode. When you finally get to cos 12.1, you can install Twrp recovery (also available among the forum threads or from the official twrp website), then flash cm13, reboot to check if everything works and then finally move to cm14.
You can post here in case of problems/confusions in any step.
Alternately, in place of cos12.1, you can flash zui as suggested. Search in the 'help, q/a' section of zuk z1 in this forum. You can find the tutorial there. Good luck.

KKaushal said:
Power button + volume up gets you into recovery mode.
(I think) Power button + volume down gets you into fastboot mode. Not sure about this one, you can search around for the key combo to get into specific modes. From fastboot mode, you can flash the stock cos 12.1 provided from the official support page of cyanogen. Make sure you download the zip compatible with fastboot mode. When you finally get to cos 12.1, you can install Twrp recovery (also available among the forum threads or from the official twrp website), then flash cm13, reboot to check if everything works and then finally move to cm14.
You can post here in case of problems/confusions in any step.
Alternately, in place of cos12.1, you can flash zui as suggested. Search in the 'help, q/a' section of zuk z1 in this forum. You can find the tutorial there. Good luck.
Click to expand...
Click to collapse
Hi,
after draining the battery (and loading up a bit) I could get access to fastboot. From there I flashed latest twrp (3.0.2) and booted into twrp.
From twrp I wiped and then flashed latest Nuclear ROM & Gapps. After rebooting I'm still ending up in twrp, again?
PS: flashing the cos 12.1 via fastboot mode didn't work, due to below:
"
fastboot -i 0x2b4c update cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
target reported max download size of 1610612736 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(14844,0xa3181000) malloc: *** mach_vm_map(size=1585467392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1583882000 bytes
error: update package missing system.img
"
many thanks again for any help/hints
best regards
m

meikelrix said:
Hi,
after draining the battery (and loading up a bit) I could get access to fastboot. From there I flashed latest twrp (3.0.2) and booted into twrp.
From twrp I wiped and then flashed latest Nuclear ROM & Gapps. After rebooting I'm still ending up in twrp, again?
PS: flashing the cos 12.1 via fastboot mode didn't work, due to below:
"
fastboot -i 0x2b4c update cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
target reported max download size of 1610612736 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(14844,0xa3181000) malloc: *** mach_vm_map(size=1585467392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1583882000 bytes
error: update package missing system.img
"
many thanks again for any help/hints
best regards
m
Click to expand...
Click to collapse
Extract cos zip files and flash separately
Enviado desde mi ZUK Z1 mediante Tapatalk

acuicultor said:
Extract cos zip files and flash separately
Enviado desde mi ZUK Z1 mediante Tapatalk
Click to expand...
Click to collapse
That was it. I did the following sequence:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
reboot device
fastboot -i 0x2b4c flash system system.img
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata.img
fastboot reboot
Then I was back to stock. After that I started from scratch to flash twrp, Nuclear and Gapps.
Many thanks to all that helped!
best regards
m

Kinda stuck on Sending system. Help?

Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056

moriyaprateek said:
Kinda stuck on Sending system. Help?
Click to expand...
Click to collapse
AFAIR, I followed https://stackoverflow.com/questions/34299245/fastboot-flash-system-img-error
=> "fastboot flash –S 256M system PATH_TO_SYSTEM.img" (the -S switch did the trick)

Even i am in the same situation how to fix it bro
meikelrix said:
Heya
many thanks again for your much appreciated help!
I'll try to figure and provide the outcome...
best regards
m
Click to expand...
Click to collapse
stuck with same situation plz need help

Can't get December 2016 security OTA.

Hey guys, a while ago I tried going back to stock with the official Motorola Factory image. I wasn't getting any security OTAs, so I tried again with this image: CLARK_RETUS_6.0_MPHS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip by Motorola-Firmware-Team It was an update behind despite being uploaded on 1/26/17. I totally reset my phone and now I'm getting the latest update notification, but it won't update because of this error: [IMG="Sorry for the BLUR (see what I did there?)"]
I get that this error happens a lot and yes, I know I went back to stock correctly and I'm pretty sure I flashed my modem correctly. Anyone know what I'm doing wrong?

pswiifanwmi said:
Hey guys, a while ago I tried going back to stock with the official Motorola Factory image. I wasn't getting any security OTAs, so I tried again with this image: CLARK_RETUS_6.0_MPHS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip by Motorola-Firmware-Team It was an update behind despite being uploaded on 1/26/17. I totally reset my phone and now I'm getting the latest update notification, but it won't update because of this error: [IMG="Sorry for the BLUR (see what I did there?)"]
I get that this error happens a lot and yes, I know I went back to stock correctly and I'm pretty sure I flashed my modem correctly. Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
We can't see your image of your error. Can you link a screen shot on imgur or something?

acejavelin said:
We can't see your image of your error. Can you link a screen shot on imgur or something?
Click to expand...
Click to collapse
Whoops! Sorry 'bout that! Okay, XDA won't let me post pictures since I haven't posted enough so let me try this. imgur . com / a / wYX1F
Does that work?

pswiifanwmi said:
Whoops! Sorry 'bout that! Okay, XDA won't let me post pictures since I haven't posted enough so let me try this. imgur . com / a / wYX1F
Does that work?
Click to expand...
Click to collapse
Yeah, I got it... You have a incomplete flash on 18-8 or you used a ROM not for your device. You need to reflash the modem stack from 18-8 image and try the update again.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY after each step, if you don't get one, do it again.
Then if it still fails to update, can you post output of `fastboot getvar all` and mask out your IMEI number?

acejavelin said:
Yeah, I got it... You have a incomplete flash on 18-8 or you used a ROM not for your device. You need to reflash the modem stack from 18-8 image and try the update again.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY after each step, if you don't get one, do it again.
Then if it still fails to update, can you post output of `fastboot getvar all` and mask out your IMEI number?
Click to expand...
Click to collapse
How did you know that would work?! The script I've been running had those steps in them and they said okay each time, so what made this attempt any different? Was it the cache clearing that happened right afterward that messed everything up or the lack of a reboot after flashing system, recovery, logo and boot?
I used the same files I'd been using, but I copied them again for good measure. Guess they got corrupted the first time huh?
Thanks so much for your help!

pswiifanwmi said:
How did you know that would work?! The script I've been running had those steps in them and they said okay each time, so what made this attempt any different? Was it the cache clearing that happened right afterward that messed everything up or the lack of a reboot after flashing system, recovery, logo and boot?
I used the same files I'd been using, but I copied them again for good measure. Guess they got corrupted the first time huh?
Thanks so much for your help!
Click to expand...
Click to collapse
Lucky guess, and I figured it was a radio issue from the error message. And I know the modem stack messes up a lot, especially when flashed too fast... There is a reason we recommend doing it manually and not with a script. ?

Complicated problem, never came across in the whole lifetime of my android usage.

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.

"No SIM Card" Error after installing LineageOS

I followed the guide here: https://forum.xda-developers.com/mo.../rom-lineageos-14-1-moto-e4-qualcomm-t3690156
But now the sim card reader is not working.
I then installed the stock ROM using this guide: http://techposts.org/unbrick-moto-g4-plus-flash-stock-romfirmware/
But it is still not working.
I really don't think it's a hardware issue because the contacts are all there and clean. The sim card works in other phones so it's not that either.
I'm actually not sure if it worked before this, but I'm pretty sure it did. Because I flashed the moment I got the phone.
Thanks for your help!

kidbao said:
I followed the guide here: https://forum.xda-developers.com/mo.../rom-lineageos-14-1-moto-e4-qualcomm-t3690156
But now the sim card reader is not working.
I then installed the stock ROM using this guide: http://techposts.org/unbrick-moto-g4-plus-flash-stock-romfirmware/
But it is still not working.
I really don't think it's a hardware issue because the contacts are all there and clean. The sim card works in other phones so it's not that either.
I'm actually not sure if it worked before this, but I'm pretty sure it did. Because I flashed the moment I got the phone.
Thanks for your help!
Click to expand...
Click to collapse
Do you have the plus model? This is for the regular e4. Probably should have activated it first too.
Which model do you have? Qualcomm? Mediatek? What carrier? You have to flash the proper firmware.

madbat99 said:
Do you have the plus model? This is for the regular e4. Probably should have activated it first too.
Which model do you have? Qualcomm? Mediatek? What carrier? You have to flash the proper firmware.
Click to expand...
Click to collapse
Hi thanks for responding! I have the E4 XT1765. It's Qualcomm. MetroPCS. I tried the PERRY_METROPCS_C and PERRY_METROPCS_C_7.1.1 from from here: firmware. center/firmware/Motorola/Moto%20E4/Stock/

Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.

Flash aokp latest build

beachfl said:
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Click to expand...
Click to collapse
Yeah same. I tried everything :\

nayan deka said:
Flash aokp latest build
Click to expand...
Click to collapse
aokp doesn't have a build for my device. The closest they have is the Moto E line, not E4

kidbao said:
aokp doesn't have a build for my device. The closest they have is the Moto E line, not E4
Click to expand...
Click to collapse
There's an unofficial one here in the forum
https://forum.xda-developers.com/mo...aokp-rom-oms-substratum-t3748033/post75529247

ok. Now I'm thinking why would aokp help me? I tried installing dotOS and resurrection. So I don't think another custom ROM will help.

kidbao said:
ok. Now I'm thinking why would aokp help me? I tried installing dotOS and resurrection. So I don't think another custom ROM will help.
Click to expand...
Click to collapse
I don't know. I was just pointing out that we had one, lol. Not sure it will help you.
I see you "solved" it, lol

Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.

kidbao said:
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.
Click to expand...
Click to collapse
Not for me. As we've said, re-installing stock ROM doesn't seem to solve the problem for some people, but it's cool it did for you. Other forums are peppered with people experiencing the same SIM issue, some even apparently happening at random.

beachfl said:
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Click to expand...
Click to collapse
By installing unofficial apps, what do you mean?
And what system apps, specifically, did you re-enable or disable?
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
kidbao said:
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.
Click to expand...
Click to collapse
But which one do we delete? sparsechunk.0 or sparsechunk.1? And beachfl says to leave out gpt.bin...

Scholeggo said:
By installing unofficial apps, what do you mean?
And what system apps, specifically, did you re-enable or disable?
Click to expand...
Click to collapse
Unofficial apps... I just mean any apps that I didn't get from the Google Play Store. Nothing too dodgy, but I just can never rule out that those might be a factor in issues.
Specifically, I played around with disabling/uninstalling the MetroPCS apps (MyMetro, NameID, MetroZone) and a few things that had "Moto" in the name, not sure which... that's all.
Scholeggo said:
But which one do we delete? sparsechunk.0 or sparsechunk.1? And beachfl says to leave out gpt.bin..
Click to expand...
Click to collapse
You delete both those lines and replace them. Unlike the system.img file, which you do have to flash in 'sparsechunks', the oem.img file in this phone's stock ROM isn't in chunks, so flashing it is as a whole, with only one line, as follows:
> fastboot flash oem oem.img
And yah, I don't understand why, but I found flashing the partition table (gpt.bin) made my phone bootloop. Omitting it worked.
HTH.

beachfl said:
Unofficial apps... I just mean any apps that I didn't get from the Google Play Store. Nothing too dodgy, but I just can never rule out that those might be a factor in issues.
Specifically, I played around with disabling/uninstalling the MetroPCS apps (MyMetro, NameID, MetroZone) and a few things that had "Moto" in the name, not sure which... that's all.
You delete both those lines and replace them. Unlike the system.img file, which you do have to flash in 'sparsechunks', the oem.img file in this phone's stock ROM isn't in chunks, so flashing it is as a whole, with only one line, as follows:
> fastboot flash oem oem.img
And yah, I don't understand why, but I found flashing the partition table (gpt.bin) made my phone bootloop. Omitting it worked.
HTH.
Click to expand...
Click to collapse
So, basically, to get back to original ROM, flash the following:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Compared to the original:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?

Scholeggo said:
So, basically, to get back to original ROM, flash the following:
Compared to the original:
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Click to expand...
Click to collapse
Yup, that list all looks exactly like what I did.
'sudo -s' .... no, you don't include that when running fastboot from Windows, it's a Linux thing. I'm not sure you have to, but I do always run adb/fastboot from a command prompt with admin priveleges when I'm using WIndows. which is kinda the same thing as 'sudo' on Linux.

Scholeggo said:
So, basically, to get back to original ROM, flash the following:
Compared to the original:
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Click to expand...
Click to collapse
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Go to Android programs and scroll down to rsdlite 6.2.4
Edit: link corrected

madbat99 said:
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Click to expand...
Click to collapse
Yep, similar experience. I hate doinking around in fastboot if another option exists. That said, one needs to be comfortable at the command line in case something goes amiss.

Davey126 said:
Yep, similar experience. I hate doinking around in fastboot if another option exists. That said, one needs to be comfortable at the command line in case something goes amiss.
Click to expand...
Click to collapse
For sure. Comfort in fastboot is a must

madbat99 said:
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Click to expand...
Click to collapse
Like some others, RSDLite couldn't see my E4 from Windows 10

F'd up hard, would need some assistancea restoring stock

Didn't want to post because I thought I would solve the issue with a simple MiFlash restore to stock, but oh well, here I go:
Due to my excitement about the Pie update (Beta), I got a fastboot flashable zip that was posted on a thread and attempted to flash it myself, manually.
Commands I executed (one by one, not through the bat script):
Code:
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot set_active a
I probably should never have flashed all this but I will explain what happened in case someone more savvy knows exactly what happened and lends a helping hand.
So all the commands passed fine, except for the fastboot flash system ones. I executed the first one and it flashed parts of 500mb or so on the partition, around 6 times. Same on the system_b.
I suppose that these flash onto the different slots (A/B), correct me if I'm wrong. Then rebooted and it would bootloop (don't blame anyone since I f'd up) and I was like "Okay then, guess I will restore with MiFlash.
Well I did. First weird thing to notice, it would only take around 213 seconds, while it would normally take around 300 seconds so I suspected I might have messed up. Note that I always restore to the April security patch to be able to enable Camera2API. Booted fine, then it was time for me to input my SIM's PIN. I do so, and a message shows up saying "SIM PIN operation failed" and after that it would close and re-open the PIN prompt, basically every time I tried to type the PIN. It basically wouldn't even let me input the PIN itself. Sometimes, if I'm fast enough I can successfully submit it but it's still messed up and doesn't work properly.
I know, I shouldn't have flashed the thing in the first place (since it's also supposed to be confidential), but I did and I regret doing so. For anyone interested, the bootloader is unlocked and I can enter fastboot mode normally. Didn't try flashing a different stock image since this is the one I always use and it works.
If anyone has got any idea about what happened here and if there's any solution, I would be really thankful.

Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.

michkost858 said:
Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.
Click to expand...
Click to collapse
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard

apexashwin said:
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard
Click to expand...
Click to collapse
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM

Why flash April update? You can enable camera2api on any ota update! :/

WhatzIt2Ya said:
Why flash April update? You can enable camera2api on any ota update! :/
Click to expand...
Click to collapse
I don't think it's what matters at the moment.

michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.

WhatzIt2Ya said:
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.
Click to expand...
Click to collapse
Just to be clear. I wasn't trying to flash any extra firmware after failing to install the Pie Beta flashable. I tried rolling back to stock.
Also, I was in the latest November update, before flashing the Pie beta flashable, so that's not what's wrong.
About the reason I flash the April update, it's just so I don't get wipes when I lock/unlock the bootloader on the process of enabling Camera2API.
Right now, I just want to get back to stock, didn't try flashing the Pie beta a second time after I failed and I won't.

Also my IMEIs are correct, if that matters in any way. I believe something got corrupted in the partitions (might be bsing) but yeah. Now whatever version I'm on (7.1,8.0,8.1) the issue still persists.
So I'd like to make a full restore, from the ground up, I suppose.

Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.

nitroax said:
Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.
Click to expand...
Click to collapse
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?

michkost858 said:
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?
Click to expand...
Click to collapse
I had a similar problem. Solved restoring persist and EfS backup.

sipollo said:
I had a similar problem. Solved restoring persist and EfS backup.
Click to expand...
Click to collapse
Hmm, I don't have such a backup. Is there a way to restore one?

michkost858 said:
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM
Click to expand...
Click to collapse
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
michkost858 said:
Hmm, I don't have such a backup. Is there a way to restore one?
Click to expand...
Click to collapse
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.

manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
Yes this is a known bug. This should fix pin issue

manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
.:Addicted:. said:
Yes this is a known bug. This should fix pin issue
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. Will be watching over the thread linked.