If i go to Rc29, How will cupcake work?

[uga.buga]

I want to get rc29 (for obvoius root purpose)

But will I get notifications to go to the "new phone software" rc30?? . Because I rmember the last update it didn't say to what I was updating it too .

How will I know if its rc30 or cupcake? (Even though I will know cupcake is out by you guys saying you got it).

From rc29 will I get cupcake and still have root acess?

Or will I need rc30 to get to cupcake?

And btw. Will going to rc29 void my warranty?


Sorry so many questions. Sorry if there's an answer. I try to search already. If you find the answer can you please tell me what question and a link . Lol .

[birdman81484]

I believe getting the JF rc30 v1.3 will disallow further OTA's. Somebody correct me if I am wrong. As for cupcake in the form of an OTA coming to a modded JF rc30 phone one would have to wait for a modded version of that update I assume.

[constellanation]

I'm sure most all the answers for those would be speculation at this point, with some amount of what happened for 29 to 30 as possible outcomes...

I think it does void your warranty, but seems odd with the whole idea of open source and all, but makes sense from tmobs point o view.

[constellanation]

1.3 blocks updates, yeah I saw that, hmmm. What if you're at 29 or modded 30 and want cupcake would you have to revert to get the update or could we somehow override the block ota with the mod?

[DesignDawg]

You would have to put the original boot image back on the phone, because the modified one you had to put in installs packages signed with the test keys. The official OTAs are signed with the google/T-Mobile/whoever keys.

[outsider]

You would have to put the original boot image back on the phone, because the modified one you had to put in installs packages signed with the test keys. The official OTAs are signed with the google/T-Mobile/whoever keys.

That's not really true. You would just have to resign the update with the test keys. More than likely cupcake will go out OTA for the developer phones which also use they test keys so any update they get then users with rooted RC30 would also likely get.

I'd honestly hold off on OTA updates either way though until we know what they are so that you don't have to go back to a stock phone with RC29 to get root back.

[rynosaur]

I'd honestly hold off on OTA updates either way though until we know what they are so that you don't have to go back to a stock phone with RC29 to get root back.

Wow. You and I agree on something :D

Having JF RC30 v1.3 is an insurance policy. Once the mod guys (JesusFreake, Koush, Stericson, et al) on XDA get a close look at the next firmware and run their coder magic on it, we modders/expert n00bs will have a safe, workable, hackable solution to manually install. I don't want the straight Tmo/Google-sanctioned code cuz frankly, they don't hold my/our interests up as the highest standard. I don't need to make a profit off of Android/G1/further Android devices, they do.

Our solution is more pragmatic, more fun, tested by an open, involved community, and not beholden to stock-holders and marketing strategies.

Democracy + egalitarian tech + open source = The Win

[DesignDawg]

That's not really true. You would just have to resign the update with the test keys.

I know that, but the people asking questions about this aren't going to be able to do this. They're going to have to wait for someone else to do it or, if they are impatient, revert back to a state that will allow it to happen automatically.

[rynosaur]

I know that, but the people asking questions about this aren't going to be able to do this. They're going to have to wait for someone else to do it or, if they are impatient, revert back to a state that will allow it to happen automatically.

Dawgy is right and I missed that point entirely, but really, the signapk.jar can't be too hard to use and it's gonna take about .5 sec for a re-signed RC3x to show up on the information superhighway.

I researched my own question, and didn't have to use letmegooglethatforyou.com ;)

To quote from the signapk.jar readme:
"SignApk.jar is a tool included with the Android platform source bundle.
testkey.pk8 is the private key that is compatible with the recovery image included in this zip file
testkey.x509.pem is the corresponding certificate/public key

Usage:
java -jar signapk.jar testkey.x509.pem testkey.pk8 <update.zip> <update_signed.zip>"

*end communication*

[DaYuMu6ft7]

I'm just going to send my phone next day air over to Ryno's crib, Because ummm...

I am lost in the sauce, Ugh!