• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root TU Android Update 2.3.6

Oh shit really? Well I tried it and it aborted installation three times so I'm gonna delete that one and wait for the one labeled safe version.
 
Thanks for this and a small request....I would do it myself but I'm short 1 TU. Can you check this new update for the presence of CIQ? I'm interested in knowing if Boost is serious about getting rid of CIQ.
 
I was wondering if anyone also receive the "over-the-air" update on the Boost Mobile Samsung Transform Ultra? I received it this morning and keep getting it popping up but I can't do the update due to my phone having the CWM installed. Is this the same update? And if it is, how can I go about installing it. CWM can't boot this for some reason.....
 
interdpth said:
Once again, the one I will be releasing is CWM safe. For like the third time.
Click to expand...

I just thought you meant it would delete CWM, not that it wouldn't work with it. That was my mistake man. :o

My main question though is if this happens to the same update that was pushed to my phone today or does that just happen to be coincidence?
 
So if it only fixes the touch screen issue, why should we upgrade if we are running Bob's new kernel that is already CWM & SU friendly?? Is anything else included in the update?
 
The update fixes the touch screen, updates the phone to Android 2.3.6, and hopefully removes carrier IQ but still waiting on someone to confirm the latter. I'm not sure what else yet.
 
it's a firmware and software update . not a hot fix . baseband should be alot better ( cmda and evdo should have better signal ). drivers should be trimed and stable ( the screen bug gone hopefully) . android should be cleaner ( ciq gone hopefully plus other things wait and see atm) . overall its a needed update. and if you don't want stock wait a week or two the rom dev's here will have it tweaked :] . relax and it'll be worth it
 
Ok. New to this crap.... I did have my phone rooted and I know better than running the update without reserching it first. So now after the over the air update my phone is not rooted. Tried to reroot it and no workie Can someone help????????? :(
 
2000bravada said:
Ok. New to this crap.... I did have my phone rooted and I know better than running the update without reserching it first. So now after the over the air update my phone is not rooted. Tried to reroot it and no workie Can someone help????????? :(
Click to expand...
I'm sure interdpth would be glad to help you...thats what he is there for anyway!

:musicus:
^^^^^^^^^ There you go interdpth....I sent a response for you so you can have more time making a rooted zip and less time answering the same question for the 4th time.

Edit: Let me explain this a little better so I don't hurt anyones feelings: Interdpth is developing a rooted zip to flash with CWM that will fix all the problems with failed updates. Developing such things takes time. If you really want to help him, hit his donate button and send him a few bucks.
 
:o its 5:32 and its not done you lieeee ... no i keed i keed i know it takes time just trying to be silly
 
From the updater-script(edited for brevity):

ui_print("Removing unneeded files...");
delete("/system/bin/iqmsd","/system/lib/libiq_client.so", "/system/lib/libiq_service.so")

But.....and this is a BIG but(pun intended)....it looks like everything has to be stock or the update will fail and leave a mess behind...as interdpth is unfortunately finding out now.....
_____________________________________________________________________

Edit: More info....the updater-script verifies files in /system but does not flash the kernel till later:

apply_patch("EMMC:/dev/block/mmcblk0p8:4468736:8ff468aad3df4901b506dc3ff6579487f5812aa6:4472832:fafa28534994de883c7d48df488cdb53a1a67224",
"-", fafa28534994de883c7d48df488cdb53a1a67224, 4472832,
8ff468aad3df4901b506dc3ff6579487f5812aa6, package_extract_file("patch/boot.img.p"));

I suppose if the /system patches are applied but that ^^^ fails, you would get a reboot into recovery so make sure you have the stock kernel flashed before you do the OTA update. I would suggest using Odin to flash back to stock recovery just to be safe but I don't know yet if that is necessary.

Edit2:
applypatch EMMC:/dev/block/mmcblk0p8:4472832:fafa28534994de883c7d48df488cdb53a1a67224 EMMC:/dev/block/mmcblk0p13 0e3e73ed806dcb0ec7f823846936ebe748968d38 4722688 fafa28534994de883c7d48df488cdb53a1a67224:/system/recovery-from-boot.p

Looks like it overwrites recovery no matter whats there.
 
You must log in or register to reply here.
Back
Top Bottom