The title pretty much says it. I've been trying to flash Axis since last night and once it hits 100% I hit the next button..it vibrates, then completely freezes. I wiped dalvik, system, and full data each time i've tried it. Didnt know what to do so I tried to restore it..and then it gets stuck on the LiquidSmooth boot screen. I'm a noob at this rom stuff so I dont really know what else to do and its stressing me out. please help!
Aroma can be a bit finicky. I have had to battery pull several times during an aroma install. Just be persistent is about all I can suggest. I haven't heard of ant tricks that helps.
Sent from my GT-P5113 using xda premium
Related
I am having this freaking problem after upgrading to 3.33 firmware and installing Elegancia 2.7. My sensation keeps getting this error "Android.process.acore has stopped" and after this my touch screen keeps on freezing.
I am unable to use touchscreen.
After restarting my phone, i still keep on getting same error :crying:
I have pull out battery from the set, kept it off for almost 6 hours and still got same error after rebooting.
Is there any solution for this issue ?
Even if i reboot to 4ext recovery, i am unable to use touchscreen.
Does the touch screen work in recovery?
It happened to me a couple of months ago, touch screen didn't work anywhere with that same error.
I thought it was the digitizer at first and sent it to a lab.
Switching it didn't help and it turned out to be the board which switching to a new one fixed it.
I don't know if we have the same problem but thought I'd let you know.
Sent from my HTC Sensation using Tapatalk 2
Badflash. Check md5 and then reflash if md5 matches. Happened to me once. Go into recovery, do wipe data/factory reset, then format partition on all except sd card. Fullwipe (you can get it from coredroid) then run superwipe. Then reflash. I always do it that way to ensure i dont get any leftover files/bad flashes.
I looked this up and it said its related to apps that use the same sync function. There solution was to close all tabs in manage applications, clear data and cash in contacts, then clear data cash in contact storage. But I don't know how you can try that if touch screen is not working. I wish I could be of more help. I do. Hope you get it working and figured out! Best wishes .
Sent from my HTC Sensation 4G using xda premium
my touchscreen is just not working. even in recovery. anyways managed to re-install stock 3.33 rom but still then touchscreen isn't responding
Anyways i dont know why the hell has it started working again after i tried to install 3.32 it rebooted and i was able to work. Lets hope it continues to work. But anybody... please let me know what had actually gone wrong and how to avoid it in future...
Running 3.33 stock rom now
My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Did you have any undervolt settings applied?
The phone is not underclocked, it is not overclocked. It was rooted, I unrooted it. its currently unrooted absolutely factory stock and still doing that. What can I do to fix this?
warranty is over as of 3 months ago
Forgot to mention the most important thing!!!
When I am on the phone with someone, it works perfectly forever, as soon as i hang up, it ends the call. this key thing might help someone find the solution!!
himalaya333 said:
My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Click to expand...
Click to collapse
Don't panic just yet... I doubt your phone is dead.
You say you've "wiped data and cache". Are you also making sure to wipe /system and Dalvik Cache?
Try flashing Zeus again.
Boot to CWM, Wipe EVERYTHING (/data, /cache, /system, Dalvik Cache). (Alternatively, get "Clean Wipe" from Qkster's Scripts and flash with CWM to easily wipe everything.)
Flash Zeus and go.
If you're still having problems, perhaps try a different rom?
okay, I read everything you guys wrote.. This is where I am, I am open to suggestions
I am on the stock rom and unrooted. Phone still boot loops. What should I do now? Step by step instructions would be great. Im unrooted, so should i root again? even though im having this problem?
bump! really need help with this guys!
Have you tried going back to stock?
If it keeps looping while on download mode then I would say you are dealing with a hardware issue.
Sent from my sweet & buttery Infuse
It just came to me that it doesn't loop in download mode. It does loop in clockwork, I flashed the stock kernel using ODIN and went completely stock through ODIN.
How do i fix this? i'm pissed that i had it for a year and three months and right after the warranty ended, the phone stopped working! Samsung never again unless this issue is fixed
I'm a newbie to flashing, so take it with a grain of salt. At least two more things seem worth trying to me:
1 - Try factory data reset (assuming you already tried the wipe Davlick and wipe cache). I'm not positive what this does, but I think you may lose some of your data if it's not backed up.
2 - If that doesn't work, try qkster's Heimdall UCLB3 stock (since you can get into download mode...shouldn't be a problem). This is complete back to stock so should be able to clear any software problem I'd think. I know you may think it's redundant since you are already back to stock, but worth trying imo since some things just take more than one try, and you may have had a bad flash the first time around.
Why zeus? try latest ones with jelly bean
Hey,
Try other roms based out of jelly bean. They are pretty stable. CM10 with 09/14 build is the latest
Here are the standard steps if you have CWM enabled.
1. Factory re-set (only when switching between different roms).
2. Cache partition wipe
3. Dalvik Cache wipe
4. Install the zip file
5. Re-start and wait until it re-starts. Initially it will take some time.
I have tried various roms and versions as well. Best would be the CM10 Jelly bean.
Thanks Kran.
Well it all started when I downloaded Boot Animations ★ root. I tried to install a bootanimation and it said failed. Thinking nothing happened , I had to restart my phone. Now my phone bootloops with an android bootanimation. I tried factory reset and that didnt work. I tried adb sideload and it would just say installation aborted. I have the system backed up on my laptop. Help... please?
Well.. Power +Up Button =recovery but Power+down button= testing (its in chinese)... how do I get to bootloader?
Go to android recovery,
Format system, wipe cache, go to advanced, wipe Dalvik cache, reboot.
If that doesn't help, try slamming your phone through a piece of China brick, see if it helps.
Sent from my LG-E730 using xda app-developers app
terris98 said:
Go to android recovery,
Format system, wipe cache, go to advanced, wipe Dalvik cache, reboot.
If that doesn't help, try slamming your phone through a piece of China brick, see if it helps.
Sent from my LG-E730 using xda app-developers app
Click to expand...
Click to collapse
LMAO Well.. The only way to get my phone back working is through Preloader but it connects and disconnects. I tried different cords and computers but nothing worked. It's really a big mistake I did. I should have installed a custom recovery and did a backup right after I rooted my phone.. Anyways.. I'm getting a different phone soon.
Chinaphone wont boot
Thanks to xda for all the help and I hope you can help me with this problem. My Chinaphone won't start, it gets to the android boot animation and sound but then nothing. The led comes on from the time the battery is inserted which is unusual.
I have the phone for about one year now, model:M-9125 (imitation of htc hd7) with dual Sim+TV and everything else that come with Android 2.3.4 gingerbread. The phones is rooted (with the MT6573 driver- and i use link2sd so everything except un-updated system apps are on the second partition. I have modified the rom with link2sd removing unwanted system apps like email, flashlight, music, browser and replaced them gmail/outlook, tinyflashlight, winamp, opera mini respectively. Tinyflashlight and opera were made system apps. I also use the go launcher which I made a system app after which I was left with only 1.5 mb of rom, (ram about 300 mb and both sd card partitions have over a gb free) but the phone worked fine. Then a few days ago the phone wont start. I thought the battery was dead but it could not charge. I tried both batteries (came with two, one of which was already drained) and they would not charge. So a friend took them to charge with a universal claiming that I Let the batteries drain out completely that's why. However I have the batteries I think they are charged cause at least now the led comes as soon as the battery pins contact those of the phone. The phone turns on, boot animation, sounds but then nothing. So I just wanted to know if its the batteries or if its the phone given that I have over-customized it. And how do I fix it.Cannot afford a new phone right now.
I know I am a noob and read your rules but I still really wants sure where to post this. feel free to move it if necessarily. thank you.
Hello Peeps,
I was trying to flash a rom yesterday and had something strange happen to me.
The rom featured Aroma installer and I had flashed this particular rom roughly 5 or 6 times with no issues.
Yesterday, I did a full wipe and tried to do a new install of this rom.
There was an option screen in aroma that allows you to choose your own mods and features or use the developers defaults.
I was on this screen trying to choose the developers defaults option and Aroma simply froze up.
It would not let me choose with version to flash.
The touch screen wouldnt respond and I didnt know what to do.
I searched google and found nothing.
I decided to do a battery pull.
I know that a batter pull during a flash is something we should never do as it will brick our phones.
In this case, as the flash had not actually started yet I decided to try it.
I pulled battery and booted into recovery and was able to restore a nanroid.
I am just curious if anyone else has had this issue?
How dangerous was it to pull my battery?
Could I have bricked my phone?
Phone has been working just fine, I am just wondering if there is another way to resolve an issue with Aroma like that?
Thank you,
I never had that problem as for the pull battery it is fine as long as you're not flashing.
I was installing a ROM on my sister's s3 when the aroma installer completely froze. I pulled the battery and it boot looped but wouldn't go into recovery until around the 10th or so time (vol up + home + power). Flashed it again and it worked fine...really weird.
As for bricking your phone I agree with above poster, it should be fine if you aren't flashing anything.
Sent from my SCH-I535 using Tapatalk 2
I've had this same issue happen a couple of times. It usually happens when I try to install the Jelly 'Beans' rom...sometimes it will work, sometimes it will freeze. I usually have to do a battery pull and recovery will come right back up. I've noticed this seems to happen the most when the phone has grown hot...so maybe it has something to do with RAM, etc.
I'm not sure how best to describe this which has made it difficult to search the forums for someone with a similar issue.
I was using CleanROM 5.1 on my rooted Verizon Samsung SIII for months. Just yesterday it decided to stop responding so I pulled the battery and turned it back on. The screen it showed me after booting was that of my background with the apps button in the middle and the clock and battery in the top right. My menu and back button were lite but I couldn't do anything.
I flashed the CleanROM 5.6 thinking something might have become corrupted but the same issue happens when I boot.
Any help would be greatly appreciated!
** Update **
I'm doing a factory reset as well. Hopefully that will do the trick. It actually it booting up and doing something now
For starters just try wiping cache, and dalvik. Are you doing clean flashes every time?
Sent from my SCH-I535 using xda premium