So I've got stuck in a boot loop twice now (both messing with build.prop I'm pretty sure) and each time I couldn't get into recovery either. I held power + volume up + home and I saw the sammy logo come up (and in the upper right hand corner in blue there was 'booting recovery' for a split second)... and then nothing. I could get into download mode though.
Both times I freaked the **** out. The first time i boot looped like this I flashed the insecure boot image and cwm recovery via Odin/S3 toolkit again (it was a shot in the dark and I was scared) The phone still didn't boot (obviously), and i thought i still couldn't get recovery for a while but then it magically came up after a few tries. I attributed it to dumb luck.
The second time i boot looped, i still couldn't get into recovery. I tried flashing like before via Odin, and this time CWM came up as expected and I could restore a nandroid.
So if you get in a bootloop and your recovery isn't working (no idea why this happens either, any thoughts???) then go ahead and flash the recovery again via odin.
Maybe I'm pointing out the obvious, and if so give me the newb damnation i deserve. But if I helped hit thanks so maybe one day ill have the privileges to bug devs in the development forums (kidding about the bugging part ). I know I couldn't find info like then when I was searching (I was also in a state of panic). Maybe there should be something like this in one of the pinned threads in the dev forums.
Crap, i mean to post this in General. Buuuut it sort of fits Q&A too. Do as you see fit, mods.
andham95 said:
So I've got stuck in a boot loop twice now (both messing with build.prop I'm pretty sure) and each time I couldn't get into recovery either. I held power + volume up + home and I saw the sammy logo come up (and in the upper right hand corner in blue there was 'booting recovery' for a split second)... and then nothing. I could get into download mode though.
Both times I freaked the **** out. The first time i boot looped like this I flashed the insecure boot image and cwm recovery via Odin/S3 toolkit again (it was a shot in the dark and I was scared) The phone still didn't boot (obviously), and i thought i still couldn't get recovery for a while but then it magically came up after a few tries. I attributed it to dumb luck.
The second time i boot looped, i still couldn't get into recovery. I tried flashing like before via Odin, and this time CWM came up as expected and I could restore a nandroid.
So if you get in a bootloop and your recovery isn't working (no idea why this happens either, any thoughts???) then go ahead and flash the recovery again via odin.
Maybe I'm pointing out the obvious, and if so give me the newb damnation i deserve. But if I helped hit thanks so maybe one day ill have the privileges to bug devs in the development forums (kidding about the bugging part ). I know I couldn't find info like then when I was searching (I was also in a state of panic). Maybe there should be something like this in one of the pinned threads in the dev forums.
Click to expand...
Click to collapse
Related
Last night I had to use Odin to flash my vibrant back to JFD (Because it got stuck in a boot loop), and everything went well. I re-rooted my vibrant, flashed clockwork mod recovery, and installed a new rom (AOSPish v1.1). Up to this point, I was able to access recovery via the 3-button method (I used the hardware buttons to get to recovery in order to flash AOSPish). However, I've been trying for the last hour to enter recovery via the hardware buttons and I've gotten nowhere. Even download mode is shot, and I don't know what could have caused this. Any help would be appreciated.
More info, my phone won't boot fully if the hardware buttons are being pressed. It remains at the Vibrant screen if the hardware keys are held while booting, and won't fully boot until the it is shutoff and allowed to boot without the hardware keys being touched... Weird.
Ok, more weird happenings. Recovery on my phone is absolutely, positively dead. I tried to reboot into recovery via Rom Manager, and now my phone won't boot at all. Thankfully though, I was able to force my phone into download mode, so I'll try to restore with Odin shortly. Maybe someone with better knowledge of this phone can come along and tell me what happened to my phone because I am completely stumped. I've never seen anyone report their phone as incapable of entering recovery at all, so I really don't understand what happened.
I guess my 3-button recovery works fine, it's just that my recovery in general is screwed up. Oh well, I'll be flashing back to Odin soon, but if anyone has every experienced this problem, please tell me what caused it so I can figure out what I screwed up. Now I'm just a little scared about flashing back to JFD since if it doesn't fix the problem, I'll be stuck in the same boat (Since Odin ends with a reboot into recovery).
Wow, I thought at least one person would post by now. Anyway, flashed JFD via Odin and everything seems to be in working order. Still have no idea what caused recovery to decide it no longer wanted to work correctly, but for future reference, an Odin flash will fix your recovery woes.
hello, my name is shahrukh and i need some help. i downloaded animmod (from 4shared) and then i donwloaded busybox. then i pressed blur and then it asked me if i want to reboot it. i pressed yes. this is when the problem starts. It turned off and then it turned on half way and then it turned off. it kept doing that and then i just left it for the night. in the morning it was not doing anything. when i held the power button it turned off and on for like two times and then turned off. i cant even start it up so i have no idea what to do.
i don"t know what to do
please help!!!!
Okay, we need details, describe exactly when "halfway on" is. We need your full model number and rom version (if you know it). Have you tried plugging it in to charge? Does it show anything now that you try to boot it? try holding volume up and powering on to enter recovery menu.
details
ok so when it turns on it says samsung. then after like 10 seconds it turns off. it does that for a few times and then it just goes in a black screen. the model number is YP-G7OC/NAW. when i plug it in to charge it goes on and off two times and then off. if it has low battery it just shows the sign. as for the rom i don't think i have any. i just rooted it using superoneclick. if it goes to recovery mode what do i do?
thanks!
(you got me really fired up when i saw the recovery menu!)
If you can get to recovery menu, try a factory reset, and clear cache. I am not sure if there is a recovery rom for your device, you should check samfirmware.com
tried both of them...no luck. and i couldn't find a recovery rom on samfrimware.com.
Your device has capacitive or mechanical home button?
it has a capacitive home button...the usa version
shahrukhraza said:
it has a capacitive home button...the usa version
Click to expand...
Click to collapse
The phone boots in recovery?
If so, I can investigate a little more what's happening.
I'll try to post a return-to-stock image soon... The problem is that mine is cluttered with crap that the zergRush exploit added (it insisted on installing busybox instead of just rooting...)
(I'm not sure, but I think someone else already posted a stock zImage and system image...)
Here is the post about fixing capacitive buttons. A quick search of forum should have found it.
http://forum.xda-developers.com/showthread.php?t=1421797
Sent from my YP-G70 using Tapatalk
nooooooo!!! you guys have all got it wrong. first of all it doesnt boot in recovery. the only way to get in recovery mode is when it shows the battery sign i hold "up volume"+ power button.and the capaciative button is completely fine. im just stuck in a bootloop (i think) and it has nothing to do with a broken capacitive button! i will try to post a video today to show you guys exactly whats happening.
i kind of had the same problem, one time i thought i had entropy's kernel on and i had CWM well i didn't but i still thought i had so i tried rebooting into recovery using the terminal:
su
reboot recovery
then i turned off and went to this weird recovery menu it had four options, reboot system, apply update from SD card, wipe data partition, and power off and it had a ton of red letters and words saying like, couldn't access data partition or cache partition and couldn't access /data/media, or system, and then i just turned it off because i wouldn't let me choose an option, and then i got stuck in a loop but not during when it says SAMSUNG mine happened during the animation music part that look like fireworks and then SAMSUNG would light up blue then go through it again and 2 more times then go black and i tried flashing the US stock ROM in download mode but still would go through the loop and it doesn't even charge so i got nothing
so did you somehow fix yours? and i never got a recovery menu that showed something about shut down.:confused
Before brick
xxxxxxxxxxxxxxxxx
wait....are you asking me those questions? just to tell you im no developer or something. im just a 12 year old who has his galaxy player stuck in a boot loop. you have to make another thread if you have a problem.
sorry!
Ok. : ) You got it wrong. No problem. His case is different from mine. Just wanted to use her Brick in case. Nothing more. good luck.
I resolve my doubts alone. Nothing that Google does not respond. haha
At least before brick.
ok. let me ask google too xD
anyways..anyone have any idea of how to fix this boot loop?
im trying to do the Linux thing by running the ressurector ans the VM windows the forum is posted under development called hard brick recovery for galaxy 5.0
ok.(i have no idea what you are saying...just saying!)
Hi
So I've had my Samsung SIII for just over 18 months, and it's all worked fine etc. I've never rooted it or anything.
But this morning it will not boot up. When I try to switch it on the start up sequence happens, but it gets stuck on the flashing Samsung splash screen. If I turn it off it just restarts and ends up back on that screen. The only way to stop it is to take the battery out.
I've tried starting it in recovery mode (power+home button+vol up), but the standing, open android just flashes and I end up with the android lay down with the red exclamation mark from there. It then loops between the two androids and the Samsung SIII start up logo screen. I have tried to press the volume buttons whilst on the red exclamation mark screen but cannot get to anywhere from it.
However, it will load the download mode (power+home button+ vol down) just fine.
I have looked all over but most people encountering anything similar have rooted their devices, which I have not.
Also, last week I lost all of my contacts which were stored on the device (I don't know why) but that might have something to do with it.
I don't particularly want to hard reset the phone and lose everything, but if it's the only solution I will do.
Thanks.
In download mode is the product number shown or a blank?
If it shows i9300 then you have a good chance of flashing either a full stock rom or a rescue firmware (see general forum) using odin. You will need to factory reset in recovery afterward, but your data is almost certainly unrecoverable.
If the product number is blank then you have partial SDS and require a new motherboard.
Sent from my GT-I9300 using Tapatalk
rachypoo said:
Hi
So I've had my Samsung SIII for just over 18 months, and it's all worked fine etc. I've never rooted it or anything.
But this morning it will not boot up. When I try to switch it on the start up sequence happens, but it gets stuck on the flashing Samsung splash screen. If I turn it off it just restarts and ends up back on that screen. The only way to stop it is to take the battery out.
I've tried starting it in recovery mode (power+home button+vol up), but the standing, open android just flashes and I end up with the android lay down with the red exclamation mark from there. It then loops between the two androids and the Samsung SIII start up logo screen. I have tried to press the volume buttons whilst on the red exclamation mark screen but cannot get to anywhere from it.
However, it will load the download mode (power+home button+ vol down) just fine.
I have looked all over but most people encountering anything similar have rooted their devices, which I have not.
Also, last week I lost all of my contacts which were stored on the device (I don't know why) but that might have something to do with it.
I don't particularly want to hard reset the phone and lose everything, but if it's the only solution I will do.
Thanks.
Click to expand...
Click to collapse
Do has boomboomer said above but as a last resort before flashing back to stock or a rescue firmware if you flash PhilZ recovery in download mode with odin.You then have a Aroma option in PhilZ recovery to browse and copy phone files so you may be able to recover some data pictures etc.
Please read PhilZ thread >> http://forum.xda-developers.com/showthread.php?t=2201860 << and the special features thread about Aroma file manager in post #3
Please note use as a last resort to get your data back! and read everything! Also all this is presuming you can get into PhilZ recovery after flashing..
I'm having the same problem , been looking through lots of topics. When I switch on the phone it's not booting android guy lays on his back. Download mode and Android Recovery are in my range.
I've been trying to flash stock-firmware from sammobile.com with ODIN but no effect , I mean It all went OK in Odin Operation list than fially phone reset and PASS. But this android guy is still laying on his back and making fun of me xD
Before trying to get back to stock ROM, I've had rooted phone and installed RR with 4.4.2 for S3, now I don't have a clue what shall I do next ...
Any ideas ? (the noob[me] have asked )
Stuck on samsung logo
Hi my s3 got stuck in the boot samsung logo.
It happend after I went to CWM app and created partition from there.
After I reboot it , then it froze down there.
S3-rooted running cyanogen mod 10.2
Teamdaiwa said:
Hi my s3 got stuck in the boot samsung logo.
It happend after I went to CWM app and created partition from there.
After I reboot it , then it froze down there.
S3-rooted running cyanogen mod 10.2
Click to expand...
Click to collapse
You buggered the partitions .
Remove partition .
SOLVED >>
I have solved my problem with this lying android guy on his back , after trying to get back stock. So the thing was on my phone there have been left the kernel from Resurection Remix , I have updated it to Custom Kernel from this topic
http://forum.xda-developers.com/showthread.php?t=2563562
And my newest version of stock firmware is swimming very nice I hope This will help someone
Just gonna cut straight to the point.
Wiped my phone to flash a new ROM, selected 'Clean to install new ROM' but instead of then flashing a zip file, i went to Reboot Recovery.
I then hit No, thinking it would take me back to the main menu, but instead it continued to restart, and now it gets stuck on the Sony logo.
I've tried flashing completely stock ROMs and also this one which, those with similar issues has said worked for them, however nothing appears to be working for me.
It does seem to flash successfully, no error messages that i saw in Flashtool, but upon booting up it still get stuck at the Sony logo. Either just Sony (older ROMs) or Sony with Xperia at the bottom (newer ROMs), so i guess the ROM is installing fine, but there's something else that isn't?
The only way to shut down is holding down Power + Vol Up, and there is no LED light (green, purple, red) to notify of anything.
And because of this I no longer have recovery either, where I could just flash a new zipped ROM and be on my merry way.
Any suggestions?
EDIT:
Ok so I hate when this happens, where I figure it out a few mins after I'm made a post (after stuffing around for several hours already).
I've just tried flashing several different ROMs again to no avail, tried once more and checked the two boxes in the Wipe options, seemed to take A LOT longer to flash, but it's now working fine
flash any ftf or chech here
http://forum.xda-developers.com/xpe...2-0-togari-t3452968/post68481255#post68481255
I also in this situation. I cannot go to recovery and stuck at boot logo. Can you point me the right direction? Thank you.
I've followed these instructions to the tee but have not had any luck with getting this to work. The flash always just results in my phone getting stuck on the "recovery booting.... recover is not seandroid enforcing - Set Warranty Bit : Recovery" screen. Odin reads as "PASS!" but my phone seems like it's just stuck. I've scoured over dozens of forums searching for answers but what works for others just doesn't seem to be working for me.
The instructions all seems so clear, and multiple forums' instructions gave me confidence that this would work no problem as long as I followed the instructions precisely. I guess that wasn't the case. I can't afford a new phone right now, but I'm sure my phone isn't completely bricked. There's gotta be a way! Can you please help me, xda community?
EDIT: I forgot to mention that I also tried the "uncheck the Auto Reboot option" method, and I'm a little confused about the last sentence. See below:
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
I'm confused about the "This will start the install process" sentence. I flash, let it finish until Odin says "Pass!", remove the battery, boot into recovery, and then I have two options from there - I can either go into download mode again, or I can start the phone normally. Starting the phone normally just brings me right to the recovery mode which gets stuck there indefinitely. I've left it there for 15+ minutes and it still just stays stuck there.
EDIT 2: Exactly how long is it suppose to take to boot up after it's been flashed?
EDIT 3: IT WORKS. So, If you just sort of hold down all the buttons at the same time, the phone will restart a few times and eventually bring you into the TWRP menu. This is what I was unaware of before. I'm not exactly sure what the specific method or timing is for that, but just tinker with holding all the buttons, and I think you can let go when you see little blue letters on the top left that says recovery or something. Of course, being able to access the TWRP menu means you must first have flashed the TWRP thing, which I did using Odin. Just download the latest TWRP .tar file and flash it with Odin.
EDIT4: SUCCESS! I am now successfully rooted! I reflashed the twrp-3.0.2-2-klte.img.tar and then I was able to access the actual GUI. I guess what I had before was some super stripped down version of the TWRP that only gave me access to a command-line looking interphase in recovery mode, with very limited options. So there you go, if you find yourself looking at pictures on forums of a supposed TWRP with an actual GUI you can navigate, that's because it does exist! Download the one I just mentioned, flash it using Odin, and boot it up by holding VolumeUP, Home, and Power. From there you can flash Zip files, just put the zip files into an sd card. I put my zip right into the sd card, not even in it's own folder or anything.
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
goog888 said:
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
Click to expand...
Click to collapse
Interesting, thanks for the info! Funny enough, while I was at Best Buy last night, I decided "what the heck" and asked a Geek Squad guy about my phone, and told him how I attempted to root and now it wouldn't boot, etc. He took my phone, and just sort of held all the buttons together and it restarted a few times, and he just kept fidgeting with it until eventually it came up to the TWRP recovery menu! So, I did a factory reset and started up the phone. It is currently on 5.1.1. I have since been able to get myself into the TWRP recovery menu by fidgeting like he did, even though I'm not entirely sure what exactly the timing or button combos are. The Geek Squad guy said he just held down ALL buttons, even VolumeUp and VolumeDown at the same time. So whatever, TWRP menu IS accessible finally.
At this point, I'd prefer to flash CM13 to it, and apparently I can just put the CM13 file on my phone storage/sd card, and then flash it through the TWRP recovery menu. But since I factory reset my phone back to 5.1.1, should I first update my radios? A techy friend of mine introduced me to a new fear - that if you flash a ROM that is incompatible with an older radio, it could "hard brick" my device. So now that's where I'm at. I want to flash a rom to gain simple root access, but don't want to risk bricking my device.
Here is my phone's information:
SM-G900T
Android 5.1.1
Baseband version G900TUVU1FOG6
Build Number LMY47X.G900TUVU1FOG6
I don't know how to mark this solved, but it is, as described my my 4th edit in the original post.