yashsingh1/xdaforums huggingface dataset:
[Dell Venue] vampirefo:
Depends on device, 3830, 3840 can install recovery. Most likely 3740 could also, but never tried it on a 3740 tablet.

Any device with an unlockable bootloader should be able to install a custom recovery.
[Dell Venue] lap770:
help

But the recovery.zip file u provided does not contain any .IMG file in it like a normal recovery .zip has so how to install it? sorry for my bad english
[Dell Venue] vampirefo:
I have made 5 installable recoveries for 3830, 3 CWM 2 TWRP, the TWRP recoveries aren't for share at this time.

I have also made a CWM recovery for 3840 which isn't for share either.

If you have a 3830 you can use any of the 3 recoveries I share.
[Dell Venue] lap770:
thanks vampirefo

Will the 3830 cwm recovery work for my tablet I have digiflip pro xt901 Intel atom z2580 2gb ram but your temp recovery works on my tablet so I think it should work?
[Dell Venue] vampirefo:
My flashable recoveries are only designed for their target, will not work for your device, you can unpack and repack 37 recovery only for your device, the other two recoveries aren't meant for any other device.

None of the recoveries can be flashed on your device as is, your device can't boot a dell kernel.
[Dell Venue] lap770:
Thanks For Your Advise

If possible can u make a recovery for my tab?
[Dell Venue] vampirefo:
Could I make a recovery for you? Well yes I could, but I wont I only make recoveries for devices I own, You would need to make your own.
[Dell Venue] aptom:
Just to report that this method with trigger 3 works perfectly for the Asus Zenfone 2 ZE500CL.

Thank you very much vampirefo!
[Dell Venue] edtechguy:
Thank you for posting a Linux guide. I really appreciate it.

After downloading and examining the contents of the directory, I have a question: Does this process install a super user app as described in the guide below? I'm trying to understand *why* this will work before I try it out.

How to root Android using Ubuntu

http://www.rojtberg.net/668/how-to-root-android-using-ubuntu/
[Dell Venue] vampirefo:
It just simply extracts the supersu zip file to system, and sets permissions.
[Dell Venue] edtechguy:
[MENTION=2472806]vampirefo[/MENTION]

Thank you. I realize it's a beginner question but I appreciate the quick response.

I've another beginner question that I'm working on:

I've successfully extracted the contents of the zip file you posted on the first post and installed android-tools-adb. I'm running a pretty plain version of Xubuntu 14.04 LTS. But when I run any of the

sudo ./trigger

commands, I get the following:

will@will-xubook:~/Desktop/CWM$ sudo ./trigger 1
Using Trigger 1
./fastboot: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
./fastboot: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
./fastboot: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
./fastboot: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

I've checked and confirmed that

libstdc++

is installed. But the ".so" or "shared object" file doesn't seem to be found. That said, I haven't run

find

on that file yet, mostly due to the fact that I'm unsure of how to form the command properly.

Do you have any troubleshooting advice? What should I investigate next?
[Dell Venue] vampirefo:
Looks like your Linux isn't setup correctly, try this fastboot if it doesn't work you will need to setup your Linux correctly to use 32bit files.

https://www.androidfilehost.com/?fid=23991606952610517
[Dell Venue] edtechguy:
[MENTION=2472806]vampirefo[/MENTION],

Thanks. I tried the alternate fastboot file but it made no difference: I still got the same errors.

But more importantly, I didn't realize that the scripts and executables required a 32-bit system (mine is 64-bit). But there seems to be a wealth of information out there describing how to achieve this (see https://www.google.com/search?clien...les+on+64-bit+system+ubuntu&ie=utf-8&oe=utf-8). Hopefully, making a few adjustments like this will help.

Thanks again.
[Dell Venue] vampirefo:
Doesn't require 32bit OS, my Linux is 64bit, requires 32 bit libraries. Just boot a live Ubuntu OS and you will be good to go from live Ubuntu you can run these scripts., your OS is too stripped down, not up to 64bit par.

Or you can install 32bit libraries on your device and scripts will work.
[Dell Venue] edtechguy:
[MENTION=2472806]vampirefo[/MENTION]

I was able to run the

sudo ./trigger 3

after following the steps here to get the necessary libraries:

http://askubuntu.com/questions/454253/how-to-run-32-bit-app-in-ubuntu-64-bit

Perhaps Xubuntu 14.04 is, as you say, "stripped down".

But now, I realize that I'm not quite certain of what do do. Here's what I've done:

will@will-xubook:~/Desktop/CWM$ adb reboot bootloader
will@will-xubook:~/Desktop/CWM$ sudo ./trigger 3
Using Trigger 3
sending '/tmp/recovery.zip' (3477 KB)...
OKAY [ 0.575s]
writing '/tmp/recovery.zip'...
OKAY [ 0.639s]
finished. total time: 1.214s
sending '/tmp/recovery.launcher' (469 KB)...
OKAY [ 0.462s]
writing '/tmp/recovery.launcher'...
OKAY [ 0.594s]
finished. total time: 1.056s
sending '/sbin/partlink' (158 KB)...
OKAY [ 0.450s]
writing '/sbin/partlink'...
OKAY [ 0.593s]
finished. total time: 1.043s
...
(bootloader) Stop partitioning

OKAY [ 0.599s]
finished. total time: 0.599s
will@will-xubook:~/Desktop/CWM$

After seeing that, I chose to reboot in "recovery mode". Is this correct? If so, I'm not sure what do do next. Here are the options on my phone (Zenfone 2 z500cl):

Reboot system
apply update from ADB
wipe data/factory reset
wipe cache partition
apply update from microSD

Please note that I do not have a microSD card installed yet.

I appreciate your persistent and helpful advice, sir!
[Dell Venue] vampirefo:
You don't do anything wait for recovery to start on it's own.
[Dell Venue] edtechguy:
[MENTION=2472806]vampirefo[/MENTION]

Ah! Thank you. Didn't realize this would happen automatically. How long is the wait? Should I be concerned after a certain point?
[Dell Venue] vampirefo:
I don't have your device, so can't say how long, should start with in a minute, you should see text stating recovery is installing, once install recovery starts, if haven't started by now something is wrong.
[Dell Venue] edtechguy:
[MENTION=2472806]vampirefo[/MENTION]

Thanks. After running the triggers for 1, 2, and 3 in sequence, it rebooted into the CWM recovery. Everything seemed to be installing correctly although I didn't have time to read all of the text as it scrolled past. I chose the option to "reboot now" and it presented the option to "root", which I also chose. But upon reboot, I checked root status and the app I used "Titanium root" said that root hadn't been given. Not sure what might have gone wrong but I know at least one other person has succeeded using your tool and trigger 3.
[Dell Venue] vampirefo:
You have to choose no, yes unroot device, boot into cwm recovery install super user zip, reboot system select no.
[Dell Venue] edtechguy:
[MENTION=2472806]vampirefo[/MENTION]

Thanks for your help. Although I have no trouble getting to the CWM recovery interface, I'm unable to enter the instructions you posted:

The sequence of "no" and then "yes unroot device" seem impossible to carry out without rebooting the device in between those steps. I'm sure I'm missing something though.
[Dell Venue] vampirefo:
Select no, not yes

You said you selected yes that is wrong select no.

Start cwm install supersu zip, reboot to system, when ask yes or no question select no.
[Dell Venue] edtechguy:
Ah! I get it now. Upon reboot of the actual system, select no when I'm asked a "yes/no" question. That makes sense.

The only part I'm struggling with now is actually getting the superuser file,

UPDATE-SuperSU-v2.46.zip

copied. After I run the triggers, I can't run ADB operations anymore. Perhaps I should copy it to root

/

first? Note that I do not have a SD card to copy to.

UPDATE 5/27:

I was able to successfully root my Zenphone 2 ZE500CL using the trigger #3.

[MENTION=2472806]vampirefo[/MENTION], thanks for your help!

Now that my device is rooted, should OTA updates be avoided?
[Dell Venue] dawgdoc:
I can't really say for the ZenPhone, but OTAs unroot my Acer A1-830 tablet.
[Dell Venue] vampirefo:
Regular OTA should be from fine, you will need to reroot after OTA.
[Dell Venue] jerbear294:
As a precaution you may want to use Survival Mode. On my MeMO I use RootZenfone's Survival and SuperSU's Survival mode in conjunction. No OTA has removed root thus far.
[Dell Venue] jerbear294:
Do you think you could incorporate T4 into this [MENTION=2472806]vampirefo[/MENTION]? My MeMO updated to Lollipop and the other triggers don't work anymore.
[Dell Venue] brackenhill_mob:
Tesco Hudl2 success!

Works perfectly when you edit the trigger script and insert

-i 0x1d4d

after every fastboot command

HTH
[Dell Venue] vampirefo:
I will add it this weekend.
[Dell Venue] vampirefo:
I have updated trigger script to include trigger 4.
[Dell Venue] social-design-concepts:
[MENTION=2472806]vampirefo[/MENTION] so haven't tested yours yet but building against cm-11 everything works except adb sideload just like in cwm guess I'm going to test yours the finish the script for the the theming.

On a side note twrp really needs to update to a newer minui the newer version not dependent on libpixelflinger really is so much smoother and faster.
[Dell Venue] vampirefo:
Mine is built off of cm12 you think cm11 is better to build from?
[Dell Venue] social-design-concepts:
If I build off cm-12.1 I get errors with adbd libc text relocation errors and linker errors so cm-11 is the only way I get working adbd.

Testing yours when I get home had to run out, I tested a few other build all seem a little laggy compared to the arm build on my lhkne adding Intel's libenc helps but still laggy, displaying the log seems to hang too.
[Dell Venue] cgf:
How is the UPDATE-SuperSU.zip file created?

Out of curiosity, how is the UPDATE-SuperSU.zip file created? If wanted to use another SU utility, how would we go about creating the .zip?

I assume that it has to be internally signed and isn't just a plain-old .zip file.
[Dell Venue] vampirefo:
Plain old zip, this is chainfire's su, I didn't create it he did.
[Dell Venue] cgf:
Sorry. I should have realized from the first post that this file is created by someone else. Feel free to ignore.

---------- Post added at 01:51 PM ---------- Previous post was at 01:49 PM ----------

My reason for asking was that Chainfire's zip has a signature at the end that I would like to know to duplicate. It doesn't show up if I just

run "zip".
[Dell Venue] vampirefo:
The signature does you no good, but you can ask chainfire in his thread.
[Dell Venue] captainmidnight:
Hi vampirefo are you able to make any additional TWRP recovery images of different screen resolutions?

Currently use the tethered CWM recovery on the hudl2 - nice work.:good:

Screen resolution required 1920x1200?

---------- Post added at 04:49 PM ---------- Previous post was at 04:27 PM ----------

Sorry forgot to say, your original TWRP builds work on the hudl2, it would be nice to have a version with a bigger native screen configuration - although the original builds due scale.
[Dell Venue] social-design-concepts:
twrp only has 5 themes now hdpi portrait / landscape mdpi portrait / landscape and watch.

1920x1200 would use hdpi either portrait or landscape depending on the orientation droidboot is displayed.

Even if you spec a device resolution in the BoardConfig.mk twrp build logic will pick one of the 5 themes. As you pointed out they now rely more or scaling the resolution spec themes. If you want something more specific for a device you have to build your own theme.
[Dell Venue] captainmidnight:
Thanks for the info - I see now. It's changed a bit since I last played about with TWRP on a 3188 tablet.

The supplied 800x1280 portrait version scales well and is more than usable. :o
[Dell Venue] vampirefo:
Yes screen sizes are limited.
[Dell Venue] AC DC:
[MENTION=2472806]vampirefo[/MENTION] i have successfully compiled twrp but i don't understand one thing ,how you made a updater script and binary , i know i can borrow them from yours, but i want to learn how to make them on my own like you did ,please help .
[Dell Venue] vampirefo:
Depends some update script are writing by hand others are just copy and paste, same with binary file, it can be made on cm11 and below by build recovery.zip instead or recovery.img also the binary can just be copied from any Intel zip.
[Dell Venue] afaquekhaja:
Will this work on dell venue 7 3740 and can anyone confirm it working?
[Dell Venue] vampirefo:
Yes it will work.
[Dell Venue] afaquekhaja:
This isn't an actual cwm or twrp recovery right?
[Dell Venue] vampirefo:
Your post doesn't make any sense, what do you think this thread is for ice cream? No it's for rooting intel tablets with either twrp or cwm recovery.

Your best bet is to use sdc windows version, or just not root your device, might be the best, rooting is not for everyone.
[Dell Venue] danieljamie:
Do you know how to make it a permanent recovery instead of tethered? (I have a Tesco Hudl 2).

Are there any terminal commands I can run to provide/learn more info on this device?
[Dell Venue] vampirefo:
Permanent recoveries are different, than tethered recoveries. You have to unpack stock recovery correctly and replace files with twrp or cwm and repack correctly then flash to device.

I do have two intel devices with permanent recoveries.

http://xdaforums.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165

http://xdaforums.com/dell-venue/general/carliv-touch-recovery-dell-venue-8-3830-t3012007

http://xdaforums.com/dell-venue/general/dell-venue-8-cwm-unsecure-boot-recovery-t2866925
[Dell Venue] danieljamie:
Thanks for this. Is there a way to check for locked/unlocked bootloader on an Intel Hudl 2 device? I don't want to brick it..

I have found the partition names and locations:

lrwxrwxrwx root root 2015-06-25 15:01 ESP -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-06-25 15:01 boot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-06-25 15:01 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-06-25 15:01 config -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-06-25 15:01 data -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-06-25 15:01 factory -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-06-25 15:01 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-06-25 15:01 logs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-06-25 15:01 misc -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-06-25 15:01 panic -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-06-25 15:01 recovery -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-06-25 15:01 reserved -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-06-25 15:01 reserved_1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-06-25 15:01 rom -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-06-25 15:01 system -> /dev/block/mmcblk0p13

Am I correct in thinking I would need to unpack the recovery which is /dev/block/mmcblk0p4 which I can get via:

dd if=/dev/block/mmcblk0p4 of=recovery.img ?

Do mkboot tools work on recovery? I guess I can research unpack/repack recovery as long as it is compiled for Intel.

Thank you for helping me.
[Dell Venue] afaquekhaja:
I'm sorry, I had no idea about tethered cwm. Thought this is normal cwm. Apologies!
[Dell Venue] vampirefo:
You can't use permanent recovery on a 3740 or 3730 they have locked bootloaders.
[Dell Venue] afaquekhaja:
Ok. Actually my device is refusing to boot into stock recovery. When I try to touch and hold power and vol down button the tablet doesn't boot into recovery instead boots into android system.
[Dell Venue] vampirefo:
You should pull both recovery.img and boot.img from device, also capture any updates for your device, to help determine if bootloader is locked.
[Dell Venue] vampirefo:
That sounds normal, volume up plus power should get it to fastboot, from there select recovery.
[Dell Venue] danieljamie:
I have boot.img and recovery.img and also someone on Modaco uploaded a recent update.zip here: Dropbox Link

What can I do now to check if bootloader is locked/unlocked?
[Dell Venue] mole62:
Having some issues rooting a Hudl2... added the vendor id code as recommended by brackenhill_mob, and used trigger 3. Used the twrp_i700_recovery.zip.

All appeared to go well, but the Hudl2 doesn't appear to be rooted, I can't push any files to /data/apps or even read the directory - permission denied.

Tried using the cwm recovery zip with trigger 3, which failed.

Repeating the process with twrp_i700_recovery.zip runs OK - apart from a FAILED message, which I assume is just losing the connection *after* the script has finished?

>writing '/sbin/partlink'...

>OKAY [ 1.168s]

>finished. total time: 2.056s

>...

>(bootloader) Stop partitioning

>

>FAILED (status read failed (No such device))

>finished. total time: 5.943s

but when I try and install the SuperSU zip the device just hangs.

The error messages shown are:

Could not mount /data and unable to find crypto folder

Unable to mount /data

Unable to mount /cache

My build is 201550529.110309, would I need a different recovery.zip file - maybe I need to use one extracted from IntelAndroid-FBRL-01-17-2015 mentioned in this (Windows-only) thread? http://www.modaco.com/forums/topic/375250-easiest-way-to-root-hudl-2-running-latest-updatesoftware/

Is there any great risk in just trying that recovery file (or a newer version)?

Any info appreciated,
[Dell Venue] mole62:
Tried the recovery.zip file from the other thread, CWM starts, but trying to install SuperSU just displays:

-- Installing /extenal_sd/SuperSU246.zip

Finding update package....

Opening update package...

and then just hangs.

I've cleared plenty of free space (2.0GB) and run fsck on the SD card.
[Dell Venue] vampirefo:
Try another sdcard, in cwm mount sdcard is there any error? something about your sdcard the recovery doesn't like.
[Dell Venue] mole62:
Yes, you're right! Even though fsck'ing the SD card showed no errors, and the card mounted OK in CWM, the SuperSU zip installed from the Hudl2's internal memory first time and it's now rooted :) Thanks for all your work!
[Dell Venue] vampirefo:
Recoveries have been updated.

Change log 7-31-2015

Twrp has been updated to 2.8.7.0

This version includes [MENTION=4821597]social-design-concepts[/MENTION] latest trigger (fbrl.trigger) and launcher (recovery.launcher), Also included is a script for Tesco Hudl 2 users, this device requires addition info to launch fastboot commands.

For Tesco Hudl 2 users use hudl2 script instead of trigger, or you can still manually edit trigger if you want.
[Dell Venue] evaskp:
Lenovo Yoga 2 1050L

.

Worked like a charm om my Lenovo Yoga 2 1050L
[Dell Venue] GartimusPrime:
Any idea if this works on the new x3 processors? Specifically for the Asus zenpad 10 z300c.
[Dell Venue] vampirefo:
No ideal, you can try it and let us know.
[Dell Venue] GartimusPrime:
Thanks but it was unsuccessful :(
[Dell Venue] jerbear294:
Did you try every trigger?
[Dell Venue] GartimusPrime:
Yeah, I renamed cwm to recovery.zip and tried every trigger. All I get it is this

http://pastebin.com/4ic28F22
[Dell Venue] bayu jhosepira:
How about update binary
[Dell Venue] GartimusPrime:
What do you mean?
[Dell Venue] juniormoncada17:
I used the first method but not work :confused:

Using Trigger 1
target reported max download size of 552779776 bytes
sending '/tmp/recovery.zip' (3623 KB)...
OKAY [ 0.633s]
writing '/tmp/recovery.zip'...
OKAY [ 0.520s]
finished. total time: 1.154s
target reported max download size of 552779776 bytes
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.421s]
writing '/tmp/recovery.launcher'...
OKAY [ 0.466s]
finished. total time: 0.887s
target reported max download size of 552779776 bytes
sending '/sbin/adbd' (349 KB)...
OKAY [ 0.394s]
writing '/sbin/adbd'...
OKAY [ 0.465s]
finished. total time: 0.859s
...
FAILED (remote: unknown OEM command)
finished. total time: 0.247s

Say: FAILED (remote: unknown OEM command)

and using the older version Linux_tethered_cwm.zip, work fine, left alone waiting in droidbot.

Helpme! please [MENTION=2472806]vampirefo[/MENTION]
[Dell Venue] vampirefo:
You don't say what device you have, You might need to try another trigger.
[Dell Venue] juniormoncada17:
I have a tablet intel, using the command:

sudo ./trigger 3

throw:

Using Trigger 3
target reported max download size of 552779776 bytes
sending '/tmp/recovery.zip' (3623 KB)...
OKAY [ 0.607s]
writing '/tmp/recovery.zip'...
OKAY [ 0.467s]
finished. total time: 1.074s
target reported max download size of 552779776 bytes
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.421s]
writing '/tmp/recovery.launcher'...
OKAY [ 0.466s]
finished. total time: 0.887s
target reported max download size of 552779776 bytes
sending '/sbin/partlink' (349 KB)...
OKAY [ 0.397s]
writing '/sbin/partlink'...
OKAY [ 0.465s]
finished. total time: 0.862s
...
(bootloader) Stop partitioning

OKAY [ 0.493s]
finished. total time: 0.493s

but, the tablet no reboot:confused:
[Dell Venue] vampirefo:
Tablet Intel doesn't tell me anything, try all 4 triggers.
[Dell Venue] juniormoncada17:
YES! it worked!! thanks [MENTION=2472806]vampirefo[/MENTION] +1 :good:
[Dell Venue] brackenhill_mob:
Asus ZenPad S 8.0 tablet (model Z580C)

Success with Asus ZenPad S 8.0 tablet (model Z580C) using trigger 2

Replacement for my Tesco Hudl2 which seemed to fry the innards when the battery ran too low :(

[MENTION=2472806]vampirefo[/MENTION] FYI TWRP doesn't work. It displays but the screen doesn't respond to any tap. CWM works fine. Happy to help debug this if you want to get a working version - PM me
[Dell Venue] RiskyBiscuits:
Hi, I'm using an Acer A1-830. I can get the recovery menu to come up with Trigger 2, but when I use the volume buttons to select an option, it flashes back and forth between Droidboot and the recovery menu, and when I press the power button, it selects the option for the recovery menu (install zip) and the Droidboot menu (reboot) at the same time, which causes my device to reboot. I can't seem to actually install SU because of this. Am I making a rookie mistake somewhere?

Edit: Never mind, I was able to bamboozle it into working by waiting for my screen to time out to black before inputting each up/down/next option to avoid the input going through to Droidboot. Thanks so much for this toolset.
[Dell Venue] dawgdoc:
That's curious, I wonder what was causing that behavior?

I have two A1-830s. The first I rooted with s-d-c's MyBatchToolkit, the second I rooted with this method using trigger 2 as you did. I had no issues either way, well no issues after I updated the drivers on the borrowed Windows laptop when rooting my original A1.
[Dell Venue] RiskyBiscuits:
Yeah, it's very strange. I didn't think I was going to be able to get through the process until I noticed that the Droidboot menu was not affected by my button input when the screen had timed out, and would only affect selecting options in the recovery menu. This did mean, however, that for every menu selection and moving the currently selected item with the power button and volume controls, respectively, I had to wait for the screen to time out before pressing a button. For anyone who runs into my problem, that's how you can get through it.
[Dell Venue] JasonSilver:
I'm thinking of doing this on my old Dell 3830 - is it still recommended? Anything I should be concerned about?
[Samsung Gear S] bda714:
CLOSED
[Samsung Gear S] bda714:
Renderings

Here are some of the renderings with a 22mm pin attachment. Just a sneak preview.
[Samsung Gear S] bda714:
res

Rsvd
[Samsung Gear S] Step666:
One small question.

Whilst 22mm is a standard size, it's not the only one - a quick look round online would seem to suggest that anything up to 30mm is pretty easy to get ahold of.

If that's the case, why opt for 22mm? It seems a little small compared to the size of the Gear S itself.