yashsingh1/xdaforums huggingface dataset:
[Dell Venue] kc12:
v8 32gb

I followed these instructions yesterday. Thanks kairnage. Worked like a charm on my v8 32gb.

I can now access recovery by choosing 'recovery' in the fastboot menu, then using power and vol + on the droid no command screen. Recovery menu then appears.

FYI: quickboot doesn't work for me. But the rebooter in ROM toolbox pro will take me to the droid no command screen, where power and vol + brings up the recovery menu.

Thanks to kairnage and Social design concepts for their time and hard work.
[Dell Venue] kairnage:
I think the Quickboot is the Intel system working slightly differently.
[Dell Venue] saintii2:
well, I reset everything and reinstalled your system image and it's still doing the same thing. "android is optimizing" any ideas?
[Dell Venue] kairnage:
On other hardware this might be a sign of bad NAND. I don't think that is it here. If you flash back another image does it do the same thing? kc12 just flashed it and it doesn't happen. Was you system DEV or stock?
[Dell Venue] Cookie Ninja:
Thanks to downloading and not checking against MD5, I've managed to soft-brick my Dell Venue 7.Screenshots on errors recieved on flashing the stock rooted img file are as attached. Does anyone have any clues as to how I can recover my tablet (rooted or not)? Thanks. Presently tablet boots, shows dell in circle bootscreen and then flashes to black screen for 5 sec and then shows a fallen droid with panel.open and a yellow triangle on top. (failed bootloader screen). Need a fresh IMG to flash or maybe a fresh factory image or RUU.
[Dell Venue] social-design-concepts:
I can assist when I get home. were you on 4.3 or 4.2.2 when you flashed.

Coming from 4.2.2 you have to update to 4.3 and wipe data or it boot loops.

You get droidboot / you get recovery it sounds like / you get boot try fast boot -w to wipedata and cache

Just saw the second error try downloading and flashing again.
[Dell Venue] social-design-concepts:
https://www.dropbox.com/s/wcps27jfjygnwph/rooted_factory_v7_system.img.gz
[Dell Venue] saintii2:
I flashed the Dev rooted system image and it doesn't do it. I did the Dev version. I was wondering if you did the jcase version or if it even makes a difference.
[Dell Venue] kc12:
BTW I dirty flashed as I couldn't get to recovery and didn't know the fb command to wipe cache.
[Dell Venue] social-design-concepts:
not sure whats going on with your flash problems but if you pm my i'll give you my hangouts name and help you the best i can,

:rolleyes: looks like im adding a md5 check verification on the images to the tool kit. sigh and here i thought i was almost done :crying:

some pictures of status check
[Dell Venue] Cookie Ninja:
Last d/l I used was copied from phone, which does not verify MD5. PC /laptop has MD5 verification in downthemall.... I've finally got a MD5 verified rooted img.gz, but now the tablet doesn't get into droidboot mode at all. Power on and the dell-in-a-circle screen comes on, vol +/- does no change to it. USB connect gives unsuccessful connect bell audio and adb devices does not show my tablet.

Sorry S-D-C, no hangouts, no G+ account, never will get one, any other means?

Dead Cookies leave no trails...
[Dell Venue] social-design-concepts:
i gave up on downloading from the toolKIT direct i'm not paying for hosting to have hot-linking / direct-download of the packages,

working on figuring out some checks on validating the package downloaded is for the attached device and that the device meets the minimum requirements for flashing the downloaded package and validating md5 on the images probably check twice.

i probably will include having the toolKIT at least open the download page for the package chosen for the device but the user will have to manually download.
[Dell Venue] social-design-concepts:
you tell me what chat client to use?

unplug from pc, hold power until the dell logo goes away, plug into compter does the charging animation show? if so you should be able to issue adb reboot-bootloader
[Dell Venue] Cookie Ninja:
Will Skype do? I'll pm my name if you say it's ok. Charging animation shows. I'm able to access this screen, wonder what recovery is this? Unable to have adb &lor fastboot commands recognised.....

Dead Cookies leave no trails...
[Dell Venue] social-design-concepts:
that's factory recovery trying to install the ota update and failing because it should verifying on of the files if it is trying to patch is different or not there.

adb reboot-bootloader brought you to factory recovery and not droidboot.img

unplug poweroff, then hold vol down and power to turn on does it go to droidboot???
[Dell Venue] Cookie Ninja:
No Droidboot does not come on. Seems like there is a corruption in some partition in the tablet. wiping data / cache and factory reset has unauthorised adb. see screenshot...
[Dell Venue] Cookie Ninja:
Ok false alarm. Was using vol up with power amd wondering why I am not getting droidboot . Such a klutz. Now droidboot is on and I've successfully flashed root image. Thanks S-D-C. Your help was most crucial. Thx.

I mistakenly let the system auto upfate OTA from 1.19 to 1.25.... Now ive updated on OTA and ROOT has been retained!!!! WOOT!!!!

Dead Cookies leave no trails...
[Dell Venue] hunterk11:
XD

Please quote me in replies.

Sent from Dell Venue 8 with Tapatalk
[Dell Venue] Cookie Ninja:
OK, I've been topping the list of Klutzy posts today.... SU app remains after OTA, SU binary is lost.... Trying to downgrade (Root using rooted image) and update OTA again after using rootkeeper / preserve SU in pro options of Super SU app.
[Dell Venue] social-design-concepts:
i'll be updating the images soon the ota wont take because the boot.img and droidboot.img are patched already just flash the root system again it boots i dont think i have all the images up on the new hosting site yet so you cant flash boot and droidboot and recovery back to pre update yet. just save your self some time and just flash the rooted system
[Dell Venue] Cookie Ninja:
Doesn't work at all. Root IS LOST!. But surprisingly, some busybox commands remain in /system/bin/, /system/xbin/, and /system/bin/.ext. And my modified hostfile also is untouched at /system/etc/hosts.....

so remaining with 1.19 rooted system image.gz, and no system updates this time.....

[MENTION=4821597]social-design-concepts[/MENTION], Can these threads help?

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

and

http://xdaforums.com/showthread.php?p=44239140
[Dell Venue] kairnage:
It was the stock rooted not the dev.
[Dell Venue] social-design-concepts:
I know how to manually update the images I hope to have the toolKIT finished and tested and updated packages up by next weekend.

I'm still searching for a file like that's called in the same manor as install-recovery.sh as this file gets updated with most ota so a fallback script that's call by root would be nice to find as I could have it reset permissions and owner ship of su each time it runs and keep root from breaking I'm hoping to find something that's called by charge mode
[Dell Venue] kairnage:
Now that you have flashing down you can easliy try the deodex push and recover if it fails right? :D:cyclops:;)
[Dell Venue] arclight25:
Anyone else having issues with the galley FC'ing? Just wondering if there was some fix or if I should just reflash
[Dell Venue] Cookie Ninja:
[MENTION=4221403]kairnage[/MENTION],

Wait awhile, I'm off on vacation for two weeks from tomorrow. Freaked out when I soft bricked it yesterday, coz it was to be one of our connectivity/entertainment hubs.... No PC (I'm texting from the airport right now...) Will try in second week of may, OK?

[MENTION=985779]arclight25[/MENTION],

Never used the stock gallery app. Quickpic, and disable gallery, unless it is linked too camera, like in AOSP ROMs.

Dead Cookies leave no trails...
[Dell Venue] hunterk11:
It is linked to the camera

Please quote me in replies.

Sent from Dell Venue 8 with Tapatalk
[Dell Venue] kairnage:
HA HA! I was more teasing then being serious. So far it appears not a lot of people are concerned about deodex so no rush.
[Dell Venue] social-design-concepts:
Send me the link and I'll test the only issue with deodex is it breaks the otas but I'll test and link them in the package section for others to see
[Dell Venue] sic-ever:
Hey, what is the ETA of your toolkit? Because I'll have to send my Venue on warranty due to LCD defects. Unfortunately I have some brighter blurry spots on screen.

Swyped on Venue 7
[Dell Venue] hunterk11:
Root, or the Dev image has broken encryption. Not sure which, just giving a heads up.

Edit.

I also solved the keyboard reseting on reboot problem. Paid apps are now stored in /mnt/asec instead of /data to allow their encryption. This directory isn't loaded on boot so it defaults back to the factory settings. Moving the app to phone fixed the issue.

Please quote me in replies.

Sent from Dell Venue 8 with Tapatalk
[Dell Venue] hunterk11:
This gives me an error, says it cant load the file then says no error.:confused:
[Dell Venue] kairnage:
Can you give the full error. I just tested this on a fully stock and it flashed with no issue.
[Dell Venue] hunterk11:
Says can't load file, that's all

EDIT:

error: cannot load '<name>': No error

Where should the file be located, I've tried the SD card and the device

Please quote me in replies.

Sent from Dell Venue 8 with Tapatalk
[Dell Venue] kairnage:
The file should be on your computer, preferably in the folder where your fastboot.exe is located unless it is pathed correctly. The instructions are the same as in the first post of the thread.
[Dell Venue] hunterk11:
Ok so I got it flashed but I went back to the stock image because themes did not work, but now on every boot it does some Android is upgrading thing, even though I re-flashed the stock boot image.

Please quote me in replies.

Sent from Dell Venue 8 with Tapatalk
[Dell Venue] kairnage:
Try going into recovery and deleting cache. if that doesn't work a factory reset.
[Dell Venue] hunterk11:
Deleting cache didn't work and I don't feel like the hassle of a data wipe so I guess I'll live with it.

Please quote me in replies.

Sent from Dell Venue 8 with Tapatalk
[Dell Venue] kairnage:
another user reported something similar but going the other way. to a custom from stock. It 's probably just a hink in the flash process. Like you get with Allwinner and Livesuit once in awhile.
[Dell Venue] eduardito:
Social-design

I'm waiting until you release the root version for the regular user in the mean time I would like to ask you some questions:

I have a venue 8 with 4.2.2 version, should I keep this version or I can update for the 4.3?

When I root the tablet I'm going to lose the installed applications and need to reinstall it again?

Thanks
[Dell Venue] hunterk11:
It is for the regular user...?

Please quote me in replies.

Sent from Dell Venue 8 with Tapatalk
[Dell Venue] joanthanmajh:
Dell Update

Dell updated the dev files last night

http://opensource.dell.com/releases/venue8/developer-edition/

they also posted a changelog and added a "venue8_version-1.22-ota-signed_full_rooted.zip to update system from sdcard"
[Dell Venue] social-design-concepts:
I'll check them out tonight....
[Dell Venue] jp0555:
I have been busy and stuff so I haven't tried to root since the end of March. I looked at the latest instructions from dell and it looks like you don't need to do all the xfsk stuff and you can just flash a rooted ROM from the sdcard. Not sure if this is correct. Any ideas on this?
[Dell Venue] kairnage:
I haven't tried it yet but downloaded the files and looked at them. The zip is a signed update for recovery. to root and unlock the bootloader. The new instructions actually have the OTA first, then the dev tool as an unbricking option.
[Dell Venue] jp0555:
Well I downloaded it and it booted up with the android updating thing. I looked in settings for a supersu setting like in cm and didn't see anything and downloaded supersu and it said no such bianry, but it may unlock the boot loader.
[Dell Venue] social-design-concepts:
Dev-Edition only gives you adb root access you still have to manually root the standard image. I'll check it out this evening.
[Dell Venue] jp0555:
Ok. Does that mean I need to flash one of the prerooted roms in this thread? And if I do, do they wipe data?
[Dell Venue] social-design-concepts:
Looks as if Dell just packaged the dev conversion as an update installable through recovery so you can just flash through fastboot the rooted Dev edition system image in the package I provide in post 2.
[Dell Venue] darklordofthesith:
Turned on my tablet and there's an update. I'm hesitant to download it.
[Dell Venue] hunterk11:
I updated, no clue what it was for though, working fine

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] darklordofthesith:
I downloaded it too. No difference. But I took pics of the droidboot screen to see if there is any difference.
[Dell Venue] jayjr1105:
Any way to know if this ota update will break root?
[Dell Venue] social-design-concepts:
sorry to bother you on so many places get me the update and ill find out for you.
[Dell Venue] :
People ! Theres some update that has 6.8 MB of weight . installing , hopefully ITS root package

Wysłane z mojego LG-OPTIMUS-L5-E610/612F przy użyciu Tapatalka
[Dell Venue] hunterk11:
…try reading others post before posting please…

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] :
Well , i wonder why it reboots many times when updating

Wysłane z mojego LG-OPTIMUS-L5-E610/612F przy użyciu Tapatalka

---------- Post added at 08:22 AM ---------- Previous post was at 08:22 AM ----------

I had hope it will be KitKat

Wysłane z mojego LG-OPTIMUS-L5-E610/612F przy użyciu Tapatalka
[Dell Venue] hunterk11:
For the love of god…

Please quote me in replies.

Sent from Dell Venue 8 3830 using Tapatalk
[Dell Venue] maxld:
Please stop spamming DEV thread.
[Dell Venue] :
Im not spamming

Wysłane z mojego LG-OPTIMUS-L5-E610/612F przy użyciu Tapatalka

---------- Post added at 11:24 AM ---------- Previous post was at 11:06 AM ----------

I modifed update-binary basing on dell update script . will try to add it as first lines in update-binary and updater-script of super su package ... There is the code ...

mount("ext4", "EMMC", "/dev/block/mmcblk0p8", "/system");

assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "dell/Tablet7/thunderbird:4.3/JSS15Q/ eng.XYX.20140226.114853:user/release-keys" ||

file_getprop("/system/build.prop", "ro.build.fingerprint") == "dell/Tablet7/thunderbird:4.3/JSS15Q/ eng.XYX.20140226.114853:user/release-keys");

assert(getprop("ro.product.device") == "thunderbird" ||

getprop("ro.build.product") == "thunderbird");

Wysłane z mojego LG-OPTIMUS-L5-E610/612F przy użyciu Tapatalka
[Dell Venue] chunkybudz:
sorry if this is a useless post. thanks to everyone working on the root issue.

just wanted to ask if it was useful to volunteer my venue as a guinea pig? it's really not much use to me unrooted, and i won't exactly miss it if it's fried. i'm not offering to send it anywhere, but am willing to destroy it in any way that leads to the golden land of root.

i am not a dev, but am knowledgeable and far from stupid. i can follow instructions and report detailed results.

running 4.3 and have NOT installed the update that appeared yesterday.

thanks again to the smart guys doing the real work. it is greatly appreciated.
[Dell Venue] social-design-concepts:
is yours 16 or 32, i already have a user i'm sending the rooted_system.img to i just have to prep it for him tmrw, if you're willing to try as well pm me and ill send it to you too.

im hoping jay will upload the new update for me to inspect.
[Dell Venue] chunkybudz:
16 and pm sent
[Dell Venue] kibuuka:
There's an update for venue8 on opensource.dell.com

http://opensource.dell.com/releases/venue8/developer-edition/

it has two main files - archive containing firmware that's pre-rooted (according to installation instruction) and updated kernel source archive.

diff -r between kernel source trees from P801-P706_OpenSource_V1.32.zip and one included in this release produces 4mb patch, so there seem to be changes :)
[Dell Venue] chunkybudz:
Files dated the 24th and instructions dated the 26th with a big warning about losing warranty with install. Did they give us what we wanted?
[Dell Venue] Cookie Ninja:
Those files are from the Venue 8 directory. Any help for us venue 7 users?

Dead Cookies leave no trails...
[Dell Venue] saintii2:
Am I reading that right??? Did Dell just give us root????
[Dell Venue] joanthanmajh:
Is anyone trying this?
[Dell Venue] chunkybudz:
I haven't tried it. Waiting on smart people to tell me what to do.
[Dell Venue] kairnage:
It's actually fully rooted. You don't need su or superuser to change anything. If you open a terminal emulator or adb shell it defaults to su/administrator. But some apps require su/superuser to work properly.
[Dell Venue] social-design-concepts:
Saying its fully rooted isn't accurate it gives you root access via a shell adb / terminal emulation for debugging and development but to be fully rooted for android you have to have su and a superuser /superSU app to handle permissions.

Thinking about it more the way the dev edition provides root is probably a high security risk as any app that can execute shell code has administrative full access to the system with out you having to grant the app permission.
[Dell Venue] Sportfreunde:
Sorry I'm a bit confused about how you root the updated 4.3 for Venue 7 listed in the OP. I've rooted before but haven't used the programs listed here so are there instructions anywhere through this thread on rooting that version of the tablet? Thanks

Mainly just don't understand which instruction apply to 4.3 and which to 4.2 and how to use ADB/Fastboot to point Windows to install the drivers downloaded from here.
[Dell Venue] N2PC Tech:
SU

Has anyone installed SU for the Dell Venue 8 yet?:good:
[Dell Venue] social-design-concepts:
The images provided in this forum have it pre installed. So I guess the obvious answer is yes.
[Dell Venue] Sportfreunde:
Is there a youtube video on how to do this? I'm having trouble figuring out what to do to root the V7 4.3 following the OP and what to do before what as well as how to install the drivers since Device Manager doesn't let me do it or I'm using it wrong.
[Dell Venue] hunterk11:
I would suggest waiting till SDC has finished his toolkits then use those.

Please quote me in replies.

Sent from Dell Venue 8 with Tapatalk
[Dell Venue] social-design-concepts:
it's about done im trying to work out a couple of little bugs still, plus a couple of issues with packing the system image with make_ext4fs something seems to break root when i flash after packing them with this. :confused:
[Dell Venue] hunterk11:
[MENTION=4221403]kairnage[/MENTION] do themes work for you on the deodex version?

Please quote me in replies.

Sent from Dell Venue 8 with Tapatalk
[Dell Venue] kairnage:
I don't use an app, I have been kind of making one on my own. I have swapped the font and some graphics in the framework-res.apk. I haven't gotten around to the systemui yet.
[Dell Venue] kairnage:
Just send me the link, been waiting on you :)
[Dell Venue] social-design-concepts:
lol you were getting the link even if you didn't want it lol.
[Dell Venue] kc12:
v1.25

I'll try it.
[Dell Venue] death-people:
can you send me ? i'm v7,i like update system .:laugh:
[Dell Venue] joanthanmajh:
I can test too
[Dell Venue] social-design-concepts:
It seems my root script didn't root correctly going to have to reroot them when i get off work and then upload them again sigh......
[Dell Venue] hunterk11:
Thanks again for all your hard work SDC

Please quote me in replies.

Sent from Dell Venue 8 with Tapatalk
[Dell Venue] phlyphish:
I'm in the same boat as Cookie Ninja. My V7 was rooted, then I accepted (didn't mean to) the last OTA update and lost root. But now because of leftover root files (Busybox, etc. in /system/bin/, etc), I can't get ADB to connect to my device.

I did try, using droidboot, to boot into recovery, but got the android logo on his back with his stomach open and a triangle with a caption that says no command. However, ADB would then connect and show the device id, but says it's unauthorized and won't allow any commands. I also tried Cydia Impactor but got the same results.

Any ideas on how to proceed from here would be greatly appreciated. I'm thinking that if I could get rid of the busybox files in /system/bin that adb would allow the connection, but I'm no expert, and deleting from system requires root (as far as I know).

Any other way to delete from system? Or any other suggestions on how to get root back?

Help!
[Dell Venue] joanthanmajh:
cant you just reflash the rooted system image?
[Dell Venue] phlyphish:
Well, pretty sure I said I can't get Adb to connect. If there's another way to flash the rooted image, I'll be all over it.
[Dell Venue] social-design-concepts:
Power off power on holding vol down and power should boot to fastboot for flashing.
[Dell Venue] phlyphish:
First off, I want to say thanks SDC for all the work you've done on this root method. I rooted easily the first time I tried it. Thanks again.

And yes, volume down + power does boot to fastboot. Then the first instruction in the OP says "adb reboot-bootloader".

So Adb is required to get started, correct? I can't run fastboot commands if Adb won't connect, correct? Am I missing something here?

Just to be clear... when I say Adb won't connect, I mean that when I run "adb devices" (in fastboot/droidboot mode), it says no devices found. So it fails when I try to run "adb reboot-bootloader". i.e. Adb is not finding the device in fastboot/Droidboot mode. I've reinstalled the adb drivers six times so I'm sure that's not the problem. USB debugging is on. Remember, I already rooted once, nothing has changed since then except for the OTA update.

Because the device is no longer rooted, AND there are "non-factory" files in the system image, i.e. busybox for one, the ROM is not recognized as an "official" system image and so I'm guessing that's why adb won't connect. It's the same problem that cookie ninja was describing in the post I quoted earlier.
[Dell Venue] social-design-concepts:
From droidboot mode you use fastboot commands to flash not adb commands. You should also be able to install the driver while in fastboot command. fastboot flash system image-name.img.gz
[Dell Venue] phlyphish:
Then why do the instructions in post 1 say to get into fastboot mode and then run "adb reboot-bootloader"?
[Dell Venue] social-design-concepts:
Because it does, but you can also boot into droidboot with the volume down and power.
[Dell Venue] phlyphish:
Well, again, I'm no expert, but I assumed that if adb wouldn't connect then neither would fastboot (in fastboot/droidboot mode).

Nonetheless, when I boot into fastboot and try to flash the root image, i.e. "fastboot flash system rooted_factory_v7jb4.3_system.img.gz", it just hangs with the message < waiting for device >. On the V7 it says, "FASTBOOT CMD WAITING". Pretty sure it'll just sit there forever like that.
[Dell Venue] social-design-concepts:
Look for an unknown device in device manager I assume the driver is messed up.
[Dell Venue] phlyphish:
Hey, problem solved. It was a driver issue. But strangely weird.

I had updated the Android ADB Interface driver with the files downloaded from Post 1 (dell_adb_driver.7). After update, the Driver Date was 7/9/2013, Driver Version: 8.0.0.0, which seemed correct. However, after your most recent answer to my posts, I uninstalled that driver and windows ended up installing an older driver, dated 8/11/2009, Driver Version: 2.0.10.2.

I decided to try flashing with that driver and "adb devices" found my device and I was able to reflash the root image. After that, just for kicks, I updated the driver again to the more recent driver from the dell_adb_driver.7z file. Once again, adb and fastboot wouldn't connect to my device.

Doesn't make sense to me, but the old driver made the connection and I was able to reflash to the root image.

Thanks again for pointing me in the right direction.