Related
I am new to the Dream, I just got mine on Friday. I have now got root access. I want to know when the RC31 comes out, if I update via t-mobile will it kill root access, or will I need to hold off until a modded FW comes from JesusFreke.
Thanks
Tim
Yes,if you update via t-mobile,it will remove root. Its best if you wait for a modded FW if you want root.
Thats what I figured. thanks for the info.
otto888 said:
Yes,if you update via t-mobile,it will remove root. Its best if you wait for a modded FW if you want root.
Click to expand...
Click to collapse
While I agree that it would probably be best to not upgrade right away, we don't know anything about RC31 yet. The only thing I think that has been officially announce is that it would contain elements of cupcake. I'm not even sure how official that was either. Let's try not to speculate.
Echoing what's been said above, being that we know NOTHING about the next OTA update, it will likely (at the very least) remove root access from a JF RC30 device. It might even prevent you from backflashing to RC29 to get back to the modified JF RC30. So whatever you do, DON'T let your phone update until the new version is examined and tested by others, or you might find yourself with a permanently locked down G1.
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
Correct, or the update will fail, can't remember which one.
So I guess it would be safe to say....
STAY TUNED!!! Same XDA time, Same XDA channel
Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
I love when modders do that, keeps me from doing something stupid
Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
I am not entirely convinced of this.
I had a chat with a co-worker about this and he said "well no, between the engineering bootloader and the test keys, there is no way the modded rc30 can be OTA'd".
I tossed this at him.
What if tmo decided to setup something like this...
check what you are running.
check what keys you are running.
send an update that does something along the lines of...
if your image is equal to or less than rc30 and your keys are either ota or test then update.
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
I imagine that anyone with ADP1 or ADP1.1 will be left alone as it would be a bad move to screw with your developer audience; but I could be wrong. They could go after anyone who doesn't have an official ADP image (non JF kernel)...
I have no idea what they are really planning but it does seem that this could be a "check mate" pivotal move if they wanted to play that card this early in the game.
Of course, it could be as simple as "let's leave everyone where they are and only focus on security moving forward" which is most likely going to be the case....
deprecate said:
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
Click to expand...
Click to collapse
The running theory is that T-Mo will not do this because all devices with the standard ota-keys installed will also get the "targeted" test-key rc31, reboot, and then freak out because the update is signed with a mismatched key.
The way the update service works is the device periodically sends its Android build fingerprint to Google servers. If the fingerprint is of a supported device (in this case Dream) and the build number is lower than the most recent, then the server may push an update back to the device. Since JF modified builds report an official fingerprint, there is no way for the server to distinguish between a modified and unmodified RC30.
However, i've seen enough in information technology to know that very little is truly "impossible". Based on what is currently known though, it is highly unlikely that Google/T-Mo/HTC could forcibly reroot a modified RC30 G1 at this time.
I really don't see T-mobile doing this. Why would they? At this point people with root don't have any real advantage over normal phones other than techie stuff. We are not pirating software or getting free minutes. Unless it becomes an issue I think T-mobile will leave us alone.
speoples20 said:
I really don't see T-mobile doing this. Why would they? At this point people with root don't have any real advantage over normal phones other than techie stuff. We are not pirating software or getting free minutes. Unless it becomes an issue I think T-mobile will leave us alone.
Click to expand...
Click to collapse
There is no piracy because apps are free. Once support for paid apps arrives, piracy will start. (Someone in this forum started a thread wondering how to do that). It happens in all software platforms, and it's going to happen with Android also. Note that I don't endorse piracy (for some weird reason people think that developers are the only guys who should work for free), less in these environments where there are lots of applications than are made by individuals, not big companies, but this won't prevent piracy to come to Android.
Anyway, if I were TMob I would try to remove root from as many devices as I can (which obviusly does NOT include ADP1, as it has nothing to do with TMob),
not just for the piracy, but to keep users from breaking their devices due to doing stupid thing with a rooted phone.
T-Mobile motivation to wipe devices using test keys
T-Mobile could have a motivation to wipe devices by providing an update using test keys. Tethering is against the terms of service and can only be done if you have root. They could take the *IAA approach and say that any one who has root wants to be able to tether and break their TOS (since tethering is the biggest advantage to root right now). If enough people tethered it could cause a problem as they may not have the bandwidth to accommodate what people want to do when tethered. BTW, for all who tether use this addon for firefox and change your user string to match the android's browser (https://addons.mozilla.org/en-US/firefox/addon/59) so they can not tell.
Is there a way to make new keys that are different from the dev keys, or is google the only ones who can do that?
Doing an update using test-keys sounds a bit desperate to me.
Moreover, as jashsu said, it seems that there is no way that currently TMob could know if you were using a G1 with an stock R30 or JF's one, so if they offered the update with testing keys, stock R30 phones would reject it.
They could try some tricks as offering the update with test keys for a while, then switch to another with official keys, then came back to test keys, etc...
But as I said, this sounds desperate and sloppy.
Mi bet is that they would try to fix the downgrade issue, and will use the official keys, so anyone with JF will be safe.
Anyway (I have an ADP1, so I've not receive any update from now), I though that, when an update was available, the user was asked whether to update or not.
clarke.hackworth said:
If enough people tethered it could cause a problem as they may not have the bandwidth to accommodate what people want to do when tethered.
Click to expand...
Click to collapse
This is not a problem. They will simply throttle you down to EDGE if they consider you are using up too much bandwidth (tethering or otherwise).
Is there a way to make new keys that are different from the dev keys, or is google the only ones who can do that?
Click to expand...
Click to collapse
Anyone can create signing keys. Not sure what you're getting at though.
clarke.hackworth said:
Tethering is against the terms of service and can only be done if you have root.
Click to expand...
Click to collapse
It is? Where? Last I remember I saw the CEO say it wasn't and it is allowed. And that they wouldn't stop it or prevent it in anyway.
deprecate said:
I tossed this at him.
What if tmo decided to setup something like this...
check what you are running.
check what keys you are running.
send an update that does something along the lines of...
if your image is equal to or less than rc30 and your keys are either ota or test then update.
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
Click to expand...
Click to collapse
It still wouldn't apply the update, even if they sent out an OTA signed with test keys. The OTAs are verified against the certificate present in /system/etc/security/otacerts.zip.
Since that file has been deleted, it wouldn't be able to verify the OTA, no matter how it was signed.
JesusFreke said:
It still wouldn't apply the update, even if they sent out an OTA signed with test keys. The OTAs are verified against the certificate present in /system/etc/security/otacerts.zip.
Since that file has been deleted, it wouldn't be able to verify the OTA, no matter how it was signed.
Click to expand...
Click to collapse
Good point. That completely escaped me. But wouldn't it be entertaining to see an official rc31 sent out with your certs as the target
deprecate said:
Good point. That completely escaped me. But wouldn't it be entertaining to see an official rc31 sent out with your certs as the target
Click to expand...
Click to collapse
Very entertaining
Hey guys,
Basically i've done some searching, but can't seem to find the answers anywhere... Just wanted to know whats the difference between these rom's?
I know ADP1 = Developer rom,
RC8 = UK and
RC30 = US
But what are the main differences between the 3? As I'm in Australia, I actually bought a g1 from the us, and it's on rc30 now, but I would imagine a less localised version would be better for me? Can I upgrade to any image? or is it specific to the handset?
Thanks for the help.
gunigugu said:
Hey guys,
Basically i've done some searching, but can't seem to find the answers anywhere... Just wanted to know whats the difference between these rom's?
I know ADP1 = Developer rom,
RC8 = UK and
RC30 = US
But what are the main differences between the 3? As I'm in Australia, I actually bought a g1 from the us, and it's on rc30 now, but I would imagine a less localised version would be better for me? Can I upgrade to any image? or is it specific to the handset?
Thanks for the help.
Click to expand...
Click to collapse
This link should give you the basic idea.
RC30=T-Mobile branding.
ADP1=My Choice =)
RC8=Would be my second choice if i ever decide to leave ADP1
Yes you can install any of the three roms
i know between the 3, phone number format is saved differently as well.
So on........check the link to get a basic idea.
Appreciate the reply back thanks
Seems to have covered all my questions.
So, according to the info I was able to gather, a US version would work in the EU, with only minor visual impairments like phone# formatting etc.? The 3G and GSM would still work?
I've just received a new T-Mobile G1 and I am pretty desperate to update to a cupcake build. There's loads of guide here that will walk me through it no problem, but there are some things they don't explain fully (or at least, I can't find them).
Will I lose all my contacts and messages when I update? Will I lose all my T-Mobile data (like message settings, 3G settings etc.?). Will Market and everything else still work? What will stop functioning correctly when I do upgrade, specifically for T-Mobile in the UK?
Thanks a lot!
Tony
Funkstar De Luxe said:
I've just received a new T-Mobile G1 and I am pretty desperate to update to a cupcake build. There's loads of guide here that will walk me through it no problem, but there are some things they don't explain fully (or at least, I can't find them).
Will I lose all my contacts and messages when I update? Will I lose all my T-Mobile data (like message settings, 3G settings etc.?). Will Market and everything else still work? What will stop functioning correctly when I do upgrade, specifically for T-Mobile in the UK?
Thanks a lot!
Tony
Click to expand...
Click to collapse
You will lose messages, you will not lose any T-Mobile data, you will not lose any contacts. I suggest you check out Haykuro's thread: http://forum.xda-developers.com/showthread.php?t=498026
You will need root. And I suggest you go with haykuro's 4.5 build. I won't go in to any more detail, just do some research in haykuro's thread and others on how to get root, etc. Good luck.
Wel.. Where can i start? The cupcake your possibly reading about isnt fully working on G1 Yet..
I recomend you try one of the magic roms ported to G1, Preferbly 5.0H
Root is easy to achieve, Just read around.. Plenty ahve asked how to do this before, so please dont make new threads, Just read please
If you are referring to the ''Cupcake'' that T-Mobile is releasing this Easter then all these guys are wrong. If you do update to HTC Sapphire it will void your warranty and there's a small(Or large if you don't follow directions) that you could brick your brand new G1. The ''Cupcake'' that T-Mobile will release or at least hoping it will, will be coming in the next days. This update is 100% safe and will not do anything harmful to your g1. It wont even delete anything.
Mast3rmatt said:
If you are referring to the ''Cupcake'' that T-Mobile is releasing this Easter then all these guys are wrong. If you do update to HTC Sapphire it will void your warranty and there's a small(Or large if you don't follow directions) that you could brick your brand new G1. The ''Cupcake'' that T-Mobile will release or at least hoping it will, will be coming in the next days. This update is 100% safe and will not do anything harmful to your g1. It wont even delete anything.
Click to expand...
Click to collapse
And as I've said in other threads re: Cupcake, I say we wait for JF to do his thing with it.
blackknightavalon said:
And as I've said in other threads re: Cupcake, I say we wait for JF to do his thing with it.
Click to expand...
Click to collapse
That's exactly what I'm planning to do. I was hard set against root when I first got my g1, but I have seen the light and enjoyed my rooted g1. Thank goodness for the jfupdater app
blackknightavalon said:
And as I've said in other threads re: Cupcake, I say we wait for JF to do his thing with it.
Click to expand...
Click to collapse
Huh? That has nothing to do with my post other. My post was answering his question about ''CupCake'' from T-Mobile and not some other Rooted Cupcake. I understand that there are other cupcakes but the best will be T-Mobile for the time being.
I think I said CupCake enough times
Mast3rmatt said:
Huh? That has nothing to do with my post other. My post was answering his question about ''CupCake'' from T-Mobile and not some other Rooted Cupcake.
Click to expand...
Click to collapse
Actually, he asked about *a* Cupcake build - he made no mention of an official build, therefore it is reasonable to presume that he is referring to *one that is available* and not *one that isn't*.
I understand that there are other cupcakes but the best will be T-Mobile for the time being.
Click to expand...
Click to collapse
Really? For the time being, there is no T-Mobile Cupcake build so how it can it be best? Granted, if and when it comes out, it may well be superior, but that is by no means certain since Haykuros builds are getting better all the time.
If the OP is waiting on an official T-Mobile Cupcake update, I suggest there is no point asking around here since if he leaves his phone with a vanilla build, he'll get the update soon enough, if and when it is released.
Regards,
Dave
Thanks guys. I'm not waiting on the t-mobile build as I have little faith in them releasing it any time soon. I'll ask my question in a different way; what's the best build to put on my UK t-mobile G1? With regards to battery life and features? Thanks
I suggest you read the threads about rooting your G1. The first thing you have to do is downgrade to RC7, and get root. Then, don't accept any OTA (from T-Mobile) upgrades if you should get a notice.
After downgrading and getting root, read up on some of the different builds. You can go to JF's RC9, which is a modded version of the official UK one with root. I would really advise you to do this first, so you will know how to flash your roms, and how to flash the radio.
It will give you a stable version which won't accept OTA updates so you don't have to worry about losing root. (Plug your phone into a power source, or at the very least, be sure your battery has a full charge while flashing, and don't ever turn your phone off while it is flashing.)
After that, read threads like the one comparing the two Magic versions. 5.xG is the google version, and 5.xH is the HTC version.
Once you have gotten root and gone to RC9, you will be able to do something called a Nandroid backup of your phone. You will then be able to try both versions of magic, and also to restore your phone to RC9 if they don't work out for you without losing anything. (Another reason to try a more official mod before trying the Magic ones).
edit: I just found this on the Magic wiki page. It looks helpful: http://code.google.com/p/sapphire-port-dream/wiki/PageName
Have fun with it!
I know there's already plenty of these around but people still seem unsure about doing this (especially users on UK G1s) so last night, I un-rooted my phone and created a new guide complete with screenshots at every step of the way.
It's rooting on a UK G1 at the latest firmware revision (CRC37 at the time of writing) right through to running CM 4.04.
I tested it as I went along (to create screenshots as well) and it worked fine for me and I know that someone else has also already used it and it worked OK for him too.
Please have a look and check it out and let me know what you think and feel free to suggest any additions (or spelling mistakes)
I'm going to do another next week for un-rooting and I will probably also do another for upgrading the radio and putting on haykuro's "danger" SPL.
Anyway, site is here http://lordsmiff.nl
Cheers,
Smiffy.
Just got my OTA Jelly Bean update last night. I am on Cincinnati Bell carrier here in Ohio. So far I am happy with it. Seems a bit more smooth and faster. Not a whole lot of new features, but glad I did the update. Will keep posting if I run into any problems or issues with this update. Anyone else out there in the area getting the OTA?
Not yet. In Texas. Crazy you have one but T-Mobile still slacking
Sent from my HTC VLE_U using xda premium
keller9431 said:
Just got my OTA Jelly Bean update last night. I am on Cincinnati Bell carrier here in Ohio. So far I am happy with it. Seems a bit more smooth and faster. Not a whole lot of new features, but glad I did the update. Will keep posting if I run into any problems or issues with this update. Anyone else out there in the area getting the OTA?
Click to expand...
Click to collapse
Can you pull the update.zip and upload it here?
It is crazy that I have it on Cincy Bell. Usually it is slow getting updates on this carrier. I could upload the update but not sure how to pull it off my phone. I see it in my downloads folder. I hook up my phone to the computer, but cant see downloads anywhere. If someone can tell me how to pull it and upload it here I would be more that happy to share.
keller9431 said:
It is crazy that I have it on Cincy Bell. Usually it is slow getting updates on this carrier. I could upload the update but not sure how to pull it off my phone. I see it in my downloads folder. I hook up my phone to the computer, but cant see downloads anywhere. If someone can tell me how to pull it and upload it here I would be more that happy to share.
Click to expand...
Click to collapse
I think its located in /cache, in the root directory. but you will probably need root access to get to your file system to copy the file. Don't quote me on that thought, you can try to get to the file without root first if you have time.
I would also like the OTA as I am on Cincinnati bell as well please.
Sent from my HTC One S using xda app-developers app
We received and updated Saturday night/Sunday morning. Was also surprised to see CBW beat T-Mobile on the update. So far we have been happy. JB has fixed an issue I had with the latest swiftkey update (jumping cursor) The one thing that we have noticed though is that battery life has been diminished with "Android OS" consuming considerable amounts of battery life. I guess the diminished battery life is a 4.1.1 thing. Not holding my breath for HTC (and CBW) to follow up with a 4.2.2 update.
Chris.
Jelly Bean Update
I live in Fairfield Ohio and received the OTA update late Sunday night. It took less than an hour to download and install. So far it appears that everything works. Hard to believe Cincinnati Bell could get this right. I did not expect to see this update for months.
Has anyone extracted a copy of the zip or found the URL from HTC for this?
You'd think there would be more than two people with the update here.
Sent from my One S using xda app-developers app
First wave of updates from a small regional carrier? I'm not too surprised to see that there's only a handful of people reporting about it.
Questionable
The mere fact that 2 users are here to report getting it on Ohio is questionable.
And why I am also questioning is neither of them posting the update zip?
I know as soon as I get it I will upload it.
Believe what you want. I got the update to Jelly Bean and cannot post the update zip because my phone is not rooted. I cannot pull the file off my phone without being rooted. Why would I lie about getting this update. That would just be stupid!
Just took a screen shot of my phone!
I haven't tried getting the OTA update as I have been using CM 10/10.1 since I bought my One S back in September from CBW. I did have a question though regarding an RUU. I was considering grabbing the RUU based off CBW's but I'm not exactly sure which one to use. I came from a Moto Droid X which I grew accustomed to SBF'ing and HTC's method is unfamiliar to me. Could someone possibly point me in the right direction?
On a side note, to those with the OTA update: have you noticed an improved reception/wifi singal strength with the update? I'm debating if its worth it to RUU to stock, grab the OTA, and re-root to move back to 10.1 in case there was a radio update along with it.
There would almost certainly be a firmware update (with radio) in a major OTA like that. It should be a full ROM update.
If you're up to it, going back to stock to grab the OTA file would certainly be welcome here.
As for which RUU to use, that's a really good question. There may be different RUUs for CBW. I don't know how to acquire them, but it seems like some people found a way to purchase them (from HTC?). What CID did your phone ship with?
ardax said:
There would almost certainly be a firmware update (with radio) in a major OTA like that. It should be a full ROM update.
If you're up to it, going back to stock to grab the OTA file would certainly be welcome here.
As for which RUU to use, that's a really good question. There may be different RUUs for CBW. I don't know how to acquire them, but it seems like some people found a way to purchase them (from HTC?). What CID did your phone ship with?
Click to expand...
Click to collapse
I have the same problem with my Cincinnati Bell phone the CID mine shipped with is HTC_017
Xvoo222 said:
I have the same problem with my Cincinnati Bell phone the CID mine shipped with is HTC_017
Click to expand...
Click to collapse
Same here, [HTC_017] for my CID.
cincinnati bell one s jellybean
Cincinnati bell HTC one s has jellybean update. I just updated it today.
Anyone ever figure out which RUU is needed to bring the CBW One S back to stock? Done a bit of digging myself to no avail.