yashsingh1/xdaforums huggingface dataset:
[Dell Venue] social-design-concepts:
what 4.4.3 update ? if there is a new ota i'm going to say don't install let me finish the few bugs in myKIT_BATCH then ill worry about future ota otherKIT

as for warranty the rule of thumb is if you root you should always consider your warranty voided : i will make no claim other wise on the subject.

i am just a simple hobbyist from Cinti. OH USA i have no intention to buy devices or users getting mad that they were under some impression myKIT wouldn't void there warranty

if you root you should always consider your warranty voided
[Dell Venue] n.vk1305:
updating to JB 1.16 gives an error message for 1st fastboot file. rest of all files are flashed successfully and it shows 4.3 after reboot. unable to install v1.25.
[Dell Venue] social-design-concepts:
what device?
[Dell Venue] n.vk1305:
venue 8,trying to update from 4.2.2.
[Dell Venue] social-design-concepts:
Screen shot please need see the about device to see what files I have.
[Dell Venue] n.vk1305:
aftert that it reboots,shows 4.3 when trying to update to v1.25 in tab the android exclamatiom mark appears,and this is prblem while updating to v1.25
[Dell Venue] social-design-concepts:
Make sure you didn't place the folder in a folder containing any white spaces

Try to run the 4.3v1.16 again what is the ifwi droid boot displays.

The second picture the issue is known it shouldn't be preventing the push of the 1.25,update to recovery though I'll have a patch out at some point tmrw I have to finish updating the su installation script first but its bed time now it 313 and I have to be up for work at 7,goodnight all.
[Dell Venue] n.vk1305:
IFWI version in droid boot is f9.6b,good night btw.. :)
[Dell Venue] dk0108:
[MENTION=4299605]n.vk1305[/MENTION] Was your stock firmware v1.42, JB 4.2.2?

I just got my tab and it's saying system up to date. Was gonna try updating using this toolkit.

Edit: I have the V7.
[Dell Venue] social-design-concepts:
What's the IFWI Version? Send me a screenshot of setting about?

if you can hold on, on updating i should have a patch out for the myKIT_BATCH today at some point that should resolve a few of the issues some users were having and with your device being on 4.2.2 i would like to send you a tool to try to capture the 4.2.2 images for the device if a v8 user also has 4.2.2 still please contact me i like to have dumps as far back as possible for both devices...
[Dell Venue] gato06:
I have this

http://s2.subirimagenes.com/imagen/8922058sin-ttulo.png

i need help my android are not start
[Dell Venue] dk0108:
Here it is
[Dell Venue] social-design-concepts:
please attach the pic direct this is too small to read it doesn't look like anything errored out though what version where you on when updating?
[Dell Venue] gato06:
[=social-design-concepts;52824100]please attach the pic direct this is too small to read doesn't look like anything errored out though what version where you on when ?[/]

IFWI Version f9.70
[Dell Venue] social-design-concepts:
i suggest waiting on me to put out the patch and then i'd like to test the jb root method in myKIT to see if it will root 4.2.2 it looks like that version of IFWI might require me to build a tool to update it, seems to be causing issues. well one user reported an issue.
[Dell Venue] social-design-concepts:
everything flashed correctly what version of android were you on before running myKIT? jb4.2.2?
[Dell Venue] gato06:
yes the last update 4.4.2
[Dell Venue] social-design-concepts:
jb4.2.2 or kk4.4.2?
[Dell Venue] gato06:
kk4.4.2 the update are original of dell

I never had update manually
[Dell Venue] dk0108:
Yea sure. :good:
[Dell Venue] eduardito:
I think if you are already in original KK4.4.2 you only need to root with #2 otion??

SDC please correct if I'm wrong

regards
[Dell Venue] kairnage:
If it is not location blocked you can download HERE and install from recovery.
[Dell Venue] Cookie Ninja:
A very weird and surprising issue.

I only wanted to upgrade to KitKat and root device. System upgrade was shown on notified action bar till yesterday. After reading thru all info on upgrade, root and toolkit instructions, I decided on the following action plan. 1 download toolkit and root zip. 2 upgrade using OTA. 3 root using toolkit instructions.

Upgrade downloaded (350 mb approx), toolkit downloaded and installed correctly on PC. On selecting the reboot and upgrade option from taskpane, suddenly, tablet shows that my system is up to date (1.25 jb fw)... I'm in India and I downloaded update 3 days ago when I got the notification in Malaysia. Can anyone help/ explain?

Dead Cookies leave no trails...
[Dell Venue] gato06:
When I try into to recovery

I view a robot android and a red triangle
[Dell Venue] social-design-concepts:
Yes if your on kitkat you only need to root.
[Dell Venue] social-design-concepts:
which upgrade option their are two option A2 jb4.3v1.25 and option A5 kk4.4.2v1.26
[Dell Venue] dk0108:
Press vol + and - together. You'll get the recovery menu. Post your results as i don't have the device with me right now to try it myself. Thanks :)
[Dell Venue] Cookie Ninja:
Ota. It shows that my system is up to date even on 1.25 jb fw. See screenshot. I know I can upgrade using your other zip file, but I wanted to try ota first.

Dead Cookies leave no trails...
[Dell Venue] social-design-concepts:
The OTA is in the otherKIT mine took wipe-data and cache and check after setting up
[Dell Venue] Taroven:
Xposed 2.6+ on 4.3+

So, I did a little checking on Xposed. We actually don't need the custom version as of May 10. Xposed 57+ added a config flag to let devices like the Venue to work without custom builds, which should just need a quick tweak and we're back in action.

I'll be testing this out LATER TONIGHT, so please don't assume it'll work 100% until you've tried it yourself or I've posted an update. I'm short on time at the moment, or I'd test first and post later. :(

Steps for this:

* Update Xposed to the latest version, or install it fresh and be sure to install the framework portion. DO NOT REBOOT YET. (Or if you do, activate safe mode during the boot loop by repeatedly pressing a volume button until it boots successfully)

* If this is a fresh install, make sure to update the Xposed modules list in the installer before proceeding. This will create the directory you're working in!

* Create a text file containing only the numbers "152" (no quotes)

* Save/copy it to /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset (no extension!)

*** Change its permissions and owner/group to the same as modules.list in the same directory (if it's there, otherwise chmod 666 and call it good)

* Reboot and it should work.

* If it doesn't, let me know exactly what steps you took and go back to the build linked above. I'll be working on it soon as I have time. All else fails, I can compile and link the latest version with tweaks for our lovely little tablets. I may just write up a quick app to do this process automatically tonight or tomorrow.

I'll check back in a couple hours and work some magic if I can. Thanks [MENTION=4821597]social-design-concepts[/MENTION] for the amazing work so far! I'm sad that I haven't had time to update to 4.4.2 yet (still on rooted 4.3). Cheers from downtown Cincinnati. :)
[Dell Venue] social-design-concepts:
Your just in my back yard lol
[Dell Venue] Taroven:
Are you sure you're not in mine? :)

Writing the fixer app now, I'll post with results soon.
[Dell Venue] Taroven:
Xposed 2.6+ on 4.3+ - AUTOMATED

Success! I have a working Xposed 2.6.1 on my Venue 7 running 4.3.

I've written a tiny app that fixes Xposed 2.6+ for us. Did it in AIDE and didn't bother with a GUI (or changing the hello world text...) but it'll tell you if anything goes wrong. If it just shows you a SU request and nothing seems to happen, it probably worked. I'll change it up when I have more time to be more informative. Probably tomorrow.

All it does is create a little file that tells Xposed what offset to use for one of the system libraries. You can check for /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset to see if it worked - if it's there, it should read as just 152. This is all we need.

Instructions:

* Update Xposed to the latest version (2.6.1 as of now).

* Make sure you have at least one enabled module. Download and ENABLE ONE if you have none (App Settings is a good one if you haven't tried it)

* Download the attached APK, install it, run it. It's named XposedX86Fix in your launcher.

* Accept the SU request.

* ...Nothing! Seriously. If you don't get a toast saying something went wrong, you're good to go.

* Remember to update your modules before you reboot. :)

If you're stuck in a boot loop from updating Xposed previously, press a volume button repeatedly while the loop is going until Android decides to do its thing. You can use this method to fix it.

Manual instructions:

* See above about updating, making sure there's at least one enabled module in Xposed.

* Copy /data/data/de.robv.android.xposed.installer/conf/modules.list (or any other file you want from the installer tree) to /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset (creating a new file from scratch won't give it the proper permissions or ownership)

* Edit the file, replace contents with "152", minus the quotes.

* Save, reboot, profit.

I'll pack up the app source if anyone wants it. Enjoy!
[Dell Venue] Tornade69:
Is this working also on kitkat?
[Dell Venue] joanthanmajh:
Xposed works without mod in kitkat
[Dell Venue] yizedxl:
You mean that I can install the Xposed framework(2.6.1). And it won't cause bootloop that happened with JB4.3?
[Dell Venue] streak4m3:
GravityBox (KK) module is pretty good too,
[Dell Venue] social-design-concepts:
myKIT_PATCH-v1.0.D

didn't really get anytime to work on anything today but i finished this last night so i figured i get it out

http://xdaforums.com/showpost.php?p=51089990&postcount=1

the patch is in the original post. . .

the patch should fix the issues caused by white space in the folder name and the error caused by cache already mounted when applying update from v1.16 to v1.25.

it also adds some information about what is going on during a couple of the tools jb root-KIT and the v1.16 to 1.25 update

other issues:

it looks like a couple of other issues have come up regarding the update from 4.2.2 to 4.3v1.16 when IFWI version is F9,6B

i have to figure the best way to handle a couple of things so another patch should be out at some point.

if users could please quote in all issues regarding myKIT_BATCH so i can try to resolve them in the next patch.

i also hope to add a function to update the toolKIT with out having to download a patch and manually apply this will hopefully allow me to issue fixes for issues faster after they have be resolved.
[Dell Venue] n.vk1305:
Thank you,will try it and let you know..
[Dell Venue] n.vk1305:
update to jb from on F9,6B has still same error as you mentioned.

after that update jb to v1.25 the following two screens appear then reboots to install that update at 25% of progressbar or so it shows exlamation.

.

the patch you said about F9.6B should fix all these issues,I have a very little knowledge of coding.Iam unable to help you.! :(:(

What all i can do is test these..!
[Dell Venue] social-design-concepts:
i still have to figure the best may to do it, hopefully ill have time to look at it tmrw.
[Dell Venue] Taroven:
Give it a try. If it gives you a boot loop, activate safe mode by repeatedly pressing a volume button while the tablet is booting, then use my tool to fix it.
[Dell Venue] social-design-concepts:
I think he was referring to if your on kk xposed works on kk with out patching.

What devices do you have?
[Dell Venue] Taroven:
Just a wifi Venue 7 (still running 4.3) and my beat up old Razr Maxx. I don't have a computer at the moment, so I have to steal a friend's laptop for flashing. :(
[Dell Venue] social-design-concepts:
gotcha was hoping i found a local v8 users for testing it would be nice to find a local user in cincinnati that could test thinks since i could be able to meet up with them when things go wrong.

glad [MENTION=4221403]kairnage[/MENTION] has been a huge help in the v8 testing and support department thanks [MENTION=4221403]kairnage[/MENTION]. . .
[Dell Venue] kairnage:
The "to many links" error can mean a couple of things. 1 is there are either more than one instance of adb open or more then one device attached to the computer. To make certain that this is not the case the easiest way is to unplug any thing from USB you don't need besides the keyboard and mouse. Then go into device manager uninstall the Venue 8 and unplug it from the computer. move the USB cable to a different USB port and then reboot the computer. When it's rebooted launch the myKIT_BATCH and go to the main menu, reattach the Venue 8 and hit enter to refresh. If the screen goes green then start from scratch.

If that doesn't work try a different USB cable as well. If you are using a laptop use the USB ports on the back, not the side.
[Dell Venue] social-design-concepts:
see the new screenshot

i actually added an explanation informing users that that's actually a normal error during that part that error is actually a good thing and will always happen during that part it's caused when the fastboot service is shutdown and the adb service is started on the devices end nothing to do with the host pc, i could silence the error from being displayed but it helps me with troubleshooting.

ifwi F6.9B has a real legitimate issue i don't have a device with that firmware so i can't tell you what the actually fastboot error is outside of bad command for some reason IFWI:F9.6B will not allow updating the fastboot.img from fastboot, but i'm working out a fix for it now. [MENTION=4221403]kairnage[/MENTION] i was hoping since you're so familiar with the dev-conversion you would test for me when its complete. all the other conditions i need to leverage the root exploit appear to exist from the screenshots the user provided so i'll just need you to check to ensure that it runs all the way through.
[Dell Venue] social-design-concepts:
can you check if the jb root tool will root the device? im debating on doing a full tool for myKIT or just a separate fix but the separate fix would require the device to have root.
[Dell Venue] Android0x309:
Ninja,

I am in the US and had the same experience. I just got my Venue 8 2 weeks ago and got the OTA update notice, but I was watching this thread and decided to wait to update until SDC got the bugs worked out of his kit. So a couple days ago after SDC did a working release with KK included, I pulled the trigger to do the OTA update. The update downloaded fine, and I got a message saying something about needed to reboot to complete the update. So I clicked the accept button (or whatever it said, I was somewhat distracted trying to do this at work), and waited for it to reboot on its own but it never did. I don't know if it was supposed to reboot on its own or not since I unfortunately didn't pay enough attention to the message. So after 5 minutes I just decided that the message probably told me that I had to reboot it myself, so I did. Well it did a normal shutdown and bootup, no updates applied or anything. So I go back into Settings to check the version and it is still at v1.25 (kernel 3.4 I think it was). I have it check for system updates and it is telling me my system is up to date. "No it's not" I reply.

I don't want to distract this thread with troubleshooting why this happened, but I just wanted to say that after a few days of searching forums and not finding any answers I downloaded SDC's kit yesterday and did the KK update (his A5 option) to get me to v1.26. I have 2 programs that won't work, but I think that is a KK issue with the new SD card security. Other than that the KK update via SDC's kit seems to work fine on a stock Venue 8. Thanks SDC!
[Dell Venue] social-design-concepts:
You won't see the update again if OTA fails to install after updating till you wipe-data / factory reset when you update via the ota a flag gets set in a database somewhere in /data informing check for update that you already downloaded and applied it doesn't seem to get unset if the update is unsuccessful so even though all the other flags for searching if a new update is available the update check app doesn't seem to care if the update already appears in the database.

This is just a quick explanation there is more to it but should be enough for users to understand what's going on.

I checked this several times over and over and over again.

But once again now that the root method is out I can't say or not if dell would go back and change the ota's to kill myKIT's ability to root...
[Dell Venue] kairnage:
Just let me know when it's ready
[Dell Venue] Taroven:
Confirmed just now.

Xposed 2.6.1 on KK works without bootlooping and does not need my fix to work. Just install, update framework, reboot.

Not so sure about 4.3. Just use my fix (posted a couple pages back) if you want to update and are concerned about loops.
[Dell Venue] cline2:
Where is this xposed framework?
[Dell Venue] Taroven:
I'd link, but I lurk too much to be able to. Just Google for it. It's not on the play store.

If you mean to ask what I mean by "update the framework", I mean the first item on the top when you open the Xposed installer.
[Dell Venue] social-design-concepts:
my eyes are hurting to much reading. . .
[Dell Venue] eduardito:
I'm in Mexico and get my Venue 2 weeks ago and decide to wait to update to KK until SDC finish the kit (I was in JB 4.3 V2.5), but suddenly on Tuesday the OTA message disappears?? So I went to settings and try to make the update but the message was no need to update?? You have the latest or something like that.

So I decide yesterday to apply the update through the Kit, and everything goes well, later I root the tablet and the same, no problem

SDC thanks a lot for your work this is the best package I ever see !!!!!!!!!!!
[Dell Venue] sic-ever:
[MENTION=4821597]social-design-concepts[/MENTION]

Just thinking. Is it possible to update Venue 8 from 4.3 1.16 (ifwi F9.6B) directly to 4.4 1.26? If 1.26 flashes it's own image of ifwi (to F9.70) so there shouldn't be any problems. Am I right? Or can something go wrong?

Swyped on Venue 7
[Dell Venue] social-design-concepts:
Dell only released patched updates at the park with my daughter I'll explain better this evening.
[Dell Venue] saintii2:
I may need help. Hell, I can't even get it to show up as a adb device from command shell.
[Dell Venue] jmjoyas:
Could you provide me the link to the files please? I would like to try it on my V8.
[Dell Venue] social-design-concepts:
ok, i will only link the file to someone that understands the risk and can handle it on their own. i wont have the time to assist anyone with it until tmrw morning est. if you feel you can do this with out assistance pm me. first come first serve. to the user who i original said i would pm it to if you want them ill still send them to you but i wont be able to assist till tmrw.

the down-loader tool is newer than what dell's instructions show the driver is a little older but does contain the clovertrail+ driver so i suspect should still work.
[Dell Venue] saintii2:
Give it to Jmjoyas. Just keep us updated jmjoyas.
[Dell Venue] social-design-concepts:
you V8 users are so lucky, hope dell does the same for the v7 the files from this partially fixed my softed bricked v7 no display as the files are wrong for my device but it got it out of download mode now, so if dell release these file for the v7 i'll have my venue running again. sucks to have a device that is not dead but the mfg refuses to give you the needed files to restore it to working order.

don't don't don't do this on the venue 7 my device was soft brick because the battery died installing the update for 4.3 i understand this more than the average user so i took a shot to see if it get my device partly working.
[Dell Venue] kairnage:
Aren't those just the dev kit files? I wouldn't think your would need them for fastboot flash.
[Dell Venue] social-design-concepts:
i would suggest trying fastboot flash first, but being the devices are efi the ifwi might turn off signature checking on the kernel. efi wont boot an unsigned kernel if secure boot flag is set in the efi. but yeah try running the p801t_JB4.3_flash_device.bat by its self first. the worst that will happen is you'll need the tools since the batch file re-partitions the device. tools posted below if needed.
[Dell Venue] social-design-concepts:
INTEL-MFG-TOOLS.7z

confirmed working for the v8 users

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

INTEL-MFG-TOOLS.7z

thanks jmjoyas for testing....
[Dell Venue] saintii2:
did he go through the whole thing or just flash the new zip?
[Dell Venue] social-design-concepts:
the whole process i believe. but go ahead try the fastboot flash batch file stand alone if it doesn't work the whole process will fix the device anyway
[Dell Venue] saintii2:
I can't seem to get adb running. it starts and stops instantly. I don't get what's going on.
[Dell Venue] jmjoyas:
"adb shell" gives root directly.

There is no "su" installed. We would have to push one to the device for apps to get root access.
[Dell Venue] joanthanmajh:
Does this delete all your apps and settings?
[Dell Venue] social-design-concepts:
yes everything i still need to post a script for adding su but it gives you root through adb.
[Dell Venue] social-design-concepts:
would you like me to write a script for this. well i have one already can you send me the /etc/install-recovery.sh from the new /system so i dont have to extract it myself?
[Dell Venue] saintii2:
Can someone tell me how to get adb running? I'm not sure if I'm not doing it right or there's something on my computer blocking it.
[Dell Venue] social-design-concepts:
from the original dell fourm

just posted in the original dell forum unconfirmed, wowbro seems to know some one on the in.
[Dell Venue] kairnage:
If you run this without the xfstk it might error out on the boot and recovery images. Not sure why. The system installs but no root access. I think it's a built in safety because if you force flash the boot.img you get stuck in a developer mode with just a USB symbol on the screen. I downloaded a chines version of the app and after some hit and miss I got it wot work. I ran the full instructions from there and it brought the tablet back with root.

here is the new default.prop

ro.com.google.clientidbase=android-dell
ro.sf.lcd_density=213
panel.physicalWidthmm=108
panel.physicalHeightmm=172
ro.opengles.version=131072
gsm.net.interface=rmnet0
persist.system.at-proxy.mode=0
persist.sys.language=en
persist.sys.country=US
ro.secure=1
ro.adb.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.ril-daemon.disable=0
persist.radio.ril_modem_state=1
persist.sys.usb.config=mtp
[Dell Venue] saintii2:
tell me how to pull it and i'll send it.
[Dell Venue] social-design-concepts:
thanks i don't need them now. but need someone to allow me remote access to work out the issues getting su installed.
[Dell Venue] sic-ever:
Sorry, I don't understand you now. What does it mean patched? How is it patched? Is it checking present firmware before updating and if it's not 9.6C it won't let system get an update?

Edit:

Understood. Family is the most important thing ;)

Swyped on Venue 7
[Dell Venue] social-design-concepts:
No it checks the hash of each file boot, fastboot, almost every file in /system, so instead of replacing say boot.img with boot.img it takes current boot.img and patches it to make newboot.img.

So in order for patches to apply it has to patch 1.16 to 1.25 then patch 1.26 in that order you can't go from 1.16 to 1.26 that's why users get error around 25% 1 or more files general boot or fastboot. More explanation later.
[Dell Venue] yizedxl:
thank you, I have installed xposed 2.6.1, and it works fine with V8(KK).
[Dell Venue] n.vk1305:
i have just checked the root for jb v1.16,it worked without any errors.after installation,downloaded the root checker granted it root access. :laugh::)