There are three parts to this thread - How to get into download mode, how to get into recovery mode, and how to solve problems connecting your Android device to your computer. I think you should be able to find where each one begins without too much trouble.
----------------------------------------------------
GETTING INTO DOWNLOAD MODE
----------------------------------------------------
"Just get into download mode and..."
Ever find yourself with a phone that's misbehaving, and you can't seem to figure out how to get it to download mode?
Here's a list of things to try, sorted in a "where are you now" setup:
Note: You will need to use Vol+ to select download mode after you reach the mode selection screen.
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol-, Home button, and Power.
- Press and hold Vol-/Home/Power, Insert Battery.
- Use a USB jig (can be manufactured jig or homemade chain of resistors)
FROM CLOCKWORKMOD RECOVERY MENU
- Position the cursor (highlighted selection) on "Restart device", hold Vol-/Home, then press power
- (Where available) Use the "Reboot Download" option in the "Advanced" menu
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot download"
- (Where available) Use the rom's power menu option to reboot into download mode.
- From a terminal, type "su", then "reboot download"
- Download the app "quickboot", follow the app directions to reach download mode.
----------------------------------------------------
GETTING INTO RECOVERY MODE (CWM RECOVERY)
----------------------------------------------------
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol+, Home button, and Power.
- Press and hold Vol+/Home/Power, Insert Battery.
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot recovery"
- (Where available) Use the rom's advanced power menu (long press power in android OS) option to reboot into recovery.
- From a terminal emulator, type "su", then "reboot recovery"
- Download the app "quickboot", follow the app directions to reach recovery mode.
- Download the app "Rom Manager", select "Reboot to Clockwordmod Recovery"
----------------------------------------------------
UNIVERSAL FIRST STEPS FOR CONNECTION ISSUES
----------------------------------------------------
So you've got Odin up, the phone's in download mode, it's connected to the computer, but Odin is saying "What phone?". You've tried jiggling the handle, checking the blinker fluid levels, and even using the board stretcher, but the Android guy is smirking at you with that smug green face.
Although it is possible that there is something else at work that's preventing your phone from connecting, I would suggest trying these "universal first steps" to see if you can resolve the connection issues:
1. Turn off both devices (phone and PC) - and I do mean full power-down. Go ahead and pull the phone's battery, if necessary.
2. Disconnect your phone from your computer at all points - USB out of phone, USB out of computer.
3. Start up your computer. Don't touch it, don't do anything to it. Let it fully boot and completely settle.
(Obviously, log in if it's necessary, but then let it finish booting before moving on to step 4.)
4. Start up Odin. Let that get completely started and settled.
(If on Vista/Win 7, make sure to "Run as Administrator" in the right-click menu.)
5. Connect your USB cable to a different port than the one you last had it connected to.
(If you're on a Windows desktop, the ports in the back of the computer are generally more stable and should be used. If you're on a laptop, use USB port #1)
Do not connect the phone to the cable yet.
6. Start your phone in download mode. Wait until you see the Android guy with the 4-5 lines of text in the upper left corner.
7. Connect your cable to the phone. Let it sit until Odin recognizes it (which should only take a couple of seconds).
If, for some reason, Odin doesn't recognize the phone at this point, here are a few more things to check/try:
- Repeat steps 1-7 above, making sure to change USB ports. As dumb as it sounds, sometimes the phone or computer just doesn't like particular USB ports.
- With everything still up, switch USB ports.
- Try a different OS (if possible) - sometimes Ubuntu will recognize what Windows won't, and vice versa.
- Try doing this on a different computer - again, different OS, different USB ports, they're all links in a chain and sometimes you'll come across a configuration that doesn't have the weak link.
- Try a different cable. I've had a case where I couldn't do any flashing with one cable, but everything was rock-solid and smooth on the same machine with just a different cable.
- Fully uninstall your drivers, reboot the computer, reinstall the drivers, power down, and then start again from step 2. Sometimes faulty drivers are the problem.
--------------------------------------
Additional Note:
If you're moving from an AOSP-based rom (MIUI, CM10, etc) to a Touchwiz-based / Samsung Stock-based rom, remember to wipe data / factory reset prior to flashing a stock rom. You will hang on the "Samsung" logo if you don't.
Please note very carefully, though, to do the wipe in CWM recovery - not 3e recovery. If you do it in 3e recovery, you'll format the internal storage, meaning you lose all your pictures, music, etc.. (I learned this the hard way.)
--------------------------------------------
If anyone has any additional items / corrections, please reply and I'll update the OP accordingly. Thanks.
Reserved
Great guide!
I'd like to add my experiences, while using CWM 6.0.1.2 booting into Recovery is a bit tricky. It appears the default recovery boots instead of CWM. The only work around I know of is to Flash ClockworkMod Recovery first from ROM Manager v5.0.2.0 and then select Reboot into Recovery. Any other method I try seems to fail.
I'm running Stock At&t ROM, rooted.
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
djtiko said:
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
Click to expand...
Click to collapse
OP thanks for exelent post..I had one more problem with USB connection. Sticks in usb port did not connect correctly. Just jently squize USB male connector on samsung data cable so top of male connector will bend just enough to get good connection when you push back to PC port.
@djtiko - I answer on other post to your problem..
djtiko said:
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
Click to expand...
Click to collapse
Do a factory reset again, should fix you up. If not, consider using Odin to flash a stock ROM package.
Thanks got it all fixed, just had to do a data wipe in the stock recovery and then I was golden
ondin
Hey guys when i run the bootloader file should i open it up in the pda tab on ondin or in the Bootloader tab?
Should be in the pda tab I believe.
Edit. Which bootloader file are you referring to? To know for sure, you could just flash the entire stock rooted jelly bean Rom.
If using Odin with Chainfire to auto root just to root I found that the file that you are using to root you HAVE to have in the SAME folder I made the mistake of downloading the Odin then Odin with chainfire from http://forum.xda-developers.com/showthread.php?t=1963790 then was opening the odin first downloaded then it would stall for not able to start the installation then rechecking the unzipped folder for the .tar.md5 file noticed that Odin was there too, loaded it and PRESTO rooted in less than 30 seconds... So for other that are just looking to root give chainfire a check, yes you would need to use the triangle away if you are worried about that however you don't loose anything when doing it this way so all a matter of what you are looking to do. THANK YOU so much for the help with the drivers issues!
Hi guys,
New to this phone, from a customer. Can get into CWM but it seems broken - can't get into most menus, just goes to the CWM logo, "no files found", does nothing on most options. Sometimes you can select something, often times not. Just a while back, I could wipe everything, but it still hangs at boot.
Download mode - is not recognized by ODIN or PC. Tried re-installing Samsung USB, 3 diff. cables, zadig does not see it in List All Devices.
Thing hangs on the bootscreen. Gets to the Android 4G Tmo- logo, then Samsung glow letters, just hangs / loops.
I have the factory ROM to install, I just need to see the damn thing :cyclops:
Tried diff pc, still... JTAG?
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!
I have a Samsung Note 8 GT-N5110 (WiFi only) that is stuck at the Samsung logo.
This started after there was an attempt to flash a non-stock firmware and the device powered off before it was done.
When I attempt to enter Recovery Mode (Volume Up + Home + Power) it displays "Write Fail!" in upper left of the screen.
I am able to enter "Download Mode", so I've tried flashing a stock firmware using Odin.
I've tried both a One-Click recovery based on ODIN3 v1.81 and also tried Odin3 v3.12.10.
Each time, Odin fails, with a message:
write fail!!
SW REV. CHECK FAIL. DEVICE:2, BINARY:1
I've tried various versions of firmware, and nothing seems to work.
I've tried disconnecting the battery for a minute or so, and it still fails.
Any ideas what else I can try?
I have screen shots and detailed logs of what I've been getting, if that helps.
Thanks!
Believe it or not, I still have this device, and have not been able to get it to work!
So, I'll just revive this zombie post more than 2 years later, and see if anyone has any idea on what to do.
I'm in the fourth (fifth? sixth?) week of corona-quarrantine, so plenty of time to look into this!
The tablet needs more power than the computer's USB port can deliver. Thus, it will slowly drain the battery while connected to the computer and working via ADB, Odin or Heimdall. Seems like that has been the case in your earlier attempt, resulting in a corrupt flash memory. I can't tell if it's really defective or just corrupt and in need of formatting.
I'd try to:
1) Charge the battery
2) Copy LineageOS to the MicroSD card
3) Boot into download mode and install TWRP only via Odin or Heimdall. If this works,
4) Boot into Recovery (TWRP, not the stock one!), connect the charger to keep it powered and go from there (wipe and repair the internal flash, install LineageOS)
If this doesn't work, try if you can find any service functions in Odin or Heimdall to wipe and repair the internal flash.
Good Luck!
Ektus.
Hi Ektus,
Thanks for your help!
I will try as you suggested, and see what happens.
I'll let you know how I do.
Thanks!
I had similar problem. What I did is just change the USB cable to new.
Hey guys, I am trying to repair an SM-T800 that a retired co-worker left in his office on his last day. Unfortunately this means I dont know if ADB is/was enabled in settings, nor do I know what he did to screw it up. I have installed the latest Samsung USB drivers on my PC. When you try to boot up it gets stuck on the logo screen with the error "KERNEL IS NOT SEANDROID ENFORCING" and will not go beyond that.
I can get in to recovery: https://dl.xda-cdn.com/5/1/3/2/7/1/5/20201109_150504.jpg?key=mBcAaKMn5XfEKbdT-D9RAg&ts=1604952923 However when i go into ADB; my PC will not detect it. I performed a wipe data/system factory reset and I get stuck with the same error on the logo screen. If i reboot to Bootloader I get stuck at the same error on the logo screen.
I can get however get into download mode.: https://dl.xda-cdn.com/5/1/3/2/7/2/7/20201109_154421.jpg?key=AVyFna3n1f9PXJ6O6fWIig&ts=1604954839 but Odin will not detect the tablet.
I tried multiple cables on on multiple different PCs and it will not detect through ADB/Odin either. Is there a flashable zip I can install via microSD card from the stock recovery? Are there any de-brick tools? Any assistance anyone can offer is greatly appreciated.
I can't count how many times I've soft bricked my T800. Odin has always been my savior. My thoughts are, if you can get it into download mode, but even with multiple USB cables, Odin fails to respond, you've possibly got a damaged USB port on the tab. Does Windows respond when you connect it to a USB port. (USB2 ONLY, I believe.)