Getting confused, I have RC30 (Rooted), Going to update - G1 Android Development

Hey all, Ill only ask this once, (Since after this time, Ill know for future updates and be on the right path =) )since this G1 is so new dev wise, its getting confusing when im studying everything all at once and only updated rooted once to the custom RC30. I saw the newer update is RC33, now when I apply that, is it required EACH TIME to wipe the device? Im asking cause it would be a pain to reinstall each app I had installed there to begin with. I know I wiped the 1st time I rooted and updated. So just wanted to check.
Also whats the new additions in these updates? Any good changelogs out there? I kinda like keeping the Tmobile US stuff on mine, but root access is awesome. =)
Thanks for any update tips out there atm.
Edit, My G1 is still on Firmware 1.1 is that a seperate update or how is everyone updating that with the custom stuff? Thanks. (And do I need that FW update before going RC33?)

Nope, you won't lose anything when you upgrade the firmware normally. Going from JF RC30 to JF RC33 should be fine
Check the stickied topic on the top of the forum to find out more:
http://forum.xda-developers.com/showthread.php?t=475381
The changelog is somewhere in there.

Thank you. =) I didnt read that one since it was talking about for UK users. Heh. Least it explained things a lil more. =DDD
What about the firmware? Seems Ill have to do the new radio too, but wondering.. is that radio one for US too or only uk? Since its in a UK thread. =/

Nah, it's not a UK topic. He just modifies the title when he adds something new. The radio should be for the US version. Just download the radio and JF RC33 and throw them on your microSD (one at a time obviously, named update.zip).
Firmware 1.1 is just like the base firmware number, you can ignore that. Firmware 1.5 (I think) is cupcake, so you get the idea.

Ok so the firmware is nothing major atm to update or would you still upset it? I havent looked into cupcake yet.

No, completely ignore the firmware number, the only numbers you want to look at are RC30, 33, etc...

Ok this is odd. I updated fine to RC33, however when I try to get back in recovery mode to apply the radio rom, it wont go into the recovery mode. It just keeps rebooting to the G1 screen when im holding the home button. Anyone seen that before or how to get back into the recovery mode?

Anyone have any ideas?

Related

G1 OTA updates for rooted phones? README!!!!

With all of the (most likely false) articles coming out saying cupcake will be released this week (from what ive heard, good luck getting it by march) everyone is asking "Will rooted G1s get OTA updates?
No, you will not (if you have rooted your phone properly (this means you have JF's latest rom)) receive the OTA update. Technically you might receive it, but it will fail to install if you do. This was done on purpose because if it succeeded you would lose root. Shortly after the OTA updates are released, various members of the G1 "hacking" (yeah, term doesnt quite fit, but it will work for now) community will intercept it, tear it apart, remove all the mean mean code that steals our precious root, maybe add some fun new stuff and then release another modified rom in its place.
If you suddenly decide you do not want root anymore (I am guessing you are too lazy to download the update manually) you can use the RC29 downgrade nbh file found on various threads here, or in my wiki (see my signature) to go back to an official RC29 which would then let you receive OTA updates normally.
duhh lol this should be a board annocuments
I've heard some people saying they got the update but I dont see how that is possible. Wasnt google says like a 2 weeks ago that cupcake isnt close to being ready for the public? The only thing I can think of would be and update to support paid apps. I figured if cupcake was launching someone on here would have announced it.
Correct me if I'm wrong but wouldn't downgrading to RC29 while still rooted just give you RC29 with test keys still enabled? Wouldn't you also need to reflash your recovery partition as well to the stock one?
the rc29 will flash the recovery also the only thing you would be left with is the boot loader
Frankly, we'll all probably have a modified Cupcake before most G1 consumers actually have Cupcake. Google rolls out the updates really slowly. There's no reason to downgrade.
xile6 said:
the rc29 will flash the recovery also the only thing you would be left with is the boot loader
Click to expand...
Click to collapse
Good to know, my g1 has a bad wifi module and I need to restore it and send it back. I figured I would experiment with rooting the defective one first in case it went wrong.
Come to think of it, my wifi reception problem could be an antenna problem which could explain my weak 3g reception, or it might just be the 3g network...
speoples20 said:
I've heard some people saying they got the update but I dont see how that is possible. Wasnt google says like a 2 weeks ago that cupcake isnt close to being ready for the public? The only thing I can think of would be and update to support paid apps. I figured if cupcake was launching someone on here would have announced it.
Click to expand...
Click to collapse
there is going to be a video recorder FINALLY... rumors rumors lol
xile6 said:
the rc29 will flash the recovery also the only thing you would be left with is the boot loader
Click to expand...
Click to collapse
bzzzzzt. wrong answer . the RC29 nbh also flashes the bootloader.
MY bad i meant the Engineering SPL wouldnt that still be left?
hmm....so the new cupcake update coming out will close root again? that is so stupid, why wont they just let it be.
granted, like mentioned above, some of our famed and hard working G1 modders will probably have a modded rom with the whole cupcake update on it before everyone would have recieved the OTA anyway.
we'll see what happens i guess, but not for nothing, im really looking forward to the Cupcake updated features and abilities
im almost tempted to just revert back to RC29 just to get the official OTA and see how it is, but then again, whos to say it wont take months for me to get it.
As a note for all those who read my post and thought "yeah, I am lazy, I might as well downgrade and let the OTA's come." you might want to rethink it. If you downgrade, and the new OTA reflashes your system to not accept the RC29 downgrade, you might never get root again. And yes, this is entirely possible.
If you have root, I would not risk it for laziness or eagerness to have the latest OTA because history shows JF has had modified updates in less than 24 hours (I think they were all about 3-5 hours later) after the OTA's were first found.
i wholey agree with that. i definatly dont want to be locked out of root again. although i dont use it as much as others, root is good to have if needed to use it for something.
It would be stupid to downgrade to receive the ota. It took 1 month after the release just to get rc29. Waiting for someone to rip apart and modify the cupcake ota will be much quicker than to wait for the ota update yourself plus root access probably will be lost. Just say no to ota!
Anyways if people are so eager to see cupcake in action visit their local tmobile retailer I bet they will have it as soon as it gets out
Downgrade? Revert? Not an option now that I have root, no way I would chance losing it. Good heads up, I was pretty sure (actually was one of the ? i had) before rooting that this would occur. I spent some time here on XDA and realized that I could trust this forum and the devs to support the rooted community.
Thanks to all who make root possible and what it is on the G1!
All~G1 said:
Downgrade? Revert? Not an option now that I have root, no way I would chance losing it. Good heads up, I was pretty sure (actually was one of the ? i had) before rooting that this would occur. I spent some time here on XDA and realized that I could trust this forum and the devs to support the rooted community.
Thanks to all who make root possible and what it is on the G1!
Click to expand...
Click to collapse
well said ..... thanx much. XDA has helped me start learning this new language. As I stumble through, I find a surprising lack of b.s. and have learned quite a bit ... way thanx, to all ya all
my theory on when the next RC will drop.
They have been slow to get out updates, unless there is a exploit found.
When the bug was found everybody got rc 30 in a few days, I think that the new found downgrade route will speedup the next update to stop downgrading, if the tmob wants to keep the handset locked they will push for a speedy update to stop downgrades.
They also eluded that a beta was close but the holidays would alow it down but they did say it would be january, and if they are late people grumble and lose faith, for a phone that's sold on what it can become not what it is out of the box, losing faith means losing sales...
Bhang
xile6 said:
MY bad i meant the Engineering SPL wouldnt that still be left?
Click to expand...
Click to collapse
I am pretty sure flashing an NBH will bring you back to the original SPL. Someone correct me if I'm wrong.
They have been slow to get out updates, unless there is a exploit found.
When the bug was found everybody got rc 30 in a few days, I think that the new found downgrade route will speedup the next update to stop downgrading, if the tmob wants to keep the handset locked they will push for a speedy update to stop downgrades.
Click to expand...
Click to collapse
The problem that T-Mobile has now is that in order to stop downgrading, HTC would have to make a new SPL that blacklists the signature of RC29 NBH. Google can patch whatever they want, but I'll be able to downgrade immediately just by putting the NBH file on my sdcard and flash it via SPL
I'm curious as to why everyone assumes that the next update will make moves specifically to remove/block root for those who have it?
My understanding/interpretations of the press relases surrounding RC30 was that it was intended to fix the massive security risk in RC29. Perhaps I've missed something, but I've not seen anything that Google or T-Mobile have done specifically to counteract the "hacker" community, the blocking of the rooting method being "colateral damage" from the security fix. If the superuser method can be used to safely provide root access couldn't this be rolled Android itself? It's over my head but has this question been posed to powers that be at http://source.android.com/?

No Multi-Touch RC33 ROM

Here is a version of JF's RC33 1.41 without the multi-touch kernal included.
This one is JF's RC33 build modified with the PRE-MT kernal (1.31). It includes all the goodies that are standard with JF's builds and was recompiled from his source. This update does include the 1.41 recovery image.
ALL CREDIT GOES TO JESUS FREKE for providing us with the source for his modified ROM's
If you are interested or do not know what JF has added to the original images check this link
Just like JF's RC33 build this does not include the radio update which can be found here(MD5:CF8714D273FB0274574D9E3831E11FDD) this will need to be flashed separately in any order. To revert the radio you WILL NEED TO FLASH BACK TO RC29 THROUGH THE DREAMIMG.NBH file that can be found here
RC33 PRE-MT Kernal (MD5:97167BFDD7957F4D95C1538410003146)
http://drop.io/qyyqvmd#
*UPDATED* RC33 PRE-MT Kernal 1.42 Recovery image, No Amazon MP3, No Stock Email, no Term Emulator (which can be downloaded from the market, the author has been making changes so I didn't want to include it)
http://drop.io/689ghtm#
(MD5:F1B80E314926C7409DDCA6C0EE107626)
Save the zip file to your sdcard named update.zip, boot into recovery mode (home + power), and then press alt+s. I must recommend that you also do a wipe in recovery mode (alt+w) before applying the update as most of the esoteric issues that arise seem to be from not wiping. This will clear all your data/settings/apps, and you will have to re-register once it boots back up.
Again THANKS JESUS FREKE
Cool thanks for this, glad to see it worked out.
Do you think I would need to do a wipe going from mt rc33 to no-mt rc33?
Doesn't seem like such a large zip is necessary.
Does the MT really alter so many files?
Hopefully there will be a mini version that does the same thing
Only the Kernal is changed so if you want you can extract the boot.img and use the flash_image tool to re-image it over your current one. JF has a thread about the flash_image tool and how to use it at this link
The reason it's so large is because its a full ROM you can flash from RC29 etc. You could probably get away with not wiping but I have to recommend it since 90% of the issues people run into doing the updates seem to end up with a wipe so why not skip the issues. Its easy so re-sync contacts and reload apps.
Hahha thanks, so then the only diff is in the boot.img? Cool.
So I could just switch boot.img's and flash whenever I want to switch between normal and MT?
Ima try it righttt now
Any chance for a ADP1.1 No Multi-Touch ROM? Please?
why would any1 one want it without the multitouch?
Because of few problems with the MT version.
I just used fastboot to flash the image nd I gotta say, touch is workin great.
I like it better this way for sure.
Im gonna wait til multitouch gets fixed up and then ill try it again.
Thers is any "problem" with the multi-touch except that devs are not making apps for its kernal. Therefore some apps may act funny.
I personally don't use the MT at all so I don't want it throught the OS. And I don't know if its in my head but the pre-MT kernal seems to give me better battery life.
topdnbass said:
I just used fastboot to flash the image nd I gotta say, touch is workin great.
I like it better this way for sure.
Im gonna wait til multitouch gets fixed up and then ill try it again.
Click to expand...
Click to collapse
Good to hear. Flashing the boot.img is really all that's needed but I wanted to make a full update just for the exercise etc since this is fairly new to me and fastboot might be more difficult for some.
Yeah It's not really a problem.
I figured it's good that both ways are on here now though.
Thanks again!
If youre already running jf rc33 do you need to do a wipe?
Ah, apparently I didn't announce mine with enough fanfare
Oh well, it is a fun exercise.
Uh, and so why would I ever want or need this flash? Dead thread. Nothing added and of no value.
But nice try. Must really like your iPhone and your paycheck...
learningmore said:
If youre already running jf rc33 do you need to do a wipe?
Click to expand...
Click to collapse
you will probably be fine without a wipe but i recommend wiping when flashing
quietlurker said:
Ah, apparently I didn't announce mine with enough fanfare
Oh well, it is a fun exercise.
Click to expand...
Click to collapse
Glad you got the issues worked out as well. not trying to be disrespectful or anything but I told people i would make up a ROM so i did and figured it might as well have some instructions in case someone needs them. I did see that you had put one up but at the time thekills was complaining about the browser so I went ahead with my version.
and it is a fun exercise
Edited:double post
justanothercrowd said:
you will probably be fine without a wipe but i recommend wiping when flashing
Click to expand...
Click to collapse
Ok i flashed without wiping everything is running good. Phone is much more responsive touch wise. Everything else still works great. Thanks to you and JF
Gadzks said:
Uh, and so why would I ever want or need this flash? Dead thread. Nothing added and of no value.
But nice try. Must really like your iPhone and your paycheck...
Click to expand...
Click to collapse
There were request from a number of people for a non multi-touch version. If your not interested simply don't use it.
And as for the other comments....lol
justanothercrowd said:
Glad you got the issues worked out as well. not trying to be disrespectful or anything but I told people i would make up a ROM so i did and figured it might as well have some instructions in case someone needs them. I did see that you had put one up but at the time thekills was complaining about the browser so I went ahead with my version.
and it is a fun exercise
Click to expand...
Click to collapse
No worries. If you keep updating your branch in the future, you may want to be sure and change the ro.modversion in the build.prop file.

Cupcake Question

Now I want to put the official cupcake update on my phone, Now I dont care about my apps and settings since I can always re do them, But how could I have cupcake on my phone.. WITH it rooted and most importantly still be able to put my apps on my sd card?
I see here,
http://forum.xda-developers.com/showthread.php?t=462512
So by this I can root it and add the cupcake update, now when i did the apps on sd update, I used the guide that has the update.zip, so im guessing if I do the instructions above ill be able to wipe out my phone, re root it, and update it with cupcake, then all i need is to find a way to add apps on sd card, my question to u is, is there a easier way to do it like in this post
http://forum.xda-developers.com/showthread.php?t=480582
or do I have to follow one of those really hard guides like this one
http://forum.xda-developers.com/showthread.php?t=504235
So to clarify, i want rooted phone, cupcake and apps on sd, if someone could point me in the right way/guide to do it id be really happy
ps im not a dev so I can only follow what a guide says
no, no and no. rooted phones **CANNOT** install the official OTA updates. you will get notified but it will fail. if you want official, downgrade to rc29 using the nbh (link in my wiki) and wait for OTA updates. if you want JF update, give it more time.
Darkrift said:
no, no and no. rooted phones **CANNOT** install the official OTA updates. you will get notified but it will fail. if you want official, downgrade to rc29 using the nbh (link in my wiki) and wait for OTA updates. if you want JF update, give it more time.
Click to expand...
Click to collapse
SO theres no way to have root apps on sd with cupcake until JF makes his own or someone else? or is there a way to have root and sd on apps just need to find a way to have cupcake download into it?
right now all my phone is running off JF rc33 build and JF radio update and lucus apps on sd guide
As Darkrift stated ....
If you can't wait for one of the dev's here to release their custom version of the offical firmware, downgrade to RC29 and wait for the OTA update.
Now there is no telling how long it'll be before you get this update.
If you want apps 2 sd you can wait on the custom release from one of the devs here once they release the firmware you can install it and start using your apps on your sdcard.
I'm betting the dev's here will have the modded version of the firmware out before the majority of us have the OTA update pushed to us. That is what happened last time.
I'm not the most knowledgeable person here, but you simply cannot have A2SD on an official ROM from TMo, they have never supported it, and most likely won't in the future. So the only way is to get A2SD is to get one of the modded ROMs from here... none of them are OFFICIAL, but JF's release is nearly identical (even better) and has root... I see no reason to have the official ROM
Alright thanks guys, I guess Ill wait

Radio Update?

So I've lurked here for a while reading many posts and whatnot, and have also updated to the latest JF release 1.5. Anyways, onto the question. After about 10 minutes of search button clicking, I've yet to find out how to flash the radio update I have to the phone. I've had a few complaints saying that i sound pretty bad while talking on the phone and I'm hoping this might fix it, but if not at least I'm at the latest radio version.
Here is what I recently got:
ota-radio-2_22_19_26I
Can someone walk me through on how to flash this and to the phone? If i have to wipe so be it. or if there's a guide on this can someone post it cause the search function missed it =/
xsnipuhx said:
So I've lurked here for a while reading many posts and whatnot, and have also updated to the latest JF release 1.5. Anyways, onto the question. After about 10 minutes of search button clicking, I've yet to find out how to flash the radio update I have to the phone. I've had a few complaints saying that i sound pretty bad while talking on the phone and I'm hoping this might fix it, but if not at least I'm at the latest radio version.
Here is what I recently got:
ota-radio-2_22_19_26I
Can someone walk me through on how to flash this and to the phone? If i have to wipe so be it. or if there's a guide on this can someone post it cause the search function missed it =/
Click to expand...
Click to collapse
Rename the zip to "update", put it on the root of your SD card and apply it like you do with any other flash.
Ok, then do I have to reflash the JF1.5 after that?
EDIT: sorry for all the dumb questions, I'm still learning but very interested.
nope, that just flashes your radio
Woot, it worked! TY uberingram, and BSDADON.
BSDADON said:
nope, that just flashes your radio
Click to expand...
Click to collapse
ok so when you say it flashes your radio what exactly does that mean and what does that do for or to the phone?? I have looked and looked for the answer to this and I have found NOTHING thanks!! anyone that knows can def answer!!!!
radio
Think of the radio as a manager in the store it kinda tells eveything how to work and when to work and to os as the worker pluging along not paying atention to this till the manager says stop you farked things up or it's quiting time
Ok, so riddle me this: does a rooted phone with jf adp 1.5 and the old 1.22 radio have issues with bluetooth not routing sound away from the internal speaker, and into the actual bluetooth device???

bricked one phone, got a few questions

i know its probably been posted 93578 times before, but i just want to 100% confirm here before i mod my new G1.
my last one, i accidentally installed SPL first before updating the radio, i didnt see any of the warnings before doing so, but now i know...live and learn i guess.
so....my new one, which is RC33, i know how to get it to RC29. ill do that, then root it.
after that, is this the correct process?
i was going to install the haykuro spl. but first, i read that one board wouldnt work, PVT or the other one i cant remember.
mine is PVT.
if thats the correct board, i can update the radio, install haykuro spl, then install the rom? i want Cyanogen, i believe is was 4.0.4, or whatever his latest stable version is. im not even sure ill like it, but thats the one i want to try, my friend runs that same setup (haykuro spl, Cyanogen rom) and he likes it.
also, at what point should i install the latest recovery? after radio update?
i dont wanna brick this phone hahah
thanks for any help and sorry if i asked questions that you guys answer on a daily basis
Don't be sorry. Next time post in the the appropriate section of the forum. Q&A
opps....lol
BoJANGLES!
ufvj217 said:
i know its probably been posted 93578 times before, but i just want to 100% confirm here before i mod my new G1.
my last one, i accidentally installed SPL first before updating the radio, i didnt see any of the warnings before doing so, but now i know...live and learn i guess.
so....my new one, which is RC33, i know how to get it to RC29. ill do that, then root it.
after that, is this the correct process?
i was going to install the haykuro spl. but first, i read that one board wouldnt work, PVT or the other one i cant remember.
mine is PVT.
if thats the correct board, i can update the radio, install haykuro spl, then install the rom? i want Cyanogen, i believe is was 4.0.4, or whatever his latest stable version is. im not even sure ill like it, but thats the one i want to try, my friend runs that same setup (haykuro spl, Cyanogen rom) and he likes it.
also, at what point should i install the latest recovery? after radio update?
i dont wanna brick this phone hahah
thanks for any help and sorry if i asked questions that you guys answer on a daily basis
Click to expand...
Click to collapse
PVT will work =D congratulations it's not really bricked... but yeah update the radio, then the SPL, then the ROM. the latest stable cyanogen is 4.1.9.2 if you ask me... still considered experimental but it's stable and solid and will probably be the basis for the actual stable 4.2 update...

Categories

Resources