Big Bear 2.1 build same as official

[Guest Richard_Arkless]

Hi guys I came to the realization earlier that the build that big bear leaked is exactly the same build as the official 2.1 release

I think the only reason why we were having so many problems with reboots and force closes was because we were using an older fastboot

Want proof extract the updata.app using split_updata.pl provided below and compare file 16 and file 23 with this link http://www.2shared.com/file/NG1axNZ1/files.html ,that big bear provided us when he made the mistake and posted the recovery image instead of the actual boot image when he leaked the 2.1 build here

http://android.modaco.com/content/t-mobile...air-rom-thread/

If you want more proof download the update.zip provided in the link directly above this and then go back to the files that were extracted from updata.app and get file18.mbn anddownload this to extract it, http://code.google.com/p/unyaffs/ in linux type in ./unyaffs file18.mbn (system image) and compare the files with each other, it should be exactly the same minus that big bear actually rooted it and added a2sd support

so what I am getting at is we can use the old 2.1 mcr build provided by paul, move lib back over and remove the symbolic links from the update-script file under meta-inf/com/google/android and put it in a zip and resign it

install ra recovery in official 2.1 and then flash the zip that you have made and now you have got a2sd support and root support and we can even do the same with shadows custom rom

sorry if I was rambling on but I dont see why people are waiting for paul to release a mcr when he has already done it

split_updata.pl.zip

Edited May 29, 2010 by Richard_Arkless

[Guest thisweb]

Hi guys I came to the realization earlier that the build that big bear leaked is exactly the same build as the official 2.1 release

I think the only reason why we were having so many problems with reboots and force closes was because we were using an older fastboot

Want proof extract the updata.app using split_updata.pl provided below and compare file 16 and file 23 with this link http://www.2shared.com/file/NG1axNZ1/files.html ,that big bear provided us when he made the mistake and posted the recovery image instead of the actual boot image when he leaked the 2.1 build here

http://android.modaco.com/content/t-mobile...air-rom-thread/

If you want more proof download the update.zip provided in the link directly above this and then go back to the files that were extracted from updata.app and get file18.mbn anddownload this to extract it, http://code.google.com/p/unyaffs/ in linux type in ./unyaffs file18.mbn (system image) and compare the files with each other, it should be exactly the same minus that big bear actually rooted it and added a2sd support

so what I am getting at is we can use the old 2.1 mcr build provided by paul, move lib back over and remove the symbolic links from the update-script file under meta-inf/com/google/android and put it in a zip and resign it

install ra recovery in official 2.1 and then flash the zip that you have made and now you have got a2sd support and root support and we can even do the same with shadows custom rom

sorry if I was rambling on but I dont see why people are waiting for paul to release a mcr when he has already done it

Interesting, sounds good , so does this mean that if we update to 2.1 official T-mob Hungary update.app (with partition resizing etc) , reinstall Recovery Boot, then install Paul/Bobos v6.1 (2.1beta) rom (or shadows vanilla v7) it should work just the same. Only now with the added bonus of a2sd and root? Or is that to simple. Are the steps above required first. If so, any chance you can create a rom? :(

Have you tested this

[Guest MarcusHenrique]

Interesting, sounds good , so does this mean that if we update to 2.1 official T-mob Hungary update.app (with partition resizing etc) , reinstall Recovery Boot, then install Paul/Bobos v6.1 (2.1beta) rom (or shadows vanilla v7) it should work just the same. Only now with the added bonus of a2sd and root? Or is that to simple. Are the steps above required first. If so, any chance you can create a rom? :(

Have you tested this

If you apply any previously custom rom won't work, since partitions are different... You'll have to wait untill the devs cooks custom roms for the official update..

[Guest thisweb]

If you apply any previously custom rom won't work, since partitions are different... You'll have to wait untill the devs cooks custom roms for the official update..

:(

sigh..its all gone quiet here on that development since yesterdays excitement :(

[Guest Richard_Arkless]

If you apply any previously custom rom won't work, since partitions are different... You'll have to wait untill the devs cooks custom roms for the official update..

Strange I just applied the rom that paul made but moved lib over to system (and changed the update-script) and it worked fine, both root and a2sd

If you apply any previously custom rom won't work, since partitions are different... You'll have to wait untill the devs cooks custom roms for the official update..

Well thats the thing, I think the one that paul made is the same as the official so its final not beta

Anyway this is the process, just update to official rom and install ra recovery

move lib over to system in pauls custom rom, change update-script and repack it and resign and flash

Edited May 29, 2010 by Richard_Arkless

[Guest MarcusHenrique]

Strange I just applied the rom that paul made but moved lib over to system (and changed the update-script) and it worked fine, both root and a2sd

Yes just update to official rom and install ra recovery

move lib over to system, change update-script and repack it and resign and flash

Hm.. so maybe that's the way to make it work. I think what Paul did to fit the beta release on pulse was moving lib. So you've just reverted the processs... =)

[Guest MrLowHoe]

:o

sigh..its all gone quiet here on that development since yesterdays excitement :(

Damn right its gone quiet :o too bad I'm not techy to do it myself. Anyway, It good time a vanilla custom rom based on the offical 2.1 should be released soon. I'm waiting for that instead of making do with T-Mobile 'not so nice' interface.

:(

[Guest MarcusHenrique]

Damn right its gone quiet :( too bad I'm not techy to do it myself. Anyway, It good time a vanilla custom rom based on the offical 2.1 should be released soon. I'm waiting for that instead of making do with T-Mobile 'not so nice' interface.

:(

I hope you're right.. I own U8220-6 and t-mo update won't work on my device =/

[Guest Richard_Arkless]

I dunno if installing mcr 1.5 rom is possible though, someone will have to try that

[Guest gusthy]

Hi guys I came to the realization earlier that the build that big bear leaked is exactly the same build as the official 2.1 release

I think the only reason why we were having so many problems with reboots and force closes was because we were using an older fastboot

Want proof extract the updata.app using split_updata.pl provided below and compare file 16 and file 23 with this link http://www.2shared.com/file/NG1axNZ1/files.html ,that big bear provided us when he made the mistake and posted the recovery image instead of the actual boot image when he leaked the 2.1 build here

http://android.modaco.com/content/t-mobile...air-rom-thread/

If you want more proof download the update.zip provided in the link directly above this and then go back to the files that were extracted from updata.app and get file18.mbn anddownload this to extract it, http://code.google.com/p/unyaffs/ in linux type in ./unyaffs file18.mbn (system image) and compare the files with each other, it should be exactly the same minus that big bear actually rooted it and added a2sd support

so what I am getting at is we can use the old 2.1 mcr build provided by paul, move lib back over and remove the symbolic links from the update-script file under meta-inf/com/google/android and put it in a zip and resign it

install ra recovery in official 2.1 and then flash the zip that you have made and now you have got a2sd support and root support and we can even do the same with shadows custom rom

sorry if I was rambling on but I dont see why people are waiting for paul to release a mcr when he has already done it

It is false. It is not fastboot, it is the firmware upgrade made by hungarian update that stabilizes 2.1.

ROMS with >100 in their numbers after letter "C" have correct firmware for 2.1. I used a C104 firmware without a single reboot, and it had the old fastboot.

For curiosity I tried all available C>100 1.5 ROMS and all was stable.

This UPDATA.APPs were all made in April.

If you applied Hungarian update, your firmware will be updated, so of course, also all roms based on BoBo's leak will be stable.

On the other hand, it is really true that BoBo kernel and official kernel are identical except for 1 byte. And also, the linux binaries are the same, differences are only in Java side.