Hi guys, reasonable newbie here. My Galaxy S2 has stopped displaying anything after the initial logo. In fact it seems to turn the phone off as you can make repeated attempts to boot it within a few seconds.
I started by flashing an insecure sgs2 kernel from this site with odin, then used s2root.
I then played around with rom managed but found it wouldn't boot into clockworkmod (orange exclamation mark in a white triangle every time) I booted into it manually and started trying to flash cm7 which I had downloaded earlier.
I wiped the data etc and flashed the cm7 zip (plus the google apps zip). Rebooted and got into cm7 with everything seeming fine.
Next I thought I should probably flash back to the stock version of the insecure kernel. I rebooted the phone but got distracted and didn't start it up in download mode, I looked just in time to see the normal logo (with the yellow insecure triangle) and then nothing....just blank.
I tried rebooting afew times and nothing, even after yanking the battery. Then I tried getting back into clockworkmod to reflash cm7. Nope, same thing happens.
I can still get back into download mode but nothing I flash makes the slighest difference. Tried reflashing clockworkmod, insecure and stock kernels of various versions but I'm stuck.
This is almost a new phone and I can't believe I've already killed it I would be so grateful for any tips, I've included as much info as I can think of from the top of my head but I will do my best to answer anything you gurus might need.
Again, very grateful for any help...I don't want to have to explain to Orange how I've managed to brick this after 4 days
Ok after trying over and over again to get into recovery mode, it booted into the original (3e) recovery. I've just flash cwmod to it again and have just flash cm7.
After reading some posts about cyanogenmod sometimes not flashing correctly first time, I did it twice (and it did indeed take longer the second time) and twice for google apps.
Next I'll try to get back to the stock kernel. This is where it went wrong before but i'll cross my fingers.
Edit: Well, multiple reboots didn't cause a problem but flashing the stock kernel back does kill the handset again. I'm sure this stuff is all obvious to those with experience I guess I'll have to sit with an insecure kernel and the yellow triangle for the forseeable future. On a side note, s2root doesn't see the phone connected with cm7 (yes usb debugging was turned on). I'm hoping that it is pre-rooted but I haven't tested that yet.
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:
revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.
tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi
Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium
freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.
i upgraded my note N8000 via odin mobile pro with success and everything was smooth and the root was not intact
I tried to flash a theme via mobile odin but was not success, but note was still ok
then 2 days later I tried to enter the recovery mode , i found the note stuck on samsung boot screen and dose not reboot, I can enter download mode but can not enter recovery mode to reflash even the stock rom
what to do?
should i reflash the CWM as 1st time? then reflash the root if i found it is gone?
or i have to reflash the stock rom first via odin desk top since i can not reboot the note? problem is the stock rom is on the note and do not have it on PC
the note now is on Samsung boot screen, how to turn it off since note can not remove the battery?
EDIT 1::good:
Flashed a stock recovery via odin desk top, and rebooted
Note is back alive , no wipes, every thing still there, root still here
Rebooted once again with success
rebooted into recovery (stock since I lost my CWM) with success
EDIT 2
Flashed CWM and my note is back for my modifications
:fingers-crossed:
Stock Recovery File?
thermax04 said:
i upgraded my note N8000 via odin mobile pro with success and everything was smooth and the root was not intact
I tried to flash a theme via mobile odin but was not success, but note was still ok
then 2 days later I tried to enter the recovery mode , i found the note stuck on samsung boot screen and dose not reboot, I can enter download mode but can not enter recovery mode to reflash even the stock rom
what to do?
should i reflash the CWM as 1st time? then reflash the root if i found it is gone?
or i have to reflash the stock rom first via odin desk top since i can not reboot the note? problem is the stock rom is on the note and do not have it on PC
the note now is on Samsung boot screen, how to turn it off since note can not remove the battery?
EDIT 1::good:
Flashed a stock recovery via odin desk top, and rebooted
Note is back alive , no wipes, every thing still there, root still here
Rebooted once again with success
rebooted into recovery (stock since I lost my CWM) with success
EDIT 2
Flashed CWM and my note is back for my modifications
:fingers-crossed:
Click to expand...
Click to collapse
Do you have a link to where you found the stock recovery rom/image? And how did you flash it? I am having a similar problem right now.
kyleschepis said:
Do you have a link to where you found the stock recovery rom/image? And how did you flash it? I am having a similar problem right now.
Click to expand...
Click to collapse
do u mean the stock rom? I got it from samobile.com
or u mean u want the stock recovery?
try this
http://mirror21.downloadandroidrom....e10.1/recovery/N8000_StockRecovery.tar?token=
Will reflashing the tablet to stock, delete all of my files off of it? Is there a way to retrieve the files through download mode somehow?
kyleschepis said:
Will reflashing the tablet to stock, delete all of my files off of it? Is there a way to retrieve the files through download mode somehow?
Click to expand...
Click to collapse
in my post i wrote that reflashing the stock rom did not wipe (delete) any thing, u will find all your stuff undeleted
thermax04 said:
in my post i wrote that reflashing the stock rom did not wipe (delete) any thing, u will find all your stuff undeleted
Click to expand...
Click to collapse
It says you flashed a stock recovery. Is it the same case for a stock ROM?
kyleschepis said:
It says you flashed a stock recovery. Is it the same case for a stock ROM?
Click to expand...
Click to collapse
sorry, my mistake, flashing the stock rom will not delete your stuff, just be sure to flash the same rom or higher, not lower one
So, I tried flashing the stock recovery and that did not work. And then I tried flashing the stock rom (multiple times with different roms) and that did not work either. My tablet is still stuck on the screen that says "Samsung Galaxy Note 10.1". Do you have any other suggestions?
can u write some details about what was before and reason for problem, to think together about a solution
thermax04 said:
can u write some details about what was before and reason for problem, to think together about a solution
Click to expand...
Click to collapse
My Note 10.1 N8013 was rooted, had TWRP, and Cyanogenmod 10.2 Nightly on it. I hadn't touched it in two days and went to turn it on. It wouldn't turn on, so I assumed it was dead. I charge it overnight and try to turn it on in the morning, but it just goes into a boot loop. The tablet says "Samsung Galaxy Note 10.1" and stays that way until it dies. If I boot into recovery mode, the Teamwin (TWRP) title screen pops up and then immediately disappears. The tablet then shows the battery loading icon if it is plugged in. The icon shows up, then disappears and the shows up again and repeats this a few times. I could only boot into download mode successfully.
I have tried flashing different stock roms and recoveries through odin, including the one that you have linked on here. None of them have worked. I have also tried repartitioning the tablet, which passed on Odin, but did not solve the problem.
Other forums say that I should do a factory reset or wipe the data, but I do not know how to do this without being able to boot into recovery or the OS itself.
Thanks
P.S. I also brought it to Best Buy to see if the Samsung guy could reflash the stock rom, but his rom did not work either. They are all passing on Odin, so it isn't an error in that case.
I read that a lot of people got problems with Cyano roms. I did not like it and never used it, sorry can not help you
thermax04 said:
I read that a lot of people got problems with Cyano roms. I did not like it and never used it, sorry can not help you
Click to expand...
Click to collapse
Could it be because of the Cyanogen rom? I didn't update recently... I probably updated it a week before it died. Would you happen to know how to do a factory reset / wipe the data from the tablet, if I can't get into recovery mode or the OS?
I don't think that there is any other way, sorry about that.
try to put your problem in the Cyano rom thread, may others had the same and solved it
Ok thank you
Let me know if you get it fixed
Hi kyleschepis,
Let me know if you find a solution. I have a very similar issue . . . the difference is, I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started about 5 days ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But 5 days ago, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I am able to get into the Odin download mode but cannot get into recovery mode no matter what I do/
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. But the power + volume up combination does not get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for 5 days now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
robb-x said:
Hi kyleschepis,
Let me know if you find a solution. I have a very similar issue . . . the difference is, I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started about 5 days ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But 5 days ago, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I am able to get into the Odin download mode but cannot get into recovery mode no matter what I do/
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. But the power + volume up combination does not get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for 5 days now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
Click to expand...
Click to collapse
Did you try removing the sd card and reboot again ?
DId you fix your tablet
kyleschepis said:
Ok thank you
Click to expand...
Click to collapse
Hi Kysleschepis,
Were you able to fix the problem with your phone.
I have exact same problem....my Gt-n8000 tablet is stuck on "Samsung Galaxy Note 10.1" logo. And i cant access the recovery mode.
Let me know if you found a solution to this problem.
Thanks.
same here but didn't work
i have same problem with my Note 10.1 N8000 stuck in bootloop problem but i didn't do anything like upgrading or install new app ... its stuck by him self and i tried the following and all not working :
1, Hard Reset with software menu (not working)"only if the device is working".
2, Hard Reset with Dial secret code key(not working) "only if the device is working".
3, Hard Reset with Hardware Key Button(Factory recovery screen not working).
4, installing recovery philz_touch_6.07.9-n8000.tar with Odin (passed installed successfully but still not working).
5, installing recovery openrecovery-twrp-2.4.1.0-p4notewifi_3 with Odin (passed installed successfully but still not working).
6, installing recovery CF-Auto-Root-p4noterf-p4noterfxx-gtn8000.tar with Odin (passed installed successfully but still not working).
7, installing recovery twrp-2.6.3.1-n8000.tar with Odin (passed installed successfully but still not working).
8, installing recovery Samsung_N8000_Hard_Reset_File_JB in "CSC" field with Odin (passed installed successfully but still not working).
9, installing "N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar" full new Android OS with Odin (passed installed successfully but still not working).
Finlay there is No Samsung Service Center in my country, i need to send it by mail to nearest country have Samsung Service Center and will cost me a lot .. what i have to do
Weeshi said:
i have same problem with my Note 10.1 N8000 stuck in bootloop problem but i didn't do anything like upgrading or install new app ... its stuck by him self and i tried the following and all not working :
1, Hard Reset with software menu (not working)"only if the device is working".
2, Hard Reset with Dial secret code key(not working) "only if the device is working".
3, Hard Reset with Hardware Key Button(Factory recovery screen not working).
4, installing recovery philz_touch_6.07.9-n8000.tar with Odin (passed installed successfully but still not working).
5, installing recovery openrecovery-twrp-2.4.1.0-p4notewifi_3 with Odin (passed installed successfully but still not working).
6, installing recovery CF-Auto-Root-p4noterf-p4noterfxx-gtn8000.tar with Odin (passed installed successfully but still not working).
7, installing recovery twrp-2.6.3.1-n8000.tar with Odin (passed installed successfully but still not working).
8, installing recovery Samsung_N8000_Hard_Reset_File_JB in "CSC" field with Odin (passed installed successfully but still not working).
9, installing "N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar" full new Android OS with Odin (passed installed successfully but still not working).
Finlay there is No Samsung Service Center in my country, i need to send it by mail to nearest country have Samsung Service Center and will cost me a lot .. what i have to do
Click to expand...
Click to collapse
I have the same problem. I was just playing a game when it suddenly turned off and went to the boot screen. Also tried installing N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar.md5 (success but also didn't work). Still stuck at the "Samsung Galaxy Note 10.1" screen.
Also can't access recovery, or do a wipe before installing firmware (I think USB debugging isn't turned on).
Did you find any solutions yet?
Thanks.
el_roi said:
I have the same problem. I was just playing a game when it suddenly turned off and went to the boot screen. Also tried installing N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar.md5 (success but also didn't work). Still stuck at the "Samsung Galaxy Note 10.1" screen.
Also can't access recovery, or do a wipe before installing firmware (I think USB debugging isn't turned on).
Did you find any solutions yet?
Thanks.
Click to expand...
Click to collapse
Sorry till now no solutions ... If you have warranty on the device go to the samsung maintenance center i think its wrong factory made
Hello,
I have an LY-F1 AllWinner A10 tablet.
I installed CWM (using this thread - http://forum.xda-developers.com/showthread.php?t=2189640) and used the reboot-recovery.sh in order to access the recovery screen where I did a full wipe and also wiped the dalvik cache.
I installed cm9, gapps and the lyf1 compatibility zip (from here - http://forum.xda-developers.com/showthread.php?t=1760929), rebooted and everything was working fine.
I did the same again for cm10 (from here - http://forum.xda-developers.com/showthread.php?t=1821398), rebooted and was presented with the spinning cm10 logo. It never gets past this stage, I have left it for 15-20 mins on a couple of occasions.
My plan then was to reflash cm9, but I am unable to get into fastboot mode, download mode, cwm or anything other than the spinning CM logo.
I looked at other similar threads, but couldn't find anything useful.
I appreciate any replies.
Thanks,
David.
similar problem
Does your device have "s off". I waited for almost 4 hours for my HTC eris to boot Evervol, but it still would not boot.
jbaker22 said:
Does your device have "s off". I waited for almost 4 hours for my HTC eris to boot Evervol, but it still would not boot.
Click to expand...
Click to collapse
It may well have been, I'm not sure.
Pretty sure it's fit for the bin now, should have checked i could access cwm with buttons instead of using the reboot script.
Or left CM9 on it... - hindsight is a great thing!
Hi guys, so recently I bought a Galaxy S6 Verizon off of eBay. I got it for fairly cheap because it was stuck in a boot loop. I usually have no problem fixing stuff like this, but this time is different. So the first thing I tried when I got the phone was to do a reset and cache wipe from recovery. I rebooted the phone and it showed a screen that said "Android is starting, optimizing app 9 out of 31." when it got to 21 the phone rebooted and went back to 9. It did this several times before I attempted to wipe/reset again. I then downloaded the tar file G920VVRU4CPH1 and flashed it in Odin. I did a manual reset before the phone booted, and it is doing the same thing again. reboots to a green screen where it tries to optimize apps, stays there for about 20 seconds, and reboots over and over again in the same cycle. I have tried all other stock marshmallow roms that i can find, Odin won't flash older ones, (assuming its not letting me downgrade). Also another weird thing, every time I flash, the blue update screen goes to 32%, stops, erases, and reboots. Phone is on 6.0.1 version MMB29K.G920VVRU4CPH1 as seen in recovery. Any help would be gladly appreciated. Thank you!
I am having a similar problem with loading new rom. The farthest it gets is 32%. Sometimes it doesn't get even that far.
I ended up just buying a trashed s6 and swapping the motherboards. Only way I could fix it