Hipstreet HS-7DTB26-4GB | Point me in the right direction to root - Android Q&A, Help & Troubleshooting

First I'd like to point out that I found this forum doing searches and came across this post since I do not have the privilege of posting in that area I am reaching out here.
I am trying to root my Hipstreet Titan + (HS-7DTB26-4GB) however none of the usual tools (Tasselhof's Root, 1 Click Root and others) and all of them indicate that my device cannot be found.
This is across 3 computers, Windows 7 32/64bit and Windows 8 32bit.
I've downloaded the Google developer tools and loaded some drivers, while Windows recognizes the device as a ADB /Android Original ADB interface none of these programs connect. I even tried some alternative drivers that make the tablet appear as a Samsung phone to no avail.
In the past I would load files into a memory card, boot the device into the recovery mode and would be able to get the device rooted like that but I am not finding anything at all about this particular tablet, the closest is the original link I've provided.
What should my next course of action be?
Thank you,
SR

sr_droid said:
First I'd like to point out that I found this forum doing searches and came across this post since I do not have the privilege of posting in that area I am reaching out here.
I am trying to root my Hipstreet Titan + (HS-7DTB26-4GB) however none of the usual tools (Tasselhof's Root, 1 Click Root and others) and all of them indicate that my device cannot be found.
This is across 3 computers, Windows 7 32/64bit and Windows 8 32bit.
I've downloaded the Google developer tools and loaded some drivers, while Windows recognizes the device as a ADB /Android Original ADB interface none of these programs connect. I even tried some alternative drivers that make the tablet appear as a Samsung phone to no avail.
In the past I would load files into a memory card, boot the device into the recovery mode and would be able to get the device rooted like that but I am not finding anything at all about this particular tablet, the closest is the original link I've provided.
What should my next course of action be?
Thank you,
SR
Click to expand...
Click to collapse
2 days later, I'm still not having any luck.
Tried every driver I can find, some are accepted and show the tablet as a ADB device, other do not work.
I cannot be the first to have a tablet that is not picked up by all these tools available - any guidance would be greatly appreciated.
SR

Related

My ADB & Vibrant Story

Mods, if this belongs elsewhere, feel free to move it.
I read many many threads about people's problems with adb on the vibrant and while there were no individual threads that matched exactly, little pieces from many helped me in my situation; in case someone else experiences what I had, this is what I did to fix it.
Environment:
Win7 Professional N x64
Vibrant (SGH-T959:2.1-update1/ECLAIR/UVJI) (this was the leaked ROM mid Sept)
Samsung x64 drivers from TGA_Gunnman's thread (forum.xda-developers.com/showthread.php?t=728929)
USB Debugging enabled
Problem:
I was able to get all the components of the phone recognized in device mgr & I was able to mount both the internal SD and my 8gb external SD cards, read & write to them with ease; I was even able to flash the leaked ROM via ODIN. I was NOT able to get adb to connect to my device.
C:\vibrant\adb devices
List of devices attached
T9596f3efa91 offline
I tried in recovery mode, no dice.
I had tried Droid Explorer, it was unable to find my device as well.
I had read somewhere that it was a driver problem, although dev mgr wasn't complaining and everything else appeared to be working just fine. One person noted they were able to use the Samsung Moment drivers from JuneFabric's website. I tried to install those drivers and was met with an error during the installation that said windows was unable to locate the file. Uninstalling, rebooting, reinstall (as many times as I had...) had no effect.
I grabbed USBDeview (thanks to masr1979's post in forum.xda-developers.com/showthread.php?t=735534&highlight=masr1979) and uninstalled every android related driver. Rebooted and when prompted for the drivers, tried the moment drivers only to face the same "unable to locate file" error. I got fed up and tried going back to the drivers from TGA_Gunnman's thread which brought
me back to the start. Atleast I was able to mount my sd cards.
Solution:
Not satisifed with this, I went to Samsung's website and found drivers for XP/Vista... i can't for the life of me re-navigate to that download page, but I have uploaded the drivers here.
After running USBDeview to nuke everythign samsung/android related (again) and rebooting, I plugged my phone back in - pointed it to the extracted folder for the attached drivers, ignored the "unsigned drivers!" error for all three devices and re-tested DroidExplorer. SUCCESS! Droid Explorer found my phone and adb (console) also shows my device attached! Everything is golden.
Summary
Random-assed drivers found on Samsung's site for XP/Vista (attached) matched what my Vibrant wanted on Win7x64 in order to get data and debugging connectivity.
Thanks
(edited for the attachment which didn't stick? & stupid 5min wait to post )

HKC p771a 7 inch Tablet Root

I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment Rockusb.rar
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
Thanks for the info. Will be giving it a go later today
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
when in doubt go back to the forums. I can not get the inf in the rockusb to install. "Installation for this file type not permited" . So I'm stuck, the program will not complete. I'm on windows 7 so maybe the driver is for another system. If you can provide futher help, Thanks in advance.
New approach
Ok I cannot get the drivers to install on my computer. Window 7 seems to default to its own driver and will not let me install the rockusb drivers.
With that said, I have the system Update.img and was wandering if the img itself can be rooted and then updated to the tablet. If this is possible and anyone with the knowledge is willing I will upload it. Or if someone is really patient and would like to walk me through the process and I will attempt to do this myself
No Help
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
Can't tell your level of PC knowledge so if you already know this don't get offended. The .inf is editable and there are areas in there that allow manufacturers to prevent installation on some OS's to prevent conflicts. Make a system restore point or better yet a backup and then post the contents of the INF somewhere and point the folks here to it and they may be able to help you edit it to install. Regardless, you'll have to use the "have disk" option instead of letting windows search for a driver even if you get the edits right. And the usual disclaimers about me not being responsible for any issues with your equipment as a result of this are in effect.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
I was able to root using the instructions above although i don't think you need the rockusb drivers. You just need the usb drivers that come with the android sdk. I am on Win 7. Thanks for the above info for rooting.
I was able to install ROM manager and now proceeding to backup ROM and upgrade using this guide: cant post link as forum is preventing, but search for rom flash guide on androidpolice com.
Hope this helps.
Big thanks to this thread to get me going...!!!
?
could someone please, Barney style, Explain how I am supposed to select the android_winusb.inf because my steps are as follows. Right click on device p771a in device manager, browse my computer, let me pick from a list of device drivers, have disk, point to the google usb driver (C:/Android/android-sdk/extras/google/usb_driver) select the android_winusb.inf open. Hit ok, (The folder you specified doesn't contain a compatible software driver for you device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems). Hope this helps explain my troubles. Glad that my thread is helping others to root this device but it does not work for me.
Could it really be that simple?
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
tannerjames said:
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
Click to expand...
Click to collapse
Glad you could figure it out...
I was not able to use the ROM Manager to backup the ROM since the device is not supported on this tool, but see below for how you can obtain the stock image.
I've tried to flash multiple different ROMs using RKAndroid to the tablet, spending days on this, with no success. The tool itself works great and I am able to flash the ROMs since it supports the RK29 chipset which I believe this tablet has. The stock ROM for this device is available from the manufacturers web site (the link is available when you go to Settings => About Device => System Update, hkcdigital dot com slash update slash update.img), if anyone would like to take the stock rom and upgrade it to Android 4.2/JB.
I was able to unpack/repack the stock image using the wendal image tools and modify / cook the ROM using Android kitchen method described elsewhere in this forum. Rockchip Batch Tool is another great utility to flash custom ROMs to this device. Also, If you put the ROM as update.zip or update.img file on the microSD card, the tablet will take it and flash the image as long as it is in the right format. Ofcourse you can put the tablet into recovery and restore from there as well. I've found that the stock image (update.img) has the following file/folder format when unpacked: /RK29xxLoader(L)_V2.27.bin, /package-file, /parameter, /recover-script, /update-script, /Image/boot.img, /Image/system.img, /Image/recovery.img and /Image/misc.img.
Is it possible to upgrade this tablet to Android 4.2 or atleast Jelly Bean? Would be very helpful if someone is able to do this. The most success I've had so far is with the custom ROM Oma_Odys_Loox_JB_4.1.1_v1.2.2a flashed using RKAndroid. It flashed the tablet fine, updated the boot etc. On tablet boot I am able to see the new logo, but then the it doesn't go anywhere from there. I think customizing this ROM or the stock ROM we should be able to get the new OS on to the HKC tablet. I've given up for now since I don't have the time to spend on this anymore. If someone is able to do this, please post the instructions or upload the custom ROM, as I am sure it will benefit a lot of people and will be much appreciated. Happy cooking!
Thanks!
jawadshaik- rom manager
If you have successfully flashed rom manager on this device could you post the steps you took to do so. What version? Manual flash? The program itself says there is no recovery for this device.
Sorry jumped the gun on that last post. Thanks for the info
What's the secret to keeping the battery from draining so quickly while it's idle? I just got this and see it drained about 40% in about 2 hours I think and I wasn't using it.
tannerjames said:
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
Click to expand...
Click to collapse
@jawadshaik
Just out of curiosity, when you were flashing that Rom that brought up the boot screen, did you do a wipe/factory reset from recovery mode before flashing? I have no idea if that would help or not, but most if not all roms require a data wipe before flashing... Just curious if you had tried this as I have heard of this happening on other devices because a data wipe wasn't done first. Might be worth a shot if you haven't tried it already, just a thought
Sent from my Huawei u8651s using xda app-developers app
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
So after doing working on this a while, I've finally figured it out. Here are some caveats:
1. You can't do this on a Mac or Linux box. Don't ask me why, you just cant.
2. You have to turn on USB debugging, change the Security to allow Unknown sources and MOST IMPORTANT: when you plug it in, you have to change it to "Connected as a Camera". Putting it in storage mode doesn't work!
HOW TO INSTALL THE PROPER DRIVER & ROOT THE DEVICE:
1. Follow the steps quoted above and download the Google Android SDK, and the Java JDK (from oracle.com/java).
2. When you first plug it in (use the USB plug labeled USB not the HOST one), it complains and will discover a P771A device. When it does, right click on your computer, choose Manage my computer, go to the device manager and then right click on the P771A device. Click "Update Device Driver". Choose "Browse my computer for Driver software". Then choose, "Let me pick from a list of drivers on my computer". Browse to the \adt-bundle-windows-x86_64\sdk\extras\google\usb_driver folder which you would have if you had downloaded and installed the Google Android SDK. A list of 3 drivers will appear when you click OK. CHOOSE THE "ANDROID BOOTLOADER INTERFACE" as the driver. None of the others work.
3. Run the root script batch file mentioned above which can be found here at: sourceforge.net/projects/androidroot
4. The root script isn't really great at explaining so I'll try. When you first run it, make sure your device is unlocked and on the home screen.
5. The first thing it will do is reboot your machine. Don't press enter until your machine comes back up.
6. After your machine boots unlock it and then press Enter again. Your machine will reboot. This time it won't seem to come up but the backlight will remain on.
7. Wait about 30-45 seconds then press enter again. You should get: uid=0(root) gid=0(root) in the command prompt window.
8. Press Enter. You should get:
remount succeeded
727 KB/s (22364 bytes in 0.030s)
Removing changes except ROOT...
Installing superuser...
2288 KB/s (843503 bytes in 0.360s)
9. After about 30-60 seconds, your device should reboot. You'll see a box briefly saying "Android is Upgrading" and you'll arrive at the lock screen. Press Enter to exit the command prompt.
Your device is now rooted and you should see "SuperUser" installed. I promptly installed "root uninstaller" to get rid of Facebook, Skype, and Youtube which my little kids don't need access to. This device doesn't have a bootloader or recovery mode so rooting it doesn't get you much besides the ability to uninstall the system software. Have fun.
This may help someone but on step 2 of the guide on the second page, after you right click your device and go to "Let me pick from a list of drivers on my computer". You then click "Show All Devices" then "Have Disk..." Direct it to the root of the adt-bundle folder you downloaded then you can select from the three drivers. I'm on windows 7 32bit and the drivers didn't show up for me like how it was suppose to..
I also could NOT get any of the drivers in the "manufacturer USB" packet to install... I WAS able to install the google drivers, but that also would not allow ADB to see the device... So still stuck with everyone else...
P771A possible problem
I'm having a similar problem where the USB driver downloaded through Android SDK's -> Extras -> Google USB Driver, tells me that the file contains no information about my device. I noticed in the Sources of SDK, there wasn't an API for 4.0.4, only 4.0.3 then 4.1, so i downloaded 4.0.3 repo.
============================================
my devices is on 4.0.4, and my Kernal is as follows:
3.0.8+
[email protected] #8
Wed Aug 29 09:59:19 PDT 2012
Build Number:
P771A-user 4.0.4 IMM76D user.v402.007 release-keys
============================================
I've also made sure weather Unknown Sources is on, as well as USB debugging.
Might the Kernal be the problem? Also, does it matter weather its MTP or CTP?
Now HKC is telling me that they don't support the ability to jail break their devices
Sent from my P771A using xda app-developers app

[Q] AOCOS PX102- Attempting to root, but having issues finding the device via ADB

Hello All,
So there is very little documentation on the PX102 online as of yet, let alone AOCOS products in general (at least on english sites which I have scoured). First off, I'm currently using OSX 10.6.8 and have the current Android developer tools package that was downloaded from their site about three hours ago (just to be clear). The PX102 is running 4.1.1 and the tablet is a fresh restore (I had a number of apps downloaded but considered that some may have been interfering...).
I will be attempting to root via psneuter exploit from SuperOneClick v2.3.3, however in the terminal when I execute "adb devices" it returns "List of devices attached" with blank space underneath...
I have tried to kill/restart server, run "adb usb", and a couple other small things to no avail.
Yes, usb debugging mode is enabled as well.
I would really like to attempt/execute this all via OSX, however name an OS and I have it at my disposal...
I admit- I am a noob in various ways, especially to android as this is my first android device. Hoever, I also consider myself to be rather self sufficient in terms of sourcing knowledge and troubleshooting, which is why I humbly ask for guidance in this endeavor.
Also, feel free to ask me any questions about the PX102 (via PM only please! I dislike threads being fuddled with asides...).
I'm not seeing too many people claiming to have these tablets though there is quite a bit of interest in them.
Anyone?
For windows you can try rkbatchtool v1.5 to get the correct drivers
Rooted mine
I rooted mine, wasn't easy though.
First problem, you need a adb driver that works on this rockchip tablet that doesn't have a built in ADB driver. Also I didn't have much luck on the chinese language AOCOS forum.
The only way I found to get one is:
1) download and install the morborobo phone manager software from moborobo.com. Yes this is a risk to your pc. God knows what else it did to my pc.
2) let IT find a driver. It will download and install two unsigned drivers.
3) those drivers aren't enough. You need to generate adb_usb.ini in c:/Users/%username%/.android/adb_usb.ini (if you're on windows 7)
Installing the SDK does that automatically otherwise you need to run "android update adb" or something to generate it
4) put the vendor id at the end of adb_usb.ini in the case of AOCOS the vendor is 0x2207
I tried using a premade adb_usb.ini with all of the vendor ids. That didn't work. It worked when I put the right on only.
NOTE, that vendor ID exists nowhere online. I had to find it by reading it directly from the device using USBVIEW from http://digital.ni.com/public.nsf/allkb/335A90747734097886257070006415B9
5) Now you should have a working adb driver. Plug the machine in and type "adb devices". It should see yours
6) now comes the rooting.
Follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1886460
The script is here: http://uploaded.net/file/0fpyh5c5
the videos showing how are here http://forum.xda-developers.com/showthread.php?p=33470626#post33470626
Note there IS a hacked adb driver that doesn't need a vendor ID, BUT it doesn't work for rooting, it's too old to have the restore feature you need for a jelly bean root.
The PX102 is cool, but mine has some problems:
1) the keyboard charge connector is bad, I have to send it back
2) the battery sucks... I'm sending back the tablet too, hopefully that will fix it
3) never drop one of these, mine only fell a couple feet and it's flaky now. :/
4) the camera is fake. It's not the 2mega pixels it says. It's super low quality and maybe vga. They put in bull**** fractal interpolation software to try to fake higher res
The keyboard is no where near as nice as a transformer, the tablet only rests on the keyboard and can fall off.
Still it's a nice machine. I have my memory cards formatted ext2 (from a previous tablet). I can mount them but the machine won't boot with an ext2 card plugged in. I have to take the card out, boot the machine, then plug it in and mount it.
I even managed to install GNU Gcc/ gnu tools
You can also try this: http://www.androidtablets.net/forum/rockchip-rk3066-tablets/46964-root-your-rockchip-3066-a.html
Or this: http://valentijn.sessink.nl/?p=382

[Q] CyanogenMod 11 -> Eclipse/ADB not detecting YP-G1 device

Howdy.
I recently updated my YP-G1 from CM10 to CM 11 [4.4.2]. I need to use my device for Android app development (and have used it before way back when it was on stock, but haven't used it in a very long time), but am unable to get ADB/Eclipse to detect that there is a device detected. Using the emulator is not an option at this point, as I need to do some work with a real camera.
I've got the Android USB debugging enabled on the device, and the little notification that debugging is enabled comes up when I plug it in.
Things I've tried:
1) Update Eclipse/ADT (complete uninstall + reinstall)
2) Update Google USB Driver (from SDK manager)
3) Update Samsung Kies
4) Google
The only related forum thread that I've located for this situation is: http://forum.xda-developers.com/showthread.php?t=1776828, which just implies that Windows should be auto-detecting the device. Windows is not doing that.
I have noticed that the YP-G1 drivers do not show up as installed under Device Manager. Perhaps that is the source of the problem? I have not been able to rectify that situation via Kies, so I am unsure. Kies doesn't even detect that the device is connected!
If it matters, I'm running on Windows 8.
Thanks much.
P.S. -- I'd post in the CM11 thread, but since I just registered, I am not allowed to do so, unfortunately.
Edit: I got mine to work finally. I solved my issue by allowing windows to automatically search windows updates for drivers. After I did that it found them and it worked, so try that.
I too am having this issue and it's really bugging me. I've tried everything I can possibly think of but I cannot get the drivers to install. I'm using windows 7 64 bit and it sees the YP-G1 but it doesn't have the drivers so things like kies and adb won't detect it. Any solution would be very helpful.
Strange...that's what the thread I linked to suggested. I've tried that multiple times to no avail. Perhaps Windows 8 doesn't find it, while 7 does for some reason? I've tried doing searches via both Device Manager and Windows Update.
Could you perhaps upload the driver files it found? You should be able to figure out what/where those are by using Device Manager, then right click the YP-G1 and go to Properties, then the driver tab, then driver details. Maybe they'll work on Windows 8 as well as 7. I might try plugging my device into someone else's computer to see if somehow mine is just acting stupid.
Thanks for your reply!
Edit: I've plugged my device into another computer. You're right -- on Windows 7, it can find the drivers just fine. On Windows 8, it can't. Go figure. Now to figure out where to get those files and/or how to get the device recognized..... (??)

Question How to get a list of Samsung Tab A8 devices installed to be able to debloat my device.

Hi, I have been trying to “debloat” my Samsung TabA8 and have been trying to do it for some days now. Have done everything according to online directions )Developer Options, debugging, etc.)
My problem:
When opening ADB power shell, I get only the list of some of the installed apps on my laptop with Windows 10, but no apps on the Samsung Tablet. Win10 apps then ask me how I want to open those apps. Some of my choices are: Notepad, Open Office,Google Drive, Internet Explorer.
I have tried all of them. Nothing is working.
How do I get a list of Samsung full apps list on the desktop power shell window??
Just entering for instance: “adb shell pm list packages“ or: “com.samsung.android.apps.spage” is not recognized. I have tried several others also.
I have done all of the online remedies and tried the same thing with another tablet-same problem. Nothing seems to help. There is probably something really easy I am missing...(I hope)
If anybody has any suggestions/advice, I would appreciate it very, very much.
uses platform tools then uses adb from inside them not powershell.
read it here https://developer.android.com/studio/releases/platform-tools
Thank you very much for taking the time to reply. Yes, I have been using the platform tools app. Also, made sure that the drivers are up to date. My problem starts in the platform tools power shell. Samsung apps are not visible there. In the past, before adb + develpoper options ,etc.,connecting the tablet to the laptop via usb, I can see the content and can delete pictures, etc.
So, I'm doing something wrong somewhere with adb.... I would really like to disable and render invisible some of those pesky Samsung apps without rooting. Have rooted my Nexus several years ago. It was great. I just don't want to lose the warranty for now.
Again, thank you. If you have any other suggestions, I will appreciate it very much.
Update...I just realized that the problem is probably with adb and power shell. At opening at the top it reads:
"PS C:\ User's \Ann\ Desktop\adb setup"
Is it not completly set up?
A few days ago,I have unzipped, and agreed to install Fastboot, ADB system-wide and installed Device Drivers. If I right click, it wants me to install again. Have done it a couple of times.... Still, it just isn't working...
Again...thank you!
Oh, one more thing I failed to mention is that this tablet is WiFi only. Does it make any difference? I want to debloat it first before doing it on my Samsung S22 phone.
-Device Driver installation problem (your wins)
-Platform tools (adb,fastboot) run with CMD from inside this folder.
you known howto fix it. wins problem.!
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
You should also replace your adb with the latest binaries by Google.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download the platform tools for windows zip file. Find out where your current adb.exe file is located. Extract the zip into that location, overwrite the old file(s).

Categories

Resources