My Nook Tablet just updated to the dreaded 1.4.1 version which makes sideloading pretty difficult.
I was reading this article which has steps to sideload apps onto the 1.4.1 NT without rooting it, and pointed to downloading this script on the XDA forums which will push the apk onto the plugged in tablet, as long as the apk is in the same folder as the Sideload script files.
So, steps 1 to 5 weren't a real problem but its Step 6 that I'm stuck on.
There is a Sideload BAT script which seemed to run (its disclaimer is that it will only run if it finds an Android device -- which is a clear indication that it could find and recognize that my Nook Tablet is plugged in). It even says C:\Sideload>adb wait-for-device. However, when I try to tell it to install the apk via Command Prompt (I type in: adb install Amazon_Appstore-release.apk ), it returns "error: device not found" .
Just for good measure, I also type in C:\Sideload\adb devices and it returns: List of devices attached .
I'd greatly appreciate if somebody could help me with this--I really have it up a wall and would just like to put this problem to bed. Thanks!
i'm having the same exact problems here! are there any specific drivers to install?
Yep, I was still fairly a noob at this when I first posted but have learned a lot ever since. Here's what you want to do:
(btw, I factory resetted to 1.4.0--you may need to as well):
When it says "no device found", it's corresponding to this command line : adb install whatevernameofapp.apk . I interpreted "no device found" to mean that it does not know what "adb" means in the command.
For it to recognize all "adb" related commands, you have to have the USB drivers installed. Look for tgps_launcher.apk on this link: http://forum.xda-developers.com/showthread.php?t=1354487. That will set you up with having you Nook to accept third party applications + having it on UBS debug mode.
Then, install the drivers (I saw this YouTube walkthrough because it is NOT intuitive and you want to be sure you're doing it right , it's not the way you would traditionally update drivers for a mouse or keyboard; here: http://www.youtube.com/watch?v=ZtGveN7jbzs )
After that, I followed the instructions on this article, made a folder in C:, called it sideload, and also pasted an .apk. Now, when I do the Commant Prompt, it says this: http://img23.imageshack.us/img23/2914/cmdnookadb.jpg . While, the transfer was successful, I haven't been able to see the app on my tablet. Does anyone know where I can find this (data/local wasn't found when I connected the tablet to my PC either, and it wasn't on my SD or so). Is it because I'm still on 1.4.0?
Let me know if you get it working all the way!
I followed all those directions exactly. I had received the No Device Found error. I followed the Youtube directions to add drivers and it seems like I did it correctly. I am seeing the android device on the device manager.
I tried running the script again and got the same error! I'm now stuck!
I had the amazon marketplace already installed and was using it successfully until my nook updated to 1.4.2. I thought I had ES File Explorer downloaded but for some reason I can't find it! So I now I am trying to sideload ES File Explorer this way but it wont work!
0x2080
^ put that in %userprofile%\.android\adb_usb.ini
Can you give me more specific instructions on how to do that?
FYI - I have ver 1.4.2 and I am NOT rooted. I have already enabled unknown sources and downloaded the amazon market. I was installing 3rd party apps fine before the update.
[HOW-TO] Use ADB tool | Android Debug Bridge
You need to revert to stock 1.4.0, there are easier and faster ways to do that now > check development section. Basically you need to have CWM booting from sdcard then flash stock ROMS posted >> Albert and I have posted 1.4.0 stock ROMs.
~ Veronica
Moved To Q&A
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
Im trying to root my kindle fire hd (version 7.4.8)
Every time i use Kindle Fire First Aide on the command prompt it says that i have a system path not specified error.
My laptop operating system is windows 8 ( I have not upgraded yet to latest version so I don't know if that's the problem)
Any Help would be appreciated
Steps I Used
1. Download KFFA
2. Opened KFFA using cmd
3. Used option 21 : Alternative root: newer devices
4. Says system path is not specified
5. It starts a daemon but thats all it does
P.S Im not sure but it also looks like i have a adb problem
I turned on the ADB with usb and used the adb drivers in KFFA but it never works
I'm having a similar problem.
I've had my kindle rooted for several months now, and I'm sure that I had turned auto updating off...however, this update (7.4.8) was forced on me a couple of weeks ago, and now I've lost the ability to usefully run Google Play (it keeps giving me a 'no connection' error). I also cannot update any programs that were obtained through google play.
A few things that I have noticed:
BusyBox Installer says that my Kindle is rooted, but cannot install BusyBox, or run any of the scripts.
KFFA cannot access my Kindle. I have tried several proceedures on the forums to rectify this problem, to no avail. I have tried with several cables including the original, and the cable that I previously successfully rooted my kindle with.
My kindle has started showing ads on the lock screen at times, which was something I disabled with KFFA when I first rooted my kindle.
I do have momentary adb access while booting, but it gets disconnected as soon as the lock screen appears and I cannot reconnect
same problem here, can't manage to root kindle with 7.4.8
RE:
Well then i guess it will only work if you brick your kindle to reboot over and over then root and use kffa to root it then unbrick it using it and i think it will work let me try
Successfully rooted Kindle Fire HD 7.4.8
Hi,
So this morning I reset to factory my KFHD 7.4.8. Clean start...
1/ install KFFirstAid from geekappz.blogspot.com/2013/02/root-kindle-fire-hd-and-2-with-windows.html
I did install the 64bit version on my windows 7.
2/ execute all installation steps of KFFA as explained in the link above until reaching C-1 root step 10 (do that step 10).
3/ connect your kindle to your computer via USB
4/ the runme.bat in KFFA depends on another system package called busybox. Great package but... you cannot install from amazon store on a fresh kindle, and the installation via the runme.bat does not work. I decided to do without busybox... So replace the original runme.bat in C:/KFFirstAid by the one attached. I edited the sections 18 and 21 (i "rem"ed some lines, and put the corrected code just below). I edited only these two options. (means do not ask about the others...)
(site did not upload the file, so here is a link to it... drive.google.com/file/d/0ByEA1ADGX9vNS2RKUEdKYnN6Uk0/edit?usp=sharing)
5/ launch "my" runme.bat.
6/ select option 21. This will root the kindle. Follow the instructions (including the full restore at the beginning). It will reboot quite a few times, just be patient... (very). Your kindle may seem up and running, but the adb communication may take a few more minutes to go through...
At the end, superuser.apk is installed, look for it in the command window log. When done, on your kindle, start supersu and let it update itself. Verify root access with root check basic.
7/ return to the main menu of runme.bat,
8/ select option 18. This will install google play. Follow the instructions, including the registration to google on the kindle, in the middle of the installation. During this registration i experienced a few "application stopped working", but it went through anyway... so do not panic...
Again, a lot of reboots...
That's all folks... (takes about two hours...)
Successfully Rooted KFHD 7.4.9
Still works for KFHD 7.4.9
Replaced some "mv" commands by "dd" commands to workaround a cross device link error, in the runme.bat file.
fabienwahl said:
Hi,
So this morning I reset to factory my KFHD 7.4.8. Clean start...
1/ install KFFirstAid from geekappz.blogspot.com/2013/02/root-kindle-fire-hd-and-2-with-windows.html
I did install the 64bit version on my windows 7.
2/ execute all installation steps of KFFA as explained in the link above until reaching C-1 root step 10 (do that step 10).
3/ connect your kindle to your computer via USB
4/ the runme.bat in KFFA depends on another system package called busybox. Great package but... you cannot install from amazon store on a fresh kindle, and the installation via the runme.bat does not work. I decided to do without busybox... So replace the original runme.bat in C:/KFFirstAid by the one attached. I edited the sections 18 and 21 (i "rem"ed some lines, and put the corrected code just below). I edited only these two options. (means do not ask about the others...)
(site did not upload the file, so here is a link to it... drive.google.com/file/d/0ByEA1ADGX9vNS2RKUEdKYnN6Uk0/edit?usp=sharing)
5/ launch "my" runme.bat.
6/ select option 21. This will root the kindle. Follow the instructions (including the full restore at the beginning). It will reboot quite a few times, just be patient... (very). Your kindle may seem up and running, but the adb communication may take a few more minutes to go through...
At the end, superuser.apk is installed, look for it in the command window log. When done, on your kindle, start supersu and let it update itself. Verify root access with root check basic.
7/ return to the main menu of runme.bat,
8/ select option 18. This will install google play. Follow the instructions, including the registration to google on the kindle, in the middle of the installation. During this registration i experienced a few "application stopped working", but it went through anyway... so do not panic...
Again, a lot of reboots...
That's all folks... (takes about two hours...)
Click to expand...
Click to collapse
Root Kindle Fire HD 7.5.1
Still works for KFHD 7.5.1
Option 18, to remove Amazon adds has been recoded in "my" runme.bat
Use also post below to remove an additional file (the kso file is now removed by the option 18 above)
http://forum.xda-developers.com/showpost.php?p=52046640&postcount=73
fabienwahl said:
Still works for KFHD 7.4.9
Replaced some "mv" commands by "dd" commands to workaround a cross device link error, in the runme.bat file.
Click to expand...
Click to collapse
Hi everyone, I recently purchased a tablet on Amazon, which is slowly gaining a lot of fame for its really affordable price .Unfortunately I was unable to find information on the specific rooting procedure for this device. I hope someone knows how to recommend a way to solve the problem, thanks to everyone anyway
PS: I have already tried several OneClickRoot applications like Kingo Root, KingRoot, Framaroot and 360 Root.
Tablet information:
Tablet name : H7 pro
Brand name : Haoqin
Device model : H7_EEA
Android version : 9
Android security patch level : August 5, 2019
Kernel version : 4.4.189
Build number : Winnovo_H7_V1.7_20200406
nubrox99 said:
Hi everyone, I recently purchased a tablet on Amazon, which is slowly gaining a lot
...
Kernel version : 4.4.189
Build number : Winnovo_H7_V1.7_20200406
Click to expand...
Click to collapse
Hi,
Unfortunately I didn't even found the firmware file for your tablet so I doubt someone will be able to root it successfully without those files.
Have a good day
nubrox99 said:
PS: I have already tried several OneClickRoot applications like Kingo Root, KingRoot, Framaroot and 360 Root.
Click to expand...
Click to collapse
My POV: Those so-called One-Click-Rooters all are crap. Most of them are heavily outdated, not applicable on devices with newer versions of Android as with Android 9 GO what is installed on your device. For example KingRoot you tried only may work on devices with Android versions up to version 5 & Framaroot you also tried only may work on device's with Android version less then Pie.
And worst: They may even inject trackers as it's reported in WEB.
In short: You have to root your device's Android manually by yourself, of course only if supported by OEM/Carrier. To verify this boot into device's Recovery and look for option "apply update from adb".
If NOT present then simply stop further reading.
How-To:
In Android's Settings->Developer options enable "USB debugging"
Install ADB-driver on your computer and make it systemwide accessible, means add its location to PATH environment variable and re-boot computer
Download SuperSU Pro
Rename the downloaded ZIP-file to update.zip and move it to folder where ADB-driver is housed
Make sure your Android is charged over 60%
Connect your Android device with computer via USB-cable
On computer open command prompt: [Win]+[R], input cmd and press Enter-key
Run commands - one by one
Code:
adb devices
adb reboot recovery
Don't close command prompt window!
In Android's Recovery menu select option " apply update from adb" and confirm by pressing power button
On computer run command
Code:
adb sideload update.zip
The zip.file will be sideloaded and written in your Android. The process will take quite a long time, so please enjoy yourself with something during the period. When it completes, you can see something like "Install from ADB complete" on the screen.
As last step on computer run command
Code:
adb reboot
Close command prompt window
You also may delete file update.zip: it's no longer needed
I hope I've made it clear to you.
jwoegerbauer said:
Code:
adb sideload update.zip
Click to expand...
Click to collapse
Hi jwoegerbauer , thank you very much for your timely and detailed reply, sorry if I did not answer immediately.I tried with your suggestions, but when I do this step, it gives me an unrecognized device error (in fact the adb devices command give me an empty list) .Checking on google, I noticed that it is a driver problem and then the phone is not recognized in recovery mode but, always on google I was unable to find a guide to solve the problem. On the android developer site I downloaded a file zip called "usb-driver", but when I update the drivers and set this folder as a directory it gives me this error: "The specified folder does not contain a software driver compatible with the device. if there is a driver in the folder, make sure it is designed to work with windows for x64 systems "
I hope it is not my mistake or that it is something resolvable anyway, I wait and trust in your further clarification if possible
@nubrox99
The driver package usb_driver_r12_windows.zip you downloaded isn't the expected one, it's only meant to be explicitely used with Google devices. Typically the USB-driver gets downloaded from OEM's/Carrier's website. If not provided by them, then the Universal ADB Driver should get installed.
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).