I was using CR Droid no problems on my device but i wanted to use another rom. I flashed DU and when i flashed it it kept on restarting not exceeding 10 minutes between restarts so it was unusable. I thought the issue was rom related so i flashed SlimRoms and it did the same thing. So then i reflashed CR, which i was using perfectly before, and it also did the same thing. Can this be fixed?? Please any help would be highly appreciated
Are you clean flashing? Did you wipe system, data, and caches in TWRP between each flash?
If the downloads are good, none of those ROMs should be an issue, all are mature and stable.
Yes nothing is wrong with the roms as i have used the same ones before and i completely wipe everything using twrp never dirty flash, so what is the issue?
Related
Unable to post in developer section, have been using custom roms since February.
Sorry if this is in the wrong section, merge it and delete this paragraph if you must with http://forum.xda-developers.com/showthread.php?t=911364&page=1278
Had wolfbreaks rom running previous to installing FXP030 and unlocking bootloader, had issues with wolfbreaks rom. FXP030 seemed great and worked well, aside from the odd glitch. Had ran it for 2 days. Tried to update to FXP030b to test out new fixes (use the camcorder often) and upon flashing new kernel FTF file, phone booted, wiped cache, factory reset, wiped batt stats, wiped dalvik cache. loaded up the custom zips, for FXP030b + gapps, booted fine, couldn't get wifi working, couldn't connect with 3g. Tried to crash system server inside bad behavior in the dev tools as per instructions from collosus. upon crashing system service, phone hung hard for over 20 mins stayed on same screen, did not boot again till i flashed stock kernel. Not even FXP030 worked at that point. Hope I was not close to bricking my device.
quanium said:
Unable to post in developer section, have been using custom roms since February.
Sorry if this is in the wrong section, merge it and delete this paragraph if you must with http://forum.xda-developers.com/showthread.php?t=911364&page=1278
Had wolfbreaks rom running previous to installing FXP030 and unlocking bootloader, had issues with wolfbreaks rom. FXP030 seemed great and worked well, aside from the odd glitch. Had ran it for 2 days. Tried to update to FXP030b to test out new fixes (use the camcorder often) and upon flashing new kernel FTF file, phone booted, wiped cache, factory reset, wiped batt stats, wiped dalvik cache. loaded up the custom zips, for FXP030b + gapps, booted fine, couldn't get wifi working, couldn't connect with 3g. Tried to crash system server inside bad behavior in the dev tools as per instructions from collosus. upon crashing system service, phone hung hard for over 20 mins stayed on same screen, did not boot again till i flashed stock kernel. Not even FXP030 worked at that point. Hope I was not close to bricking my device.
Click to expand...
Click to collapse
Hi Buddy,
What you should have done when your phone froze after crashing the system server is to have taken your battery out and then just re-booted your phone, all would have been good.
If you are still at the same stage now from when you posted just flash the fxp kernel in the flashtool provided by J, your phone will now boot with FXP030b.
You was never close to bricking your phone so do not worry.
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
EtherBoo said:
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
Click to expand...
Click to collapse
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
xxxrichievxxx said:
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
Click to expand...
Click to collapse
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
EtherBoo said:
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
Click to expand...
Click to collapse
Yeah it can be such a pain, I flashed nightlies when they sounded like they fixed an important issue (it'd be every other day) and I flashed clean all the time. Now im just going to stick to CM11 M4 until the next milestone.
try changin network type to GLOBAL.
I got a question guys, i flashed the latest version PA for our device (PA4.5 beta 2) and notice i was having random reboots, i thought it was the rom, so i flashed CM latest nightly (2014815) & still was having reboots, so i figured it had to be an apk not playing nice & thought i was right when i noticed it was happening the most while using chrome, but it happened during the settings and some other apks, its not constant though, it very random, its like when you stay on an apk for a while, it just randomly reboots, anyone else been having this issue? or had this issue?, i both like two great theses for these roms & would feel like a fool if i cant use em lol, so any help would be appreciated, thanks
Are you wiping between flashes or dirty flashing?
If flashing clean, restore your apps (without data backups) one at a time. If you stop having the issue, then restore your app data one at a time.
If that doesn't fix it and you're flashing clean, going back to stock and doing a factory reset will almost certainly solve the issue.
frostedunit said:
Are you wiping between flashes or dirty flashing?
If flashing clean, restore your apps (without data backups) one at a time. If you stop having the issue, then restore your app data one at a time.
If that doesn't fix it and you're flashing clean, going back to stock and doing a factory reset will almost certainly solve the issue.
Click to expand...
Click to collapse
I always clean flash, I decided to flash sacs until a next major builds releases, thanks though
What kernel are you using?
Hey guys,
so I recently flashed the Ressurection Remix ROM v5.6.0 and all was working fine until today the touch screen decided to stop working. I couldn't unlock the phone so I tried rebooting it and now it's stuck on the boot logo screen. I can access TWRP and the touch screen works fine so I think the ROM has an issue of some kind? Just wondering if anybody else has experienced a similar issue with this ROM at all? The phone is SM-G900I and I flashed the kltedv ROM onto it. As I said it worked fine for a couple of days then all of a sudden it decides to stop working
Any and all help is appreciated
Did you do a clean flash? If not, try a clean flash or installing again. Also, try clearing your cache and dalvik
Well I did a factory restore using TWRP before flashing the rom on and then cleared Cache and Davlik after installing (as per developer recommendation) and it was fine for a couple of days which is what's stumping me! :S
Hello
I have been searching for a while about this and I've decided to make my own thread to help me and others.
My Moto X Pure (Style) has been having trouble booting into Lineage OS 14.1. The Problem started when I flashed it to the phone, I got an TWRP Error 7, so I opened the ZIP file and deleted two lines of code to stop Error code 7 from returning, surprisingly enough, it worked.
I recompressed it back to ZIP then, did an Advanced Wipe. I wiped Dalvik/ART Cache, Data, System, Cache.
Then, I reflashed the ROM. When it finished, I wiped the cache then rebooted to the newly flashed OS.
It was just sitting there, unresponsive, and the phone was progressively starting to heat up to a abnormal temperature while vibrating slightly. So I had to turn it off to cool the phone down before I make another desperate attempt to re-flash the OS.
I retried so many times until I found XDA Dev, I found it interesting and I've thought you've guys might help me along with the great community.
Please XDA Community, I'm in desperate need of your help.
--Victor F. 3/29/18 11:04 PM
I have this problem also. Was able to get up and running with this:
Flash this TWRP: https://forum.xda-developers.com/sho...&postcount=917
Flash this LineageOS: https://forum.xda-developers.com/sho...postcount=1054
Device booted fine after flashing these older builds. Only problem now is my device does not see any future Lineage updates.
Victor F. said:
Hello
I have been searching for a while about this and I've decided to make my own thread to help me and others.
My Moto X Pure (Style) has been having trouble booting into Lineage OS 14.1. The Problem started when I flashed it to the phone, I got an TWRP Error 7, so I opened the ZIP file and deleted two lines of code to stop Error code 7 from returning, surprisingly enough, it worked.
I recompressed it back to ZIP then, did an Advanced Wipe. I wiped Dalvik/ART Cache, Data, System, Cache.
Then, I reflashed the ROM. When it finished, I wiped the cache then rebooted to the newly flashed OS.
It was just sitting there, unresponsive, and the phone was progressively starting to heat up to a abnormal temperature while vibrating slightly. So I had to turn it off to cool the phone down before I make another desperate attempt to re-flash the OS.
I retried so many times until I found XDA Dev, I found it interesting and I've thought you've guys might help me along with the great community.
Please XDA Community, I'm in desperate need of your help.
--Victor F. 3/29/18 11:04 PM
Click to expand...
Click to collapse
Victor F. said:
Hello
I have been searching for a while about this and I've decided to make my own thread to help me and others.
My Moto X Pure (Style) has been having trouble booting into Lineage OS 14.1. The Problem started when I flashed it to the phone, I got an TWRP Error 7, so I opened the ZIP file and deleted two lines of code to stop Error code 7 from returning, surprisingly enough, it worked.
I recompressed it back to ZIP then, did an Advanced Wipe. I wiped Dalvik/ART Cache, Data, System, Cache.
Then, I reflashed the ROM. When it finished, I wiped the cache then rebooted to the newly flashed OS.
It was just sitting there, unresponsive, and the phone was progressively starting to heat up to a abnormal temperature while vibrating slightly. So I had to turn it off to cool the phone down before I make another desperate attempt to re-flash the OS.
I retried so many times until I found XDA Dev, I found it interesting and I've thought you've guys might help me along with the great community.
Please XDA Community, I'm in desperate need of your help.
--Victor F. 3/29/18 11:04 PM
Click to expand...
Click to collapse
How did you edit the file to make it flashable?
frakkingcylon said:
I have this problem also. Was able to get up and running with this:
Flash this TWRP: https://forum.xda-developers.com/sho...&postcount=917
Flash this LineageOS: https://forum.xda-developers.com/sho...postcount=1054
Device booted fine after flashing these older builds. Only problem now is my device does not see any future Lineage updates.
Click to expand...
Click to collapse
I have the same problem and sove whits this older builds, but some one know how update the LOS after this flash?
Lol, it works now
It works now, i just decided to wait
its all good now!
Victor F. said:
It works now, i just decided to wait
its all good now!
Click to expand...
Click to collapse
Sorry, but wait what?