yashsingh1/xdaforums huggingface dataset:
[Dell Venue] vampirefo:
[MENTION=4821597]social-design-concepts[/MENTION] has already answered your question, I will expand some what, Yes one can root via command line or via script I do it myself. You need to stop droidboot then start adbd, setup recovery, the recovery is set to be pushed or just use busybox to untar, temp mount /data to get adb key permission or adb wont connect. I have a special adbd which is 100% root all the time, so need to patch or change files to get root out of adbd, I also use the same adbd on my iview i700, to give me adb remount, I have a script to replace the stock adbd on each reboot, so I have adb root or adb remount anytime I want.

This adbd is private though, at the moment not share able.

But to answer your questions yes it can be done.
[Dell Venue] vampirefo:
Here are my scripts, nothing fancy but they work.

adb reboot bootloader

setup_adb

#!/bin/bash
fastboot flash /sbin/adbd-recovery ./adbd-recovery
fastboot flash /sbin/partlink ./partlink
fastboot flash /tmp/busybox ./bb
fastboot flash /tmp/recovery.tar ./recovery.tar
fastboot oem stop_partitioning

partlink

#!/system/bin/sh
stop adbd
mount -t ext4 /dev/block/mmcblk0p9 /data
#stop fastboot
stop droidboot
rm -r /sbin/adbd
chmod 755 /tmp/busybox
/tmp/busybox tar -xvf /tmp/recovery.tar
mv /etc/recovery.fstab /etc/recovery.fstab.bak
cp /sbin/recovery.fstab /etc/recovery.fstab
chmod 755 /sbin/adbd-recovery
mv /sbin/adbd-recovery /sbin/adbd
/sbin/adbd
start adbd
umount /data

adb shell

/sbin/recovery &
[Dell Venue] tomtom1265:
WOWW!!!!!!!!!

Beautiful work man, no more closed binary files.

As always very impressive.
[Dell Venue] kepalakayu:
Hello,

it's a little off topic, but I would like to know if there is for Android, Linux Intel Atom and not ARM version , installable with Linux Deploy eg

Thanks
[Dell Venue] vampirefo:
Not that I am aware of.

sent from my kingSing T1 via taptalk
[Dell Venue] kepalakayu:
Halas !

Ouch!

everything worked, I got a notice from a system update , I can not but should have : it has stopped on the way and especially now the tablet does not stop to reboot :confused: Is it may be the rooting and what to do ?
[Dell Venue] vampirefo:
No ideal, this is just for rooting, you should always unroot before doing any updates.
[Dell Venue] kepalakayu:
un-bricking...

Hello,

Of course , I try to recover my Iconia TAB8 :(

So, I run:

adb reboot bootloader

and it works well

Then I try

sudo ./start_recovery

and it works well

so I can try to execute something:confused:

is what I can load a new "clean" system and therefore reset ?

and where to find this system ?

---------- Post added at 07:28 PM ---------- Previous post was at 07:10 PM ----------

Is what I can place

SDs_Acer_AV0K1_A1-840FHD_RV0TRC01_WW_GEN1.zip

on my SD card

then put the SD card in the tablet

and then execute to return to the starting level
[Dell Venue] Innarthe:
I have a Acer Iconia One 7 B1-730HD I should use the "backup_factory"(T2) option according to the windows thread.

So I changed the last line in start_recovery to: "./fastboot oem backup_factory". But at the end of the script I got this message: "FAILED (remote: unknown OEM command)" and a similar one on the device. I tried the recovery options anyway but the system rebooted to the "Android system recovery <3e>". Then I tried "stop_partitioning" (T2) I got no error messages but it rebooted to the system recovery. Finaly I tried "startftm", no error message, but when the device rebooted in to the system recovery it froze.

In the windows thread they mentioned that "oem stop_partitioning" should work on many kitkat builds. But I would rather not upgrade.

Data from the device

IAFW v.: F9.E1

Android: 4.2.2

Kernel: 3.4.43

Image v.: Acer_AV052_B1-730HD_RV04RC01_WW_GEN1

Build number: Acer_AV052_B1-730HDRV04RC01_WW_GEN1

Image P/N FM.NPA.A0.00T

Droidboot v.: 2.0

(According to the "Linux Deploy" Google Play page the latest version should work with Intel devices)
[Dell Venue] vampirefo:
You get the triggers from /system/bin/droidboot

adb pull /system/bin/droidboot

open terminal in directory where you pulled droidboot

strings ./droidboot > trigger.txt

grep -Hr backup_factory

grep -Hr stop_partitioning

grep -Hr startftm

Here is my output.

vampirefo@vampirefo-GA-MA78GM-US2H:~/Desktop/hh$ strings ./droidboot > trigger.txt
vampirefo@vampirefo-GA-MA78GM-US2H:~/Desktop/hh$ grep -Hr backup_factory
Binary file droidboot matches
trigger.txt:sys.backup_factory
trigger.txt:backup_factory
vampirefo@vampirefo-GA-MA78GM-US2H:~/Desktop/hh$ grep -Hr stop_partitioning
Binary file droidboot matches
trigger.txt:stop_partitioning
vampirefo@vampirefo-GA-MA78GM-US2H:~/Desktop/hh$ grep -Hr startftm
Binary file droidboot matches
trigger.txt:startftm
vampirefo@vampirefo-GA-MA78GM-US2H:~/Desktop/hh$

Post your results.
[Dell Venue] vampirefo:
Also If you want to use T2, and your device supports it, make sure you change the script correctly.

Just call this script start_recovery_T2

#!/bin/bash
./fastboot flash /tmp/recovery.tar ./recovery.tar
./fastboot flash /tmp/recovery.envsetup ./recovery.envsetup
./fastboot flash /tmp/recovery.fstab ./recovery.fstab
./fastboot flash /tmp/postrecoveryboot.sh ./postrecoveryboot.sh
./fastboot flash /system/bin/cp recovery.launcher
./fastboot oem backup_factory
[Dell Venue] tomtom1265:
[MENTION=2472806]vampirefo[/MENTION]

Thanks again for the script method, it's nice to know how things work and how and where to get the trigger information, so we can look for other triggers, plus we will know right away what triggers work for our device.
[Dell Venue] Innarthe:
Are you aware that the second last line in the original script is "./fastboot flash /sbin/partlink recovery.launcher"?

I tried the new script (with "./fastboot flash /system/bin/cp recovery.launcher") but it failed with the same "FAILED (remote: unknown OEM command)" message.

The string "backup_factory" was not found in trigger.txt but the two others.

I include the output file from the "adb pull /system/bin/droidboot" command if it could be of any use.

Maybe I should ask the one who reported the 730HD device supported trigger T2 for various versions of his device?
[Dell Venue] vampirefo:
Below is the T3 which is original script, no ideal what you are asking.

#!/bin/bash
./fastboot flash /tmp/recovery.tar ./recovery.tar
./fastboot flash /tmp/recovery.envsetup ./recovery.envsetup
./fastboot flash /tmp/recovery.fstab ./recovery.fstab
./fastboot flash /tmp/postrecoveryboot.sh ./postrecoveryboot.sh
./fastboot flash /sbin/partlink recovery.launcher
./fastboot oem stop_partitioning

Both T2 and T3 scripts work on my tablets.
[Dell Venue] Innarthe:
My native language is not english so maybe I have a problem to make myself clear. And I have no experence rooting devices and limited knowledge of linux.

The reason I asked about the old scrip is because, the one I downloaded, had this line:

./fastboot flash /sbin/partlink recovery.launcher

And in the script in your reply that line was replaced with:

./fastboot flash /system/bin/cp recovery.launcher

I used the "adb bugreport" command and found out I had this build "Acer_AV052_B1-730HD_1.011.00_WW_GEN1". Do you have the same tablet?

If I would take the Windows approach and succed would that mean I have done something wrong or missing some dependency when I tried it in Linux? If it works in Windows it should work in linux?
[Dell Venue] vampirefo:
Try windows version, I don't understand, what you are asking, windows version should work for you.

T2

#!/bin/bash
./fastboot flash /tmp/recovery.tar ./recovery.tar
./fastboot flash /tmp/recovery.envsetup ./recovery.envsetup
./fastboot flash /tmp/recovery.fstab ./recovery.fstab
./fastboot flash /tmp/postrecoveryboot.sh ./postrecoveryboot.sh
./fastboot flash /system/bin/cp recovery.launcher
./fastboot oem backup_factory

T3

#!/bin/bash
./fastboot flash /tmp/recovery.tar ./recovery.tar
./fastboot flash /tmp/recovery.envsetup ./recovery.envsetup
./fastboot flash /tmp/recovery.fstab ./recovery.fstab
./fastboot flash /tmp/postrecoveryboot.sh ./postrecoveryboot.sh
./fastboot flash /sbin/partlink recovery.launcher
./fastboot oem stop_partitioning
[Dell Venue] tomtom1265:
Vampirefo

What about trigger 1 or T1? I have all three triggers on my dell.
[Dell Venue] kepalakayu:
in the infernal loop

Good evening everyone,

Voila! I turn around for a while after making a stupidity I think ...:confused:

The résult is that without stop my tablet boots up normally, and then displays the beginning of the logo flashes, begins to show the start of the logo, etc.

When I try adb reboot bootloader, it tells me that there is no device ! :(

Is there a way to regain control, and then how to rewrite the bootloader in Iconia?
[Dell Venue] social-design-concepts:
Which one the needed files for unbricking are only available for a few of the Acer does the device not boot into fastboot / droidboot by hardware keys?
[Dell Venue] vampirefo:
T1 is a mess, I don't post it cause it takes a long time to start recovery from several seconds to minutes, T2 and T3 start recovery quickly, so they should be used instead of T1.

T1 uses /sbin/adbd, This was SDC original trigger works well for adb push and set permissions, eg root via adb, but is slow to launch recovery, then need to push fstab and reset recovery to get to work correctly.

I am going to leave it out, but you can figure it out just remember /sbin/adbd.
[Dell Venue] vampirefo:
You may need to try key combo power off, press volume down and power same time, or try volume up and power, I don't have your device so unsure what combo you need.

From reading your post I think you are in a bootloop, and unable to use adb.
[Dell Venue] kepalakayu:
Ah ! I progress

OK , you're right ,

doing power + vol down, this gives me good with the menu:

-droidboot,

-reboot,

-recovery,

-power off

Now it remains to be again a tablet boots up properly ;)
[Dell Venue] kepalakayu:
I'm afraid of being stuck

Good Evening,

How can I do, in fact this is what I run and I get :

adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

as if the tablet was not connected ...
[Dell Venue] vampirefo:
You haven't setup your user to use adb?

Make sure USB debugging is checked.

Open terminal

killall adb

Sudo adb devices

sent from my kingSing T1 via taptalk
[Dell Venue] kepalakayu:
my problem is that the SD card is not detected,

So I can not enter a .zip file

in fact, when I boot (power + vol down) I get the following messages on the bottom screen on the tablet:

FASTBOOT INIT...

installer device ignored

FASTBOOT CMD WAITING...

failed to mount device '/dev/block/sda1' as installer partition using fs_type 'vfat'

ition using fs-type 'vfat'

installer device ignored

installer device ignored

no valid installer medium found

Could not open /sys/devices/virtual/backlight

and of course usb debug is not enabled,

So if I type

adb devices

I get nothing because the tablet is not detected as device

an idea?
[Dell Venue] vampirefo:
Perhaps you can get help here

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

The thread is about Acer tablets.
[Dell Venue] kepalakayu:
no, its same...

how can I force the USB debug?
[Dell Venue] hazyl:
the difference between the two scripts

He is pointing out that, besides the expected difference in the last line, a second last line is also different. This got me wondering too, as I have no knowledge of the inner workings of any of this stuff. So, is it a mistake or indeed, both lines of the script need to be different? A little explanation will go a long way.

Thank you.
[Dell Venue] social-design-concepts:
the second to last line is the binary for the service you're replacing the last line is the oem command that triggers that service
[Dell Venue] dawgdoc:
[MENTION=2472806]vampirefo[/MENTION] I unsuccessfully tried tethering the recovery as directed in your first post on my Acer A1-830, but have not yet given up. Have you had any reports of this working with my device? I will next try the second trigger, but first I will pull /system/bin/droidboot to see what is there.

How things went:

I used the google adb and fastboot you linked at the bottom of the post. ADB was able to detect the device and boot it into droidboot/fastboot. I executed the start_recovery script and could see flashing occuring, text was scrolling at the bottom of the device screen. It seemed to be the same text that was displayed in my terminal.

dawgdoc@jrw-lts17c ~/android/a1-830-acer/Linux-tethered-recovery $ adb devices -l
List of devices attached
CLVFB45520B device usb:2-2 product:a1-830_ww_gen1 model:A1_830 device:ducati

dawgdoc@jrw-lts17c ~/android/a1-830-acer/Linux-tethered-recovery $ adb reboot bootloader
dawgdoc@jrw-lts17c ~/android/a1-830-acer/Linux-tethered-recovery $ sudo ./start_recovery
target reported max download size of 614492842 bytes
sending '/tmp/recovery.tar' (5859 KB)...
OKAY [ 1.202s]
writing '/tmp/recovery.tar'...
OKAY [ 0.599s]
finished. total time: 1.801s
target reported max download size of 614492842 bytes
sending '/tmp/recovery.envsetup' (29 KB)...
OKAY [ 0.423s]
writing '/tmp/recovery.envsetup'...
OKAY [ 0.545s]
finished. total time: 0.968s
target reported max download size of 614492842 bytes
sending '/tmp/recovery.fstab' (0 KB)...
OKAY [ 0.426s]
writing '/tmp/recovery.fstab'...
OKAY [ 0.543s]
finished. total time: 0.970s
target reported max download size of 614492842 bytes
sending '/tmp/postrecoveryboot.sh' (0 KB)...
OKAY [ 0.424s]
writing '/tmp/postrecoveryboot.sh'...
OKAY [ 0.547s]
finished. total time: 0.971s
target reported max download size of 614492842 bytes
sending '/sbin/partlink' (5 KB)...
OKAY [ 0.423s]
writing '/sbin/partlink'...
OKAY [ 0.547s]
finished. total time: 0.970s
...
(bootloader) Stop partitioning

OKAY [ 0.551s]
finished. total time: 0.551s
dawgdoc@jrw-lts17c ~/android/a1-830-acer/Linux-tethered-recovery $

When all was stopped/finished I selected the option to boot into recovery from the droidboot menu. This took me to the stock recovery <3e> instead of to the tethered CWM recovery.

I'll let you know how it all goes. although it may be a couple of days. I'm already rooted and was attempting this to use the CWM to make a nandroid backup, therefore not in a great hurry.
[Dell Venue] dawgdoc:
I pulled /system/bin/droidboot from my Acer A1-830, so now I need to learn how to see its contents. If this file is of any use to you, [MENTION=2472806]vampirefo[/MENTION] I will attach it to another post.

Trigger 2 works to open the CWM tethered recovery. I'm in the process of making a nandroid at the moment.

Nice Ubuntu Alien vampirefo.

------------

backup completed,

No /sdcard/.android_secure found, skipped backup of applications on external storage. >> That's okay, I haven't installed any to the external card.

No sd-ext found. Skipping backup of sd-ext. >>
[Dell Venue] kepalakayu:
unable switching USB-Debug

Hello,

is there a program (flashable with FlashBoot) that would put USB-Debug ON (for A1-840FHD) ?
[Dell Venue] vampirefo:
no it has to be enabled in normal mode, if you can fastboot then adb debug is enabled, I think you are trying to use adb in fastboot mode, you can't do that unless you are already running cwm tether, fastboot doesn't adb by default, cwm tethered enables adb .

with cwm tehered running open terminal

adb devices
[Dell Venue] vampirefo:
Ok that error just means you need a different recovery.fstab, you need to change my recovery.fstab to your tablet. Do you have stock recovery image? I can look at recovery.fstab.

Also you should try to place zip on internal sdcard, in recovery select sdcard instead of external_sd.
[Dell Venue] kepalakayu:
Unfortunately not.

Precisely this is the question I asked myself:

how many has t he recovery img in total?

where can I find the stock versions?

In which file I must flash?

I admit I'm a little lost to Android specificities, and then they announced that 5.0 will still change things !

Thanks
[Dell Venue] vampirefo:
You try internal sdcard?
[Dell Venue] vampirefo:
Is this your tablet? If so that recovery which is a port of mine is ported to acer.

http://xdaforums.com/showpost.php?p=58275054&postcount=66
[Dell Venue] kepalakayu:
Hum

Ah! there may be a problem: I see a doc that A1-840FHD supports SD Cards up to 16GB and I put a 32GB.

Is it serious, I can change tomorrow
[Dell Venue] social-design-concepts:
Maybe switch :

the recovery.envsetup with the recovery.launcher

and the recovery.launcher with the recovery.trigger

From my latest tethered cwm the fstab generation should resolve the issue.
[Dell Venue] kepalakayu:
No, I just tried and it's the same

sorry
[Dell Venue] vampirefo:
Try this version

http://www.mediafire.com/download/y6d76tfw646i1ot/Linux_CWM_Tethered.zip

Download, extract to desktop make sure trigger is executable

boot into fastboot

open terminal

./trigger 3

all three triggers are included in the trigger script.

to use trigger script open terminal in directory where files have been extracted.

./trigger 1

./trigger 2

./trigger 3

[MENTION=4821597]social-design-concepts[/MENTION]

Thanks for this update works well, this should help alot of people.
[Dell Venue] kepalakayu:
yes I Try

Hello and thank you,

sorry for the wait is the time difference

So I downloaded and extracted the file which gave me a Linux_CWM_Tethered directory.

Having booted the tablet I performed ./trigger 3 and I get this:

$ ./trigger 3
Using Trigger 3
target reported max download size of 1279077034 bytes
sending '/tmp/recovery.zip' (3477 KB)...
OKAY [ 4.669s]
writing '/tmp/recovery.zip'...
OKAY [ 1.003s]
finished. total time: 5.672s
target reported max download size of 1279077034 bytes
sending '/tmp/recovery.launcher' (469 KB)...
OKAY [ 1.304s]
writing '/tmp/recovery.launcher'...
OKAY [ 1.002s]
finished. total time: 2.306s
target reported max download size of 1279077034 bytes
sending '/sbin/partlink' (158 KB)...
OKAY [ 0.954s]
writing '/sbin/partlink'...
OKAY [ 1.006s]
finished. total time: 1.960s
...
(bootloader) Stop partitioning

FAILED (status read failed (No such device))
finished. total time: 5.957s

$

my tablet rebooted and now I'm under Vampirefo Venue 8 v6.0.3.7

with a menu and a new icon on the screen.

Menu:

-reboot system now

-install zip

-wipe data / factory reset

-wipe cache partition

-backup and restore

-mounts and storage

-advanced

I chose "mounts and storage"

there I mounted everything except successively

/ external-sd

and

/ sd-ext

for which I have an error mounting

It does not happen at all to see the SD card

is what it is because it is a 32 GB ?
[Dell Venue] vampirefo:
Try another micro sdcard.
[Dell Venue] kepalakayu:
Waow

OK, so I went to buy a 16MB SD Card (that's good because at the moment there are big discounts ...)

and I installed it (it is formatted factory in FAT32)

and I again

so I have the same messages, and after reboot, the same menu

but now I have no problem mounting the SD Card (empty ...)

this is a big progress

Going further, I do:

$ Adb devices
List of devices attached
430000786412 device

$

Yeah !!!

I am very happy because it really progressing

Besides making a shell adg, I may "walk" in the tablet:

$ adb start-server
$ adb shell
~ # pwd
/
~ # ls
cache installer
charger lib
config logs
data mnt
datadata original.fstab
default.prop proc
dev property_contexts
droidboot.init.ducati2fhd.rc props.platform.rc
emmc props.rc
etc res
external_sd rfkill_bt.sh
factory root
file_contexts sbin
fstab.charger.ducati2fhd sd-ext
fstab.ducati2fhd sdcard
fstab.ramconsole.ducati2fhd seapp_contexts
init sepolicy
init.baylake.sh sys
init.firmware.rc system
init.net.eth0.sh tmp
init.partlink.rc ueventd.ducati2fhd.rc
init.rc ueventd.modules.blacklist
init.watchdog.rc ueventd.rc
init.watchdog.sh usr
~ #

etc...

so I can do now a lot of things

but yet I still do not have the graphical interface to the normal start

I loop without stop (start of image / blank screen)

what should I do now to get back to normal?
[Dell Venue] vampirefo:
What caused the loop? In recovery format data and cache then reboot.
[Dell Venue] kepalakayu:
hard

Ok, that's what I did but it does not work, I'm still in the loop
[Dell Venue] vampirefo:
What was you doing when the tablet went into a loop? What did you add or remove from your tablet?
[Dell Venue] kepalakayu:
When I'm in the loop, I can not do anything except turn off ...

I have not changed, just after rooted successfully, I got an update notice OTA and I was idiot enough to do so directly.

I think this is the beginning update that is wrong, can be detected at t he a bad sign or SU mode ON

Anyway, since then I turn around, so to say!

Is it possible to reflash various img (system, wifi, photo, etc.)
[Dell Venue] vampirefo:
If you can get stock system and boot you can flash them, I think [MENTION=1829889]vache[/MENTION] may have the files you need, pm him.

sent from my kingSing T1 via taptalk
[Dell Venue] kepalakayu:
OK, I'll try everything to upgrade in out of factory mode

Then start going slowly ...

Thank you for your help, I'll let you know if it's good,

in any case the CWM is excellent
[Dell Venue] kepalakayu:
see you later

I try to join Vache, when its site is up, to see if he has a ROM allowing me to get out

I attached the log of what happened, if it can be useful

thank you and may be soon :)
[Dell Venue] social-design-concepts:
Acer also has the recovery installable zip up on their site for all the devices but the 830 so you could try that route
[Dell Venue] kepalakayu:
Hourrah !

Phew! at last! I have here an operational tablet!

But now I wonder, I do or not I do? the rooting of the tablet ...

Previously, I would like to install CWM permanently (for already make a full backup, etc).

Is that if I do ./trigger 3 it will give me this?
[Dell Venue] kepalakayu:
finished troubleshooting

Okay, I give up, I have not found how to make a nandroid backup without rooting, is may not be possible.

I'll first root, then make all backup and put them carefully away to avoid happening again

Thank you all
[Dell Venue] hazyl:
Regarding the 2015-01-24 build of the tethered CWM recovery (same questions could apply to any version of the tool), is there a plain english description of what recovery.launcher and recovery.trigger are doing? Is there source code that can be shared?

Further, recovery.zip includes several system binaries which presumable replace the ones provided by Android. Is there a description of why these and not others need replacing and what the exact modifications with respect to stock Android are? Source code?

Thank you.
[Dell Venue] vampirefo:
I explain this in post 19, How this works.

sent from my kingSing T1 via taptalk
[Dell Venue] hazyl:
I do not see anything in post 19 that explains what the two binaries recovery.launcher and recovery.trigger do, nor anything about the binaries in recovery.zip. Maybe it is in a different post, if at all? How about sources for all those binaries? Thanks.
[Dell Venue] vampirefo:
You are asking the wrong person, those are SDC files, my post explains what is being done.

If you want SDC source ask him in his thread, which is the windows version.

sent from my kingSing T1 via taptalk
[Dell Venue] hazyl:
OK, sure.

However, recovery.zip appears to be your work. Can you please:

provide a description of why the binaries therein need to replace the stock

say what the exact modifications in those binaries are with respect to stock

provide source code

The reason I am asking, is that nobody should be replacing their stock binaries unless they know what the mods are and preferably be able to see the source.

Thank you.
[Dell Venue] vampirefo:
Lol, the recovery does not replace any files, it brings the files it needs to run.

Google how to build CWM Recovery, you will find many guides, and instructions on how to get cwm source code, as you need it to build the recovery, and it's support files.

Enjoy, I Google for you.

http://www.google.com/url?sa=t&rct=...BTrl0y5axeA6qbQNtChWaow&bvm=bv.85076809,d.aWw

sent from my kingSing T1 via taptalk
[Dell Venue] lap770:
Is It Possibel to install this recovery permanently?

Is It Possibel to install this recovery permanently after getting root access so we don't need every time Pc to boot the recovery