yashsingh1/xdaforums huggingface dataset:
[Dell Venue] vilehost:
I didn't use that one so I cant advise you if its safe or not, clean unroot supersu option I think is what put it in bootloop. after lots of different things to get it to try a fac hard reset, (apparently these devices have a few different hk options including holding the power button down for 30 seconds then power up as normal (( supposed to hard reset but I found not in my case)), a diagnostic's mode you get to by holding vol up and pressing power simultaneously but only holding the vol up key - this also didn't work in this case) and getting into droidboot (fastboot) by holding vol down and power button till screen power's on,

after that you can do all the fastboot commands on your computer like /fastboot flash recovery xxxx -p xx (this is where my delima is, erase commands work, but when it begins the flash just after it's finished pushing i'll get a failed remote: flash_cmds error! two or three things could be causing this and I don't know how to go about it on this specific device atm,

also there you can get into recovery, once you see the droid on his back with the explanation mark you have to simultaneously press vol up and power key and keep doing it till you see the dialog, in there it's almost like basic cwm with wipe data/fac. reset, update from zip, wipe cache and reboot (update from zip I get zlib corruption errors)

p.s I wouldn't recommend anyone messing around with any of this stuff unless you know what you really know what your doing, and or already have a busted device

-im hearing that the only easy way to get rid of impactor master key root is by flashing the newest official firmwares
[Dell Venue] stang48317:
You could try the x86 system image in this forum, since this tablet uses the same processor? http://xdaforums.com/showthread.php?t=2568724
[Dell Venue] vilehost:
tried this one and a build from x86android, both wrote with :fastboot flash update /path/to/cf but still results in bootloop after self reboot. somethings up with /system part

fastboot seems to get further than recovery update from zip, everyone I tried there gives me zlib memory /data/corruption error failed and will stop before writing begins
[Dell Venue] Minnetonka4me:
Awesome to hear you guys got it working! Now...how when is someone going to make a youtube for us dummys?
[Dell Venue] megaghostgamer:
I can give you a pretty detailed description on how to root your dell venue, that's about it because I don't want to root mine just yet. The review I'm doing is basically from sfleury.

Neither sfleury or I take any responsibility as to you bricking your device at any time. Some people are finding out that they can't root their device with this method because of signature bugs. Continue the root guide on your OWN terms. Thank you.

1. Get Cydia Impactor (This is being the main root exploit.) The Site can be found here: http://www.cydiaimpactor.com/ . Choose the operating system you are using on the left section and wait for the download to complete.

2. Where ever your Cydia Impactor is located on your computer, unzip the files into a folder.

3. Once files are unzipped, insure you are running the impactor.exe in administrator mode. (Windows Users right click and Run As Administrator)

4. Now we need to get the intel android drivers. These drivers are located here: http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices . Sometimes users have to go into the compatibility mode and install the driver in windows 7 mode or you can also check device manager (accessed by right clicking my computer and clicking manage) and find your venue in the list and manually update it with the package. [Thank IShman For This Step!

5. Make sure your tablet is properly connected to your computer with the usb port and make sure USB Debugging is Enabled!

6. In the Impactor ensure that it says "# drop SuperSU su to /system/xbin/su" and hit the Start button located the the right of the line.

7. Once this is completed, you want to open command prompt or terminal in your adb on your computer. This will be found in the platform tools section of the adb on your computer. On windows to access the terminal or command prompt hold shift and right click in the folder and click open command window here.

8. Now the command window is open you want to type the following 1 line at a time:

Adb Shell

/system/xbin/su

mount -orw,remount /system

mv /system/bin/su /system/bin/su.org

ln -s /system/xbin/su /system/bin/su

8. Now that root has been pushed to your tablet, you want to install the SuperUser app from the playstore.

9. Once you have downloaded the app, you should be able to use root and do whatever you like with the root.

Enjoy! :) Also, notify me if anything is wrong in this guide! I will be sure to change it as soon as possible!

This guide was based off of sfleury's guide

Again, neither of us are reliable for any damage cause to your tablet! USE AT YOUR OWN RISK!

Have a nice day :)
[Dell Venue] sfleury:
root is root ... be careful what you try to do with it.

If you tried to install Complete Linux Installer from the play store it can't work because that is for ARMv7 and these are x86 tablets you would need a Linux that was compiled for x86

I don't know about the tor app, but if it needs root to install a binary it probably has the same issue, i.e. it needs an ARM processor.

---------- Post added at 03:37 AM ---------- Previous post was at 03:25 AM ----------

The most likely scenario is that you can get the 4.3 update, and that it will overwrite your system partition and your root access will be lost. To go along with that, based on what others have said 4.3 doesn't appear to have the same vulnerabilities, they even seem to be fixed on some flavours of 4.2.2 on this device, so rooting 4.3 with the same method won't likely work.

I think, until there is a known 4.3 root method, you have to choose either 4.2 with root or 4.3 without.
[Dell Venue] xdajunkman:
Unfortunately, Cydia Impactor did not work for me...as sfleury stated there may have been some versions of 4.2.2 on this device with the exploit patched as it is not working for everyone. Regarding keeping root after the 4.3 update, the updater-script in the 4.3 update file does not appear to have anything in it that explicitly breaks root or removes the su binary. The 4.2.2 update did. That doesn't mean that there isn't something hidden in the edify code that will break root, but I can't find anything. If anyone is interested, I uploaded the updater-script to my Dropbox:

https://dl.dropboxusercontent.com/u/59893236/updater-script

The whole update file is here:

https://dl.dropboxusercontent.com/u...456e56466ad8.Venue8SignedDeltaV1.39-V1.15.zip

If anyone is particularly brave and willing to risk losing root, try updating and see what happens. The community will honor your sacrifice if you lose root.
[Dell Venue] Ishman:
Good write up. I would add to make sure you install the intel android driver from here

http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices

Also, I still had to go to compatibility mode and install the driver in Windows 7 mode.

One should also check device manager afterward and might have to manually go and update the Android driver (I did).

Worked fine after this.

thanks
[Dell Venue] JediSooner:
Cydia Impactor did not work for me either... it hangs on "Testing #9950697". I tried it even though I took the 4.3 update. SRT AppScanner also shows that the 3 vulnerabilities it checks for have been patched.

At this time, there's no way to go back to 4.2.2., correct?
[Dell Venue] N2PC Tech:
Mine hangs with that error also and is still read only!

*Busybox showed it as rooted, but wouldn't install!
[Dell Venue] saintii2:
Is that the 4.3 update file? If so, how do you install it?
[Dell Venue] sfleury:
Well that is interesting I didn't expect them to update individual files in /system I thought they would overwrite the whole partition.

I think line number 5702 of the updater-script will be a problem (i.e. it will remove root access):

set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");

If I read that correctly it will change all files under /system/xbin to root:shell (uid=0:gid=2000) ownership with 0755 (-rwxr-xr-x) permissions and we need /system/xbin/su to be owned by root:root (uid=0:gid=0) with suid permissions i.e 06755 (-rwsr-sr-x). Without the correct ownership and suid/sgid permissions su can't give you root access.
[Dell Venue] Minnetonka4me:
Thank you for that excellent write up. I was confused last night what firmware it was working on, but I see now that 4.3 doesnt work. I already updated. I needed multi-user mode.

I will keep watching you bad aszes break down these issues....hopefully someone can exploit 4.3.
[Dell Venue] deansouth8:
Anyone think a rootkeep app or supersu check box attempt to keep root will work in this scenario? Something with 4.3 support? Android root toolkit in the play store says does.

Also, I can only get supersu app to work, I can't get chainsdd superuser app to work (prompt for root perms). Anyone know if this is normal? Otarootkeeper doesn't have 4.3 support.
[Dell Venue] sfleury:
I have not used ChainsDD but looking at its entry in the play store it appears to have last been updated in July 2012 and it says it has a binary. I suspect the binary is only compatible with ARM arch devices ... It looks like there is an x86 version on the developers web site, but also comments that it doesn't work past 4.1
[Dell Venue] megaghostgamer:
Thank you a lot, but this may be a silly question, but tweaking that package not apply the patches, could we possibly have a functioning 4.3 with root. I see the patch folder in the update, all you would have to do is delete it and mess with the updater script, I'm not sure if it'll work and I'm not sure what all is in the patch folder as far as other bug patches. I'm just throwing an idea out there, not sure if it'll work or not or if it's even smart to attempt, but thanks again for the update. My tablet ran real racing 3 really slow on 4.2.2 but now it's working really fine with no lag.
[Dell Venue] xdajunkman:
I stand corrected. You are correct...this would break root.

---------- Post added at 06:27 PM ---------- Previous post was at 06:08 PM ----------

The file is signed. Recovery will refuse to install the update if you alter the file. I have tried several methods without luck.
[Dell Venue] rener78:
Hi there I already rooted my Nexus S and my SGS3 and I just bought a Venue 7 and wanted to root it, not to use a different rom but just having root acces. So if I can sum up the whole thread it is possible to root a Venue 7 and 8 but not all of them right ? Right now I'm not on 4.3 so there's a 50/50 % chance that I would be able to root my Venue 7 is that right ? Just have to follow the instructions stated a few post prior correct ? Is there a recovery existing for the venue 7 and is there a TWRP or CWM existing for the venue 7 ?

Thanks all
[Dell Venue] megaghostgamer:
Yes, since you're on 4.2.2 you are liable to be rooted. Just look at the guide a few post back and follow details closely, also the tablet does come with a stock recovery but that's pretty much it. We just got a root exploit so we do not have TWRP or CWM available. Give it time though ;)
[Dell Venue] deansouth8:
What is the method by which you updated assuming you used the posted download?
[Dell Venue] megaghostgamer:
I was unsure as to if we could delete some things in the update so we could root 4.3 but we can't because of security checks.
[Dell Venue] uptick:
iirc it's possible to root a Venue 8 that has older firmware,

but the Venue 7 shipped later in the year, with all the exploits

patched shut, according to what this thread says.

So no, your Venue 7 can't be rooted from re-reading this

thread and applying the ideas given (except possibly the

cydia Impactor method -- I don't remember the outcome

on that in the thread; I couldn't try it here but tried most

everything else offered in the thread).

The reason I remember is because I'm reading the thread

carefully, with an eye towards rooting a Venue 7. And I

don't feel deprived, as to my knowledge, nobody has a

rooted Venue 7.

Nobody.

Not yet. ;)

Says the thread, unless I'm mistaken.

Edit:

Thread milestone:

Post 184 - a Venue 8 is rooted on 29 December, 07:01 UTC.

uptick

New England, USA

____

me: Venue 7; 4.3 OTA update pushed after a factory reset

I did on Dec 20th.

The audio is futzed now. Rebooting, then clearing MX Player

cache and data seems to correct it, temporarily. Multi-user

in use; nice for handing the tablet to a friend without privacy

issues.

Edit:

* Bluebox Security Scanner says I'm patched for bug 8219321

and bug 9695860.

Edit:

This leaves bug 9950697 open to exploit on my Android 4.3

(Dec 2013) OTA push (to Venue 7). Possibly.
[Dell Venue] rener78:
Thanks [MENTION=2117449]megs[/MENTION]ghostgamer and [MENTION=5590319]uptick[/MENTION]. Really appreciated I read the thread carefully and being bilingual and French being my mother tongue I just wanted to make a post and clarify some info before bricking my daughter's Christmas gift lol. Thread is not confusing but it's not clear really. Since its brand new I'm pretty sure it has been patched but oh well I'll try since it's still under the warranty. I'll keep you posted, thanks all.

One quick question. When i plugged the tablet in my computer I the drivers were install automatically by Windows should I remove it and install the one provided in the root post instead or it wouldn't make any difference at all.

Thanks again and happy holidays by the way.

Envoyé de mon SGH-T999 en utilisant Tapatalk
[Dell Venue] megaghostgamer:
Install the drivers provided in the guide posted back.

To Root You Need:

Dell Venue (8 Only So Far)

4.2.2 (4.3 Cannot be rooted)
[Dell Venue] robrowald:
Manually updating to 4.3

For those of you like me who want 4.3 but your tablet hasn't gotten it, or didn't work when you downloaded it, fear not!

I have created a step by step guide for manually updating to 4.3. Thank's to [MENTION=686670]xdajunkman[/MENTION] for the update file.

see this thread: http://xdaforums.com/showthread.php?p=48971583#post48971583
[Dell Venue] darklordofthesith:
Hopefully someone can come up with a root method for us on 4.3. God, I hope so.
[Dell Venue] deltatux:
Technically since some people have been able to gain root from their Dell Venue 8 tablets, they can simply extract the boot.img so that it can be made insecure by developers. Once that is done, pretty much everyone can get their tablets rooted. An insecure kernel is required for adb root to work in the first place by modifying the default.prop that's stored in the boot.img.

deltatux
[Dell Venue] xdajunkman:
True, but remember that we kind of tried this already. Fastboot on these devices is crippled so that we cannot boot from an alternate boot image - the 'fastboot boot' command is disabled. We also cannot flash anything to the device with the stock version of fastboot, only erase partitions. Without the ability to actually boot from the insecure boot image, nobody else can profit. The device has a functionally locked bootloader, or at least no easy way to modify the contents of a non-rooted device.
[Dell Venue] chairsz:
you have any pointers on how to extract bootimg? im been trying some guides around xda within terminal EMULATOR and nonE are working for me, like the cat /proc/partitions and others.

btw me device is my second venue 8 with stock 4.2.2 with NO UPDATE PERIOD. not the small 6.5MB or the subsequent 4.3 (165 MB ish) and rooted.
[Dell Venue] stang48317:
You could try the methods in here: http://www.addictivetips.com/mobile/how-to-backup-your-android-phones-boot-recovery-and-system-partition-images/

Or use this tool: http://xdaforums.com/showthread.php?t=1770816
[Dell Venue] deltatux:
That could just be that the boot.img may have failed due to improper boot.img compilation. We still haven't tried the extraction method yet since we just recently achieved root.

deltatux
[Dell Venue] cellphone89:
Just installed and ran SRT AppScanner on my Dell Venue 7 (4.2.2) and I couldn't do anything with it since everything seems to be patched.

Well guys thanks for the support I look forward to see a new costume firmware up ahead. (Happy new year to all!)
[Dell Venue] kildurin:
Just to add to the discussion, I have a Venue 8 that I purchased in November 2013. App Scanner shows that it has been patched. So, not all 4.2.2 Venue 8's are rootable. Mine has a build date of Oct 19 2013. So, 4.2.2 was patched at some point.

Dell Venue 8 3830_v1.39_131019-nomodem

Kernel: 3.4.34

DYY@build162 #1

Sat Oct 19 10:51:31 CST 2013
[Dell Venue] jayjr1105:
Hey all, been a while since I checked this thread. I see someone was partially successful with root on 4.2.2. Unfortunately I'm up to date with 4.3 however my touch screen issue is gone. Are we well on our way to full root/custom rom's or is it still a ways away?
[Dell Venue] chairsz:
what constitutes as full root? like is there a certain command you cant type in terminal adb or what? cause im un der the impression since I can access al files and change whatever I want in data, the built prop area etc... if that's not full root what is?
[Dell Venue] sfleury:
If you have the right 4.2.2 build(s?), on a Venue 8 then it is fairly easy to get root access, but so far with later versions of 4.2.2 and 4.3 it is not. I don't really know what you mean by "full root", root is root just be careful what you try to do with it....especially on a device that won't let you back in if you screw it up.

My priority is to try and find a way to keep root access when/if I upgrade to 4.3+ which is not currently possible. If I figure that out I will post details.

My secondary desire to to enable people on other builds to gain root access, but at this point all I can really do is lend moral support to people with those builds.

As for custom ROM's, there is little to no progress on that front and there probably won't be until/unless someone can figure out how to push in reliable, unlocked recovery software.

There are various people trying things and I'm sure if they have any good news to report they will do it here.
[Dell Venue] TwisteDale:
So there is no root at all for the Dell Venue 7?

I'm new to this android thing, so there is no root for the Dell Venue 7 at all because of the bootloader?
[Dell Venue] sfleury:
Not at this time ... it is more because the "known" vulnerabilities for which there are tools to allow root access in 4.2.2 have been fixed on the version that is on the Venue 7. With any luck someone will find another one in either 4.2 or 4.3 but its hard to say how many people are trying.
[Dell Venue] aniym:
For those who have achieved root on the Venue 8:

Is there any way to get rid of the navigation bar and use something like PIE Control?

It's annoying because most Android tablets have a combined nav/status/notification bar on the bottom. The Venue has both a status bar on the top and a huge nav bar on the bottom. Combined, they cover up quite a bit of the screen, especially in landscape mode. Something like PIE Control would be great to reclaim the wasted space.

Alternatively:

1. Is there a way to make the nav bar transparent?

2. How about reducing the size of the nav bar (which you can do with PA Roms for instance)

Thanks.
[Dell Venue] chairsz:
im sure u can change that stuff but we dont have any real devs yet looking at the venue to take a crack at it, which is sad because this device is right up there next to the best in terms of hardware but the ui and software is simply where dell needs to up their game. it seems most devs these days are only interested in the super high end devices where it costs an arm a kidney and 2 fingers to buy, and even more to fix if it breaks.
[Dell Venue] sfleury:
Some of the other launchers, Go Launcher for example on the Play Store have options to hide the status bar, there is an app called "fullscreen" (and there may be others too) that can hide the Nav bar.... not sure which, if either, of those things requires root access.
[Dell Venue] endleesss:
Adding softkeys do not require root, many apps do it.

Removing your stock navigation bar requires root.

fullscreen requires root access. you can also do it manually:

to remove softkeys

Go to /system

build.prop

add:

qemu.hw.mainkeys=0

to turn it back on delete the gemu line, or substitue a 1 where 0 is.

warning, if you do not have another app that shows your navigation bar, you will not be able to navigate.
[Dell Venue] aniym:
Thanks for the tips. I really hope a simple root or custom recovery method can be developed. I've just noticed that the battery life on these is pretty bad: I'm getting 4-5 hours of on-screen time, which is a lot less than what I was expecting.
[Dell Venue] chairsz:
I thought that as well but after having the venue 8 for a few weeks now, battery lasts me for as long as I need it depending on what im doing. ex if im playing a heavy battery consumption game like the dark knight from a full charge I might get say a good 3-4 hours of playing and another 6 or so of web browing or another couple of days of idle mode. battery life all depends on what your doing, regardless of actual capacity.
[Dell Venue] sfleury:
I don't find the battery to be any better or worse than the 3 other tablets in the house.
[Dell Venue] NotQuiteANoob:
Additional User experience following the Venue Root guide.

First of all thank you for adding the details! There is no way I would have attempted this otherwise. This worked on my 4.2.2 Venue 8. I did everything including installing the intel USB driver and my PC connected to the Venue with no problem. However I had a few hiccups once I got to step 6 which I'll mention in case anyone runs into something similar.

Cydia gave me the following error "could not access the package manager. is the system running". I realized I had the bluestack emulator installed on my PC and I believe Cydia Impactor was trying to connect to that so I uninstalled the bluestack android emulator. After rebooting the PC then I got an error about no device from Cydia Impactor even though my Venue opened in explorer and I could see the files, etc. I ran the Cydia USB/driver scan and that fixed the problem and I was able to run the Cydia command "# drop SuperSU su to /system/xbin/su" which now proceeded and finished. However, at the same time Norton 360 complained about Suspicious.AD and quarantined installer_x86.exe which makes me go hmmmm. Does anyone this is a virus or did Norton flip because it's a hacking tool?

2nd hiccup was that the ADB commands wouldn't work for me at first. I was using the ADB dated 10/23/13 from the SDK and it did nothing for some reason. I switched to using the ADB dated 3/6/13 that came with the Kindle Fire Utility and that worked fine.

So now I'm rooted and have made my first Titanium Backup.

Edit:According to OTA Rootkeeper I'm not rooted but the Titanium Backup did work Is there such a thing as half ass root?.
[Dell Venue] aniym:
I understand that battery life varies according to use patterns. But this is far from my first Android tablet...I've owned and used 10.1, 7, 8.9 and 9.7 inch tabs with varying battery capacities. I also don't game on this tablet at all....it's web browsing and PDF/ebook reading mostly for me. Reviews of the tablet on both Amazon and Laptop Magazine have called out the poor battery life as well.

I'm trying to find the actual battery capacity for the tab, but Dell's website doesn't show it and sites like GSM Arena often get these specs wrong. If the battery capacity is significantly lower than Samsung Gtab 8.0 or the Dell Venue 8 Pro (which according to reviews gets 8+ hours without issue) then I don't think any amount of custom ROM optimization can improve it beyond what I'm currently getting.