Problem after BAMF Remix Flash - Thunderbolt General

I flashed BAMF Remix 1.6.3 and everything seemed fine until I rebooted. I had restored everything. Now when I reboot I get:
ROM Manager Premium License has stopped unexpectedly
The Process com.android.phone has stopped unexpectedly
The Process android.process.media has stopped unexpectedly
The last two pop up a few times. The radio does not connect.
Tried powering off once and it rebooted. Hit the power button on another occasion and it rebooted.
Great!

When you say restored everything, you mean using titanium backup ? Sounds to me like it wasn't a clean install or you restored apps+data and not just apps....... But idk just a stab in the dark
Sent from the Swag ThunderBolt ADR6400L using XDA Premium App

Seems like it wasn't a clean install. Did you make sure to wipe everything before flashing?

Yes, I wiped everything. My problem may have been restoring everything from Ti Backup. I flashed Clockwork Recovery and re-flashed BAMF and let the apps reload themselves and am selectively restoring certain items from Ti Backup. So far so good.
Still new to Ti Backup. Learning....

I had this same thing happen to me. Wiped and everything. When I restored backed up apps (with titanium) it started giving me never ending force quits to my phone (com.android.phone).
I am going to start from scratch again and see what happens...

Related

Please help: unusual bootloop/CWM error

Hi
I installed Thiaz ROM and the ICS theme which there is a link to on his V2.4 page. All was running fine and dandy for a day. I installed all of my programs, apps, etc, and used App2SD to move some of them to the SD. Each time I did this, it said 'failed' the first time and then allowed them to be moved on the next. I rebooted the phone a couple of times and never had any problems. After I had got things set up as I wanted them, I rebooted into CWM and did a new backup. I then rebooted and went into bootloop.
Cleared data, dalvik and even battery stats. Tried fixing permissions. Nothing worked at all, still boot loop. Did a factory reset and restored the backup and still bootloops.
If I restore to the original backup from when I first put on the ROM (no ICS theme), it works OK. Then after a few hours and after I have turned on and off successfully a few times, I get the old bootloop again. I have not messed around with any system files, etc. One time it was after I moved a file with File Expert but I uninstalled that programme and haven't used since.
Any help or suggestions would be very gratefully received as I don't really want to go back to the stock V21a but I can't be doing with setting up everything on my phone from scratch every day either!
I hope someone can help me.

[Q] Froze Andriod OS in Supermaid, can't boot.

I rooted my phone and replaced all kinds of things and a installed a new launcher, but the startup time was unbearable. I let my friend tinker with it, and from the SuperMaid app, he apparently froze the Android OS (I guess he thought my launcher was an OS) before I had a chance to back anything up with Titanium. When the phone died, it won't of course won't load. It's a Samsung Mesmerize, so I have the the one file from ClockModRecover, and that's it. I tried to restore that file, and it won't. Is my phone bricked? I'm kicking myself for all of this.
Well...did you install clockwork mod recovery? Not the manager app in android, but the actual recovery? If so, did you do a nandroid backup? If you did, restore it. If you never bothered to do a backup but do have cwm recovery, do a factory reset. If no cwm then last thing is boot into normal recovery and try a reset from there. You will likely lose root, and will need to root the phone again, and keep your friend out of your OS.
Tapatalked from my A100 - Flex Reaper RF1.
recovery isn't working
When I tried to restore the nandroid backup, it repeatedly failed saying it couldn't (I can't remember if it was mount or unmount) the system. So I did the factory restore as you suggested, and when I turned on the phone, I received a text message. However, I'm getting a force close message that's preventing me from doing anything: "The application TwLauncher (process com.sec.android.app.twlauncher) has stopped unexpectedly...") When I click Force close, it just pops right back up, cutting off functionality of the phone.
Ok reboot back into recovery, wipe cache, go to advanced, wipe dalvik, fix permissions, reboot.
Sent from my LG-P999 using Tapatalk 2
didn't work =(
I did all those things and the system repeatedly wouldn't unmount. I had to just go back to Froyo 2.2 with Odin. The good news there is now I can install Ice Cream Sandwich. I figure I can't do too much damage, and if I do, I still have the backup
I said to reboot not restore or flash, but I'm glad you got it all figured out. The fix permissions and caches being wiped was to try to fix the current install, not prep for a new rom or restore. At least I assumed flash or restore since you mentioned system not unmounting which only happens for that.
Sent from my LG-P999 using Tapatalk 2
Sent from my LG-P999 using Tapatalk 2

Shutdown issue - freezing on shutdown - SkyICS [FIXED]

I was running SkyICS ROM 4.2E6.
Great ROM, liked it a lot.
I then installed the KOB4LT theme. Upon my first shutdown, I noticed it was freezing. Just a blank screen and the haptic buttons were lit up.
I did the usual, cleared cache, davlik, removed battery a few minutes, fixed permissions, etc. Nothing helped.
So I reinstalled the most recent update patch from SkyICS and that didn't fix it either. So I wiped the phone and installed the RIII base and E7 of SkyICS (very latest).
Again I loved things for a few days.
But then I used ROM Toolbox to do a little customization.
Then I installed a few live wallpapers from the Market.
And got some spam infestation as a result.
So I wiped the phone and restored from a day old Nandroid backup.
And voila... the shutdown issue is back.
So I wiped the phone again and restored a two-day old Nandroid.
And again I have the shutdown issue.
Any ideas for me to try? I spent a lot of time getting that ROM just the way I wanted and don't want to have to reflash a new ROM all over again.
Fixed it.
1) Wiped phone (again).
2) Flashed the original UCLD2 ICS leak (I727UCLE2_OneClick).
3) Flashed recovery.
4) Installed 5.5.0.4 (?) touch recovery.
5) Wiped phone.
6) Restored from backup.
7) Rebooted w/out any problem.
Thanks, I was having the same problem today and this fixed it.

System Partition Read Only.

Earlier tonight I was on Valhalla Final Lightning Zapped. After using titanium backup to integrate some system app updates to rom and adjusting my SD Read Ahead to 4096 I then restarted my phone just to see if any system changed needed to take place because of a needed reboot. But once I rebooted everything kept on crashing and I was instantly bogged with app FC and something about Android Log provider crashed please retry again. Every time I tried to restart the log provider it kept on crashing preventing me from doing anything. So I said let me go back to my lock screen and long press power button to reboot into recovery using advance power menu. So my phone then rebooted into recovery so I tried formatting data, cache and dalvik and reflash my back up of Valhalla Final but when I went to do so I kept on receiving a error saying fail to unmount system partition. So I went to advance settings in recover and clicked on show log then after looking at the log it said system read only so I said dammit man .-. Since the partition was no read only I couldn't flash any rooms at all. Even if I did it would just restore the boot image and restart Valhalla final which kept on crashing because of the stupid android log provider. At the time I was away from my computer so I just decided to try flashing a ics. Risky but bleh at this point my options are slim, I flashed cm9 but phone restarted and showed Android logo with some crazy crash image. So I said to myself I wonder if I could access CM9 Recovery. So I took of my battery cover and pull the battery out and reinsert it. 3 button combo my way into cm9 recovery and install a fresh copy of cm9. I figured though the system partition was read only and at the time a BML state if I try to convert it to MTD it should everything should go back to normal. So on I had went with proceeding to flash cm9. Phone booted perfectly luckily I had a nand backup of cm9 before I had downgraded back to GB. I then went back to recovery to wipe everything and restore from backup phone is run completely back to normal now. Does anyone have any insight on this strange fiasco?
Sent from my SGH-T959V using Tapatalk 2
VillaCastana321 said:
Earlier tonight I was on Valhalla Final Lightning Zapped. After using titanium backup to integrate some system app updates to rom and adjusting my SD Read Ahead to 4096 I then restarted my phone just to see if any system changed needed to take place because of a needed reboot. But once I rebooted everything kept on crashing and I was instantly bogged with app FC and something about Android Log provider crashed please retry again. Every time I tried to restart the log provider it kept on crashing preventing me from doing anything. So I said let me go back to my lock screen and long press power button to reboot into recovery using advance power menu. So my phone then rebooted into recovery so I tried formatting data, cache and dalvik and reflash my back up of Valhalla Final but when I went to do so I kept on receiving a error saying fail to unmount system partition. So I went to advance settings in recover and clicked on show log then after looking at the log it said system read only so I said dammit man .-. Since the partition was no read only I couldn't flash any rooms at all. Even if I did it would just restore the boot image and restart Valhalla final which kept on crashing because of the stupid android log provider. At the time I was away from my computer so I just decided to try flashing a ics. Risky but bleh at this point my options are slim, I flashed cm9 but phone restarted and showed Android logo with some crazy crash image. So I said to myself I wonder if I could access CM9 Recovery. So I took of my battery cover and pull the battery out and reinsert it. 3 button combo my way into cm9 recovery and install a fresh copy of cm9. I figured though the system partition was read only and at the time a BML state if I try to convert it to MTD it should everything should go back to normal. So on I had went with proceeding to flash cm9. Phone booted perfectly luckily I had a nand backup of cm9 before I had downgraded back to GB. I then went back to recovery to wipe everything and restore from backup phone is run completely back to normal now. Does anyone have any insight on this strange fiasco?
Sent from my SGH-T959V using Tapatalk 2
Click to expand...
Click to collapse
Maybe it all started w/ a bad Valhalla Final or Lightning Zap download, check the md5, also if u r trying to flash ics I would recommend using a one-click first (It just seems like it always works better for me when I do that)... and I assume u know about the kernel version b4 flashing ics, right?
Yeah. Seems like I do have to do a one click. Everytime I go to make a call on pics it just ring once and then automatically hangs up
Sent from my SGH-T959V using xda premium
ya I would try that 1st

[Q] Gapps and other processes keep crashing

yesterday I made a backup of my android phone using clockwork mod. After that I installed CM11 and flashed gapps it was working just fine. But I decided to restore to my old backup. So I whipped the phone cache and did a factory reset. But when the restore finishes and I restart my phone the phone becomes practically unusable. It says Unfortunatley the proceses com.google.gaspps has stopped. So every time I press ok the processes says the same thing along with other proceses that keep crashing. My phone is a s4 and the back up was of Kitkat 4.4.2 touchwiz.
try clear all gapps (playstore,gmail,google sync,etc) data and cache
reflasher said:
yesterday I made a backup of my android phone using clockwork mod. After that I installed CM11 and flashed gapps it was working just fine. But I decided to restore to my old backup. So I whipped the phone cache and did a factory reset. But when the restore finishes and I restart my phone the phone becomes practically unusable. It says Unfortunatley the proceses com.google.gaspps has stopped. So every time I press ok the processes says the same thing along with other proceses that keep crashing. My phone is a s4 and the back up was of Kitkat 4.4.2 touchwiz.
Click to expand...
Click to collapse
I have the same issue. i tried everything but when i restore a backup upon restart the phone GAPPS process crashing.
so just for checking i factory reset phone and take a backup. when i restore that fresh backup, it show same result.
any help will be highly appreciated.

Categories

Resources