Not charging or connecting file system. Was working fine, and no stressing of the USB port. I'm on AOKP 6/30. I reflashed AOKPand GAPPS, clearing cache, and Dalvik.
Ideas?
At least I have a wall charger for batteries..
p1gnone said:
Not charging or connecting file system. Was working fine, and no stressing of the USB port. I'm on AOKP 6/30. I reflashed AOKPand GAPPS, clearing cache, and Dalvik.
Ideas?
At least I have a wall charger for batteries..
Click to expand...
Click to collapse
That's very very odd, you could have a short somewhere but idk...... Have you tried flashing Plasma and tweaking with the charging options in STweaks? Also another user had issues with one of the AOSP Roms charging, I want to say Liquid, so he flashed Plasma and still couldn't get it to work until her froze the Performance app with Tibu. The discussion he had is in the Plasma thread a few pages back from the last.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
That's very very odd, you could have a short somewhere but idk...... Have you tried flashing Plasma and tweaking with the charging options in STweaks? Also another user had issues with one of the AOSP Roms charging, I want to say Liquid, so he flashed Plasma and still couldn't get it to work until her froze the Performance app with Tibu. The discussion he had is in the Plasma thread a few pages back from the last.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Success. Before I saw your response I downloaded VanillaRootBox nightly, flashing it with Gapps,clearing Cache, Dalvik then saw that the battery was charging. Then went back to AOKP & Gapps, clearing Cache, Dalvik AND DATA, and all slowly reinstalled back to normal..
Guess it shows that occasionally one must clear just about all, and that sometimes things do happen to corrupt perfectly good ROMs
p1gnone said:
S
Guess it shows that occasionally one must clear just about all, and that sometimes things do happen to corrupt perfectly good ROMs
Click to expand...
Click to collapse
Yep, I clear EVERYTHING before flashing. I format all my data and my system partition in TWRP just cause I don't like having to just through all the hoops of setting it back up cause of a screw up.
Sent from my SCH-I605 using XDA Premium HD app
Related
Did some searching and didnt find anyone with this problem. I have the lockscreen with the ring but the 4 apps to choose from aren't there and it seems to not care that I change between the 7 available different lockacreens. Anyone have a fix for this or experience it yet?
Would have posted in the BAMF thread but it says i need more posts befote I can.
Did you try rebooting?
First time I loaded, it didn't show up, but after a reboot, it's been working fine.
Reboot didn't work, grr.. I wonder if it has anything to do with spare parts?
Sent from my ADR6400L using XDA App
atm0sphere said:
Reboot didn't work, grr.. I wonder if it has anything to do with spare parts?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
One more question...
Did you do the update through Rom Manager or Clockwork Recovery?
Reason I ask, I noticed when I used Rom Manger the first time, not all everything worked correctly and things were missing.
So I restored my backup then went into clockwork recovery and installed the zip.
Then everything worked properly. I know others have reported odd issues when trying to flash through Rom Manager as opposed to Clockwork.
Not sure if that will help you, but you can always give it a try.
I wiped everything and used clockwork not rom manager
Sent from my ADR6400L using XDA App
Sorry I couldn't be anymore help.
Only thing I could think to do is try and reload the rom again.
About to do that now
Sent from my ADR6400L using XDA App
Yea took me 2 full clears/installs to get 2.05 installed correctly and fully
this is so frustrating, i did a reinstall and it worked for like 10 seconds then stopped working again.
i'm restoring my backup with everything that was working right now so i have a phone to use for the rest of the day but tm i'm gonna load up the froyo radio in case i wanna go back to das bamf 1.6.3 until some more of these kinks are worked out (random force closes of apps i wasn't even aware were running lmao)
thanks for all the help as always guys, this rom has SO much potential its amazing.
Would like to update this: the bamf remix Rom after a full wipe fixed literally every issue I had with the old ROM.
Best of luck to other early adopters, and these guys are doing a fantastic job..
Sent from my ADR6400L using XDA App
atm0sphere said:
Did some searching and didnt find anyone with this problem. I have the lockscreen with the ring but the 4 apps to choose from aren't there and it seems to not care that I change between the 7 available different lockacreens. Anyone have a fix for this or experience it yet?
Would have posted in the BAMF thread but it says i need more posts befote I can.
Click to expand...
Click to collapse
I had this issue after trying to solve a separate issue. The lock screen works in conjuction with a group of other operations, and if one of those other operations is stopped/removed/frozen/whatever, it messes up the lockscreen. I had to do a full data wipe and reinstall. Haven't had an issue since.
Yeah I had the problem once again. Driving me nuts
Sent from my ADR6400L using XDA App
I have been having this same problem since coming from 2.0-4 to 2.0-5 and remix.
Almost thought I was the only one with this problem. I did a full wipe twice before loading remix. Worked for a while until I fixed permissions then rebooted. No more lockscreen icons
No idea what I did but now my lock screen is back to normal.
I hope this isn't something that happens all the time with this ROM. that would get super annoying
did you have any issues with previous versions?
I really don't wanna loose my angry birds space save, any other way out of this other than wiping? This is what happened to me on gingerbread too, apparently the flyer just does not like having its battery drained the whole way.
Sent from my HTC PH39100 using xda app-developers app
Cor-master said:
I really don't wanna loose my angry birds space save, any other way out of this other than wiping? This is what happened to me on gingerbread too, apparently the flyer just does not like having its battery drained the whole way.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Bootloop on GB is Lee's ROM problem as i did experianced it onlly on his rom - FlyHigh Rom does not have that problem and been using it now for long time - very satisfied i must admit.
It was mention b4 that do not discharge Flyer completlly. As solution i guess u already did only wipe cach and dalvik and battery stats - leaving out data?
And ofc no TBackup with data on that app?
Well I didn't intentionally let the battery run dead, I was low on charge like below 20% and my son wouldn't stop crying so I was playing music to try and calm him down, and oops! It died. Yeah was on senseless, and I cleared all cache and reinstalled the Rom without whipping and no dice. I can't help but think there has to be something cached some where that is keeping it from booting. Maybe I should logcat it. How do I do that exactly?
Sent from my HTC PH39100 using xda app-developers app
I ran tb a couple weeks ago, whenever it was that ioiwilioi released senseless 4.1. But I played a ton of angry birds space over this weekend (sigh)
Sent from my HTC PH39100 using xda app-developers app
So anyone got some kind of insite? Dalvik cache is boot cache right? You'd think that would do it but it's not. I wonder if I wipe the battery stats if it might help, system might still think that battery is dead.
What its doing exactly is starting up, going to the senseless boot screen, then rebooting, and after the white screen it just goes black and stalls. It's still turned on but its black. I have to shut it off through hboot right now.
Just don't get why running the battery dead would do this, my vivid has terrible battery life and I run it dead all the time. Something has to be cached that won't let it boot. Hmmm.... Maybe an hboot flash?
Sent from my HTC PH39100 using xda app-developers app
Make a nandroid backup then just reinstall the rom and restore data through advanced restore? Will that not work?
To run logcat - Download the Android SDK if you haven't already and open the DDMS.bat executable from /Android-SDK/Tools then plug in your tablet and boot it, then when you see your device in the top left hand box click it then Device > Run logcat
If restoring the data partition doesn't work though you can always extract the app data from the data.img in the nandroid folder
maybe try
fastboot erase cache
Jamielawther said:
Make a nandroid backup then just reinstall the rom and restore data through advanced restore? Will that not work?
To run logcat - Download the Android SDK if you haven't already and open the DDMS.bat executable from /Android-SDK/Tools then plug in your tablet and boot it, then when you see your device in the top left hand box click it then Device > Run logcat
If restoring the data partition doesn't work though you can always extract the app data from the data.img in the nandroid folder
Click to expand...
Click to collapse
Great idea
Sent from my HTC PH39100 using xda app-developers app
Cor-master said:
Great idea
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
I had the same problem last night only my phone haha.
Well not exactly the same, but I corrupted the Framework-res.apk so it wouldn't boot, I forgot to make a backup so my only choice was to go back to the stock rom, which conveniently wouldn't flash because my phone was updated and Huawei haven't released the full package for the update! Aah. Ended up having to manually extract my sms and contacts from the data partition then downgrade the phone, reinstall the software then update it again. Never again in my life. haha.
Woo hoo it worked! Thank god, I didn't feel like setting my flyer all up again. Thanks for the suggestion!
Sent from my HTC PH39100 using xda app-developers app
No problem, Happy it worked haha.. Reinstalling everything is a pain :L
Just wondering why when I flash a new ROM I'l see the default wallpaper for it, then it'll change back to the one I had on the previous ROM. Is this due to not wiping something during recovery?
It happens to me as well. TB just came out with an update that may address our issue.
I've never heard of that
Sent from my ADR6400L using xda premium
Happens because some settings are stored on the sdcard
Sent from my ADR6400L using Tapatalk 2
I always found that if you get ANY old settings from a previous ROM to rewipe and reinstall. I wipe a MINIMUM of 5 times. I have project Team Win and the touch screen makes it easy, i just watch tv and do it.
ang1dust said:
I always found that if you get ANY old settings from a previous ROM to rewipe and reinstall. I wipe a MINIMUM of 5 times. I have project Team Win and the touch screen makes it easy, i just watch tv and do it.
Click to expand...
Click to collapse
Wow! I only flash super wipe once
Sent from my Liquid ICS Thunderbolt
My phone was charging, and one of my alarms went off. I dismissed it, then all of a sudden all the google services started crashing on me. Messages kept popping up, so I rebooted the phone.
After doing that, I'm stuck in the Cyanogen boot up animation. I've tried taking the battery out multiple times and that didnt fix a thing.
Suggestions?
edit: tried wiping the partition cache. didn't fix
Boot to recovery and wipe dalvik and regular cache. If that doesn't work try wiping data.
Sent from my SGH-I777 using xda premium
sdy284 said:
My phone was charging, and one of my alarms went off. I dismissed it, then all of a sudden all the google services started crashing on me. Messages kept popping up, so I rebooted the phone.
After doing that, I'm stuck in the Cyanogen boot up animation. I've tried taking the battery out multiple times and that didnt fix a thing.
Suggestions?
Click to expand...
Click to collapse
Its a boot loop. Search the xda forum about it.
Read this too maybe it helps... http://forum.xda-developers.com/showthread.php?t=1108499
Sent from my GT-N7000 using xda premium
ended up with doing data wipe and installed the latest CM nightly. Thanks for the suggestions!
sdy284 said:
ended up with doing data wipe and installed the latest CM nightly. Thanks for the suggestions!
Click to expand...
Click to collapse
Greatz..
Sent from my GT-N7000 using xda premium
Just like the title says, any chance it's associated with faulty hardware?
Huh
Sent from my SM-N900P using Tapatalk now Free
thekingofmean said:
Just like the title says, any chance it's associated with faulty hardware?
Click to expand...
Click to collapse
Ben getting this as well. Also fc's in Lumen Toolbar.
GAPO said:
Ben getting this as well. Also fc's in Lumen Toolbar.
Click to expand...
Click to collapse
Same here... by any chance did you notice these things start happening after you modded the pen window or the multi window(assuming you may have).Im not sure but I just when into twrp and cleared my cache and delvik and reinstalled the deodexed m15 rom and then cleared cache and delvik again. Now my phone is running good with no more force closes... give it a shot, you dont have to clear the data as long as its the same rom..
aparasg1 said:
Same here... by any chance did you notice these things start happening after you modded the pen window or the multi window(assuming you may have).Im not sure but I just when into twrp and cleared my cache and delvik and reinstalled the deodexed m15 rom and then cleared cache and delvik again. Now my phone is running good with no more force closes... give it a shot, you dont have to clear the data as long as its the same rom..
Click to expand...
Click to collapse
I am all stock. No apps, no nothing. I do plan on routing the phone, but I want to know what it's like out of the box first. the force close issue is apparently an issue across all carriers. specific to that watch on app.
Second that! No modifications, at all. I just wanted to make sure everything was working fine before rooting.
I had the same thing happen to me Watch On would fc like every 5 min. but then I went into Watch On and set it up for comcast and no more fc's from then on.
Sent from my SM-N900P using XDA Premium 4 mobile app
I Cleared data on WatchON, and i havent seen the FC since then.
Yeah, I've found either clear the data on watchon, or go ahead and set it up, and the force closes will stop. Good old Sammy software lol
Sent from my SM-N900P using XDA Premium 4 mobile app
Yuhfhrh said:
Yeah, I've found either clear the data on watchon, or go ahead and set it up, and the force closes will stop. Good old Sammy software lol
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had several watchons and one my magazine fc's.
Will try clearing the data on both, ty.
I get FC's for Apps I don't use Lumen Toolbar & WatchOn, for Apps I didn't know I had until they FC'dMy Magazine
Those are mildly annoying but since I never use the apps I can deal with it pretty well. I'm confident these kinks will be straightened out eventually.
It's when it's an app I use all the time like XDA Premium App FC's everytime I open it I get annoyed!! LOL
I'm expecting these inconvenience are only temporary and things will get optimized hopefully sooner rather then later. :good: