Database Info

Desire S stops at Boot Screen

Hey Guys,
i need your help once again.
So my Desire S showed a lot of errors in the last time. E.g. turned off, couldn't connect to mobile internet. So i decided to factory reset. The phone is rooted and s-off.
I booted into the recovery mode and selected
Wipe Cache
Wipe dalvik cache
wipe battery stats
removed the sd Card
and at last
wipe data/factory reset.
After that i reboot and now the phone stops at bootscreen. I can go into the revolution recovery console again. But don't know what do now..
Would be great, if anyone could help me out.

Soccout said:
Hey Guys,
i need your help once again.
So my Desire S showed a lot of errors in the last time. E.g. turned off, couldn't connect to mobile internet. So i decided to factory reset. The phone is rooted and s-off.
I booted into the recovery mode and selected
Wipe Cache
Wipe dalvik cache
wipe battery stats
removed the sd Card
and at last
wipe data/factory reset.
After that i reboot and now the phone stops at bootscreen. I can go into the revolution recovery console again. But don't know what do now..
Would be great, if anyone could help me out.
Click to expand...
Click to collapse
hey. Your post made me smile. since you have done a full wipe, your phone is nearly empty. there is nothing to boot anymore. You need to install a new ROM.
(do I really need to explain how 2 do?)
Always make sure you know what you're doing, you did wipe your phone without knowing the results
Sent from my Desire S using XDA App

hahahah...
ok now i can and i have to smile again.
Thank yaaaa

[Q] Soft Brick on Flashing CM9 Nightly

Okay, so when I attempt to flash the CM9 nightly (7.2.12 edition) and the Google Apps ICS from CyanogenMod's wiki page I get a soft brick in reboot loop. What happens is three things (it's happened differently each time): First, I get the white SAMSUNG logo. After that, I get an extra-long black screen before a bootscreen. The first time it was an ANDROID logo with moving reflections. The second time it was the CM9 bootscreen. The third time it was simply a white screen. All three times, shortly after the bootscreen began, the phone froze at one frame early into the animation and rebooted. The same thing continually happened. To flash the ROM, I have the newest CWM Recovery for the T-Mobile Galaxy S II installed. From there, I did this (in this order): wipe data/factory reset, Wipe Dalvik Cache, and then Wipe Battery Stats. From there, I flashed the ROM from the internal SD card and then Google Apps for ICS from the internal SD card. After going to reboot from CWM Recovery, I always got that soft brick (three times now). After each soft brick, I have used CWM Recovery to recover a previous instance on the stock ROM.
Any help will be rewarded with imaginary thanks.

wipe cache, format system, format data

http://www.teamchopsticks.org/p/install-guide.html
Here are the steps but for me personally I do 3x cache/3x dalvik and I have installed every update just fine. :good:

Ends said:
wipe cache, format system, format data
Click to expand...
Click to collapse
Okay, worked on second try. Did steps first time, fail. Try again with usual steps, currently in boot screen lacking loop. Thanks!
P.S. UZ7 - Too late hehehe. Thanks anyways, have a cookie.
Sent from my MB860 using xda app-developers app

Okay, wipe cache, format system and data left my device in bootscreen all night. I'm trying the TeamChopsticks method now...
And...
Bootscreen not freezing...
Got soft touch button lights...
Success!

[Q] [P6210]Boot Looping and Corrupt Data Partition

Been running CM10 and CWM 6.0.1.9 for ages with no issues and loving it. Yesterday morning (while on vacation) picked up the tab from charging and it was boot looping. Tried formatting cache and Dalvik cache as 1st attempt to fix and it reboots when trying to format Dalvik cache, regular Cache deletes just fine. Next reflashed CM10, but still boot loops. Started manually formatting partitions and when I get to Data it reboots.
So this sounds like Brick Bug, but shouldn't be since I'm on CM10/CWM6.0.1.9 and wasn't wiping when it occurred.
So questions for the braintrust...
1) Is there anything I can do to fix this while on vacation when the only PC I can access is Windows RT? Basically it needs to be something I can flash with CMW.
2) Assuming #1 isn't possible, my next step was to try flashing a stock rom when I get back home. Make sense or other thoughts?
Thanks,
Todd

try removing your ext sd card and boot it up. See if that helps. If not, I'd Odin the stock ROM

I have experienced this too. My fix was to delete data after reflashing CM10. I tried just clearing cache and dalvik like you did but it continued to boot loop. So I flashed CM10 because I was at school and it was all I have but it was still stuck and so I cleared data at CWM(Didn't flash CM10 again anymore). And yeah, it pretty much deleted everything, but I had a backup at home. It was fixed.

Graffiti Exploit said:
I have experienced this too. My fix was to delete data after reflashing CM10. I tried just clearing cache and dalvik like you did but it continued to boot loop. So I flashed CM10 because I was at school and it was all I have but it was still stuck and so I cleared data at CWM(Didn't flash CM10 again anymore). And yeah, it pretty much deleted everything, but I had a backup at home. It was fixed.
Click to expand...
Click to collapse
Thanks. Formatting data causes a reboot, so I think I'm stuck until I get back home and can use Odin.
Sent from my SCH-I535 using Tapatalk 2

[SOLVED] [Q] [P6210]Boot Looping and Corrupt Data Partition
For the sake of the archives...reflashing stock Honeycome fixed the partition problem and allowed me to re-install CM10.

Infinite booting

So I haven't changed anything on my phone in a little while. Running CM 10.1 (from about a month ago) with no issues.
Today, my phone on my desk at work reboots. Ok, whatevs. Boot animation, CM animation, get to home screen, it says 'Loading Widget' then reboots. It's been doing this for about an hour now.
Any ideas of what to do, short of re-flashing? (which I realize isn't that bad, compared to problems that a lot of people have).
Thanks

If it isn't booting properly, I wouldn't think there's any other option apart from flashing again.
Sent from my Evita

Just dirty flash (wipe cache and Dalvik, then flash) and see if it boots. Or restore a nandroid, if you have it. Either would have taken about 5 minutes.
Of those fail, then full wipe and reflash.

redpoint73 said:
Just dirty flash (wipe cache and Dalvik, then flash) and see if it boots. Or restore a nandroid, if you have it. Either would have taken about 5 minutes.
Of those fail, then full wipe and reflash.
Click to expand...
Click to collapse
Managed to get it to reboot into bootloader, wiped cache and dalvik, and then it worked! (didn't flash anything).
No idea what broke it, but it's working now. Thanks for the responses

Update/dirty flashing Euphoria OS freezes at the Google boot screen

So every time I have dirty flashed Euphoria OS, it has frozen at the Google boot screen. This has forced me to wipe system, install the rom, install gapps, and reconfigure settings. What am I doing wrong that can't I update normally without having to wipe system?

stynatu46 said:
So every time I have dirty flashed Euphoria OS, it has frozen at the Google boot screen. This has forced me to wipe system, install the rom, install gapps, and reconfigure settings. What am I doing wrong that can't I update normally without having to wipe system?
Click to expand...
Click to collapse
What works for me is to wipe cache and davlik before I dirty flash the Rom.
Then after flashing the Rom, SuperSu......... etc wipe cache and davlik again before rebooting.
I have never had any problems dirty flashing Euphoria with this method on both Nexus 5 and Nexus 4.

One more thing. I always make sure to have the latest TWRP installed before I attempt any dirty flash.
Latest version as of this post is TWRP 2.8.5.2

joegestes said:
What works for me is to wipe cache and davlik before I dirty flash the Rom.
Then after flashing the Rom, SuperSu......... etc wipe cache and davlik again before rebooting.
I have never had any problems dirty flashing Euphoria with this method on both Nexus 5 and Nexus 4.
Click to expand...
Click to collapse
I usually do both of those things. I will say that I used ROM Installer to update it, but then dirty flashed with twrp and it still didn't work. Maybe next week I should just straight out flash with TWRP first?

Okay I just did this today and the thing STILL happens. I'd flash the update, wipe dalvik/cache, then reboot system. Then it hangs on Google boot screen for at least 10 minutes. Then I go back to TWRP, wipe system, data, cache, and flash it again and then starts to work, but all my apps are gone. Why can't I just flash the update and have it done with it instead of constantly tinkering around? Am I doing something wrong? is this what a dirty flash is?

I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Are you undervolting?
Ignore. Wrong thread.

Bump

stynatu46 said:
Okay I just did this today and the thing STILL happens. I'd flash the update, wipe dalvik/cache, then reboot system. Then it hangs on Google boot screen for at least 10 minutes. Then I go back to TWRP, wipe system, data, cache, and flash it again and then starts to work, but all my apps are gone. Why can't I just flash the update and have it done with it instead of constantly tinkering around? Am I doing something wrong? is this what a dirty flash is?
Click to expand...
Click to collapse
See if this helps.
If you have many apps, try waiting 10 minutes or longer after wiping cache/davlik before rebooting into android. Or you could try a double wipe.
Apparently, it can take quite a while for cache to clear even if TWRP shows complete.

joegestes said:
See if this helps.
If you have many apps, try waiting 10 minutes or longer after wiping cache/davlik before rebooting into android. Or you could try a double wipe.
Apparently, it can take quite a while for cache to clear even if TWRP shows complete.
Click to expand...
Click to collapse
I've tried this several times yesterday, I think I waited 20 minutes and rebooted again to do the same thing. I also don't have that many apps, I only have 4 rows filled in my app drawer

Okay everyone, I found the problem! All I had to do was uninstall the driver/app for CF.lumen before flashing because it tampered with the /system partition making it unable to boot. I then installed it again after the flash was done.