I need to dump phone contents in forensics way, but without hardware tampering. Android is 4.1, stock unrooted ROM with patternlock, stock recovery. I don't want to install custom recovery, but can do everything with update.zip and appropriate scripts. My question is, does the vulnerability with master key applies only to *.apk files or can it be used to pass through signature verification of update.zip in stock recovery?
Related
How to flash back to signed-kila-ota-115247-prereq.TC4-RC19+RC28.zip?
I've flashed my mtd1 and mtd2 which I backed up before I apply the modified recovery.img.
But when I do the reboot and update, It said:
"E: No signature (376 files)"
"E: Verification failed"
It seems I dont get my images flashed correctly, be I'm sure the boot image was flashed..
fluke.l said:
How to flash back to signed-kila-ota-115247-prereq.TC4-RC19+RC28.zip?
I've flashed my mtd1 and mtd2 which I backed up before I apply the modified recovery.img.
But when I do the reboot and update, It said:
"E: No signature (376 files)"
"E: Verification failed"
It seems I dont get my images flashed correctly, be I'm sure the boot image was flashed..
Click to expand...
Click to collapse
I'm assuming you have the modified recovery.img installed. Run SignApk.jar on the signed-kila-ota-115247-prereq.TC4-RC19+RC28.zip. Rename it to update.zip and put it on the sdcard (taking care to unmount the usb mass storage before unplugging). Boot into recovery menu (Home+Red) and Alt+S to flash. When it's done press Home+Back as prompted. That should do it.
Isn't the official RC29 update.zip signed with google's private key?
How could I sign it?
I'm just recovered to the offcial boot.img and recovery.img, which were backed up by myself from mtd1 and mtd2.
The way signing works with java archives is rather than encrypting the files themselves, the signing process simply adds a list of filehashes encrypted with the priv key. Resigning simply overwrites this list with your own (in this case the test private keys).
If you want to install with the original stock ota update then flash the original recovery.img (you can extract it from the stock ota update).
jashsu said:
The way signing works with java archives is rather than encrypting the files themselves, the signing process simply adds a list of filehashes encrypted with the priv key. Resigning simply overwrites this list with your own (in this case the test private keys).
If you want to install with the original stock ota update then flash the original recovery.img (you can extract it from the stock ota update).
Click to expand...
Click to collapse
Thanks. I got it.
I'll do this soon.
I've failed with log into google account many times with the unofficial update package.
Everytime when I finished log in, the com.google.setupwizard throws exception.
Right I have the modified RC30 and the modded recovery & boot image.
I'm going to return my G1 for a new one but before i do, i need to flash it back so it can install the OTA updates. (Phone keep shutting off when i close my screen) I want to make sure what I'm going to do is correct so i don't brick my phone.
Download the RC29 patch and extract the recovery & boot img.
Flash the images into the phone.
Is this correct ?
Thanks for the help
You don't need to reflash recovery or boot. Use SignApk.jar on the official RC29 or RC30 and put it in the root of memcard. Reboot and flash. Should be official. You have to sign it with test keys or the modified recovery will reject it.
jashsu said:
You don't need to reflash recovery or boot. Use SignApk.jar on the official RC29 or RC30 and put it in the root of memcard. Reboot and flash. Should be official. You have to sign it with test keys or the modified recovery will reject it.
Click to expand...
Click to collapse
Alright thanks a lot.
Hello Guys
I am new to android so please correct my mistakes and i will try to give every detail as possible.
I am having Genx tablet GX pad 300 (It is rooted). By mistake i left my tablet as home and my small brother tried to unlock it. As it was password protected so after 15 failed failed attempts, it got hard locked and Asked for my Gmail ID and PASSWORD to unlock. BUT my wifi was disabled so i was not able to reset it.
An other method was to use ADB and bypass the Password, but The usb debugging was disabled so it didnt worked either
thirdly I saw a method (on XDA) to use Recovery mode to flash AROMA Filemanager and delete the files that were related to the password.
Now the real problem begins so please cross your fingers.
First i copied the 'aroma file manager" .zip file in external sd card. the file is in the attachment and here is the link to its XDA page, click here
First i booted my device into the Recovery mode and seleted the the option "Apply update from external sd" and selected the update file (.zip format). It gave me error
E Signature verfication failed
Installation aborted
I had Android System Recovery 3e
I did a five hour research and came to know that it is security in android system recovery 3e to reject unofficial installation, i came to know that if i have to fix these errors the either i have to flash a Custom rom like CWM or a MODDED Android system recovery 3e which allows the installation of unofficial apps. the problem is that there is now Custom CWM for my device and i dont know how to make one from the source code. Secondly they have to be installed by ADB but i cant acess my device locked. I also found that sometimes we try to flash a new recovery form within a recovery it may brick the device. i also found that the updates that can be flashed by android system recovery should be named Update.zip and should be officially signed.
I know that there are many methods and apps to sign the .zip files so that they are accepted by the Android system recovery 3e.
i came across apps like zipsigner and signapktic both of them are available on google play. I also used used manual method to sign the aroma filemanager .zip file but every thing i tried it gave me the E signature verification error installation aborted.
My Question is this that how to Sign files so that they are accepted in the ANDROID STOCK RECOVERY 3e
Please keep it simple as possible.:good::laugh:
Download APKManager (5.1). Extract it, copy your zip to ./other/ folder, run cmd.exe, change directory to ./other/ then sign using following command in cmd.exe:
java -jar signapk.jar -w testkey.x509.pem testkey.pk8 your-rom.zip signed.zip.
~It does not require internet connect connection..you can sign in to google account without internet~
Me too!
I have the same problem and can not find an answer for my life! I really need something that can sign the zip for the stock recovery!
do not recognize the command
This is the official stock 4.1.2 ROM for the SM-T210R. Only requirement is to have a custom recovery (TWRP was used, but others might be compatible).
The provided folder and its files need to be extracted using 7zip (or supportable extractor) to the tab's SD card in the "/TWRP/Backups/<device serial>" folder. (create a backup from the recovery if you need to make the folder)
(DO NOT SKIP THIS STEP): Before flashing, one needs to either perform a factory reset, or preferably wipe the "data," "cache," and "dalvik-cache" from inside the recovery before "restoring".
{DO NOT WIPE YOUR "EFS" PARTITION!!}
If having problems with the KitKat update, try: http://forum.xda-developers.com/gal...-stock-sm-t210r-4-1-2-jellybean-odin-t2958676
It's actually better to use because it restores EVRYTHING, the TWRP flash doesn't.
The 4.4.2 Stock ROM is available here: http://forum.xda-developers.com/galaxy-tab-3/general/tab-3-7-0-sm-t210-r-stock-4-4-2-kitkat-t2930075
A torrent client (such as utorrent) is required to download this file.
Anyone who wishes to contribute, please seed if you can after downloading ("Force Starting" the torrent will seed it indefinitely.)
Hello,
I have a phone that I would like to root, unfortunately the bootloader is locked. There are some pre-rooted stock roms around that you could flash using fastboot without unlocking the bootloader. Unfortunately the latest version of the firmware is not available in pre-rooted form.
I downloaded the lastest official firmware (an update.zip package) from the website of the manufacturer and installed it on my phone using the stock recovery. Now the only thing that I need to do is modify the system image and flash it back in the phone.
I converted the system.new.dat file that was included inside the zip package into a raw image that I can easily mount and modify from my computer (I use Debian Jessie). How could I modify the system image to include the su binary and a Superuser up (SuperSu, or equivalent) and convert it into a format that I can flash using fastboot?
I'm running Android 6.0.1 with SELinux set to enforce. The device is an Asus Zenfone 2 Laser ZE550KL. I've posted here because the process of modding a stock rom should be almost doable regardless of the phone manufacturer
Hey,
I have an android smartphone called chameleon 5r single that has those biometric functions and staff. it has a modified kernel, not rooted, and not that popular, I could not find any stock rom for it to extract the boot.img file, And I need to root it to customize some functions. It is not rooted, it does not have a custom recovery, And I need to at least dump the boot.img file to create a twrp custom recovery for it. Any recommendations/solutions?