Indirect please create a script that does this for us.
-XE
Is this for the Nook Tablet? That's what this forum is for.
Sent from my BNTV250 using Tapatalk
ckevinwelch said:
Is this for the Nook Tablet? That's what this forum is for.
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
Yup, changed the typo. I've been messing with the Touch for a few hours as well.
Not quite sure about "Recovery" Is this installing CWM or is it to recover BN software or what? My assumption is this is an automated CMW install, but it is not clear what it is.
hmm doesn't work for me. I always get the error cannot stat ' ./mods/ntrecoveryv2.img' Not such file or directory
Unable to chmod
Fail
Didnt work for me too! Changed the script to properly point at the .img file, still doesnt reboot into recovery! :-/
rjmohit said:
Didnt work for me too! Changed the script to properly point at the .img file, still doesnt reboot into recovery! :-/
Click to expand...
Click to collapse
Just tested it and fixed the directory error.
imo, change the title to include [CWM] and [Windows] since this script is for the former and only runs on the latter.
Just my 0b10 cents to keep it clear
Nuckin said:
imo, change the title to include [CWM] and [Windows] since this script is for the former and only runs on the latter.
Just my 0b10 cents to keep it clear
Click to expand...
Click to collapse
Thanks, I knew somebody would see the error and address it.
Nuckin said:
imo, change the title to include [CWM] and [Windows] since this script is for the former and only runs on the latter.
Just my 0b10 cents to keep it clear
Click to expand...
Click to collapse
Ok, all better..
working,
did not reboot in recovery but i did it manually
just need to test to make a backup
I might also suggest adding to your read me, to boot into recovery, turn off NT, hold nook button and power button simultaneously until the NT boots into CWM recovery.
Might clarify for the newbies that don't know.
Win7 64, Rooted via Zerg. Drivers setup correctly(or so i assume since i zerg'd and the script recognizes it), i run the .bat, says
Your Nook Tablet is successfully connected!
* daemon not running. starting it now*
* daemon started successfully *
protocol failure
* daemon not running. starting it now *
* daemon started successfully *
Unable to chmod /data/local/ntrecoveryv2.img: No such file or directory
/data/local/ntrecoverv2.img: cannot open for read: no such file or directory
...then the rebooting into recover msg..
it reboots to the exclamation symbol, says "please restart you device and try again. if yyou encounter the same issue, please contact customer service or visit...blah blah...then it shuts down
EDIT: Auto mount is disabled, when i connect the nook, in the device manager it shows "USB Mass Storage Device" in the driver list which I had to uninstall when I zerg'd,( it reinstalls when ever i reconnect the nook). When I uninstall mass storage, and run the script say device not found and can't find the build prop. So it will only see the nook when mass storage is running, and won't when its uninstalled.
When the .bat said it was rebooting into recovery, it just rebooted to desktop. I used quick boot and did the reboot to recovery. All is good. Thanks for the easy install.
You might try disabling automount USB. I know it is not mentioned, but I am pretty sure it is a requirement. That is at the bottom of the list where you checked usb debugging ect..
yes, you need to uncheck automount for the script to work. thats how i installed mine. I also use quickboot to go into recovery, much easier than holding buttons
---------- Post added at 06:52 PM ---------- Previous post was at 06:49 PM ----------
tep065 said:
Win7 64, Rooted via Zerg. Drivers setup correctly(or so i assume since i zerg'd and the script recognizes it), i run the .bat, says
Your Nook Tablet is successfully connected!
* daemon not running. starting it now*
* daemon started successfully *
protocol failure
* daemon not running. starting it now *
* daemon started successfully *
Unable to chmod /data/local/ntrecoveryv2.img: No such file or directory
/data/local/ntrecoverv2.img: cannot open for read: no such file or directory
...then the rebooting into recover msg..
it reboots to the exclamation symbol, says "please restart you device and try again. if yyou encounter the same issue, please contact customer service or visit...blah blah...then it shuts down
EDIT: Auto mount is disabled, when i connect the nook, in the device manager it shows "USB Mass Storage Device" in the driver list which I had to uninstall when I zerg'd,( it reinstalls when ever i reconnect the nook). When I uninstall mass storage, and run the script say device not found and can't find the build prop. So it will only see the nook when mass storage is running, and won't when its uninstalled.
Click to expand...
Click to collapse
Re download the file it was just updated
make sure you have both usb debugging checked (uncheck it and recheck it again) also make sure automount is unchecked as well.
plus make sure your adb drivers are set up correctly.
Both are checked, automount disabled (all done before i started this) drivers SHOULD be good, they are the ones i used to zerg and the script msg says it sees the nook (when USB Mass Storage is running). The nook drives do not mount.
Edit: Using the updated script, i even downloaded it a second time...still get the Protocol failure message and the reboot error, etc from my first post.
Factory resetting, gonna do this with a fresh install. See if I can narrow down the issue.
redownload again previous posts had similar issues. he updated the script
Know-Fear said:
I used quick boot and did the reboot to recovery.
Click to expand...
Click to collapse
I have never used quick boot, but gave it a try, works great. Thanks for the heads up.
tep065 said:
Both are checked, automount disabled (all done before i started this) drivers SHOULD be good, they are the ones i used to zerg and the script msg says it sees the nook (when USB Mass Storage is running). The nook drives do not mount.
Edit: Using the updated script, i even downloaded it a second time...still get the Protocol failure message and the reboot error, etc from my first post.
Factory resetting, gonna do this with a fresh install. See if I can narrow down the issue.
Click to expand...
Click to collapse
Was your ADB working before you tried the CWM flash? (I understand it worked when you rooted it, mine did too, but never worked again after that) If it was working fine, you will need to run the USBdeview or similar to remove any and all USB mass storage device, anything android related and probably anything related to a particular phone. I did this last night and ADB is now running perfectly. Also, make sure you install ADB hijack as well after rooting.
Post back after you restore and get re-rooted as to whether or not ADB is working correctly.
Related
So I just installed Ubuntu 10.10 on my PC and I'm really digging it. But when I try to mount my sdcard from the phone, it doesn't show up under my places menu. I'm running GSB 1.8.1. I don't have a problem mounting it under windows XP, and also have no problem using the wired tether function. Is there anything I can change on the phone or in Ubuntu to fix this?
I am running Ubuntu 10.04 LTS - inside a Virtual Machine - and I can mount the drive from inside the VM. (Believe me, that's even trickier than what you are trying).
But, 10.10 might have had some changes, and I wouldn't be surprised if your result depended on which desktop you are running; so maybe you need to mount the thing manually.
Try this:
With the phone unplugged, type
$ sudo /bin/bash
# tail -f /var/log/messages
This will continue to show you various kernel messages as they appear. Next, plug in the phone.
Hopefully, you will see some lines scroll by that mention USB.
Next, mount the SD to the PC from the phone. If all goes well, you should now see some mention of "SCSI" devices /dev/sdX, where X is probably "a", "b" "c" "d". Probably you will also see mention of the first partition on the device, such as "/dev/sdb1". Make a note of this drive device name.
Cancel the "tail" command (Ctrl-C) and do a
# mount | grep sdb1
( note device name "sdb1" ; use whatever you saw previously )
This will show you if the device is already mounted somewhere.
If the device has not been mounted, you can manually mount it, as in:
# mkdir -p /mnt/Eris_SD
# mount -o rw /dev/sdb1 /mnt/Eris_SD
( Again, note device name "sdb1" - use whatever you saw previously. If it doesn't recognize the file system, use "mount -o rw -t vfat /dev/sdb1 /mnt/Eris_SD" )
Hopefully that will do it. Don't forget to "umount /mnt/Eris_SD" when you are done.
If the device never shows up in the /var/log/messages file, then you have some other problems.
If you don't see anything in the log file indicating USB activity, well - you ought to investigate what is going on at the USB port.
Right now my phone is booted into Amon_RA; if I issue the "lsusb" command, I see:
Code:
Bus 001 Device 031: ID 0bb4:0c98 High Tech Computer Corp.
BTW, on my VM, it seems like I need to unplug the USB cable after I dismount the drive, or the next time I export the SD card to the PC, the kernel recognizes it, but the automounter doesn't automatically mount it.
Another thing that you might try to make things more automatic is the instructions in "Step #5" of this XDA post. This is meant for allowing an unprivileged user on your Ubuntu box to use ADB or fastboot without needing to "sudo" to root. I did this on my VM - I don't think that's the reason that the phone automounts into the SD drive, but perhaps it is related - the same "Vendor_ID" is in use when the phone is in "Composite ADB mode".
When you get to the part in these instructions about restarting the "udev" subsystem, unplug your USB cable first - and then see what you get when you plug it in and fire up the SD export from the phone.
hope that helps.
bftb0 said:
BTW, on my VM, it seems like I need to unplug the USB cable after I dismount the drive, or the next time I export the SD card to the PC, the kernel recognizes it, but the automounter doesn't automatically mount it.
Click to expand...
Click to collapse
I noticed this on my desktop with a full install of Ubuntu. I knew it was connected because the charge led was lit, but I would have to unplug the usb and plug it back in almost every time just to get it to mount or connect to the internet with wired tether. I never messed with it BUT it did seem to fix itself once I started doing the system updates on Ubuntu.
bftb0 said:
$ sudo /bin/bash
# tail -f /var/log/messages
This will continue to show you various kernel messages as they appear. Next, plug in the phone.
Hopefully, you will see some lines scroll by that mention USB.
Next, mount the SD to the PC from the phone. If all goes well, you should now see some mention of "SCSI" devices /dev/sdX, where X is probably "a", "b" "c" "d". Probably you will also see mention of the first partition on the device, such as "/dev/sdb1". Make a note of this drive device name.
Click to expand...
Click to collapse
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
prsguitaruser said:
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
In case this helps, GSB mounts the SD card through USB just fine with Windows. Don't take my comment as a Windows versus Ubuntu, thing, however. Just for whatever it's worth.
prsguitaruser said:
I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
Glad to here you got this fixed
prsguitaruser said:
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
Great news! I don't know how I missed your edit since I quoted it in my last response. I must've had this thread open in my browser from before, and went to respond to it after your edit.
OK, so I went back to GSB and had the problem again. I found out that ADB works and the sdcard mounts until I turn on wired tether, then if I turn wired tethering off, my sdcard still won't mount, nor will ADB recognize my phone, until I reboot the phone. Every time I've tried to mount the sdcard, I've made sure to turn tethering off. But it seems like tethering is what kills it.
prsguitaruser said:
OK, so I went back to GSB and had the problem again. I found out that ADB works and the sdcard mounts until I turn on wired tether, then if I turn wired tethering off, my sdcard still won't mount, nor will ADB recognize my phone, until I reboot the phone. Every time I've tried to mount the sdcard, I've made sure to turn tethering off. But it seems like tethering is what kills it.
Click to expand...
Click to collapse
Are you using the tethering abilities built into CM7 (for wired you have to use the Tether Widget from the market, but that's it), or are you using the "for root" apps? IMHO, the "for root" apps are redundant and don't work as well as the native tethering in CM6 and CM7.
roirraW "edor" ehT said:
IMHO, the "for root" apps are redundant and don't work as well as the native tethering in CM6 and CM7.
Click to expand...
Click to collapse
Really? Because I have never been able to get "native" tethering to work. They appear to be working but there not allowing data to pass through.
Also I only use the ones posted on Google's source page.
I believe there may be an issue here that isn't faulted by the phone or the tethering apps. I think it has something to do with the way Ubuntu reacts to the change between allowing data inbound and when it goes back to remounting the phone and its SD card. Honestly if you can I would say allow your Ubuntu to do its system updates then see what happens.
@ roirraW "edor" ehT, no harm intended at the top of my post. Just my personal observation of how these things generally work out for me. Heh.
Powered by: GSB CM7
wildstang83 said:
Really? Because I have never been able to get "native" tethering to work. They appear to be working but there not allowing data to pass through.
Also I only use the ones posted on Google's source page.
I believe there may be an issue here that isn't faulted by the phone or the tethering apps. I think it has something to do with the way Ubuntu reacts to the change between allowing data inbound and when it goes back to remounting the phone and its SD card. Honestly if you can I would say allow your Ubuntu to do its system updates then see what happens.
@ roirraW "edor" ehT, no harm intended at the top of my post. Just my personal observation of how these things generally work out for me. Heh.
Powered by: GSB CM7
Click to expand...
Click to collapse
Just curious, did you have the opportunity to try the native tethering under Froyo/CM6 as well, or did you only try it under CM7? I haven't needed the tethering since before I started to try CM7, so I actually don't know from personal experience if Cyanogen has made the tethering work correctly under it yet. I didn't have any trouble with it under CM6, besides the usual occasional semi-random tethering failures.
My ubuntu 10.10 install handles native tethering just fine. However, that stupid bug where the Eris loses data connection randomly. while natively tethered kicks in.
The only solution I've found is to use AziLink (seems to solve the random disconnect as well as pdanet does.)
Sent from my Eris using XDA App
adaneshade said:
My ubuntu 10.10 install handles native tethering just fine. However, that stupid bug where the Eris loses data connection randomly. while natively tethered kicks in.
The only solution I've found is to use AziLink (seems to solve the random disconnect as well as pdanet does.)
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Thanks, I'll keep them both in mind. I tried PDANet a long time ago and it didn't keep the tethering from failing, but maybe they improved it.
my lappie which is a
Windows Vista 32 bit
it is not detecting the APX mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=861950
Now I am fixed in a reboot loop and I have tried everything suggested in this thread
OK I know I had no business doing this because I dont know the D of developing....
but the TNT Lite worked so well and was so easy to install I got carried away by it and tried to install the amd to let my computer detect the gtab. this is where I got stuck!!
to start from the beginning
I installed TNT lite on my GTab and it worked really well, I could see Youtube videos and access the Android market
Then I thought I should maybe transfer a few files to the Gtab so I could view them, but when I tried to do that I found out it was another long process, Normally being a non developer I would have probably just tried to find out a non hacking method to do this like download it from gmail or something. Or just use an SD card
But it had been so easy to install the alternate ROM from instructions in this forum I thought maybe it wouldnt be a big issue..sad!!
It was!
Now my one day old GTab wont start up and if it does it just keeps displaying a weird kind of screen with squares on it which I am assuming is the reboot screen
And so I tried to use Nvflash to restore it like mentioned in the thread above but my lappie wont detect it at all..
So now I really need help before I attempt anything else on my own
I dont want to send my Tablet back and would appreciate any help from experienced developers like you guys...!
Please do help me and I promise never to attempt something like this again..!!
Thanks
please !!!! anyone!!!!!
First, I think you need to breathe. Patience is a virtue. *NOTHING* about being excited will help. So calm down first, then go.
Did you install the drivers listed on that page?
Here's a direct link:
http://www.myadventvega.co.uk/SystemUSB.zip
Getting them to install can be a bit tricky, though, since it's not an executable. Download it, unzip it, go into the Flash USB folder, go into the USB folder, right click on the nvidiausb.inf file, and select install. That *should* install the driver. However, it might not. If it doesn't, post back and say what happened.
And as far as transferring files - there's no need to hack to do that. Just connect via USB, pull down the USB attachment notification on your tablet, and say connect. Then drag and drop on the computer. Done.
tedlogan42 said:
First, I think you need to breathe. Patience is a virtue. *NOTHING* about being excited will help. So calm down first, then go.
Did you install the drivers listed on that page?
Getting them to install can be a bit tricky, though, since it's not an executable. Download it, unzip it, go into the Flash USB folder, go into the USB folder, right click on the nvidiausb.inf file, and select install. That *should* install the driver. However, it might not. If it doesn't, post back and say what happened.
Done.
Click to expand...
Click to collapse
Thanks, I think I did forget to breathe..
It says " the inf file you selected does not support this method of install"
Alright. Crap. I forgot that happened to me too when I had to do it.
I think I had to install it via using Device Manager. Here's how you can get to it in Vista (I'm about to sleep, so I'm saving typing time):
http://windows.microsoft.com/en-US/windows-vista/Open-Device-Manager
Once you've got that open, go ahead and boot the tablet into APX mode, meaning that from a powered-off state, you'll hold down the power and volume - buttons simultaneously until your G-Tab comes up and the goes back to a black screen (words stolen from the original NVflash post).
Connect it to your computer (while Device Manager is opened). When you connect it, you should see a new device appear that is labeled Unknown Device. Right click on it, and select Properties. Click the Driver tab (may be different - I'm on 7, but I think it's the same). Click the Update Driver button. Choose the "browse my computer for driver software." Using the browse function, point it to the folder with the inf in it (%wherever_you_extracted_it%\System USB\Flash USB\USB). Click Next.
I think that's what I had to do on mine when I borked my tablet with an experimental build of Vegan Ginger. If the driver installs, that should allow you to then go on with the rest of the directions. If it doesn't, post more information. I can't promise I'll be on any time soon, but maybe someone else can help out if they're up.
ok it says at the end when I have pointed it at the driver file (NVidiaUsb.inf)
"The folder you specified doesnt contain a compatible software driver for your device. If the folder contains a driver make sure that it is designed to work with windows for 32 bit systems."
This is what happened last time also, and then the system says that I already have the most compatible driver for the system and puts me on "Microsoft WPD filesystem volume driver"
EDIT: I should mention that I also had a tough time deleting my NVidia driver, but as soon as it was deleted, it was automatically replaced by the "Microsoft WPD filesystem volume driver"
Not sure what to tell you. The INF clearly points to the x86 version, so it should install. Is there more than one unknown device in your device manager? If so, you might somehow have the wrong one, though the approach earlier should have made it easier to track the new one.
Sorry. You might want to try getting on IRC to see if other people have some bright ideas. An NVFlash does seem like what you need to do, though.
EDIT: I did some digging into the forums (you should probably continue that). Here's a thread all about these drivers.
http://forum.xda-developers.com/showthread.php?t=1012009&highlight=NVFlash+USB+Driver+Solution
If those fail, there's another method that involves installing the entire SDK, which is linked on this thread (the second post about the MSI):
http://forum.xda-developers.com/showthread.php?t=882814
However, my impression is that that option might create more complexity than it's worth.
I haven't done anything but what I explained earlier (if I remember right - it's been a while), so I can't talk about any other approach. However, these will at least maybe make my failure into less of a dead end.
I ran into the exact same problem a few weeks ago after installing CM7...
http://forum.xda-developers.com/showthread.php?t=902860&highlight=usbdeview
I used a program called USBDEVIEW and just obliterated all the usb drivers (I guess the safe way is to remove any mention of Nvidia usb devices) and rebooted the computer. Let the system reinstall all the USB devices. Restarted the computer again. AND ONLY THEN did I plug in the gTablet. Once plugged in, the system automatically installed drivers and recognized the tablet, you may have to point to the inf file if it fails to install automatically.
USBDeview from CNet
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
Good luck!
Don't let this setback keep you from using great ROMS like VEGAn Tab Gingerbread RC1... once you've mastered the NVFlash process and CWM recovery install (I prefer the external CWM install) you are all set for other mishaps.
http://forum.xda-developers.com/showthread.php?t=865245
supergroverthm said:
I ran into the exact same problem a few weeks ago after installing CM7...
http://forum.xda-developers.com/showthread.php?t=902860&highlight=usbdeview
I used a program called USBDEVIEW and just obliterated all the usb drivers (I guess the safe way is to remove any mention of Nvidia usb devices) and rebooted the computer. Let the system reinstall all the USB devices. Restarted the computer again. AND ONLY THEN did I plug in the gTablet. Once plugged in, the system automatically installed drivers and recognized the tablet, you may have to point to the inf file if it fails to install automatically.
USBDeview from CNet
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
Good luck!
Click to expand...
Click to collapse
I tried to uninstall the nvidia drivers using USB deview, it asked me if I wanted to uninstall drivers I said yes but I can still see the drivers in the USB list
Is that ok?
You need to run USBDeview as an administrator. Right click on "USBDeview.exe" select "run as administrator" and then when you are asked to confirm, click "yes"
Only then when you "uninstall selected device" the device will disappear. Otherwise you are only in view mode.
supergroverthm said:
You need to run USBDeview as an administrator. Right click on "USBDeview.exe" select "run as administrator" and then when you are asked to confirm, click "yes"
Only then when you "uninstall selected device" the device will disappear. Otherwise you are only in view mode.
Click to expand...
Click to collapse
OK I just figured that out and was coming to post that. Thanks for realising that is what I was doing..
I conneccted the tablet to my PC.but it still does not detect it
The only time my PC detected it was the first time when I pointed it to the nvflash folder. After that it has never detected it and I havent seen the yellow ! icon.
what am I doing wrong?
Firstly, powerdown the gTab.
Turn on power while holding "vol -" to enter into APX mode (you'll see the viewsonic birds then the screen will go blank)
On the bottom right corner of the Vista screen, click on the USB icon that says "safely remove hardware and eject media"
Look at the list the pops up, does one of the devices say APX?
no It only says safely remove mass storage device
oh wait
my tablet switched on to the reboot screen and didnt stay black
trying it again
it installed "NVIDIA boot recovery driver for mobile devices", is that correct?
This is where I get stuck, my device manager doesnt show the apx at all whatever I do, what am I doing wrong?
I think there was a way to overlook safety signatures somewhere but I couldnt get to do it,
Is there some way I can ask my computer to overlook the safety signatures?
EXCELLENT!!! Now you are ready for NVFlash instructions:
http://forum.xda-developers.com/showthread.php?t=861950
BTW, you will not be able to see the device under windows explorer as in the normal way such as "D:" "E:" etc drive.
Once you get everything setup per the above instructions and run "nvflash_gtablet.bat" you will see the flashing process in the text box.
Just want to make sure...
Under Vista Device Manager
-- "universal serial bus controllers" you have "NVIDIA USB Boot-recovery driver for Mobile devices"
supergroverthm said:
Just want to make sure...
Under Vista Device Manager
-- "universal serial bus controllers" you have "NVIDIA USB Boot-recovery driver for Mobile devices"
Click to expand...
Click to collapse
Yes I do, so I should start the process now?
THANKS a lot, will update you as it goes on.
Yes, follow Roebeet's instructions and you should be set. Also play it safe and keep your gTab plugged in unless you are sure of the amount of battery life left.
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Good write up!
The procedure worked fine on my laptop. When I did it on on my home PC I forgot to disable auto-mount and the Nook installed itself as mass storage. I was able to right click -> un-install all the USB Mass Storage entries (with the Nook unplugged), disable auto-mount, plug the Nook back in, and have it show up correctly.
In short, I did not need to use "USBDeView" as I was able to remove the diveres manually. I suppose if you have more than a handful for USB devices (I just have a Mouse, Keyboard, and printer) "USBDeView" might be helpful to determine which drivers to un-install...
The device manager is enough for most people, but there is a somewhat large number of us that are having trouble still. Possibly because of other devices we have installed before. (I dont understand how all the drivers work and I wont pretend to)
Some people have go so far as putting a fresh install on Windows on a partition of a PC.
I had this problem with both my laptop and my desktop, which surprised me. This worked on both the laptop and PC, so hopefully it can help other people.
I cant wait to get my own tablet on the 12, I will take lot of pictures and make this process more user friendly.
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
mtelesha said:
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
Click to expand...
Click to collapse
Did you sort by last time plugged in and delete all of those too? Have you re-checked and then re-un-checked automount/usb debugging and such?
This is interesting, you'll have to come back and let me know if you ever get it working on your PC. Maybe its a good excuse for a nice healthy re-format and reinstall of windows?
l3ft3r1s said:
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
Click to expand...
Click to collapse
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
The_Joe said:
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
Click to expand...
Click to collapse
Yeap, that did the trick, thanks. Drives installed successfully this time, but adb devices still returns nothing.
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
adb error: device offline
This drove me nuts for at least a day. Turns out it is what happens when you are plugged into a USB 3.0 port on your PC side. Find out which USB is 2.0 (Front Panel for ZT Systems), use it and life suddenly gets really good.
The_Joe said:
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
Click to expand...
Click to collapse
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
l3ft3r1s said:
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
Click to expand...
Click to collapse
The problem is sdk uninstall and use ccleaner to clean your PC and registries. Use the drivers provided in this forum
Sent from XDA using one of my Android Toys
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
LadyPenley said:
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Click to expand...
Click to collapse
In the future don't delete your original, just post an edit with the fix. That way when someone else has a similar problem your post can help.
Sent from my BNTV250 using xda premium
mtelesha said:
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
Click to expand...
Click to collapse
Did you find a solution? Thats a problem I sadly dont know how to help with. I would start with:
-Check USBDeview and delete anything android/Nook/usb related. Delete just about everything.
-Restart the device
-Uncheck and recheck the USB Debugging boxes
-Recheck and uncheck the auto-mount box
-Test
-Try a different USB Port
-Try another PC
Thanks but didn't work.
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
The_Joe said:
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Click to expand...
Click to collapse
whitets said:
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
Click to expand...
Click to collapse
I had literally this exact same problem the 6th time I restored and flashed. IF im right, you just need to uncheck then recheck usb debugging.
Let me know if it works!
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Added English version manual on Lenovo-Forums.ru
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
Do this root apply to the s8-50F ?
EDIT: This method indeed does work on the S8-50F variant. Was having problems with device staying in adb while running program, but a reboot of pc fixed that and gained root effortlessly. THanks!
Glad It Helped !!!
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
The download isn't working for me. It's not downloading as a zip? Any suggestions?
If youre using windows, download a program called 7-zip and downoad the file. right click the root software and click extract here. or open with 7-zip. You could also use winrar. The format of the file is in .7z right ? that means search up http://www.7-zip.org/
Any idea how to unroot?
Not sure. Have you tried the full unroot method in the su app?
__McB__ said:
Any idea how to unroot?
Click to expand...
Click to collapse
SuperSU.apk.....in the setting, unroot, cleanup...
icanttinkofaname said:
Not sure. Have you tried the full unroot method in the su app?
Click to expand...
Click to collapse
jazzespresso said:
SuperSU.apk.....in the setting, unroot, cleanup...
Click to expand...
Click to collapse
Thanks both of you. I ended up returning it, root and all, but I'm sure your suggestion would have worked.
After rooting, has there been anything anybody's been able to do about battery life? I don't imagine there's been any Roms built for this device yet, but didn't know if maybe someone's figured out something that's helped extend their battery life, because when playing certain games like clash of clans for instance, I'm lucky to get an hour and a half of game play, and that's with my brightness turned all the way down. Any suggestions would be greatly appreciated. Thanks
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
This root guide works on s8-50f! thanks Xakep
This is a very easy and usefull root instruction, i rooted my tab s8-50f with no problems.
I followed the steps described and got instant root without any issues.
My machin is windows pc with windows 8.1 pro 32bit. Plug your tab and windows recognized the drivers just make sure your device mngr shows lenovo s850 and you are all set. Then just run the flash tool and it will run in less than a minute your tablet will reboot and your tab will be rooted.
Yes this is probably the easiest I've ever rooted any device in the past. If at first it doesn't take, don't worry it will. Just repeat the process till it does. Thanks Hash.h for putting up this thread and passing along the info
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
Where can I download the ADB drivers for S8-50 from?
I think drivers come with tablet. Try to connect the tablet and it will show CD drive on which is the driver.
error: device offline?
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Worked great. Thank you.
Awesome little tablet.
Jirbo said:
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Tried on another computer and succeeded.
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
moogthedog said:
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
Click to expand...
Click to collapse
Same problem here. Lost root after the last update and now I can't get either root method to work.
**New** Root Access is Now Required!
Download:
- G900T_OF6_Batch_Debloater_&_App_Freezer
Instructions:
1. Extract the G900T_OF6_Batch_DeBloater & App Freezer folder onto your desktop.
2. Turn on USB Debugging from Developer Options and connect your device to your *PC.
3. Double-click DeBloater.bat to launch the program.
4. Select "Light," "Medium," "Extreme", or "Freeze Apps"**and press "Enter."
5. Grant Root Access if prompted by your device and press "Enter" to begin.
6. Once complete press "Enter" to return to the Main Menu and select ***"Reboot Device."
7. Last, select "Exit" from the Main Menu to end your session. Done!
* Make certain that you have Samsung Drivers installed.
** Use notepad++ or other text editor to view/edit the lists of affected apps in the debloater.bat file.
*** It is normal for apps to begin force closing prior to rebooting your device.
muniz_ri said:
Download:
- G900T_OF6_Batch_DeBloater
Instructions:
1. Extract the G900T_OF6_Batch_DeBloater folder onto your desktop.
2. Boot into *TWRP, Press "Mount" and make certain that "system" is checked.
3. Connect your phone to your **PC while still in TWRP and double click on the DeBloater.bat file.
4. Select "Light," "Medium," or "Extreme" debloating (see DeBloater.bat file for list of removed apps).
*I used TWRP 2.8.6.0 (could not get TWRP 2.8.7.0 to connect to PC).
** Make certain that you have Samsung Drivers installed.
Click to expand...
Click to collapse
The Tmobile my account app shows up in my installed apps but no where to be found in system/app or priv_app any ideas ?
Sent from my SM-G900T using XDA Free mobile app
dzhowandai said:
The Tmobile my account app shows up in my installed apps but no where to be found in system/app or priv_app any ideas ?
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Its likely under a different name. I used the extreme option and its no longer installed.
It's a no go fir me with same result. Is your rom deodexed or does it make any difference?
Sent from my SM-G900T using XDA Free mobile app
dzhowandai said:
It's a no go fir me with same result. Is your rom deodexed or does it make any difference?
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Not deodexed.
Not working for me either:
I just get:
" rm: can't remove '/system/app/xxxx': No such file or directory"
poncespr said:
Not working for me either:
I just get:
" rm: can't remove '/system/app/xxxx': No such file or directory"
Click to expand...
Click to collapse
To clarify does the PC recognize the device while in twrp and the tool runs successfully? But you get one or a few of the above error msg's or an extensive list of apps that it cannot remove? Are you on a completely stock rom that is not already debloated?
muniz_ri said:
To clarify does the PC recognize the device while in twrp and the tool runs successfully? But you get one or a few of the above error msg's or an extensive list of apps that it cannot remove? Are you on a completely stock rom that is not already debloated?
Click to expand...
Click to collapse
I went to far as to reinstall samsung drivers, google drivers.
I can check adb devices and see it is there.
Also, this is without any modification to your batch file.
poncespr said:
I went to far as to reinstall samsung drivers, google drivers.
I can check adb devices and see it is there.
Also, this is without any modification to your batch file.
Click to expand...
Click to collapse
Did the tool delete any apps? The extreme option includes over 90 apps. How many "could not find" msgs did you see? Also, which twrp version did you use?
muniz_ri said:
Did the tool delete any apps? The extreme option includes over 90 apps. How many "could not find" msgs did you see? Also, which twrp version did you use?
Click to expand...
Click to collapse
I chose extreme debloat and could not see any app succesfully removed.
I ended up using a debloater for the G900F via recovery, but it does not remove the Tmo bloat.
Anyway, I thank you for sharing your work.
poncespr said:
I chose extreme debloat and could not see any app succesfully removed.
I ended up using a debloater for the G900F via recovery, but it does not remove the Tmo bloat.
Anyway, I thank you for sharing your work.
Click to expand...
Click to collapse
The tool will not show successfully removed apps only failed apps.
Glad you found another method. I am just trying to understand why it works for me but not for you and another user so that I can either modify the tool or provide additional instructions.
muniz_ri said:
The tool will not show successfully removed apps only failed apps.
Glad you found another method. I am just trying to understand why it works for me but not for you and another user so that I can either modify the tool or provide additional instructions.
Click to expand...
Click to collapse
I tried quite a few times. Installed TWRP 2.8.6.0.. I re-downloaded drivers. I did a system restore on my windows 7 64 PC to make sure no other programs were conflicting.
Might give it a try again later on. I really want to get rid of Tmobiles useless app.
Edit:
Reinstalled drivers once more, used a different USB port, and selected minimal debloating (since I already removed most of the stuff I did not want)
and it finally worked. No more Tmobile branded bloat on my GS5.
Thank you again.
poncespr said:
I tried quite a few times. Installed TWRP 2.8.6.0.. I re-downloaded drivers. I did a system restore on my windows 7 64 PC to make sure no other programs were conflicting.
Might give it a try again later on. I really want to get rid of Tmobiles useless app.
Edit:
Reinstalled drivers once more, used a different USB port, and selected minimal debloating (since I already removed most of the stuff I did not want)
and it finally worked. No more Tmobile branded bloat on my GS5.
Thank you again.
Click to expand...
Click to collapse
I suspected that was the case so I have modified the tool to not run unless the device is recognized by the PC.
I can use "adb devices" to get adb to recognize my device when it's booted normally and usb debugging is checked (also checked always allow authorization), but when it booted to TWRP 2.8.6.0 and Mount system adb cannot recognize it ("adb devices" returns empty list) and thus the script cannot run (stops at the "waiting for device" part) . Any help?
Im having an issue with MTP not installing on Windows 7, tried many fixes and nothing is working. Really want to use this thing! Has anyone had this issue and know a possible fix?
Master619 said:
I can use "adb devices" to get adb to recognize my device when it's booted normally and usb debugging is checked (also checked always allow authorization), but when it booted to TWRP 2.8.6.0 and Mount system adb cannot recognize it ("adb devices" returns empty list) and thus the script cannot run (stops at the "waiting for device" part) . Any help?
Click to expand...
Click to collapse
Only thing that comes to mind are samsung drivers, try install or reinstall.
Edit: played around with it....connect your phone while in recovery to your PC and run Windows Update. It should give you the option of installing Android ADB Driver.
MortTheBeast said:
Im having an issue with MTP not installing on Windows 7, tried many fixes and nothing is working. Really want to use this thing! Has anyone had this issue and know a possible fix?
Click to expand...
Click to collapse
What I did is I disabled MTP in TWRP.
You disabled in TWRP and windows installed MTP? Because I tried that and windows won't even attempt to install MTP and phone doesn't get recognized.
MortTheBeast said:
You disabled in TWRP and windows installed MTP? Because I tried that and windows won't even attempt to install MTP and phone doesn't get recognized.
Click to expand...
Click to collapse
I tried Samsung drivers first, then used Google drivers. Still after a coulple of seconds I would always get an error 10 saying "This device could not start".
Tried downloading MTP drivers from microsoft somewhere, and that did not work either so finally decided to disable MTP on TWRP.
But, the ABD device was still recognized after disabling ATP.
poncespr said:
I tried Samsung drivers first, then used Google drivers. Still after a coulple of seconds I would always get an error 10 saying "This device could not start".
Tried downloading MTP drivers from microsoft somewhere, and that did not work either so finally decided to disable MTP on TWRP.
But, the ABD device was still recognized after disabling ATP.
Click to expand...
Click to collapse
I got nothing... here's crossing my fingers that someone is working on a root method, or else I will have to dump 5.1.1 and go with 5.0. :good: