My phone was just working fine yesterday, but when i just booted today after charging i am having all my processes stopped, what can be the reason? i tried doing a clean wipe again and still does it
i could really use some help..
Could use more info ..
Rooted or not
Custom rom or not
Etc etc....
Sent from my LS670 using XDA App
Does your phone start at all. You can try flashing with the original firmware via the KDZ updater.
Refer to the sticky in this sub-forum...
Thanks guys, but i figured out the problem it must of been the data i was loading from titanium backup after narrowing it down. I believe it had some incompatible data that could not be used on the custom rom therefore the notifications stopped appearing. whew!
Related
I installed the new OTA update earlier today and then did the one click mod.
Then installed CWM Recovery using the guide on this site.
Everything went perfectly the first try. I have ROM Manager installed also.
Browsing works fine.
When trying to download an app it errors out in the info bar and says, "Download was unsuccessful." Sometimes AppBrain will say connection error after opening.
Gmail app gives me a connection error, as does Google Talk.
I've tried clearing the data and cache for all these apps including the Download Manager and rebooting. I'm treading in unfamiliar waters and I'm not sure what to try next. I'd love some help please!
Was so excited that everything went flawlessly and now this...
I waited for the OTA update before rooting just so I'd be as legit as possible. I'm not sure if the root caused the problems or if flashing CWM caused the problems, so I've been trying to find a way to go in reverse and get rid of CWM, but I haven't found anything that's made sense yet. From what I gather I'd have to put the stock Recovery back, and I don't know how to do that. All I have is a ROM Manager backup that I performed after the CWM install.
I'm confused and I hope someone can point me in a safe direction.
Fixed itself. Glad I was patient enough not to try something stupid.
See, I was out of cell service while rooting. Once I got into 3g service this morning everything started working. Even turned airplane mode on and everything works via wireless now.
Haven't a clue why, but I'm thankful nonetheless. : )
My friend and I flashed MUIU onto his Vibrant we were coming from trigger 3.2. Everything was going great it work for about a few hours then a force close kept appearing.
android.process.acore
It will not let him use his keyboard or even get to his messaging app.
We have wipe data cache and davilk and even went to ROM manager and fix permissions.Still didn't work. Should I just ODIN back to stock re-root and find a different ROM or can this be fix's.
Need more information, like what version of MIUI you installed, did you make sure it was the one made for the Vibrant and not a different Galaxy S variant, did you follow all the instructions, did you wait the full 10 mins after first flashing it, did you try restoring all your apps + data with a non-MIUI backup program like Titanium Backup, did you try to restore system apps...
Anyway, try a complete re-install of MIUI. Follow the instructions posted in the MIUI thread to a "T".
I installed the latest build off of the thread in the vibrant forums. And yes I used titanium to do a restore
Sent from my ADR6400L using xda premium
I didn't wait ten minutes. What does that do. There weren't any instructions just wipe and flash.
Sent from my ADR6400L using xda premium
http://forum.xda-developers.com/showthread.php?t=1123922
that is the Rom we flashed
I think you might want to start from scratch and follow this link:
http://forums.miui.us/showthread.php?1189-Installing-MIUI-from-any-Non-MIUI-rom
As a rule you generally can not jump immediately from a non-MIUI rom to MIUI without resetting some parameters. In addition, you also need to be on FROYO bootloader instead of Gingerbread.
Anytime I run into issues with any ROM the first thing to try is a simple re-flash of the ROM. This fixes problems 97% of the time. If all else fails ODIN will take care of any other problems for the other 2% of the time. The other 1% is left open as nothing in life is perfect
I flash all MIUI/CM7 ROMs from a clean stock setup to ensure a good flash.
Sup,
So, I flashed mutliple custom ROM's when I got this device like any other crack-flasher would but I then realised I much prefer it to be running stock with root access until an AOSP ROM comes along.
So I came from Omega 4.0 to stock LE8 in the UK, ever since I've flashed this stock ROM (Which is odexed) I keep getting the message "Sorry, messaging has unfortunately stopped" every time I open the app. I've tried wiping data/cache/dalvik and flashing in Odin again, same issues. I then went back to another custom ROM (HyperGalaxy) then went back to stock to test, still the same.
I have also tested an inverted AOSP 4.0.4 Mms app which worked on Omega, but didn't work on stock (Got the same message)
Data of the Messaging app has been wiped, i've disabled the app, rebooted, enabled again, still the same issues.
I've searched and I found 2 other threads with the same thing, but noone has been helpful enough yet.
It seems like the phone still thinks its running a Deodexed ROM but I need to get it back to full working order since I need to text something.
Any help is appreciated.
Try a factory reset...
Mopral said:
Try a factory reset...
Click to expand...
Click to collapse
Probably didn't make it clear enough, I did that already. 3 times to be exact.
i have the same issue. Need help.
i get this message with multiple apps.
all of them are standard run of the mill things like browser, messages, video player. My phone is only a week old and completely stock
some real bugs in this phone still that need sorting asap. poor effort by samsung really
Same issue here, has anyone found a fix for it yet?
I only encounter this in hyper x rom. So far so good in omega
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
nbhadusia said:
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
Click to expand...
Click to collapse
i got this everytime i clear cache and or wipe data from recovery before flashing new fw's.
so never wipe anything before flashing. if u already wiped, then flash it all over again and it will be all ok
for some reason every rom I flash works great until I Install my apps. Now I use Titanium for my backup and installation of all my apps . Ive ran a scan in my app data and everything is clean. Ive even gone so far as to manually download every app I have from the market one by one . But every time I finally get everything set up and customized the way I want my phone start rebooting every 5 min.it reboots and loads everything fine and once i start using my phone my soft keys stop working but my screens touch works fine I can scroll click on things etc . thats when I know its going to reboot.then it starts every five minutes... now Ive used Cyanogen 9,Mikrom,Viper,Synergy and every one does this. Of course I do a complete wipe of all my data ,cache and partitions etc before I flash Every rom but nothing helps. Ive gone through the process of factory resets and wiping everything at least 10 times with each rom. Upon my days and hours apon hours of research the only suggestions I found was the possibility of a corrupted partition, and to re-install the ruu to completely clean all partitions and set everything back to original then try again . so I did , then I rerooted and and flashed a rom. with the same results. i know its either something Im doing or not doing thats causing this because to have his happen with every rom I flash isnt just the rom. now ..when Im on my stock rom I dont have this issue . so I know Its not a hardware issue. its just when I flash a new rom.
and another thing I noticed is after a couple random reboots it takes a while to connect to my 3g and turn my signal on. in fact sometimes it wont automatically connect until i open my connection in settings. I dont have to click on connect or anything ,all i have to do is basically open my settings or my quick toggles in my navigation bar.
and on a side note. well maybe its a side note maybe might be the actual cause of the problem haha.. when i do a factory reset through recovery everything works fine but i get an error [E: format_volume: make_extf4fs failed on /dev/block/mmcblk1p2] but everything finishes and resets fine as far as I know ... but could this be whats causing these reboots? when i look through my file explorer I find all of the mmcblk files but it seems that this file is the only one not there. can I fix this ?
Evo3d cdma rooted s-off hboot 1.4 revolutionary
Your "side note" might just be your problem. Have you tried a factory reset with another recovery, or maybe redownload and flash the same recovery.
Also, are you restoring data for system apps with titanium backup?
Are you flashing the correct hboot for the Rom you're installing?
Wikd said:
Your "side note" might just be your problem. Have you tried a factory reset with another recovery, or maybe redownload and flash the same recovery.
Also, are you restoring data for system apps with titanium backup?
Are you flashing the correct hboot for the Rom you're installing?
Click to expand...
Click to collapse
I redownloaded and installed the same recovery when I unrooted and rerooted ...is there another recovery you suggest trying ? I used the recovery that came with the revolutionary.zip
No I'm just restoring user apps from the market and 3rd party downloaders (4shared etc.)
And as far as the h.boot. when i was downgrading my h.boot to 1.4 ,after I downgraded my bootloader said 1.4 but I couldn't root through revolutionary . And I found that I needed to downgrade my software from 2.18.... In order for me to be truly at 1.4 hboot and run revolutionary. So I did and it worked perfectly . So now my software is 1.13.651.7. To be honest I wasn't sure if me upgrading to a newer software and running a newer RUU (not an ota ,just higher than 1.13...if it would cause any problems with my root as far as upgrading my h.boot to one that doesn't work with revolutionary as I had that issue with trying to root originaly.
Sent from my PG86100 using xda app-developers app
So I think its something to do with me moving my apps to sd. I only move my user apps and use titanium to do so. Now I have all my apps restored from titanium but didn't move any to sd and I havent had any reboots ...my internal memory is kind of low but its not lagging ... But I can't put any of my games on because they are big on memory . And I'm already low . Does anybody know what's causing my reboots when I move my apps to sd ? Would creating a partition on my sd card fix this ?
Oh and I used a different recovery to do my full wipe ( team wins recovery ) and it didn't give me the error I was getting before . Which is good .but I still got my random reboots .. but I noticed I only get them when I move all my user apps to sd . ( besides my lwps , widgets, system apps and things like setcpu etc.)
Sent from my PG86100 using xda app-developers app
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
r1k1v1 said:
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
Click to expand...
Click to collapse
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
kunal1540 said:
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmm, I don´t remember that the BlackBox 2.0.2 had any Framework...thats why I did a manual installation. But I will try the new version 2.1. Hopefully the problems may have been solved.
boomboomer said:
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Interesting. So I have to apply mods one by one? Or can I add multiple mods because corruption has already been solved?
On a side note, when I boot the phone the red exclamation mark that used to appear has disappeared. Does that means that I somewhat reseted the flash counter to 0?