I found this on http://cliq-development.com/forums/viewtopic.php?f=5&t=13
hopefully this can help anyone who is trying to develop a way for root on the cliq.
To get where we are at in development you must learn about a few things
.SHX = A re-flashing file similar to a .nbh on the HTC brand. It is a full re-flash of everything on the phone, full stock. When extracted it creates three files the main one is the CG2
CG2 = A file extracted from the shx that hold the main partitions that will be flashed to the phone.
-----------------------------------------------------------------------------------------------------------------------
How to extract a shx
(http://modmymoto.com/forums/showthread.php?t=525344)
A developer by the name of Meiner Einer created a program named SbfRecalc. With this program we can extract three files and as i stated above the most important one is the CG2
How to extract a CG2
(http://modmymoto.com/forums/showthread.php?t=525477)
A developer by the name of Skrilax_CZ created a program named CG2 Parser. With this program we can extract all of the files within the CG2.
-----------------------------------------------------------------------------------------------------------------------
After you extract all of the files from the CG2 you will find that some of the names were similer to the partitions of the cliq. With a little file manipulation i recreated a boot.img and a recovery.img from some of the files. The guys over at modmymoto dumped a full system partition.
(http://android-dls.com/wiki/index.php?t ... oot_Images)
To recreate both the boot.img and the recovery.img just do these simple steps
1. Create a directory and put either bootsec.mbn or recoverysec.mbn from the CG2 dump inside it
2. Download the split_bootimg.pl from the link above and run it with the file in the directory to get both a kernel and a ramdisk file.
3. Using the mkbootimg from the android source code you can recombine the kernel and the ramdisk files to create your boot.img/recovery.img strait from the re-flash file
------------------------------------------------------------------------------------------------------------------------
With the system dump from modmymoto and my boot.img(+a little root) I created an update.zip file with root ready to be flashed when the keys are ready.
This is where we are at any help would be greatly appreciated.
Wow, nice work!
This could really so with a sticky...
Thanks for the update! The cliq goes hard. Once rooted its ova, best android phone on tmo!
Nice! It would be really great if you could repost this at android-devs.org over in the cliq development section of the forum
Since XDA is only for HTC phones and most people here most likely don't have the cliq and there really isn't a correct forum to have this posted in..
I'd reccomend using android-devs.org forums
Hello all,
I am looking for a good comprehensive guide to creating my own .zip files to flash certain changes I like to make when flashing a rom or just adding files.
Now I have found a few good guides here on XDA but they seem to no longer apply as the update script needs to be in edify and not amend. This is the issue I am having so if anyone can point me to a walk through that explains this type of thing I would appreciate it.
Anyone?
lol, i dont think developers/people-with-knowledge would go into a Q&A sub-forum .
I'm neither on of them, however here is my would-be-successful attempt p) :
1- Make all your modifications and finalize them, the root folder must be /system/ .
2- use apktool to recompile as an apk (apktool b system)
3- sign that .apk.
4- rename extension to zip and violla
theoretically, it should work.
Not shure if this can help you, but i created a zip (original Script is from dungphp) to replace files on my device from CWM:
http://forum.xda-developers.com/showthread.php?t=1241244
Hello, I would like to know how I could extract backed up TWRP data on my computer? maybe because the data was large TWRP split it into two files : data.ext4.win000 and data.ext4.win001 (sizes 1.5 and 1.2 GB)
How I got there:
I've been using XenonHD rom for quite a while, and this rom uses koush's superuser app.
I noticed there was a newer version on the market so I installed it; however it appears the one used by the rom developer was modified and therefore had a different package name: I ended up with two superuser apps, one of them asking to update the binaries, which I did.
After that the phone got stuck and rebooted two or three times before being stuck indefinitely at 'updating app' message right after the bootanimation. I tried:
- to wipe dalvik cache but it was still stuck;
- I reflashed the rom + gapps but it was still stuck;
- then I went to the /data/app/ folder (via TWRP) and deleted the superuser app i installed from market, as well as the corresponding data in /data/data, wiped cache and dalvik again: still the same...
-the I decided to make a backup via TWRP : one of the whole system, and one of Data partition only;
- then I realised I couldn't transfer it to my computer in TWRP, so I finally made a factory reset, re-flashed the rom+gapps, and then (it worked) copied my backup to the computer
now; how can I retrieve the data of my apps only, as I guess it is the system data that is messed up?
Of course I tried to restore the Data backup in twrp and it got stuck again the same way....
any help greatly appreciated!
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
forvrknight said:
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
Click to expand...
Click to collapse
It actually helped me, thanks a lot!
Two Questions
asim0 said:
On this file I used AccessData FTK Imager,
Click to expand...
Click to collapse
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
asim0 said:
All you have to do now is to merge the two data folders and voilà
Click to expand...
Click to collapse
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
pi_yush said:
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
Click to expand...
Click to collapse
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
number_thirty_two said:
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
Click to expand...
Click to collapse
Thanks number_thirty_two, I copyed thes to a folder I named untar in my home folder of CYGWIN, and extracted my system files perfectly
C:\cygwin\home\carl\untar\
system.ext4.win000
system.ext4.win001
tar xvfz system.ext4.win000
tar xvfz system.ext4.win001
Apologies for resurrecting this, but does anyone know how to extract them if they were compressed as .comp files?
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voil
Click to expand...
Click to collapse
Hey all, I've looked all over an can't find the answer to this... I have a NAND backup I made using TWRP, however, I had the problem many have had with getting errors when trying to restore it. So I thought I'd try a different way by creating a TWRP flashable file from the NAND files. I have taken the files from the backup and extracted them using CYGWIN. I read a thread here:
https://forum.xda-developers.com/showthread.php?t=2746044
But I'm stuck on a couple of things... First, the part about using the META-INF folder from another ROM... I've checked the files in in the META-INF folder and notice that the updater-script is what loads the files and directories. But none of the META-INF files I have found matches my backup files.
The files I want to flash are the complete system folder, complete data folder and the boot.img file. Is it possibly to flash these with TWRP without the META-INF folder/files? If I have to use the META-INF how do I make sure all the files and folders are flashed?
Would it be better to create an ODIN flashable file and just use Odin to do the flash? If so should I put the system and data folders into one file and then use the boot.img (or would I put the boot.img finle into a tar) in the Bootloader spot in Odin?
Thanks in advance.
Hello everyone, I wanted to open a new thread, maybe others like me found themselves in the same siditura, that is, to be able to extract a saved file, backed up with TWRP the file in question, was initially saved in.snb format, file an app. pre-installed on the S3Neo, and it's called SMemo, the file contains sensitive data and password, you will say but because it does not restore the backup, if you want, but the saved one there are data that are not in another file, I made two backups , with the data inside, are in various formats, some I add immediately after, now what I ask, you can find that file and extract it using a PC with windows7 system, thank you in advance.
- recovery.emmc.win.md5
-system.ext4.win000.md5
-recovery.log
-data.ext4.win001
-data.ext4.win000
-boot.emmc.win
-recovery.img
and others similar with different formats. :fingers-crossed: