TPT-Hu: Packing "mainstream" ROMs?

[Guest aleckxander]

The idea come after i read and tried the TPT mode here: http://android.modaco.com/content/zte-blad...vices-to-512mb/

i'm just wondering...

Let's say that i may want to help the newbie community, or simply help some non-tecchie friend, how can i PACK a TPT file with a chosen custom rom?

looking into the image.zip file i see the same .img files that i can find in a common nandroid backup.

So i was wondering:

is it enough to swap the original .img files with the same files coming from a nand-backup done from a chosen custom rom??

it sounds too easy, expecially due to 2 main factors:

1- we know that partitions after a TPT change.

Is it enough that the above said nand-backup comes from an already TPTed phone? partition should be the same..

2- different recoveries generate different nand backups (i read this on the RA recovery thread)

I may sound noobish about all this.. well it's because i am :P

said that i'd like to help somehow, and since TPT is the most easy way i ever seen to install a ROM i'd like to help people that are uncomfortable with all these matters providing "mainstream" ROMs in a TPT way.

Tips and taunts are welcome :D

Edited January 10, 2011 by aleckxander

[Guest IronDoc]

You need to use a TPT template (sort of) with the right partition size. Kallt_Kaffe had a 128Mb system one and an Original size system one somewhere I think. Then just put in the images you want to overwrite and make sure they're named the same. Shouldn't matter if it was Clockwork or RA did the backup.

[Guest oh!dougal]

You need to use a TPT template (sort of) with the right partition size. Kallt_Kaffe had a 128Mb system one and an Original size system one somewhere I think. ...

First post in the Jellyfish thread, last time I looked.

You need to ensure that the download has no errors/corruption.

Its particularly important with Total Transplant installs.

So check the md5.

Astro File Manager will check the md5 of the file as loaded onto the phone, and extract it to the appropriate folder.

Flashing only needs two fingers (Vol+ and Power) not three.

Makes sense to rename (or discard) /image once it has flashed into the phone.

Obviously this method is not advised if your phone is an 880 or a 003z .... unless you want to try and turn it (permanently, for now) into an 'ordinary Blade' (but we don't know what would happen ... serious brick potential :D )

[Guest aleckxander]

mmmh sounds to risky to stick to my original intent.

i want to help new people with a easy-to-go flashing method, it makes no sense if it is to risky and/or it's good only for some model and/or changes the phone in a way that further modifications (assuming that a newbie won't be like that forever) are going to be too or more complicated :|

[Guest StevenHarperUK]

I do think having a return to stock TPT for all devices would be great.

These could be based on the Original Hungarian ROM with Boot and Recovery and System swapped.

Also maybe a TPT with just Recovery.img to install clockwork.

Just thoughts

[Guest oh!dougal]

mmmh sounds to risky to stick to my original intent.

i want to help new people with a easy-to-go flashing method, it makes no sense if it is to risky and/or it's good only for some model and/or changes the phone in a way that further modifications (assuming that a newbie won't be like that forever) are going to be too or more complicated :|

Risk - its important people check their downloads are perfect. We are talking about processor instructions, not dots in a picture! IMHO, its particularly important for this install method. But its actually important for any system software download.

There are too many "I'm stuck with a green android, help!" threads.

Checking the checksum routinely is an excellent habit to adopt.

Ease - the user needs to create a folder with a specific name, and extract the files into it. Astro (free from the Market) will do all of that. And it can also (as a earlier step) check the md5 checksum, in about 10 seconds or so.

Changes - the only functional "change" that the installer makes is to unlock hidden ram on "256mb" versions.

It can be configured to adjust partitioning (make more space for app storage), otherwise it resets the partitions to ZTE-original sizes (so no change unless it was previously changed).

Beyond those, it probably updates various hidden files to their latest version. No bad thing, but no visible difference.

Models - no-one on here has (so far) offered a rom for the Chinese and Japanese market "Blades" (the V880 and 003z) - which are running production FroYo anyway. Our roms won't work on those machines. But using this method to try and install an unsuitable rom would make things worse.

Those not-normal-Blades apart, this install seems to work happily on all 'normal Blades' (those that can take our roms).

I do think having a return to stock TPT for all devices would be great.

These could be based on the Original Hungarian ROM with Boot and Recovery and System swapped.

I've suggested this to Sebastian, and paricularly that it would be great to make sure that the output from his "romdump" script could produce boot, system, and recovery images ready to drop into a TPT /image folder.

But he seems to be having issues with his stock rom hosting that are occupying his time right now.

One obvious use of TPT is indeed to 'revirginate' phones back to stock.

Also maybe a TPT with just Recovery.img to install clockwork.

That is what kallt_kaffe has posted.

His idea is to put Clockwork as both recovery and normal boot, so that after adjusting partitioning, one is all set to run Clockwork and flash in whatever update zip one might choose.

It even makes for a small download ...

Edited January 10, 2011 by oh!dougal

[Guest IronDoc]

That is what kallt_kaffe has posted.

His idea is to put Clockwork as both recovery and normal boot, so that after adjusting partitioning, one is all set to run Clockwork and flash in whatever update zip one might choose.

It even makes for a small download ...

I think Steven meant as an alternative to fastboot, since it doesn't need any software.

[Guest oh!dougal]

I think Steven meant as an alternative to fastboot, since it doesn't need any software.

Yes, as I said, that is exactly what kk has already posted

http://www.mediafire.com/?xtckadj09b7sxt2 (16mb download)

MD5: C8010D841AF463F3CB1FDEDFFAFA3B1E.

After this you will have Clockwork Recovery as both boot and recovery image so you'll need to put a ROM on your SD-card and install.

(It also resets partitioning to standard, if it was changed.)

So after loading this TPT image, whether you boot normally or into recovery (Vol-), you find yourself in Clockwork, ready to load your zip format rom!

Edited January 10, 2011 by oh!dougal

[Guest aleckxander]

Risk - its important people check their downloads are perfect. We are talking about processor instructions, not dots in a picture! IMHO, its particularly important for this install method. But its actually important for any system software download.

There are too many "I'm stuck with a green android, help!" threads.

Checking the checksum routinely is an excellent habit to adopt. SOLD

Ease - the user needs to create a folder with a specific name, and extract the files into it. Astro (free from the Market) will do all of that. And it can also (as a earlier step) check the md5 checksum, in about 10 seconds or so. SOLD

Changes - the only functional "change" that the installer makes is to unlock hidden ram on "256mb" versions.

It can be configured to adjust partitioning (make more space for app storage), otherwise it resets the partitions to ZTE-original sizes (so no change unless it was previously changed).

Beyond those, it probably updates various hidden files to their latest version. No bad thing, but no visible difference. SOLD

Models - no-one on here has (so far) offered a rom for the Chinese and Japanese market "Blades" (the V880 and 003z) - which are running production FroYo anyway. Our roms won't work on those machines. But using this method to try and install an unsuitable rom would make things worse.

Those not-normal-Blades apart, this install seems to work happily on all 'normal Blades' (those that can take our roms).

I've suggested this to Sebastian, and paricularly that it would be great to make sure that the output from his "romdump" script could produce boot, system, and recovery images ready to drop into a TPT /image folder.

But he seems to be having issues with his stock rom hosting that are occupying his time right now. SOLD

Well you sold me all your points :P

Actually after properly underlined a couple of point this could be a really nice way to flash our (non-strange) blades.

Now my doubt (technical ones are tons) is one.. which line to follow? only "deliver" stock rom? stock rom with CWM? mainstream roms? only the winners of the weekly contest? :D

[Guest hecatae]

Well you sold me all your points :P

Actually after properly underlined a couple of point this could be a really nice way to flash our (non-strange) blades.

Now my doubt (technical ones are tons) is one.. which line to follow? only "deliver" stock rom? stock rom with CWM? mainstream roms? only the winners of the weekly contest? :D

my take on this got me to this.

http://android.modaco.com/content/zte-blad...01-05-oled-tft/

it's not ideal with just a stock image, as other members want automatic apn settings.

we should be able to build a stock eclair and a stock froyo and package them up with apn lists and a specific recovery.

[Guest tcpaulh]

So with TPT, partitioning doesn't take place where a partition already exists with the required size/type/offset?

I was kinda hoping it could re-initialise partitions to help fix badly configured devices. You know, delete all partitions (except any hidden ones with SPL code I guess) then re-create them

Could one be put together that does this?

Edited January 10, 2011 by tcpaulh

[Guest IronDoc]

Yes, as I said, that is exactly what kk has already posted

http://www.mediafire.com/?xtckadj09b7sxt2 (16mb download)

MD5: C8010D841AF463F3CB1FDEDFFAFA3B1E.

(It also resets partitioning to standard, if it was changed.)

So after loading this TPT image, whether you boot normally or into recovery (Vol-), you find yourself in Clockwork, ready to load your zip format rom!

I (and Steven I think) mean that if you don't put in a boot or system, then it is exactly as if you just flashed clockwork with fastboot. You just don't have the hassle of downloading it and the necessary drivers. That said, it's probably quite a rare use case when someone wants to install clockwork but keep their current ROM.

[Guest oh!dougal]

So with TPT, partitioning doesn't take place where a partition already exists with the required size/type/offset?

...

No, it overwrites what is there.

If what was there was the standard partitioning, and the TPT installer is as-Hungarian-original, there is no change to the partitioning.

Using a patched version of this installer is the only means known. thus far, for users to alter the partitioning.

[Guest oh!dougal]

I (and Steven I think) mean that if you don't put in a boot or system, then it is exactly as if you just flashed clockwork with fastboot. You just don't have the hassle of downloading it and the necessary drivers. That said, it's probably quite a rare use case when someone wants to install clockwork but keep their current ROM.

I don't think the installer has been tested with payload parts missing. (Be my guest!)

Whether or not you could use a totally empty image for boot and system (and thereby hopefully leave the existing partition content untouched), I really don't know -- but I do strongly doubt it.

I think in that case, the installer is going to put in 'partition catalog' entries to indicate that the partition is 'empty' (as with initialising a disk).

I started calling this thing the Total Phone Transplant, because it seems to set out to replace all the accessible and changeable firmware in the phone.

It wants to rewrite everything

There is pre-Linux setup and load software that is not accessible from a normal running phone.

But its all in the Hungarian update ... and almost totally undocumented!

If anyone thinks they know how to get the thing to leave specific partition contents in place and ready to run again, please share that knowledge!

In the meantime, kk's image, linked above, provides a "no special software, or pc, required" method of installing Clockwork, and from there, any 'conventional' zipped rom.

[Guest IronDoc]

I don't think the installer has been tested with payload parts missing. (Be my guest!)

Whether or not you could use a totally empty image for boot and system (and thereby hopefully leave the existing partition content untouched), I really don't know -- but I do strongly doubt it.

I think in that case, the installer is going to put in 'partition catalog' entries to indicate that the partition is 'empty' (as with initialising a disk).

I started calling this thing the Total Phone Transplant, because it seems to set out to replace all the accessible and changeable firmware in the phone.

It wants to rewrite everything

There is pre-Linux setup and load software that is not accessible from a normal running phone.

But its all in the Hungarian update ... and almost totally undocumented!

If anyone thinks they know how to get the thing to leave specific partition contents in place and ready to run again, please share that knowledge!

In the meantime, kk's image, linked above, provides a "no special software, or pc, required" method of installing Clockwork, and from there, any 'conventional' zipped rom.

I thought you could leave out the imgs. I'm fairly certain I deleted cache last time I used it, or does it get wiped anyway?

Edit: If you download KK's JJ image it has no recovery, so yeah you can leave stuff out.

Edited January 10, 2011 by IronDoc

[Guest hecatae]

kallt kaffe left out the recovery.img.

there is nothing to stop trying the reverse, insert clockork or ra as recovery and remove boot.img and system.img

what happens if you combine a 2.2 boot.img with a 2.1 system.img ?

Edited January 11, 2011 by hecatae

[Guest isambard]

you can leave out some images (also the amss files). i can't remember if it wipes the partitions when you leave it out or not.

you can mix and match boot and system images. though when i tried i had a non-working touchscreen and thought that this was due to the mis-match, but later realised it was a hardware fault.

Edited January 11, 2011 by isambard

[Guest hecatae]

okay, mixing a 2.2 boot.img and 2.1 system.img