http://androidspin.com/2010/10/18/rom-leaked-for-the-t-mobile-mytouch-htc-glacier/
think we can use this to extract the wifi-calling and other goodies to our G2s?
Not until write protection is disabled...
Sent from my T-Mobile G2 using XDA App
For anyone that would like to open it up and look at what is inside the ROM, it is a RAR file. Once you have it downloaded change ZIP to RAR and open it.
The contents:
Code:
android-info.txt 73
boot.img 2,994,176
hboot_0.86.0000.nb 1,048,576
radio.img 25,427,968
rcdata.img 114
recovery.img 4,042,752
splash1.nb0 786,432
system.img 585,101,312
72,945 tp_atmel224_20aa.img 72,945
72,289 tp_atmelc12_20aa.img 72,289
userdata.img 1,232,072,704
I do not know what the userdata.img is yet, but it is big. Maybe the Apps already installed to SD? Oh, maybe user data like videos, games, music. That makes sense.
android-info.txt contains:
Code:
modelid: PD1510000
cidnum: T-MOB010
hbootpreupdate:2
mainver: 1.14.531.1
-Unconnected
Edit: maybe I should find some other place to post this data (too?)
That wifi call stuff requires more than just an app. IIRC there's a kernel module and VPN connection to deal with. Extracting these from the MyTouch rom is dubious, but not impossible. The write protection is still the limiting factor at the moment.
userdata is just your user partition.
It's an (almost) empty preformatted ext3 to dd.
You can mount-loop it as ext3 and browse through the contents.
Can anybody post a mirror? I've tried a few times to get it with no luck... :-/
Related
Hello,
I have a zip file which contains boot.img, hboot.nb0, radio.img, recovery.img, splash1.nb0, system.img and userdata.img.
Also there is a text file called android-info with the following content:
modelid:CLIC10000
cidnum:HTC__001
cidnum:HTC__102
cidnum:HTC__203
cidnum:HTC__E11
cidnum:HTC__016
cidnum:HTC__032
cidnum:HTC__Y13
cidnum:HTC__506
cidnum:HTC__304
cidnum:HTC__405
cidnum:HTC__N34
cidnum:11111111
mainver:1.65.405.1
Click to expand...
Click to collapse
It is a tattoo rom.
My question is, if I flash hboot.nb0 to my phone and my phone's cid is not in the above list, will it kill my phone?
Also, how do I get the cid of my tattoo knowing that I dont have root access?
Thank you
First of all: Tool to be used in this guide was developed by user And_pda from Russian 4pda.ru forum. So all credits must go to And_pda
The original thread (in Russian) is here. Actually the original thread is about several tools to works with different images for different phones. But we will talk only about Moto X.
The guide will describe how to extract all files from system partition from stock firmware. The tools works under Windows (I personally tested it on Win 7).
If you unzip any stock firmware you will find one file, which represents system partition: system.img.
To extract all files from system.img please do:
1. Download ImgExtractor_1_3_4.rar and extract it.
2. Create directory System in the folder where system.img is located;
3. Copy ImgExtractor.exe into the folder where system.img is located;
4. Run CMD and "cd" to the folder where system.img is located
5. In CMD run the following: ImgExtractor system.img System
After ImgExtractor finished you will have all system files and folders in System directory.
That's all
PS. ImgExtractor also can extract modem firmware (NON-HLOS.bin)
Anyway to extract system image on 4.4, inject su binary re-image, and msfastboot flash?
Sent from my XT1080 using Tapatalk
djnikko said:
Anyway to extract system image on 4.4, inject su binary re-image, and msfastboot flash?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Maybe. But to get the locked recovery to flash it must be signed by moto thousand bit code.
extract for something like my signature?
Hey this will mos def save some time. Thanks my dude
Sent from my XT1095
Can you get this to work with motoboot.img? It'll make it possible to downgrade to bootloaders such as 4-21, 3-15, etc.
mr_verystock said:
Can you get this to work with motoboot.img? It'll make it possible to downgrade to bootloaders such as 4-21, 3-15, etc.
Click to expand...
Click to collapse
Phone's cid partition changes with every firmware update so bootloader downgrade will not work. The phone just won't boot up. I know the man who tried all this tricks - he flashed dumps from phones with unlocked bootloaders.
Pretty cool tool... I just wished it would keep the original timestamps for the directories and files....
Is there any way to assemble extracted files and build original system files?
Sent from my SM-N910C using Tapatalk
Latest version if any need it
It can't handle large img files though.
works on Samsung Galaxy S6 , Note 4 , cache.img , hidden.img , files which ext4 unpacker couldn't handle.
How big were the img files? It can't handle the 4GB LG G4 .img files but works fine with the smaller Motorola RAZR HD Maxx .img files.
i used it only for cache and hidden, so <250MB. I didn't tried on larger files.
That's why it works.... the Motorola img files were 1 GB or less... it can't handle the LG G4 files.
it would be great if the author patched/forked the original ext4 unpacker, so it can open newer img's like this (sparse with moded header) , so we would've had a GUI, because imgextractor is only text.
imgextractor is the only one that works on Motorola img files.
yes, even with Samsung Galaxy Note 4 / S6 and newer devices, on the IMG file - the ext4 sparse header is not standard, but i said, since this program (imgextractor) is based on ext4 unpacker sources, it could've keeped that GUI and only mod a little.
Anyway, you could also open IMG with the original ext4 unpacker if you fix it first with IMGEXTRACTOR. to fix: convert IMG file from MODED SPARSE EXT4 to normal EXT4 (> imgextractor.exe original.img temp.ext4 -conv) and then back to FIXED SPARSE EXT4 (> imgextractor.exe temp.ext4 fixed.img -conv). Now open fixed.img in ext4 unpacker program and it will work.
l.e. I found what the problem was, on Samsung Exynos devices, and the newer ones, the IMG files headers are 32 bytes, instead of the normal 28, Chainfire explains it here. So that's why ext4 unpacker gives error on opening. For alternative fix (instead of the conversion i explain upper in this post using imgextractor) you can use Chainfire's sgs4ext4fs tool , works on Windows/Linux, builds and other useful tool here.
Also there is a tool for Motorola IMG files there, see the Usage section.
gracias
tanks bro work in motorola razr hd stock kitkat system.img
BenjaminW8 said:
can you maybe make a more detailed guide how you did this
i cant seem to make sytem.img to extract for the s7 Edge
Click to expand...
Click to collapse
I believe you want be able to utilize Imgextractor as the S7 system.img exceeds the supported size of the Imgextractor
If anyone has a REAL GPE or a converted GPE you will notice you can't flash any ROMS without getting errors. I investigated into this and this is what I found. The system partition is only a little over 1 gig where the sense system partition is 2.8 gb. So if you try to flash a sense rom on a GPE or a converted HTC m8. It will fail (because the partition is too big for the gpe partition). The only way to correct this is to flash a sense RUU when it's available.
I'm working on a new GPE conversion RUU that will use a bigger system partition. If this works (which I'm not sure it will) then it will be easy for people who to convert to go back..
Just figured I'd let everyone know.. This was NOT tha case with the m7!
Here is a df from a real GPE (non converted)
/system 1006.7M 778.0M 228.6M 4096
Mine after conversion:
/system 1006.7M 779.1M 227.6M 4096
Can someone do a df on a sense version?
Using adb
Type adb shell
Then df
Thanks for that info, very good to know!
Sent from my LG-V510 using Tapatalk
Wow! Glad I didn't convert yet! Here's a pic of it
Sent from my HTC One_M8 using XDA Premium 4 mobile app
I converted not worried about it at all tho. On a side note graffix do you have the GPE hboot pulled? If so can you upload it or add it to your recovery thread, want it to edit out the red dev text lol.
djkinetic said:
I converted not worried about it at all tho. On a side note graffix do you have the GPE hboot pulled? If so can you upload it or add it to your recovery thread, want it to edit out the red dev text lol.
Click to expand...
Click to collapse
It's already there I posted it last night in the stock recovery thread.
Sent from my HTC One_M8 using Tapatalk
subscribed. :fingers-crossed: will guinea pig if safe
Can't you just flash sense (htc) hboot.img? Won't that change the partitions.
Remember on my desire I used to modify the hboot to make a bigger system partition.
No one seems to have sent you this yet so... Here is a stock Sense
/system 2641M 2062M 579M 4096
backfromthestorm said:
Can't you just flash sense (htc) hboot.img? Won't that change the partitions.
Remember on my desire I used to modify the hboot to make a bigger system partition.
Click to expand...
Click to collapse
I tried that and it didn't work. Maybe a modified hboot but not the normal one.
Sent from my HTC One_M8 using Tapatalk
Do you need a signed ruu? Or can you just have someone dump from a sense rom the same partitions changed with the conversion?
Are the bootloaders different because of this?
Sent from my HTC PG09410 using xda app-developers app
scotty1223 said:
Do you need a signed ruu? Or can you just have someone dump from a sense rom the same partitions changed with the conversion?
Are the bootloaders different because of this?
Sent from my HTC PG09410 using xda app-developers app
Click to expand...
Click to collapse
You don't need a signed one I don't think. But the issue is with the system image. RUU mode complains the image is too big. Jmz Taylor was saying that there is a size limit on the system images that be flashed in fastboot/ruu mode. So they need to be split.. And each zip run after each other in ruu mode. Maybe a signed one does deal with the system image differently (not sure)
If you do a Google search on split system image ruu, you'll see a few examples. Jmz sent me a template to use and I was able to split the system image and I flashed the first one and it flashed correctly, the 2nd part failed.. I'm going to try again though.. One more time to see if I can get it to work.
Sent from my HTC One_M8 using Tapatalk
graffixnyc said:
You don't need a signed one I don't think. But the issue is with the system image. RUU mode complains the image is too big. Jmz Taylor was saying that there is a size limit on the system images that be flashed in fastboot/ruu mode. So they need to be split.. And each zip run after each other in ruu mode. Maybe a signed one does deal with the system image differently (not sure)
If you do a Google search on split system image ruu, you'll see a few examples. Jmz sent me a template to use and I was able to split the system image and I flashed the first one and it flashed correctly, the 2nd part failed.. I'm going to try again though.. One more time to see if I can get it to work.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I really hope it works. I'm really mad at myself for doing the conversion. Are you in Colorado now?
Sent from my HTC One_M8 using Tapatalk
graffixnyc said:
You don't need a signed one I don't think. But the issue is with the system image. RUU mode complains the image is too big. Jmz Taylor was saying that there is a size limit on the system images that be flashed in fastboot/ruu mode. So they need to be split.. And each zip run after each other in ruu mode. Maybe a signed one does deal with the system image differently (not sure)
If you do a Google search on split system image ruu, you'll see a few examples. Jmz sent me a template to use and I was able to split the system image and I flashed the first one and it flashed correctly, the 2nd part failed.. I'm going to try again though.. One more time to see if I can get it to work.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
hmm that makes sense,now,lol. a couple weeks ago a set up the ruuveal tool to decrypt ruus,and when i broke down m7 rom.zip from 4.19.401.9 it gave me 5 more zip files,instead of a bunch of images.
the first contains adsp thru tz. the next 3 each contain 2 android info documents and a system image,lables system_1,system_2,system_3 inside their respective zips. the last one contains different dz_data and tp.
at first glance,the zip files all appear the same:
Code:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
mainver: 4.19.401.9
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
numofsystem: 3
indexofsystem: 1
sizeofsystem: 629145600
even tho the system zips,each have a second one named android-info-1,android-info-2,android-info-3,matching the the number of the system image inside that particular zip. if thats confusing,the sustem zips each contain: androit-info.text , android-info-x.txt , and system_x.img
sorry if youre allready aware of all this,the point is that you prolly just need to get the android info documents correctly worded/formatted,and the system images all named correctly. not sure if we can manually flash the zips one at a time,or need to zip them all up together somehow with yet another text document inside my ruuveal folder,all there was were the zips,i dont recall it showing anything else in there.
if you need a i can upload this decrypted ruu somewhere for you to look at,or copy/paste the rest of the android info documents. as soon as i get my m8 set up,ill try and flash them all and see what happens. that may be a couple days,tho.
**
the other thot that i had,is it possible to simply DD system back instead of using ruu/fastboot? what about DDing back the whole phone(mmcblk0) ?
housry23 said:
I really hope it works. I'm really mad at myself for doing the conversion. Are you in Colorado now?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, sir I am
scotty1223 said:
hmm that makes sense,now,lol. a couple weeks ago a set up the ruuveal tool to decrypt ruus,and when i broke down m7 rom.zip from 4.19.401.9 it gave me 5 more zip files,instead of a bunch of images.
the first contains adsp thru tz. the next 3 each contain 2 android info documents and a system image,lables system_1,system_2,system_3 inside their respective zips. the last one contains different dz_data and tp.
at first glance,the zip files all appear the same:
Code:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
mainver: 4.19.401.9
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
numofsystem: 3
indexofsystem: 1
sizeofsystem: 629145600
even tho the system zips,each have a second one named android-info-1,android-info-2,android-info-3,matching the the number of the system image inside that particular zip. if thats confusing,the sustem zips each contain: androit-info.text , android-info-x.txt , and system_x.img
sorry if youre allready aware of all this,the point is that you prolly just need to get the android info documents correctly worded/formatted,and the system images all named correctly. not sure if we can manually flash the zips one at a time,or need to zip them all up together somehow with yet another text document inside my ruuveal folder,all there was were the zips,i dont recall it showing anything else in there.
if you need a i can upload this decrypted ruu somewhere for you to look at,or copy/paste the rest of the android info documents. as soon as i get my m8 set up,ill try and flash them all and see what happens. that may be a couple days,tho.
**
the other thot that i had,is it possible to simply DD system back instead of using ruu/fastboot? what about DDing back the whole phone(mmcblk0) ?
Click to expand...
Click to collapse
Yeah, I'm aware of the different info files I used a template zip that JMZ sent me.. hmm dding the whole system image might work.. I didn't think of that before..It could fail, but it might work.
@housry23 I'm uploading a system.img now from my AT&T version as well as my boot.img from it. Once it's done uploading I'll post the link and directions what I want you to try to get back into sense. If you don't mind giving it a try that is.
graffixnyc said:
Yes, sir I am
Yeah, I'm aware of the different info files I used a template zip that JMZ sent me.. hmm dding the whole system image might work.. I didn't think of that before..It could fail, but it might work.
@housry23 I'm uploading a system.img now from my AT&T version as well as my boot.img from it. Once it's done uploading I'll post the link and directions what I want you to try to get back into sense. If you don't mind giving it a try that is.
Click to expand...
Click to collapse
Let me know how it goes.
if the boot/system fail,I think it's worth a shot to dd the whole phone and see what happens.
Sent from my HTC One using Tapatalk
I'll try too...Link me as well
graffixnyc said:
Yes, sir I am
Yeah, I'm aware of the different info files I used a template zip that JMZ sent me.. hmm dding the whole system image might work.. I didn't think of that before..It could fail, but it might work.
@housry23 I'm uploading a system.img now from my AT&T version as well as my boot.img from it. Once it's done uploading I'll post the link and directions what I want you to try to get back into sense. If you don't mind giving it a try that is.
Click to expand...
Click to collapse
I don't mind at all. Just let me know.
Sent from my HTC One_M8 using Tapatalk
Ok, well I'm out at the moment (on vacation in Colorado) I'm uploading a system IMG at the house (we are out to dinner)
Sent from my HTC One_M8 using Tapatalk
graffixnyc said:
Ok, well I'm out at the moment (on vacation in Colorado) I'm uploading a system IMG at the house (we are out to dinner)
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Take your time. Enjoy your vacation man. This can wait for sure!
Sent from my HTC One_M8 using Tapatalk
Hi, I've been trying to make sparse system.img from firmware tar file into a twrp-flashable zip file but I'm not sure which is the best way.
All operations are performed on latest linux mint and I'm not going to use any kitchen. All binaries used to convert images are compiled from latest AOSP sources.
Here are some of the methods I've tried.
a) Extract everything from system.img and set metadata infos in updater-script, just like any other "rom"s. (e.g. SuperMan Rom)
Probably one of the simplest ways, and system files inside the zip can be modified easily - extract, edit, recompress.
But this method has a potential of destroying unique permissions/owner infos, such as those of symlinks.
I'd like to flash the system.img "as-is," without making a mess with whatever's inside the image.
b) Extract raw system.img directly to /dev/block/platform/155a0000.ufs/by-name/SYSTEM.
Not so bad. Raw system.img can be easily generated with simg2img. But turns out to take too much time to flash and doesn't get along well with DualBoot patcher.
c) Sparse dat, like the ones used in most AOSP-based roms
Probably the most ideal one. But when I took the following steps to make it, I found out that system partition size gets kinda damaged or something.
- Convert system.img to raw system.img with simg2img.
- Convert the raw system.img to sparse image again with ext2simg, to make img2sdat.py work properly.
- Convert the sparse image to sparse dat with @xpirt's img2sdat.py.
- Finally, convert the generated sparse dat to raw system image with sdat2img.py to check if partition size matches.
Then I get the following results.
- Size of original raw system.img : 4404019200
- Size of raw system.img generated in last step : about ~100MB smaller
I know I can loop mount system.img and then make a new sparse image with make_ext4fs,
but it also breaks some permissions and make_ext4fs won't recognize file_contexts.bin from nougat firmware whereas it worked well with marshmallow's.
If anyone's got a better method or a solution for method c please leave a reply. Thanks in advance.
Hi all,
Is there a tool that can unpack system.img for the Pixel 4 (that actually works..) ?
What I want is to create a system.img that will have the following change:
Replace the below apex zip file:
`/system/apex/com.android.runtime.release.apex`
to an extracted version of it:
`/system/apex/com.android.runtime.release`
I've tried most of the online tools and tutorials with no luck.
So I unzip the ` flame-qd1a.190821.007` factory image, and then unzip the `image-flame-qd1a.190821.007` within in.
This gives me many .img files, including system.img, system_other.img, and super_empty.img.
I guess in some phones super.img had included the system.img, but that's not the case with `flame`.
imjtool can extract the `system.img` using:
Code:
imjtool system.img extract
With the below warning:
Warning: system.img is likely truncated or still compressed
Sparse image v1.0 detected, 196053 blocks of 4096 bytes
196053 blocks of 4096 bytes compressed into 15 chunks (1% compressed)
Click to expand...
Click to collapse
Then `extract/image.img` cannot be further recognized by the tool:
Code:
imjtool extracted/image.img
extracted/image.img is not a recognized image. Sorry
Click to expand...
Click to collapse
I've also tried simg2img to convert a sparse android img to a normal one,
but then mounting failed, in both Linux and mac.
Paschalis said:
Hi all,
Is there a tool that can unpack system.img for the Pixel 4 (that actually works..) ?
What I want is to create a system.img that will have the following change:
Replace the below apex zip file:
`/system/apex/com.android.runtime.release.apex`
to an extracted version of it:
`/system/apex/com.android.runtime.release`
I've tried most of the online tools and tutorials with no luck.
So I unzip the ` flame-qd1a.190821.007` factory image, and then unzip the `image-flame-qd1a.190821.007` within in.
This gives me many .img files, including system.img, system_other.img, and super_empty.img.
I guess in some phones super.img had included the system.img, but that's not the case with `flame`.
imjtool can extract the `system.img` using:
Code:
imjtool system.img extract
With the below warning:
Then `extract/image.img` cannot be further recognized by the tool:
Code:
imjtool extracted/image.img
I've also tried simg2img to convert a sparse android img to a normal one,
but then mounting failed, in both Linux and mac.
Click to expand...
Click to collapse
I use SuperR Kitchen
It unpacks everything. You must then use Apktool or third party software (ticklemyandroid) to decompile and recompile apks for editing. I don't have a way to edit a .apex file.
Here is the file in question. Just rename it by taking off the .zip. only way I could upload it.
https://www.androidfilehost.com/?fid=8889791610682898672
The full Android SDK. But it's definitely not a beginner friendly process. If you have to ask how to do it then you probably shouldn't try it until you learn more. ?