yashsingh1/xdaforums huggingface dataset:
[Dell Venue] Cookie Ninja:
Are we on the same planet? I have a 3-day old dell venue pro 7 (android 4.3) running WiFi only on a dual core Intel processor; and here are people talking of venue 8 (I thought this was the big brother android device) and winphone 8?WTFIHH?

Dead Cookies leave no trails...
[Dell Venue] social-design-concepts:
Venue 7 isn't pro Venue 8 isn't pro Venue Pro is a Windows Phone, Venue 8 Pro is a Windows 8 tablet, your whole statement confused me and made my head explode...

---------- Post added at 01:05 PM ---------- Previous post was at 01:03 PM ----------

and to answer your question before you ask because you obviously haven't read this thread no there is no root for the JB4.3 2013 Venue 7/8 tablets yet...
[Dell Venue] rb420:
Although it wasn't for me, thanks! saved me from reading through the last couple dozen posts since I've last checked.
[Dell Venue] hunterk11:
Yeah… you are horribly confused

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] megaghostgamer:
Let me explain this since people can't seem to read before posting...

Venue 7 and Venue 8 Are BOTH ANDROID TABLETS.

The dell venue 8 pro is a Windows Tablet which is nearly completely unrelated to this root process

When people say v8 they mean venue 8

When people say v7 they mean venue 7

What are the differences between the dell venue 7 and 8???

Hmmm well let's see. The processor in the v8 is faster than the one in the v7. I believe the v7 is 1.6ghz and the v8 is 2ghz. They use the same Intel processor though

The camera is better in the v8 as well but I really don't use it.

The venue 7 is a 7 inch tablet.

The venue 8 is a 8 inch tablet.

Let's not forget once again:

The dell venue 7 & 8 are android tablets

The dell venue 8 pro is a windows tablet

Please read before you post so both others and I don't have to waste our time on these useless post. The title of this thread clearly states 2013 Dell Venue Tablet - root process. If you have any questions, create a thread and let it be answered their. This thread is meant for development purposes not questions. I cannot stress this enough. Don't feel like I'm only ranting on you, its a lot of others who haven't seem to grasp the concept of the thread, my post goes out to them as well.

Thanks and have a great day.
[Dell Venue] hunterk11:
We have been using it as a section though, since we dont have one

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] cline2:
Please close this damn thread if there is no root method for Venus 7/8. If someone find a way to root then open the new thread!
[Dell Venue] 177aj:
Thread

This thread is not just for the root method, it is for any question anyone might have. We just use this thread since there is no official one yet.
[Dell Venue] madi05:
i think the title should be changed from root progress to something else imho
[Dell Venue] social-design-concepts:
update: flashing 100MB userdata.img seems to be large enough to boot android, :good: but /data/local.prop is not used on user builds. :crying:

well the search continues for something in /data that is called by root that maybe we can exploit, any ideas?

i've attached a simple proof on concept 100MB userdata.img that can be flashed through fastboot

!!!!!!!!caution this completely wipes the /data partition backup you data before you try this is !!!!!!!!NOT ROOT!!!!!!!! just a simple proof of concept.!!!!!!!!

extract the zip to some where you can use fastboot from and run

reboot into fastboot and run:

fastboot flash data userdata.img

what this does is flash a 100MB data partition that i built to the Dell Venue 7 / 8 Venue 8 is untested

i've add a few apps that will be handy if i figure out root access, terminal.apk, rootcheck.apk and koush's superuser.apk, no real woop here...

the fun part:

i've set a few persist properties under /data/property

sets the usb mode to iadb this is the adb mode used when the device is powered off and charging

:good: persist.sys.usb.config=iadb

sets the usb state to iadb and makes our device detect as adb this is the usb state used when the device is powered off and charging

:good: persist.sys.usb.state=iadb

this sets adb debugging enabled so we don't have to complete the android setup wizard and go into settings to enable it to allow us to authorize our device.

:good: persist.service.adb.enable=1

big woop right? these properties can only be called by root on boot so if something can be found that is called by root while booting we might be able to exploit it to run a rooting script or crafted binary to root the device.

and the search continues...

you will need to factory/data reset through either the settings menu or wipe data/cache through recovery to restore the data partition back to its normal size after.
[Dell Venue] hunterk11:
Then how the **** would we know a new thread opened, if it bothers you stop following it.

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] megaghostgamer:
It can be asked in general section with a Q next to it and a correct title. Hell , even still they should still read before posting and keep it TOPIC RELATED as states in XDA rules.

---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------

Your statement is flat out ignorant. The thread title clearly states root progress NOT root. Learn the difference.
[Dell Venue] social-design-concepts:
Won't be back to work on this till late tonight. If any one has any productive suggestions please quote this post.
[Dell Venue] arclight25:
Your hard work is appreciated!
[Dell Venue] wowbro:
Can I please get the Rooted 4.3 dumps
[Dell Venue] social-design-concepts:
they'll be linked when i get a chance to. i'll only be uploading the dumps for droidboot, recovery, and boot kernel/ramdisk, ive not found any way to flash them unless it was a way to root the device i'm not going to be uploading the system.img.
[Dell Venue] social-design-concepts:
I wouldn't call it work. Its boredom. wish i understood androids inner workings better, lots of reading lots of trial and error.
[Dell Venue] Cookie Ninja:
ADB debugging is enabled in dev settings, always allow was ticked when adb ran first, but subsequent connection to PC shows device as off line when running "ADB devices" command. Any help? Dell venue 7......

Dead Cookies leave no trails...
[Dell Venue] social-design-concepts:
restart adb kill-server, adb start-server, try rebooting the tablet. also go into storage under settings click the pc connection menu from the 3 dots uncheck ptp/mtp which ever one is checked, in none are checked the device will be in adb only mode check your adb devices again, \

oh wait never mind all that unauthorize all device under debugging and reauthorize, i believe it's what happens if you tell android not to auth the pc connection.
[Dell Venue] kairnage:
Also make sure you have the latest SDK installed or the adb from the latest SDK
[Dell Venue] social-design-concepts:
forgot that one :good:
[Dell Venue] Cookie Ninja:
T'was the SDK. wanted to change locale to en-IN, and didn't have root (obviously), so more locales suggested ADB shell method, and couldn't connect on ADB. Thx guys.

Sent from one of my/our device/s
[Dell Venue] joanthanmajh:
can we try something like this?

androidforums.com/merit-all-things-root/676258-root-update-zip-root.html
[Dell Venue] :
No . Not working
[Dell Venue] bolibo:
Did anybody try this:?

http://hexamob.com/devices/devices-devices/android-rooting-methods-for-dell-venue-8-3830-with-android-version-4-x-jelly-bean/
[Dell Venue] joanthanmajh:
could you elaborate?

---------- Post added at 02:26 PM ---------- Previous post was at 01:39 PM ----------

This was tried back here

http://xdaforums.com/showthread.php?p=48674438&highlight=srs#post48674438

and it failed
[Dell Venue] :
I typed at Dell's FB site . I wonder , what they will reply.
[Dell Venue] jp0555:
They probably won't reply, but I hope it some how convinces them to gives us control of our devices like you said.
[Dell Venue] social-design-concepts:
lol, i knew that when i posted it, i couldn't find jakubekw1997 post. maybe ill post an open letter on their FB page and link it here you all can go and like it.

in the time being maybe see how many likes it can get

https://www.facebook.com/DellHomeUS/posts/10151918586617056
[Dell Venue] jp0555:
Nice 1 like. From me, come on every one else.
[Dell Venue] joanthanmajh:
done
[Dell Venue] jp0555:
I wonder if the Dell guy even knew which venue we are taking about, the Android venues don't even have BIOS.
[Dell Venue] social-design-concepts:
i ranted, they actually do have a bios of sorts, and looking at the droidboot binary with a hex editor droidboot actually disables displaying the efi utility, how we access droidboot is how we would access the efibios if it had a traditional one. its a traditional bootloader we actually don't really use.

droidboot also has tons of references to flashing chome boot images.
[Dell Venue] jp0555:
My bad, but I still don't know if he knew which venue.
[Dell Venue] hunterk11:
Of course he did, he said he owned the v8

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] jp0555:
Yeah that guy knew. I am talking about a thing on Facebook. It is a recent comment on Dell's page.
[Dell Venue] social-design-concepts:
no need to say mybad

---------- Post added at 11:11 PM ---------- Previous post was at 11:09 PM ----------

if any one wants to comment or like i recommend ranting to them. maybe even posting your own.

https://www.facebook.com/DellHomeUS/posts/10151918586617056
[Dell Venue] jp0555:
I read your Facebook comment and was wandering if you tried droidboot over Ethernet or if it would even make a difference.
[Dell Venue] social-design-concepts:
I've not tried yet since the 4.3 update, I have the adaptor but I don't think it make any difference the boot command has an IP address in it so maybe I'll try tomorrow left the addaptor at work.

I'm gonna post some notes tmrw on droidboot and somethings I figured out a couple of days ago,

Under droidboot the rootfile system / is mounted rw but outside of how to push individual files through fastboot to certain locations I've not figured out how to exploit it. Did read a couple things I'm gonna check tmrw in the droidboot source code from android-ia.
[Dell Venue] hellios1:
A word from jcase would be appreciated. Some clue or anything. Try send him PM, maybe he just forgot about us.
[Dell Venue] arclight25:
Liked and posted as well.
[Dell Venue] hunterk11:
Same

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] :
They respond me to look at this in forums .., THEY MAKES THAT DEVICES AND THEY SHOULD TELL US ABOUT IT !!!
[Dell Venue] hunterk11:
If you could restate that or put it in your native language so we can use a better translator that would be great. I understand other languages can be hard, not being an asshole just trying to understand.

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] :
They making these devices and they must know how to root them .....

Wysłane z mojego Venue 7 3730 przy użyciu Tapatalka
[Dell Venue] hunterk11:
Oh yeah, of course, they locked them XD

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] NotQuiteANoob:
after the 4.3 OTA update, here's the new hotmail settings

Correction:

after I got the 4.3 OTA update, here's the new settings that fixed it.

inbox

imap-mail.outlook.com

993

SSL/TLS

Out going

smtp-mail.outlook.com

587

STARTTLS
[Dell Venue] hunterk11:
Lol i just use the outlook app, it supports push and direct exchange

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] NotQuiteANoob:
I originally did the same but I have 5 diff email accounts so combining them into one view in this email client was what I want.
[Dell Venue] maxld:
Guys let's stick to the topic.
[Dell Venue] hunterk11:
I have multiple also, i just forward them all to outlook.

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk

---------- Post added at 06:50 AM ---------- Previous post was at 06:48 AM ----------

Please refer to the answer we gave cline on page 74-75

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] megaghostgamer:
Y'all can't seem to comprehend the rules of threads. Stick to thread title. How hard is it???? If you got a question male a new thread with [Q] in the title. Hope it isn't too hard to do that
[Dell Venue] NotQuiteANoob:
the essence of "comprehending the rules of threads"

So not sure if either of you have been following this thread for long but in the essence of "comprehending the rules of threads" you might want to read this thread from the beginning before you assume something and make an ass of yourself. If you had followed your own advice and obeyed the basic tenant of threads, you would have learned why there are so many "off-subject" posts in here. Basically we are stuck in this one thread while we wait for "root progress" to start moving again and for the forum mods to deem us worthy of our own forum. Notice that we are stuck in Legacy & Low Activity Devices? There was a lot more activity here when we had a developer who actually rooted one V8 4.3 but he got sick or something and took his ball and went home. For unknown reasons, he didn't want to share with the rest of us. Other than social design concepts, it doesn't seem anyone is actively working on rooting 4.3 and I'm afraid this endeavor and the thread will just die from lack of interest.

BTW, my post about email settings that offended you was an update to a comment I had made to a question earlier in this same thread.

Since you are both "senior" members, can you influence the powers that be here at xda to give us our own forum? Do you know enough about rooting that you can contribute to the rooting effort? My opinion is that accomplishing root would rejuvenate some life in this thread and it would naturally refocus on just that topic.
[Dell Venue] social-design-concepts:
if i ever get root i have some theories on how to get the actual boot.img, recovery.img, and droidboot.img off of the devices and a theory on loading a temporary 3rd party recovery and flashing a third party recovery. Dell just replied again. facebook app accidentally deleted my comment ill repost my reply to dell later.
[Dell Venue] megaghostgamer:
No need to use profanity and look ignorant my dear friend. I wasn't directing that towards you either. I've actually been watching this thread for a while and getting notified pathetic post such as this one gets old after a while. Judging me by my tag is ignorant as well because I could have been on a different site. This thread is meant for developers. People should know when and where to post. Another things is I don't need you repeat what has happened throughout the thread. Unlike most others I actually read before making statements. Funny you say we have only one section because I see other threads with [Q] in the title in the general section. THIS MAKES EVERYTHING SO MUCH EASIER AND MORE SIMPLE TO WORK WITH.

I wish I could have made this post through private messages instead of wasting others time to check their device. My apologies .
[Dell Venue] social-design-concepts:
if you don't wanna be notified turn it off, if you notice this thread is under the older dell venue phone thread anyway this device hasn't gotten any other threads yet the couple that do exist all point here. until someone starts a new thread just for devs this is it, and there is no real point to starting a new thread until a root is release, if you don't wanna be notified don't follow the thread and check back when you can. im sure when a root is posted a new thread started the link to the new thread will probably be the last thread posted here and how about everyone just respect each other if you don't like someone's post or have anything constructive to add to the post don't reply and in if somethings been cover and you know where it was covered in the thread link it.

but if you're new here please i know its alot but if you can't at least take the time to read the whole thread skim it at least.
[Dell Venue] cline2:
That's for memo pad 10.
[Dell Venue] chairsz:
jst got my hands on the venue 8 after multiple other tabby returns and other wibesz...

I installed the intel drivers from this post http://xdaforums.com/showthread.php?t=2551863

rebooted both pc and tabby but windows wont show drivers as installed just showing unknown device connected. any workarounds as all? or am I missing something? I installed the IntelAndroidDrvSetup1.1.5.zip version of the driver
[Dell Venue] xdajunkman:
Did you follow the directions there regarding the manual installation of the drivers? It does not work to simply extract the drivers and run the install program.

As for progress on the rooting front...I have the kernel compiled. As for the Android source, my git repo sync hung and had to start over again....back to waiting for the source to download....
[Dell Venue] giveen:
Can someone give superoneclick a try

http://xdaforums.com/showthread.php?t=803682

---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------

BINGO!!!

I need someone to test this one right away!!

http://www.srsroot.com/supported

Dell	Venue 7 3730	TBP706A113200	4.2.2	clo
[Dell Venue] deltatux:
Problem with that one is that the system image is for the 10", it might break the screen sizes and stuff. Plus, will have ASUS bloats and may not have the proper system drivers and binaries no?

I saw that root method but never suggested it because I don't think it'll work.

Now this one looks promising!! However, not sure I can trust the exe...

deltatux
[Dell Venue] cline2:
Tried it on venue 8 8380. Failed! Error: Failed to remount filesystem :(
[Dell Venue] xdajunkman:
Well...some not-so-good news.

I managed to get the kernel compiled and get the appropriate build environment set up. Compiled the Android source according to the directions in the Dell source download, and got a viable ramdisk image. I put the two together to create an insecure boot image. However, it appears that the 'fastboot boot' command is disabled on our device - I get a 'remote boot command stubbed' error when trying to boot from my new boot image. So, I decided to risk bricking my device and flashing my new boot image to the device. That also failed with nondescript error message.

So....I think I have an insecure boot image for the device, but am unable to boot from it or flash it to my device. It seems that Dell has crippled our version of fastboot so that we cannot issue the 'fastboot boot' command.

Giving up for now...will try something else later. I have attached my boot image. I would not recommend that anyone else try and flash this to your boot partition...on the chance that it works you might end up with a bricked device as I have been unable to test it.
[Dell Venue] deltatux:
Could it be that the bootloader is partially locked? I only tried executing:

fastboot erase cache

since that was the safest command, maybe try to see if there's:

fastboot oem unlock

Not sure if that works, but guess it might not hurt?

Also, how did you manage to make an insecure_boot.img? We weren't able to pull the boot partition due to lack of root...

deltatux
[Dell Venue] giveen:
xdajunkman, I'm not quite sure how much experience you have with Android development, but I am telling you, as of right now, kernel does not matter. Achieving root is more important as we need MANY important files that resides in the boot.img on the device, without it, a compile boot.img will fail to boot.
[Dell Venue] giveen:
I'm trying to confirm on twitter about srsroot working with the maker of the tool.
[Dell Venue] xdajunkman:
All fastboot oem commands error with 'unknown OEM command'. I can get some of the other fastboot commands to register, but for the most part it seems that our version of fastboot is pretty useless...or as you pointed out the bootloader is actually locked and fastboot is disabled as a result. It would help if someone else could try a few fastboot oem commands (like 'oem unlock') to make sure that there isn't something wrong with my setup and fastboot binary. If there is no luck with these, then I think that we must assume that the bootloader is locked.

As I have been saying all along, if Dell released the source we would be able to get the boot image. The boot image is made up of the kernel and the ramdisk (which is the root filesystem). We were given the source for the kernel, which I compiled independant of the rest of the source. Dell also gave us the remainder of the code changes they made to make their version of Android for this device. I downloaded the Android 4.2.2r1 source (the branch of the Google AOSP that our OS is based on), inserted their changes, and built the source. This gave me the ramdisk. Putting these two together should have given us a functional boot image for this device. I do not think that the problem is that my boot image does not work...the problem is that the fastboot that is on the device will not even let me try. If the boot image is no good, then the device will simply fail to boot. I can't even get it to try to use my image....the command that would be required ('fastboot boot insecure_boot.img') does not work - it appears that they have disabled the 'fastboot boot' command.

The kernel does matter as per the above. You cannot make a boot.img without the kernel. You cannot extract the boot.img from a device without root. Once other software means are exhausted, you cannot easily root the device without the boot.img (though as it is turning out in this case even having the boot.img is not helping). I don't know if my compiled boot image will work...but it doesn't really matter as it is appearing that we likely have a locked bootloader after all. All of these efforts are aimed at trying to get root....I did not spend the time to download the AOSP source and build the code just to make my own boot image. We have largely exhausted other methods of getting root that are available without some real development skills. If you have such skills to contribute, then please feel free to do so. Otherwise, it seems the largest contribution you have made to the discussion thus far is to take credit for Dell releasing the source for this device.

It seems that we may be down to more advanced methods for getting a shell with elevated priviledges - UART, JTAG, etc. I doubt anyone here is willing to potentially sacrifice their device in order to get root with these means. Unless we can get the bootloader unlocked (or at least fastboot to cooperate), we will need the help of someone with a more advanced skill set. Until then, I think we are stuck. I will keep poking around, but if I can't get root with the source in hand and compiled, then I doubt I will be able to accomplish anything meaningful.
[Dell Venue] giveen:
Dude, I wasn't trying to be critical of you, just making sure you were aware.
[Dell Venue] kwarizmi:
I wonder if the update that most of us received when we first turned on our tablets (Venue 8 in my case) has caused this method not to work.

On the SRSRoot site it claims to support build number YTP801A113200. When I check the build number on my tablet, it reports build number YTP801A113900.

Rats.

Note that I did not try SRSRoot myself, but it seems others have reported it not working for them.
[Dell Venue] giveen:
Can someone try this, its suppose to use a major exploit for almost all devices

http://www.cydiaimpactor.com/
[Dell Venue] deltatux:
That may mean that we need to have someone with an unpatched tablet to try the exploit and then pull the necessary boot.img and etc. to get root working for everyone else.

deltatux
[Dell Venue] xdajunkman:
SRSRoot does not work.

Cydia Impactor does not work.
[Dell Venue] deltatux:
Could be also due to the ARM-x86 incompatibility.

deltatux
[Dell Venue] kwarizmi:
Looking at the Impactor.dat file reveals versions of busybox and su for x86.

However, running BlueBox and SRT Appscanner on my Venue 8 reveals that both the exploits that Cydia Impactor relies on have been patched.
[Dell Venue] N2PC Tech:
I've had no luck with this so far! :eek: