Im currently running the synergy rom on my evo 4g. After playing around with the settings and what-not, i decided to flash a kernel. Well i flashed one via kernel manager and when my phone rebooted all i got was a continuous message saying that process.android.acore has stopped working and i have to force close it. It repeatedly does this with no end. So once again i rebooted it. Its now stuck in a boot loop, any way to fix this? Also, once fixed will it do the same thing again and again?
please help
If you did a nandroid, just go into recovery and flash that. Or use a different Rom and flash that.
Sent from my PC36100 using XDA Premium App
okay thanks, i got out of the bootloop, but i also had to got back to stock gingerbread, is it possible for me to reflash synergy? Because it seems that its backup is corrupted.
Yes, backup your current rom, then do a full wipe, then flash synergy.
well it all started when i tried rooting my phone, i used the hack ace tool, followed all the instructions and so far through it froze. after so long i decided to pull the plug and take the battery out... when it restarted it all booted up fine and i did the checks to find somehow it had done it
then downloaded cyanogen 7 and put it on with clockwork recovery is it? when it first installed it just boot looped so took out the battery and it started up fine, i had also made a backup of my stock rom which was a orange branded one. i messed around with it for a while before flicking back and forth between the stock and cyanogen when on cyanogen i think i put back clockwork recovery to an older state. after this it wouldnt access the stock rom files so i couldnt revert back to it, assuming it was the clockwork i tried to uninstall it with titanium but it didnt work and had to restart the phone. after that i tried re rooting hoping it would reinstall clockwork like when i first rooted it.
now my phone boots up to the htc screen and i dont know what to do, could anyone give any help?
dl clockwork 5.0.2.0 and flash in recovery.
Sent from my HTC Sensation Z710e using XDA App
solemnbob said:
well it all started when i tried rooting my phone, i used the hack ace tool, followed all the instructions and so far through it froze. after so long i decided to pull the plug and take the battery out... when it restarted it all booted up fine and i did the checks to find somehow it had done it
then downloaded cyanogen 7 and put it on with clockwork recovery is it? when it first installed it just boot looped so took out the battery and it started up fine, i had also made a backup of my stock rom which was a orange branded one. i messed around with it for a while before flicking back and forth between the stock and cyanogen when on cyanogen i think i put back clockwork recovery to an older state. after this it wouldnt access the stock rom files so i couldnt revert back to it, assuming it was the clockwork i tried to uninstall it with titanium but it didnt work and had to restart the phone. after that i tried re rooting hoping it would reinstall clockwork like when i first rooted it.
now my phone boots up to the htc screen and i dont know what to do, could anyone give any help?
Click to expand...
Click to collapse
you have to do a full wipe be for flashing a completely new ROM, if you go in to hboot then go into recovery, you can do the full wipe pm me if you need extra help
If I helped you hit the thanks button!
Hi, this is my first post so please be patient with me
Today I finally decided to update my Nexus from 4.0.4 to 4.1.1 up till now I have been running ARHD.
I decided to flash the new MinCo ROM, everything went smooth, I did a Nandroid backup and used Superwipe Light.
Then flashed the ROM via CW, the phone booted fine and I restored my apps and I thought everything was fine till I checked the system information. There it says I am running 4.1 and no mention of MinCo ??? It shows Francos Kernel though
Did I just out myself as a noob or what went wrong ?
Help is much appreciated
PS. Love XDA :fingers-crossed:
I just looked at the build.prop file of my minco download and it shows 4.1.1. in the ro.build.version.release which would dictate what shows up under version. Maybe you downloaded a different rom?
Sent from my Galaxy Nexus using xda premium
I downloaded the ROM from the official source.
Here are my steps.
1. Downloaded ROM, Gapps
2. Backed up the phone using CW
3. Wiped the phone using Super Wipe Lite Nexus
4. Flashed ROM using CW
5. Flashed Gapps using CW
6. Rebooted the phone
7. Restored Apps via Titanium Backup
Should I have done a full wipe? I didn't want to loose all my stuff.
Thanks for the help by the way.
Whenever you are flashing a new base you want to do a full wipe. I'm not sure what happened with your download and why it says 4.1 instead of 4.1.1. Probably not worth losing sleep over though.
Sent from my Galaxy Nexus using Tapatalk 2
Ok seems like I have to wipe the whole thing then.
Will post the results later.
Thanks.
So I did a full wipe and flashed the ROM again. This time the System UI kept crashing.
This kept happening over and over again. I wiped and re installed 4-5 times with the same result.
Then I downloaded the the ROM and the bootloader again and flashed it again. This time it worked and it stopped crashing.
The ROM then showed 4.1.1.
I then flashed Gapps and MinCo+ Stock Mod and after reboot it was showing Android 4.1 again!
I really have no idea what is going on ???
Using UpdateMe on my GS3, I downloaded Free GS3 3.0 to my phone (I was running the previous version). Went into TWRP, installed it (backed up and wiped all caches and system before hand). Rebooted, and it worked fine. Then, I went back into TWRP to install a mod for the batter percentage indicator that I had previously used on the old version of Free GS3. Installed it, worked without a hitch. Except, now my phone won't boot. It flashes the samsung logo then the galaxy s3 logo, followed by blank screen. That's it. I think the problem is that my version of TWRP isn't the latest version (I couldnt' find out how to update it anywhere). Now, I have no idea what to do. Somebody please help, I just want to use my phone again.
Go back into recovery wipe cache and dalvik and reflash the rom. Do not use the mod again.
Sent from the future via Tapatalk 4
The problem is the mod. The MD4 update changed a lot of things, you're just gonna have to wait for Clark44 to update the battery mod.
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
captican said:
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
Click to expand...
Click to collapse
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
I had the same problem since 4.3 came out. It has to do with partition tables... What i've done to correct the problem:
- Odin back to stock
- Format entire phone. (Complete wipe) + Dalvik and cache
- Odin stock with root
- Replaced TWRP recovery for CWM
- Flashed 4.3 ROM and VOILA
- I have tried every 4.3 rom ever since with no problems
Don't (Complete wipe) with Twrp recovery, it seems to mess up the partitions.
Hope this works for you
Cheers
danielhep said:
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
Click to expand...
Click to collapse
It loaded the first time and then rebooted, freezing on the kernel screen. I could get into recovery, and restore a previous ROM but it would hang up on 4.3. I described the steps I had taken when someone suggested reformatting data. I tried again and it is working now.
The method described in the other post may also solve your problem. I say that because I cannot update twrp to 2.6.1, at least via goo manager. I have not tried using Odin to update (yet).
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
I managed to load a stock rom back to the phone but again, it hung on the SAMSUNG screen. Took it to "a guy" and he did a
key sequence and got it to boot. Woulnd't tell me what it was........
ANy one know???
Apocalypse487 said:
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This happened to me after I flashed back but formatting data got it to work (but I have had more problems with apps not installing properly but I learned how to deal with that...still cannot update TWRP via goo manager; waiting on trying it with Odin).