I unlocked bootloader and rooted a couple of days ago. Phone was running smooth. I downloaded and installed cwm. Today I downloaded Bean's Build 14 and tried to install through cwm. When it rebooted I got stuck on the Samsung screen. I tried to flash back to original settings with Odin but now my phone won't turn on at all. I am charging but no battery indicator or led is on to indicate charging. Please help.
Try leaving it plugged in for an hour, and then trying. Also might want to try leaving the battery out for 30 min and trying again. If you are unable to get any response from the phone, then it is likely hard bricked. The only thing that can save it at that point is sending it in for JTAG repair. That service starts at $60.
JHomrig said:
I unlocked bootloader and rooted a couple of days ago. Phone was running smooth. I downloaded and installed cwm. Today I downloaded Bean's Build 14 and tried to install through cwm. When it rebooted I got stuck on the Samsung screen. I tried to flash back to original settings with Odin but now my phone won't turn on at all. I am charging but no battery indicator or led is on to indicate charging. Please help.
Click to expand...
Click to collapse
How did you unlock the bootloader? using EZ-Unlock? Also did you make a nandroid before you flashed? If so try booting into CWM using VOL+ Home and Power and restore your nandroid and see if that works.
Related
I plugged in my device and Kies said there was a firmware update. I let it go through it's paces and upon reboot, it just sits at a pulsating samsung logo.
I've tried reflashing a stock GB image using Odin. Even tried an ICS one. All of them result in the same pulsating samsung logo going nowhere.
What steps can I take from here?
Power + Vol Up
Select Wipe/Factory Reset
Cross your fingers...
Good Luck
I couldn't get recovery to come up before. But it did this time . Anyway, we're back in business. ICS is fantastic on this!
Hi people, I update my tab7+ 6210 to ICS everything was fine, but sometimes I got random reboots and today it suddenly turn off, I tried to turn on but nothing happens, so I plugged into charge but show no signs of life, I tried to enter stock recovery but accidentally enter download mode, Im screwed?, please I need some guidance. Thanks.
--------_______________________-----------
IT boot again, Im going to try enter recovery and do the wipes.
My phone is rooted with stock rom. The only changes are listed below
Froze bloat that was safe
changed bootanimation to stock samsung
replaced some apps with inverted versions of themselves (ex. google +, stock messaging)
Here goes:
I was using navigation and I noticed that my phone was off after I had finished. Nothing worked at all, I could not boot into recovery or download. I connected the phone to a charger and red led flashes and an empty battery appears. The battery was full. I could reboot the phone while on the charger, but it would shut off as soon as it got to the homescreen. While off, If I pressed the home button, the green battery would appear as if it were charging. From here I could boot into recovery and download mode. The phone will only boot into these modes while connected to the charger. Here is where it went bad. I attempted to restore a backup while the phone was on the car charger and my car charger got pulled out in the middle of a restore. No charger meant that the phone shut off mid restore. Now, when I plug in the phone, the red led appears and the empty battery with a circle inside appears and then goes away. This repeats itself over and over and the phone buzzes when the empty battery reappears. I can still boot into download mode but not recovery. If I try to flash the stock samsung rom via odin, it says that it passes, however upon automatic reboot the samsung appears and nothing else. After the samsung appears the phone just continues to buzz every 5 seconds or so as if it is trying to do something. Could it be a bootloop? I have done a ton of searching here and now I am resorting to help! Your time is appreciated and beers on me if you can help me get my phone back to normal.
Put your phone into download mode and let it sit on the charger for 30 minutes. After pull and reinsert your battery and then try to power on your phone without your charger. Then proceed to charge your phone to full since it powered on.
Sent from my Freaked VzW s3 using xda premium
This did not work but thank you for the suggestion. From what I have gathered, as long as I can get into recovery then I should be able to get everything back to normal. Anyone?
elreydenj said:
This did not work but thank you for the suggestion. From what I have gathered, as long as I can get into recovery then I should be able to get everything back to normal. Anyone?
Click to expand...
Click to collapse
if you can get into download mode, you can use odin to fix everything.
you might have to do a complete wipe but it is what it is
http://forum.xda-developers.com/showthread.php?t=1840030
read that
I tried this already. My problem is that after I flash the first bootchain, the second bootchain will not flash. I gets stuck at the setup in odin. I see there is an option to disconnect the phone and exit odin and reconnect the phone without leaving download mode if this happens. My problem is that if I disconnect the phone from the computer or from the charger it shuts off automatically. I tried these steps the best that I could and when I click nand erase and it reboots, then all it does is buzz every few seconds. I then shut it off and do the data and cache wipe and reboot. It reboots and appears to be the stock rom asking me for language and activation after, but the phone shuts off almost immediately and reboots to a blank battery with a circle in the middle. This is after I have had the phone on the charger for a long time. This happened out of the blue after I was using navigation. This problem did not arise from changing something in the system or from flashing a rom or kernel or anything of the sort. No one has seen this issue with the blank battery? I saw someone mention in android forums but the resolution was that they returned it and got a refurb.
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.
Hello guys I have been struggling for the past week, my LG G2 phone has been rooted, I flash a custom recovery TWRP then I lunched to my stock rom I then tried to update my firmware to 4.4.2 kitkat the update was downloaded successfully, then it told me to reboot, so I did phone switched off then I was stuck on a boot loop but this time it was a boot loop with a error message on the left top corner. and then it would take be to a dim back screen. I searched the entire week to find a method to get me through the start screen and I found this -> NO Recovery mode, No download mode, after OTA on rooted LG G2 http://forum.xda-developers.com/showthread.php?t=2582142 I done exactly what it was showing, then my phone switched off and now it won't power up. Then I tried turning it on NOTHING phone does't show the LED charging lights, does't respond to the usb being plugged in can't do ANYTHING I am guessing the battery has died so now I don't know what to do, either contact LG or should I try getting a battery that is fully charged or even use a factory cable any ideas guys ?
Call LG support.
Sent from my g2 using Tapatalk
I had my phone just sitting on a wireless charger this morning and had been there for about 15-30 minutes. I noticed it was rebooting, odd I thought? I took it off and then realized it was going into a boot loop. I gave it a soft reset and then it would turn on and stay on for about 10 seconds before boot looping again. I again gave it a soft reset after a couple loops and now it seems to totally dead, as the title implies.
No button combination has worked and I've held them all down for well over 30 seconds each. I've tried plugging it into my PC and haven't gotten any response that way. The blue LED is on so I know it's not dead...I think? To make matters worse, I bought this phone off Craigslist about 5 months ago and it's the Exynos version so I definitely can't get any kind of warranty on it. I'm hoping someone has had this problem and can help or just has some advice. Thanks everyone.
EDIT: To keep this updated, I have been able to get into Odin Mode and have tried to flash stock firmware. Odin says everything went fine but the phone hangs up at the Samsung Galaxy S7 logo. I'm unable to boot into recovery mode and I've even tried to reinstall TWRP with Odin and that has not worked.
Seen the LED only problem before, waiting for the battery to drain and the phone to turn off seems to be the only known cure atm
Once it does, connect the charger for 15 mins, then boot directly into recovery and clear caches to try fix the bootloop, possible it may need factory resetting / clean flash of stock ROM
Using the MicroUSB > USB white adapter, you may be able to connect a power hungry USB peripheral to the phone to drain the battery faster, I use a USB desktop fan, but some people report it not working when it is stuck in this LED loop and have just had to wait it out
Thanks for that advice, I'll let it drain over night. However, I have been able to get it to boot into Odin Mode and Odin v.3 recognized it. I flashed the stock firmware but upon rebooting nothing happened and now it gets stuck at the Samsung logo screen. I can still get it back into Odin mode, which I believe will be the fastest way to kill the battery, but I find it odd that I can get into that but not recovery? I am rooted and have TWRP installed, if that matters at all.
If you can get into Download (ODIN) mode, then letting the battery drain probably won't help, that only seems to help when the phone is completely stuck with nothing but the LED working
Make sure you flash CSC (Not HOME_CSC) along with the other 3 sections of the ROM, using ODIN 3.12.3, that should factory reset the phone after the flash
If you successfully flashed stock with ODIN already, you are no longer rooted and do not have TWRP installed, flashing stock with ODIN replaces all that with stock
I updated Odin and once again tried to flash the 4 parts, making sure I used the right CSC file, but I'm still getting hung up at the Samsung Galaxy S7 logo. Do you have a suggestion as to which region's firmware I should use? I have been trying the Australia one from SamMobile's site.
EDIT: And to clarify, I have the G930FD(the duos one).
jonny727272 said:
I updated Odin and once again tried to flash the 4 parts, making sure I used the right CSC file, but I'm still getting hung up at the Samsung Galaxy S7 logo. Do you have a suggestion as to which region's firmware I should use? I have been trying the Australia one from SamMobile's site.
EDIT: And to clarify, I have the G930FD(the duos one).
Click to expand...
Click to collapse
Any region would work, and the F firmware works for the FD too