Hi all,
I wanted to install a custom firmware to my Tab GT-P3110. I followed the instructions and downloaded the files needed to root the device first. But to my surprise, i couldnt proceed with even a simple process of rooting. I have done this before with my Galaxy s2 without any problem. But now the laptop is refusing to detect my tab in a normal way or in the download mode. So i cant proceed with Odin. Although in the download mode, it says that Odin in red small letter on the top left corner alongwith some more 2 line detail but thats it. It is not recognized by the laptop.
Here are the things which i tried:
Uninstalling and reinstalling the samsung drivers
Re-installing kies
restarting latop (dozen times)
Tried on 3 different laptops
Tried three different USB ports
Any help is appreciated. Last effort i'll factory reset it and then hope that it works as a new tab and i dont need to look into a custom firmware.
Hello guys, i am new here and I am seeking help from the more experienced
To cut to the chase and make a long story short, my Galaxy Tab 2 is currently in a boot loop in ClockworkMod recovery. (I was trying to flash my first ROM, got Status 7, and while waiting for my order of OEM USB cable to come as to fix the problem, my data got deleted one day idk how) The tablet model is 10.1 P5113
It probably doesn't seem like a big deal until you find out that you can't flash roms from internal; storage (all my data got deleted somehow and I figured I was screwed after reading "no data found" on the script)
But what makes matters worse is that I cannot flash a stock ROM via ODIN...this is because USB Debugging was left disabled...i never knew i would need it now lol. What sucks also is that I have no nandroid backups to fall back on...
Basically, I have a tablet that boots into CWM and has no data to rely on whatsoever, it really sucks...no USB Debugging means I cannot flash my out of this predicament with ODIN either. I have a Windows PC (Windows 7) and a OEM USB cable. My tablet model again is 10.1 P5113
May somebody please give me advice on how to take this? I want to get out of this bootloop, get some rom running (even stock) and get another go at flashing my custom rom. I would greatly appreciate any advice from anybody)
I found a solution by flashing the stock rom via ODIN. It turns out stock roms do not need USB debugging to be enabled, so I saved my tablet....
I am going to switch to TWRP Recovery as soon as I can
Thread closed as user already founded by himself a solution.
I've searched for nearly 12 hours and tried several methods, but since this is an older device a lot of threads and links are dead. I was hoping someone could give me advice here, and I did use the search but to no avail.
The situation is I have a Galaxy Tab 2 10.1 (GT-P5113) and it's stuck on the logo and the sound it boots up cuts out half way (wondering if it's a hardware issue). I can boot into Download Mode and I have the drivers for it on my computer. The problem I'm having is USB Debug wasn't enabled. Is there a way I can flash through Odin3 and which version should I use? This device isn't rooted either. Any help or advice would ease my mind.
Moceimo said:
I've searched for nearly 12 hours and tried several methods, but since this is an older device a lot of threads and links are dead. I was hoping someone could give me advice here, and I did use the search but to no avail.
The situation is I have a Galaxy Tab 2 10.1 (GT-P5113) and it's stuck on the logo and the sound it boots up cuts out half way (wondering if it's a hardware issue). I can boot into Download Mode and I have the drivers for it on my computer. The problem I'm having is USB Debug wasn't enabled. Is there a way I can flash through Odin3 and which version should I use? This device isn't rooted either. Any help or advice would ease my mind.
Click to expand...
Click to collapse
download a copy of your device stock firmware, if you already have it, flash it with odin, there is no specific version of odin, it works on all as long as your device gets connected and shows in odin you are fine.
regarding the hardware issue, it might be or it might be not, you can only be sure after successfully flashing a stock firmware file.
it won't need any USB Debug option for flashing stock firmware so you are safe to flash.
If odin does not work you may try going to the recovery and perform a factory reset and delete cache
Hi,
Yes, I know, there's a million topics about this and I'm pretty sure I tried them all!
Long story short: been running Lineage OS on my Tab 2 for a while but it's been sitting in a drawer. Saw a video about using old tablets for emulating retro consoles and the Tab works a dream for that. So I bought a Bluetooth controller for better gameplay but it just wouldn't work under Lineage so thought I'd flash the original ROM back onto it to see if that would work. I'm not a n00b, but haven't done it for a while so thought to be safe I'd follow a guide. All seemed to be working well when Odin crashed and left me with the Firmware Upgrade Failed error.
I've been trying for about four hours to get it back, but having no luck. I've tried the latest version of Odin, as well as the old 1.7 version I was using; tried Kies, tried uninstalling Kies; tried uninstalling the stock drivers MS installed when connected, no go. Interestingly Odin doesn't seem to see the Tab at all now, so I tried the UniversalADB installer, tried installing ADB drivers as well as Samsung drivers manually, but nothing works, it just sits at "connecting" but never actually does. Also tried different stock ROMs to no avail. I think my issue is with the ADB drivers, just don't know how to fix it.
I don't know what to try now. Any advice?
Using MS Surface Pro (2017) running Win10.
Not allowed to post screenshots, but do have some.
Thanks.
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Tab_Triggerhappy said:
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Click to expand...
Click to collapse
Hi,
Thanks for your reply and sorry it's taken me so long to respond; I've got several health issues I have to work around!
I can't get into the OS at all, it's just stuck at the "Firmware upgrade..." screen and there's nothing else I can do with it.
It was rooted and I was running TWRP recovery, but can't access it at all now. I did a wipe in TWRP but was still able to boot into it before I ran Odin. Odin worked fine, then it just stopped for reasons unknown and now there's nothing I can do with the Tab at all.
I see this in Device Manager: samsung mobile usb cdc composite device. Have tried manually installing driver but nothing seems to work.
Have tried it on my Mum's Win7 machine, but to no avail. I really need ADB drivers but I can't install them without turning on debugging on the Tab and I can't do that because I can't get out of this blasted error screen!
There's literally nothing else I can say about it as this is all that's happening.
Annnnd, now it doesn't seem to want to hold a charge. :crying:
Thanks again.
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Tabby22020 said:
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Click to expand...
Click to collapse
Maybe a longshot, but you can test if this free version can access the tab:
https://www.tenorshare.com/products/reiboot-for-android.html
No use buying if it can't.
But since Device Manager sees something it's worth a shot.
Do you have to longpress power button to turn it off?
If so... when the screen goes off, have you tried to quickly let go of the power button and immediately press it again together with Volume Up?
Or down, for download instead of Recovery.
With my P3100 it was much easier with no charger plugged in...
Edit:
Tried the software and my tab is OK, but no connection established anyway. Only result was that I couldn't access tab in File Explorer and MTP state... only PTP.
In Device Manager I got a new Android Device: Something like Google Nexus ADB... sorry but I uninstalled it directly without noting exact name.
Replugged USB cable and MTP working again.
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I finally thought that this tablet did not have its bootloader locked. I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
- yo - said:
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I finally thought that this tablet did not have its bootloader locked. I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
Click to expand...
Click to collapse
This is obviously your own fault you should of unlocked the bootloader first before flashing twrp
Your device is basically bricked because u risked your device trying to flash twrp with a locked bootloader
Austinredstoner said:
This is obviously your own fault you should of unlocked the bootloader first before flashing twrp
Your device is basically bricked because u risked your device trying to flash twrp with a locked bootloader
Click to expand...
Click to collapse
As I said, the first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I spent hours searching about that and could not find it. Also, some people were saying that this device doesn't have a locked bootloader.
Is it possible to do anything in this situation ?
- yo - said:
As I said, the first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I spent hours searching about that and could not find it. Also, some people were saying that this device doesn't have a locked bootloader.
Is it possible to do anything in this situation ?
Click to expand...
Click to collapse
I don't know because I don't have that device
- yo - said:
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I finally thought that this tablet did not have its bootloader locked. I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
Click to expand...
Click to collapse
There is a forum for this device.
Samsung Galaxy Tab 3
The Samsung Galaxy Tab 3, much like its predecessors, comes in three sizes, 7", 8" and 10". The 7" is powered by an Exonys 1.2GHz dual core processor, the 8" is powered by the Samsung Exonys 1.5GHz dual core processor and the 10.1" powered by a 1.6GHz dual core Atom processor. They run on 1GB...
forum.xda-developers.com
Did not know that. Sorry. I am going to post it under the right topic. If someone want to delete it.