I am reviewing one of the update file for the Android device which is a ZIP package - when put on the root of the USB stick and reboot the device, it's automatically unpacked and installed (new software version).
ZIP file is called: vendor_Version.zip and contains a few files:
Code:
.
├── META-INF
│ ├── CERT.RSA
│ ├── CERT.SF
│ └── MANIFEST.MF
├── vendor_Version.dat (1 KB)
└── vendor_Version.enc (755 169 KB)
MANIFEST.MF contains:
Code:
Manifest-Version: 1.0
Created-By: 1.0 (Android SignApk)
Name: vendor_Version.enc
SHA1-Digest: C83q1xzzLihdxzgcci5kyO9ar8A=
Name: vendor_Version.dat
SHA1-Digest: +DdVkCEm8SasdwPnlpMMxG+mYY=
And here comes the question:
Is it possible to extract the vendor_Version.enc file, modify its content and pack it back?
Related
Here's what I have so far, courtesy of the DOS "tree" command.
Code:
[FONT="Courier New"]├───kernel
│ Stock-Triumph-Kernel_test.zip
│ Umph-Kernelv1.zip
│ Umph-Oddballv1.zip
│
├───recovery
│ cwm-recovery 4.0.1.4.zip
│ Stock_Recovery.rar
│
├───rom
│ ├───austrie
│ │ Princely - Black, Red, Transparent.zip
│ │ Princely - Gingerbread.zip
│ │ Princely - Honeycomb.zip
│ │ Princely - HTC Black, Blue, White.zip
│ │ Princely - Purple.zip
│ │
│ ├───b_randon14
│ │ Deodexed_Theme_Template.zip
│ │
│ ├───llorn
│ │ pink1.1b.zip
│ │
│ └───punkmaxx
│ BlacknBlue_Oddball.zip
│ BlacknWhite_Oddball.zip
│ Black_Oddball.zip
│ Ginger v3.zip
│
└───stock
bootloader image.zip[/FONT]
you forgot cm7 by genesis( i think thats his name)
kofman13 said:
you forgot cm7 by genesis( i think thats his name)
Click to expand...
Click to collapse
That, the 1% battery mod, and b_randon14's mod? Oh dear... and that was the reason I just swapped SD cards too!
I have installed busybox on my device, though have trouble in using tar. I issued this command but gets an error,
$ tar -xv stressapptest-1.0.4.tar
This is the usage help it gives,
BusyBox v1.19.4-Stericson (2012-02-20 19:30:32 CST) multi-call binary.
Usage: tar -[cxtZhmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
Z (De)compress using compress
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
What combination should I use to extract the file(.tar)?
Thanks..
DKSL said:
I have installed busybox on my device, though have trouble in using tar. I issued this command but gets an error,
$ tar -xv stressapptest-1.0.4.tar
This is the usage help it gives,
BusyBox v1.19.4-Stericson (2012-02-20 19:30:32 CST) multi-call binary.
Usage: tar -[cxtZhmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
Z (De)compress using compress
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
What combination should I use to extract the file(.tar)?
Thanks..
Click to expand...
Click to collapse
You didn't add the "f" switch to choose the filename so tar is trying to read from stdin. Change your command to:
tar -xvf stressapptest-1.0.4.tar
Similar problem I have:
Command:
tar -zcvf /storage/emulated/0/!Backup/backup_`date +%Y-%m-%d_%H-%M-%S`.tar.gz /storage/emulated/0/!Bac
kup/tmp
BusyBox v1.21.0-Stericson (2013-01-28 21:49:55 GMT) multi-call binary.
Usage: tar -[cxtZhmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
====================================
I want to compress to gz.
The thread http://forum.xda-developers.com/showthread.php?t=1886460 looks very promising for rooting my device (Star B94M Quad Core).
But there is no instruction on how to get it to run from Linux, and i can't figure it out. There are some .sh shell scripts and things that look like linux binaries (no extension name), but nothing that says what to run when. There's a readme.txt but it's full of characters my locale can't deal with and it doesn't specify which one it's in (but i'm guessing it belongs to a language i wouldn't understand).
Code:
├── RunMe.bat
├── stuff
│** ├── adb
│** ├── adb.exe
│** ├── AdbWinApi.dll
│** ├── AdbWinUsbApi.dll
│** ├── busybox
│** ├── busybox-armv6l
│** ├── busybox.exe
│** ├── checklt30.bat
│** ├── fakebackup.ab
│** ├── fastboot.exe
│** ├── install-recovery.sh
│** ├── libservicemenu.so
│** ├── onload.sh
│** ├── ric
│** ├── rootkittablet.tar.gz
│** ├── RootMe.tar
│** ├── script1.sh
│** ├── step2.sh
│** ├── step3.sh
│** ├── su
│** ├── SuperSu.apk
│** ├── Superuser.apk
│** ├── tabletS.ab
│** └── Term.apk
└── z_rootkit
├── getroot.sh
├── onload.sh
├── readme.txt
├── src
│** └── onloadhook
│** └── jni
│** ├── Android.mk
│** └── onLoadHook.c
└── usbux.ab
Also i can't post in that forum, that's why i'm posting here. I will try sending the OP of the thread a message to attract his attention to this.
ACtually you have to translate the bat file to sh or just wait for v26, i will add a unix compatible script into that one.
Regards
I tried running the adb binary, but
Code:
$ ./stuff/adb wait-for-device
never returns it prints
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
And then i killed it after some time.
Code:
$ ./stuff/adb pull /system/app/Backup-Restore.apk .
Gives "error: device not found"
Is this an indication that i need to use one of the other options from RunMe.bat?
I'll keep fiddling...
In v29 it's still the same: daemon started succesfully, then nothing happens.
PS The RunMe.sh contains Windows line ends, if anyone reads this it's easily fixed with vim, ':set fileformat=unix'
Hey Xda!
I need help rooting this LG phone called a M153 "Fortune" running on android 6.0.1 Marshmallow. Does anyone know how to go about it?
With Android 6 by default Toybox ( no root ) is integral part of it. Update Toybox to version 0.8.5 what comes with root ( SU ).
jwoegerbauer said:
With Android 6 by default Toybox ( no root ) is integral part of it. Update Toybox to version 0.8.5 what comes with root ( SU ).
Click to expand...
Click to collapse
Thank you for your answer! But I'm somewhat of a noob, can you please elaborate?
You create a
Code:
TOYBOX-UPDATER.ZIP
|
│
├───bin
│ │ toybox_updater.sh
│ │
│ ├───busybox-1.29.0
│ │ ├───32
│ │ │ busybox
│ │ │
│ │ └───64
│ │ busybox
│ │
│ └───toybox-0.8.5
│ ├───32
│ │ toybox
│ │
│ └───64
│ toybox
│
└───META-INF
│ CERT.RSA
│ CERT.SF
│ MANIFEST.MF
│
└───com
└───google
└───android
update-binary
updater-script
and flash it by means of a Custom Recovery
Neo 2 kernel boots slow and then crashes then boots back again over and over , i found that if i enable a screen lock it just fix this issue temporarily and the system starts , i found that wifi and audio drivers not recognized there's no wlan0 no wifi connection , and no audio but camera works. I don't know if this issue is due to broken kernel source or the source is ported to specific variant of Android 11 say A.03 or whatever
Or is it just me not knowing how to append the kernel DTB to stock DTB but i tried
After compiling the kernel it gave me this list of dtbs
~/.../arm64/boot $ tree dts/
dts/
├── modules.order
├── qcom
│ ├── apq8016-sbc.dtb
│ ├── apq8096-db820c.dtb
│ ├── ipq8074-hk01.dtb
│ ├── modules.order
│ ├── msm8916-mtp.dtb
│ ├── msm8992-bullhead-rev-101.dtb
│ ├── msm8994-angler-rev-101.dtb
│ ├── msm8996-mtp.dtb
│ └── sdm845-mtp.dtb
└── vendor
├── 21615
│ ├── kona-mtp-overlay.dtbo
│ ├── kona-v2.1.dtb
│ ├── kona-v2.dtb
│ ├── kona.dtb
│ └── modules.order
├── 21619
│ ├── kona-mtp-overlay.dtbo
│ ├── kona-v2.1.dtb
│ ├── kona-v2.dtb
│ ├── kona.dtb
│ └── modules.order
├── modules.order
└── oplus
└── modules.order
5 directories, 22 files
Click to expand...
Click to collapse
I have no idea why is it doing that or what to do with them
However the stock dtb is roughly 22M in size those dtbs that the kernel gave me won't reach to that size so i thought i could use cat command and cat the stock dtb and kernels one into a single dtb but that didn't work i got a corrupted boot image screen when boot
I also tried to decompress stock dtb with dtc command and tried to recompress it, it resulted a dtb file less in size than the original one
Have anyone succesed in compiling and booting neo 2 kernel ?