Database Info

New Rom=Long Reboot?

(Noob) Haven't ever tried installing new roms before and giving it a new shot using clockwork recovery mod.
My question is this, I've tried putting two new roms in and both cases, the phone reboots and seems to be stuck on the "htc incredible" with white background boot theme. It just hangs there, both time I waited about 10 minutes. Is this normal, should I wait longer, or just do a recovery and retry?
Thanks

What roms?
Sent from my Incredible using XDA App

jdkoreclipse said:
What roms?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
The sense red and sense froyo with apps aligned from Jonnybueno. I just did a recovery and it booted up back to normal, trying the cyanogen 6 build now

bjw1979 said:
The sense red and sense froyo with apps aligned from Jonnybueno. I just did a recovery and it booted up back to normal, trying the cyanogen 6 build now
Click to expand...
Click to collapse
Maybe try unrevoked3 again. If that doesnt work, unroot using the ruu and reroot and reflash with unrevoked3. Remember if you are um rooting, backup all data contacts and apps.
Sent from my Incredible using XDA App

Yes, a new ROM can take several minutes to boot the first time. As far as how long... I don't know that I have ever sucessfully waited more than 15 or 20 minutes for first boot.
Take preceding advice with a grain of salt, I have not flashed a new ROM on my Incredible yet, I only have ROM experience with my Magic.

[Q] Adrynalyne Kernel Stuck

I flash a couple of roms and kernels but when i flashed adrynalyne kernel, my phone was stuck at the htc screen...i tried it 3wice already and nothing...any suggestions

How long did you wait? It takes awhile.
Sent from my ADR6400L using XDA App

Less than 2min...wait more than that???

Boot into recovery and flash the rom again.
Sent from my ADR6400L using XDA Premium App

Yeah first time it can take 2 min. or longer. A few times I was just about to pull the battery and then it booted.
Sent from my ADR6400L using XDA App

first time booting a new rom always takes significantly longer for me
Try again you should be fine.

Tried flashing it via kernel manager? The ui is nothing to look at but it seems to work pretty well and is fast.

some of his kernels do not work on my phone either. my cpu is very finicky. I think in the end number c worked for me.
this is not a signature I type it in every time maybe sent from my phone or my computer

Mine also took about 10 min at the first boot
I don't know why, but mine also took about 10 min or more at the first boot.
I suppose they have some initializing scripts on the first run.
Wait few more minute

[Q] Running Slow....

I have had Hienz 57 running for about a month now and it seems to be running really slow. Even while doing the smallest things like typing it will be a couple letters behind. Anyone have any ideas. I have cleaned all the app caches and deleted what I don't use any more but still slow.

1fast72 said:
I have had Hienz 57 running for about a month now and it seems to be running really slow. Even while doing the smallest things like typing it will be a couple letters behind. Anyone have any ideas. I have cleaned all the app caches and deleted what I don't use any more but still slow.
Click to expand...
Click to collapse
Rebooting usually fixes this for me
Sent from my SCH-I500 using XDA App

That sometimes works but I was kinda looking for a more permenent solution. Would wiping the cache or dalvik possibly help?

1fast72 said:
That sometimes works but I was kinda looking for a more permenent solution. Would wiping the cache or dalvik possibly help?
Click to expand...
Click to collapse
you got voodoo enabled. what are your settings like...maybe you just need to re-odin then reflash the ROM and stuff...sometimes phones just need a fresh start

^Agreed. I can't count the times if done that. Mostly after I have went through five or so kernels but none the less it can't hurt and I haven't done it yet and regretted it.
Tap-a-Talked

There's a formatting utility here:
http://forum.xda-developers.com/showthread.php?t=1090127
I used the ext4 (voodoo) version and it worked great. I know they mean nothing, but I was getting 1500-1600 Quadrant scores before I ran it (still with voodoo), and I'm getting 1700-1800 now.
Sent from my Kangbanged Mesmerize
edit: This does wipe everything, so run your backups beforehand if you decide to try it.

That's the one I used today and it is freakin sweet. An excellant tool.
Tap-a-Talked

Yes I have voodoo enabled. I have not changed any voltage settings yet. When you say to re-odin are you saying to flash back to stock ec10 and then reflash the hienz 57? Still learning the terminology. I did go from the voodoo kernel to hienz without a fresh start. I also didn't wipe the data but for the first few weeks it ran awesome. I have also had a few half reboots. Like it would go to the android logo but not all the way to the samsung logo

defenestrado said:
There's a formatting utility here:
http://forum.xda-developers.com/showthread.php?t=1090127
I used the ext4 (voodoo) version and it worked great. I know they mean nothing, but I was getting 1500-1600 Quadrant scores before I ran it (still with voodoo), and I'm getting 1700-1800 now.
Sent from my Kangbanged Mesmerize
edit: This does wipe everything, so run your backups beforehand if you decide to try it.
Click to expand...
Click to collapse
+1 works great

Thinking of trying this but did you have the cwm 3 or just the 2.5.x? Also can I just flash the H57 zip and be back up and working?

Ran the utility and worked great. Have more memory too so the tons have been staying behind a little. Phone is much smoother and faster.
Sent from my SCH-I500 using XDA App

Normally i have zero issues with lag, however as of late I've had some slight issues with lag as well, even with lagfix enabled - to remedy it I simply enabled the 1120 overclock step and it's been fast ever since (and not too bad on the battery)

I just happened to be browsing the Sd card since I just dl the newest H57 and noticed that after formatting I dont have the android secure folder. Is this a problem or will it create a new one?
Sent from my SCH-I500 using XDA App

Replaced battery now FC galore.

When i picked up my charge i also got the desk cradle with the extra battery. Yesterday at work i was listening to music and drained the battery pretty quickly so i swapped in the extra battery. Once i rebooted i started getting a bunch of FC's. I'm getting ones for Google Services Framework, messaging, android.processes.acore and one or two others i can't remember. I reflashed GC and still get the errors. Anyone have any idea why this would happen after swapping batteries and how to fix this?
Sent from my SCH-I510 using XDA App

It just happens sometimes. Ill have to do this once every 3 months or so. Hope you made a backup...If you have the EXT4 formatter saved then just mount all in CWM, wipe all user data, dalvik, cache, etc. Then run EXT4 formatter, then flash GC. If you don't have it, you have to restock with the EE4 Odin and PIT, then reflash GC.
Sent from my Droid Charge running GummyFroyo 1.9.1

Happened to me a week or so ago, huge pain because I hadn't backed up in a while but it took me about a day or two to get all my apps back in order. In all honesty though it was one of the most annoying things that could happen. Had to redownload a ton of my apps and all the apps I had backed up were outdated(like ColorNote, I lost like 4 notes because it was an old backup). Happened totally out of the blue, I just rebooted the phone because apps weren't installing and I got spammed with FCloses. Not even a factory reset/cache/Dalvcache worked I had to flash the .pit/ee4factory.md5 to get my phone working again. PAIN IN TEH ASH.

Well son of a batch of cookies. That was my last resort but i suppose i will give that a shot this evening and report back to ya.
Sent from my SCH-I510 using XDA App

I finally got around to restoring my phone using the EE4 ODIN. I had no idea it was going to take over an hour to do, lol. Anyway, the flash completed and passed so I unplugged the USB cable, pulled the battery, but now I can't get the phone to turn on. Is there something else that I screwed up?

Lockett said:
I finally got around to restoring my phone using the EE4 ODIN. I had no idea it was going to take over an hour to do, lol. Anyway, the flash completed and passed so I unplugged the USB cable, pulled the battery, but now I can't get the phone to turn on. Is there something else that I screwed up?
Click to expand...
Click to collapse
It should have not taken an hour. If you flashed without the battery try flashing again with the battery in.
Also make sure you are using the PDA button.. not phone. Flash will show pass if you use phone but it will not boot.
Sent from my SCH-I510 using XDA App

Yep that was the mistake i made. I was in a rush to get my phone back up and running before i went to sleep that i accidently used the phone option. I reflashed using PDA and all is well. Now i just have to reroot.
Sent from my SCH-I510 using XDA App

I dont know if you were rooted and on a rom already but for future ref., when this happened to me I just went into CWR, fixed permissions, wiped cache and dalvik, rebooted and bam the FClosing stopped. my wifes phone on the other hand I had to just go into CWR and flash the rom over again and it cleared the problem rather than going through ODIN.

jrock7885 said:
I dont know if you were rooted and on a rom already but for future ref., when this happened to me I just went into CWR, fixed permissions, wiped cache and dalvik, rebooted and bam the FClosing stopped. my wifes phone on the other hand I had to just go into CWR and flash the rom over again and it cleared the problem rather than going through ODIN.
Click to expand...
Click to collapse
I was rooted and running GC 1.9.1. I went into CWR and tried wiping just the cache and dalvik as well as flashing the rom again and I couldn't get the FC's to stop. Thanks for the info, I'll keep this in mind next time this happens.

I was on GC 1.9 when my mega galore of FC's started happening too, my end result was a replacement phone from Verizon... I really don't know what happened or why. It just randomly happened under normal use.

Wow, that kinda sucks. They didn't say anything about the phone being rooted? They gave me hell for trading my rooted D2G for my charge.

Lockett said:
Wow, that kinda sucks. They didn't say anything about the phone being rooted? They gave me hell for trading my rooted D2G for my charge.
Click to expand...
Click to collapse
No because I flashed a bone stock ED1 with no root and nothing at all on the phone, I even had a blank 2GB SD Card in it.

Same happened to me. Yesterday I just clicked on camera and got a force close, then froze. Pulled battery, then everything was force closing. Only thing that would function was browser. Flashed everything, wiped data, you name it. Nothing has worked for me.

Happy! said:
Same happened to me. Yesterday I just clicked on camera and got a force close, then froze. Pulled battery, then everything was force closing. Only thing that would function was browser. Flashed everything, wiped data, you name it. Nothing has worked for me.
Click to expand...
Click to collapse
Just do what I said.
Sent from my Droid Charge running GummyFroyo 1.9.1

Did the rom you were running have journaling turned off by default?? If so, any improper shutdown will result in data corruption.
Sent from my SPH-D700 using xda premium

And I second clearing the cache and dalvik.
Sent from my SPH-D700 using xda premium

nismology said:
And I second clearing the cache and dalvik.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
When I had this problem clearing cache and dalvik didn't help at all.
Sent from my Droid Charge running GummyFroyo 1.9.1

kvswim said:
When I had this problem clearing cache and dalvik didn't help at all.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
It depends on the level of data corruption I suppose. As an aside, roms should really be released with journaling enable or at least have that option. The slight speed increase is not worth the hassle IMO.
Sent from my SPH-D700 using xda premium

When it happened to me one the first things I tried was wiping cache and nothing worked. If you follow kv's advice and that doesn't work then the only other method would be to odin back to stock and start fresh. I did have one fc for android.processes.acore but I can't remember what I did to cause or replicate it. The only thing I'm having trouble with now that I rerooted the phone is that I cannot get back into CWR. I flashed the latest version and was able to get in to flash gc and everything else but now when I try to get in it locks up on the samsung logo.
EDIT: I wasn't able to get past the Samsung logo no matter what I tried. I ended up having to odin back and start fresh....again.
Sent from my SCH-I510 using XDA App

nismology said:
It depends on the level of data corruption I suppose. As an aside, roms should really be released with journaling enable or at least have that option. The slight speed increase is not worth the hassle IMO.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Is there any way to re-enable it?

[Q] Stuck at black screen after boot...

Hello,
Thank you for taking the time to read this. I'm currently on Beans' Build five (love it of course). About an hour ago, I went to switch out batteries, and when I turned my S3 back on, I got the normal Pink Samsung stuff exclusive to Beans' rom, then, instead of going to the boot animation of falling jars of Jelly Beans, the screen turns completely black, and vibrates very softly and quickly every seven seconds. I can boot into Clockwork Recovery. I tried wiping cache, dalvik cache, factory reset (3 times), unsuccessful in each attempt. I have no idea what to try next, and was hoping to avoid the whole replacement route. Also, not sure if this is relevant or not, but prior to my latest boot, I installed some automatic Google Wallet Installer app, ran it, and didn't get past the emulator page of the process. I assume it failed. Wasn't too sure if that could have tweaked something with the system, or if it was just a coincidence. Any and all help is appreciated.
Thank you,
Matt

You should reflash your ROM or restore a backup.
Sent from my SCH-I535

kintwofan said:
You should reflash your ROM or restore a backup.
Sent from my SCH-I535
Click to expand...
Click to collapse
That was my initial plan, until I navigated to my extSD and immediately remembered that I had just deleted my backups AND the actual rom itself. So I had to download it on the world's SLOWEST computer in the history of mankind. Anyways, after flashing it, I read your response literally at the exact same time as the jars of JBs began to fall. Thankfully, because I didn't want to lose the 32gigs of internal memory worth of music/videos. Thank you for your quick response, you were right.
Matt

Glad you got it! Bet you keep a backup at all time now.
Sent from my SCH-I535

kintwofan said:
Glad you got it! Bet you keep a backup at all time now.
Sent from my SCH-I535
Click to expand...
Click to collapse
DEFINITELY! That extra space of memory seems less important now. Thanks again.
Sent from my SCH-I535 using Tapatalk 2