Hi there,
Sorry if this thread is redundant, but it seems the topic is always buried within other threads versus focusing on it. Then again, maybe it's a simple answer and needs no focus.
I had some quick questions before I mod my G1, and know it has been touched upon, but just want to make sure.
Once your phone is modded and using the test keys, then is it currently impossible to ever go back to an official firmware update without the need to resign it with the test keys?
I guess I am curious if Google ever did force a 'test key' OTA update that took away root (or worse), then would we be stuck at that version until someone finds a way to flash the device via other means? Even if we had root, would we ever be able to revert back without having Googles private key?
Also, with the new modded firmware will we be able to install older revisions (i.e. go back to an earlier modded release candidate? say RC32 to RC30)
Thanks,
olsk00lz
If you're that worried about Google signing an update with the test keys (which, FYI, would be a horrible idea, as the devices that have the official keys would freak and couldn't update), then do this:
Make your own keys (it's not too hard, I'm sure JesusFreke could help), sign the modded RC30 yourself, and update to that. There's nothing Google could really do to stop that, except somehow make an update that didn't require signing. If they did that, we could just make our own update that didn't need signing, which wouldn't even require root access anymore.
Makes sense, but questions still remain. More out of curiosity.
- If you wanted to sell your phone as stock or something later and wanted to revert back to "enable OTA"... is there anyway to do this?
* May not be possible without a private key???
- If you are using the test keys, or your own keys, then can you install any firmware. a) revert from a modded RC32 to a modded RC30 with google test key, or b) switch from a modded RC30 (goog test key) to a modded RC30 (your own key)
* Should be possible if you have both public/private keys??
Also, anyone see an impact with the new fingerprint being sent back to google, I have seen suggestions to create a new entry in your host file to prevent this.
Thanks !
oldsk00lz
Yes, you can go back to stock updates.
You can grab the recovery image from one of the official updates and flash it in the same way you did to get the modded one, and then apply the official update.
oldsk00lz said:
Makes sense, but questions still remain. More out of curiosity.
- If you wanted to sell your phone as stock or something later and wanted to revert back to "enable OTA"... is there anyway to do this?
* May not be possible without a private key???
- If you are using the test keys, or your own keys, then can you install any firmware. a) revert from a modded RC32 to a modded RC30 with google test key, or b) switch from a modded RC30 (goog test key) to a modded RC30 (your own key)
* Should be possible if you have both public/private keys??
Also, anyone see an impact with the new fingerprint being sent back to google, I have seen suggestions to create a new entry in your host file to prevent this.
Thanks !
oldsk00lz
Click to expand...
Click to collapse
Yes, you would be able to reflash the official keys, so that it'll OTA update again. You should have backed up your keys before you flashed (I'm not sure if the guide on the forums tells you to do this, it probably doesn't, so you shouldn't follow that exactly).
You probably won't be able to go from modded RC30 to official RC30. The updater would probably disallow it because it is the same version. I think you'd have to modify the modded to RC29 (although, there's probably a build number that it uses somewhere, I doubt they use the RC identifier we do for update checking).
If you were to resell the G1, just reflash the normal keys. When the next update comes out, he'll be back on stock.
Gotchya.... Thanks!
I think your question has already been pretty much answered, but let me clarify the details
There are 2 ways you could apply an "official" update over a modified one:
- You can resign the official update with the keys used by the modified recovery image.
- You can re-flash one of the official recovery images, and then apply the official update without having to re-sign it. The updates themselves contain the recovery image for that version (look for recovery.img). So you could extract that file, flash it onto the recovery partition, and then apply the update.
hey J.F. correct me if im wrong...
But you included the goog signed recovery.img in the androidmod.zip so you could just refollow the directions in the package to go back to a goog signed G1.
At least that's how I understood it.
Bhang
Your missing out on something important here.. when most of the population will have been upgraded to a non rootable firmware your rooted g1 will be worth n time its original value. Why on earth would you sell it locked for 1/2 of the original price???!!!
bhang said:
But you included the goog signed recovery.img in the androidmod.zip so you could just refollow the directions in the package to go back to a goog signed G1.
At least that's how I understood it.
Bhang
Click to expand...
Click to collapse
No, I included the RC29 boot image (not the recovery image), which was just a convenient "known good" boot image I had laying around at the time when I packaged it up.
You'll need to get an official recovery image from one of the official updates. It's called recovery.img, and is in the system folder in the zip file.
mrboyd said:
Your missing out on something important here.. when most of the population will have been upgraded to a non rootable firmware your rooted g1 will be worth n time its original value. Why on earth would you sell it locked for 1/2 of the original price???!!!
Click to expand...
Click to collapse
No, it won't. As it's been said before, I did quite a bit in the PSP scene for hacking/homebrew. A rooted G1 won't sell for much more than an unrooted one, if its at all higher.
New exploits will be found, and I won't be shocked if eventually Google just opens it up.
I gotta say, this one may be up in the air.... until hardware competition comes out that is. How many UNIX/Linux-heads out there will find out that you can have Debian or some other cool stuff that just doesn't work on a standard G1? I haven't even looked at what O/S PSP can run, but think you will still have to code with there libraries, no?
I think once we are able to tighten down root with actual logins, and make the modded phone more secure, some of the worriers will have wished they had a modded phone. Okay, I am sure other exploits will be found some day... I have enjoyed watching the community get as far as it has.
So... anyone want to buy my modded RC30 G1 for $1500.00 USD?????? Any takers?? (Okay, I think I can concede that even if there is a profit or not on ebay, it probably won't be much of a markup unless you reach the right target audience.)
-oldsk00lz
Reverting from Modified RC30 to official (updated to NBH method)
Update 1/13/2009:
Reverting via the RC29/RC30 NBH files is a more straightforward method. Download those files here.
The original update.zip method is deprecated in favor of the NBH method. I am removing the update.zip files from my server space. Text remains for historical purposes.
These are update.zip files for taking a G1 with MODIFIED RC30 or any other G1 with test key signed recovery partition (e.g. white developer G1s) back to official firmware. You have the option of RC29 or RC30. These will install official ota firmware.
As usual rename to update.zip, dump into sdcard and reboot G1 into recovery.
MOD RC30 --> OTA RC29
Download (Root bug still enabled)
MOD RC30 --> OTA RC30
Download (No root access. Can still downgrade using NBH)
Hopefully this will help for folks who want to revert to official firmware from the xda-dev modified firmware or have a white developer G1 and want to update it but aren't getting ota updates.
jashsu said:
.... or have a white developer G1 and want to update it but aren't getting ota updates.
Click to expand...
Click to collapse
Maybe I'm not understanding ... is there a 'whit developer G1' ? Where can we get them?
Thx
This will VERY RARELY be needed. If you were not sent to this thread to download this because of a major problem, you should probably ignore this. These are for worst case use only.
Those who need these will know and be looking for them already (so now they can find them )
Help - is my phone bricked?
tried converting back to official RC30 from JFv1.31.
downloaded the ota-rc30-testkey-noassert-update.zip, renamed it update.zip, put it on SD card, Home+Power into recovery mode, it comes up with the red, green, blue screen and then it quickly displays the message 'No Image File!' and then goes back to red, green, blue screen displaying the following text:
DREA100 PVT 32B
HBOOT 0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2, 2008
Serial0.
Pls help....
The RGB screen is the bootloader screen, not the recovery screen. To revert using the bootloader screen, you need the NBH file, not the update.zip file. Get the RC30 NBH here.
jashsu, thanks for the quick reply
but that is what I had attempted earlier, but that failed. Sorry, I should have mentioned that.
When I tried the DREAMIMG.NBH file, the bootloader did find the image file, and it showed me the progress bar, the progress bar goes all the way till the end, but none of the steps had ok next to it at the end and it said Update terminated update failed.
that is when i tried doing it this other way.
EDIT
OK, never mind, for some reason when i re-attempted the .nbh method, it worked this time. i re-downloaded the file from the site you linked to this time, maybe the 1st attempt file was corrupt in some way.
Thanks again...!
KG
this is good to know, that way when the official cupcake comes out, I can upgrade!
Related
http://www.megaupload.com/?d=QPUWC9AC
ROM Re-flash (THIS FILE IS LEAK FROM HTC)
1. Format the SD card to FAT32 mode
2. Copy image file XXX.nbh to the SD card and rename to DREAIMG.NBH
3. Turn the device power off and insert Diagnostic SD card
4. Hold Camera button, and press Power button to entry Boot loader mode
5. Press Power button to start upgrade procedure
6. After finish, perform the soft reset to reboot
Please check this link Service manual for G1 (Page 63-64) for more info http://forum.xda-developers.com/showthread.php?t=457133
Mod Edit: Link broken but get Manual Here: www.mikechannon.net
Can we have more of a discription of what exactly this is???
DreaIMG_1.26.531.2_Official_signed.nbh
find this file, still don't know what it is!
http://odiness.com/misc/android/DreaIMG_1.26.531.2_Official_signed.nbh
Mirror. Have not tested.
it is a origional RC30 and without root, right?
hskoon... can u describe what r u posting here...? we know it's RC30 image but if it's the OTA RC30 ver, then it'll just do more harm here & pointless
Can we have DREAIMG.NBM file for RC19 or RC28 or RC29
With this, at least now we can upgrade to an official version of Cupcake without worrying it patched up any (yet to discovered) security holes in RC30.
Still hoping to root my official RC30 phone...
coolbho3000 said:
With this, at least now we can upgrade to an official version of Cupcake without worrying it patched up any (yet to discovered) security holes in RC30.
Still hoping to root my official RC30 phone...
Click to expand...
Click to collapse
HTC can have Google change the private keys of their bootloader with no consequences. HTC/T-Mobile is the only one that uses them, so they'd just have to check which version to use before reflashing. If it's an older phone, use the older version.
Basically, the cupcake build can include new keys which would make this .nbh useless.
Gary13579 said:
HTC can have Google change the private keys of their bootloader with no consequences. HTC/T-Mobile is the only one that uses them, so they'd just have to check which version to use before reflashing. If it's an older phone, use the older version.
Basically, the cupcake build can include new keys which would make this .nbh useless.
Click to expand...
Click to collapse
Crafty, aren't they. What are we to do?
ok testing this dreaimg.nbh on my non rooted official rc30 so that if it indeed is official RC30 no loss. will post results shortly.
Update Terminate UPDATE FAIL
no soup... tried this on my locked RC30 G1 and the update failed.
WARNING!!
From what I can disect from the file it includes t-mobiles shipped SPL, so if flashed and you have a eng bootloader or a dev phone it might overwrite your fallback bootloader!!!!
To the Poster, if you had access to this version can you see if you can get for us any earlier version before rc30, and or rc8 for uk phones. This would be most excellent and allow us to revert all rc30 rc8 phones.
Thank you for your time and effort!!!
Its just the RC30 nothing special about it.
so, i would highly advise that nobody use this. I had a perfectly usable g1 official rc30 and after trying this NBH and it failing, the phone is now unusable. REPEAT DO NOT USE THIS IMAGE!!!
The image update did not fail on my g1.
But ended up with the the same non rooted rc30 as i had on that phone.
indeed stupid... and double post.. http://forum.xda-developers.com/showthread.php?p=3014684
bunny0007 said:
The image update did not fail on my g1.
But ended up with the the same non rooted rc30 as i had on that phone.
Click to expand...
Click to collapse
bunny0007 what steps did you take? did you have to rename the file to dreaimg.nbh and remove all the other stuff? i would like to try to reflash this one to at least get it back to stock rc30
Yep renamed it with capital letters to DREAIMG.NBH on a blank sd, and flash it thrug the bootloader.
But the system and user date took a while.
odd, thats what i did to two of these testers that i had and both got corrupted... oh wait, it wasnt capital letters, not sure if that would make a difference or not, but it seemed to have found it and started working... let me try with caps....
i have a g1 that i installed Jesusfreaks 1.31 to and also flashed hardspl to it.. im having serious battery issues so i am going to return my phone for another one.. im trying to find a how-to on reversing everything i have done along with the stock rc30 image... can someone please point me at a tutorial or in the right direction...
i have googled it for the past 30 mins and have found nothing..
thanks
Download the G1Orig SPL here, flash that. Then download one of the revert update packages here and flash that. Remember to Alt+W to wipe the user and cache partitions too.
Edit: By the way are you having recurring serious battery charge loss or was it just one event?
You could flash the original bootloader (image is in the SPL thread) and then load the stock t-mobile rc29 onto your phone. Then take your phone to T-Mobile for warranty.
This way it just seems as though your phone never got the OTA rc30 update
I brought my phone in to ask a question about a clicking noise my phone had (the arm that the display moves on feels loose) when open. The guy behind the counter asked to see my phone and I was not thinking...he took it and noticed the clicking but said it was normal; he showed me his phone and a few display phones that did the same. Then he fired up "About phone" and suddenly became quite...he turned quite confused and told me that this was not a Dev phone. I played dumb and told him "I don't know, this is how it came from the store when I got it last month..." He then rebooted my phone to see both custom spash screens and the engineering boot loader...I wish I had a camera for the look on his face.
Oddly enough, both he and his manager were reluctant to give me my phone back.
So yeah, I recommend putting a stock rc29 on your phone before taking it in
i downloaded the origSPL and when i go to flash it with alt s it says verifying update package
no signature
verification faield
installation aborted
its renamed to update.zip and im assuming because i have done this before that i am doing it correctly .. any advice?
Did you already revert back to official Android? The SPL updaters are signed with test keys, so if you have already reverted to official Android then anything signed with test keys will fail to flash.
this is my build and kernel version..
would this be the updated rc30? i thought that i updated it correctly and i assume that i could not have flashed hard spl if i hadnt
Kernel version
2.6.25-01843-gfae26b0
[email protected] #19
build numberer kila-user 1.0 tc4-rc30 116143 ota-rel-keys,release-keys
When you enter recovery mode do you see JF's custom background or is it the standard recovery?
its JF's recovery screen.. im thinking to flash the test key recovery.img and then downgrade.. flash the new orig spl then the orig rc30.. witll that work?
If you're seeing JF's recovery screen then you already are running on test keys; there is no need to flash a different recovery.img
i have reformatted the sd card a bunch of times... only thing i can thnk of is that when i download the files from here to my mac it comes as a folder and then i zip them and rename them.. can this be the problem?
Comes as a folder? Sorry, I have no idea how macs work (or don't). You should not need to be zipping anything. If it worked before in the past i'm sure you got it working somehow. The MD5 of the file as it appears on the sdcard should be the identical to what I posted in the SPL sticky.
honestabe said:
i downloaded the origSPL and when i go to flash it with alt s it says verifying update package
no signature
verification faield
installation aborted
its renamed to update.zip and im assuming because i have done this before that i am doing it correctly .. any advice?
Click to expand...
Click to collapse
just use the RC29 NBH file and flash it from SD card. this will make it like it was out of the box.
but the spl will be the hardspl not the orig spl correct?
NBH file doesn't overwrite the SPL though, does it?
honestabe said:
i have a g1 that i installed Jesusfreaks 1.31 to and also flashed hardspl to it.. im having serious battery issues so i am going to return my phone for another one.. im trying to find a how-to on reversing everything i have done along with the stock rc30 image... can someone please point me at a tutorial or in the right direction...
i have googled it for the past 30 mins and have found nothing..
thanks
Click to expand...
Click to collapse
Just flash the Dream file here : http://forum.xda-developers.com/showthread.php?t=463779
It will go back to RC29 and back to that tri-color boot screen, then get the OTA RC30 here : http://forum.xda-developers.com/showthread.php?t=451090
ok.. i figured it out.. here was the problem.. on my mac when using safari in the preferences it has an option to auto open trusted files ..ex. pdf zips etc..
so it was unzipping the zips into folders.. then when i was re-zipping them it was messing it up.. i now have it working..
hope this helps others with this problem
and thanks to you guys for trying to help me trouble shoot it
honestabe said:
my mac when using safari
Click to expand...
Click to collapse
There's your problem
that brings up the question...
to make thing simple for people.
Does anyone have the orignal G1 recovery.img image so for those who want to revert back to orignal firmware with ORIGNAL keys it would be nice.
for some people its better for them to know that thye are reversing their steps them.
what I know from all the threads above is just loading loading firmwares with test keys....
now how about the original recovery.img. Provding a reverse would be nice.
=)
Getting the original recovery.img is easy. Just download the original RC30/RC8 file from any mirror and open it up with your favorite archiving program. However in order to revert the SPL you would still need to be using test keys.
recovery I can do
the reverting of SPL..hell I dont know how to do that....
oh no, oh no, what have i done??
I've created a little problem for myself. While at work I performed a wipe/restore on my phone. I have modified rc30 jf 1.3 and when my phone is booting up now I get stuck at the android screen. The green light near the ear piece comes on and a ringing can be heard from the speaker. I have tried to wipe again to no avail. Has anyone heard of this happening? Is it because I have a theme file on my sd card named update.zip? I know I can't be the only one to brick their phone!
blehman said:
I've created a little problem for myself. While at work I performed a wipe/restore on my phone. I have modified rc30 jf 1.3 and when my phone is booting up now I get stuck at the android screen. The green light near the ear piece comes on and a ringing can be heard from the speaker. I have tried to wipe again to no avail. Has anyone heard of this happening? Is it because I have a theme file on my sd card named update.zip? I know I can't be the only one to brick their phone!
Click to expand...
Click to collapse
Try reflashing JF 1.3. Did u create a backup?
I did not backup. I will reflash when I get home.
blehman said:
I did not backup. I will reflash when I get home.
Click to expand...
Click to collapse
That should work. I had the same problem.
thanks, i need to hear that.
how would i go about using hard spl to bring it back from the dead?
Foolproof solution would be to use RC29 DREAIMG.NBH. More intricate solution is to fastboot flash your nand backups (provided you had the foresight to make backups in the first place).
What jashsu said. I nearly bricked my phone once but reflashing with RC29 was the quick and easy way of saving it.
i need help think that i am bricked
I was on 1.1 ADP JF with the mac 2.2 theme for 1.1 ADP i wanted to get back to the original theme so first i installed the restore theme thing on the fourms after this i have been stuck at the android screen when booting. i have tried to the wipe alt W but right now i am downloading the image file to get back to the original rc 30... can anyone help me out??? i really need to my phone tommorow and help would be much appreciated thank you
Assuming that you have the JF recovery utility, you should be able to copy the update.zip for RC30 to the sdcard (take the sd card out of the phone and copy update.zip to it), and apply the update from the JF recovery utility. You can get into the recovery utility by holding home+power when booting the G1. I hope this helps.
assuming if the above post don't get you up and running you will want to donwload the stock rc29 dreamimg file and copy that manually to your memory card and with the phone off. Hold down the camera button while turning on and you will get a grey screen the and should let you flash back to the original rc29 if you can't to an alt w whipe this would be the next thing I would recomend.
Just to clarify you said your phone is the adp - android developer phone, a phone that allows you to restore the phone to earlier states?
If this is the case you just need to grab a recovery image and reflash your phone by depressing camera on boot or using fastboot to restore your phone to an earlier backed up configuration.
If you don't have the developer phone, and infact have a rooted handset with a custom firmware such as JF your best bet would be as above to roll back to rc29 or rc07 if you're uk based using RC29 DREAMING.nbh -steps can be found here http://android-dls.com/wiki/index.php?title=Root_For_RC30
The downside is this will require you to reroot your phone. May i suggest in future if you do NOT have a developed phone you install Nandroid and do regular backups before playing with your phone -details here http://androidcommunity.com/forums/f28/nandroid-v2-0-full-nand-backup-and-restore-tool-9336/
Let us know hopw you get on and if we can offer any further assistance.
ok thanks guys
i installed rc 30's official image to my g1 by power+camera and everything is fine besides being unrooted i think i will root back to ADP again because of its advantages but if i am the flash a theme once again how do i get back to original theme because im sorry but i still dont understand the steps needed to do this from a ADP 1.1 jf build ty
You should have tried updating back to the 1.1 ADP JF version you were on first, would have saved you alot of time.
Hey! I assume for the purposes of this post and on accout of your having dev phon firmware you know how to use fast boot. if not go to http://androidcommunity.com/forums/f28/nandroid-v2-0-full-nand-backup-and-restore-tool-9336/
Anyway if you restart your phone with the home button depressed alt b makes a back up, use fastboot to flash this to your phone and restore it to an earlier state!!!!
Can the G1 officially be bricked?
I know you can screw up and update or 2...but with the PWR + Camera thing and the Home + PWR update method...is there a way to officially brick the G1? or is it relatively brick-proof?
I wouldn't think any phone is brick-proof. Then again, the G1 does seem more "mod" friendly than others.
Flash a corrupt SPL and you will have a brick really fast
AbsoluteDesignz said:
I know you can screw up and update or 2...but with the PWR + Camera thing and the Home + PWR update method...is there a way to officially brick the G1? or is it relatively brick-proof?
Click to expand...
Click to collapse
Try it really quick and please post your results lol
I might be wrong, but I think as long as we don't mess with the boot loader, it should always be able to start with camera-power
ok since there are 5 threads right now on the first page about how to do it and there shouldn't be, this is what you do, i will not link anything to anything because you should be able to find everything pretty easily(they are all stickies)
so all of you that messed something up on your phone and need to get it back into warranty this is how, FOLLOW THESE STEPS:
NOTE: if you have flashed a custom splash screen to splash2 then you will need to erase that before step one with this code
plug phone into usb in fastboot mode
Code:
fastboot erase splash2
After that you will have only one splash screen and when you flash the .nbh you will be fine
1. Get the original SPL for your phone, get it here
2. Rename it to update.zip and copy it to your sd card. /sdcard
3. Download the DREAIMG.nbh from here.
4. Place DREAIMG.nbh on the root of your SD card. /sdcard
5. Go into your phones recovery. [Hold the home & power button]
6. Push Alt+S on your G1 to flash it with update.zip
7. After it does its thing, gettig back to your home screen.
4. Start phone in bootloader. [Hold camera+power button]
5. Hit power to start the update DO NOT INTERRUPT!! i can not stress this enough.
6. Click on the action button(track ball) and your phone will reboot.
7. YOU NOW HAVE STOCK FIRMWARE, it will update on it's own in a little bit, or *Settings>About phone>System Updates*
MODS PLEASE I'M BEGGING YOU TO STICKY THIS POST OR AT LEAST THIS ONE:
http://forum.xda-developers.com/showthread.php?t=485364
so that people can stop posting: how can i unroot my phone or can i revert back to stock firmware like theres not 10 different posts about it.
Mods sticky
Hey man you got my vote it was drivin me insane tryin to find this and thank you!!! Also, just to amke sure that it worked, what is it supposed to say on "About Phone". Thank you man
Just wanted to add one point - I followed this guide, but there's one bit that might not be obvious.
DREAIMG.nbh will restore your phone *mostly* to stock. There's one thing it won't change - the second splash image. If you've changed your splash images, you might want to restore them to stock separately before following these instructions.
Wouldn't be an issue for most users, but in my case the keyboard bit the dust and I had to do a return, and once I set it back to stock I couldn't re-root (and was left returning the phone with a custom second splash image).
i followed all of these steps and as it was applying the dreamimg rc29 for me it said failure... what do i try now? it seems that now my phone will only boot to the multi-colored screen and everytime i try to apply the update it fails about 3/4th of the way through... my phone doesnt work... any thoughts on how to fix this?
found the problem, sorry for my ignorance i didnt format the card completely so there were other files in the root and all i did was reformat and just copy the nbh file back over and it worked just fine sorry guys
one question...do i have to find the stock rc30 and rc33 to update also?? aren's there somethings required to update to cupcake? (like radio??)
kenny9438 said:
one question...do i have to find the stock rc30 and rc33 to update also?? aren's there somethings required to update to cupcake? (like radio??)
Click to expand...
Click to collapse
you don't need to find the RC30 or RC33 files because when you have the stock RC29 your phone will update on it's own after a few hours. the only thing needed to upgrade to cupcake is the cupcake image. the radio is a choice and you ocan choose not to flash it. i still use the original radio that came on the phone with RC30 simply because i have been too lazy to get the latest radios
bump. good info
DreamingTTE said:
I just unrooted myself, just for a while.
Now I am on RC8, am I going to have to play the waiting game for RC9 uk or can I grab RC9 elsewhere? I have searched on this site for RC9 and it just returns 0 results.
Excuse my fatal error newbish ways, there is lots of us out there. ;o)
Thanks.
***EDIT***
It just automatically did it! Ignore my post.
ERRRR.....its 1.5 now, and im in the uk. it says firmware 1.5!!!!! build number CRB17 KERNEL 2.6.27.-00392-G8312BAF ANDROID [email protected] #72
lol Am I the first in the uk to recieve this ?
Click to expand...
Click to collapse
I did the same thing. But I am still on RC8... Did you upgrade to RC9 before 1.5?
DreamingTTE said:
I just unrooted myself, just for a while.
Now I am on RC8, am I going to have to play the waiting game for RC9 uk or can I grab RC9 elsewhere? I have searched on this site for RC9 and it just returns 0 results.
Excuse my fatal error newbish ways, there is lots of us out there. ;o)
Thanks.
***EDIT***
It just automatically did it! Ignore my post.
ERRRR.....its 1.5 now, and im in the uk. it says firmware 1.5!!!!! build number CRB17 KERNEL 2.6.27.-00392-G8312BAF ANDROID [email protected] #72
lol Am I the first in the uk to recieve this ?
Click to expand...
Click to collapse
I rooted my fone for the first time today and played around. In the end I decided to unroot, because I need steeel and chompsms too much.
I went back to RC7 (my phone was previously RC9 before I rooted). How long should I expect to wait before my G1 auto-updates?
Thanks!
this should be a sticky... thanx
the greatest thing about the thread? well since making it i have only seen two people post that they need to unroot their phone and don'w know how. woo hoo
how long does it usually take to upgrade on its own? its been over 2 hours now and nothing..
its been over 24 hours since ii brought mine back to "stock" and i still havent received the update, what the f is going on? is this normal? sorry but im a newb.
same here I am back to the orignal RC29 but have not received any OTA like RC33???
to all of you that haven't recieved an update yet, there is an option in settings that will allow you to check for updates. or download anycut and create a shortcut. if you do not know how to follow the instructions in this thread you probably shouldn't have rooted your phone. i have reciueved many PM's about how to do this and as much as i am willing to help you, i expect you to have SOME common sense, if you do not i will not help
sorry man, didn't mean to piss you off, i stated im a newbie, i have the firm belief that nobody learns unless they try it themselves, albeit some help from others never hurts, + the version checker is on rc33, not rc29, hence i cannot take that route, if not i already would have. i guess ill simply continue to wait, phone works fine, just does not load any apps that have to be paid for on marketplace, i work for t-mobile, so im hoping that they may have stopped ota's of rc33 since we are launching 1.5 soon. quick question for those who know, is the build number supposed to be TC4-RC29 115247? this is the one i have. Thanks man!
+ I followed your instructions to a t. and have the classic "rainbow" android boot screen.
What happend to the sticky?? I culd have sworn this was stick yesterday.. PS thanks for this thread as i had to unroot my first g1 now i might have to do my second one .. argg..
Alternate way to revert to stock firmware without waiting for update
Hello,
This is my first post. I have been using an alternate way that I figured out to return to stock. This also works when you try to install an official update and it rejects the package due to invalid keys or device checks. You MUST already have root on your phone for this to work.
1) download official firmware image (whatever version you want)
2) extract recovery image from package to root of SD card
3) rename downloaded package to update.zip and place in root of SD card
3) reflash recovery image from terminal on rooted g1
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
4) Restart phone in recovery mode and proceed with update
5)Profit! Well, stock g1 without having to flash to RC29 and wait for an update.
I feel this is a more straightfoward way to flash back to stock. YMMV.
Hope someone can help with a few things
i have a UK Magic on vodafone, updated to crb43
Then I wanted to try the google ion rom (not haykuro, the image released elsewhere) as it was faster and had voide dialing
I used the new-recovery to install it, booting it from fastboot rather than flashing it. I made a nandroid backup first.
Anyways, I wanted to go back to default rom and OTA updates, so thought i'd restore my backup.
\
I've done this, but had to flash the new haykuro spl...
My question is will i get OTA updates with this SPL?
I cant find the stock spl anywhere for download, whats the hard spl - does it exist for the magic or just the dream???
Basically i just want the simplicity i started with not bothered with root.
really? no one knows?
dazcox5181 said:
really? no one knows?
Click to expand...
Click to collapse
Hi dazcox5181,
The answer is a few posts below yours.
I haven't tried myself as I'm very happy with my rooted Magic.
http://forum.xda-developers.com/showpost.php?p=3857151&postcount=10
Thanks, I thought that might have something to do with it.
Now back to Voda system, data and recovery with the spl linked above. Should that now get me back to being tied to vodafones OTA updates?
I'm new to Android, so I'm not sure how much of a restriction / or not this is? Are OTA updates common/regular/likely to add anything worthwhile (well, I guess cupcake was...but you probably all had that anyway)
Thanks, with a bit more research I finally stumbled on the solution.
Had to restore to crb17 from the link on the thread above, and then flash the original recovery in fastboot, then the OTA update to crb43 worked perfectly!
Phew!
I'll probably re-root sooner or later, can't help but play around on this device :0 so much more to play with than my iPhone he he
Apologies if this thread annoys anyone who says I should have searched better to start with, I did, and read many threads but theres a lot to take in!
Anyways, maybe someone else has same problem and this might have helped
and to make it easier for future searchers could you compile a detailed list of step-by-step instructions for doing this? Could be handy for a wiki somewhere
OK, will add details later, but briefly
To restore to factory:
1) Download and follow instructions to flash the crios spl (one with older version reported)
2) Download and follow included instructions to flash the SFR CRB17 image using included recovery.img (boot dont flash it)
3) Download and flash original recovery image (again from crios) can be found at thread linked earlier in this one.
Reboot, and go through usual setup etc OTA update will be on its way
Be sure to remove any update.zip from your SD before attempting ther OTA update, ie before first boot if possible
It's actually really easy now I know how, and took about 20min in total (probably less)
Where do you get the SFR CRB17?
f34r said:
Where do you get the SFR CRB17?
Click to expand...
Click to collapse
Here : http://wiki.smartphonefrance.info/firmware-htcmagic.ashx