Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
JasePK said:
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
Click to expand...
Click to collapse
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from (TWRP or CWM) (how to: https://sites.google.com/site/tomsgt123//adb-fastboot)
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: http://www.reddit.com/r/htcone/comments/1rkvy0/help_stuck_in_bootloop_without_access_to_recovery/
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Techngro said:
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from -snip-
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: -snip-
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Click to expand...
Click to collapse
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
JasePK said:
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
Click to expand...
Click to collapse
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
Click to expand...
Click to collapse
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
JasePK said:
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
Click to expand...
Click to collapse
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
cdresor said:
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
Click to expand...
Click to collapse
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
JasePK said:
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
Click to expand...
Click to collapse
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
cdresor said:
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
Click to expand...
Click to collapse
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
JasePK said:
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
Click to expand...
Click to collapse
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
cdresor said:
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
Click to expand...
Click to collapse
No that's alright, I just wanted to know if it was something I should avoid. :laugh: I'll use Odin to flash the official firmware back on regardless.
I had this happen to me, what had occurred was that the efs was corrupt. Here's the fix:
http://forum.xda-developers.com/showthread.php?t=2507403
Now to implement this fix, you must first be able to get into download mode. To do so:
1. Pull the battery
2. Wait 10-20 secs
3. Reinsert battery WHILE holding power button and (volume down + home???, whatever the key combination is)
5. Phone will boot directly to download mode, no logo
6. Flash twrp via odin
7. Phone will reboot into bootloop again
8. Repeat steps 1-4 except this time use the key combination for recovery
9. You must now use adb and push the file I linked to earlier
10. Then without rebooting you must flash it
11. Reboot and problem solved
Fixed issue with continuous recovery boot
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
This is exactly what I posted above lol
LOL Sorry. When I flash the TWRP file it just rebooted the phone back into the Hyper Drive Rom I'm using, did it do the same for you?
Thanks to everyone who has provided information and tried to help me! Thankfully, T-Mobile simply sent me a new phone. However, I'm definitely going to keep this topic bookmarked for future reference. This seems to be a rather uncommon problem, considering I had to make a topic to find a solution since all of my searches didn't give me any results.
Thanks again to everyone!
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
I'm having the same problem with my TMobile Note3 after using Kingo after upgrading via Kies to the latest Firmware. The only difference is my phone immediately starts rebooting as soon as I put the battery back in. It doesn't appear that any keys stop this and the USB isn't recognized by my computer in time before the reboot cycle starts.
Is there anything else to try other than sending the phone back for warranty replacement?
tim
Yeah Kingo has given me nothing but trouble, I'd steer clear of that software. I'm assuming you have no access to recovery mode? I have had that issue before on an S3 and was able to finally get it into download mode, but the battery being inserted immediately boots the phone up. So what you have to do is 1. Take battery out and unplug usb cable. 2. Plug USB cable in and Hold download mode buttons with BATTERY OUT (vol+, home and power) 3. insert battery simultaneously while holding buttons down, phone will boot up.. After holding down for about 10 seconds phone will manually reboot, 4. When screen shuts off (potentially vibrates) release download mode buttons, then IMMEDIATELY press and hold download mode buttons again (must perform this step FAST, the key is to do it right before the screen turns on if you can.) 5. The manual boot you've performed should allow you to trigger download mode. I was eventually able to get this to work (about 3 tries. ) I believe your download mode is still intact, you just have to use this method to access it. Remember that because your phone atuo boots with battery inserted download mode will only be available by manual reboot not battery insert.
Give thanks if I assisted you.. Your phone isn't a hard brick so Jtag service should be unnecessary at this juncture.
---------- Post added at 05:09 AM ---------- Previous post was at 05:01 AM ----------
Awesome!! Glad I could be of such assistance
---------- Post added at 05:13 AM ---------- Previous post was at 05:09 AM ----------
R187J said:
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
Click to expand...
Click to collapse
Awesome man!! Glad I could be of assistance!!
Give thanks/thumbs up!
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks
Related
So, after trying out a few firmwares (JM2, JG8, JM5) and kernels (Samset&OC) I can't no longer boot to recovery with Vol UP + Home + power. I can't really say when this problem first occurred, but maybe with JG8 flash. The strange thing is that I can get to recovery with adb reboot recovery and through android console with reboot recovery (when rooted ofc). Also download mode works great.
Things I have tried:
-flash again to JM2 and JM5 with re-partition checked (512 PIT)
-cleared cache+data through recovery
-factory reset through phone code (this also cleared the internal SD)
-took out the battery multiple times
-booted phone without sim
-flashed phone without sim
-changed CSC with phone code
-restore a nandroid backup of JM2. Recovery worked with this one when I took the backup
-there's no external flash card inserted
Soooo..does anyone have any idea about this kind of problem?
i had a similar problem after trying few ROMs. In my case, when i pres the key combi i get the boot logo and then few seconds later the screen goes black and then i see the boot logo again, and this goes forever. and then i tried pressing the same key combination simultaneously and once i see the boot logo i let go the power button and keep the vol up and home pressed, and then only it went into the recovery mode.
hope it works the same for you
Cheers
Agreed, 99.9% chance you are doing it wrong.
Sent from my GT-I9000 using XDA App
mmthabet: I had the exact same experience. Letting go of the power button when the logo appears lets me enter recovery.
or you may need to take out the battery first for a few seconds... after that, you can reinsert it back and try recovery mode...
at least this work for me...
Thanks for replies but none of the solutions work. The recovery mode button combination DID work for a few weeks, but then just stopped working.
I know that I'm doing it right. I have always pressed vol up and home down until the phone loaded recovery and only briefly pressed power button just at the start. I have also tried to remove battery multiple times and once waited 30 mins before re-inserting it.
Trust me, I'm not doing it wrong :s And recovery is working great through adb reboot recovery and shell.
Darkstriker said:
Agreed, 99.9% chance you are doing it wrong.
Click to expand...
Click to collapse
More so a timing issue. Buttons not pressed at the same time.
I get it all the time for all combo's.
Just keep trying.
You might already have this however just in case you dont, check out Quick Boot.
http://www.appbrain.com/app/com.siriusapplications.quickboot
With this app you can boot into recovery mode. Have to be rooted though.
odyssey61 said:
You might already have this however just in case you dont, check out Quick Boot.
http://www.appbrain.com/app/com.siriusapplications.quickboot
With this app you can boot into recovery mode. Have to be rooted though.
Click to expand...
Click to collapse
this wont work, if you bricked the phone in a bad flash situation.
in times when this app works, you can easily do adb reboot recover
so this app still doesn't address the real issue of how to get the 3 buttons press hardware recovery mode
Laum said:
I know that I'm doing it right. I have always pressed vol up and home down until the phone loaded recovery and only briefly pressed power button just at the start.
Click to expand...
Click to collapse
I release the buttons right when the first Samsung texts comes on the screen. It will take it to Recovery mode. I also had a "boot loop" few times, if I keep pressing the buttons all the time.
Have you tried release your fingers right in the first texts? I really don`t know what is exactly the right way to press the buttons, but this always have took it to Recovery.
Looks like my latest full wipe with *2767*3855# cured it. Flashed JM5-->full wipe-->samset1.9b-->samset kernel and now it works. It must've got stuck somehow in my previous JM5 installation.
I cant get into the download- or recovery-mode by using these keys... so i am not able to flash a new firmware! can anybody help me please? is there a chance to get into the download mode by using an adb-command?
please help i just cant get into the download mode!
Igor02 said:
I cant get into the download- or recovery-mode by using these keys... so i am not able to flash a new firmware! can anybody help me please? is there a chance to get into the download mode by using an adb-command?
please help i just cant get into the download mode!
Click to expand...
Click to collapse
yes
adb reboot download
but it is dangerous, as you can not recover from a bricked state, if your flash is not compatible or if something went wrong with odin, etc.
I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.
arch3rm said:
I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.
Click to expand...
Click to collapse
AHHHHHHHHH OMG, WHY DIDN'T YOU SAY THIS SOONER, like 5 hours ago...
i could have tried that, and not had to send my phone back for "repair"
well i'm sure i'll see that screen again in the future, i'll try that next time
AllGamer said:
AHHHHHHHHH OMG, WHY DIDN'T YOU SAY THIS SOONER, like 5 hours ago...
i could have tried that, and not had to send my phone back for "repair"
well i'm sure i'll see that screen again in the future, i'll try that next time
Click to expand...
Click to collapse
Well I did just get the phone 2 days ago,
Had that problem the same day, discovered the fix two hrs of horror later
Same Problem here i contact samsung here in mexico and a technical aggent tell me if we make a repair our phones we need a jtag and this is so bad alllready contact many people jtag manufacturers in china and honkong trow alibaba.com and no luck don't have other source i try is contact to nspro and z3x and no support for this repairand only hope still have is a reply from the people in the forum SMTi Jtag Repair Tool
Its hard to me go to UK Samsung Service Center i'm in mexico like i said
and i'm waith for a solve this i;m so very sad
http://www.youtube.com/watch?v=g8AIvalzBvY
Darkstriker said:
Agreed, 99.9% chance you are doing it wrong.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I usually release the power button on the boot screen first and then the other two buttons
arch3rm said:
I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.
Click to expand...
Click to collapse
Any idea how long you waited? Been waiting 5 minutes, hasn't shut off. Mine's a Bell though so I'm guessing I won't have any luck.
The way i do it (no chance of doing it wrong and timing):
hold down+home and then also press the power button for a little more then 10 seconds (so all 3 buttons for 10 seconds). The phone will reset into download mode, never fails in whatever mode the phone originaly was..
Hi,
yesterday i got my sgs and first i wanted to update it to JM5.
Because 3 of my friends have the same phone i know what to do.
First i tried to get into download mode but it doesn´t work.
I found here in the forum (thread 749470) "Australia Optus Galaxy S no download mode!" that i´m not the only one with this problem.
Someone told me to use "adb reboot download" to enter download mode - and this worked fine. The working android appeared on the screen.
Odin now found the phone and i tried to flash but it always ended with "file analysis....". So I found help in this forum - restart pc, start odin as admin, use another firmware, try other usb port - nothing happened - last thing: remove the battery for 30sec and try again.
NOW: SGS alway shows the same pic: a phone + ! + PC - but PC can´t find phone, phone can´t be switched off - nothing!
What can I do now except taking the phone back to my dealer?
I appended a pic from my display.
Thanks for your help!
HolyFreak
if you can not get into download mode, then there is no way to fix it
you'll have to send it back to the store, to have it repaired
hmm, you can press at least the power button for 7-10 seconds, then the phone reboots, mybe you are able to go into download or recovery mode, with those button combinations.
but isn't that icon his screen shows, meant to connect the phone to pc and start kies so kies can fix it? (at least i read sth like that on forum) but if this all doesn'T work i don't know
You can always switch the phone off, pull the battery out. ( Avoid doing so when flashing though. )
http://forum.xda-developers.com/showthread.php?t=725858
saldawop said:
http://forum.xda-developers.com/showthread.php?t=725858
Click to expand...
Click to collapse
This guide is really not all that useful.
Take out the battery, and reboot by first pressing voldown+home and then power and wait until you see the yellow download screen.
I'd recommend not doing anything with a phone that you can't get into download mode from a cold start with. Too much can go wrong. Leave it on stock.
I remember seeing that screen when I thought I had bricked my phone, I think I managed to pull back by removing the battery and trying again.
waspbr said:
I remember seeing that screen when I thought I had bricked my phone, I think I managed to pull back by removing the battery and trying again.
Click to expand...
Click to collapse
that is only because your 3 button combination was working
in his case, his 3 buttons are not working
there is a batch of samsung phones that came from factory with the 3 button combo disabled
Having the same issue. Think the stores will replace it under warranty like this?
I can`t get the phone in recovery mode.
Here is the issue:
Running Jedi mind trick rom three weeks. One day the phone restarted and got stuck in the boot screen.
The phone restarted and eventually keeps vibrating without display
After trying many times i did got in recovery mode so i could install the rom again (using darkside super wipe and then the rom). After one day it crashed again and again i installed an different rom which also crashed after several hours.
Now i can`t even get to download mode, Is this hardware related or do i need to use an usb jig to get this working again?
Does your phone screen turn on and at least show the Samsung logo? If not, and you said button combo presses do not work using a USB Jig will be your way to go to get back in to download mode.
By the way, did you flash the correct ROMs specifically for our phones? You shouldn't have experienced and crashes. Also, for the vibrating issue without the display, it had been mentioned that it could also be due to a stuck/dirty power button. If you can try, clean up around it.
FineTalent said:
Does your phone screen turn on and at least show the Samsung logo? If not, and you said button combo presses do not work using a USB Jig will be your way to go to get back in to download mode.
By the way, did you flash the correct ROMs specifically for our phones? You shouldn't have experienced and crashes. Also, for the vibrating issue without the display, it had been mentioned that it could also be due to a stuck/dirty power button. If you can try, clean up around it.
Click to expand...
Click to collapse
Yes it does show the samsung logo at starting up but after that it turns off with 1-2 seconds vibrating intervals.
I already cleaned the power button but without any satisfaction.
I did dropped the phone monday but not from a great heigth.
estimated: 1mtr above ground
Yes i did. I used the guides from galaxy2root.com
Well, if you were able to use a USB Jig to get into 'Download mode', get a stock ROM from here and flash it through Odin which is also included in the link. Good luck!
So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch
neim81094 said:
So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch
Click to expand...
Click to collapse
i think the problem is on power button...
if the power button press contiues will be like that
i meet the same case like u...
sory my englis
press thanks if i help...
I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
It just turned on, I guess it was the power button.
Sent from my SGH-T999 using xda app-developers app
i'm experiencing a similar issue. I can only get any result while it's plugged in. it wont boot past the second splash screen, I got it into download mode and flashed the stock package from sammobile.com with no change. the phone keeps trying to boot into recovery after flashing stock but it goes to the android with the open chest screen and reboots and tries again over and over. i've taken the phone apart and seen nothing wrong, no corrosion, no water damage and i've even replaced the battery with no success. i tried flashing clockworkmod recovery, the flash was successful but it still wont even boot to recovery. the power button isnt stuck, i can manipulate it when i have the bare motherboard in my hands and still it's fine. would replacing the power switch have any affect? please any thoughts would be appreciated
edit: since flashing stock, plugging the phone into the computer with oem cable causes it to vibrate intermittently. holding power causes it to try recovery mode. running windows 7 with samsung drivers properly installed and adb recognizes my galaxy s2 and captivate no problems. someone mentioned on a post i read about using a 3 part stock rom, modem, pda and phone to flash instead of the all in one tar file, any thoughts?
another edit. this phone has never to my knowledge been rooted or had any kernel/rom flashed onto it. as far as i know it's stock from Wind mobile, 3 months past warranty
Hello guys.
I just bought my Pixel 3 XL phone straight from the Google Store and it just arrived two days ago. After learning about Android Q, I opted-in on the android beta and downloaded the Beta 6 OTA update to my phone. The phone downloaded the OTA and installed it and it seems all is well until the moment it rebooted. It didn't turn on again. It won't turn on. I tried to force restart it by pressing the power button 10 seconds, 30 seconds, or even 1 minute+, won't turn on, no haptic feedback, nothing. I even tried the power button + volume down combo. I also tried plugging it to the original charger it came with for 30 minutes, nothing.
Before this, I have experience with flashing stock and custom roms with pixel devices and other brands (I have owned the OG Pixel until it wont boot due to its motherboard issue), and while normally, I could have just unlocked the bootloader and installed the beta firmware thru fastboot/recovery, or even installed a custom recovery, I didn't and instead tried the OTA update thingy (which claimed that you don't have to unlock your phone or anything). I didn't expect that it will brick this early and unexpectedly.
My suspicion would be that the OTA update broke the bootloader itself, or the firmware that loads the bootloader, thus not responding to the power button correctly. It's also not a power problem, because the phone warms up when plugged to the charger. Also, I download and applied the OTA while the phone is charging (around 70%). Could that also be the culprit?
I'm at my wit's end here. I'm thinking I should RMA this phone, which I haven't done before. Are there any similar issues like this before? Did anyone else had similar issues like this one?
wincaffeine said:
Hello guys.
I just bought my Pixel 3 XL phone straight from the Google Store and it just arrived two days ago. After learning about Android Q, I opted-in on the android beta and downloaded the Beta 6 OTA update to my phone. The phone downloaded the OTA and installed it and it seems all is well until the moment it rebooted. It didn't turn on again. It won't turn on. I tried to force restart it by pressing the power button 10 seconds, 30 seconds, or even 1 minute+, won't turn on, no haptic feedback, nothing. I even tried the power button + volume down combo. I also tried plugging it to the original charger it came with for 30 minutes, nothing.
Before this, I have experience with flashing stock and custom roms with pixel devices and other brands (I have owned the OG Pixel until it wont boot due to its motherboard issue), and while normally, I could have just unlocked the bootloader and installed the beta firmware thru fastboot/recovery, or even installed a custom recovery, I didn't and instead tried the OTA update thingy (which claimed that you don't have to unlock your phone or anything). I didn't expect that it will brick this early and unexpectedly.
My suspicion would be that the OTA update broke the bootloader itself, or the firmware that loads the bootloader, thus not responding to the power button correctly. It's also not a power problem, because the phone warms up when plugged to the charger. Also, I download and applied the OTA while the phone is charging (around 70%). Could that also be the culprit?
I'm at my wit's end here. I'm thinking I should RMA this phone, which I haven't done before. Are there any similar issues like this before? Did anyone else had similar issues like this one?
Click to expand...
Click to collapse
Plug the charger in and hold all 3 buttons together, not saying it will work but worth a try, it deletes battery stats and cache, if it does boot then keep hold of them for about 40 secs, hold them for over ten seconds even try for a whole minute, this sounds like hardware fault to me though. Also, if youve just bought it, swap it.
boe323 said:
Plug the charger in and hold all 3 buttons together, not saying it will work but worth a try, it deletes battery stats and cache, if it does boot then keep hold of them for about 40 secs, hold them for over ten seconds even try for a whole minute, this sounds like hardware fault to me though. Also, if youve just bought it, swap it.
Click to expand...
Click to collapse
I have tried what you suggested. Still nothing.
If I can I'd try to resolve this without returning the thing but yeah, it may really be a hardware fault. Guess I have to wait for a miracle to happen (like the phone turning on by itself after several hours, like with some posts that I have found around).
If all else fail, maybe I'd just ask Google to replace it.
Thanks anyway :good:
You may want to try to see if you get a USB notification from your computer on Windows and if it does try to flash it Back to stock. Hope it works
Sent from my SM-G975W using Tapatalk
kentek said:
You may want to try to see if you get a USB notification from your computer on Windows and if it does try to flash it Back to stock. Hope it works
Sent from my SM-G975W using Tapatalk
Click to expand...
Click to collapse
I also have tried that to no avail. The phone won't just turn on. Anyway I already returned the device. Thanks
wincaffeine said:
I also have tried that to no avail. The phone won't just turn on. Anyway I already returned the device. Thanks
Click to expand...
Click to collapse
Have you tried making an edl cable, to see if the phone boots to qualcomm flash/diagnostic mode. I dont understand why no one in this thread as mentioned EDL mode, its a life saver for when you brick your device. This allows a full factory image flash through qualcomm flash mode. Plenty of tuturials on internet for EDL. (Emergency Download)
boe323 said:
Have you tried making an edl cable, to see if the phone boots to qualcomm flash/diagnostic mode. I dont understand why no one in this thread as mentioned EDL mode, its a life saver for when you brick your device. This allows a full factory image flash through qualcomm flash mode. Plenty of tuturials on internet for EDL. (Emergency Download)
Click to expand...
Click to collapse
Because of warranty?