How to get back to RC29? by modifying the update script?
I' chose to update to RC30 while didn't know that update fixed up the permission problem.
I wanted to roll back to RC29 then I tried to do update to the RC29 package.
Failed at the first line of update script:
assert getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,test-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,test-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,test-keys"
Click to expand...
Click to collapse
I'm gonna try to append one condition to this line: "|| 1"
But is there any side effect by doing this?
And, I don't know if this will work, since I don't quite know the update package's format.
I think is kind of sun's jar file, and plus a update script in META-INF folder, two cert files(one of this also keeps the sha1 of the manifest file's sha1sum).
Can someone give me some advice?
fluke.l said:
I' chose to update to RC30 while didn't know that update fixed up the permission problem.
I wanted to roll back to RC29 then I tried to do update to the RC29 package.
Failed at the first line of update script:
I'm gonna try to append one condition to this line: "|| 1"
But is there any side effect by doing this?
And, I don't know if this will work, since I don't quite know the update package's format.
I think is kind of sun's jar file, and plus a update script in META-INF folder, two cert files(one of this also keeps the sha1 of the manifest file's sha1sum).
Can someone give me some advice?
Click to expand...
Click to collapse
As soon as you change one byte in the update.zip folder, the update won't verify against the signature, and will fail.
I've tried.
How did you modify the update.zip?
Did you package it in jar way -- which will count the sha1sum of each file and put into MANIFEST.MF?
How do the phone verify the update.zip? by cert files or just check the sha1sum?
Question: what happens, if I try to apply rc29 from SD card (i.e. signed-kila-ota-115247-prereq.TC4-RC19_RC28) after getting RC30 OTA on my G1?
1. update fails
2. update bricks the phone
3. I can have my root back
Does the name _really_ mean that TC4-RC19 is the only thing it will install over?
What checks are actually made before it bootstraps a SD card update.zip?
Can someone comment on the likely result before I get impatient and discover it is #2, please
Doesn't work but doesn't brick
I just tried it. The update will fail, but you won't brick the phone.
this may be a dumb question but why can't the modded RC30 update just be signed with the OTA keys and then used as an update.zip from the SD card?
dagentooboy said:
this may be a dumb question but why can't the modded RC30 update just be signed with the OTA keys and then used as an update.zip from the SD card?
Click to expand...
Click to collapse
Because only {Google,T- Mobile,HTC} have the OTA private keys needed for creating an OTA signed file.
I guess the only hope is google/t-mobile releasing a full update
Downgrade from RC30 to RC29
I have been reading up on the modded RC30 and haven't seen anyone mention this, so here it goes:
My phone had been taking forever to get OTA updates - I didn't get any notifications until the 11th. I wanted to keep root access so I never applied it, but downloaded the RC29 update and installed that manually. I was planning on updating to the modded RC30 once I had some free time. This morning I accidentally allowed the OTA update - damn thing popped up as I was clicking something else. I figured I was stuck with the official RC30 update.
At the end of the first part of the update it gives you the normal recovery prompt - reboot, install update from sdcard, or show/hide text, so I figured I'd try to install RC29 over RC30 (even though I'd heard it's impossible). It worked! I guess until the phone has fully installed the update, you can re-flash whatever update you have on the card. This probably won't help too many people, but if you accidentally allow the OTA update like I did and still have an update on the card this could save you!
Nice to know. Thanks
so if i let it reboot after it installed the update than im pretty much screwed for now?
ChrisAshton84 said:
I have been reading up on the modded RC30 and haven't seen anyone mention this, so here it goes:
My phone had been taking forever to get OTA updates - I didn't get any notifications until the 11th. I wanted to keep root access so I never applied it, but downloaded the RC29 update and installed that manually. I was planning on updating to the modded RC30 once I had some free time. This morning I accidentally allowed the OTA update - damn thing popped up as I was clicking something else. I figured I was stuck with the official RC30 update.
At the end of the first part of the update it gives you the normal recovery prompt - reboot, install update from sdcard, or show/hide text, so I figured I'd try to install RC29 over RC30 (even though I'd heard it's impossible). It worked! I guess until the phone has fully installed the update, you can re-flash whatever update you have on the card. This probably won't help too many people, but if you accidentally allow the OTA update like I did and still have an update on the card this could save you!
Click to expand...
Click to collapse
U Said your Phone taking foreever to get Update
This means you must be on RC19 and phone was trying to get Full RC30 from google.
Becuase of Full update it paused some where and ask you to reboot, Becuase Patch RC30 Update dont ask for it.
Please Explain you Full Situation !!
yup i got stuck with the RC30 update about an hour ago. was dialing a number and it popped up and i accidentally pressed update now! it bites, oh well
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
I'm mad that I didn't decline the update to rc30!!!!!!!
ChrisAshton84 said:
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
Click to expand...
Click to collapse
Thanks for your reply
hmm, possible reasons
it seems to me (very close to a complete moron) that the updates get copied to a "ramdisk"(4 lack of a better term) then when you see that arrow going into the chip after reboot is when its written from this "ramdisc" to the flash?
maybe its just the hash talkin take it for what it is an educated guess... AKA a theory.
bhang
ChrisAshton84 said:
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
Click to expand...
Click to collapse
great tip this is bound to help many others, anybody by any chance know when the next update is coming out?
I tried to Simulate Same thing
1. I already had Updated the phone to Stock RC30 and
2. I Copied RC30 on to SDCard as update.zip
3. Started into Recovery Modem and Pressed ALT+S
4. The Phone Started Verifying the File
5. Then i have Format Boot, System Partition
6. Copied some thing to Phone and asked me to Press Home+Back
7. I pressed it and its flahed Radio Image and reboot in recovery ode twice and did something.
In your Case the Phone might have Extracted the Images into Ramdisk but it might didnt flashed it to phone really and between that u got that Reboot Option and Reflashed the Full RC29 again.
We can reflash the same Version as many time we like but we can not flash lower version as the Recovery command dont allow.
If we keep RC30 as Update and remove the SDCard in between and put a new Card with Update.zip of RC29 the phone unmount the SDCard and then it dont detects the new SDCard is inserted and flashes error so Simulating your Process by Swapping 2 SDcard with RC30 and later on RC29 dont work for me.
If i could place RC30 into Phone and then Try to Simulate that it got the RC30 update frmo Internet and in between flash it with RC29 from SDcard might help me. But i am still not sure.
Downgrade from official RC30 to RC29 ?
My try to change some file on my system then my font was brick . But I use recovery mode, update to official RC30 then I phone worked again. But I want to acess my phone again. Please tell me how to downgrade to RC29 from official RC30 ?
Related
Hot off the presses. Get it here.
That file is the crappy "patch" version that tries to patch you from RC29 to RC30.
Here is the full update, which should be much more reliable
Obviously, don't install it unless you want to lose root access
Update for those who are interested: I went ahead and bought myself a new G1. One of the stores in the area had a couple. It still had RC28 (not RC29) on it, so I'm back in business. I'll just unlock my RC30 one and sell it on ebay.
OMG how stupid can they be... look what I see in the update script
# delete unneeded files
delete SYSTEM:system/bin/telnetd
Click to expand...
Click to collapse
Can we patch this like today cause I kinda think there is more to this than just doing that.
neoobs said:
OMG how stupid can they be... look what I see in the update script
Can we patch this like today cause I kinda think there is more to this than just doing that.
Click to expand...
Click to collapse
There is. They added a kernel option "console=null", which I suspect basically makes it so that the physical keyboard no longer sends input to the console device. Note that there is still a root shell running on the console though.. it's just that now there isn't any way to send keypresses to that root shell.
Plus there are a ton of patches to the android apps and framework jars and such. Not sure what all changed there.
I'm in the process of modifying the patch, to apply to my phone without losing root access. More to come
What does the "applypatch" piece do?
That part looks different.
Interesting that it's only a 4 meg update, and that it only contains a new recovery.img and a new boot.img - I wonder what is different in those images. I hope they are keeping the recovery stuff in the open source branch updated - because, well, that's the nice thing for them to to do
Jesus Freke - when you get your patched-up version ready, please post it somewhere for us lazy bastards who want to ride your coat-tails
I just noticed something. This update doesn't wipe the system partition. If you had created a setuid copy of the shell ("su", or whatever), I don't think it will get deleted if you applied the update as-is.
but didn't you say it removes the use of keyboard in shell? If so we would still be up the creek. you know what a notice this update came really fast i never got and OTA until this(fishy) i had to force OTA. Well hope you work your magic JesusFreke.
Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Oh, btw - I was wrong about the update keeping the setuid shell around. It completely wipes the permissions of the system folder, so if you did have a setuid copy of the shell, it will be set back to normal non-setuid status by the update. duh.
Sh**!! You were the shining hope , one question can you still get root through the adb shell? cuz if so you can save your a**
Nope. Like I said, I'm out of the game. Unless someone wants to trade me for a RC19/RC29 phone. Or until another root exploit is found. *sigh*
DOH! That sucks! Sorry to hear that, and thanks for taking one for the team.
So if an update does try to install do we just need to turn off the phone until a solution is found? I may need to go back to my Dash for a while until this all gets figured out!
The update that you meant to put on the card- was it a test? If the worst that will happen is the update will take maybe someone that doesnt mind the update could test it for you?
JesusFreke said:
Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Click to expand...
Click to collapse
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?
Can not we flash back that old RC29 File again ????
The update zip contains the boot.img and the recovery.img. so when the update starts it rewrites JesusFreke's mod recovery.img
spoofing
could we spoof the version # on our device? thus ending the nag and the ability to force the upgrade, for the time being?
bhang
RegGuheert said:
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?
Click to expand...
Click to collapse
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
Ahh! That's a pain in the arse... the usb mass storage process is running as root, any chance of a buffer exploit there?
JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
koush said:
mount -oremount,rw /dev/block/mtdblock3 /system
You can't remount that directory that unless you have root.
Use the dd command to copy stuff around (the cp command is not available). I should mention I'm a Windows guy, and am pretty clueless with Linux: my coworker figured the rest of this out once I got to a root prompt.
Incidentally, in the /system/bin directory there is a flash_image executable that changes the recovery.img used when you hard reset the device. I've noticed that I can run this without root access from a standard adb shell. Maybe we never needed to root the device after all... I think we can flash it without root access... I'm too scared to mess with that at all though.
Click to expand...
Click to collapse
I found this, you may want to look into it.
syrusfrost said:
I found this, you may want to look into it.
Click to expand...
Click to collapse
Thanks. But you have to have root access for the flash_image command to work. Or more precisely, you have to have write access to the /dev/mtd/mtd# device that you are trying to flash.
I am also the same unlucky guy who had Press Update Button and now we are in RC30
Now what are the chances of our device to get root access or ability to flash Test_Signed code in RC30
well i removed( # delete unneeded files delete SYSTEM:system/bin/telnetd )and replaced the boot.img and recovery.img with jesusfreke's anything else i should edit before i try to resign and update?
Okay, I had ordered another phone from ebay. The guy had just received it and it was new and unused. It has RC28 on it.
fingerprint= kila-user 1.0 TC4-RC28 114235 ota-rel-keys,release-keys
When I launch /system/bin/telnetd from terminal console I am not getting root. I do not see a process running when I run ps afterwards. Also, I tried typing reboot from the contact, and it is not recycling the phone.
Any chance they have updated the init.rc to close the console bug on an older RC for phones just shipping out from tmobile this past week?
I plan to update to the stock RC29 which I manually updated to on my other phone. I'd really like root before I update to the new RC30 modded, so I can back up my files before overwriting them. [Though, last time I upgraded Google did OTAs right away.]
** Anybody want me to explore the phone for any differences to the standard RC28 to see if the cause for the exploit not working?
-oldsk00lz
Just go ahead and install the official RC29 and you should be able to get root access
Are you sure it's not working? IIRC if you don't connect to telnetd fairly fast, it stops running for some reason. I know that I've had to run it a couple times before I could connect.
As for the root console bug, I've also heard that it closes after some time of the phone being on. Did you try it after a fresh reboot?
Updating to RC28 or RC29, the ones that we mirrored, should activate the console bug again, if they are fixing it.
Yeh, it was not working (telnetd/console exploit) on the RC28 I had. I tried hitting enter to clear any previous commands, tried rebooting, tried back to back calls with telnet right afterwards, telneting locally and from several boxes. Was weird.... Much different than another G1 I had. That's why I was surprised.
Only thing I could think of (besides a tweaked RC28) was that my router could have been acting up.
Anyhow, I moved forward with updating to RC29, getting root, updating to modded RC30, and all is good. Just wanted to throw this out there in case any other recent buyers encountered a similar issue.
SIDENOTE: JesusFreak lived up to his name. I was slightly "freaked" out after the recent upgrade. I went to the System settings and looked to be the standard RC30 fingerprint!!! versus the modded xda one. Thought I may have installed the stock update. :O But, everything else is as expected, root, root, and more root. I must have missed a message if he reverted back to the standard fingerprint.
-oldsk00lz
oldsk00lz said:
SIDENOTE: JesusFreak lived up to his name. I was slightly "freaked" out after the recent upgrade. I went to the System settings and looked to be the standard RC30 fingerprint!!! versus the modded xda one. Thought I may have installed the stock update. :O But, everything else is as expected, root, root, and more root. I must have missed a message if he reverted back to the standard fingerprint.
-oldsk00lz
Click to expand...
Click to collapse
Indeed, I thought the same thing, but it is much, much, much better this way. If JesusFreke left the fingerprint to be the same as the old one, Google would be able to target OTA updates specifically for rooted G1s. This way, if they release an update signed with the test keys, they'd have to have millions of non rooted G1s freak out because they couldn't update.
Gary13579 said:
Indeed, I thought the same thing, but it is much, much, much better this way. If JesusFreke left the fingerprint to be the same as the old one, Google would be able to target OTA updates specifically for rooted G1s. This way, if they release an update signed with the test keys, they'd have to have millions of non rooted G1s freak out because they couldn't update.
Click to expand...
Click to collapse
Not quite...
First, I don't think Google cares for those of us having root with RC30 moded recovery and keys. They really only care about patching the "average consumers" phone. They have to do it globaly (I mean in the distribution sense) not to get in trouble, or a BIG bug wich is what was patched.
Second, they only have to do the following if they want to put "us" back to stock (if we don't check the update of course AND don't pay attention and apply the update [BIG IF]):
Script the rewrite of recovery.img from their package (before rebooting in the background) to our phones and apply the update.... ... ... that's it.
This will get a bit of the "unaware" people who have root with RC30. But for the more savey of us, no.
quedijo said:
Script the rewrite of recovery.img from their package (before rebooting in the background) to our phones and apply the update.... ... ... that's it.
This will get a bit of the "unaware" people who have root with RC30. But for the more savey of us, no.
Click to expand...
Click to collapse
And what good would secretly rewriting recovery.img do? Once JF replaces the recovery.img with the modified one, it doesn't matter how many times they write it to flash, it's still modified.
They don't need to use the update package to take away your root. With modified RC30, any dalvik program that knows and wants to can write directly into /system. If they wanted to get draconian about it, they could push code down from Market to reflash whatever they want in /system.
You said "With modified RC30, any dalvik program that knows and wants to can write directly into /system".
Aren't these apps sandboxed? If they do have access to /system, I assume they would only have access if they ran su, assuming you didn't rename it, and was able to remount system as read/write.
Or am I missing something like a different exploit? root on 'my' phone is great for me, but not good for others.
-oldsk00lz
oldsk00lz said:
You said "With modified RC30, any dalvik program that knows and wants to can write directly into /system".
Aren't these apps sandboxed? If they do have access to /system, I assume they would only have access if they ran su, assuming you didn't rename it, and was able to remount system as read/write.
Or am I missing something like a different exploit? root on 'my' phone is great for me, but not good for others.
-oldsk00lz
Click to expand...
Click to collapse
Yeah, by invoking su. Deleting or renaming it is probably the safest bet for now. I doubt any Android devs are actively looking for phones to brick but better safe than sorry.
a new workaround for our very insecure rooted RC30
I just read a post here about a better fix for the issue.
This very smart cat, added a password routine to SU and judging by my read of the post it seems to be well implemented, you do have to type some commands and you could pooch your g1 but it seems better than runnin just about as wide open as goog had us...
Without a decent browser getting the link is a pita, if somebody can't find it ill link it when I'm at the desktop
Bhang
*EDIT*
I found the link its just a pain in the arse while typing a message, to all the helpful folks who will want to tell me how to do it, I know how I just think it could be easier
http://forum.xda-developers.com/showthread.php?t=448775
I just bought a new G1 and I would like to prevent it being firmware updated to the official RC30 so I can become root. I have already seen the update firmware screen and clicked on update later.
How can I be sure the firmware is not updated?
How may I know my current firmware version?
follow this tread to get modify RC30 update and your done http://forum.xda-developers.com/showthread.php?t=443797
info about your current version you can find under settings/about phone/ build number
Some good step-by-step instructions are at http://android-dls.com/wiki/index.php?title=Keeping_Root
I have a RC29, I want to keep root and I am not going to upgrade to RC30 right now. the only thing I need to flash is the modified recovery img, right?
Correct. Once you do, no more annoying update messages, and continued root access
or you can just rename the otacerts.zip file and reboot and it won't prompt you any more
alapapa said:
or you can just rename the otacerts.zip file and reboot and it won't prompt you any more
Click to expand...
Click to collapse
That won't stop the prompts; it will only make the update fail on the crypto check. To stop the prompts you need to kill the update service process.
jashsu said:
That won't stop the prompts; it will only make the update fail on the crypto check. To stop the prompts you need to kill the update service process.
Click to expand...
Click to collapse
I didn't have to do that.
all i did is mount system rw and rename the otacerts.zip file and reboot.
no prompts -- was getting them aplenty before that too
jashsu said:
That won't stop the prompts; it will only make the update fail on the crypto check. To stop the prompts you need to kill the update service process.
Click to expand...
Click to collapse
IIRC, it checks the OTA update before it prompts you. So renaming otacerts.zip should stop the prompts as well.
signed-PLAT-RC33-from-RC30.f06aa9b3.zip
Only RC30 Users can Update to this Package RC28 or RC29 can not do that, Rooted users will require it to resign it with TestKeys or Else Wait for JF modded Version
The links are as Below
https://android.clients.google.com/updates/signed-PLAT-RC33-from-RC30.f06aa9b3.zip
http://64bit.in/signed-PLAT-RC33-from-RC30.f06aa9b3.zip
http://www.megaupload.com/?d=AMR2SBT8
http://rapidshare.com/files/194349437/signed-PLAT-RC33-from-RC30.f06aa9b3.zip.html
http://www.mediafire.com/download.php?ytzw24fmyyj
THIS FILE is SIGNED WITH ORIGINAL Google Private Keys so ALL ROOT Users wait for JF to come with JF33
Or if you have Knowledge to Rapir Recovery and Boot Image out of this and Sign it with Test Keys and Update it to your G1.'
Seeing into System Folder the Package Update so many Library, OpenCode Media Library, WLan Patch, Framework.Odex and Framework-res.apk is also Patched to Handle APK Updates from Android Market.
Gmail, IM, Browser, Search etc also have been Patched bu dont know whats have been done for that.
Fresh Packages Included
app\IM.odex
app\SystemUpdater.apk
app\SystemUpdater.odex
app\TmoImPlugin.apk
app\VoiceSearch.apk
app\VoiceSearch.odex
Radio Image Included
radio.img 20.8 MB
Patches Included
AlarmClock.apk.patch0
AlarmClock.odex.patch0
Browser.apk.patch0
Browser.odex.patch0
Bugreport.apk.patch0
Bugreport.odex.patch0
Calculator.apk.patch0
Calculator.odex.patch0
Calendar.apk.patch0
Calendar.odex.patch0
CalendarProvider.apk.patch0
CalendarProvider.odex.patch0
Camera.apk.patch0
Camera.odex.patch0
com.amazon.mp3.apk.patch0
Contacts.apk.patch0
Contacts.odex.patch0
DownloadProvider.apk.patch0
DownloadProvider.odex.patch0
DrmProvider.apk.patch0
DrmProvider.odex.patch0
Email.apk.patch0
Email.odex.patch0
FieldTest.apk.patch0
FieldTest.odex.patch0
GDataFeedsProvider.apk.patch0
GDataFeedsProvider.odex.patch0
Gmail.apk.patch0
Gmail.odex.patch0
GmailProvider.apk.patch0
GmailProvider.odex.patch0
GoogleApps.apk.patch0
GoogleApps.odex.patch0
GoogleSearch.apk.patch0
GoogleSearch.odex.patch0
gtalkservice.apk.patch0
gtalkservice.odex.patch0
HTMLViewer.apk.patch0
HTMLViewer.odex.patch0
IM.apk.patch0
ImProvider.apk.patch0
ImProvider.odex.patch0
Launcher.apk.patch0
Launcher.odex.patch0
Maps.apk.patch0
MediaProvider.apk.patch0
MediaProvider.odex.patch0
Mms.apk.patch0
Mms.odex.patch0
Music.apk.patch0
Music.odex.patch0
MyFaves.apk.patch0
MyFaves.odex.patch0
PackageInstaller.apk.patch0
PackageInstaller.odex.patch0
Phone.apk.patch0
Phone.odex.patch0
Settings.apk.patch0
Settings.odex.patch0
SettingsProvider.apk.patch0
SettingsProvider.odex.patch0
SetupWizard.apk.patch0
SetupWizard.odex.patch0
SoundRecorder.apk.patch0
SoundRecorder.odex.patch0
Street.apk.patch0
Street.odex.patch0
Sync.apk.patch0
Sync.odex.patch0
Talk.apk.patch0
Talk.odex.patch0
TelephonyProvider.apk.patch0
TelephonyProvider.odex.patch0
Updater.apk.patch0
Updater.odex.patch0
Vending.apk.patch0
Vending.odex.patch0
VoiceDialer.apk.patch0
VoiceDialer.odex.patch0
YouTube.apk.patch0
YouTube.odex.patch0
awesome
cant wait for JF to pick this apart..
hetaldp said:
signed-PLAT-RC33-from-RC30.f06aa9b3.zip
The links are as Below
https://android.clients.google.com/updates/signed-PLAT-RC33-from-RC30.f06aa9b3.zip
http://64bit.in/signed-PLAT-RC33-from-RC30.f06aa9b3.zip
http://www.megaupload.com/?d=AMR2SBT8
Click to expand...
Click to collapse
Anybody know if it is OK to go ahead and load if we already have root?
Nice work mate.
Keep it coming
texasaggie1 said:
Anybody know if it is OK to go ahead and load if we already have root?
Click to expand...
Click to collapse
If you load this you will most certainly lose root I would wait until JF puts out a Modded version.
Nice, i already got tired of waiting
All Root Users Just wait for JF33
As this is Original Signed Update Package and will not load on rooted G1 as rooted G1 have Test key Signed Recovery Mechanism.
Good to see it Just on 5th Feb.
JF, Koush are you seeing this.
hiteshpatel80 said:
Good to see it Just on 5th Feb.
JF, Koush are you seeing this.
Click to expand...
Click to collapse
i kinda have the feeling they are too busy modifying to respond at the moment - LOL
For those who cant wait..... Wouldn't it be possible to try it out on emulator? like this http://androidcentral.com/cupcake-android-emulator/??? I dont know if it work, just throwing ideas.
I looked at the file there doesn't appear to be a new mountd.conf or init.rc... Is this an indication that if we've hacked "programs on SD" that this may still work if we apply this update? Just wondering as I would hate to lose that ability because of an update. Otherwise, this is great news... Just copy the file in it's current fashion to the SD or rename update.zip? That's the only other question. Also, no change in the bootloader... Interesting. I'll be excited to see what JF comes up with!!!
This is a Step forward to cupcake as Voice Search, Market Update Facility etc. were planned to be rolled out in Cupcake.
We have to wait for 4 or 5 such Updates to have Cupcake in our Mouth
Damn I just got it & was about to post it up too! Sweet hopefully we have it soon!
I just got my G1 2 days ago and I wanna get RC33. Now my question is, when i follow the instructions from the "Rooting, Hacking and Flashing" thread, can I simply download the RC33.zip instead of downgrading to RC29 then installing the RC33?
If you are not Interested Rooting the Device go on and raname Rc33 zip file to
update.zip and place it in Memory Card and Press Home + Power Button Constantly while booting and load RC33 right into the G1
DeFiant*X said:
I just got my G1 2 days ago and I wanna get RC33. Now my question is, when i follow the instructions from the "Rooting, Hacking and Flashing" thread, can I simply download the RC33.zip instead of downgrading to RC29 then installing the RC33?
Click to expand...
Click to collapse
If you are downgrading to RC29 you are probably wanting to root your phone with an upgrade to a modified RC30.
RC33 was JUST pushed by Tmobile and hasn't been modified yet. Meaning if you go through all that trouble of rooting your phone, you will lose it by going to RC33.
I would suggest if you wanna keep root to wait for a modified version of RC33.
hetaldp said:
signed-PLAT-RC33-from-RC30.f06aa9b3.zip
The links are as Below
https://android.clients.google.com/updates/signed-PLAT-RC33-from-RC30.f06aa9b3.zip
http://64bit.in/signed-PLAT-RC33-from-RC30.f06aa9b3.zip
http://www.megaupload.com/?d=AMR2SBT8
http://rapidshare.com/files/194349437/signed-PLAT-RC33-from-RC30.f06aa9b3.zip.html
THIS FILE is SIGNED WITH ORIGINAL Google Private Keys so ALL ROOT Users wait for JF to come with JF33
Or if you have Knowledge to Rapir Recovery and Boot Image out of this and Sign it with Test Keys and Update it to your G1.
Click to expand...
Click to collapse
Woot! way to go HetalPatel
I'll get to work on it once I get off work this evening. Should have it by 8-9pm (central US time)
Thank you. I'm just gonna run RC33 and wait for JF before I root.
hetaldp said:
If you are not Interested Rooting the Device go on and raname Rc33 zip file to
update.zip and place it in Memory Card and Press Home + Power Button Constantly while booting and load RC33 right into the G1
Click to expand...
Click to collapse
JesusFreke said:
Woot! way to go HetalPatel
I'll get to work on it once I get off work this evening. Should have it by 8-9pm (central US time)
Click to expand...
Click to collapse
Should have it working for us or just getting the file?
http://androidguys.com/?p=3572
This is the Stock 8.6.5.13 US update repackaged with:
* Clockworkmod support (It does not include CWM, but doesn't reflash the recovery partition either)
* Rooted (includes SuperUser.apk & su 3.0.0)
* Busybox (1.19.2)
This update worked fine on my TF101. I built it using the same method Roach2010 used to make his previous CWM-repacks so it should be ok. I have only tested this on my own tf101. Let us know when it works for yours too!
This will not work unless you have:
1. clockworkmod
2. STOCK firmware (root is fine)
3. the US or WW firmware
4. firmware 8.6.5.9
If this update will not apply, take note of which assert stopped the process. You probably applied some sort of mod to your transformer.
There was an issue in the initial release. If you downloaded it, delete it and download the new one.
CWM package for ASUS FOTA Update 8.6.5.13 US
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-proper.zip
Problems updating? Customized Transformer? Try the Update checker.
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-checker.zip US
The Update checker will verify all of the same files that the update verifies. It will not stop on the first error. This way, you can see ALL the files which will cause errors and fix them all at once without the tedious reboot / try update / reboot / fix problem / reboot / try update loop.
Courtesy of brk:
CWM package for ASUS FOTA Update 8.6.5.13 WW (with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5
Has this been tested yet??
Thanks
*Offtopic*
delete ffs
same here, stock but with xoom system UI and bloatware deleted.
Sorry, in my haste I didn't update the recovery binary.
Fixed version in testing now.
Updated first post, new zip is available here:
http://bellybuttonporn.com/transformer/kwt-cwm-8.6.5.13-proper.zip
cky2000 said:
for me, it did not work.
I tried from a fresh/clean install (nvflash) of US_epad-user-8.6.5.9. and got this error in CWM:
assert fail: getprop ("ro.product.device") == "EeePad" || getprop ("ro.product.device") "EeePad"
E:Error in /sdcard/kwt-cwm-8.6.13.zip
(Status 7)
Installation aborted.
bellybuttonporn
Click to expand...
Click to collapse
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.
Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John
Cordy said:
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.
Click to expand...
Click to collapse
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).
Xerravon said:
Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John
Click to expand...
Click to collapse
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)
ryan stewart said:
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).
Click to expand...
Click to collapse
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?
The issue is I have it back on my device, I found it, and the update is still hanging on that.
daoist said:
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)
Click to expand...
Click to collapse
Hi,
Thanks for the help! It worked like a charm, no problems at all.
I am wondering now, do I need to update my CWM recovery, or do I just leave it how it is?
thanks for the file and help!!!
Now I just have to figure out how to get rid of the notification...
Has anyone noticed the web browser performance? Is it still checkerboard on display? Where it displays the page in chunks... and is this android 3.2.1? or just firmware update?
Worked fine on mine, Thx.
daoist said:
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?
Click to expand...
Click to collapse
Would it be possible to remove the check and the patch? I am looking at the updater script, what I would love is to just remove its check and attempt at patching the bloatware.
For Example, the Check:
assert(apply_patch_check("/system/app/Finsky.apk", "19a70336522820f20a9e1d9f065ae56a714aa7cf", "690dc80af4303cb2df1991de9d52c269211e1dcf"));
set_progress(0.116486);
assert(apply_patch_check("/system/app/Finsky.odex", "fda5fbff54fc6c35b9210afd4a3b76b6a8862d83", "59412510a7d0a789b1e732dbffdc9feb3245e964"));
set_progress(0.119390);
And the Update:
apply_patch("/system/app/Finsky.apk", "-",
19a70336522820f20a9e1d9f065ae56a714aa7cf, 1070527,
690dc80af4303cb2df1991de9d52c269211e1dcf, package_extract_file("patch/system/app/Finsky.apk.p"));
set_progress(0.135043);
apply_patch("/system/app/Finsky.odex", "-",
fda5fbff54fc6c35b9210afd4a3b76b6a8862d83, 655760,
59412510a7d0a789b1e732dbffdc9feb3245e964, package_extract_file("patch/system/app/Finsky.odex.p"));
set_progress(0.138224);
If I didnt want it to update finksy (bad example but just one I grabbed) could I just delete everything above from the script? In the case of something like Zinio I dont even want the update since I nixed the underlying app.
I actually tried something like that but it failed immediately, no error. Im wondering if I havent zipped it up right.
Yeah, if you search through the update script for the name of the file that's erroring out, there's 2 places. First the assert, then the patch. Get rid of both and you're fine.
I'd google what those files are before you remove them from the script, just to be safe.
Just for example, Finsky is part of Market
Im wondering if there is something I am doing wrong or if there is a trick to zipping it back up. I tried removing those lines (for AWS, not Finsky ) and the update failed without an error (just aborted).
Im wondering, should I be leaving that set progress, zipping using a particular method?
The biggest problem I had was making sure the files were saved with unix line-endings. If you edited it in notepad or something like that it may have defaulted to windows line-endings.
Hi can you add this to 1st post:
CWM package for ASUS FOTA Update 8.6.5.13 WW
(with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5
If it gives you an error about some file check, edit update script and put a "#" before the line of that file.