I am trying to apply the BFS patch from here:
http://ck.kolivas.org/patches/bfs/
When I try to apply it, these are the errors that I get:
[email protected]:~/Desktop/test/msm$ patch -p1 < 2.6.31-sched-bfs-222.patch
patching file Documentation/sysctl/kernel.txt
Hunk #1 succeeded at 25 (offset -2 lines).
Hunk #2 succeeded at 45 (offset -5 lines).
Hunk #3 succeeded at 167 (offset -6 lines).
Hunk #4 succeeded at 329 (offset -16 lines).
patching file fs/pipe.c
Hunk #1 succeeded at 42 with fuzz 2 (offset -36 lines).
patching file include/linux/init_task.h
Hunk #1 succeeded at 124 with fuzz 2 (offset 8 lines).
patching file include/linux/sched.h
Hunk #2 succeeded at 140 with fuzz 1 (offset -7 lines).
Hunk #3 succeeded at 152 (offset -7 lines).
Hunk #4 FAILED at 243.
Hunk #5 FAILED at 1010.
Hunk #6 succeeded at 887 (offset -139 lines).
Hunk #7 succeeded at 921 (offset -139 lines).
Hunk #8 succeeded at 984 (offset -147 lines).
Hunk #9 succeeded at 1174 (offset -182 lines).
Hunk #10 succeeded at 1449 with fuzz 1 (offset -198 lines).
2 out of 10 hunks FAILED -- saving rejects to file include/linux/sched.h.rej
patching file kernel/sched.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched.c.rej
patching file kernel/sysctl.c
Hunk #1 FAILED at 86.
Hunk #2 FAILED at 102.
Hunk #3 FAILED at 241.
Hunk #4 succeeded at 587 (offset -87 lines).
3 out of 4 hunks FAILED -- saving rejects to file kernel/sysctl.c.rej
patching file kernel/workqueue.c
Hunk #1 succeeded at 322 (offset 5 lines).
patching file kernel/sched_fair.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_fair.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_fair.c.rej
patching file kernel/sched_idletask.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_idletask.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_idletask.c.rej
patching file kernel/sched_rt.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_rt.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_rt.c.rej
patching file kernel/sched_bfs.c
patching file kernel/Makefile
Hunk #2 succeeded at 95 (offset -12 lines).
patching file kernel/kthread.c
Hunk #1 succeeded at 14 with fuzz 2 (offset -2 lines).
Hunk #2 succeeded at 179 with fuzz 1 (offset 9 lines).
patching file kernel/posix-cpu-timers.c
Hunk #1 FAILED at 249.
Hunk #2 succeeded at 466 (offset -50 lines).
Hunk #3 FAILED at 476.
Hunk #4 FAILED at 967.
Hunk #5 succeeded at 1020 (offset -13 lines).
Hunk #6 succeeded at 1028 (offset -13 lines).
Hunk #7 FAILED at 1344.
4 out of 7 hunks FAILED -- saving rejects to file kernel/posix-cpu-timers.c.rej
patching file kernel/exit.c
Hunk #1 succeeded at 122 (offset 2 lines).
Hunk #2 FAILED at 144.
1 out of 2 hunks FAILED -- saving rejects to file kernel/exit.c.rej
patching file kernel/fork.c
Hunk #1 succeeded at 1169 (offset -24 lines).
patching file mm/oom_kill.c
Hunk #1 succeeded at 333 (offset -5 lines).
patching file init/Kconfig
Hunk #1 FAILED at 441.
Hunk #2 FAILED at 505.
2 out of 2 hunks FAILED -- saving rejects to file init/Kconfig.rej
patching file kernel/delayacct.c
Hunk #1 FAILED at 127.
1 out of 1 hunk FAILED -- saving rejects to file kernel/delayacct.c.rej
patching file kernel/trace/trace.c
Hunk #1 succeeded at 160 (offset -115 lines).
patching file fs/proc/base.c
Hunk #1 FAILED at 366.
1 out of 1 hunk FAILED -- saving rejects to file fs/proc/base.c.rej
patching file kernel/sched_debug.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_debug.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_debug.c.rej
patching file include/linux/ioprio.h
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
patching file kernel/Kconfig.preempt
patching file kernel/timer.c
Hunk #1 succeeded at 973 (offset -180 lines).
Click to expand...
Click to collapse
Any ideas about what could be causing these errors?
I'm kind of confused, shouldn't you be flashing a BFS enabled kernel?
33K said:
I'm kind of confused, shouldn't you be flashing a BFS enabled kernel?
Click to expand...
Click to collapse
I'm trying to make my own kernel with BFS.
Hotweiss, the problem with this patch is that it was made for a 2.6.31 kernel and you are trying to patch a 2.6.29 kernel.
Cyanogen had to backport it to work on 2.6.29 from 2.6.31.
So I would recommend you either ask Cyanogen for a kernel patch or back-port it yourself.
TigerTael said:
Hotweiss, the problem with this patch is that it was made for a 2.6.31 kernel and you are trying to patch a 2.6.29 kernel.
Cyanogen had to backport it to work on 2.6.29 from 2.6.31.
So I would recommend you either ask Cyanogen for a kernel patch or back-port it yourself.
Click to expand...
Click to collapse
I just downloaded the 2.6.31 kernel and it patched perfectly. I will try to patch it manually today.
I am trying to apply the BFS patch from here:
http://ck.kolivas.org/patches/bfs/
When I try to apply it, these are the errors that I get:
[email protected]:~/Desktop/test/msm$ patch -p1 < 2.6.31-sched-bfs-222.patch
patching file Documentation/sysctl/kernel.txt
Hunk #1 succeeded at 25 (offset -2 lines).
Hunk #2 succeeded at 45 (offset -5 lines).
Hunk #3 succeeded at 167 (offset -6 lines).
Hunk #4 succeeded at 329 (offset -16 lines).
patching file fs/pipe.c
Hunk #1 succeeded at 42 with fuzz 2 (offset -36 lines).
patching file include/linux/init_task.h
Hunk #1 succeeded at 124 with fuzz 2 (offset 8 lines).
patching file include/linux/sched.h
Hunk #2 succeeded at 140 with fuzz 1 (offset -7 lines).
Hunk #3 succeeded at 152 (offset -7 lines).
Hunk #4 FAILED at 243.
Hunk #5 FAILED at 1010.
Hunk #6 succeeded at 887 (offset -139 lines).
Hunk #7 succeeded at 921 (offset -139 lines).
Hunk #8 succeeded at 984 (offset -147 lines).
Hunk #9 succeeded at 1174 (offset -182 lines).
Hunk #10 succeeded at 1449 with fuzz 1 (offset -198 lines).
2 out of 10 hunks FAILED -- saving rejects to file include/linux/sched.h.rej
patching file kernel/sched.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched.c.rej
patching file kernel/sysctl.c
Hunk #1 FAILED at 86.
Hunk #2 FAILED at 102.
Hunk #3 FAILED at 241.
Hunk #4 succeeded at 587 (offset -87 lines).
3 out of 4 hunks FAILED -- saving rejects to file kernel/sysctl.c.rej
patching file kernel/workqueue.c
Hunk #1 succeeded at 322 (offset 5 lines).
patching file kernel/sched_fair.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_fair.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_fair.c.rej
patching file kernel/sched_idletask.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_idletask.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_idletask.c.rej
patching file kernel/sched_rt.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_rt.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_rt.c.rej
patching file kernel/sched_bfs.c
patching file kernel/Makefile
Hunk #2 succeeded at 95 (offset -12 lines).
patching file kernel/kthread.c
Hunk #1 succeeded at 14 with fuzz 2 (offset -2 lines).
Hunk #2 succeeded at 179 with fuzz 1 (offset 9 lines).
patching file kernel/posix-cpu-timers.c
Hunk #1 FAILED at 249.
Hunk #2 succeeded at 466 (offset -50 lines).
Hunk #3 FAILED at 476.
Hunk #4 FAILED at 967.
Hunk #5 succeeded at 1020 (offset -13 lines).
Hunk #6 succeeded at 1028 (offset -13 lines).
Hunk #7 FAILED at 1344.
4 out of 7 hunks FAILED -- saving rejects to file kernel/posix-cpu-timers.c.rej
patching file kernel/exit.c
Hunk #1 succeeded at 122 (offset 2 lines).
Hunk #2 FAILED at 144.
1 out of 2 hunks FAILED -- saving rejects to file kernel/exit.c.rej
patching file kernel/fork.c
Hunk #1 succeeded at 1169 (offset -24 lines).
patching file mm/oom_kill.c
Hunk #1 succeeded at 333 (offset -5 lines).
patching file init/Kconfig
Hunk #1 FAILED at 441.
Hunk #2 FAILED at 505.
2 out of 2 hunks FAILED -- saving rejects to file init/Kconfig.rej
patching file kernel/delayacct.c
Hunk #1 FAILED at 127.
1 out of 1 hunk FAILED -- saving rejects to file kernel/delayacct.c.rej
patching file kernel/trace/trace.c
Hunk #1 succeeded at 160 (offset -115 lines).
patching file fs/proc/base.c
Hunk #1 FAILED at 366.
1 out of 1 hunk FAILED -- saving rejects to file fs/proc/base.c.rej
patching file kernel/sched_debug.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_debug.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_debug.c.rej
patching file include/linux/ioprio.h
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
patching file kernel/Kconfig.preempt
patching file kernel/timer.c
Hunk #1 succeeded at 973 (offset -180 lines).
Click to expand...
Click to collapse
Any ideas about what could be causing these errors?
Which ROM are you applying this to?
You have to do a lot of other stuff. Your best bet is to checkout android-2.6.29-bfs from android.git.kernel.org under experimental.
hey Cyanogen, would you mind telling me some of the specifics for the backport
Trying to test out the new BFS 310
Ok, pulled the .31 kernel from android git - apply bfs batch
All good with one error trying to figure out
patching file linux-2.6.31-bfs/kernel/posix-cpu-timers.c
Hunk #3 FAILED at 526.
Reject file info:
*************** void posix_cpu_timers_exit_group(struct
*** 526,532 ****
cleanup_timers(tsk->signal->cpu_timers,
cputime_add(tsk->utime, sig->utime),
cputime_add(tsk->stime, sig->stime),
- tsk->se.sum_exec_runtime + sig->sum_sched_runtime);
}
static void clear_dead_task(struct k_itimer *timer, union cpu_time_count now)
--- 526,532 ----
cleanup_timers(tsk->signal->cpu_timers,
cputime_add(tsk->utime, sig->utime),
cputime_add(tsk->stime, sig->stime),
+ tsk->sched_time + sig->sum_sched_runtime);
}
static void clear_dead_task(struct k_itimer *timer, union cpu_time_count now)
Going to try to compile with reject and see how it goes
Is there not a pre patched file we can just flash for 4.2.5?
Funkstar De Luxe said:
Is there not a pre patched file we can just flash for 4.2.5?
Click to expand...
Click to collapse
Compiling a patched version of AOSP experimental bfs .29 with bfs310 (versus the original 230) now
Great, hopefully it's an easy install proceedure
Anyone managed this yet? Eager to test
got bfs 311 working on 2.6.29.6. Seems to work fine.
Code:
uname -a
Linux localhost 2.6.29.6-cm42-bfs311-farmatito9 #20 PREEMPT Mon Nov 23 22:46:22 CET 2009 armv6l GNU/Linux
Code:
# dmesg | grep BFS
[ 7.187500] BFS CPU scheduler v0.311 by Con Kolivas.
farmatito said:
got bfs 311 working on 2.6.29.6. Seems to work fine.
Code:
uname -a
Linux localhost 2.6.29.6-cm42-bfs311-farmatito9 #20 PREEMPT Mon Nov 23 22:46:22 CET 2009 armv6l GNU/Linux
Code:
# dmesg | grep BFS
[ 7.187500] BFS CPU scheduler v0.311 by Con Kolivas.
Click to expand...
Click to collapse
Is there a file you can upload from your build so I can use it on mine? Or do I need to patch my own install?
I could upload the full source...but where to?
or maybe a diff but against which kernel version?
Can't figure out a solution....
UPDATE: This version of the tool is now deprecated. Please use the updated version!
(and thank @nkk71 while you're at it!!)
[TOOL][LINUX|WINDOWS][64bit][20-MAY-2016]Universal HTC RUU/ROM Decryption Tool 3.0.0
----------------------------------------------------
Original Post:
First of all, I want to state that I deserve credit for none of this - all I did was aggregate some of the great work done by the fantastic devs here on XDA.
BIG Thanks @nkk71, for his idea to make this work universally on all encrypted HTC RUUs and all his hard work to make it happen! All I really did was post the thread.
Prerequisites:
- A system running a 64-bit Linux distro (tested on Ubuntu 15.10 & 16.04 LTS)
- At least 5GB of available disk space (ROMs are big)
readme.txt:
Code:
*** Captain_Throwback & nkk71's RUU decryption scripts for HTC Devices ***
INSTALLATION STEPS:
Extract files into folder of your choice, being sure to preserve the folder structure. The decrypt-htc binary and this readme file should be the only files in the root folder.
Download the encrypted RUU or encrypted rom zip of your choice from HTC (or wherever).
Place RUU.exe in the "place_ruu_here" folder or the ROM.zip in the "place_rom_zip_here" folder.
Run ./decrypt-htc and wait for script to complete (you may be prompted for input if there are issues).
The script will output 3 files (to the "out" folder): boot.img, system.img & the encrypted rom zip you started with (or was extracted from the RUU), named for SD card flashing on your device (if your device has an SD card). There will also be a folder with the extracted firmware for your device that can be used however you see fit :).
NOTE: For the A9, for example, the rom.zip will be named 2PQ9IMG.zip. Each device has a specific filename which will be reflected.
Below is a script of the expected output of the script when processing a RUU.exe.
Code:
Welcome to the RUU extraction and decryption script!
Extracting temporary files...
Extracting rom zip files...
Extracting rom.zip...done.
Extracting android-info.txt...done.
Cleaning up...
Done!
Extracting ZIP files
LargeZip format detected, using ruuveal
ruuveal
-------
Large zip format detected containing 7 zipfile(s)
Dumped (copied) zip file to: 01_dmp.zip
Dumped (copied) zip file to: 02_dmp.zip
Dumped (copied) zip file to: 03_dmp.zip
Dumped (copied) zip file to: 04_dmp.zip
Dumped (copied) zip file to: 05_dmp.zip
Dumped (copied) zip file to: 06_dmp.zip
Dumped (copied) zip file to: 07_dmp.zip
Finished: Successfully extracted zip files to '/home/throwback/android/decrypt/tool/working/extract'
Model ID found by extracting android-info.txt from RUU. Model ID identified as: 0PJA
Looking for keyfile: 0PJA_keyfile_2.bin
Found matching keyfile! Using keyfile: 0PJA_keyfile_2.bin
Decrypting ZIP files
Decrypting 01_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_01_dmp.zip
Decrypting 02_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_02_dmp.zip
Decrypting 03_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_03_dmp.zip
Decrypting 04_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_04_dmp.zip
Decrypting 05_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_05_dmp.zip
Decrypting 06_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_06_dmp.zip
Decrypting 07_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_07_dmp.zip
Unzipping decrypted zips
Archive: decrypted_zips/dec_01_dmp.zip
inflating: decrypted_all/android-info.txt
inflating: decrypted_all/aboot_signed.img
inflating: decrypted_all/radio.img
inflating: decrypted_all/splash1.nb0
inflating: decrypted_all/adsp.img
inflating: decrypted_all/rfg_1.img
inflating: decrypted_all/rfg_2.img
inflating: decrypted_all/ramdisk.img
inflating: decrypted_all/android-info2.txt
inflating: decrypted_all/sensor_hub.img
inflating: decrypted_all/emmc_appsboot.mbn
inflating: decrypted_all/persist.img
inflating: decrypted_all/dt.img
inflating: decrypted_all/bootloader
inflating: decrypted_all/gpt_main_32g.img
inflating: decrypted_all/pg2fs_ship_signkey.img
inflating: decrypted_all/apppreload.img
inflating: decrypted_all/cota.img
inflating: decrypted_all/gpt_main_64g.img
inflating: decrypted_all/sbl1-8994-1.img
inflating: decrypted_all/sdi.img
inflating: decrypted_all/hosd_signed.img
inflating: decrypted_all/rpm-8994-1.img
inflating: decrypted_all/pmic-8994-1.img
inflating: decrypted_all/boot_signed.img
inflating: decrypted_all/recovery_signed.img
inflating: decrypted_all/cpe.img
inflating: decrypted_all/tz-8994-1.img
inflating: decrypted_all/hyp-8994-1.img
inflating: decrypted_all/tp_SYN3351.img
inflating: decrypted_all/tp_MXM11876.img
inflating: decrypted_all/cir.img
inflating: decrypted_all/backup_android-info.txt
Archive: decrypted_zips/dec_04_dmp.zip
inflating: decrypted_all/system.img_02
Archive: decrypted_zips/dec_03_dmp.zip
inflating: decrypted_all/system.img_01
Archive: decrypted_zips/dec_07_dmp.zip
inflating: decrypted_all/dzdata_16g.img
inflating: decrypted_all/dzdata_32g.img
inflating: decrypted_all/dzdata_16g.hdr
inflating: decrypted_all/dzdata_32g.hdr
inflating: decrypted_all/dzdata_64g.hdr
inflating: decrypted_all/dzdata_64g.img
Archive: decrypted_zips/dec_06_dmp.zip
inflating: decrypted_all/system.img_04
Archive: decrypted_zips/dec_02_dmp.zip
inflating: decrypted_all/system.img_00
Archive: decrypted_zips/dec_05_dmp.zip
inflating: decrypted_all/system.img_03
7 archives were successfully processed.
Move system img files to system folder
‘decrypted_all/system.img_00’ -> ‘decrypted_system/system.img_00’
‘decrypted_all/system.img_01’ -> ‘decrypted_system/system.img_01’
‘decrypted_all/system.img_02’ -> ‘decrypted_system/system.img_02’
‘decrypted_all/system.img_03’ -> ‘decrypted_system/system.img_03’
‘decrypted_all/system.img_04’ -> ‘decrypted_system/system.img_04’
Finished: Successfully decrypted RUU to '/home/throwback/android/decrypt/tool/working/decrypt'
/home/throwback/android/decrypt/tool/working/decrypt/decrypted_system
/home/throwback/android/decrypt/tool/out
Attempting to create system.img
Multi-part system images
Sparse Image detected, using simg2img
Please be patient, this can take several minutes...finished.
Testing system.img...
e2fsck 1.42.12 (29-Aug-2014)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/home/throwback/android/decrypt/tool/out/system.img: 4685/286720 files (0.0% non-contiguous), 1041188/1146880 blocks
Finished: Successfully created system.img in '/home/throwback/android/decrypt/tool/out'
Renaming and moving files...
Rom.zip has been renamed for your device.
Boot image extracted from firmware.zip. boot.img & system.img can be used as base for building a new ROM.
Script complete! Files can be found in the 'out' folder. Enjoy your decrypted system!
(above output is from M9 RUU)
Important Notes:
If decrypting a rom.zip that is "combined" (meaning the first zip isn't encrypted), you will see the following error message at the top of the ruuveal section:
Code:
invalid htc aes encrypted zip file!
This just indicates that the first zip file isn't encrypted. The script will continue and complete with no issues, so this isn't a concern.
You may also see these messages:
Code:
caution: filename not matched: system.img*
Code:
1 archive had fatal errors.
These errors indicate that the first zip doesn't contain a system image to be extracted, which is fine (that's the zip that contains the firmware). This isn't a concern either.
The last issue you might notice is this:
Code:
warning [../out/firmware.zip]: 256 extra bytes at beginning or within zipfile
(attempting to process anyway)
The extra 256 bytes is HTC's signature on the unencrypted firmware zip. This also is nothing to worry about.
As long as you have all of the output files at the end of the script, everything should be fine.
Thanks:
twogood for unshield
@kmdm for unruu & ruuveal
@Flemmard for bruutveal
@osm0sis for Android Image Kitchen
@A.S._id for ANDROID_IMG_REPACK_TOOLS
Additional Info
Change Log:
January 11, 2016 - v2.0.0
Complete overhaul of existing script and process
Now works on any encrypted RUU/ROM for any HTC device with a known decryption key
For devices with unknown keyfile, user can provide hboot or hosd image (based on same software version is preferable) and a new keyfile will be created. You can share the new keyfile so that it can be added to our database.
Improved script output and error handling
January 1, 2016 - v1.5.3
Fixed the binary problem - should now work on PCs other than mine
January 1, 2016 - v1.5.2
Back to bash script (for now) to ensure compatibility with other PCs
January 1, 2016 - v1.5.1
Some script and binary cleanup (back end stuffs)
December 31, 2015 - v1.5
Compile script into binary format (back end stuffs)
December 31, 2015 - v1.4.1
Back-end cleanup to use "working" folder for zip processing
December 31, 2015 - v1.4
Added code to handle "combined" zips where first zip file is already decrypted
December 31, 2015 - v1.3
Can now handle encrypted rom zips!
Kill script if no files found
Script renamed from decrypt.sh to decrypt-htc.sh
Renames rom.zip from ruu (or provided rom.zip) to 2PQ9IMG.zip (or whatever corresponds to that for other applicable devices) automatically and puts in "out" folder
December 31, 2015 - v1.2
Added unshield and libunshield to zip so manual compilation is no longer necessary (thanks @nkk71)
December 30, 2015 - v1.1
Added version number
Modified script to allow for usage on multiple HTC devices
December 30, 2015
Initial version
Mine [emoji6]
Sent from my HTC One M9 using Tapatalk
Updated this (just now) to allow for handling of other devices which use the same type of encrypted RUU (like the Desire 626s, for example).
v1.2 is up! No more compilation of libunshield is necessary, thanks to @nkk71's help! Seriously, give that guy some love!
v1.3 is up!
Now there are provisions for handling encrypted ROMs that are zipped, and not just those from an RUU.
Can someone please try this thing out and provide feedback!!!!
v1.4 added.
Now "combined" zips can be extracted/decrypted as well.
Hello. Have tried it. I get the three files. But in Terminal i get the Message
"21 archives were successfully processed"
"2 archives had fatal errors"
Can i ignore the 2 archives fatal errors?
comibined zip first not encrypt
AntikerTa said:
Hello. Have tried it. I get the three files. But in Terminal i get the Message
"21 archives were successfully processed"
"2 archives had fatal errors"
Can i ignore the 2 archives fatal errors?
Click to expand...
Click to collapse
Yes you can, the error is not really an error, it just doesn't find a system.img_xx in 2 zip files, that's all
Sent from my HTC One M9 using Tapatalk
AntikerTa said:
Hello. Have tried it. I get the three files. But in Terminal i get the Message
"21 archives were successfully processed"
"2 archives had fatal errors"
Can i ignore the 2 archives fatal errors?
Click to expand...
Click to collapse
If you look in the "expected script output" in the OP, you'll see the same message (which is why I posted it there).
Though with the latest version, there will only be one archive with a "fatal" error.
If you have good files in the "out" folder, then assume everything went fine.
bl4ckluna said:
comibined zip first not encrypt
Click to expand...
Click to collapse
Was there a point to this post?
Followed instructions...
~/ruudecrypt$ ./decrypt-htc
./decrypt-htc: }u2n��ɢ
No worky, that is the output. Took the HTC RUU from their site. renamed ruu_a9.exe put it in the folder. Nothing else in root. Run decrypt script and that is what it does above.
Also, extracted the rom.zip out of the RUU, placed it in the folder ruu_a9.zip same error.
techlogik said:
Followed instructions...
~/ruudecrypt$ ./decrypt-htc
./decrypt-htc: }u2n��ɢ
No worky, that is the output. Took the HTC RUU from their site. renamed ruu_a9.exe put it in the folder. Nothing else in root. Run decrypt script and that is what it does above.
Also, extracted the rom.zip out of the RUU, placed it in the folder ruu_a9.zip same error.
Click to expand...
Click to collapse
What are you running this on? Where are the details to help troubleshoot? "No worky"? Really?
Is anyone else having issues with the latest version? I can go back to the previous format, but as long as the Linux distro can handle a bash script, it shouldn't matter whether the script is used or the binary is.
Followed your instructions, not much more to explain. For kicks, installed VMWorkstation Pro 12, installed a fresh Ubuntu 15.10, updates etc. Java/ADB and the usual basic stuff. Nothing special going on here, plain vanilla Ubuntu.
Again, downloaded your script in a folder. Copied ruu over to the working folder, renamed it to ruu_a9.exe
Ran the ./decrypt-htc script
Now, it gives this message, but similar:
./decrypt-htc: 8��������y����Y'��w������W�+Ɣ?�has expired!
Please contact your provider [email protected]
What more do you want for diagnosis?
techlogik said:
Followed your instructions, not much more to explain. For kicks, installed VMWorkstation Pro 12, installed a fresh Ubuntu 15.10, updates etc. Java/ADB and the usual basic stuff. Nothing special going on here, plain vanilla Ubuntu.
Again, downloaded your script in a folder. Copied ruu over to the working folder, renamed it to ruu_a9.exe
Ran the ./decrypt-htc script
Now, it gives this message, but similar:
./decrypt-htc: 8��������y����Y'��w������W�+Ɣ?�has expired!
Please contact your provider [email protected]
What more do you want for diagnosis?
Click to expand...
Click to collapse
Try the version I just uploaded and see if that works any better.
Tried that one, more of the same:
[email protected]:~/decrypt$ ls
bin decrypt-htc keyfile lib place_rom_zip_here place_ruu_here readme.txt
[email protected]:~/decrypt$ ./decrypt-htc
�N��<Z"��@i�?|�w���U>I�t��k �*��TN� 8'B��8�m?�"w$�[email protected]�['��
bF��#��
[email protected]:~/decrypt$
techlogik said:
Tried that one, more of the same:
[email protected]:~/decrypt$ ls
bin decrypt-htc keyfile lib place_rom_zip_here place_ruu_here readme.txt
[email protected]:~/decrypt$ ./decrypt-htc
�N��<Z"��@i�?|�w���U>I�t��k �*��TN� 8'B��8�m?�"w$�[email protected]�['��
bF��#��
[email protected]:~/decrypt$
Click to expand...
Click to collapse
Alright, 1.5.2 should take care of it. I'll have to figure out why only I can run the binary. But until then, might as well have a usable version available .
Captain_Throwback said:
Alright, 1.5.2 should take care of it. I'll have to figure out why only I can run the binary. But until then, might as well have a usable version available .
Click to expand...
Click to collapse
That worked. Thanks.
Here's a new tool for use with Titanium Backup - https://github.com/cjnaz/tibuscrape. I've found this tool to be extremely useful for backing out app revs and recovering older data.
tibuscrape creates an archive of the versions of apps and their latest data files from your Titanium Backup.
Each time that you update an app on your phone, Titanium Backup normally creates a backup of the .apk file and the associated data files (.properties and .tar.gz or .xml.gz). Each successive Titanium Backup run creates new data files up to your rolling "Max backup history" setting, and after that number of runs the older .apk version and it's data files are deleted forever.
For example, I have "Max backup history" set to 4 and run the backup nightly. This means that if I update an app I only have up to four days to find out that I'd rather stay on the older version.
This is where tibuscrape comes in: tibuscrape monitors your local Dropbox or Google Drive copy of the TitaniumBackup "Remote location" backup directory and keeps an "archive" copy of every backed-up .apk version and --the latest-- data files associated with that .apk version. tibuscrape does not modify or delete any files in the TiBU backup directory.
Code:
$ ./tibuscrape -h
usage: tibuscrape [-h] [-T TIBU_PATH] [-A ARCHIVE_PATH] [-n] [-l]
[--purge [PURGE]] [-s] [-v] [-V]
Titanium Backup Scraper
optional arguments:
-h, --help show this help message and exit
-T TIBU_PATH, --tibu-path TIBU_PATH
Path to the Titanium Backup directory.
-A ARCHIVE_PATH, --archive-path ARCHIVE_PATH
Path to the Archive directory.
-n, --dry-run Copy/delete no files.
-l, --list Print content of the Archive directory and exit.
--purge [PURGE] Keep only n most recent versions in the archive - default 3.
-s, --summary Print an operations summary.
-v, --verbose Print status and activity messages.
-V, --version Return version number and exit.
Example runs
Code:
$ ./tibuscrape -T /<path_to>/Dropbox/TiBU/ -A /<path_to>/TiBuScrapeArchive --summary
Archival transactions tally:
3 saved .apk.gz files
38 saved datafiles
35 deleted datafiles
2 skipped new datafiles (due to missing backup .tar.gz/.xml.gz file usually due to incomplete cloud sync)
Archive integrity checks tally (should all be 0, run with --verbose for more info):
0 missing .apk.gz files (Archive has .properties that references a non-existing .apk.gz)
0 missing .tar.gz/.xml.gz files (Archive has .properties but no matching .tar.gz/.xml.gz)
0 extra .apk.gz files (Archive has no associated .properties/.tar.gz datafiles)
0 extra .tar.gz files (Archive has .tar.gz but no matching .properties)
0 extra .xml.gz files (Archive has .xml.gz but no matching .properties)
0 extra datafiles (More than one datafile set for a given .apk.gz)
Archive contains backups for 76 apps with 214 total versions
Code:
$ ./tibuscrape -A /<path_to>/TiBuScrapeArchive --list
***** Archive current content and integrity checks *****
Amazon Kindle 8.14.1.0 -- Mon Jan 28 11:02:44 2019 -- d9082798a9deee56e5d392220ae2ddec -- com.amazon.kindle-20190128-175851
Amazon Shopping 18.1.0.100 -- Mon Jan 21 02:03:48 2019 -- 2b8027975f3419888e6c0e5e32d58407 -- com.amazon.mShop.android.shopping-20190121-090328
Amazon Shopping 18.2.0.100 -- Mon Jan 28 11:03:00 2019 -- 675a8939665613908ee908fadbbda99c -- com.amazon.mShop.android.shopping-20190128-180244
Bluetooth Connect and Play 3.19 -- Mon Jan 28 11:03:01 2019 -- dc8d7a66d5c2271b2fda8774ba3d1543 -- com.cp2.start.and.play.music.player-20190128-180300
Bluetooth Pairings -- Mon Jan 28 11:03:01 2019 -- none -- com.keramidas.virtual.BLUETOOTH_PAIRINGS-20190128-180301
bVNC Pro v4.0.1 -- Mon Jan 28 02:04:37 2019 -- 347ef1517f5ea7af5c0e5567ca79bc15 -- com.iiordanov.bVNC-20190128-090414
bVNC Pro v4.0.3 -- Mon Jan 28 11:03:25 2019 -- afcdaf4d8b4c670c24126ddc2c9b0edc -- com.iiordanov.bVNC-20190128-180301
b\u00b7hyve 1.7.30 -- Mon Jan 28 11:03:26 2019 -- 981f04bc7ae5b6b4ba64eaed4cdd1481 -- com.orbit.orbitsmarthome-20190128-180325
Calendar 6.0.12-224984167-release -- Thu Jan 24 02:04:35 2019 -- 7eb1f865be1747d48cb08acb5722c124 -- com.google.android.calendar-20190124-090432
Calendar 6.0.18-228718019-release -- Mon Jan 28 11:03:29 2019 -- 236fd5c0321e3fbd97d74995b8bac03e -- com.google.android.calendar-20190128-180326
CamScanner 5.9.0.20190116 -- Sun Jan 27 02:09:16 2019 -- 9a7bce8e67acd25e06385efeb3661fce -- com.intsig.camscanner-20190127-090651
CamScanner 5.9.1.20190126 -- Mon Jan 28 11:05:51 2019 -- 3fdd290f93765b1703c36ba1393fa7eb -- com.intsig.camscanner-20190128-180329
...
Google Play Books 5.0.5_RC04.227721962 -- Mon Jan 28 02:27:39 2019 -- 841e0b13dca884c33bcbec5e26cc628c -- com.google.android.apps.books-20190128-092147
...
Messages (SMS & MMS) -- Sun Oct 6 10:52:22 2019 -- none -- com.keramidas.virtual.XML_MESSAGES-20191006-174511
Plex 7.9.0.8439 -- Mon Jan 28 11:35:04 2019 -- dd229309cb03775a42a45f92b7d57b72 -- com.plexapp.android-20190128-183422
Podcast Republic 19.01.15R -- Sun Jan 27 02:37:17 2019 -- f92a636d822ea0d7fc89ce54f990d36d -- com.itunestoppodcastplayer.app-20190127-093706
Podcast Republic 19.01.28R -- Mon Jan 28 11:35:15 2019 -- 28be82cec85691945f1abe4d12418486 -- com.itunestoppodcastplayer.app-20190128-183504
...
xBrowserSync 1.4.0 -- Mon Jan 28 11:40:50 2019 -- e93715bb65db886a6c5d16b948689d9a -- com.xBrowserSync.android-20190128-184045
Archive integrity checks tally (should all be 0, run with --verbose for more info):
0 missing .apk.gz files (Archive has .properties that references a non-existing .apk.gz)
0 missing .tar.gz/.xml.gz files (Archive has .properties but no matching .tar.gz/.xml.gz)
0 extra .apk.gz files (Archive has no associated .properties/.tar.gz datafiles)
0 extra .tar.gz files (Archive has .tar.gz but no matching .properties)
0 extra .xml.gz files (Archive has .xml.gz but no matching .properties)
0 extra datafiles (More than one datafile set for a given .apk.gz)
Archive contains backups for 76 apps with 214 total versions
Anyone try this yet?
THERAJ12 said:
Anyone try this yet?
Click to expand...
Click to collapse
Apparently only me. I've been running this nightly for months. If the concept makes sense to you, give it a shot. I used it to recover an older "safe" version of CamScanner last September.