First thread here
I used cf auto root specifically for my device from the autoroot chainfire website just to delete bloatware like galaxy apps, S health. I didn't delete Touchwiz
Everything was fine and dandy for a few days until my phone starts crashing when browsing youtube, facebook etc.
recovery screen said it was due to 'dm-verity verification failed'
Browsing the forums, apparently flashing it with the stock rom should solve the issue. It didn't though
I flashed it and rooted it again and the problems persist
I'm lucky I backed up my data. It's just annoying having to restore everything once my phone boot loops.
What seems to cause it?
Because it's not clear from your thread, I've got a question:
After you flashed the ROM and rooted it again, did you remove the bloatware again, just as before?
Vygravlil said:
Because it's not clear from your thread, I've got a question:
After you flashed the ROM and rooted it again, did you remove the bloatware again, just as before?
Click to expand...
Click to collapse
Yes
I deleted Galaxy apps, penup, s health etc.
muaddibzero said:
Yes
I deleted Galaxy apps, penup, s health etc.
Click to expand...
Click to collapse
So the problem is caused by removing the bloatware. Because of the programming of the bloatware and the ROM itself (they are kinda "linked" to each other), it can brake your system, just as in your case.
How did you remove the bloatware? Did you use an app? Maybe we can find a way removing it without killing your system.
Vygravlil said:
So the problem is caused by removing the bloatware. Because of the programming of the bloatware and the ROM itself (they are kinda "linked" to each other), it can brake your system, just as in your case.
How did you remove the bloatware? Did you use an app? Maybe we can find a way removing it without killing your system.
Click to expand...
Click to collapse
I used titanium backup to delete it
Update
Bloatware doesn't matter now though
I reflashed my phone with stock rom again, this time without rooting. My phone still suffered from boot loops. What's happening here? Do I have to do a factory reset?
muaddibzero said:
I used titanium backup to delete it
Update
Bloatware doesn't matter now though
I reflashed my phone with stock rom again, this time without rooting. My phone still suffered from boot loops. What's happening here? Do I have to do a factory reset?
Click to expand...
Click to collapse
Did you flash the proper stock ROM for you device? Where did you get it from? I guess that something went wrong while flashing. A factory reset could solve it, but flashing the stock ROM should have resolved the issue already if the bootloop was caused by removing the bloatware - that's what surprises me.
Vygravlil said:
Did you flash the proper stock ROM for you device? Where did you get it from? I guess that something went wrong while flashing. A factory reset could solve it, but flashing the stock ROM should have resolved the issue already if the bootloop was caused by removing the bloatware - that's what surprises me.
Click to expand...
Click to collapse
Hi sorry for necroing and leaving a late reply
I used the Singapore starhub android 6.0.1 rom the device came with
I reflashed it and did a factory reset 3 weeks ago
Replaced battery as well
Worked fine for the time being
Then out of a sudden a boot loop occurred while I was on data
What's the cause of this?
I'm frankly tired of having to reflash the rom over and over again as well as restoring backups
I'd go for a full, clean install of stock (format /data from TWRP. Yes, a full format! Make sure you backup your media as this will erase absolutely everything.) and then flash stock with Odin.
Test it out see if it still has problems or if it's stable.
DO NOT RESTORE APPS FROM TITANIUM BACKUP
Re-download them from scratch.
I've noticed that I used to get random re-boots after restoring backed up apps from Titanium Backup.
Went ahead and started the phone over from absolute 0 and it seems my problem went away.
Related
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
obelisk79 said:
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
Click to expand...
Click to collapse
Will that work on MCR 2.2 as well? I'll look into that. Is it something I can do from recovery?
Ceger
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
obelisk79 said:
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
Click to expand...
Click to collapse
Do you need to do both? Wiping the dalvik cache created lots of app fc issues, which would be fine if the phone actually worked. Still won't make or receieve calls.
And thank you for the assistance.
Ceger
Edit. Clearing the boot cashe got rid of the FC issues. However, still have same issue with the phone app. This is so annoying.
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Ceger said:
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Click to expand...
Click to collapse
use these commands to clear cache
rm -r /data/boot-cache/
rm /data/dalvik-cache/
once you finish then reboot.everything should go away...
he's done that already.
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
obelisk79 said:
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Click to expand...
Click to collapse
Done and done and no difference.
reddick said:
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
Click to expand...
Click to collapse
Done, even manually moved some files in case they were corrupted at one point. Very bad move, nandroid backup was my friend there.
Guess a wipe will be the only option then. How annoying.
Thanks for all of your inputs.
Ceger
Another thought... would updating my phone with latest kernal compile possibly do the trick? Or how about a replacement process for google.com.phone?
Ceger
Interesting theory.... worth a try.
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
toastcfh said:
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
Click to expand...
Click to collapse
Actually, the fix was much simpler. I wiped the SD ext partition and just did a Recovery Wipe. It went back to stock modded rom that remained rooted. I then used Titanium to reinstall my apps with data and then MyBackup to get back some settings such as my scenes, etc. and all was good. Took all of 30 minutes to get my Hero back up and running in better condition than before.
Thanks all for the assists.
Ceger
com.android.phone
com.android.phone
i am facing this prob on cyanogen mod10....when ever i reboot my optimus 2x....i face this damn problem
help plzzzzzzzzzz.....!!!!!
Has anyone else had an issue with s-voice not working? Mine opens fine, takes the voice command, acknowledges it, and then black screen and crash. I've rooted and disabled all the AT&T labeled apps in TiBu and that's it. Any input on troubleshooting would be great!
devlmaycry81 said:
Has anyone else had an issue with s-voice not working? Mine opens fine, takes the voice command, acknowledges it, and then black screen and crash. I've rooted and disabled all the AT&T labeled apps in TiBu and that's it. Any input on troubleshooting would be great!
Click to expand...
Click to collapse
That's exactly your issue by experience, you can't disable chatOn, somehow it is needed food S voice to work, if you removed them you still need to restore with Kies or Odin, if you didn't remove them, then unfreeze them.
Yeah I had removed them in TiBu and then restored them, but the problems persist. Right after I posted the thread I read another with the same problem. So, right now I'm in the middle of a reset.
devlmaycry81 said:
Yeah I had removed them in TiBu and then restored them, but the problems persist. Right after I posted the thread I read another with the same problem. So, right now I'm in the middle of a reset.
Click to expand...
Click to collapse
Tryng to restore them after been removed doesn't work , like I mentioned before, the same happened to me, it seems that once you remove them something gets corrupted in the shared apps and it doesn't get fixed restoring those apps back in order to fox you must restore with Kies or Odin. but don't worry, you won't lose your data, settings and apps, you will get all the original apps back just re-root, and this time just remove the rest but these ones.
erasat said:
Tryng to restore them after been removed doesn't work , like I mentioned before, the same happened to me, it seems that once you remove them something gets corrupted in the shared apps and it doesn't get fixed restoring those apps back in order to fox you must restore with Kies or Odin. but don't worry, you won't lose your data, settings and apps, you will get all the original apps back just re-root, and this time just remove the rest but these ones.
Click to expand...
Click to collapse
Cool deal! I'm waiting for the stock rom to DL now so I can odin back to stock... The things I will do for an app to work
Problem fixed with odin back to stock then freezing everything except chatON.
Sent from my SAMSUNG-SGH-I337 using xda premium
Hi, I recently was on paranoid android and was getting ready to sell my galaxy s4 I9505 so restored a back up I made of the stock rom which was what came on the phone when I bought it.
I restored the back up, but once the phone had booted it was really slow and I kept getting loads of error messages saying different processes had kept failing. The same as in this thread.
http://forum.xda-developers.com/gal...restoring-stock-rom-cwm-t2882455#post55566370
I then booted back into recovery and wiped data and dalvik cache, which after rebooting sorted the problem. The device was running smoothly and so I went on downloading my apps from the play store.
But I've since noticed apps like swift key, instagram, whatsapp and snap chat seem to be having issues. I don't have any SD card installed just the phones internal memory, which I have ample space (9GB) but whatsapp won't let me download images.
Snapchat says I need to install an sd before viewing video and Instgram mentions I need an SD before being able to take a picture.
Also the language pack for Swiftkey won't download and when I try and download a theme it says it can't save it.
So it seems there's something wrong with the way it's trying to store certain files. Has anyone else come across this yet?
I'm planning on following the whole unroot process anyway documented here: http://forum.xda-developers.com/showthread.php?t=2265477 which I'm hoping will fix it.
But I wondered if anyone knew what it is that's caused it?
Rezaei12 said:
Hi, I recently was on paranoid android and was getting ready to sell my galaxy s4 I9505 so restored a back up I made of the stock rom which was what came on the phone when I bought it.
I restored the back up, but once the phone had booted it was really slow and I kept getting loads of error messages saying different processes had kept failing. The same as in this thread.
http://forum.xda-developers.com/gal...restoring-stock-rom-cwm-t2882455#post55566370
I then booted back into recovery and wiped data and dalvik cache, which after rebooting sorted the problem. The device was running smoothly and so I went on downloading my apps from the play store.
But I've since noticed apps like swift key, instagram, whatsapp and snap chat seem to be having issues. I don't have any SD card installed just the phones internal memory, which I have ample space (9GB) but whatsapp won't let me download images.
Snapchat says I need to install an sd before viewing video and Instgram mentions I need an SD before being able to take a picture.
Also the language pack for Swiftkey won't download and when I try and download a theme it says it can't save it.
So it seems there's something wrong with the way it's trying to store certain files. Has anyone else come across this yet?
I'm planning on following the whole unroot process anyway documented here: http://forum.xda-developers.com/showthread.php?t=2265477 which I'm hoping will fix it.
But I wondered if anyone knew what it is that's caused it?
Click to expand...
Click to collapse
Did you install the stock rom before or have you just restored your old backup?
If I were you, I would clean everything, install the stock sammy firmware (with latest base) and after that restore your backup
Tkkg1994 said:
Did you install the stock rom before or have you just restored your old backup?
If I were you, I would clean everything, install the stock sammy firmware (with latest base) and after that restore your backup
Click to expand...
Click to collapse
No it's not a rom, I just restored my old back up of my OS before I started flashing any custom roms.
I did a factory reset on the phone hoping it might resolve it. Which hasn't, but I'm not sure now if it's got rid of CWM. Would as I can't seem to get it to boot into recovery (it maybe just me not releasing the volume up button at the right time).
Think I'm going to have to flash a clean stock firmware following the unroot process and hope that fixes it.
I I have a Galaxy S4 with KitKat 4.4.2 and TWRP installed. I have been using Nandroid for backups.
Today I (stupidly) deleted the CSC.apk file with Uninstall and the phone started acting really strangely. I tried restoring the CSC app but it wouldn't do it (I tried multiple times). So I booted into TWRP recovery mode and did a full restore which worked fine...until I rebooted the phone.
I have quite a few apps that continually crash with:
Unfortunately, (App Name) has stopped
and then all I can do is tap the OK button. After tapping OK the errors popup continuously.
Is this normal? How can I fix this without reflashing the phone? This is my first restore ever done with Nandroid Any ideas? Annoyingly I also lost the activation for my GPS app (CoPilot). I thought Nandroid was an exact clone/backup so when you screw the phone up you can restore back to EXACTLY how the phone was when the backup was done?
Anyway, appreciate any help or thoughts on how I can get my apps to work without the constant stopping popups!
Thank you!
Can anyone help please?
Go back into recovery and wipe both the regular cache and dalvik cache.
As to the lost CoPilot activation, you'll need to contact CoPilot, then explain the situation to them, and they should be able to help you.
Strephon Alkhalikoi said:
Go back into recovery and wipe both the regular cache and dalvik cache.
As to the lost CoPilot activation, you'll need to contact CoPilot, then explain the situation to them, and they should be able to help you.
Click to expand...
Click to collapse
Thanks! I tried that but after wiping both caches and rebooting the phone and entering my SIM PIN, I am still constantly getting the "Unfortunately, (App Name) has stopped".
Is there anything else I can try? I'm a but confused by this as I thought Nandroid was an exect image of the phone! I'm not worried about CoPilot at all but the rest is important
Do a factory reset from within TWRP, then restore from the nandroid backup. How old is this nandroid?
Strephon Alkhalikoi said:
Do a factory reset from within TWRP, then restore from the nandroid backup. How old is this nandroid?
Click to expand...
Click to collapse
I'll give that a try tonight. I am running Nandroid 4.4.5 and the backups were created about a week ago.
Many thanks for your help!
BB007BB said:
I'll give that a try tonight. I am running Nandroid 4.4.5 and the backups were created about a week ago.
Many thanks for your help!
Click to expand...
Click to collapse
So I tried doing a factory reset from TWRP and then doing a Nandroid restrore but after rebooting the phone I was still getting LOTS of errors with applications not working. Even the firewall wouldn't work as it couldn't find the config file.
I don't get it, I thought Nandroid made an EXACT image of your phone so if something went wrong and you performed a restore, your phone would be back to a working state?
BB007BB said:
So I tried doing a factory reset from TWRP and then doing a Nandroid restrore but after rebooting the phone I was still getting LOTS of errors with applications not working. Even the firewall wouldn't work as it couldn't find the config file.
I don't get it, I thought Nandroid made an EXACT image of your phone so if something went wrong and you performed a restore, your phone would be back to a working state?
Click to expand...
Click to collapse
It does, but your backup can get corrupted.
Hello.
My Galaxy S4 was dying so T-Mobile just replaced it with an S5. It came with:
LMY47X.G900TUVS1FOJ4
I clicked on Software updates in About device and it did whatever updates, but the version stayed the same. Then I went to autoroot [dot] chainfire [dot] eu and downloaded the correct file to root. I unzipped the file and ran Odin 3.10.6 that came with it. I was able to root the device no problem.
What seemed like a problem afterward was that I couldn't find SuperSU in the Application list. I know the phone was rooted though because I could launch Titanium Backup to restore all my stuff from the S4. I went to the Play Store to download SuperSU. It kept complaining that I needed a new binary, but it would fail every time to update. I even tried downloading the latest SuperSU zip to install in the recovery mode, but that failed too. I really wasn't too worried about this.
While looking up how to root the S5, I saw some posts where people mentioned their root access stopped after 24 hours. I just experienced this when I launched Titanium Backup to begin uninstalling bloatware. I was informed that I didn't have root access anymore.
I figured I'd try to reflash the auto-root through Odin. According to Odin, everything passed, but looking at the device, it said it's already patched and the restore failed, so it aborted.
Now the device is stuck in an infinite reboot loop. I can access both the download and recovery modes, but that's it.
I'd really really like to not have to do a factory wipe as it was a pain to get everything copied over from the S4.
Can I flash it with something else?
Once I can get back in the device, how do I keep the device rooted? Do I have to flash TWRP or CWM?
The only root program I use is Titanium Backup and would really really like to keep using it to makr regular backups.
Thanks a lot.
Try booting into recovery and wiping the CACHES
If it still won't boot, grab a stock ROM from sammobile .com for your model S5 (G900T by the looks of the ROM name) and flash it with ODIN from download mode
That won't wipe your data or anything you've restored, as long as you don't reset
If it still won't boot, you might have to suck it up and factory reset after flashing stock
Was the TiBu backup you restored, rooted? Maybe restoring the backup restored an old version of SuperSU and broke the CF AR version
Might need to go down the TWRP and SuperSU from TWRP recovery route to get it rooted properly if CF AR isn't woprking 100%, which it doesn't for a fair few people
I tried clearing the cache, but that didn't work.
Is there a way to download the stock ROM without having to create an account on the download site?
The Titanium Backup I restored was rooted. Everything was totally fine, until I went back to TB and it suddenly told me I wasn't rooted anymore.
I did try TWRP after I made the original post. I think messed up the device, but I can get in now. I flashed the latest version and booted into Recovery Mode. I clicked on Fix Permissions and possibly one other thing. It let booted farther before the infinite bootloop. It'd show my lock screen and give me 1-2 seconds before rebooting. If I swiped quickly, I could see the home screen with most of my icons gone. Clicked on Apps shows most of the apps are gone. When I removed the SIM card, I stopped getting the infinite bootloop. Here are the list of important programs I have left:
Contacts (all cleared out), Gallery (all present), Messages (all present), My Files (shows files from previously installed programs that I can no longer access), Phone (works when I put the SIM card back in), Settings
Unfortunately, TB and the Play Store are both gone. I might be able to install stuff using adb or by copying files over. I haven't tried, but it doesn't look good. I tried reflashing the CF ROM. It didn't change anything. I suspect I may be looking at a factory reset at this point. I'm happy to try any other suggestions.
Thank you.
whynoteel said:
Is there a way to download the stock ROM without having to create an account on the download site?
Click to expand...
Click to collapse
Wut? lol, just make one, it's free...
XDA does not spoon feed
I created an account and downloaded the stock ROM. I flashed the device and got most of the programs to appear again though the Play Store was still missing. I decided to cut my losses and just do a factory reset. I rooted again and put everything back in place. Now I'm experiencing the problem where I lost root after a day or so of use. I'll start a new thread.
Thanks for your help.