Develop Bugs

Help son's New Tablet

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

SOLVED Wug's toolkit has me jammed.

Edit: I had switched to a different (charge-only) cable halfway through and not realized it. Switched back and the phone was recognized again.
Steps:
I unlocked my bootloader with Wug's toolkit.
I installed the zips that it asked me to (that it put on my SD card).
I updated SuperSU
I got a notice to update the SuperSU binary.
SuperSU binary won't install via Play.
Tried to install via TWRP and recovery isn't twrp, seems to be stock recovery (thought I installed it, maybe not)
Now the toolkit won't recognize my device. neither will windows. It gives me the USB noise but won't show the device in the folder list and defaults to USB for Charging. I can change it but it doesn't make it recognizable.
I'm trying ot back out and try again but the toolkit says it finds the device but that it's listed as "offline". When I toggle the USB debugging, it doesn't ask me to fingerprint my computer.
When I try the "soft brick" option to flash from the bootloader, the script reports a failure "data transfer failure (unknown error)", then says "rebooting into bootloader..." and does nothing else BUT my phone's bootloader still says "downloading..." When I reboot, the script throws another failure and says "waiting for device". when I bootload into it again and connect, the script throws more failures.
I've been on this for 4 hours, getting pretty fatigued (through the night on a weekend when family is visiting. yes, I'm an idiot for trying this procedure but the 5 went so smoothly I was optimistic).

try reinstalling the drivers. also the OEM-lock option in the dev-settings may help bringing you back to step one.

I was halfway through installing the drivers when I quit for sleep last night.
I'm using the LG-Mobile-Driver_v3.14.1.exe package, and the installer says it installed successfully, but windows says that MTP and PCI Simple Communications Controller had "No driver found", so the device doesn't show up in my drive list and wugfresh won't detect it.
I've removed all Google, LG, MTP, and Nexus drivers in USBDeview, but can't seem to figure this out.
I was able to get the drivers installed on my wife's system, so I'll open another thread about this if I can't get them to work.

Try using @Heisenberg root instructions if you get back to stock. I've tried multiple times to use the toolkit to no avail. I've had to resort to Heisenberg's root method every time and it just works.
You may wonder why I've rooted multiple times...I was testing with Android Pay and wanted to start clean. Although I was able to use the toolkit to get back to stock easily.

oubravs2b said:
Try using @Heisenberg root instructions if you get back to stock. I've tried multiple times to use the toolkit to no avail. I've had to resort to Heisenberg's root method every time and it just works.
You may wonder why I've rooted multiple times...I was testing with Android Pay and wanted to start clean. Although I was able to use the toolkit to get back to stock easily.
Click to expand...
Click to collapse
so, the reason my computer stopped recognizing the phone was that I switched to a charge-only cable without realizing it. Switched back and the phone recognized fine.
The weird thing is, the charge-only cable worked fine for data xfer on my wife's system.

Unbrick FireTV Stick?

Looks like I bricked my fireTV Stick today.
What i did: After i updated to 5.2.1.0 I rooted with Kingo Root. I checked if everything was still running fine, which was the case.
Then i removed Kingo Root App and the superuser app that came with Kingo Root. I installed Chainfires latest supersu.apk which did not work (immediately crashed after start). Then i downloaded older version v1.97 of chainfires supersu. This version did not crash directly after starting it. It asked to update the su binary, which I accepted. Unfortunately it did not seem to work, that's why i rebooted the stick after some minutes.
Now it stucks at the "fireTV stick" logo.
Connection to adb works if i connect the Stick to my PC.
Is there anything i can try? Is there a way to factory reset via adb or anything like that?

Bierfreund said:
Looks like I bricked my fireTV Stick today.
What i did: After i updated to 5.2.1.0 I rooted with Kingo Root. I checked if everything was still running fine, which was the case.
Then i removed Kingo Root App and the superuser app that came with Kingo Root. I installed Chainfires latest supersu.apk which did not work (immediately crashed after start). Then i downloaded older version v1.97 of chainfires supersu. This version did not crash directly after starting it. It asked to update the su binary, which I accepted. Unfortunately it did not seem to work, that's why i rebooted the stick after some minutes.
Now it stucks at the "fireTV stick" logo.
Connection to adb works if i connect the Stick to my PC.
Is there anything i can try? Is there a way to factory reset via adb or anything like that?
Click to expand...
Click to collapse
Connect your fire stick to a windows pc/laptop. (i used windows 10 64bit)
Let the drivers install.
Download the windows version of Kingo root.
Click root, try this a couple of times (it probably will fail and stick at 70 percent)
unplug the stick and try again, when it hits 70 percent again plug your hdmi lead in (already connected to tv)
It should root and write back the correct su files.
If you want to unroot, install kingo and super user again on the fire stick then either use the unroot feature in super user app (you will have to purchase mouse toggle for fire tv, if you havent got it already to navigate to the 3 little dots menu icon top right corner)
Or re plug it into windows pc/laptop and unroot through the windows tool.

Worked! Did not know, that there's also an windows application for Kingo root.
So it's better to not use another superuser app when rooting the fireTV (stick) with Kingo root?

Thanks sconnyuk. I have a bricked Stick from the Feb. KingRoot -> SuperSUMe disaster. Tried a lot of things, no luck.
But the Windows KingoRoot worked on the first try. (No 70% stoppage or anything.) I now have a root shell over adb. I'm going to wait on a rooted ROM to get it back to a normal state, but at least now I have hope.

Bierfreund said:
Worked! Did not know, that there's also an windows application for Kingo root.
So it's better to not use another superuser app when rooting the fireTV (stick) with Kingo root?
Click to expand...
Click to collapse
Just use Kingo roots superuser. Im going to try a few different su versions later see if I have any luck.
At the moment any other than kingoroots will brick, (caun unbrick if in this situation so I guess anyome can try)
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
ftgftg said:
Thanks sconnyuk. I have a bricked Stick from the Feb. KingRoot -> SuperSUMe disaster. Tried a lot of things, no luck.
But the Windows KingoRoot worked on the first try. (No 70% stoppage or anything.) I now have a root shell over adb. I'm going to wait on a rooted ROM to get it back to a normal state, but at least now I have hope.
Click to expand...
Click to collapse
No need to wait. Try this guide ive put together, just do it over usb. Cant see why I wouldnt work.
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298

sconnyuk said:
Connect your fire stick to a windows pc/laptop. (i used windows 10 64bit)
Let the drivers install.
Download the windows version of Kingo root.
Click root, try this a couple of times (it probably will fail and stick at 70 percent)
unplug the stick and try again, when it hits 70 percent again plug your hdmi lead in (already connected to tv)
It should root and write back the correct su files.
If you want to unroot, install kingo and super user again on the fire stick then either use the unroot feature in super user app (you will have to purchase mouse toggle for fire tv, if you havent got it already to navigate to the 3 little dots menu icon top right corner)
Or re plug it into windows pc/laptop and unroot through the windows tool.
Click to expand...
Click to collapse
Thanks for the tutorial. But it doesn't work for me. I have and old fire stick TV with 5.0.5 that I bricked with KingRoot (not Kingo) -> SuperSUMe. I tried to follow your steps and KingoRoot goes to 100% at the first time. But when I connect the stick to my PC it's still stucks at the FireTV Logo . I don't know if I followed some step wrong.
PS: Sorry for my bad english.

SrTommy said:
Thanks for the tutorial. But it doesn't work for me. I have and old fire stick TV with 5.0.5 that I bricked with KingRoot (not Kingo) -> SuperSUMe. I tried to follow your steps and KingoRoot goes to 100% at the first time. But when I connect the stick to my PC it's still stucks at the FireTV Logo . I don't know if I followed some step wrong.
PS: Sorry for my bad english.
Click to expand...
Click to collapse
Try multiple times with Kingoroot, You can try windows version of KING root multiple times also.
Failing this you can try to run both programs simultaneously.
Good luck

sconnyuk said:
Try multiple times with Kingoroot, You can try windows version of KING root multiple times also.
Failing this you can try to run both programs simultaneously.
Good luck
Click to expand...
Click to collapse
It finally works!!!...... almost
Now the sticks pass the fire tv logo, but takes a lot of time to open the firestarter menu. And I can't do anything there. The remote doesn't response. I try to do a factory reset to the stick but I can't find the way . Thank you anyway. At least I can escape from the loop at boot.

SrTommy said:
It finally works!!!...... almost
Now the sticks pass the fire tv logo, but takes a lot of time to open the firestarter menu. And I can't do anything there. The remote doesn't response. I try to do a factory reset to the stick but I can't find the way . Thank you anyway. At least I can escape from the loop at boot.
Click to expand...
Click to collapse
Try removing the batteries and re-pairing the remote, try this multiple times as it has happened to me before.

sconnyuk said:
Try removing the batteries and re-pairing the remote, try this multiple times as it has happened to me before.
Click to expand...
Click to collapse
I thought that I had edited my previous post but it seems that it didn't save the changes. Finally I could restore my fire stick following your downgrade guide. I reinstalled the firmware 5.0.5 and everything works perfect. Thanks a million!!!

SrTommy said:
I thought that I had edited my previous post but it seems that it didn't save the changes. Finally I could restore my fire stick following your downgrade guide. I reinstalled the firmware 5.0.5 and everything works perfect. Thanks a million!!!
Click to expand...
Click to collapse
Your welcome.
Glad I could help.

Hi,
I tried to install XPosed to be able to install Google Play store later following a guide I successfully used on my rooted FTV 1st gen.
XPosed installation went fine but probably I deleted some user file I had not and box started checking for updates. I stopped the process in the meantime. Nothing seems to be affected. Root is still in place and firmware version is still 5.0.5. BUT each time a reboot my stick now it asks to pair my remote, then asks me to choose a language as it wants to complete an update. Just when I goes further it says that it has not been possibile to complete update. I tried to "downgrade" with a clear 5.0.5 firmware zip. It went fine but I had to disable OTA again to avoid the online updates. So it still fails to check for updates and each time it tries to reinitialize update process. basically default amazon launcher doesnt work anymore but it's not a issue cause I have Firestarter 3.3 which works fine. The worst issue is that each time I reboot it asks for rempote pairing and I can't use amazon video anymore. Basically I'd like to remove this "checking for update" process and return to my actual rom. Is that possibile?
Thanks.
puppinoo.

Hoping someone can help me out. My stick is bricked. I loaded up the Kingoroot and tried to run the steps to recover it. However i dont think it's recognize the device since kingoroot is stuck at the loading page. Which driver files did you install for the fire stick? thanks.

Bricked fire stick- any advice
I tried to transfer a ustv4.0 APK zip file to the firestick via USB after some extensive instructions on YouTube video but found that using Google Drive with ES File Explorer would be the quick and easy method. I also got lost in the instructions after downloading ADB and fire starter. When plugging the firestick back into the TV to go the ES file route, the firestick doesn't even show up on the TV now- the HDMI port that I had used would display 'fire stick' and display the HDMI port #, now nothing shows up and then the screen times out quickly as if nothing is plugged in. When I first plugged in the firestick to my windows 10 laptop, I checked the drives and it didn't show up although I could hear a USB connection chime as if something just was connected and if I disconnected it, it had a disconnect chime as well. I did see in device manager before unplugging it that it had shown up as 'unknown device' towards the bottom land labeled as AFTM. Can anyone tell me what they think may have gone wrong and why it no longer shows up on the TV or why it's now not starting up for that matter? Any help would be appreciated.

tjmethod said:
I tried to transfer a ustv4.0 APK zip file to the firestick via USB after some extensive instructions on YouTube video but found that using Google Drive with ES File Explorer would be the quick and easy method. I also got lost in the instructions after downloading ADB and fire starter. When plugging the firestick back into the TV to go the ES file route, the firestick doesn't even show up on the TV now- the HDMI port that I had used would display 'fire stick' and display the HDMI port #, now nothing shows up and then the screen times out quickly as if nothing is plugged in. When I first plugged in the firestick to my windows 10 laptop, I checked the drives and it didn't show up although I could hear a USB connection chime as if something just was connected and if I disconnected it, it had a disconnect chime as well. I did see in device manager before unplugging it that it had shown up as 'unknown device' towards the bottom land labeled as AFTM. Can anyone tell me what they think may have gone wrong and why it no longer shows up on the TV or why it's now not starting up for that matter? Any help would be appreciated.
Click to expand...
Click to collapse
Hi did you find a solution. I have the same problem.
Thx

Is my watch bricked? PC & Device Manager not recognizing watch, drivers are installed

Is my watch bricked? PC & Device Manager not recognizing watch, drivers are installed
I was running on the latest (v2.7) Negalite Rom NX 1 when I got the notification to update the watch. Upon rebooting (and presumably installing), the watch got stuck in loading screen (4 dot animation) so I force rebooted the watch into recovery and wiped everything (Advanced Wipe, everything).
Upon connecting my watch to my computer (watch in recovery (TWRP)), I was not able to connect the watch to ADB nor Fastboot; adb/fastboot devices returns nothing.
I tried reinstalling, uninstalling, deleting and reinstalling the drivers but I haven't gotten any success
I've tried several ports (and another computer) without any success
The watch does not show up at all in Device Manager (definitely not in "Other Devices")
I'm unable to manually install the device drivers because the watch does not show up in Device Manager
The device is connected because it's charging, but there's no notification sound when plugging the watch/USB cable into the computer
I have previously been able to connect the watch through ADB, to be able to transfer Negalite rom, likely half a year ago
I've tried installing Pdanet ADB Drivers, but it requires the watch to be detected otherwise it closes the installer
I am using Windows 10
Has anyone else had this problem? Is there a way to check if the drivers are installed or not?
Every thread I've read instructs to install the drivers manually for the device, but I don't have the device in Device Manager.
I'd love to be able to use the watch again (currently sitting @ 100% battery, in TWRP).
Thank you
Edit: When I boot system from recovery (I know I don't have an OS installed), I get a message that I haven't seen before: "Device software can't be checked for corruption"
I read that it was caused by unlocked bootloader, but I've never encountered that before, if I had accidentally booted system without OS.

HELP! Can't connect MotoG5 to computer.

A while ago, I rooted my phone and flashed Lineage OS. Magisk recently stopped working, failing to hide the root and the unlocked bootloader from other apps. This lead to me being unable to use a variety of nescessary applications. I decided I wanted to flash stock rom, remove the root and re-lock the bootloader. It requires my phone being connected to a pc and using ADB. I connected it, it charges but it doesn't show up on file manager. There is no notification, allowing me to transfer files as well. I tried going to fastboot on my device as well and still fastboot devices returns nothing. Not an issue with drivers as well, as every other phone connects succesfully. I am stuck here with LineageOS unable to flash stock firmware and re-lock the bootloader. Any help would be greatly appreciated.
EDIT: I'd like to also point out that I don't really need to connect my phone to a computer if Magisk works. For now, basicIntegrity is false for me for whatever reason. If I could fix that I wouldn't have the need to connect my phone to a PC. I haven't rooted with any other program apart from Magisk, also don't have Xposed installed. I have no clue why it isn't working.

Try the SafetyPatch magisk module