I flashed the S3 Sprint MOAR ROM on my phone. Other Virgin Mobile users in the MOAR thread seem to be using the ROM fine. It looks slick but I am getting a problem with com.android.phone. It FCs all the time at boot and about every 3 minutes after. I have tried flashing the MK3 and MK5 modems. I have tried flashing all of the APN fixes. I have tried reflashing the ROM several times. I have tried clearing the cache and data of Phone and Contacts. To flash I am running the latest version of Philz Recovery.
Thanks!
Did you do a " Clean " install at first ? Meaning did you wipe System - Data - Dalvik - Dalvik Cache - Factory Reset - Wipe Internal Storage. Did you verify the MD5 checksum before flashing the Rom ?
prboy1969 said:
Did you do a " Clean " install at first ? Meaning did you wipe System - Data - Dalvik - Dalvik Cache - Factory Reset - Wipe Internal Storage. Did you verify the MD5 checksum before flashing the Rom ?
Click to expand...
Click to collapse
I did all of this but completely wipe out the internal of all folders. I didn't bother to remove my download, pictures, etc.
This is going to sound strange, especially after asking if you did a clean install. But try doing a dirty flash.
prboy1969 said:
This is going to sound strange, especially after asking if you did a clean install. But try doing a dirty flash.
Click to expand...
Click to collapse
That was the first thing I tried actually. I figured, oh I'll just overwrite whatever broke. No dice :\. I'm wondering if its something with my phone. This isn't the first rom where I have experienced this.
Have you tried fixing permissions?
Related
Just did a clean install of Anthem v2.1 and everything booted up fine. I went into recovery, wiped data, dalvik, and cache, and installed the latest gingertiny kernel. When I reboot from recovery, I get bootloop. What's wrong?
prinzmetal6 said:
Just did a clean install of Anthem v2.1 and everything booted up fine. I went into recovery, wiped data, dalvik, and cache, and installed the latest gingertiny kernel. When I reboot from recovery, I get bootloop. What's wrong?
Click to expand...
Click to collapse
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.
cmlusco said:
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.
Click to expand...
Click to collapse
Thank you!
cmlusco said:
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.
Click to expand...
Click to collapse
Just to add to this. NEVER wipe data after flashing a Sense 3 or Sense 3.5 ROM. Actually even some Sense 2.1 ROMs that is a bad idea.
This is because the way these ROMS are built as the storage in /system cannot hold the whole ROM so they have to build part of it in /data. So wiping data will clear the ROM components as well as the user data. If you have to wipe data, plan to reflash the ROM again. So I say don't wipe data AFTER flashing the ROM unless you plan on reflashing the ROM. You can and will probably need to wipe data before flashing the ROM though.
Is there a reason why Titanium Backup isn't working? When I try to restore the progress bar just doesn't do anything...I had this problem with my Galaxy Tab and I had to change the app processing mode but is there a different issue?
prinzmetal6 said:
Is there a reason why Titanium Backup isn't working? When I try to restore the progress bar just doesn't do anything...I had this problem with my Galaxy Tab and I had to change the app processing mode but is there a different issue?
Click to expand...
Click to collapse
Make sure USB debuggging is on. If it is, I don't know.
I think the problem is that I ran out of internal memory, I have a huge sd card so I think I can solve this problem. Thank you for replying though. I would've posted something on the actual rom page but I don't have enough thumbs up
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Firewalker1980 said:
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Click to expand...
Click to collapse
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
ahmadallica said:
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
Click to expand...
Click to collapse
Hey thx for your suggestions!
I always flash a "new" rom that way though. But an update of the same rom, I "dirty" flash, which should be fine according to everyone.
No matter what Rom/Kernel I use, I still frequently have to pull the battery out.
It's never from locking up within Android. It just freezes/loops on the Google bootlogo.
I once wiped everything, even the storage space, and it helped for a little while, but did not make it go away for good.
Could it be related to certain apps ? Maybe PGM or Seeder or smth ?
All input welcome
---------------------------------------------------------------
Phone: Samsung Galaxy Nexus Maguro
Rom: AOSPA 2.99 latest
Kernel: AK Purity v20
Recovery: TWRP 2.3.3.0
Hey all,
I've been searching for a while now and decided I should just post my question finally. I have the Galaxy SIII, rooted, and running CM10 stable. For the last 3 months or so, my SMS app, Messaging, has been randomly force closing and crashing. The only way to fix it is by rebooting the phone. I've tried re-flashing the mod 5 times, and even wiped data and done 2 factory resets. Still no luck.
And more recently my "phone" app has been doing it too. It crashes when I open up the dial pad and drops calls randomly and I have to restart my phone for it to work again.
Both of these will happen randomly. Sometimes I can go 4 hours without having to restart my phone, other times I have to restart my phone every 20 minutes. It's really starting to bug me.
Is there an app that's known to cause these crashes? Or is there a possibility that the mod file is corrupt? Thoughts? Questions? Any help is appreciated!!
When you flashed Cm10, did you come from stock or a custom rom? Did you also format /system?
If you made a nandroid while on stock, I would:
Wipe data, cache, dalvik and restore that. Then (assuming you still have Cm10 and gapps zips on your device) I would wipe data and caches again, format /system and flash rom/gapps. Wipe data/cache and reboot.
xBeerdroiDx said:
When you flashed Cm10, did you come from stock or a custom rom? Did you also format /system?
If you made a nandroid while on stock, I would:
Wipe data, cache, dalvik and restore that. Then (assuming you still have Cm10 and gapps zips on your device) I would wipe data and caches again, format /system and flash rom/gapps. Wipe data/cache and reboot.
Click to expand...
Click to collapse
When I flashed, it was from a previous CM10 ROM that worked fine. I reflashed because one of my apps was getting an "unknown" error, and now this crashing is happening. I don't think I have ever done "format /system". How do I go about that?
tango259 said:
When I flashed, it was from a previous CM10 ROM that worked fine. I reflashed because one of my apps was getting an "unknown" error, and now this crashing is happening. I don't think I have ever done "format /system". How do I go about that?
Click to expand...
Click to collapse
To have a completely clean install, you should always:
Wipe data
Wipe cache
Wipe dalvik (under advanced)
Format /system (under mounts and storage)
Flash rom
Flash gapps
Wipe data
Reboot
Be sure to have whatever you feel important backed up as this will wipe your system. Make a nandroid first if you don't already have one
xBeerdroiDx said:
To have a completely clean install, you should always:
Wipe data
Wipe cache
Wipe dalvik (under advanced)
Format /system (under mounts and storage)
Flash rom
Flash gapps
Wipe data
Reboot
Be sure to have whatever you feel important backed up as this will wipe your system. Make a nandroid first if you don't already have one
Click to expand...
Click to collapse
Thanks!! I'll try it tonight and post with the results tomorrow. Last time I flashed it took 2 days until the problems arose again.
tango259 said:
Thanks!! I'll try it tonight and post with the results tomorrow. Last time I flashed it took 2 days until the problems arose again.
Click to expand...
Click to collapse
There shouldn't be any issues if you have flashed correctly. Many users have also noted that a custom rom performs better when returning to stock and then flashing the new rom via the above procedures. Feel free to pm me your results
What the???
xBeerdroiDx said:
There shouldn't be any issues if you have flashed correctly. Many users have also noted that a custom rom performs better when returning to stock and then flashing the new rom via the above procedures. Feel free to pm me your results
Click to expand...
Click to collapse
To have a completely clean install, you should always:
Wipe data
Wipe cache
Wipe dalvik (under advanced)
Format /system (under mounts and storage)
Flash rom
Flash gapps
Wipe data <------------- ????
Reboot
I can't see this is a good thing, but I'm a noob.
You're saying after installing the new ROM and apps (Flash rom Flash gapps), you then go back into CWM and select 'wipe data/factory reset'??
Again, I'm a noob and maybe I'm reading this wrong!
Doing a wipe again right after installing a new ROM sounds so wrong to me.
What would that do?
RoidRulez said:
Wipe data <------------- ????
Click to expand...
Click to collapse
This step (step 7 in your list) isn't necessary.
When in doubt, follow the directions in the OP of the rom you are trying to flash, usually can't go wrong.
My detail about phone
Omega rom v14 XXDM5
XXDLK7
Stock kernal
Installation done and results :
Emotion note 4.5 without simplistic- system ui stopped status bar disappeared
Moon rom -system ui stopped status bar disappeared
Alliance rom v2 and v3 same problem
P.A.C man- bootloop
Resurrection remix -bootloop
EmotionMIUI - phone switches off in boot animation screen
What should I do to get my phone work normal.....?
Get TWRP Recovery
Wipe System, data, cache, dalvik, factory reset (wont delete anything from Internal sd) and/or... format data (deletes internal and everything but not extSD but I recommend doing this format)
Then fresh install a ROM
This should hopefully fix all problems in the phone..
Sent from my GT-N7100
Mohammed779 said:
Get TWRP Recovery
Wipe System, data, cache, dalvik, factory reset (wont delete anything from Internal sd) and/or... format data (deletes internal and everything but not extSD but I recommend doing this format)
Then fresh install a ROM
This should hopefully fix all problems in the phone..
Sent from my GT-N7100
Click to expand...
Click to collapse
Or use MegaWipe
http://forum.xda-developers.com/showthread.php?t=1983489
What recovery mode your using , Use TWRP, while installing rom , make sure you Wipe Cache, Dalvik Cache, and factory reset, and then install the Rom should be able to install it without any issues , Usually you get this error if your not following the OP instructions as mentioned please read the OP in how to install the rom.
Mohammed779 said:
Get TWRP Recovery
Wipe System, data, cache, dalvik, factory reset (wont delete anything from Internal sd) and/or... format data (deletes internal and everything but not extSD but I recommend doing this format)
Then fresh install a ROM
This should hopefully fix all problems in the phone..
Sent from my GT-N7100
Click to expand...
Click to collapse
I did full wipe even wipe system nothing happend...still the same...
I also tried install stock through odin(unrooted) again rooted still same problem
I follow same instructions give for a rom to install
While installing rom my phone not takes much time in boot animation sreen I takes about half minutes. ....
premve said:
I did full wipe even wipe system nothing happend...still the same...
I also tried install stock through odin(unrooted) again rooted still same problem
I follow same instructions give for a rom to install
While installing rom my phone not takes much time in boot animation sreen I takes about half minutes. ....
Click to expand...
Click to collapse
Mate are you sure you have 7100 but not the lte version?
try and check with Dr. Ketan see if you cold pm him and get some help he is the 1 who could help you in this situation
Sent from my GT-N7100 using xda premium
Problem:
After installing a new rom, I get stuck at the Samsung screen during 1st boot.
Background:
I tried cleaning up the internal card memory,just what I could see from My computer, so I started deleting files.After that my problem began. I had a back-up of Albinoman887's 4.4 build from 12-24-2013 which boots. I cant install the new nightly build without the problem occurring
Attempts to correct.
Factory wipe / Delvik Wiped each time
I used odin to revert back to stock. Installed but would not boot.
Any thoughts ?
Epoxyburn said:
Problem:
After installing a new rom, I get stuck at the Samsung screen during 1st boot.
Background:
I tried cleaning up the internal card memory,just what I could see from My computer, so I started deleting files.After that my problem began. I had a back-up of Albinoman887's 4.4 build from 12-24-2013 which boots. I cant install the new nightly build without the problem occurring
Attempts to correct.
Factory wipe / Delvik Wiped each time
I used odin to revert back to stock. Installed but would not boot.
Any thoughts ?
Click to expand...
Click to collapse
Have you tried using a different (newer version?) kernel?
After Odin back to stock do a factory reset.
☞ Sent from here☜???
error post ignore
error post ignore
error post ignore
baseballfanz said:
After Odin back to stock do a factory reset.
☞ Sent from here☜???
Click to expand...
Click to collapse
Shoot how did I forget that. I did that and it did boot. but the other roms will not
Epoxyburn said:
Shoot how did I forget that. I did that and it did boot. but the other roms will not
Click to expand...
Click to collapse
Because you need to do a full wipe from within recovery before you can install a different type of ROM. You can't just clean up files you can see through your computer. Also, full wipe is more than just factory reset and Dalvik cache.
Sent from my SGH-M919 using xda app-developers app
lalec said:
Because you need to do a full wipe from within recovery before you can install a different type of ROM. You can't just clean up files you can see through your computer. Also, full wipe is more than just factory reset and Dalvik cache.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I guess I should ensure that I am doing a "full wipe" properly. I suppose I am not doing it. How should I be doing a full? Like this? :
Wipe Data/factory reset
Wipe Cache
Wipe Dalvik-Cache
Wipe Battery Stats
Format /system
lordcheeto03 said:
Have you tried using a different (newer version?) kernel?
Click to expand...
Click to collapse
Installed "ChronicKernel-KK4.4-AOSP-TMO-v2.4.zip" ...problem persists
Epoxyburn said:
I guess I should ensure that I am doing a "full wipe" properly. I suppose I am not doing it. How should I be doing a full? Like this? :
Wipe Data/factory reset
Wipe Cache
Wipe Dalvik-Cache
Wipe Battery Stats
Format /system
Click to expand...
Click to collapse
You haven't wiped the system partition in that description.
You need to wipe, system, data, cache, dalvik (battery stats isn't a real thing that needs wiping)
Then flash the ROM.
If none of that works, restore the whole thing back to stock in Odin and start over.
Epoxyburn said:
I guess I should ensure that I am doing a "full wipe" properly. I suppose I am not doing it. How should I be doing a full? Like this? :
Wipe Data/factory reset
Wipe Cache
Wipe Dalvik-Cache
Wipe Battery Stats
Format /system
Click to expand...
Click to collapse
Your exact steps are dependent on which custom recovery you are using (e.g., CWM, TWRP, Philz Touch, etc.). For the custom ROMs I have tried the developer always included information in one of the first couple of posts explaining exactly how much wiping is required for that ROM and what specific steps to follow in CWM or TWRP. For a good example of this look carefully at jovy23's original post in this thread and you will see both TWRP and CWM sections:
http://forum.xda-developers.com/showthread.php?t=2292054
I've seen different definitions of "full wipe," one example of which is in the 6th post of this thread:
http://forum.xda-developers.com/showthread.php?t=1410881
but, having said that, if your ROM's developer has specific instructions it's always a good idea to follow those. Good luck!