Related
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!
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....
How to downgrade from Rc33
Ok...I updated to RC33. Didn't know before I updated that I wouldn't be able to go from RC33 to root. So now I need to downgrade.
Can anyone help me downgrade from RC33 to RC29? Or maybe even RC33 to RC30? I searched and couldn't find anything on this but did see someone post that JF walked someone thru it recently....how ever I can not find it.
Any help would be greatly appreciated.
http://forum.xda-developers.com/showthread.php?t=442480
If I could get a dollar for everytime I linked to this sticky....
acousticdank said:
http://forum.xda-developers.com/showthread.php?t=442480
If I could get a dollar for everytime I linked to this sticky....
Click to expand...
Click to collapse
I been in that thread....it's instructions to downgrade from RC30....not RC33.
And I have been going backwards in that thread from the latest posts for about 10 pages now and see nothing about downgrading from RC33.
Doesn't matter what rom you have installed as of now.
You need to follow the instructions and then pick which rom betters you.
Or even try going straight to 30 by renaming it, update, and install it in recovery mode.
Ok....I missed one small word....RC30 and above...
Thanks...in the process of trying to gain root now...
To make it clear for me, is the old downgrading process with a new german RC33 G1 still possible or will it fail because of an new SPL?
ThaBadBoy said:
Ok...I updated to RC33. Didn't know before I updated that I wouldn't be able to go from RC33 to root. So now I need to downgrade.
Click to expand...
Click to collapse
i don't really understand your problem. you want to downgrade because you don't have root anymore?
if so, it's a bit strange because i have root access on RC33 Oo
Meltus said:
i don't really understand your problem. you want to downgrade because you don't have root anymore?
if so, it's a bit strange because i have root access on RC33 Oo
Click to expand...
Click to collapse
Think he means he upgraded to OTA RC33. Anyway like the previous posters have already indicated, the NBH file downgrades OTA RC33 as well.
ah i see, my mistake.
Hey guys I have two quick questions:
1. I have an OTA rc33 (stock) update on my phone I just received today, in order to root my g1, I will need to downgrade to the stock rc29. It's imposible just to get my phone rooted straight from rc33?
2. If the first question is true. After I downgrade and rooted the rc29, can I just download the latest jfv1.41 rc33 (developer version) ? Or I would need to update the rooted rc30 first in order to get the jfv1.41 rc33.
Your kindly help and suggestion are greatly appreciated.
phuthanvinh said:
Hey guys I have two quick questions:
1. I have an OTA rc33 (stock) update on my phone I just received today, in order to root my g1, I will need to downgrade to the stock rc29. It's imposible just to get my phone rooted straight from rc33?
Correct you need to downgrade to RC29 first for root.
2. If the first question is true. After I downgrade and rooted the rc29, can I just download the latest jfv1.41 rc33 (developer version) ? Or I would need to update the rooted rc30 first in order to get the jfv1.41 rc33.
For RC29 you can install JF's Modded version of RC33
Your kindly help and suggestion are greatly appreciated.
Click to expand...
Click to collapse
You're welcome
Just One Question:
Is it still possible to downgrade with an GERMAN G1 with the original Bootloader installed on it, or is the security hole fixed which allows downgrading with the nbh File. Please do someone answer me that question please
I tried root but had problems went back to RC29 stock but now I would like to go to RC33. What do I need to do to manually update?
Viper
Links to manually update are here:
http://forum.xda-developers.com/showthread.php?t=479571
i manually installed rc33 ota update and so i decided root my g1 then i get stuck on the colorful boot screen.
as the instructions on downgrading from rc30 i suspect it would be the same on a g1 with rc33.
im not sure if the formatting was done correct but i did the following:
on my eee linux netbook i typed
umnount /dev/sdd1
mkdosfs -F 32 /dev/sdd1
the zip file contained a file named "DREAIMG.nbh" the instructions quoted the file name as "DREAMIMG.nbh" so i tried it with both names and i get the same thing.
on another thread
http://forum.xda-developers.com/showthread.php?p=3271739&highlight=image+rc29+rc33#post3271739
if anybody can shed some light please. thanks =)
if i load a new spl will it help?
mark925 said:
Links to manually update are here:
http://forum.xda-developers.com/showthread.php?t=479571
Click to expand...
Click to collapse
Thanks but that want work as I am at RC29 right now. That file says from RC30 to RC33.
Viper
to the official RC33 rom. I have had some probelms with jf 1.42 and cupcake. So i just want to go back to what i had. I searched already. I would just like an Update.zip file
The fastest way is just to use the same DREAIMG.NBH you used in the process to root, then apply an official update.zip. Otherwise get an official update.zip and use a signing tool (e.g. signapk) to sign it with the test keys.
This is what I found
**Didnt my link didnt work, not signed. something I have no idea how to do
jashsu thanks worked great!!! thanks man
jashsu said:
The fastest way is just to use the same DREAIMG.NBH you used in the process to root, then apply an official update.zip. Otherwise get an official update.zip and use a signing tool (e.g. signapk) to sign it with the test keys.
Click to expand...
Click to collapse
Ok so I have rc29. I thought it would just ask me if I wanted to upgrade but it hasn't all day. I'm guessing its not an original file. Do you knoww where I can get the original signed file?
Found it!! Thanks for the start
Rc29 to RC30
RC30 to Rc33
hey man i had a modded rc33 but i went to th 5.0.2H build and i wanna go back to just rc33, is that what you did, if so please explain to me how you did it.... please
idragbody said:
hey man i had a modded rc33 but i went to th 5.0.2H build and i wanna go back to just rc33, is that what you did, if so please explain to me how you did it.... please
Click to expand...
Click to collapse
I copied DREAIMG.NBH the file you used to get back RC29
then I downloaded the files in the links i posted. and updated my phone manually.
Rename the files to Update then hitting the home button when you restart then phone
Rc29 to RC30
http://android-dls.com/files/apps/signed-RC30-from-RC29-fat.1582cace.zip
hello! i rooted my phone before to get the 1.5 cupcake update downloading from some website.. then i installed back rc29 but now idk how to go back to rc30 or higher ( i think i need to go from step by step meaning after rc29 its rc30 then next one isnt it?)
can anybody help me with links where i can try getting rc30 or i can already just go from rc29 to rc33??
You can go straight from RC29 to RC33.