Develop Bugs

Wiped Dalvik Cache, Now stuck in boot

Can anyone help me?
I am running SkyRaider 3.1 with the Hydra SSUV kernel.
I ran ClockworkMod through Rom Manager, selected wipe cache, then wiped dalvik cache and the phone is now stuck in the boot sequence at the Droid eye screen. It's now been about 20 minutes, so I assume it has had enough time to rebuild itself.
Any ideas? I have a nandroid backup from a few days ago, but I would like to avoid doing that.

joehero said:
Can anyone help me?
I am running SkyRaider 3.1 with the Hydra SSUV kernel.
I ran ClockworkMod through Rom Manager, selected wipe cache, then wiped dalvik cache and the phone is now stuck in the boot sequence at the Droid eye screen. It's now been about 20 minutes, so I assume it has had enough time to rebuild itself.
Any ideas? I have a nandroid backup from a few days ago, but I would like to avoid doing that.
Click to expand...
Click to collapse
It should have completed by now, I hate to say pull the battery.... but if you are really stuck.
go back to recovery wipe Dalvik and Cache Partition, try booting again, it will take quite a bit of time to reboot this time.
If that does not work use your nandroid backup.
BTW always nandroid before making any changes to your phone that way you lose nothing, even if you think they are quick, easy or minor. Hardware has a way of keeping us humble.

Thanks for the recommendation. I had pulled the battery and figured I would try booting to recovery and wiping the cache again to see what happened. Did that and booted in a minute.
Currently doing a new Nandroid backup...

Help N stuff!

I rooted my Epic 4g touch.
I cant get it to go past the start up screen.
I can however put the phone into dowload mode.
I can also get to clockwork.
Ive even reflashed with odin but nothing i do will go past the boot screen.
the boot screen changes everytime i flash but never progresses past this.
please assist, i had a ton of errors with starburst rom, but i watched the video and the comments said to format and that is what caused this issue.
please help in anyway you can.
i really need my phone back up its my only point of contact

If you are using CWR, try erasing your /system before flashing the new rom. It's under the mount option (I think). Also clear the cache and the Delvik Cache too.
Otherwise go get the stock image, flash that with Odin and start over.
That's about all I know, hope it helps.

Thanks for trying...
Ive tried erasing the system clearing the cache and the delvik cache...
ive also tried flashing with odin with the stock image all it does is changes the boot screen but it stays suck there...
at least you tried to help thanks man

[Q] [HELP] Borked up phone!

Ouch. Been running various ROMs and various kernels. Had a ROM installed with imosyons exp2 kernel and touch recovery. Was trying out 1.42GHz. All of a sudden phone spontaneously rebooted. Hung repeatedly on Google screen. OK, no problem. Will wipe cache and dalvik cache and reinstall kernel. Hung on the dalvik cache wipe. OK, will skip the wipe and just load kernel. Opps, hung looking for .zip files. Opps, will reload recovery. Still hanging everywhere.
Used Galaxy Toolkit to reload stock images. It did do 1 bootloop, but then acted normally.
Reloaded everything. Left 1.42 alone! Worked all day and then I installed ROM Manager to make a nandroid backup. It wanted to install CWR so I let it. Upon a reboot it went into bootloops. Now I cannot do a factory restore (all my data is there upon a reboot). Tried the ODIN solution but it's still not clearing data. Apparently no PIT available to reparition? Shoot, what do I do!

[Resolved!] Update to 4.3+ ROM freezes on boot

I am on Liquid Smooth 2.9 (4.2.2) and using TWRP 2.6.3.0 phone is an i747m 32GB model. I tried upgrading to LS2.10 which is 4.3. Installed ROM OK but after first reboot phone froze on the Samsung logo. It wouldn't even get the the boot animation. I tried several methods of flashing as requested but to no avail. Today I tried the latest nightly of Carbon ROM which is 4.3.1 and encountered the same issue. I tried rebooting after flashing GAPPS and it just froze at the Samsung logo without going to boot animation. I did flash the latest bootloader in between while trying to diagnose as well.
Does anyone have any suggestions or similar situations? I would really like to upgrade to a 4.3 ROM but seem to have hit a hurdle...
Thanks in advance.

So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.

Galloway said:
So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.
Click to expand...
Click to collapse
When you flash the ROM, are you wiping dalvik cache as well as wiping all data/ factory reset and cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?

gluk1470 said:
I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?
Click to expand...
Click to collapse
At least it's not just me....unfortunately I don't have much time lately so I haven't been able to try experimenting. I noticed you are using TWRP as well....I may try flashing CWM if I get a sec and see if the results are the same. Also if the same happens and I have enough time I'll try and grab a logcat. If I don't have time it's called wipe and restore from a backup.
And yes Dalvik + cache are always wiped anytime I flash anything as a minimum. With this issue I have been doing an entire internal format. I have tried just wiping cache and Dalvik when it occurs as well as fixing permissions but still doesn't boot. Wish I had more time latrely to narrow it down.

Yes, its work. I flashed stock ROM 4.1.2, then root device, flash CWM 6.0.2.3 (no touch) and flash Quantum 2.20. But I think, problem not in recovery or device. Problem in Titanium Backup, I used it to restore some system apps and accounts, now I restored only call log and SMS.

I have now tried flashing with TWRP and pulling SD card before initial boot to eliminate an SD card issue. I've set to not install backups from Google as precaution. Still the same result of frozen at Samsung logo.
I've then flashed the newest CWM non-touch and wiped all with flash. The result was even worse. This time it wouldn't even boot the first time for initial setup it just hangs at the Samsung logo.
This is starting to get frustrating just due to the fact of me not having a huge amount of time to dedicate to isolating the issue. I need to get a logcat but I am not usually near a computer to ADB to it when it is not booting. If I have time this weekend I'll try and get a logcat to post up.

CWM broke it real good! LOL! Anyways I couldn't even get my backups to restore. I tried taking a logcat while it was frozen but was not able to get an ADB connection in order to even get a logcat. I managed to push a fresh copy of Liquidsmooth 2.9 to the SD card and install it. Then flashed TWRP back. Then restored my back up. What a tedious task to still be scratching my head as to why multiple 4.3 ROM's won't boot on the second boot after flashing...

It's been resolved! As per an awesome person on Carbon's G+ thread don't flash the ROM from external SD .Only flash it from internal storage!

[Q] "gapps stopped" loop after CWM restore

Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );

if you can still get to recovery, download latest gapps and flash that

Did you factory reset before or after you restored your back up?

Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:

Try to factory reset again

vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!

I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.