Only recently, from today i have been experiencing stuck on boot screen problems with a rom, i wiped cache and dalvik, even changed kernel but still stuck, so i wiped data and flashed a new rom. I wiped everything, the first boot worked, i installed my apps then i wanted to flash a file so i rebooted, however my device got stuck on boot screen again. It is always stuck on the Galaxy s 2 screen and every rom i use, if i reboot it will get stuck!!! Im not sure what the problem is and im getting very nervous now. Can somebody please help me or at least tell me what is happening? Thank you
I was using the latest NeatRom Lite when the first bootscreen happened, so i switched to Wanam and now same problem, i even tried booting without my sd card, but still cant boot!
Why on earth did you title your topics as nothing more then "Please Help!!!!" ??
Topic titles are supposed to be descriptive (NOT GENERIC) so that people browsing forum can see what topics are about. Your likely to get less page views and hence less likely to get help if you dont use common sense and title topics correctly.
Try a kernel cleaning script.
Try a rom cleaning script.
Try re-stocking via odin.
Related
Hello I'm new to all of this so I figured I would ask here, I installed clockwork mod and then TnT lite 4.40, even found the install for the Wi-fi bug.
But now Im stuck in a boot-loop but i can boot into the clockwork recovery.
From here should i try to reinstall TnT 4.40 from an SD card or is there a way to flash it to go back to original settings from and SD card?
Sorry if this seems like a noob question but i bought this just today after reading all the cool things you guys have been doing with it and it seems i screwed it up.
You could try re-flashing... you could try a cache and/or data wipe... if none of that works you could try repartitioning... if that fails nvflash...
Would you like links to all of those?
Seriously, It would help if you told us what you've tried and what happened. There are different kinds of bootloops. If it's looping between the birds and gtablet screens you'll most likely need a data wipe and reflash (maybe even repartition and nvflash). If it's looping in the boot animation a data wipe will likely clear it.
Boot into CWM and try the cache/data wipe. If that doesn't work let us know a little more about your situation and we can get you on the right track.
Best of luck.
Well I booted into clockwork and tried a cache and data wipe rebooted and it keeps looping from the birds to the G-tablet logo and thats all it does.
I can turn it off and then go back into clockwork but thats where i'm sorta stuck. Any suggestions would help and links to the things you said would be great i could be doing something wrong.
Thanks
Boot into cwm, try partitioning the sdcard 2048/0. This generally fixes the type of bootloop you're describing. I know from experience. =]
Agreed. You most likely need to repartition.
Hello, sorry if this has already been answered but I did look around at similar scenarios and it seems to me that using odin to flash the stock kernel should fix it but on my device, however, it doesn't fix my problem. I beleive what I did was select update firmware from .zip in clockwork on accident. Idk if this is what you consider a "boot loop" because it doesnt restart it just sits there at the black galaxy s2 screen. Any insight would be great. I hate to have to buy a new one as it is quite alot of money. Like I said, sorry if this is already answered but after looking around for hours I still hve had no luck. Thanks in advance, Alex
Can you get into recovery (volume up+home+power) or download mode (volume down+home+power)?
I can get in to download and recovery mode both
The outlook is promising then. Without knowing what you've flashed, it's impossible to say what damage you've done, but if you don't mind losing your data, you can certainly get back to a working state by following [READ THIS] Got a Boot Loop? Don't post a New Thread!.
Before going down that route though, if you do want to keep your data, let us know what you flashed as it might be recoverable (maybe you just flashed the wrong kernel).
I can't say for sure what i flashed but I can say that i either flashed with an update or updated with a kernel??? sound right??? idk. the data isnt near as important to me as the 680 dollars my carrier will charge me for a new s2. Right now im using a junk alcatel tribe and im going through galaxy withdrawls.
Well before flashing anything else, make sure you definitely have an I9100, not some other variant (I notice you mentioned dollars). If you have a different model, you're in the wrong forums and might make things worse by following advice for the I9100.
I was pretty sure that it is the I9100 but i took the battery out and double checked. it IS the I9100
also for what it's worth when going into recovery(stock version) right after the text reading updating application it gives me an error in red. (E:install_application_for_customer:Can't unmount /preload copy application failed) and after the (Appling [yes it really spells it appling] Multi-CSC) it says Can't access to '/system/csc/TTT/system/'. However, the line after it says that it says Successfully applied multi-CSC
My first attempt to get back to a working phone without losing data would be to flash a stock kernel then, have you tried that?
Ok.. done.. but it still sits at the galaxy screen except now it has the triange due to the custom firmware
If that hasn't got you up and running then it's probably time to bite the bullet and follow the instructions from the boot loop thread linked above (which will also remove the triangle).
Maybe you can answer another question for me. When in recovery mode it says apply update from sdcard... why does it say that when it doesnt actually read from the sdcard? i have checked with the sdcard both in and out and the file directory in the recovery mode doesnt change. is it calling the usb storage an sd card?
ok when flashing a stock rom do i use the phone option in odin or the pda still
If you're flashing a stock rom from [ROM+Guide]Official i9100 Firmwares KG, KH1/2/3/4, KI1/2/3/4/8, KJ1/2 Download, then just follow the instructions from there (but usually PDA).
:'( Still wont boot.
What does happen, did any steps fail, any error messages?
Everything went smooth with no errors. No steps failed. Sitting at the boot screen is all it does though
Did you definitely wipe user data? (step 3). The final step of that thread is to try flashing a ROM which wipes, such as (non-stock) VillainROM 1.1.
well... yes i definitely wiped the user data and it was successfull when doing so. I didnt try the villian rom just because I thought that it was an optional thing but i will def. try it now that you bring it up. and hey, i really appreciate the help no matter what the outcome
(VillainROM 1.1 - XWKE7 base) I'm a UHKG7..... is this going to be a problem? just something i noticed and thought I would ask before going ahead
I am trying to flash into this custom ROM http://forum.xda-developers.com/showthread.php?t=1766999 on my ATT galaxy s3... the first times i tried it it hung indefinitely at the updating android applicatoins screen after installing.. I was successfully able to restore from my nandroid fortunately.
The third time, I booted into the OS but it started hanging when i was signing into my google account and never let me open any applications. Then when I reboot it it just hung at the samsung screen forever.
I don't know what im doing wrong, I am clearing data and cache and then flashing from the SD drive then rebooting. Am I the only one having this problem? Should I try another rom and see if that works?
This is my first time flashing a ROM
theraker007 said:
I am trying to flash into this custom ROM http://forum.xda-developers.com/showthread.php?t=1766999 on my ATT galaxy s3... the first times i tried it it hung indefinitely at the updating android applicatoins screen after installing.. I was successfully able to restore from my nandroid fortunately.
The third time, I booted into the OS but it started hanging when i was signing into my google account and never let me open any applications. Then when I reboot it it just hung at the samsung screen forever.
I don't know what im doing wrong, I am clearing data and cache and then flashing from the SD drive then rebooting. Am I the only one having this problem? Should I try another rom and see if that works?
This is my first time flashing a ROM
Click to expand...
Click to collapse
i would restore my nandroid and see if all is well, if so, try a wipe of cache, dalvic cache, and factory reset, then try flashing the rom, if that fails too, try a different rom.
It seems based on the official thread that many users experienced the same problem flashing to 4.0 from stock.. Have to go to 3.0 first and then 4.0 (see the thread I linked, last couple of pages)...
Posting it here in case I wasn't the only one who didn't read the whole thread.
Hi, all! I'm sorry if this is in the wrong section, but I'm having a hard time trying to understand the different forums.
My Samsung Galaxy Ace (S5830) running under a custom ROM The Ultimatum (I've been using this custom firmware for a few weeks now, with no real problems up until now), is bootlooping with no apparent reason. On a rare occasion, most apps on the phone stopped responding and would crash upon opening, and would require a restart before they worked again. Well this happened to me a few hours ago, so I decided to reboot my phone. After coming back to check my phone, I had found it was still booting. This has gone on for several hours now, and I've tried turning it on and off, removing batteries and everything. It's stuck in bootloop. I found this was odd, as I have had no dramas with the firmware I've been using. I have not made ANY recent changes to the phone whatsoever, so I can hardly believe it would be my fault.
Now, my question is; how do I fix this without wiping all data and installing a clean ROM? I have a lot of stuff in the internal storage I can't afford to lose, and it's really important to me. A full wipe of all data would not be ideal. I can access recovery mode.
Thanks in advance, and I apologise if this is in the wrong forum!
You might want to ask to the rom thread for some help or ask in this section,
Galaxy Ace S5830 Q&A, Help & Troubleshooting
Anyway, I will try to help. If your custom recovery is support backup and restore (and advanced restore) your rom (check your custom recovery thread), try to backup your phone rom for now, so you could restore it back when solution not working.
Try to reflash the rom again without wipe data and reboot. If still in bootloop try to wipe data and reboot, see if that phone still bootloop.
If phone is successfully boot, go back to recovery and go to advanced restore, restore only data and then reboot. If still not working, then just full restore back to the phone to state before since I have no idea anymore.
That is the option I only know for now. However, try to ask help on section I link above or the rom thread before try this one, since I only familiar with Galaxy Gio (really similar to Ace) in the past.
I tried what you suggested but no positive results, really. I managed to boot after a full wipe, but restoring data locked it back into a bootloop. I'll try posting it in the other section.
Thanks.
So it is that embarrassing time when you have messed up and have to ask for help
So to keep things short and sweet, but still give enough detail:
Phone: SGS2 i9100
Flashed the correct Siyah kernal - ran it for a few days with the stock rom and all was good
Decided to flash a rom and after reading about Neatrom I followed the instructions on Sale's Neatrom page on XDA...
.... all seemed to go OK. Flashed the custom recovery, flashed the rom, flashed the gapps and rebooted.
All seemed to be OK until it fully booted - to the screen where it asked for my pin. I wasn't expecting this, but used the pin I would normally use - didn't work. Tried a few obvious default style pins like 1234, 1111 etc. Nothing worked.
Decided to boot into recovery and flash the nandroid backup I had made, but instead of booting up into CWM it booted in TWRP and I could find the nandroid backup.
Perplexed I tried reflashing the rom - this seemed to go OK, but then when I tried to reboot, the phone got stuck on the Neatrom splash screen.
I feel like an idiot (I guess I am!)
Many thanks for reading and I hope someone is gracious enough to help me out.
Right, just to prove I'm not useless... OK not really, I did it cos I wanted a working phone... I had a flash (flash, geddit?) of inspiration and used TWRP to flash the CWM zip on my phone. I then used CWM to restore the nandroid backup and I now have a working phone again. Yay!
I'd still like a custom rom (neat rom would be good), but unless I know what to do differently I'm going to end up with the same problem of being unable to get past my lock pin... I suppose I could remove the lock pin and then try again, but I suspect that the lock pin might not be my only problem...