downgraded NEW tab to 1.4.0 but can't root in Windows 7 64-bit - Barnes & Noble Nook Tablet

I got a new Nook Tablet and it came with 1.4.1 installed, so I downloaded the acclaim_update.zip and put it on a microSD card and successfully downgraded to 1.4.0 but had to do a factory reset and opted out of the "out of box experience".
The problem seems to be that I have a Windows 7 64 bit system and this prevents me from "upgrading" the drivers on my system so that I can root the tablet.
Would it be easier to use the script for rooting the tablet using a Linux system?
I am going to see if I can find that script online in case that is the only way to go.
I do not have a 32 bit Windows system.
thanks

I have Windows 7 x64 bits and i had no problems at all even having my LG GT 540 drivers installed, i have windows update disabled "never check for updates" and before install the drivers u need to run the runmefirst.bat if you are having conflict with drivers there is a step by step guide try that and report back. Also do not run as administrator the .bat scripts. In my FAQ (link in my signature) there are other links to troubleshoot drivers if needed.
~ Veronica

I can't offer you much help, but I rooted my NT (1.4.0 out of the box) twice on two different machines running Win7 x64 without issue...
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
lavero.burgos said:
I have Windows 7 x64 bits and i had no problems at all even having my LG GT 540 drivers installed, i have windows update disabled "never check for updates" and before install the drivers u need to run the runmefirst.bat if you are having conflict with drivers there is a step by step guide try that and report back. Also do not run as administrator the .bat scripts.
~ Veronica
Click to expand...
Click to collapse
Note also that I had two "runmedirst.bat" files - one packed with the drivers and one with zergrush. The first time I tried I used the wrong one and couldn't root. I *think* you want the one that was packed with zergrush.

lavero.burgos said:
I have Windows 7 x64 bits and i had no problems at all even having my LG GT 540 drivers installed, i have windows update disabled "never check for updates" and before install the drivers u need to run the runmefirst.bat if you are having conflict with drivers there is a step by step guide try that and report back. Also do not run as administrator the .bat scripts. In my FAQ (link in my signature) there are other links to troubleshoot drivers if needed.
~ Veronica
Click to expand...
Click to collapse
Thanks for the reply. The problem is that the moment I connect to wifi on the NT, it will be upgraded to 1.4.1, right? Can I download the TGPS_Launcher.apk on a pc and copy the file to MicroSD card and install from there? I am unable to install apk's at the moment since no installer is on the NT and I think I can only install from Market. I don't know how to get around this problem.

LordGibson said:
Note also that I had two "runmedirst.bat" files - one packed with the drivers and one with zergrush. The first time I tried I used the wrong one and couldn't root. I *think* you want the one that was packed with zergrush.
Click to expand...
Click to collapse
Thanks for this tip. I will look for the second script. It is likely I used the wrong one. If I do not see it, I will look for a separate Zergrush. I know I have one file or directory by that name with the drivers I downloaded.

spottedtadpole said:
Thanks for the reply. The problem is that the moment I connect to wifi on the NT, it will be upgraded to 1.4.1, right? Can I download the TGPS_Launcher.apk on a pc and copy the file to MicroSD card and install from there? I am unable to install apk's at the moment since no installer is on the NT and I think I can only install from Market. I don't know how to get around this problem.
Click to expand...
Click to collapse
You must install the drivers in order to root. LordGibson is right use the runmefirst.bat from Nook&Zergy.zip i too had issues with the runmefirst.bat from the drivers.zip

lavero.burgos said:
I have Windows 7 x64 bits and i had no problems at all even having my LG GT 540 drivers installed, i have windows update disabled "never check for updates" and before install the drivers u need to run the runmefirst.bat if you are having conflict with drivers there is a step by step guide try that and report back. Also do not run as administrator the .bat scripts. In my FAQ (link in my signature) there are other links to troubleshoot drivers if needed.
~ Veronica
Click to expand...
Click to collapse
I downloaded the other Zergy and drivers files and had the same problems. I think the problem is the Windows 7 system and I could not get the "new" drivers to install. I will check your FAQ and if that does not work, I will try to get it rooted via Linux, but that approach seems not so easy.
Also, do I need to make a new Google account in order to download an app to the tablet? I tried it and it just sends the app to my phone.
thanks

Windows 7 64-bit here as well. The drivers are a pain but keep trying with usbdeviewer helping you and you will get it.
Also I have rooted three times and each time I had the tablet hooked to WIFI for extended periods and never once did it show any signs of upgrading to 1.4.1

spottedtadpole said:
I downloaded the other Zergy and drivers files and had the same problems. I think the problem is the Windows 7 system and I could not get the "new" drivers to install. I will check your FAQ and if that does not work, I will try to get it rooted via Linux, but that approach seems not so easy.
Also, do I need to make a new Google account in order to download an app to the tablet? I tried it and it just sends the app to my phone.
thanks
Click to expand...
Click to collapse
for sideload apps like tgps_launcher.apk you dont need a google account, but for download from android market you will need one after you root.
Check out Albert's videos:
~ Veronica

I watched the video but was unable to install tgps_launcher.apk due to a parsing error. I do not think this is going to work.
I have never registered this device, I was afraid that if I did that, the device would revert to 1.4.1.
Linux also did not get this thing rooted with the NARS script. Although the Linux netbook mounts the tablet and I can see the files on it, the NARS script can't find the device.
thanks
P.S. I was able to install another package called AppMenu and that allowed me to enable USB debugging. This might be helpful.

blawens said:
Windows 7 64-bit here as well. The drivers are a pain but keep trying with usbdeviewer helping you and you will get it.
Also I have rooted three times and each time I had the tablet hooked to WIFI for extended periods and never once did it show any signs of upgrading to 1.4.1
Click to expand...
Click to collapse
It seems as though it will wait to upgrade when one registers the device with B&N and I have not yet done this.

lavero.burgos said:
for sideload apps like tgps_launcher.apk you dont need a google account, but for download from android market you will need one after you root.
Check out Albert's videos:
~ Veronica
Click to expand...
Click to collapse
Thanks for all the help. The video showed me what (I think) I might have done wrong. I did not think it was still necessary to reboot the machine after removing a driver. That and the link the video gives for an AppMenu really helped.
I am not certain whether all went well because the window closed abruptly after I selected removal of game apps during the installation process. I only wanted to remove the games and leave everything else. Going to reboot the NT. At least if something went wrong, I know I can restart.

spottedtadpole said:
Thanks for all the help. The video showed me what (I think) I might have done wrong. I did not think it was still necessary to reboot the machine after removing a driver. That and the link the video gives for an AppMenu really helped.
I am not certain whether all went well because the window closed abruptly after I selected removal of game apps during the installation process. I only wanted to remove the games and leave everything else. Going to reboot the NT. At least if something went wrong, I know I can restart.
Click to expand...
Click to collapse
You can uninstall the games later manually no need to run the script again, just make sure it rooted your device and you be good to go, also do not forget to block OTA. Indirect has another post for that specifically.
Download this app to uninstall data and system applications...
http://dl.dropbox.com/u/21630798/Apps/root_app_remover_vip_4.4Final.apk
Just in case read this is you ever want to debloat:
http://forum.xda-developers.com/showpost.php?p=21339441&postcount=2
~ Veronica

lavero.burgos said:
Just in case read this is you ever want to full debloat:
http://forum.xda-developers.com/showpost.php?p=21339441&postcount=2
~ Veronica
Click to expand...
Click to collapse
I did not full debloat because I thought I would lose all access to B&N. It happens that when I try to access B&N's Nook apps, to look for more apps, I get errors. This is probably not a big deal since I can probably get everything B&N has, from Android Market.
I did not know which launcher to install since I am unfamiliar with them. I just went with the "Go" launcher because it was first on the list; it's okay I am not voting for politicians, just a launcher for my tablet.
BTW, the first thing I did after restarting the tablet was to use Titanium Backup, then I replaced the backup files with three I had downloaded a few days ago, then I did a "restore" to those files. I checked my device information and confirmed that all went well.
I think this is why I can't access more Nook apps from B&N.

Related

How to sideload on 1.4.1 update: Guide + script

Alright, you need to be able to have the drivers setup and everything correctly because I'm not offering support on this. Sorry but I have alot of stuff to maintain so I can't always help. I'll try but I would prefer the community support each other too. (you also need tgps launcher already installed so if you havent rooted, I dont think you will be able to do this.)
Anyway: you need to get the .apk file you want to install and just put it into the directory and name it A.apk b.apk c.apk d.apk and so on. I will have it install up to 26 apps (all the way up to z) then you can remove and start over.
Script download:
here
I will probably update it eventually but right now it's supposed to be very basic.
Manual instructions:
All you need to do is use adb install appname.apk
Indirect said:
Alright, you need to be able to have the drivers setup and everything correctly because I'm not offering support on this. Sorry but I have alot of stuff to maintain so I can't always help. I'll try but I would prefer the community support each other too. (you also need tgps launcher already installed so if you havent rooted, I dont think you will be able to do this.)
Anyway: you need to get the .apk file you want to install and just put it into the directory and name it A.apk b.apk c.apk d.apk and so on. I will have it install up to 26 apps (all the way up to z) then you can remove and start over.
Script download:
here
I will probably update it eventually but right now it's supposed to be very basic.
Click to expand...
Click to collapse
Basically, for those a little familar with ADB, they didn't block adb install, so you should be able to adb install path\to\app.apk and it will load without an issue. If your not familiar with adb, using xIndirect's method is probably for the best for you.
so the android central sideload wonder machine should work.
In addition, they did not actually close the hole, they just covered it up better. If you sideload anycut, in theory, you can allow any other install. I am going to try it, and let you all know how it goes.
~Leko
gameman733 said:
Basically, for those a little familar with ADB, they didn't block adb install, so you should be able to adb install path\to\app.apk and it will load without an issue. If your not familiar with adb, using xIndirect's method is probably for the best for you.
Click to expand...
Click to collapse
They would have to maintain two versions of their software if they blocked adb install. How are they going to test the apps going into their market.
Sent from my BNTV250 using xda premium
xdahgary said:
so the android central sideload wonder machine should work.
Click to expand...
Click to collapse
Someone try this. You need the apk file of the app you want to install on your cimputer.
http://forums.androidcentral.com/an...-central-sideload-wonder-machine-v-1-2-a.html
Hey all, I cannot get his to work because I no longer have usb debugging. I should say I am on a Nook Color not tab. I just thought it would be nice to try non-rooted for a while. I guess I will just re root.
~Leko
lekofraggle said:
In addition, they did not actually close the hole, they just covered it up better. If you sideload anycut, in theory, you can allow any other install. I am going to try it, and let you all know how it goes.
Click to expand...
Click to collapse
I have AnyCut installed and created a shortcut to app settings. I reset the "Install from unknown sources" to be checked and then tried installing an app from the Amazon Market. When the package manager ran I got the new will not install dialog. Dang! So I launched the app settings again and noticed that the unknown sources box was unchecked. I checked it again, closed, and relaunched the settings window. The option is unchecked again. Grr....
Installing apps from the Android Market works just fine though, as it does not require the package installer to install an app.
Am I understanding this correctly? So even with un-rooted NT that has updated to 1.41 we can use this method to sideload? I so hope I am understanding this correctly. If so thank you so very much!!!!! If not thanks anyway for helping me learn!!!!!
I have been unable to clear and reset my drivers for the NOOK Tablet.
I've uninstalled and reinstalled but I must not have the right drivers.\
I'm running Win 7 64bit.
Any link would be appreciated.
GreenFuzzer said:
Am I understanding this correctly? So even with un-rooted NT that has updated to 1.41 we can use this method to sideload? I so hope I am understanding this correctly. If so thank you so very much!!!!! If not thanks anyway for helping me learn!!!!!
Click to expand...
Click to collapse
BUMP, as I was wondering this myself.
I understand how to use adb, but how do I get the Nook Tablet with 1.4.1 in debugging mode? I can't install the tgps launcher apk because it says it is not a Nook Store app. My Nook was previously 1.4.0 and rooted with android market and lots of apps installed. I have no problem with the new side loading method, but I need to figure out how to re-enter USB debugging mode.
Ugh, my Nook just updated to the dreaded 1.4.1 version. I tried the script from XDA and ran it with the command prompt, but it says "error no decide found", even though my Nook Tablet is plugged into my Windows XP Machine. Any ideas why this is happening?
I'd greatly appreciate it. Thanks!
Also, I got the script from here: http://forum.xda-developers.com/showthread.php?t=1407023 . I run the Sideload.bat file which usually doesn't run until an Android device has been found, and in MS Dos it says: C:\Sideload>adb wait-for-device . And yet when if I were to install an apk residing in the Sideload folder via Command Prompt, it says no device found.
szumlanski said:
I understand how to use adb, but how do I get the Nook Tablet with 1.4.1 in debugging mode? I can't install the tgps launcher apk because it says it is not a Nook Store app. My Nook was previously 1.4.0 and rooted with android market and lots of apps installed. I have no problem with the new side loading method, but I need to figure out how to re-enter USB debugging mode.
Click to expand...
Click to collapse
Scrap that. I thought I had to re-download the apk file. I realized that it is installed as a device app. Once I entered debugging mode I was able to sideload apps onto 1.4.1 using the instructions.
Now I would love to get Android Market working again...
Indirect said:
Script download:
Click to expand...
Click to collapse
Is there something available for Mac users? I don't have access to any Windows system for over a week.
Also, I was wondering if anyone out there has had success access the Android Market after using this new script? Hopefully some of the root teams/specialists out there can find use a better answer that going by to sideloading.
szumlanski said:
Scrap that. I thought I had to re-download the apk file. I realized that it is installed as a device app. Once I entered debugging mode I was able to sideload apps onto 1.4.1 using the instructions.
Now I would love to get Android Market working again...
Click to expand...
Click to collapse
Ok, so how DID you get it into debugging mode?
geonjay said:
Ok, so how DID you get it into debugging mode?
Click to expand...
Click to collapse
If you rooted 1.4.0, you would have used tgps launcher downloaded over the air. Once you run (install) the tgps launcher, it remains in your android apps installed on the Nook tablet after the 1.4.1 is installed by B&N. Just unplug your USB cable, run tgps launcher, go into te development settings, enable two debugging options, disable auto mount. Then when you plug in USB it should pop up a notification that you are in debugging mode.
Do "adb devices" from a command prompt. If your device is found, you can adb install apps.
so this won't work for unrooted? got my mom this for xmas, we had 1.4.0 and started sideloading apps...then outta nowhere today, the OTA came through and now i can't do anything. when i try this method, it tells me device not found. it doesn't show up under adb devices, either.
jayochs said:
so this won't work for unrooted? got my mom this for xmas, we had 1.4.0 and started sideloading apps...then outta nowhere today, the OTA came through and now i can't do anything. when i try this method, it tells me device not found. it doesn't show up under adb devices, either.
Click to expand...
Click to collapse
Looks like your only option will be to manually downgrade to 1.4.0 and load all the apps you want. You can also prevent OTA update to 1.4.1. Search the forums for the instructions. That sucks.
Alternatively, wait and see if a 1.4.1 root comes out.
xdahgary said:
Someone try this. You need the apk file of the app you want to install on your cimputer.
http://forums.androidcentral.com/an...-central-sideload-wonder-machine-v-1-2-a.html
Click to expand...
Click to collapse
Thanks, this works great. I know there is a way to root and install google apps on 1.4.1 now, but I'm fine with this since I don't have to go through the process of losing and then restoring all the apps and books I have loaded.
Just like another person mentioned, all one has to do is have NT Hidden Settings or tgps_launcher installed prior to the upgrade to be able to enable USB debugging.

[Q] NT=Android ADB interface instead of Android composite ADB interface. WTF!

downloaded all the stuff from the thread. everything went smoothly. i watched the video step by step. after uploading the usbdrivers to my NT it said
"Android ADB interface" instead of "android composite ADB interface"
it shows up in my device manager as a nook tablet still.
i derped. so i thought it would be ok anyways and then tried to zerg rush the baster-ahem NT only to see that the Zerg didn't even find my device.
i promptly decided to just wipe everything from my nook and start fresh but also every single thing i tried has failed to get rid of that blasted "android ADB device" from the one click unroot thing to doing a 8 step reset thingy and just plainly reset and wipe data from the stock settings, and now many hours later i have had enough and decided to swallow my pride and flaunt the noob card. i need help. i must find a way to wipe everything or maybe i can take a step from here. i dunno. derpy derp.
windows 7 ultimate 64bit
nook tablet 8 gb sd card.
(^^this is how people write these things right?)
wagon_burner said:
downloaded all the stuff from the thread. everything went smoothly. i watched the video step by step. after uploading the usbdrivers to my NT it said
"Android ADB interface" instead of "android composite ADB interface"
it shows up in my device manager as a nook tablet still.
i derped. so i thought it would be ok anyways and then tried to zerg rush the baster-ahem NT only to see that the Zerg didn't even find my device.
i promptly decided to just wipe everything from my nook and start fresh but also every single thing i tried has failed to get rid of that blasted "android ADB device" from the one click unroot thing to doing a 8 step reset thingy and just plainly reset and wipe data from the stock settings, and now many hours later i have had enough and decided to swallow my pride and flaunt the noob card. i need help. i must find a way to wipe everything or maybe i can take a step from here. i dunno. derpy derp
windows 7 ultimate 64bit
nook tablet 8 gb sd card.
(^^this is how people write these things right?)
Click to expand...
Click to collapse
hm... well not sure if this is hidden anywhere in your description but did you try reinstalling the nook tablet drivers? since you have android adb device right now, uninstall that and if windows prompts you to restart you should do that. When you uninstall the adb drivers if there is a checkbox saying delete driver software for this device make sure to check that as well. basically what i am trying to say is you want to start fresh as in there should not be any reference to android or nook on your windows pc
another program that may be helpful is using usbdreview which is a program that monitors all devices with usb drivers. this may help is attempting to delete any reference to android and nook on your windows pc. hope this helps!
EDIT: just to add this tidbit in, if your having troubles with ADB, chances are it has nothing to do with your NT but rather with the drivers that Windows has installed already. There's a guide to installing ADB correctly, here's a link:
http://forum.xda-developers.com/showthread.php?t=1424563
ShinnAsuka said:
hm... well not sure if this is hidden anywhere in your description but did you try reinstalling the nook tablet drivers? since you have android adb device right now, uninstall that and if windows prompts you to restart you should do that. When you uninstall the adb drivers if there is a checkbox saying delete driver software for this device make sure to check that as well. basically what i am trying to say is you want to start fresh as in there should not be any reference to android or nook on your windows pc
another program that may be helpful is using usbdreview which is a program that monitors all devices with usb drivers. this may help is attempting to delete any reference to android and nook on your windows pc. hope this helps!
EDIT: just to add this tidbit in, if your having troubles with ADB, chances are it has nothing to do with your NT but rather with the drivers that Windows has installed already. There's a guide to installing ADB correctly, here's a link:
http://forum.xda-developers.com/showthread.php?t=1424563
Click to expand...
Click to collapse
thanks for the reply, tried it. i tried the process and my computer said itfound drivers for my device but couldn't install new drivers on my android ADB interface.
same problem i had previously.
wagon_burner said:
thanks for the reply, tried it. i tried the process and my computer said itfound drivers for my device but couldn't install new drivers on my android ADB interface.
same problem i had previously.
Click to expand...
Click to collapse
hm.. well if it keeps on auto installing generic drivers you will need to disable auto installation of drivers by windows. try looking through each of these links and see if it solves your problem. fyi you should uninstall all drivers relating to android and nook before proceeding
http://www.addictivetips.com/window...tomatic-driver-installation-in-windows-vista/
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/
hope this helps
ShinnAsuka said:
hm.. well if it keeps on auto installing generic drivers you will need to disable auto installation of drivers by windows. try looking through each of these links and see if it solves your problem. fyi you should uninstall all drivers relating to android and nook before proceeding
hope this helps
Click to expand...
Click to collapse
well this is weird one atleast for me. i had all those settings on at the very start of the rooting process. and in the end i need to enable in the system config the USER to override the automatic driver install policy. so my anti install was thwarting me this entire time!!! ugh!!! total noob but we all gotta start somewhere. thanks to everyone for helping me out!

Snowball Mod/Root Issue

So I have been trying to install the snowball mod on my root. The problem is that no matter what I do each computer I plug the nook into it automatically installs the drivers so I cannot load the usbdrivers. I have tried on 3 different computers. 2 win 7 (64bit) and one Vista (32bit). One of the 7's was a fresh install with no updates. Do I need to use a specific version of windows or something? Is there any way to do this under Linux?
Have you read the sticky by lavero.burgos on NT Tips and Tricks? It got a FAQ and step by step guide link there to make things work under driver issue.
Step by Step guide to enabling ADB Connection on your stuborn Nook Tablet
jhall1990 said:
Is there any way to do this under Linux?
Click to expand...
Click to collapse
Snowball-mod comes with all the scripts also available in BASH for easy use in Linux and other GNU operating systems.
You just have to get the drivers to work, but after that it's just "sh ./snowball.sh" instead of "snowball.bat".
this may be the answer I'm looking for
I simply run snowball.sh instead of .bat if I already have a working, rooted NT, is that correct?
It simply adds/fixes all the stuff zergy doesn't, correct?

[Q] Woah! CWM problems

So, last night i tried to flash GtabComb to my 1.1 Gtab. After 3 unsuccessful installs (which I now believe are attributed to the system partition size of only 200 rather than 250 [help here would also be apprciated]) i downloaded the latest Rom Manager and updated ClockWork Mod. After the initial scare that my SD card had been totally formatted, i found that for some reason, this new CWM likes to use the second SD card... You know, the one with no backups or anything saved to it. For now, I am running a random ROM (Vegan Gingerbread) until i find out how to switch the SD card read by CMW. So any help guys? It's probably something really simple I'm over looking.. Help is appreciated greatly. Thanks
Edit: On a side note, I finally got GtabComb to load on my tablet! Seems I only needed a little bit of patience...
theshafe said:
So, last night i tried to flash GtabComb to my 1.1 Gtab. After 3 unsuccessful installs (which I now believe are attributed to the system partition size of only 200 rather than 250 [help here would also be apprciated]) i downloaded the latest Rom Manager and updated ClockWork Mod. After the initial scare that my SD card had been totally formatted, i found that for some reason, this new CWM likes to use the second SD card... You know, the one with no backups or anything saved to it. For now, I am running a random ROM (Vegan Gingerbread) until i find out how to switch the SD card read by CMW. So any help guys? It's probably something really simple I'm over looking.. Help is appreciated greatly. Thanks
Click to expand...
Click to collapse
The best way to install CWM is through NVflash. Rom manager is really designed for phones not this tablet. NVflash is simple and easy to use as long as you have a desktop or laptop using either windows or Linux. Here is the link to guide you through those steps. Helped me out when I was in a jam.
http://viewsonic-gtablet-for-dummies...om/nvflash.htm
Thanks for the advice! NVFlashing is a tad of a problem for me, however. I've actually commented on that particualr NVFlashing tutorial earlier today explaining how my computer won't recognize my tablet while it's in APX mode. I seem to have the worst luck with this kid of thing..
Would there another way to change which card is being read?
Do not use Rom Manager on the Gtablet it will mess things up. You can go to this link and download a .zip installable version of CWM for your bootloader. There are versions for installing from either the internal or external sdcard. If you are not installing from the external sdcard, it is best to remove it.
You could also check out this thread, and this one for more info.
It sure does mess things up! And that CWM.zip would be great had I not had another (worse) version already installed.. woe is me. I'll give those threads a read tomorrow and hope something turns up. Thanks for the links!
DaggerDave said:
Do not use Rom Manager on the Gtablet it will mess things up. You can go to this link and download a .zip installable version of CWM for your bootloader. There are versions for installing from either the internal or external sdcard. If you are not installing from the external sdcard, it is best to remove it.
You could also check out this thread, and this one for more info.
Click to expand...
Click to collapse
That would be the way to go but if you can't access the current CWM you cannot get it to install anything. The only other alternative would be to figure out why the computer won't recognize the tablet in APX mode. What OS are you trying it with?
Try this:
Download this .zip file and extract it to your Gtablet's sdcard.
Using a root file manager (ES, Root Explorer, etc.) mount /system as read-write (rw) and move the downloaded files in each folder to their proper locations (copy the system/etc/recovery folder into /system/etc and the files in system/bin into /system/bin) and make sure all the permissions are correct. The recovery images should be -rw-r--r--, the scripts inside of /bin should be -rwxr-xr-x and flash_image should be -rw-r--r--.
Open a terminal emulator and type 'su' (without quotes) and allow SuperUser when it asks. Your shell prompt should go from a '$' to a '#'. Now type 'cwmrecovery.sh' (without quotes) and enter. That should install cwm-08 for you, just exit when it finishes and try to reboot into recovery. You can use the 'fixrecovery.sh' script to flash the stock 1.1 recovery if you ever need to.
See the last thread I linked to in my last post for more info on this. Good luck!
DaggerDave said:
Try this:
Download this .zip file and extract it to your Gtablet's sdcard.
See the last thread I linked to in my last post for more info on this. Good luck!
Click to expand...
Click to collapse
Just extracted to the external SD that was being read from and updated from there with the new CWM and bam! .08 is on and working like a charm. Many thanks!
nobe1976 said:
Another alternative would be to figure out why the computer won't recognize the tablet in APX mode. What OS are you trying it with?
Click to expand...
Click to collapse
I would love to know why it doesn't. I was previously using a froyo tap'n'tap, but now I am running 3.0.1. Would OS make a difference? I always assumed it was my tablet/PC's/luck
I would love to know why it doesn't. I was previously using a froyo tap'n'tap, but now I am running 3.0.1. Would OS make a difference? I always assumed it was my tablet/PC's/luck[/QUOTE]
The OS on the tablet doesn't matter since the APX mode is the tablets download mode. The OS on you computer is what might be the issue, or could even be just a bad USB port or even drivers being used. If the computer keeps promptings that software needs to be installed. Guied the it to install them from the extracted NVflash file and install the ones that are in the pack.
I would love to know why it doesn't. I was previously using a froyo tap'n'tap, but now I am running 3.0.1. Would OS make a difference? I always assumed it was my tablet/PC's/luck
Click to expand...
Click to collapse
As the post above said, the OS on your PC is probably your problem. Which OS are you using? WinXP, Win7? I can't for the life of me get Windows7 to recognize my ICS Gtablet but o'well!
If you are comfortable with using or trying Linux, you could try installing Knoppix on a USB drive and run that. I think Knoppix has everything set up for MTP & ADB already and is 'live' so no real configuration is needed to get it running (except for your wifi of course). Just use the Linux version included in most NvFlash packages. If you have a fairly powerful computer, you could also try running Linux in a VM, but Knoppix doesn't run in a VM very well.
My favorite is Arch Linux (not in a VM). Although you have to build and configure the system yourself from the ground up. Since I started using Linux I have really enjoyed it. It is much faster than Windows, more secure and gives me less problems than the Win PCs I deal with. Check out this site if you are interested in Linux.
DaggerDave said:
As the post above said, the OS on your PC is probably your problem. Which OS are you using? WinXP, Win7? I can't for the life of me get Windows7 to recognize my ICS Gtablet but o'well!
If you are comfortable with using or trying Linux, you could try installing Knoppix on a USB drive and run that. I think Knoppix has everything set up for MTP & ADB already and is 'live' so no real configuration is needed to get it running (except for your wifi of course). Just use the Linux version included in most NvFlash packages. If you have a fairly powerful computer, you could also try running Linux in a VM, but Knoppix doesn't run in a VM very well.
My favorite is Arch Linux (not in a VM). Although you have to build and configure the system yourself from the ground up. Since I started using Linux I have really enjoyed it. It is much faster than Windows, more secure and gives me less problems than the Win PCs I deal with. Check out this site if you are interested in Linux.
Click to expand...
Click to collapse
To top on this excellent information. If you decided to try a Linux disto I would recommend a version of Ubuntu, doesn't really matter which one they are all really user friendly and depending on you pc setup depends on which version of it you can use. I have 11.05 installed on a 2nd partition for doing my Droid stuff on a computer that is around 9 years old, runs smooth. Windows xp is the other alternative which I have used several times NVflashing stuff, but adb seems to run better through Linux in my opinion.
Ah, mind went blank there. Right now, all I have is a windows 7 laptop (my XP desktop and older Vista laptop are probably long gone) Ive attempted to flash before with the vista laptop to no avail. In both instances, I connect the tablet in APX and it was not even recognized as a connected device. I'm hesitant to run Linux, even from a flash drive. If I get the chance to soon, I may very well end up doing it, as it appears the ONLY option.. Thanks for your help guys. If you could think of anyway for Windows 7 to recognize my tablet, please let me know. You guys are a great help. Thanks again!
If you haven't already tried this maybe it will work for you.
- Put the tablet into APX mode, then plug in the USB. Windows7 will drag on then fail installing the drivers, as usual.
- Go to Control Panel->Hardware and Sound->Device Manager and find the '!' (unknown device)
- Right click and choose Properties, then Uninstall Driver (if it is an option)
- Next, click on Update Driver, then choose Browse My Computer ...
- Navigate to the NVFlash folder (the one you extracted from the nvflash .zip you downloaded)
- Open the folder inside called 'usbpcdriver' or similar, and select the .inf file (NvidiaUsb.inf) and choose to install it. Once it installs, it should recognize the tablet as a MTP device. If not turn off the tablet, unplug the USB, restart Windows and plug it back in when it is finished rebooting and start the tablet in APX mode again. If it still doesn't recognize it try the whole process over agian.
I can understand being hesitant toward running Linux but running from a flash drive or in a VM is pretty safe, as in if you mess up the OS you can always start over without damaging Windows. Done it many times! Try running Ubuntu in a virtual machine such as Virtual Box, it is almost as user friendly as windows and you can have the VM capture USB devices such as the Gtablet which Ubuntu should recognize. Probably won't run very fast on a laptop but if you have at least a dual core with 2 GB of ram it should be pretty smooth.
Not trying to push Linux on you or anything, just some suggestions. From what I hear most of the Gtab devs use Windows7 and it seems to work great for them!

[Q] idiot's guide to rooting the 7840?

Hello...these forums seem to be both about older Dell Venue 8 models and also the newish Venue 8 7000 (7840). I do not know if they are supposed to be the same for rooting purposes.
I am not a complete newbie, having rooted several phones and tablets in the past, but I did that by faithfully following setp-by-step instructions I found here. I did find the following thread:
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
which seems to be relevant for the 7840, but post#1 assumes much prior knowledge and is beyond my capability to follow and implement.
Any advice or guidance would be appreciated, and pointing me to a set of instructions that doesn't assume much expertise would be fantastic.
Chuckles960 said:
Hello...these forums seem to be both about older Dell Venue 8 models and also the newish Venue 8 7000 (7840). I do not know if they are supposed to be the same for rooting purposes.
I am not a complete newbie, having rooted several phones and tablets in the past, but I did that by faithfully following setp-by-step instructions I found here. I did find the following thread:
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
which seems to be relevant for the 7840, but post#1 assumes much prior knowledge and is beyond my capability to follow and implement.
Any advice or guidance would be appreciated, and pointing me to a set of instructions that doesn't assume much expertise would be fantastic.
Click to expand...
Click to collapse
That is what I used.
bamfsig45 said:
That is what I used.
Click to expand...
Click to collapse
That may be, but as I noted above, I cannot follow these instructions. The poster himself/herself notes that these are rough notes. Would anyone be able/willing to provide a walkthrough for non-experts?
If you have any fear, do not proceed or get help from a knowledgeable warm body
Chuckles960 said:
That may be, but as I noted above, I cannot follow these instructions. The poster himself/herself notes that these are rough notes. Would anyone be able/willing to provide a walkthrough for non-experts?
Click to expand...
Click to collapse
@Chuckles960 - I know this isn't the answer you want to hear, but I would not attempt this method if you in any way feel uncomfortable with the process. The Venue 7840 does not have any 'reverse'/unbrick procedures out there (as of yet). Also, Dell does not offer their ROM for reinstall like other manufacturers do. However, there is a link to a full Nandroid backup of the 4.4.4 stock ROM within the Venue General forum.
Have you ever installed recovery, unlocked bootloader(s) or rooted any other Android devices?
-Jay
PS - By 'knowledgeable warm body', I didn't mean it offensively. Just a friend or someone you can meet locally that can help you in person. Trust me, this is hard to translate over a forum. I just want to make sure you don't have any frustrations with your Venue. Congrats on the purchase!
It's easy...
1) Install the Intel ADB Drivers from: https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
(Use compatibilty mode if you are using Windows 8.1)
2) Device Manager may not properly detect the drivers so you have to specify the Android ADB driver from the install folder above.
3) Extract IntelAndroid-FBRL-01-17-2015.7z into a folder.
4) Copy UPDATE-SuperSU-vX.Xx.zip to the internal storage or SD card
5) Run launcher.bat and and make sure it detects your device in debug mode (Turn on debug from Settings on the device.)
6) Choose the T3 mode and wait for Fastboot to load and select the SuperSU zip and install. Reboot... It should be rooted.
This worked for my 7840 and 3840...
And, in case you were not aware, enable USB Debugging on your 7840. After doing so, upon the first cable connection to the PC, a pop-up will appear asking for permissions to connect. Be sure to approve this.
DanielNTX said:
It's easy...
1) Install the Intel ADB Drivers from: https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
(Use compatibilty mode if you are using Windows 8.1)
2) Device Manager may not properly detect the drivers so you have to specify the Android ADB driver from the install folder above.
3) Extract IntelAndroid-FBRL-01-17-2015.7z into a folder.
4) Copy UPDATE-SuperSU-vX.Xx.zip to the internal storage or SD card
5) Run launcher.bat and and make sure it detects your device in debug mode (Turn on debug from Settings on the device.)
6) Choose the T3 mode and wait for Fastboot to load and select the SuperSU zip and install. Reboot... It should be rooted.
This worked for my 7840 and 3840...
Click to expand...
Click to collapse
Chuckles960 said:
That may be, but as I noted above, I cannot follow these instructions. The poster himself/herself notes that these are rough notes. Would anyone be able/willing to provide a walkthrough for non-experts?
Click to expand...
Click to collapse
I'm right there with you - The challenge I'm having seems to be more with the Windows drivers... it always sees the device as MTP or just a portable device regardless of having the Intel and pointing Windows to the Intel install folder. Can't seem to get it to recognize the device correctly.
In my case I to select the ADB Interface driver manually (can't remember exactly) rather than relying on Windows to identify which driver it needed on it's own. IIRC you have to click 'Have disk' and go through the steps there until you get two lists, one of manufacturers and the other of device types. You're looking for an intel ADB interface or similar.
anggusss said:
In my case I to select the ADB Interface driver manually (can't remember exactly) rather than relying on Windows to identify which driver it needed on it's own. IIRC you have to click 'Have disk' and go through the steps there until you get two lists, one of manufacturers and the other of device types. You're looking for an intel ADB interface or similar.
Click to expand...
Click to collapse
This was the piece I was missing!!!! I used the Have Disk and managed to load the ADB driver that way. THANK YOU!
Thanks to all for the tips! I will try it now.
Question: there is a Lollipop update promised for this month (or so). Will I be able to root again after the update, using the same procedures? (I am sure this is a naive question.)
DanielNTX said:
It's easy...
1) Install the Intel ADB Drivers from: https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
(Use compatibilty mode if you are using Windows 8.1)
2) Device Manager may not properly detect the drivers so you have to specify the Android ADB driver from the install folder above.
3) Extract IntelAndroid-FBRL-01-17-2015.7z into a folder.
4) Copy UPDATE-SuperSU-vX.Xx.zip to the internal storage or SD card
5) Run launcher.bat and and make sure it detects your device in debug mode (Turn on debug from Settings on the device.)
6) Choose the T3 mode and wait for Fastboot to load and select the SuperSU zip and install. Reboot... It should be rooted.
This worked for my 7840 and 3840...
Click to expand...
Click to collapse
This worked fine on my 7840, but only after some struggling with drivers. I have Win8.1 64bit, and the ADB driver from these instructions (line#1) did not work. Going back to the main thread (linked in the first post on this thread) and paging through to (I think) page 10, I found a link to Win8.1 ADB drivers and those worked.
Other than that, everything went smoothly. Thanks to everyone who responded helpfully!
Now what happens when we get Lollipop? TBD?
Chuckles960 said:
This worked fine on my 7840, but only after some struggling with drivers. I have Win8.1 64bit, and the ADB driver from these instructions (line#1) did not work. Going back to the main thread (linked in the first post on this thread) and paging through to (I think) page 10, I found a link to Win8.1 ADB drivers and those worked.
Other than that, everything went smoothly. Thanks to everyone who responded helpfully!
Now what happens when we get Lollipop? TBD?
Click to expand...
Click to collapse
Exactly! If SuperSU build supports that version of Lollipop, the tethered CWM should hopefully work ONLY if Dell doesn't have some f***ery in any new boot.img updates
Thanks for making this thread, I just successfully rooted my 7840. Now hopefully Dell comes out with a lollipop update and we still keep root :fingers-crossed:
Has anyone tried this with Lollipop yet ?
I accidentally (!) installed the OTA.
I wanted to install LinuxDeploy
Many thanks
Old method not working with latest lollipop update...
Can someone post the screen shot of trigger T2 from the tethered cwm recovery , I know it doesn't work but I need to see the batch screen output.
screens T2 T3
here r the screens for T2 , cannot attach pictures or 2 dumb
https://drive.google.com/folderview...I1REJPOVZhWEx5dlNGZF9iV1MzNnJ0c3c&usp=sharing
and T3
https://drive.google.com/folderview...BkRm5DUHdFbkJqdVpIVXJjM1FicGNtWjg&usp=sharing
Bad news on the root and 5.0.2. I feel pretty confident that it will eventually come to be. I just wish there were more development and fanfare for the 7840. It is such a stunning piece of technical
Gonna need a couple testers soon, think I found away just need to work out a few kinks,
I have an early test ready if interested reply to this post.
yeah, i'm in :good:

Categories

Resources