GT-N5100 After OTA 4.2.2 stuck in safe mode. I didn't expect problems from a stock update.
It was working perfectly yesterday. I have wiped it clean, no change.
Kies doesn't seem to offer anything that will recover it.
Does anyone have 4.1.2 for North America? It is the international version tablet.
The one strange thing is that the volume down button does not work now.
Baseband version: N5100XXCMJ2
Build Number: JDQ39.N5100XWCNA1
Any ideas?
Dulie said:
GT-N5100 After OTA 4.2.2 stuck in safe mode. I didn't expect problems from a stock update.
It was working perfectly yesterday. I have wiped it clean, no change.
Kies doesn't seem to offer anything that will recover it.
Does anyone have 4.1.2 for North America? It is the international version tablet.
The one strange thing is that the volume down button does not work now.
Baseband version: N5100XXCMJ2
Build Number: JDQ39.N5100XWCNA1
Any ideas?
Click to expand...
Click to collapse
Try volume up and hold until you see the Samsung on the screen. I use that to boot when hung with odd firmware issues arise.
You can try going into stock recovery holding down home, volume down and power key when powering up.
If you get the notice... you should be able to connect via USB to your computer and use Odin 3.7 and flash a compatible ROM for your device, if available. I don't have a 5100, so I am not able to assist in locating one for you. You should state what carrier your tablet is with. So others can assist with the right ROM.
gooberdude said:
Try volume up and hold until you see the Samsung on the screen. I use that to boot when hung with odd firmware issues arise.
You can try going into stock recovery holding down home, volume down and power key when powering up.
If you get the notice... you should be able to connect via USB to your computer and use Odin 3.7 and flash a compatible ROM for your device, if available. I don't have a 5100, so I am not able to assist in locating one for you. You should state what carrier your tablet is with. So others can assist with the right ROM.
Click to expand...
Click to collapse
T-mobile is my carrier. I tried the phone and text messages and they are not working, yet the mobile data is.
When I tried the home/voldwn/pwr I get the
Warning!
A custom os can cause critical problems in phone and installed applications.
If you want to download a custom os,press vol up key.
Otherwise, press the volume down key to cancel.
At this screen I can't press either button. Neither will do anything. I know the volup was just working.
I get different screens by either using the volup or voldwn. So this would indicate the vol buttons are fine as I knew yesterday.
I also was not wanting to do anything to void the warranty at this point since it is less than 1 month old.
OK, well then as long as it was an OTA and you did not root... I would take it back to T-mobile and ask for a replacement. They should be able to give you a replacement if they cannot reload the ROM and correct the issue.
gooberdude said:
OK, well then as long as it was an OTA and you did not root... I would take it back to T-mobile and ask for a replacement. They should be able to give you a replacement if they cannot reload the ROM and correct the issue.
Click to expand...
Click to collapse
Samsung said to stop by a best buy where the samsung store is inside and have them reflash it with a US carrier firmware.
That seemed like a good idea, but he was unable to get to his server where the firmware resides. He also made mension of the fact they have heard of this model having these issues. So he was unable to do anything after an hour of computer issues with reaching their internal site.
Stuck in "Safe Mode" Issue Corrected
:laugh:
The Samsung reps at my local BestBuy could not fix it. They said they could fix anything. Not this apparently.
I remember that sometimes after firmware loads need to be cleared out. So I found this procedure, which is part of a manual firmware update, and figured maybe it would clear the issue causing safe mode.
If Galaxy Note 8.0 N5100 stuck at booting animation after Step 10 then go to recovery mode (press and hold the Volume Up, Home and Power buttons together) and perform Wipe data/Factory Reset and Wipe Cache Partition task before selecting reboot system now function. In recovery mode use Volume keys to navigate between options and Power key to select the option. Please note, performing wiping task will erase your device internal memory data and not external SD card data.
YES, no more safe mode!!
Related
So a friend of mine was updating ClockWorkMod and within about two reboots his phone would only flash the Samsung logo that pops up when the phone first turns on then nothing would happen (black screen). He reflashed the last version of CM stable (CM 10.1.2 for d2att) and nothing changed.
So I figure, we can just flash back to stock via ODIN but the device will only enter Download Mode for about a split second; it shows the green Android then flashes away to a black screen just like bootup. There was a video taken of the text in the corner, the flash counter was incremented and it said something like "QUALCOMM SECUREBOOT: ENABLED"
To be clear, we can enter CWM recovery just fine with no hiccups but we can't enter Download Mode or boot the device. I've tried booting into each mode with the device plugged into a computer and ADB will only recognize it in recovery mode, not in Download or normal bootup.
Is this a hardware failure? I can't tell and I'm not sure how to proceed. Would a Jig help?
Any help would be appreciated.
EDIT: It has now been discovered and confirmed that a loose power button is the culprit here.
Do you have access to a USB jig to force the phone into download mode?
audit13 said:
Do you have access to a USB jig to force the phone into download mode?
Click to expand...
Click to collapse
We don't but we're skeptical of it working; we fear that once it's in Download Mode and we unplug the Jig so we can plug the phone into the computer, it will turn off.
It does seem like our only option however; do you think we should go ahead and order one?
hakoda said:
We don't but we're skeptical of it working; we fear that once it's in Download Mode and we unplug the Jig so we can plug the phone into the computer, it will turn off.
It does seem like our only option however; do you think we should go ahead and order one?
Click to expand...
Click to collapse
Since you can get into recovery mode, can you try flashing a stock file via recovery? You can use another device (another phone, SD card reader/writer, card adapter, camera etc) to copy the flashable zip to an SD card, then place the card in your phone and install via recovery. I'll suggest you use the MJ2 (modified 4.3 stock ROM) so you don't lock yourself into the 4.3 bootloader yet. Please check the instructions to see if you'll require the kernel and modem zips as well. If this doesn't work, then you have a hardware problem and not firmware.
http://www.androidfilehost.com/?fid=23196940996968760
Larry2999 said:
Since you can get into recovery mode, can you try flashing a stock file via recovery? You can use another device (another phone, SD card reader/writer, card adapter, camera etc) to copy the flashable zip to an SD card, then place the card in your phone and install via recovery. I'll suggest you use the MJ2 (modified 4.3 stock ROM) so you don't lock yourself into the 4.3 bootloader yet. Please check the instructions to see if you'll require the kernel and modem zips as well. If this doesn't work, then you have a hardware problem and not firmware.
http://www.androidfilehost.com/?fid=23196940996968760
Click to expand...
Click to collapse
When I attempt to flash the ROM on CWM, it says something about "script aborted: status 7 (expected 5 arguments, got 3)". Sounds like the way CWM is formatting and mounting the partitions differently than stock recovery.
hakoda said:
When I attempt to flash the ROM on CWM, it says something about "script aborted: status 7 (expected 5 arguments, got 3)". Sounds like the way CWM is formatting and mounting the partitions differently than stock recovery.
Click to expand...
Click to collapse
You should load an updated version of CWM. The status 7 error can occur if the ROM is too new for the recovery.
A jig may work but try updating recovery and flashing first.
audit13 said:
You should load an updated version of CWM. The status 7 error can occur if the ROM is too new for the recovery.
A jig may work but try updating recovery and flashing first.
Click to expand...
Click to collapse
CWM was already updated to its latest; so a TWRP 2.7.0 flashable zip for d2att was executed to see if that would fix the flashing issue but now it won't enter recovery at all
Starting to think the power button is stuck
hakoda said:
CWM was already updated to its latest; so a TWRP 2.7.0 flashable zip for d2att was executed to see if that would fix the flashing issue but now it won't enter recovery at all
Starting to think the power button is stuck
Click to expand...
Click to collapse
You could try and see what happens when you remove and replace the battery. Usually, with stuck power button, the phone tries to power on immediately the battery is inserted even when you don't press the power button. Unless, of course, something is broken or dislodged inside. It could indeed be you have a combo hardware/firmware problem. The firmware problem can be easily fixed by flashing a correct and working ROM but you need to be able to get the device into recovery/download first.
Larry2999 said:
You could try and see what happens when you remove and replace the battery. Usually, with stuck power button, the phone tries to power on immediately the battery is inserted even when you don't press the power button. Unless, of course, something is broken or dislodged inside. It could indeed be you have a combo hardware/firmware problem. The firmware problem can be easily fixed by flashing a correct and working ROM but you need to be able to get the device into recovery/download first.
Click to expand...
Click to collapse
The insertion of the battery definitely turns on the phone; it's the only way we've been turning the device on and off.
Tapping the front/back of the phone near the power button also seems to randomly wake the device and frankly would explain a lot.
Thanks for the help guys
hakoda said:
The insertion of the battery definitely turns on the phone; it's the only way we've been turning the device on and off.
Tapping the front/back of the phone near the power button also seems to randomly wake the device and frankly would explain a lot.
Thanks for the help guys
Click to expand...
Click to collapse
Sounds like a stuck power button then. Thankfully, this can be routinely fixed at a tech shop or by yourself if you have the right tools and skills for this. Sometimes it doesn't even require replacement of the power button which can be bought cheaply on places like that online auction site.
Larry2999 said:
Sounds like a stuck power button then. Thankfully, this can be routinely fixed at a tech shop or by yourself if you have the right tools and skills for this. Sometimes it doesn't even require replacement of the power button which can be bought cheaply on places like that online auction site.
Click to expand...
Click to collapse
Can confirm that it's a stuck power button; tapping it continuously with an end of a chapstick tube while the phone booted got us all the way into Cyanogenmod; we confirmed that TWRP flashed successfully as well. However, we as soon as we stop tapping it, it goes back to the previous behavior.
We're now looking for some guides online to fix it, seems mechanical if tapping it continuously will keep it unstuck for short amount of time.
Thanks again guys
I have a rooted I747 with an android 4.3 rom. The LCD is broken and I am looking to sell it as is. I am wondering if it is possible to factory reset the device with a PC (possibly with kies, odin, or adb). I have seen a kies tutorial but it bricks devices running android 4.3. Any input would be greatly appreciated, thanks in advance.
efaustus9 said:
I have a rooted I747 with an android 4.3 rom. The LCD is broken and I am looking to sell it as is. I am wondering if it is possible to factory reset the device with a PC (possibly with kies, odin, or adb). I have seen a kies tutorial but it bricks devices running android 4.3. Any input would be greatly appreciated, thanks in advance.
Click to expand...
Click to collapse
If the phone still has a stock recovery you can boot into it and factory reset the device. Getting into stock recovery and using it is all done with the volume rocker and power buttons, so the broken screen won't be a problem.
jason2678 said:
If the phone still has a stock recovery you can boot into it and factory reset the device. Getting into stock recovery and using it is all done with the volume rocker and power buttons, so the broken screen won't be a problem.
Click to expand...
Click to collapse
Thanks, I've found that method elsewhere;
Enter recovery by holding the volume up, home button and power button simultaneously while booting. Wait 20 seconds after first vibration. After 20 seconds push the volume down button three times, then press the power button, wait for vibration and reset should be complete.
I am still somewhat curious to know if it is possible to do it remotely with a PC.
Best method I can think of from a PC would be flash this with Odin: http://forum.xda-developers.com/showpost.php?p=52341560&postcount=227
Only flash that if you're sure you were on stock 4.3 with MJB firmware, or you'll brick. Did you have ADB enabled before the screen broke? It would give you a method to check firmware without the screen.
Sorry about the post above. You said broken LCD, but I heard broken digitizer. I thought you could still see what you were doing. I still think stock recovery could work in a pinch; just find a Youtube video and mimic it. Sounds like you've already got the button presses down. Good luck
My wife's old S3 was given to me to use. I had originally flashed CM 11 on it and tried to upgrade to CM 12.1. In doing so I accidentally forgot to flash GAPPS.
I reverted to the stock ROM via Odin but now I'm stuck in a boot loop. The best part? The device's power button does not work and I cannot make any selections within the stock recovery to clear the cache and reset to factory settings.
Can anyone help me?
Pull the battery to turn off the phone and put it back in. If you feel the phone power up by vibrating upon putting the battery in and not touching the power button and go into loop then you have a bad power button. Do you have this problem? If so, then your only options are repair or remove the power button (there is an alternate way to power the phone up). Let us know if it is a bad power button or not so that hardware issues can be accounted for and go from there.
NOTE: The S3 has been known for some time now to have power buttons that fail. Mine did, and I opt to remove mine as I could not justify paying for a repair when the S3 is my backup phone and test platform and I have a method to power up. I use widgets for controlling power off, restarts, and recovery once powered up.
I no longer have a power button either and recently encountered this same issue after using Odin to flash a stock image.
My solution was to flash TWRP recovery using Odin, which allows one to perform operations using touch instead of the power button.
Gargat said:
I no longer have a power button either and recently encountered this same issue after using Odin to flash a stock image.
My solution was to flash TWRP recovery using Odin, which allows one to perform operations using touch instead of the power button.
Click to expand...
Click to collapse
That works. Glad you found a way to get through it.
n_alvarez2007 said:
My wife's old S3 was given to me to use. I had originally flashed CM 11 on it and tried to upgrade to CM 12.1. In doing so I accidentally forgot to flash GAPPS.
I reverted to the stock ROM via Odin but now I'm stuck in a boot loop. The best part? The device's power button does not work and I cannot make any selections within the stock recovery to clear the cache and reset to factory settings.
Can anyone help me?
Click to expand...
Click to collapse
Bootloops have not been uncommon when reverting from LP to KK. Once you have flashed TWRP as others in the thread have suggested, you will probably need to wipe/ format the internal sdcard. The other remedy some have posted is to load a stock recovery and do a factory reset from within that stock recovery.
Not sure how to get into recovery without a power button.
Is the button loose or not functioning at all? You could try opening the phone and removing everything from the frame and see if the power button functions.
I haven't tried this with my SGS3, but on my Acer tablet I have booted into recovery using adb and fastboot. This requires connection to a computer, but not a power button. Unless you have a touch version of a custom recovery installed you still would not be able to select an item.
You may be able to flash a custom recovery using adb. I had broken my stock recovery on that tablet and used fastboot to reflash a working stock recovery.
Im looking to flash my galaxy s7 active because, for some unkown reason the os is corrupt or has a virus.
I have not downloaded anything, all i did was charge it while i slept, picked it up an hour ago and the voulme keeps going down no matter if i press the key or not, the button isnt damaged the voulme menu never leaves the top of device like some ghost hand is permently holding back on the volume dunno wtf that is. I did a factory reset, that didnt fix the issue. The phone is permmently stuck in safe mode, I have tried to enter recovery mode and it gets stuck in a boot loop or opens the light blue screen with the explaination point, the only options is download custom os or cancel. I would like your help on what software i need to fix my somehow randomly damaged device.
Andriod version 7.0
Model number: sm-g891a
jinakanishi said:
Im looking to flash my galaxy s7 active because, for some unkown reason the os is corrupt or has a virus.
I have not downloaded anything, all i did was charge it while i slept, picked it up an hour ago and the voulme keeps going down no matter if i press the key or not, the button isnt damaged the voulme menu never leaves the top of device like some ghost hand is permently holding back on the volume dunno wtf that is. I did a factory reset, that didnt fix the issue. The phone is permmently stuck in safe mode, I have tried to enter recovery mode and it gets stuck in a boot loop or opens the light blue screen with the explaination point, the only options is download custom os or cancel. I would like your help on what software i need to fix my somehow randomly damaged device.
Andriod version 7.0
Model number: sm-g891a
Click to expand...
Click to collapse
Your phone doesn't have a virus. The fact that you already did a factory reset has already reverted your OS back to retail apps and settings, just like how you first got it.
Given the scenarios you provided, it seems that your volume down-button is indeed "stuck" internally (for some reason). Samsung's universal safe mode trigger is to "press-hold down button while booting"--since your vol-down button is stuck, every time you boot, it will always be in safe mode.
You might want to remove the phone case if you have one installed. Then try to inspect the volume down button a bit closer. If all else fails, get a replacement/warranty or something similar (if still in scope). It could be a hardware defect that just popped up.
Goodluck
jembot said:
Your phone doesn't have a virus. The fact that you already did a factory reset has already reverted your OS back to retail apps and settings, just like how you first got it.
Given the scenarios you provided, it seems that your volume down-button is indeed "stuck" internally (for some reason). Samsung's universal safe mode trigger is to "press-hold down button while booting"--since your vol-down button is stuck, every time you boot, it will always be in safe mode.
You might want to remove the phone case if you have one installed. Then try to inspect the volume down button a bit closer. If all else fails, get a replacement/warranty or something similar (if still in scope). It could be a hardware defect that just popped up.
Goodluck
Click to expand...
Click to collapse
It had to have been a virus or corrupt os, I restarted into recovery and flashed it to stock and it works perfectly now with no issues, the button was not stuck internally or externally, as pressing it caused no issues as well as if the device button was stuck it should have navigated the recovery menu if it was stuck. either way after flashing it works perfectly so no it wasnt stuck, and besides i have a galaxy s7 active, trying to disassemble that thing is a nightmare
[SOLVED] Download mode can't be removed, I had to try all dat long but I finally could boot into it.
Hi,
So... I had a working Samsung Galaxy S9 (SM-G960F/DS) running Lineage OS yesterday. I noticed something wrong related to the mobile network in my country (FR) and decided to flash the correct stock firmware matching the country code XEF before doing a full LOS reinstall.
Fast-forward 20hrs of download, I perform the flash operation this morning using heimdall(1) and reboot.
Now, the phone bootloops. I can't get into download mode as usual, and the only thing that is available is the stock recovery mode that allows:
apply update from adb
apply update from sdcard
wipe data
wipe cache
mount /system
view logs
run graphics test
I have a working all-countries firmware archive that contains the one that was working previously (minus the mobile network problem). But since I don't have download-mode anymore I can't install it. I tried adb sideload (which is available via the "apply update from adb" option), wipe data/cache to no avail.
Is that hard-brick? Did you ever experience a similar situation? I think there's no way out of this but any advice would be appreciated.
Thanks again!
You should be able to get into Download Mode (Vol Down & Bixby & Power)
Keep trying, try keeping hold of the button combo until after the phone reboots twice hopefully the second time into download mode
Download mode has nothing to do with firmware or recovery that has been flashed, and if you can enter recovery mode, it doesn't sound like a hardware problem either
And use a Windows machine & ODIN 3.13.1 to flash stock
Unfortunately it doesn't seem to work, i tried many tiimes and I usually can do that very easily. It seems flashing the corrupted images wiped it out.
mateba said:
Unfortunately it doesn't seem to work, i tried many tiimes and I usually can do that very easily. It seems flashing the corrupted images wiped it out.
Click to expand...
Click to collapse
Impossible as it is not part of the firmware, nor can be touched by firmware, it is part of the hardware (Think BIOS vs OS)
You can even 100% wipe all internal storage clean so there is no OS at all and download mode will still work fine
Keep trying
Okay I guess it's possible that the download mode is still there but I can't reach it.
I've been trying hundreds of times every combination I can think of (including Home + Vol Down + Power that used to work).
Any alternative way to trigger the download mode ?
How are you trying Home? There is no physical home button
The button combo is Vol Down & Bixby & Power from a powered off state
Keep a hold of all 3 until it hits the Warning screen, then hit Vol Up to enter Download mode
No other way to access it that I know of, USB Jig hasn't worked since a few models back
Have you tried factory resetting from inside recovery? Unless you used CSC during the stock firmware flash, that could be a reason for the bootloop
*Detection* said:
How are you trying Home? There is no physical home button
Click to expand...
Click to collapse
Yeah sorry, speaking of the Bixby button.
*Detection* said:
The button combo is Vol Down & Bixby & Power from a powered off state
Keep a hold of all 3 until it hits the Warning screen, then hit Vol Up to enter Download mode
Click to expand...
Click to collapse
That's what used to work indeed. I did that many times before.
*Detection* said:
No other way to access it that I know of, USB Jig hasn't worked since a few models back
Have you tried factory resetting from inside recovery? Unless you used CSC during the stock firmware flash, that could be a reason for the bootloop
Click to expand...
Click to collapse
I tried factory reset/wipe cache from inside the recovery and yes, I used CSC.
mateba said:
Yeah sorry, speaking of the Bixby button.
That's what used to work indeed. I did that many times before.
I tried factory reset/wipe cache from inside the recovery and yes, I used CSC.
Click to expand...
Click to collapse
Maybe the issue is with the Volume Down button, does it work inside of recovery for navigating the menu ?
What happens when you try entering Download mode? It just tries to boot as if you didn't press anything?
Only other thing is to hold Volume Down & Bixby, then connect the USB cable to power it on (instead of using the power button)
*Detection* said:
Maybe the issue is with the Volume Down button, does it work inside of recovery for navigating the menu ?
What happens when you try entering Download mode? It just tries to boot as if you didn't press anything?
Only other thing is to hold Volume Down & Bixby, then connect the USB cable to power it on (instead of using the power button)
Click to expand...
Click to collapse
The volume down button works perfectly in the recovery menu.
When I try entering download mode normally while device is powered down, the phone never turns on.
When I try to hold the buttons during the interval of the boot loop, it goes to recovery (yes, even with volume down, not volume up).
The other technique you mentioned also went to recovery.
*Detection* said:
Impossible as it is not part of the firmware, nor can be touched by firmware, it is part of the hardware (Think BIOS vs OS)
You can even 100% wipe all internal storage clean so there is no OS at all and download mode will still work fine
Keep trying
Click to expand...
Click to collapse
BINGO! I kept trying. Did this all day literally hundreds of times.
And it just worked.
I didn't change the way I do it, I think there was some nasty timing going on with the boot loop.
Anyways... lesson learnt: download mode is indeed hardcoded. What a day!
Thanks for being so helpful!
mateba said:
BINGO! I kept trying. Did this all day literally hundreds of times.
And it just worked.
I didn't change the way I do it, I think there was some nasty timing going on with the boot loop.
Anyways... lesson learnt: download mode is indeed hardcoded. What a day!
Thanks for being so helpful!
Click to expand...
Click to collapse
Good stuff, yea well whatever it was hopefully it's sorted now, use ODIN this time