Database Info

downgrade to rc29 from rc30?

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 ?

New phone (RC29) - no console exploit (telnetd)

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

!!Root for RC30 users!! RC29 Downgrade NBH image: Get it now!

This was posted in another thread here, but it needs its own. (if someone beat me to it, please delete).
A .nbh image file has been released that will allow you to downgrade your rc30 phone to rc29 which will re-introduce the root bug. Once there you can follow the steps to get root access, install the modified recovery image and flash JF's rc30 and keep root! The steps can be found in various threads on this forum, and also in my wiki.
To downgrade using this NBH file: http://android-dls.com/wiki/index.php?title=Root_For_RC30
To gain root access: http://android-dls.com/wiki/index.php?title=Rooting_Android
To flash the recovery and install modified rc30: http://android-dls.com/wiki/index.php?title=Keeping_Root
Please remember this wiki is made and edited by users, not just me. Some information might not be written as well as it can, and if you find a problem, please feel free to login and correct it.
Good luck to everyone stuck on RC30 who wanted root, its finally here!
By the way, I got this info from disconnects site (gotontheinter.net) and I believe (might be wrong) he got it from here somewhere.

Hehe. I knew someone out there still had a copy of the RC29 NBH. This is great news!
MD5 checksums:
53840b90a0fe1bfab19fab8ef8fb9724 *DREAIMG_TC4-RC29.NBH
4f0efb2037524a06bda26f286bba474d *HappyNewYear.zip
Eng Bootloader sticky information updated.

Darkrift said:
This was posted in another thread here, but it needs its own. (if someone beat me to it, please delete).
A .nbh image file has been released that will allow you to downgrade your rc30 phone to rc29 which will re-introduce the root bug. Once there you can follow the steps to get root access, install the modified recovery image and flash JF's rc30 and keep root! The steps can be found in various threads on this forum, and also in my wiki.
To downgrade using this NBH file: http://android-dls.com/wiki/index.php?title=Root_For_RC30
To gain root access: http://android-dls.com/wiki/index.php?title=Rooting_Android
To flash the recovery and install modified rc30: http://android-dls.com/wiki/index.php?title=Keeping_Root
Please remember this wiki is made and edited by users, not just me. Some information might not be written as well as it can, and if you find a problem, please feel free to login and correct it.
Good luck to everyone stuck on RC30 who wanted root, its finally here!
By the way, I got this info from disconnects site (gotontheinter.net) and I believe (might be wrong) he got it from here somewhere.
Click to expand...
Click to collapse
I'll update my stickied post and host the NBH as well.

Nice, spread this fast!! all those users who have wanted root and its here. We need them all to get it before tmo or google find a way to block this!! Someone slashdot it!!! (just please dont slashdot my site directly lol, im on shared hosting)

Yehaaa, best christmas present, however a bit late
Anyone already tried it out?

To avoid creating two stickies with overlapping information, I suggest putting a prominent link in the first post to Koush's main sticky on rooting.

will this work on tc5-rc8 uk

Nope, we'll need a different .nbh file for that. With luck someone'll find it soon

works on stock RC30 just fine..

For TC5-RC8 users:
http://forum.xda-developers.com/showpost.php?p=3109773&postcount=97
http://www.megaupload.com/?d=QIDKOHPW
MD5:
2f02dd9a3b7c7f2fe058047b9c7a0245 *DREAIMG_TC5-RC7.NBH
b253b71fad2ed0352bcb58c4966b9a25 *HappyNewYearUK.zip

For those in the UK...
Here's your RC7 NBH... http://forum.xda-developers.com/showpost.php?p=3109773&postcount=97

Man. chavonbravo is everyone's hero today.

I am trying this now - once flashed with root on RC7, can i do the bootloader flash to Engineering to keep root forever?

for the tc5 rc8 i keep getting
no signature (1 files)
verification failed
any ideas

Epic Fail
Runs through the update, then:
DREAIMG.nbh - FAIL
Update Terminate
UPDATE FAIL
UPDATE:
I had to download the DREAIMG.nbh that was in the zip file, and put that on the sd card. De-bricked, and now my phone is root-enabled.

Thank u so much, I have been waiting this for a long time. Happy new year to everybody

OMG it worked!!!!!
I wiped out my SD card with it connected to my comp through USB. Then reformatted it to FAT32 (it was FAT), and copied the dream file to my phone. Rebooted with the camera key held, pressed power when it told me to. Then it took less than 10 mins to do its thing and now I am setting up the phone again after its reset.
Woot!
kila-user 1.0 TC4-RC29 115247
ota-rel-keys,release-keys

am i missing something, i got the phone to flash back to RC29, did the reset and typed telnetd, but its not doing anything, it just says telnetd on the screen. did i miss a step?

After that go to market and download the telnet app and keep going. And using those walkthroughs I did what they said but I used JK v1.3 instead of 1.2 and now I am a very happy panda, just look at my sig!

thanks to all for the NBH file, I downgraded from RC30 to RC29, rooted upgraded to modified JF1.3 changed to Engineering bootloader, the best new year gift for G1 user.. am planning to upgrade to modifed RC8 but not now..
-Pramod

[[[CUPCAKE OTA FOUND]]] Waiting for JF now.

Thanks to zinx for figuring out the url.
http://android-dls.com/wiki/index.php?title=OTA_Updates#Cupcake_1.5
This update is the OFFICIAL and will cause you to lose root. If you wish to have root please wait for JF's version to be made.

am i missing some thing?
Cupcake 1.5
Download: Google Download * Android-DLs.com Download
Date: 5-23-2009 (day we found the file, it was reported a few days before)
Size: 46.23MB
Filename: signed-kila-ota-148830.de6a94ca.zip
Fixes: edit me
New Features: Camcorder, <edit me>
Root Obtained: yes, see Rooting Android <----- is that realy all we need to root it?

Thank You
I am glad it was finally found. Thanks to all who were helping with this.

thank you so much
im guessing this is official US cupcake since it has the H in the build
thank you very much i appreciate you uploading this

t1h5ta3 said:
am i missing some thing?
Cupcake 1.5
Download: Google Download * Android-DLs.com Download
Date: 5-23-2009 (day we found the file, it was reported a few days before)
Size: 46.23MB
Filename: signed-kila-ota-148830.de6a94ca.zip
Fixes: edit me
New Features: Camcorder, <edit me>
Root Obtained: yes, see Rooting Android <----- is that realy all we need to root it?
Click to expand...
Click to collapse
All versions since rc29 have had the same thing. Rc33 for a while said no. It is basically saying you *can* get root, just need a modified rom.

at last someone finds this.
now lets wait for jf

I have a second G1, it is not rooted, my wife isn't into the rooting thing, but I want to update hers to 1.5 if I am thinking correctly, all i need to do is place the .zip file on her SDCARD and run the installer app correct.

I wonder if they have improved the Stock IM apps.

I was one of the first persons who received the log, and had been trying to figure out the link since 9:30am this morning. But I am in awe of Zinxx, how did he ever figure out the partner part of the link? Nice.. Thanks!

Mr. Moe said:
I have a second G1, it is not rooted, my wife isn't into the rooting thing, but I want to update hers to 1.5 if I am thinking correctly, all i need to do is place the .zip file on her SDCARD and run the installer app correct.
Click to expand...
Click to collapse
NO. rename it to update.zip and press hold HOME+END and alt+s in recovery

omg.. i just copied IM.apk/odex, ImProvider.apk/odex and TmoImPlugin.apk to my g1 on dudes1.1a
its looping on the 2nd boot screen

lovegu said:
omg.. i just copied IM.apk/odex, ImProvider.apk/odex and TmoImPlugin.apk to my g1 on dudes1.1a
its looping on the 2nd boot screen
Click to expand...
Click to collapse
Thats terrible although let us know if you get it to work.

lovegu said:
omg.. i just copied IM.apk/odex, ImProvider.apk/odex and TmoImPlugin.apk to my g1 on dudes1.1a
its looping on the 2nd boot screen
Click to expand...
Click to collapse
flash the ota over again and install apk's using apk installer it shouldnt mess up that way

How is JF going to make this build different from the ADP1.5 thats already out there?
Whats the difference besides (possibly) the stock IM stuff?

lovegu said:
omg.. i just copied IM.apk/odex, ImProvider.apk/odex and TmoImPlugin.apk to my g1 on dudes1.1a
its looping on the 2nd boot screen
Click to expand...
Click to collapse
Boot in recovery mode
then alt+x
mount system
mount data
and rm those files and reboot !
You won't need to wipe or reinstall that way.

Senorkabob said:
How is JF going to make this build different from the ADP1.5 thats already out there?
Whats the difference besides (possibly) the stock IM stuff?
Click to expand...
Click to collapse
We will have to wait and see, don't forget myfaves lol. Thanks darkrift and zinx

MyFaves is quite honestly a waste. This app polls Tmobiles server several times a minute wasting battery life. You can set your faves online and save battery life.

Gimpeh said:
MyFaves is quite honestly a waste. This app polls Tmobiles server several times a minute wasting battery life. You can set your faves online and save battery life.
Click to expand...
Click to collapse
Yeah i was being sarcastic, dont miss it at all!

I just tried pusing all apps from ota.zip. i got the same reaction from it lol

So what is the RC version of the official OTA 1.5?

OTA Supersonice 1.47.651.1-1.32.651.6_r

DO NOT FLASH THIS UPDATE UNTIL YOU HEAR FROM THE BIG GUNS OR RISK LOSING YOUR ROOT!
Please Be Patient!!!!
Sprint is pushing out a system update this morning with a size 21.43mb
Update Download Links:
http://www.mediafire.com/file/2myavzqygir/OTA_Supersonic_1.47.651.1-1.32.651.6_releaseq2wpcb5jl7uowah9.zip Thanks Calkulin!
http://www.sdx-downloads.com/sdx/evo/stock/OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip Thanks Joeykrim!
Firmware Version
2.1-update1
Baseband Version
2.05.00.06.10
Kernel Version
2.6.29-789bf291
[email protected] #1
PRI Version 1.40_003
PRL Version 60667
Thank you joeykrim for the following:
RADIO - the radio is updated through a radio.diff.
SYSTEM - no system/app files are changed
it appears this OTA is much more extensive than the previous OTA.
this one appears to apply small patches to every application in /system/app. a few are large in size, but most are very small.
it also appears to patch:
16 files in system/bin
etc/wimax/
etc/firmware/fw_bcm4329.bin and (ap)
31 files in framework
28 files in lib
2 files in lib/modules - bcm4329.ko and sequans_sdio.ko
SYSTEM updated files (might be more, researching now):
wifi module - BCM4329B1_002.002.023.0396.0402.hcd
android.hardware.camera.flash-autofocus.xml
android.hardware.telephony.cdma.xml
ton of framework files
libCamera_donut.so
libCamera_eclair.so
Fixes & Bugs:
From user npace: (I extracted and fastboot flashed the kernel zImage. Here's a rundown of the issues that I tested for fixes
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
3. 30 fps cap -- still there

same radio by your title?

Appears to be. I am waiting for it to finish downloading and I will attempt to upload.
This thread will probably be moved / deleted but I was just letting everyone know. Personally I am going to wait to hear from the Dev's on this download before even touching it.

is this breaking root access.. some unrevoked users via face book saying unrevoked is no longer working.. i guess they should have went all out and did the full root

danon.brown said:
is this breaking root access.. some unrevoked users via face book saying unrevoked is no longer working.. i guess they should have went all out and did the full root
Click to expand...
Click to collapse
Even if you rooted via toasts method, i would not update until a custom ROM is put out with the update included. You could lose root ability forever.

Anyone know the location of system updates are stored on the phone? I am trying to locate using the adb shell but have had no luck finding the download yet.

huoter said:
Appears to be. I am waiting for it to finish downloading and I will attempt to upload.
This thread will probably be moved / deleted but I was just letting everyone know. Personally I am going to wait to hear from the Dev's on this download before even touching it.
Click to expand...
Click to collapse
can you post this OTA .zip?

joeykrim said:
can you post this OTA .zip?
Click to expand...
Click to collapse
Its done downloading, just trying to find the darn file right now. Any ideas?

Awaiting an update zip

Here's the untouched update zip for those that want it. If you want to put it in the OP, feel free to
OTA_Supersonic_1.47.651.1-1.32.651.6_releaseq2wpcb5jl7uowah9.zip

huoter said:
Its done downloading, just trying to find the darn file right now. Any ideas?
Click to expand...
Click to collapse
i didn't look into the last one and this is my first HTC phone so im not familiar with their OTA process.
perhaps try /cache? or any type of temp directory on /data or /sdcard?
we know it won't be on /system.

We install this from recovery, right?

herzzreh said:
We install this from recovery, right?
Click to expand...
Click to collapse
Don't install anything until some devs have had a look around--they'll make a package to flash when it's safe.

herzzreh said:
We install this from recovery, right?
Click to expand...
Click to collapse
I'd recommend not installing it at all until the devs here have had a chance to go through it and release it themselves. You risk loosing your root if you don't. Then follow their release instructions to apply it.

Btw the radio is 2.05.00.06.10 with this update.
Sent from my EVO using Tapatalk

Shidell said:
Don't install anything until some devs have had a look around--they'll make a package to flash when it's safe.
Click to expand...
Click to collapse
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...

donatom3 said:
Btw the radio is 2.05.00.06.10 with this update.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
if you've applied this, can you take a screenshot of the about phone -> software versions or manually type all the info up on here?
im wondering about the PRI ...

herzzreh said:
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
Click to expand...
Click to collapse
No, looks like just about all the preloaded APK's are in there, including the Sprint crap. I assume if you apply it as stock you'll get them back, but I could be wrong.

herzzreh said:
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
Click to expand...
Click to collapse
The official froyo release from HTC / Sprint will definitely contain all the "Sprint Junk" and if you've given up root to one of these updates and go to apply that it will all come back. You may never get root again in order to re - clean it up once you apply froyo.
Be patient. It won't take the devs here long to cook up an update for us. Flipz had the rooted .6 update rom out in 24 hours or so...
.....
Just took a look inside the zip file. All the apk files are there, including the sprint junk...

Just installed....all is well with root...