I want to upgrade my tablet with Lineage OS 14.1, so first i have to install a recovery.
My tab sm-t900 is original with android 5.1 on it and it has become slow.
When the tab is turned on, it's recognised by my windows 10 pc and odin. When the tab is in download mode, it's not recognised by my pc, so also not in odin.
I use the original Samsung cable and tried other original ones. I tried uninstalling and re-installing kies. I installed the latest windows 10 drivers for the tab, which i downloaded from the samsung page. I have enabled usb debugging in developers options.
I tried it on a windows 8.1 laptop and on a windows 7 pc with all the suggestions i described, but i can't get it to be recognised when in download mode.
I noticed the blue line 'secure download : enabled' in download mode and wondered if that may be an issue?
I have searched for a long time by now and don't know what to do anymore. Does anybody have a suggestion? Am i missing something?
It seems like my problem is the locked bootloader, but i can't figure out how to unlock it. In developers options there is no option to uncheck OEM.
How can i see if i have the lollipop bootloader?
Related
Hi All,
I recently purchased two Galaxy Tab S tablets (10.5, SM-T800) which I have been trying to root for the past couple of days but have been getting nowhere.
The issue stems from the inability of my computers being able to detect the tablets in Download Mode.
I have tried the following:
I have tried installing different versions of Odin
I have download kies.
I have tried re-installing the Samsung usb drivers on numerous ocations in two different computers.
I have tried different usb cables to include the cable that came with the tablet.
If Tablet is powered on however, the computer will detected it and thus so will Odin. This is only happens in Download Mode.
If googled this issue and it seems to be a none issue however I have yet to find a fix to this. I was hoping I would have better luck in this forum.
Have you tryed using a different usb port? How about using a different pc? Does it even connect when you tab s is on? My pc can detect my tab s fine but had some issues with windows 8.1 and odin crashing. My guess would be trying on a pc that can detect other devices in download mode just fine. Did you also enable usb debugging?
I'm stumped given what you have tried. I'm assuming you are using CF-autoroot. On Windows 7, Odin wouldn't see download mode until I installed the Samsung drivers downloaded from Samsung. Then everything went fine (after which I rolled Windows back to the previous restore point because the Sammy drivers messed up my Nexus 5 connection. Also, if it matters, I used Odin 3.0.9 but with Chainfire's Odin.ini file.
Are you waiting to plug the tablet in until after you have entered download mode? I don't know why, but the instructions for CF-autoroot were very explicit about that.
coolguycarlos said:
Hi All,
I recently purchased two Galaxy Tab S tablets (10.5, SM-T800) which I have been trying to root for the past couple of days but have been getting nowhere.
The issue stems from the inability of my computers being able to detect the tablets in Download Mode.
I have tried the following:
I have tried installing different versions of Odin
I have download kies.
I have tried re-installing the Samsung usb drivers on numerous ocations in two different computers.
I have tried different usb cables to include the cable that came with the tablet.
If Tablet is powered on however, the computer will detected it and thus so will Odin. This is only happens in Download Mode.
If googled this issue and it seems to be a none issue however I have yet to find a fix to this. I was hoping I would have better luck in this forum.
Click to expand...
Click to collapse
Dont mean to patronize...but you have enabled usb debugging in developer options and installed the adb driver right? Coz odin wont see anything until you do this.
pdolton2000 said:
Dont mean to patronize...but you have enabled usb debugging in developer options and installed the adb driver right? Coz odin wont see anything until you do this.
Click to expand...
Click to collapse
You dont need adb as it worked fine without adb for me. Usb debugging does the trick. But installing adb could help
Yes I already tried different USB ports. Different USB cables. Different computers. USB Debugging is enabled.
Again Odin does detect the tablet as long as the tablet is booted up to Android. Odin detects is, Windows Detects it, Kies Detects it.
As soon as I reboot the tablet into Download Mode and plug it back into the computer, is as if nothing is plugged in. No driver gets installed. No new hardware is detected and thus Odin wont detect it.
FIXED!!!!!
Ok so what essential was happening is I was turning off the tablet. Putting it into download mode using VolDown+Home+Power. However that seemed to be actually taking me to recovery and now download mode.
I ended up booting back into android with usb debugging mode enabled and running the following adb command
adb reboot download
This rebooted the tablet into download mode which looks totally different than the recovery, it then installed the drivers and Odin was able to finally detect it!
Thank you all for your assistance!
coolguycarlos said:
FIXED!!!!!
Ok so what essential was happening is I was turning off the tablet. Putting it into download mode using VolDown+Home+Power. However that seemed to be actually taking me to recovery and now download mode.
I ended up booting back into android with usb debugging mode enabled and running the following adb command
adb reboot download
This rebooted the tablet into download mode which looks totally different than the recovery, it then installed the drivers and Odin was able to finally detect it!
Thank you all for your assistance!
Click to expand...
Click to collapse
Nice one pal glad it all worked, thought you might not of been in dwnload mode coz thw only reason odin wouldnt detect it is that reason....strange how vol down was taking you into recovery though, usually thats vol up...mad
---------- Post added at 07:35 AM ---------- Previous post was at 07:32 AM ----------
DUHAsianSKILLZ said:
You dont need adb as it worked fine without adb for me. Usb debugging does the trick. But installing adb could help
Click to expand...
Click to collapse
Adb drivers are active regardless when usb debugging is enabled ....some times though you have to install them manually....but as hehad installed samsung software the drivers got installed.
Hi Guys,
Bought a used but like new Samsung Galaxy Tab 3 8.0 wi-fi (SM-T310) for my boy.
It's installed with latest stock firmware (T310XXUBNH3) and I need some guidance to root it.
I do not to mess around with the kid’s tablet, I just want to root it, so to be able to uninstall all system apps and do other simple stuff.
I have searched Google and what I found, is that root has to be through ODIN.
I have downloaded the files (ODIN and Root) and when I put the tablet in download mode Odin does not recognize it.
I'm using Windows 8.1 Pro and I noticed that in Device Manager, it’s showing as unknown device. When I try to update the driver only gives me the option to install it as a samsung modem usb, but even after that, keeps showing as unknown.
I have Kies installed and the drivers, supposedly installed, since with the tablet connected, the computer recognizes it immediately.
My problem is then the Download Mode, I’m positive because its missing the correct drivers.
I have also tried to switch cables, very dumb I know, but I had to try.
So my questions are:
1. where can I find the correct drivers for Download Mode?
2. Is there any other and simple way of rooting this baby?
Thanks guys
Djuganight said:
Hi Guys,
Bought a used but like new Samsung Galaxy Tab 3 8.0 wi-fi (SM-T310) for my boy.
It's installed with latest stock firmware (T310XXUBNH3) and I need some guidance to root it.
I do not to mess around with the kid’s tablet, I just want to root it, so to be able to uninstall all system apps and do other simple stuff.
I have searched Google and what I found, is that root has to be through ODIN.
I have downloaded the files (ODIN and Root) and when I put the tablet in download mode Odin does not recognize it.
I'm using Windows 8.1 Pro and I noticed that in Device Manager, it’s showing as unknown device. When I try to update the driver only gives me the option to install it as a samsung modem usb, but even after that, keeps showing as unknown.
I have Kies installed and the drivers, supposedly installed, since with the tablet connected, the computer recognizes it immediately.
My problem is then the Download Mode, I’m positive because its missing the correct drivers.
I have also tried to switch cables, very dumb I know, but I had to try.
So my questions are:
1. where can I find the correct drivers for Download Mode?
2. Is there any other and simple way of rooting this baby?
Thanks guys
Click to expand...
Click to collapse
Download THIS.
Extract and run the UniversalADBDrivers file. That will install ADB drivers. Ensure that you have enabled USB debugging under the Developer Options in settings on the tablet. If you don't see the Developer Options, tap the "build number" 10-12 times to enable it.
If it still doesn't work, you will need to ffnd a Windows 7 or XP computer.
fantastic!
thats worked like a gem.
thanks a lot m8
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Hi i have a similar problem as you, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
bigillz said:
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
Click to expand...
Click to collapse
---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------
I am confused what you mean by calculator, I am on Win 10 and have a similar problem, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
thank you very much. it worked.
I attempted a downgrade to an older version of twrp via twrp in recovery mode. Not sure what I did wrong. Now my LineageOS hangs at the LG logo at startup. When I try to access TWRP using recovery mode, the LG logo flashes on and off (loops). I cannot access the LineageOS to enable debugging, OEM unlock, MTP USB mode, etc...
From a Windows XP SP3 desktop:
I can manually put my D851 into Download mode and can get from Download mode to firmware update mode when connected to a Windows XP computer. The Windows XP computer sees the phone as new hardware ("LGE Android Net MTP") device when connected in Firmware Update mode. In Firmware Update mode, I cannot properly access the phone using the LG PC Suite, ADB/fastboot tools, etc...
I have tried installing various versions of the LG United USB drivers. Originally, the driver installs failed citing "Windows MTP driver" not found and advising me to install Windows Media Format Update. After learning Windows Media player contained the Windows MTP driver, I installed Win Media Player 11. Now the LG United driver install fails but without mentioning missing Windows MTP driver or Windows Media Format 11 runtime updates. I have tried installing the USB drivers using LG PC Suite but it too fails when reinstalling the driver. LG PC Suite cannot connect to my phone. . Ihave tried to install the LGMobile Support Tool (ie. LGMobile Phone Software Update Tool), but the install seems to hang.
I feel that if I could just get a computer to communicate properly with the phone while in Firmware Update mode, I should be able to restore my phone. Does anyone have any ideas on other things I might try?
Thank you
I got stuck in that same boot loop as you. There's a thread that claims that the D851 is unbrickable: https://forum.xda-developers.com/tmobile-lg-g3/help/lg-g3-d851-unbrick-qualcomm-9008-t3430221 But I was also unable to get it to work on my laptop. I think some computers may have a hard time using the drivers correctly and maybe trying another computer is your best bet.
But personally, I ended up sending mine to a J-Tag service on eBay and paying some $30 to get the thing completely reset.
I am trying to fix a tablet for a friend, but I think I am in over my head.
This SM-T210 is stuck on the bootlogo and does not switch off; when I disconnect the battery and connect the device to my computer, it autostarts into the samsung logo again. It does not get "recognized" by windows, even with drivers preinstalled, so KIES does not "see" the tablet. I cannot get into recovery mode. There is a plusside: I can get into Odin, but like I said, Windows does not see the device.
Is it possible to fix this tablet and how?
Odin does not recognise it? Reinstall Samsung and Android drivers.