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.
Related
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
MrAwesome75 said:
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
Click to expand...
Click to collapse
ya but i havent even tried loading a file into odin cause it wont see my device
and i have installed the samsung drivers but after this happened my pc wont see the phone
has to be a way to get a connection between the pc and phone
I'm not an expert so I'm not sure. Do you have the correct drivers installed on PC?
---------- Post added at 06:34 AM ---------- Previous post was at 06:30 AM ----------
Try different Odin versions. And make sure you have the proper drivers installed on the PC.
ya ive actually read that it probably doesnt have the function running to talk with the pc cause it cant boot. im all set up to reset the phoone. just need it to appear in my odin
..does kies still work?
[email protected] said:
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
Click to expand...
Click to collapse
When you boot to system
It doesn't show anything right ??
but the touch is still functioning
Sent from my GT-i9300 running cm11 using tapatalk.
when i just boot it goes to download mode and says "could not do do normal boot"
i can access recovery mode and download mode but i cant get drivers to show it, and it used to show it until i did this, can i put a file on my micro SDcard from my pc via card reader then install it in recovery mode ? like firmware or a memory wipe reset?
If you can get into recovery, I believe that would be possible. Couldn't hurt to try. As long as you can get into recovery and all the recovery functions work, I don't see why you couldn't.
fixed it!
well after two nights of reading i got my pc to discover the device by changing ports three different times to find one that seamed to like it. and also installed kies and installed the drivers from them, (figured couldnt go wrong after as many as ive used from samsung and others). so win7 pro / altered boot command and only stock options afterwards sucks big time. ty all for helping me
never let up
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
[originally posted here on reddit, but due to the low activity around this device i'm posting it here too]
Hi All,
I have some experience installing TWRP via Odin and LineageOS via TWRP on 2 Galaxy S3s. Recently i have tried installing them on my S2 plus so i can have a backup phone. I know there are newer phones, i just want this for the challenge and to give it to a special someone...
basically i aim to install Lineage 14.1 and preferably (but not necessarily) with TWRP too.
Any suggestions on how to proceed ?
some info:
Samsung model:GT-i9105p
Android version: 4.1.2
Computer OS: Windows 10. the same ports and cables that i always use. in fact i just used them again for my s3.
with Heimdall the problem is:
when running zadiag.exe, i follow these instructions but list all devices does not give me any of these device names even after i uninstall all samsung USB drivers and Kies.
Run zadiag.exefrom the Drivers folder of the Heimdall suite.
Choose Options » List all devices from the menu.
Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu. (If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Kies)
Click to expand...
Click to collapse
.
with Odin The problem is:
i fail after flashing TWRP successfully. each time the boot after the successful installation gives me the Samsung splash screen for quite some time and then the normal stock android comes up.
I successfully flashed twrp-2.8.7.0-s2vep.img.tar and twrp-2.8.7.0-s2ve.img.tar (not sure what the difference is) many times.
i tried both with both Odin 3.12.3 and Odin 3.09 that i found on XDA threads that are specific to S2 Plus, and every combination was successful as far as Odin reports.
I tried manually pressing the combination to enter recovery mode when the phone restarts after the flash, and also to flash without an auto-restart and then do the above, with and without the removal of the battery
overall 10 successful flashing with all of them going to the stock eventually.
I also followed all instructions on https://www.xda-developers.com/how-to-install-twrp/ but running
adb reboot bootloader
only results in a normal boot of the stock android
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,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.
I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.