Related
I need help figuring out how to root a RCA RCT6077W22 tablet. It has Android Jellybean 4.1.1- v1.0.1, 8GB built in storage, 1GHZ processor, Google apps installed, kernel is [email protected]#132.I'd like to try to root it from the tablet itself if not I'm familiar with SuperOneClick as I've used it for my Samsung Galaxy S 4G before I should it. If it comes to that option I need to be able to use a rooting program on my computer that does not require internet the only internet I am able to use is the libraries. I have a laptop but no charger so my laptop is dead. I'm not a noon when it comes to rooting as I've mentioned I've done it before. Just need help finding a root for this tablet. I appreciate any help I get and thank you. If you need more info feel free to ask. I've also looked at the topic about the 4GB but its not that helpful is why I created my own topic.
deathscreations said:
I need help figuring out how to root a RCA RCT6077W22 tablet. It has Android Jellybean 4.1.1- v1.0.1, 8GB built in storage, 1GHZ processor, Google apps installed, kernel is [email protected]#132.I'd like to try to root it from the tablet itself if not I'm familiar with SuperOneClick as I've used it for my Samsung Galaxy S 4G before I should it. If it comes to that option I need to be able to use a rooting program on my computer that does not require internet the only internet I am able to use is the libraries. I have a laptop but no charger so my laptop is dead. I'm not a noon when it comes to rooting as I've mentioned I've done it before. Just need help finding a root for this tablet. I appreciate any help I get and thank you. If you need more info feel free to ask. I've also looked at the topic about the 4GB but its not that helpful is why I created my own topic.
Click to expand...
Click to collapse
Did u figure out how to root your rca tablet....I have one and I need mine rooted also I can't store any apps on my ad card
Can you give more specifics such as the the model number, what version of android is it running?
Sent from my Nexus 5 using xda app-developers app
I have the rct6378w2 RCA 7' 8GB tablet (4.2.2 JB). (Black Friday 2013 Walmart for $49)
I was able to root it by first installing the pdanet drivers (for adb access). And then using the kingo app, which you can get from http://www.kingoapp.com/.
Its free but closed source. I found it via this youtube video. https://www.youtube.com/watch?v=8MiZtZCqu4k
Worked even with the 1.0.2 update installed (which I have no clue what it did (17MB).
Takenover83 said:
I have the rct6378w2 RCA 7' 8GB tablet (4.2.2 JB). (Black Friday 2013 Walmart for $49)
I was able to root it by first installing the pdanet drivers (for adb access). And then using the kingo app, which you can get from http://www.kingoapp.com/.
Its free but closed source. I found it via this youtube video. https://www.youtube.com/watch?v=8MiZtZCqu4k
Worked even with the 1.0.2 update installed (which I have no clue what it did (17MB).
Click to expand...
Click to collapse
TAHNK YOU Takenover83 you are amazing. I rooted my tablet same model and set up as yours.
frarredo here is the information you were asking about in the picks below..
Please take notice to picture Screenshot_2013-11-29-23-15-32.png running bubble launcher, xposed framework , and xhalofloaingwind, to muliwindows on the tablet and all android phones,
Sorry here is the last pic it did not let me upload
Help
Takenover83 said:
I have the rct6378w2 RCA 7' 8GB tablet (4.2.2 JB). (Black Friday 2013 Walmart for $49)
l]
Worked even with the 1.0.2 update installed (which I have no clue what it did (17MB).
Click to expand...
Click to collapse
I cannot get pdanet to get the drivers. I cant find any drivers anywhere. Pdanet says to click ok after connecting, and it just says no android device found..I think there's an error box too.. I don't know how to fix it. I also have the tablet from the black friday event. Exact same one. Also, I have USB debugging on...
UPDATE: I found out the problem! The support files weren't in the root file I had the .exe in. I just moved the .exe to the same folder with the support files, and now I'm rooted and ready! Thanks!
wy3r5 said:
I cannot get pdanet to get the drivers. I cant find any drivers anywhere. Pdanet says to click ok after connecting, and it just says no android device found..I think there's an error box too.. I don't know how to fix it. I also have the tablet from the black friday event. Exact same one. Also, I have USB debugging on...
UPDATE: I found out the problem! The support files weren't in the root file I had the .exe in. I just moved the .exe to the same folder with the support files, and now I'm rooted and ready! Thanks!
Click to expand...
Click to collapse
how are you turning on usb debugging? I also have this tablet(purchased on black Friday from Walmart like everyone else) and mine doesn't seem to have that option anywhere. in fact, compared to the previous two android products I have, this device seems to lack ALOT of available functions. though I am capable of navigating a recovery menu at boot. but that doesn't do me any good for using pdanet. that seems to be my biggest road block. pdanet wont install because the onl;y way I can allow my device to connect to my pc with adp is using the adp updater in the recovery boot menu.
Desarial said:
how are you turning on usb debugging? I also have this tablet(purchased on black Friday from Walmart like everyone else) and mine doesn't seem to have that option anywhere. in fact, compared to the previous two android products I have, this device seems to lack ALOT of available functions. though I am capable of navigating a recovery menu at boot. but that doesn't do me any good for using pdanet. that seems to be my biggest road block. pdanet wont install because the onl;y way I can allow my device to connect to my pc with adp is using the adp updater in the recovery boot menu.
Click to expand...
Click to collapse
It is a hidden option that needs to be enabled. Follow this guide: www ninjaromeo com / enable-usb-debugging-developer-options-jelly-bean/
I just enabled this option on my Walmart BF 7" RCA RCT6378W2 tablet.
Sorry I had to mangle the link because XDA wont let me link external sources yet.
Glad I could help a few. Now, someone get on a functional recovery ;p
I have poked around a little at the stock recovery, backing it up, etc.. But am not brave enough to try and get CWM working on it.
I was able to use th Xposed framework for a few mod's no problem. Battery mod, reboot menu, hide navbar, etc.. But Xposed can only do so much.
Edit: I heard on reddit this tool also works for rooting. I have not tested it (already rooted with the other method).
http://www.cydiaimpactor.com/
Getting Debugging to work.
I was not drunk when I made this post...I have the RCT6378W2 if you go to about tablet in your settings and repeatedly tap the build number...the deveolper options will appear...I fell out of my seat when i discovered this.
On a side note...if you repeatedly tap the android version...a cute picture of the android jellybean will appear. Try it.
rca 7" dual core tablet root
Takenover83 said:
Glad I could help a few. Now, someone get on a functional recovery ;p
I have poked around a little at the stock recovery, backing it up, etc.. But am not brave enough to try and get CWM working on it.
I was able to use th Xposed framework for a few mod's no problem. Battery mod, reboot menu, hide navbar, etc.. But Xposed can only do so much.
Edit: I heard on reddit this tool also works for rooting. I have not tested it (already rooted with the other method).
http://www.cydiaimpactor.com/
Click to expand...
Click to collapse
im not down with kingo, too risky! gonna try impactor. i will report back soon :fingers-crossed:
---------- Post added at 09:31 PM ---------- Previous post was at 09:15 PM ----------
1: Install drivers. Seeing as RCA does not provide drivers, we had to find some that work. That's where PDANET comes in. Their drivers support a very wide range of Android devices. We are not installing it to tether. We just want the drivers it provides. So download PDANET, install, let it detect your device, install the drivers, and then afterwords you can uninstall it.
2: Enable Developer Options. Settings>About tablet> Tap Build Number a bunch of times till it's enabled.
3: Enable USB Debugging. Options>Developer Options>Click On (up top)>Then checkmark USB Debugging
That should clear up some of the confusion in this thread. How you root after step 3 is up to you. Personally, I did it with Kango. Which was straight forward. Connect device, hit a button, Say yes to a couple questions, reboot, presto done.
cueballs said:
It is a hidden option that needs to be enabled. Follow this guide: www ninjaromeo com / enable-usb-debugging-developer-options-jelly-bean/
I just enabled this option on my Walmart BF 7" RCA RCT6378W2 tablet.
Sorry I had to mangle the link because XDA wont let me link external sources yet.
Click to expand...
Click to collapse
Thanks, that sorted things out.
To make clear, and aid in any other inquiries, I managed to find an ADP connection mode, among other android update features. with the device off, hold volume up while turning the device on. it should boot to an image of an android with an open chest panel and the words, "no command". if you push volume up again it will provide you with options and instructions on how to execute. you can manual update the device with an SDK through USB ADP mode this way. I'm not sure if that makes anything simpler or generates a work around but I hope it helps with future development for this device.
Well got root now we need a recovery...
For some reason when trying to make sure I can send adb commands to my tablet, I am showing no devices connected. I check in device manager and it shows up as Android ADB interface for the tablet. These drivers were installed with the latest version of PDANet. Thoughts or how were you all able to get the drivers fully loaded and working? I have developer options already enabled and USB debugging mode is checked.
Info: RCA RCT6378W2 Tablet
Android 4.2.2
Kernal 3.0.36+
PDANet+ 4.12
Windows 7 64 Bit (I also tried it on my windows 7 32 bit computer)
GloryFreak said:
For some reason when trying to make sure I can send adb commands to my tablet, I am showing no devices connected. I check in device manager and it shows up as Android ADB interface for the tablet. These drivers were installed with the latest version of PDANet. Thoughts or how were you all able to get the drivers fully loaded and working? I have developer options already enabled and USB debugging mode is checked.
Info: RCA RCT6378W2 Tablet
Android 4.2.2
Kernal 3.0.36+
PDANet+ 4.12
Windows 7 64 Bit (I also tried it on my windows 7 32 bit computer)
Click to expand...
Click to collapse
You need to create "adb_usb.ini" in "Users>Username>.android".
Inside "adb_usb.ini" insert "0x2207" and save.
Source: http://blog.fh-kaernten.at/wehr/?p=1182
I need some help rooting this tablet. The point is when im installing the pdanet drivers the screen hangs saying installing drivers.. i finally was able to get the driver installed. but then king root can not connect to it. i checked the device manage and the abd phone is installed. so im not sure what im doing wrong.
scooter29 said:
I need some help rooting this tablet. The point is when im installing the pdanet drivers the screen hangs saying installing drivers.. i finally was able to get the driver installed. but then king root can not connect to it. i checked the device manage and the abd phone is installed. so im not sure what im doing wrong.
Click to expand...
Click to collapse
I had this problem too. make sure you're using the most recent version of pdanet. for whatever reason the older version just hang there and dont work right.
Installed the latest pdanet. It wont install the driver. I checked the device manager and it still shows the device without the driver. not sure what else to try..
I recently got one of these, I imagine quite a few people did (sale this year on em), and could find no documentation on how to root it. Hopefully this hits google and will help all the other users out there! I did not make the software but gave it a go and it worked fine.
How to Root your Nextbook NX007HD
Google and download Cydia Impactor (First result on Google) Extract it (desktop, wherever you prefer)
Enable USB Debugging on your Tablet (Settings > Developer Options > USB debugging)
Plug up your Tablet via USB, do not turn usb storage on, let windows try (and most likely fail) at installing drivers.
Launch Impactor and select USB Driver Scan from the top menu (under USB). Let it do it's thing, reboot your PC after.
Verify your tablet/android device is showing up on the start-bar as being plugged up/in (bottom right area)(this may not be needed depending on your setup)
Relaunch Impactor (if rebooted ) and hit the Start Button
Let it do it's thing.
You should be rooted :victory: now go install SuperUser!
I should additionally note in my experience the SuperUser by ChaindsDD does not properly catch/work, but the one by CWM does.
Hope this helped everyone out who was slightly concerned when they couldn't find a root method someone else had tried/verified!
Thank You
I got the NX007HD cause it was on sale, before needing this one I head bought a tablet Craigslist and it WS already rooted.
I have never rooted before and tryed the one click root which didn't would and came across this and after spending all day trying to root it with or help it was done in under 10 mins I can't thank you enough.
P.S by any chance cukdu tell me how I could change the start up screen?
niftypixelz said:
I recently got one of these, I imagine quite a few people did (sale this year on em), and could find no documentation on how to root it. Hopefully this hits google and will help all the other users out there! I did not make the software but gave it a go and it worked fine.
How to Root your Nextbook NX007HD
Google and download Cydia Impactor (First result on Google) Extract it (desktop, wherever you prefer)
Enable USB Debugging on your Tablet (Settings > Developer Options > USB debugging)
Plug up your Tablet via USB, do not turn usb storage on, let windows try (and most likely fail) at installing drivers.
Launch Impactor and select USB Driver Scan from the top menu (under USB). Let it do it's thing, reboot your PC after.
Verify your tablet/android device is showing up on the start-bar as being plugged up/in (bottom right area)(this may not be needed depending on your setup)
Relaunch Impactor (if rebooted ) and hit the Start Button
Let it do it's thing.
You should be rooted :victory: now go install SuperUser!
I should additionally note in my experience the SuperUser by ChaindsDD does not properly catch/work, but the one by CWM does.
Hope this helped everyone out who was slightly concerned when they couldn't find a root method someone else had tried/verified!
Click to expand...
Click to collapse
WHERE usb driver
jlneely said:
P.S by any chance cukdu tell me how I could change the start up screen?
Click to expand...
Click to collapse
You unfortunately can only change one of the three images on boot animation (no idea why, have tried many diff ways!)
Check this out : http://forum.xda-developers.com/showthread.php?t=2334927
ming ming said:
WHERE usb driver
Click to expand...
Click to collapse
Be sure to hit > Usb > Driver Scan at the top of Impactor as noted in the instructions!
Glad this helped you, I've rooted a few other friends tables (same model) with no problems!
Upgrade
Do you know where I can find help to upgrade the firmware from 4.1.1 to any later version, or if this is even possible for this model?
I am trying to download Angry Birds for my daughter, but it says that its not compatible with this version firmware.
No upgrade needed!
dannybz said:
Do you know where I can find help to upgrade the firmware from 4.1.1 to any later version, or if this is even possible for this model?
I am trying to download Angry Birds for my daughter, but it says that its not compatible with this version firmware.
Click to expand...
Click to collapse
Hello dannybz,
Last weekend I was able to install many apps on my niece's tablets, (Angry Birds, Hay Day, Google earth, Ninja Fruit cut) :good:
After rooting the tablet with the great instructions you found here, you have to install an app called: "Market Helper" and follow the instructions...
codekiem.com/2013/02/13/market-helper/
Then you can install many apps you want...
Hope it can help you... It helped me a lot.
(I did this on 2 tablets with Android 4.1... the original version that comes with the tablet)
Can you provide a dump of original rom for this tablet?
Been trying to get a hold of it since forever.
"No such device" Error
Hi! I'm trying to use Cydia Impactor on my Nextbook NX007hd tablet but get error "No such Device" and sound like disconnecting from USB port.. can anybody help me please?
Nextbook model: next7100kld can be root?
thanks
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
ericdg said:
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
Click to expand...
Click to collapse
ADBSetup will get you the drivers you are looking for:
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Worked for any Android phone I tried.
Thanks, I'll give that a shot and see what happens!
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
ericdg said:
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
Click to expand...
Click to collapse
Easiest way to tell is open up a command prompt in the folder that adbsetup installed to (C:\ADB I think) and type:
Code:
adb devices
If all is well, then the device will be part of the listing.
Thanks Joel.............I think it worked.
The ADB command came back with:
List of devices attached
HT22_______7 device
That's not a number that I've ever seen associated with my phone, but I assume that's it.
Confirmed.................I was able to reboot the phone by ADB!
Excellent! This will also mean the fastboot commands needed to unlock your bootloader will work too.
.........one would think so, Joel, but I can't get fastboot to do anything. ADB recognizes the phone, and will reboot into bootlocker, but once there it'll do nothing. Windows pops up a message shortly after bootlocker opens that says something to the effect of "there was a problem with USB device not recognized". I tried the command "fastboot devices", but got nothing. I know that I'm darned close, and it's probably something simple, but just can't get it to work. Maybe I need additional drivers for fastboot, or need to move it to another directory?
Thanks,
~E
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
joel.maxuel said:
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
Click to expand...
Click to collapse
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
ericdg said:
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
Click to expand...
Click to collapse
Dont know where you got your HTC drivers, but you should try the ones in this post (step one - hopefully its still live - if not I can dropbox it for you):
http://forum.xda-developers.com/showthread.php?t=1801106
Sent from my LG-D520 using XDA Free mobile app
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
ericdg said:
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
Click to expand...
Click to collapse
Uh-oh. Either the link was dead when I went through this process back in April, or I had bad organizing skills at one point and didn't put the file in the Doubleshot folder before completing a purge. Either way, I don;t have the file.
Nor did I really need it. The second Doubleshot I rooted I ended up using it in my native Linux environment (no drivers needed), vs my Windows XP emulated through VirtualBox. That's what you could do. Get a live Debian DVD (Im like the XFCE desktop version), boot in, get fastboot:
Code:
sudo apt-get install fastboot
And then use fastboot:
Code:
sudo fastboot ...
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
ericdg said:
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
Click to expand...
Click to collapse
Just need the one. My recommended file to download is this:
http://cdimage.debian.org/debian-cd...ybrid/debian-live-7.6.0-i386-xfce-desktop.iso
Burn the image (not the file) onto a DVD (can be a rewritable) and reboot with the disc in the drive. Once it's fully loaded, you can either enter commands by clicking on the "terminal" icon on the bottom of the screen (preferred), or press Ctrl + Alt + F1 to get a prompt (may have to log in as "user", there shouldn't be a password). Hope this helps.
I've been trying to root my device, unfortunately I've received no help or feedback from this forum (I'm surprised as it was recommended in some tutorials I've read) but hoping someone might be able to help this time.
There is another thread which I've been trying to follow here:
http://forum.xda-developers.com/general/help/acer-iconia-one-8-b1-810-root-bloatware-t2991943
And it states to install usb drivers, alexys77 has posted a link for the drivers needed and I downloaded it but I don't know howto actually install them. I downloaded it from my tablet, I double click but nothing happens. I tried extracting it (by connecting it to my laptop) but I'm still unsure exactly what to do. Help!! Can anybody give me precise instructions on how to do this (including which part needs to be done on laptop/ tablet
Also, I'm still wondering if there Is a way to use a 1 click root for this? My exact model name is acer iconia one 8 b1-810_2cbw_316t. Is the above link the easiest method of rooting? Hope someone can help soon! Thanks again (to anyone who tries to help) :crying:
supashaka said:
I've been trying to root my device, unfortunately I've received no help or feedback from this forum (I'm surprised as it was recommended in some tutorials I've read) but hoping someone might be able to help this time.
There is another thread which I've been trying to follow here:
http://forum.xda-developers.com/general/help/acer-iconia-one-8-b1-810-root-bloatware-t2991943
And it states to install usb drivers, alexys77 has posted a link for the drivers needed and I downloaded it but I don't know howto actually install them. I downloaded it from my tablet, I double click but nothing happens. I tried extracting it (by connecting it to my laptop) but I'm still unsure exactly what to do. Help!! Can anybody give me precise instructions on how to do this (including which part needs to be done on laptop/ tablet
Also, I'm still wondering if there Is a way to use a 1 click root for this? My exact model name is acer iconia one 8 b1-810_2cbw_316t. Is the above link the easiest method of rooting? Hope someone can help soon! Thanks again (to anyone who tries to help) :crying:
Click to expand...
Click to collapse
You have to install usb drivers on your pc and keep the supersu.zip in your device. Then follow the procedure in the above thread!
Piyushlosalka said:
You have to install usb drivers on your pc and keep the supersu.zip in your device. Then follow the procedure in the above thread!
Click to expand...
Click to collapse
Thanks! I unzipped the folder which contains the drivers needed, but which file from there do I click to install? It contains the following folders:
ADB Interface (Interface 1)
Android-Phone
B1-810 (1)
Dispositivo USB MTP
Intel Android AD
I thought the B1-810 (1) would be the most likely choice, but none of the files in that folder seemed to install anything. Or is it simply enough to have the files unzipped on my laptop? lol I'm still confused as to why I need to install usb drivers when my tablet is recognised when I plug it into USB?? I would have thought it necessary if there was an obvious problem??
Which file is the install file??
Thanks I eventually rooted it, but using cydia impactor drive scan (the steps in the tutorial didn't quite work for me) Got there in the end but lol
Nice![emoji106]
supashaka said:
Thanks I eventually rooted it, but using cydia impactor drive scan (the steps in the tutorial didn't quite work for me) Got there in the end but lol
Click to expand...
Click to collapse
If you can, would you share what you did?
The mystery: I cannot establish a USB connection between my Pixel 7 Pro (Android 13) and PC (Windows 11). When I try, the PC makes that characteristic "connected device" sound, but Windows Explorer doesn't discover the Pixel, nothing shows up anywhere in the Windows Device Manager, and the ADB command
.\fastboot device
returns nothing. The Pixel is similarly not discoverable as a bluetooth device to the PC, although it IS to other devices (like my earbuds).
This is the first task I have attempted since I performed a factory reset (and walked through the automated Pixel setup process) last night. I have spent the last three and a half hours reading Android forums, testing USB port-cable permutations, and installing and uninstalling drivers. There is no obvious solution to this problem within the first ten pages of Google search results. I would be beyond grateful for any possible insight, but please, take a moment to review what I have attempted already before you expend any effort helping me troubleshoot.
The Pixel CAN connect to an older laptop running Windows 10, appearing both in the Windows Device Manager (which says my drivers are up to date) and in File Explorer (where I can access the internal memory). But ADB similarly returns nothing on the ADB
.\fastboot devices
command. Also, my old phone (a Samsung Galaxy S20 FE 5G running Android 13) connects fine--both by USB and by bluetooth--to all three devices.
So the PC (Windows 11) connects to the Galaxy and the laptop (Windows 10) connects to the Pixel (kinda), which fairly well eliminates the possibility of an issue related to my hardware or USB cables. But the PC (Windows 11) won't connect to the Pixel--not anymore. Everything worked just fine when I unlocked the Pixel's bootloader a few weeks ago.
What I need now is to recover the functionality of the USB and bluetooth connectivities between the Pixel and the PC running Windows 11, especially for file transfers. For several reasons, WiFi reliant solutions are untenable for my situation. I also need to re-lock the bootloader by any method (not necessarily with the PC). As mentioned above, ADB has not succeeded in finding the device on either platform.
Finally, in case it's relevant: when I open the Pixel's USB Preferences menu, I cannot switch from "USB controlled by...This device" to "USB controlled by...Connected device"--in both cases, the Pixel returns a "couldn't switch" dialogue. And yes, I have of course enabled USB debugging.
If you took the time to comb through all those particulars, Thank you. I'm getting desperate for some thoughtful expertise, and while I'm open to retrying anything for the fifth or sixth time, (maybe I somehow missed the magic driver package), it is a special kind of tribulation to review the same tired list of perfunctory solutions to a different problem. I promise, the solution I need isn't one of the usual suspects.
I spent $800 on this device. That's a lot of money for me. It feels absurd and unfair that such a basic functionality--one that far more affordable devices have been delivering reliability for decades--should be missing from the Pixel 7 Pro. Please please please help me!
Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.
jaseman said:
Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.
Click to expand...
Click to collapse
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..
GodieDan said:
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..
Click to expand...
Click to collapse
Have you tried putting in Fastboot mode and then connect to computer?
schmeggy929 said:
Have you tried putting in Fastboot mode and then connect to computer?
Click to expand...
Click to collapse
Putting what in fastboot mode?
GodieDan said:
Putting what in fastboot mode?
Click to expand...
Click to collapse
Your phone in Fastboot Mode aka bootloader Mode.
Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not
yurishouse said:
Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not
Click to expand...
Click to collapse
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?
Yeah, you probably just need to install the official USB driver from Google. That was a problem that numerous people had when the Pixel 7 series first released.
GodieDan said:
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?
Click to expand...
Click to collapse
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".
yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse
We'll I'm certainly not above learning new vocabulary but but in this case I don't think the issue is having read too little. Do you mean recovery mode? So far there is no custom recovery available for the Pixel 7 Pro, but yes I did try with the phone in the stock recovery
I have read every relevant article on XDA and three other forums and nothing has helped so far. I promise you I would not have posted if I could find the solution elsewhere.
Also the phone doesn't work fine on the windows 10 system. I was able to view my files but I couldn't read, write or execute ADB commands. I do consider USB file transfer to be a basic functionality, and windows 11 is backwards compatible with every storage device since punch cards.
Anyways I'm no pro, but I have had success with rooted devices in the past. For my benefit it would be helpful to be assiduous with language choice.
.
H
bobby janow said:
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".
Click to expand...
Click to collapse
I there, yes, my objectitve was to lock the bootloader, not unlock it. However I got that part figured out at least, by getting the phone replaced (i had fortunately splurged on the extra protection). But also I never bricked my device, and as best I can tell, the issue at hand isn't related to the rooting, or everything would be working again with the new phone. I wanted to re-lock the bootloader because everything was just getting to be so unstable. This was never a problem on my Nexus 6p, but that was two devices ago. Also, is it just me, or are there generally fewer benefits to rooting than there were in the teenies?
Hi there
simplepinoi177 said:
yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me
GodieDan said:
Hi there
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me
Click to expand...
Click to collapse
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
simplepinoi177 said:
...Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!
simplepinoi177 said:
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!
Click to expand...
Click to collapse
Wow, thank you for the speedy reply!
1. Having splurged on the protection plan, yesterday i went to best buy and replaced my device, and I'm no longer interested in messing with the bootloader. So where ADB is concerned, I don't need it. What i DO need is the functionality of making file transfers between my PC and my phone. Do you still suggest I look for the ADB driver on the developer website, or is there something more basic (and hopefully reliable)?
2. The device status reads:
"
The device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
"
I spent a few minutes googling around about those errors, no luck yet.
3. It would be straightforward to uninstall (or disable) the device, but when I do, I worry it will be difficult to locate where the drivers are hiding (to delete manually). Under the "Driver" tab I clicked "Driver Details" and found the directories for three files, winusb.sys and two .dll files. Are these the culprits? Might there be others anywhere?