So the only rom I have on my boost mobile moto g is not working. I flash it and when it boots up i get the phone force closing non stop. Its crazy because i flashed this exact rom zip a few times before and it worked fine. For whatever reason though, it won't now and I'm not sure what to do. As stupid as it is, its the only rom zip i have on my phone....
So how would I go about restoring my moto g... Please help!
Ok....so I got that issue fixed...now the new issue is...whenever i install any rom, besides the stock boost one, i get constant android.process.phone and android.process.acore has stopped errors, non stop! I have tried many different roms, gapps, and both twrp and cwm recovery. roms were working just fine before...i am out of ideas!
itslels said:
So the only rom I have on my boost mobile moto g is not working. I flash it and when it boots up i get the phone force closing non stop. Its crazy because i flashed this exact rom zip a few times before and it worked fine. For whatever reason though, it won't now and I'm not sure what to do. As stupid as it is, its the only rom zip i have on my phone....
So how would I go about restoring my moto g... Please help!
Ok....so I got that issue fixed...now the new issue is...whenever i install any rom, besides the stock boost one, i get constant android.process.phone and android.process.acore has stopped errors, non stop! I have tried many different roms, gapps, and both twrp and cwm recovery. roms were working just fine before...i am out of ideas!
Click to expand...
Click to collapse
Just try a clean installation bro format data , cache, davic cache and under mount and storage delete system ,data, cache bro just try this once
And flash a correct gapps pack for the ROM sure it will work
moha07 said:
Just try a clean installation bro format data , cache, davic cache and under mount and storage delete system ,data, cache bro just try this once
And flash a correct gapps pack for the ROM sure it will work
Click to expand...
Click to collapse
I did that many times and flashed many different roms and gapps packages and kept having same issue. I finally fixed it though. I had to restore it back to stock by flashing the stock firmware with fastboot. Roms work now. :good:
Related
Just got my n5 and decided to unlock and root it, everything went well until I wanted to flash a rom, no matter what rom I flashed I got all kinds of issues from all apps force closing to bootloops, soft keys not working ect. I've tried flashing stock img, factory reseting ect, nothing seems to work. I'm not sure what's going on here, any help?
I am probably already asking you questions you have already done but... Have you reformated the system, data, and cache partitions prior to flashing? Also are you checking the MD5 of the ROMs you are trying?
Yeah tried all of that, md5's are correct, thanks though
what recovery and version are you on?
what wipes exactly are you performing?
you've checked the md5?
Ok. just trying to narrow things down. When you flash the stock image from https://developers.google.com/android/nexus/images#hammerheadkrt16m are you running the flash-all script? And after that before even adding any apps or changing anything does it give you issues?
@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why
Xolith said:
@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why
Click to expand...
Click to collapse
are you flashing a gapps add-on package with your custom roms? the right gapps?
Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?
simms22 said:
are you flashing a gapps add-on package with your custom roms? the right gapps?
Click to expand...
Click to collapse
Yeah, tried a few including banks, PA 0-day, psx gapps
neomorphix said:
Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?
Click to expand...
Click to collapse
They appear right after I flash the rom, tried with both the included and with a custom one
Tried a few days later and it worked, weird haha. Thanks though
so i had been running my nexus 5 with cataclysm ROM for a while.,today i decided to do a cm12 nightly flash ...i worked well it booted fine, everthing worked well ,flashed gapps ,tibu,restored my apps .now after a reboot i kept getting "system uid inconsistent " errors.I (like a idiot) tried "fix permissions "in TWRP which resulted in a boot loop.so i decided to flash cataclysm rom freshly again.It worked well but now sometimes i get force close errors like "android.process.acore" and sometime google playstore force closes.
i am scared i might have spoiled something,
also the cm12 nightly reflashed bootloader as it was 5.0.2 and also radio ,do these things cause something to break??
how do i return to normal??
I have updated my Radio while I am still using Cataclysm and I didn't face any of the problems you mentioned above. I have also switched from Cataclysm to other ROMs (including CM12) and back couple of times in between and never faced any problems.
I generally wipe everything except Internal Memory when switching ROMs. Did you do the same?
Yes,its a clean flash.
Just a question has this got something to do with the "fix permission" thing I did in TWRP?
Even though I wiped and flashed cataclysm later??
Also I googled around .does a corrupt data partition cause these kind of errors to pop up??
Currently the occurrence of these errors is rare but I've notice reccurent notifications from google playbooks even after I remove the notifications they reappear after some time .
I've decided to use my nexus 5 for a while and see if the problems are reproducible .
But I feel like the only wrong thing I did was "fix permission " in TWRP other than that its was just regular ROM flashing.
Yes... a corrupt data partition might cause this.
Generally I wipe the following when I am flashing a new ROM:
Dalvik Cache
System
Data
Cache
As you see I wipe data as well when I am moving to completely different ROM.
Does that mean my device is not fit for flashing new Roms anymore.?
How can I fix my data partition to be as good as new??
No... What I meant was to wipe the Data partition as well before flashing a new ROM. Wipe all the partitions except the Internal Storage partition. (Note: Data and Internal Storage are not the same)
If that still doesn't work, try flashing the factory image to rollback to stock. Then again flash the recovery and try flashing a custom ROM.
You might try just reflashing the CM12 nightly and see if that fixes it. Otherwise you'll have to flash from fresh. I wouldn't recommend doing a full backup restore if possible.
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
I_HAVE_NO_IDEA said:
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
Click to expand...
Click to collapse
Well if you can boot into the recovery and if its custom (TWRP) wipe all the data on your phone. Second I would try to flash a ROM onto your device such as Resurrection Remix and see if that works. Update on your progress.
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
I_HAVE_NO_IDEA said:
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
Click to expand...
Click to collapse
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
vtails said:
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
Click to expand...
Click to collapse
Thank you. But I can't flash a cm12.1 atm (see my post below). I can only flash through fastboot. I'm not sure I properly understood you, what do you call 4 22 ?
FYI I managed to boot again. Here's what I did:
Flash a 5.x ROM, try to boot to let the system make partitions and stuff (I think)
Boot in TWRP and saw that system and cache were not mountable, so I wiped them.
Flash a cm12.1 (+ Gapps) and here we go!
Thank you for your help!
I have a Moto G XT1540 US Retail 2GB running stock 5.1.1 System version 23.31.33.osprey_retus_2gb Build number LPI23.72-33. Data (LTE) working fine.
There is an update available to 23.46.4, but I have not bothered to update as I'd rather run CM12.1.
I've tried flashing 4 different CM12.1 roms
- cm-12.1-20150922-UNOFFICIAL-osprey.zip
- cm-12.1-20150925-NIGHTLY-osprey.zip
- cm-12.1-20150926-NIGHTLY-osprey.zip
- Random-Radium-1.4-OFFICIAL-osprey-20150917.zip
and data is not working in any of them - I can make/receive calls and send/receive texts, but data always shows !
The APN looks correct to me, and I've tried adding a new APN with the same info as stock and rebooting, but it still doesn't work.
I restored to a nandroid backup of stock and data (LTE) is working fine again.
Any ideas or suggestions for how to debug this?
Thanks.
Bob
The first time you flash a custom rom its recommended that you do a factory reset.
so there are no leftovers of the stock system.
just backup your data (and store that backup on a sd) and try a factory reset.
i hope this solves the problem
(sorry for bad english)
HelpMeruth said:
The first time you flash a custom rom its recommended that you do a factory reset.
so there are no leftovers of the stock system.
Click to expand...
Click to collapse
Yes, I did. I used TWRP to do a factory reset, flash ROM, flash Gapps, wipe Dalvik and cache, and reboot before each
of the above 4 ROMS.
Bob
Hmm thats werd, maybe try flashing a custom kernel. Otherwise i realy dont know how tot help you
HelpMeruth said:
Hmm thats werd, maybe try flashing a custom kernel. Otherwise i realy dont know how tot help you
Click to expand...
Click to collapse
cm-12.1-20150922-UNOFFICIAL-osprey.zip, which contains squid2 custom kernel, was one of the ones I tried where data was not working for me.
Can anyone verify that they have tried any of those same roms and had data work for them?
Bob
Have you enable data in setting and try in quick setting tiles pressing the mobile signal icon it should then turn on if not restore firmware then try installing custom rom again
Everytime I try and use Google Maps either flashed with gapps/bean or installed later from play store all reboot my phone. Stock does not have any issue.
Tried:
ASOP-CAF
ASOP-EX
MOTOPURE
Lineage
TESLA
I just wonder why if the stock maps app works on 6.0 why not on 7.0?? The only thing I can think of is the GPS.
Any tips or suggestions?
Thanks!
Tried nano, pico and full for ARM and Android 7
open_gapps-arm-7.1-full-20170523
open_gapps-arm-7.1-nano-20170511
open_gapps-arm-7.1-pico-20170513
also BeansGapps-Full-7.1.x-20170509 BeansGapps-Mini-7.1.x-20170509
Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.
grantdb said:
Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.
Click to expand...
Click to collapse
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...
acejavelin said:
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...
Click to expand...
Click to collapse
Thanks for helping me, do you mean bootloader.img?
Ok done reflash stock, OTA's and checked gps is fine now backing up... going to use the PureNexus rom or ASOP-CAF
ARRRRRGGGGG Same damn issue... Maps crashes the phone.... so frustrating I am going to give up soon and stick with stock.
Going to try an get a logfile maybe someone can take a look at it
Thanks
ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks
grantdb said:
ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks
Click to expand...
Click to collapse
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!
grantdb said:
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!
Click to expand...
Click to collapse
You can use ADB to get real-time logging of the crash on your PC... Use Google to find the command.
acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
Sent you logcat via pm thanks again!
Well I started getting random reboots in Pure Nexus ROM and so tried LOS and right away I had the reboot from Maps. I give up, staying with stock.
Thanks
Seems like one of my problems could be ASOP-CAF ROM as the version I was flashing uses a custom Kernel that has known issues with 7.1.2 and causes bootloops and crashes. The UltraDev kernel changes some things in the modem and could be why any roms I tried after flashing ASOP-CAF would not change the modem and were 7.1.2 based.
Anyways...
Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.
grantdb said:
Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.
Click to expand...
Click to collapse
Check out this bug report. It might be your APNs... https://jira.lineageos.org/browse/BUGBASH-248
By messing with my APN settings as per above bug report I can use maps and have no more random reboots. Woop woop