Trying to flash the stock ROM here, but ODIN isn't working. ID:COM doesn't turn blue! I've booted my Note 8 into download mode, but absolutely NOTHING indicates that anything has been connected. The regular Android has been disconnected, and NOTHING new gets connected that might be the "download mode" device (whatever that device may be).
How do I get this to work?
For reference, at the ltop left of the screen, it says:
ODIN MODE
PRODUCT NAME: GT-N5110
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
NOTHING CHANGES IN THE DEVICE MANAGER WHEN PLUGGING IN THE DEVICE
This leads me to suspect I need to do something on the device itself to get it to "do" something, whatever the flipping heck is needed to make a pc connection.
Kies has been installed. Same problems before installing it.
I've used the Toolkit from skipsoft, and used the drivers that came with it. No change before or after.
I've installed and uninstalled and reinstalled drivers, and more dirvers, but nothing.
NONE OF THIS WORKS.
USB connection for ADB mode works fine, both in recovery and when fully booted.
Android is currently Cyanogen 11, pc is Windows 7. I'm trying to get the stock ROM on it again, I've got it ready for upload, now all that remains (hopefully) is to get the device to connect so that it can download the "update".
Please help, I'm out of ideas.
Okay, time for an update. For some odd reason, the tablet needed to be plugged into a USB 3.0 port in order for download mode to work. Very odd. Very odd indeed. NONE of the guides mention anything about this, but apparantly it's a thing.
Anyway, Now that I'm back to an official stock ROM with Android 4.2.2, booting the device takes abnormally long. It's been in a boot process for the last 10 minutes now. IT DOES NOT LOOP, it just shows the samsung logo with an animating blue glow behind it. And nothing else.
The tablet is quite warm, which is nice for my hands, but not great for the battery. It will probably drain out in the next hour.
When I connect the tablet to the pc (on the USB2 port again), it detects a normal range of Android devices. They all install normally, except for the MTP device - that one fails. Not sure if related, but it's a thing that happens nonetheless.
What can I do to make it go and boot through to Android?
Boot into stock recovery and factory reset... wipe cache... should take care of the excessive boot time.
Related
My Salutations, I am asking a question in regards to a serious bootloop I have managed to pull myself into.
Most bootloops I usually just enter CWM and flash another rom or restore. This problem however is much more serious.
Every time I attempt to enter CWM it goes directly to download mode. It's as if CWM doesn't exist on my phone anymore or something.
Download mode is the only thing I can access. I have tried multiple attempts to enter any other recovery mode but they all end up getting me to download mode.
This isn't the only problem. I thought this wouldn't be a big deal until I realized my PC can't recognize my phone at all anymore. Even before I got into the bootloop, my phone would only charge but any other recognition from the PC was absent. I have all the correct drivers installed including numerous attempts at re-installing, re-configuring, and restarting my PC.
I think I may have reached an irrecoverable error.
Any ideas would be much appreciated. Thanks.
FYI, The ROM I flashed when my Phone started acting like a bundle of ninnyhammerness was AOKP milestone 6. It's not the ROMs fault of course, seeing as how this ROM is very good. I also had the Darkside kernel. This is when I couldn't manually enter CWM. In stead, I had to let the phone boot up and utilizing the power menu, restart in recovery mode. I thought this was strange at first. I then wiped, and decided to flash the 20th Nightly of AOKP Jellybean just to try it. It booted fine, but then when I had to restart to enter CWM again I chose to flash another Darkside kernel. After this, my phone went into a bootloop. That is where everything else fell apart.
Sounds like either the recovery isn't sitting in the system correctly or its gone. When your phone is in download mode you said that you can't connect to pc. Are you running odin as admin and/or connecting the device to pc previous to putting the battery back?
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
Yes I did run Odin as an administrator. I also tried connecting the device prior to putting the battery in, and also after.
I had this sort of problem yesterday (I installed a port of CWMR and it had some bugs which lead to it formatting the disk and then freezing and a reboot wouldn't allow me to install a rom...) anyways
1) Go to http://www.samsung.com/us/support/owners/product/SGH-T989ZKBTMB? and download the drivers for the phone. This will allow windows to recognize the phone, without the phone having to communicate to the computer.
2) Download Odin v 1.85 (that's what I used anyways)
3) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1481141 It'll give you a workable CWMR to allow a format and installation of a rom to stop the boot loop
Those three steps should solve the problem, it did for me at least.
Hope that helps!
kmcclry said:
I had this sort of problem yesterday (I installed a port of CWMR and it had some bugs which lead to it formatting the disk and then freezing and a reboot wouldn't allow me to install a rom...) anyways
1) Go to http://www.samsung.com/us/support/owners/product/SGH-T989ZKBTMB? and download the drivers for the phone. This will allow windows to recognize the phone, without the phone having to communicate to the computer.
2) Download Odin v 1.85 (that's what I used anyways)
3) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1481141 It'll give you a workable CWMR to allow a format and installation of a rom to stop the boot loop
Those three steps should solve the problem, it did for me at least.
Hope that helps!
Click to expand...
Click to collapse
Thanks but, it still hasn't worked. It keep saying "USB device not recognized, Device driver software was not successfully installed."
I was able to fix it. If anyone else encounters this lethal, and pretentious conflict again... I resolved the problem by repeatedly spamming the power button on my computer, unplugging the cable repeatedly and letting my phone sit without the battery inside of it for 24 hours until my PC finally recognized the device.
i3lackDawn said:
I was able to fix it. If anyone else encounters this lethal, and pretentious conflict again... I resolved the problem by repeatedly spamming the power button on my computer, unplugging the cable repeatedly and letting my phone sit without the battery inside of it for 24 hours until my PC finally recognized the device.
Click to expand...
Click to collapse
also it may be because of a faulty data cable !
Hi,
My brother's SGH-T989D phone (Koodo / Telus) crashed during an android update. Now, the phone boots to a black screen with the taskbar on top. There is no menu screen anymore. No apps at all. Doing a factory reset via the recovery mode does not change anything.
My PC does not detect the phone. Therefore, I am unable to install a new ROM with Odin. Here are all the infos I have :
1. The phone boots, but there is absolutely nothing except the task bar (I can toggle the wifi and bluetooth on and off, thats it...). There phone says preparing SD storage upon booting. There are no SD card and SIM card.
2. The phone is able to go into recovery and download modes.
3. My PC does not detect the phone. I know the Samsung drivers, Odin v3.07 and USB cable are working properly because I am able to connect my own phone which is also a SGH-T989D.
4. In recovery mode, there is a dead android with a red triangle with an "!" in the background.
5. It used to have the stock gingerbread Koodo ROM, and was probably updated over the air to the newest ICS from Koodo.
6. The phone was never rooted or messed with. I don't think it was ever connected to a computer before.
7. It is not under warranty anymore.
I've spent hours trying to get it recognized by the computer. I've tried putting the ROM on the SD card and applying the update via external storage in recovery mode. I get a message about Signature verification failure.
I've tried cleaning the micro-usb slot. Blowing in it resulted in the computer saying "Unknown device malfunctioned" a single time, which leads me to believe it only did that because some saliva created a short somewhere in there. The connections look clean.
I'm about to throw this phone off the building. What is wrong with it?
**EDIT**
Forgot to mention...the phone does charge when connected to the usb cable.
kamikazee1989 said:
Hi,
My brother's SGH-T989D phone (Koodo / Telus) crashed during an android update. Now, the phone boots to a black screen with the taskbar on top. There is no menu screen anymore. No apps at all. Doing a factory reset via the recovery mode does not change anything.
My PC does not detect the phone. Therefore, I am unable to install a new ROM with Odin. Here are all the infos I have :
1. The phone boots, but there is absolutely nothing except the task bar (I can toggle the wifi and bluetooth on and off, thats it...). There phone says preparing SD storage upon booting. There are no SD card and SIM card.
2. The phone is able to go into recovery and download modes.
3. My PC does not detect the phone. I know the Samsung drivers, Odin v3.07 and USB cable are working properly because I am able to connect my own phone which is also a SGH-T989D.
4. In recovery mode, there is a dead android with a red triangle with an "!" in the background.
5. It used to have the stock gingerbread Koodo ROM, and was probably updated over the air to the newest ICS from Koodo.
6. The phone was never rooted or messed with. I don't think it was ever connected to a computer before.
7. It is not under warranty anymore.
I've spent hours trying to get it recognized by the computer. I've tried putting the ROM on the SD card and applying the update via external storage in recovery mode. I get a message about Signature verification failure.
I've tried cleaning the micro-usb slot. Blowing in it resulted in the computer saying "Unknown device malfunctioned" a single time, which leads me to believe it only did that because some saliva created a short somewhere in there. The connections look clean.
I'm about to throw this phone off the building. What is wrong with it?
**EDIT**
Forgot to mention...the phone does charge when connected to the usb cable.
Click to expand...
Click to collapse
IDK if this will help you. IF the phone isn't rooted or a custom recovery installed I don't believe you can reinstall the ROM. It does say 'signature verification error' so you might be able to turn off MD5 checking before install. It will be in the settings menu if TWRP is used. I don't believe its an option to do if on stock recovery.
I found, after months of searching, a customized recovery (TWRP 2.8.7.0) for my Tab, and the Android SDK (ADB & Fastboot).
I backupped all of my files and things, and I wiped everything out (accidentally).
Now, my Tab can access Recovery, but when I try to copy a ROM into it's internal storage, after some minutes it exits automatically (I turned the Screen Timeout off), failing the copy operation and not giving any option to restart it at a later time (dumb Windows), and no ROM that I have seen so far is small enough (100-200MB) to copy before the Recovery auto-closes. My USB picks it up (but only for accessing through Windows - Fastboot and ADB don't pick it up).
My Android version is 4.1.2, and I haven't tried many methods apart from Kies (does not detect anytime) and the ones descripted here. The Tab can't charge, and I have 86% battery. I believe that the Samsung firmware is too big for the auto-exit cycle.
However, it can access Download Mode but the USB nor the computer respond, and ADB & Fastboot either.
When I start my Tab up, it gets stuck in the bootloader screen, and Odin (v3.09) shows 1 "Added!!!" message, but I can't do anything with the PC/Tab connection.
So my Tab is stuck until I can find a 100-200MB rom that can be copied without the Recovery shutting down automatically.
Can anyone help me out?
Fixed, installed Odin 3.07 and it somehow made the recovery not close itself, so I flashed RocketTab 3.0!
Hi all, I've been using XDA for years since the original O2 XDA's and I have never had to post anything as I've always found my solution. I'm hoping somebody can assist me with a problem I have on this stock galaxy tab 3.
The device was brought to me after being thrown down the stairs. I replaced the screen and built it back up,
Removed battery connector and reconnected = nothing happens
Press power = nothing happens
press download mode = nothing happens
press recovery mode = nothing happens
Plug USB into PC = nothing happens on PC or tablet
Plug in USB mains charger and it displays battery charging logo but it doesn't fill or animate the fill then it starts the samsung boot screen. It reboots and continues to do this constantly and never ends.
I've tried two batteries and both batteries work in another tab 3 but neither batteries changed how the device works.
Thank you for any advice in advanced!!
I just received a Tab 3 lite (SM-T110) for repair, it's having a similar problem.
It does automatically turn on when plugged into charger or computer.. It is stuck on a bootloop, requiesting a Kies recovery. It does reboot when given the three finger salute (center button, volume down, and power) - it will not enter recovery mode though - same firmware error message). The device is also full off or full on, no indication of it's it's recharging or no - let the battery run out, it's off - else it's on (does not turn on or off with power button). I don't have any info how it got into this state - most likely power loss during a firmware update, but haven't ruled out other possibilities (ie bad rooting job, a custom ROM upgrade went wrong, etc). I'm not 100% concerned about cause, but hopefully I can unbrick the thing.
Anyways, I loaded Kies onto my computer and put it into recovery mode and plugged it in - nothing. Exit the recovery mode of Kies, and all of a sudden the program goes nuts trying to connect and disconnect from the device. Hmm... Okay, disconnect it, uninstall Kies, install Kies3 and try again - same thing except it complains the device is too old when the program leaves recovery mode - but same thing otherwise - does not show up in recovery mode, connects and disconnects at huge rate when not in recovery mode....
Hmmm...
Now looking at the screen, it does indicate (in the upper left hand corner) that it's in ODIN mode... So my next step I figure I'll try ODIN (although I'm researching ODIN at the moment as I haven't used it before (never had to unbrick anything from Samsung prior to now).
Okay, that was painless - downloaded and installed ODIN 3.10.7, and then downloaded the latest firmware from Samsung, extracted the firmware, added it to ODIN's AP line, then hit start to push the latest firmware onto the tablet. Good as new again.
Its been a long time since I booted my Galaxy Note-II (GT-N7100) as I use an iPhone and Nexus 5 as my daily drivers.
The phone wont boot past the Samsung Galaxy Note II GT-N7100 logo. I am able to access the recovery and download mode as well, and I have flashed the latest stock rom from Sammobile using the Odin. The flashing was successful. however the phone doesn't boot past the logo. Also the phone will not power up unless connected to a PC, it wont power up even when connected to a charger and will immediately shut down when the USB cable is disconnected from the PC. I flashed TWRP 3.0.2 Custom Recovery using the Odin and tried installing CM 13 based Rom through the mem card, however the log reads patching image unconditionally and also that "Failed to mount /system" (invalid argument). The phone when restarted into recovery can no longer mount the /system partition. However on flashing the stock rom using Odin, the /system partition is available for mounting. The recovery log also shows MTP enabled, but my PC doesn't detect the phone when in recovery, it only detects the phone in Download mode. I have the Samsung drivers installed. Since the phone is not being detected in recovery I am unable to use the adb.
I am out of ideas and request your suggestions other than approaching a service centre.
If I can somehow access the phone via ADB, I might be able to check the memory partitions for corrupt units, and possibly create a custom PIT file to repartition and suit the available memory units.
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
audit13 said:
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
Click to expand...
Click to collapse
Thanks a lot.
Tried your method and finally the phone has booted into the OS.
Had to replace the battery with another spare one in the process.
However the phone is still not being detected by the PC unless it's in Fastboot/ Download mode.
When connected to a computer, does anything appear on the phone screen? If you're using Windows, nothing new appears in device manager?
sorry to jump in this thread but i am having a similar problem
my completely stock tmobile note 2 is stuck on the samsung logo
i have never flashed it or done anything to it
my phone was working really slow, freezing up and battery draining fast
so i did a hard reset and it fixed the problem of running slow and freezing up for a week or so but battery drained fast
so i bought a replacement battery from ebay and installed it and the next day i restarted my phone and it froze on the samsung logo
i tried turning it off and on and still the same thing
any suggestions or should i start a new thread?
fyi i am a noob