[Q] Galaxy note II bootloop problem. worst i have faced! - Galaxy Note II Q&A, Help & Troubleshooting

Hey guys....im new on xda i had a problem. recently my phones in a bootloop.i did not drop it or try to flash a custom rom. it was in a bag for 2 hours after which it just starts up to the white logo and not even the animated one and keeps repeating that. i have tried pulling out the battery for long times and letting the charge drain out thing but in vain. worst part is i caannot get into recovery or donwload mode. download mode flashes for a few seconds but just reboots. recovery mode doesnt work at all. i however managed to boot into download mode. once the download mode warning appeared i pulled out the battery with the usb cable in it. but thats as far as i got. i cannot flash a rom on to it either becasue it needs to restart i guess and wihtout a battery thats not possible..........i thought of trying out cwm becasue that had usb debugging turned on as default and then using abd command line to retrieve my data but for that i need to get into download mode. even checked out the power button problem but the button was fine.....im running out of options....my phone is not rooted.....any suggestions guys?....really need help saved up a lot to buy this :crying::crying:

DoomsDrag426 said:
Hey guys....im new on xda i had a problem. recently my phones in a bootloop.i did not drop it or try to flash a custom rom. it was in a bag for 2 hours after which it just starts up to the white logo and not even the animated one and keeps repeating that. i have tried pulling out the battery for long times and letting the charge drain out thing but in vain. worst part is i caannot get into recovery or donwload mode. download mode flashes for a few seconds but just reboots. recovery mode doesnt work at all. i however managed to boot into download mode. once the download mode warning appeared i pulled out the battery with the usb cable in it. but thats as far as i got. i cannot flash a rom on to it either becasue it needs to restart i guess and wihtout a battery thats not possible..........i thought of trying out cwm becasue that had usb debugging turned on as default and then using abd command line to retrieve my data but for that i need to get into download mode. even checked out the power button problem but the button was fine.....im running out of options....my phone is not rooted.....any suggestions guys?....really need help saved up a lot to buy this :crying::crying:
Click to expand...
Click to collapse
Your battery is faulty. All those things you mentioned are signs of a dyeing battery. Get it replaced or borrow a battery from your friend to check it out.

mannyvinny said:
Your battery is faulty. All those things you mentioned are signs of a dyeing battery. Get it replaced or borrow a battery from your friend to check it out.
Click to expand...
Click to collapse
Are you sure? because the first thing i did was use a battery from a different phone....a grand, just aligned the terminals and held it in place with my hands....phone seemed to go into bootloop again????

Related

Did I just BRICK my G Nexus?

So, last night I was out and about - just having a good time. Noticed that the battery on my GSM Galaxy Nexus was getting low. Went "Meh, wasn't the first time it's died." It got to 1% battery power and shut-off, like it normally does. Me being who I am, I turned it back on to see just how much more juice I could get out of it.
Phone booted up alright. Finished the boot animation, and then a couple seconds later turned off.. not a big deal. I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
I'm not talking about the regular charge screen. After the battery gets 'filled' twice, it completely restarts. Black screen for 2 or so seconds, and then it goes through the charge animations as it would if you had just pluggied it in. I CAN get into bootloader, but that's about it. I'm just curious.. has anyone seen this before? Or know what my problem might be?
I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Try going into recovery and wiping cache and dalvik. If that doesn't work reflash your rom
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
i.vt3c.d0hc said:
[snip]
I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
Click to expand...
Click to collapse
Turn it off. Leave it charging for a few hours before turning it on.
i.vt3c.d0hc said:
[snip] I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Click to expand...
Click to collapse
You do not need to have USB debugging enabled to use fastboot.
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
It doesn't take long at all to install the drivers. Look for a thread with "universal" in the title. I think it is in GN General. Once you do install the fastboot driver, download the fastboot.exe file and reflash the stock ROM.
Diger36 said:
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
Click to expand...
Click to collapse
It's volume up and the power button.
Sent from my Galaxy Nexus using Tapatalk
The problem I have is that the charge animation doesn't change... i.e. It'll constantly refill the battery and all, but it always starts from the bottom (While when a phone is say... half charged, the little battery is half filled and the animation continues.
I'm not sure it's even charging at all.
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
i.vt3c.d0hc said:
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
Click to expand...
Click to collapse
Power down phone, do a long battery pull, place it inside again, let it charge for a few hours without powering it on, when it is fully charged (or after a few hours) pull battery again and then take charger out the phone. After a few minutes, place battery inside phone again and start it up without the charger.
Hope that works.
Sent from my Galaxy Nexus using xda premium
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
i.vt3c.d0hc said:
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
Click to expand...
Click to collapse
You could always try a new battery
Sent from my Galaxy Nexus using xda premium
+1 for the new battery thought.
Battery test
I am having a similar problem, I get the boot loop.
Difference is that I had started with a new battery so that could be your problem or unrelated. I went to a mobile shop yesterday and they let me use a new battery to see if the loop would start. It did not so there seems to be at least one other failure path. I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
I posted to this thread #192
http://forum.xda-developers.com/showthread.php?t=1490815
My Galaxy Nexus phone from WIND went into a reboot loop yesterday. It had been charged to 98%, used to make a call and then put away. Wireless was enabled. Noticed vibration periodically and say it was rebooting every 6 - 7 seconds. Pulled battery to stop reboot. Saw references to fully charged battery via USB stops reboot loop so tried that. Battery voltage was 4.17V and still went into reboot loop.
Tried to boot into safe mode but still goes into a loop
I went into recovery mode and tried all options but factory reset because I am hoping to recover some pictures
reboot system now
apply update from cache (but did not have an update to install as only options were ../ lost+found/ recovery and when I selected these was in a loop as well)
wipe cache partition
Can't tell what version of Andorid I have as the phone never finishes booting.
Boot console gives the following information
Product Name – tuna
Variant – maguro
HW version – 9
Bootloader version – PRIMEKK14
Baseband version – I9250UGKL1
Have installed SMS backup because I was planning to do a backup after a trip. Also have two GPS tracker apps installed.
GNMO15 said:
[snip]
I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
Click to expand...
Click to collapse
If you can boot into recovery, you may be able to get your pictures off your device.
1) Make sure you have the drivers for your device properly installed on your computer.
2) Download the attachment and unzip it to a directory on your computer.
3) Open a command prompt in the same directory.
4) Reboot your device into recovery and plug into your computer.
5) Make sure your computer sees your device by typing: adb devices
6) Pull the data off your device by typing: adb pull /data/media
Note: depending on how much data you had on /sdcard, this could take a while, so be patient.

[Q] Can't boot to recovery or download mode

It is a long story, started with wanting Photoshare App. After rooting using Odin got into all sort of process stopped error. Desperate, downloaded and tried to flash CM10 using CWM. All I got was CM logo circling endlessly for 30 minutes. Pulled the plug and now, I seem to have a brick, can't even boot to recovery or download mode. When I try to boot to downlad mode, the warning screen appears for just a second and goes away. When I try recovery mode Samsumg log appears and then blank.
Is there anything I can do at this point? I appreciate any help I can get.
dileepan said:
It is a long story, started with wanting Photoshare App. After rooting using Odin got into all sort of process stopped error. Desperate, downloaded and tried to flash CM10 using CWM. All I got was CM logo circling endlessly for 30 minutes. Pulled the plug and now, I seem to have a brick, can't even boot to recovery or download mode. When I try to boot to downlad mode, the warning screen appears for just a second and goes away. When I try recovery mode Samsumg log appears and then blank.
Is there anything I can do at this point? I appreciate any help I can get.
Click to expand...
Click to collapse
Hm. if you boot up your phone are you stuck at the cm bootup? If you are im sorry bro you cant fix it for free by sending it to samsung. JTAG for 60 bucks or samsung for 60 bucks. Reason being that it shows that you have rooted and modded your device. If you were hardbricked and nothing would turn on at all you would be able to send it to samsung and get it fixed for free!
Well if it shows Download mode then it might be working, just not showing, if you see a blue ID:COM number in Odin its working. Try to flash a stock ROM in Odin while in Download mode and make sure its in PDA or you will brick. Check only Auto-Reboot and F. Reset time.
If it works congrats if not search this forum for a service called JTAG which repairs bricks.
\(._.\) To the window, to the wall.
(/._.)/
A little update ...
I was able to get to download mode after many trys and got back to stock -- unrooted. I should have stopped when I was ahead, but I was feeling invincible after this feat of reviving the phone and that was really stupid.
I wanted to root and flash CM10 nightly. I followed the instructions from http://rootzwiki.com/topic/32486-gu...m10-nightlies-without-k-exec-updated-8-18-12/. After unlocking the bootloader step, I wanted to backup the stock ROM I had on the phone -- I don't know why I wanted to do that as I had just flashed the stock and didn't have anything customized. Anyway, when I clicked backup from CWM everything died, kaput, nothing. I have been desperately holding the power button, reovery combination of buttons, download mode combination, anything I can think of, the phone is giving me the total silent treatment, which BTW I am used from a more human source.
Let me know if there is anything I can do, perhaps stand on one leg and try switching it on perhaps. http://forum.xda-developers.com/images/smilies/redface.gif
Sorry for the dumb jokes, I am a little frustrated, but I am sure I will get over it.
Thanks for those who took interest to read my question and those who cared to respond, I appreciate it....
Cheers!
are you getting any signs of life with the phone plugged in with or without the battery in?
jeeper11 said:
are you getting any signs of life with the phone plugged in with or without the battery in?
Click to expand...
Click to collapse
Absolutely nothing, not even the light that comes on when plugged in for charging.
best ...
dileepan said:
Absolutely nothing, not even the light that comes on when plugged in for charging.
best ...
Click to expand...
Click to collapse
Best advice...take out the battery, leave for 1-2 hours, insert battery, try to access download, flash stock in odin, reboot, don't flash any more Jelly Bean roms. lol

[Q] Samsung Note N7100 stuck boot loop when unplug,but when charging loads the KitKat

Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
Ive just encountered the same problem. Were u able to find a solution?
Shahin7631 said:
Ive just encountered the same problem. Were u able to find a solution?
Click to expand...
Click to collapse
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
anish100 said:
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
Click to expand...
Click to collapse
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
GStriker said:
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
Click to expand...
Click to collapse
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
GStriker said:
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Click to expand...
Click to collapse
Ive literally tried everything .even repartioned the phone . it works fine in recovery and download mode but as soon as i want too boot to android unplugged it restarts . when plugged it has no problem
Funny thing. I have a factory Sprint Note 2 with the latest kitkat updat and I am experiencing the same problem. Phone has not been rooted or messed with. If anybody come across a solution let me know. I booted the phone and unplugged the power button to verify and it does the same thing. Only stays on when in airplane mode or charging.
One more thing. I tried somewhat to do what was posted above about performance / cpu power. I put the phone in powersave mode and checked limit cpu and is is fully operation. problem gone. If I turn power save mode off I'm back to square one.
To late. Took a picture by mistake and phone jumped into boot loop.
i have GT-N7100 and same problem phone is stuck on boot loop when unpluged
---------- Post added at 04:22 PM ---------- Previous post was at 03:24 PM ----------
i just tought maybe it needs new battery. cause before i unpluged it it showed 67% then bootlooped 2x then i pluged back in and it shows me only 5%. i think its battery cause it cant dishcharge in 1 or 2min
My initial problems were that it would drop signal and show an x with no bars intermittently. then i started having problems anytime the phone demanded use. Picture, internet, video. tried a few things listed above. Still would go into a boot loop when not plugged in. Battery would charge normally and show it percentage like normal. It would reach 100% with no difference in charge time. When battery saver is on it would not have a problem unless I use an app that demands more cpu usage, network connection, battery consumption. Put a new battery and problem is gone. some people say the battery show swelling but my battery looks identical to the new one. no swelling and it is not deformed in any way.
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Shahin7631 said:
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Click to expand...
Click to collapse
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
dcmobiletech said:
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
Click to expand...
Click to collapse
Ive tried already with another battery ....its a very strange situation while everything works fine in download or recovery mode when its unplugged ...i have ordered a third party battery to see if it'll make a difference or not ....i'll keep u updated tomorrow
GStriker said:
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
Click to expand...
Click to collapse
Where is the Preferences section? I am unable to find that on my Note 2 settings.
Experienced the same thing and this is the first time I had this. I was playing a game after I fully charged my battery and suddenly it turns off. So I waited for it to turn on where I noticed that it keeps on turning on and off and stuck on the " Samsung Galaxy Note 2" logo screen. Then I tried several things like clearing the cache and dalvik but it just do the same thing. I re-flashed the 4.4 ROM that I was using but sadly it does the same thing. I then noticed that if I plug in the charger it works normally and does not boot loop. And as soon as I remove the charger it will keep on restarting on and off on that screen. I was thinking that it might be a hardware failure or the battery itself. So I went to recovery mode and unplugged the charger, it stays on. Went to download mode without the charger and it stays on. Freakin' weird. I am about to flash a different ROM and will wipe everything and see what happens...
Fully charged the battery to 100%, unplugged the charger and it started to boot loop again. I allowed it to boot loop once and immediately went to recovery mode and saw that my fully charged battery went down to 3%. Tried different ROMS (Omega, DN3, and Phoenix), I still have this issue. Now can use my Note2 as long as the charger is plugged in...
Change your battery and solve the problem ?
Sent from my GT-N7100 using XDA Free mobile app
I did. Case closed!
red_hanks said:
I did. Case closed!
Click to expand...
Click to collapse
is it working fine after battery change? does it still get stuck in boot loop? mobile networks?
It works perfectly !

T999 Won't boot/start

Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.
DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.
DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited
Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.

Phone won't boot up or charge

Hello there Beautiful People,
Yesterday i tried to root one of my former phone as a test if i could root current one cause im interested in it, it was my first to root, i was able to unlock oem and everything after i tried to flash the magisk image i accidentally wrote it to the system partition instead of boot one and i was stuck in a boot loop, i figured that too after booting into Recovery Mode and after that i went for the "Power Off" mode and after that my phone stopped booting and charging, i just wonder if there's anything i could do with it or its now completely dead forever. Thank You for your time.
UPDATE: i was able to bring it back to life after 5 hours of suffering.
Try changing the battery outside the phone on a stand-alone charger or in another phone.
Salvadorfreeman said:
Try changing the battery outside the phone on a stand-alone charger or in another phone.
Click to expand...
Click to collapse
i tried that, phone shows no sign of turning even though i pressed power button and volume down button at the same time for about 5 minutes
UPDATE: i was able to bring it back to life after 5 hours of suffering.

Categories

Resources