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!
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....
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?
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.
WHAT THIS IS FOR:
This is for those of you that upgraded to the newest rogers rom, and caught yourselves with an unrooted device.
IMPORTANT NOTE: Emergency phone calls are broken in this version (the whole reason for the upgrade), so see to it that you switch to a rom / boot.img that doesn't suck. (thanks a lot rogers >_>)
http://haykuro.polygonize.com/ROGERSDREAM.nbh.zip
Steps to take:
1. Download the file
2. Extract and rename to DREAIMG.nbh
3. Place on root of SD card (your SD card has to be formatted as FAT32 if it fails to find it in the next step!)
4. Power off, hold camera button, power on. This will boot into SPL and prompt you to install. Proceed.
5. After your phone is done flashing, it will prompt you to press another key to reboot the phone. Do so.
6. Use flashrec, and follow procedures to root again.
Haykuro strikes again! I didnt put the update on but im sure this will be put to good use.
wow dat was quick, so downgrade and follow the rooting process again is it ?
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Sejanus said:
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Click to expand...
Click to collapse
if u havent update to the new rogers rom and having CM 4.2.13 then forget abt this,
if u flash rogers rom u will lose your root as i did
so better not to if u like the root, cos there is nothing special with the rogers update,
but the Magic update is awesome
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
I get the same thing! arrgghgh
Haykuro: can we use goldcard for this???
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
Get the same thing. Thanks for the effort Haykuro. Anything else up your sleeves?
ok update failed
dammm... was hoping for a fix!
Dropped the nbh file in my goldcard....nada....failed the same way.
I even ran the 1.89 RUU and replaced the rom.nbh file in the temp folder with the old one we all downloaded and named it rom.nbh.... just to see what would happen....failed
I'll have to try another goldcard....I might have messed up somewhere.
Can someone please try this with a goldcard and see if it works?
Thanks haykuro for getting on the ball on this....
Rogers.....karma is gonna be a B*&%$......for you guys one day....
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
weird, I have lost all the signal ever since trying to flash the nbh file
copolii said:
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
Click to expand...
Click to collapse
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
alan090 said:
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
Click to expand...
Click to collapse
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
copolii said:
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
Click to expand...
Click to collapse
... and that is even though HTC would be perfectly happy to make a 1.6 for them.
I assume that the 1-click-root vulnerability is gone, anybody try it?
Annoyances
So, I called Rogers tech support on Monday morning after they turned off my 3G and told the tech guy there that I've been running a ROM with the 911 fix since last September or so, and could they please turn my 3G back on. He did something on his end to re-provision my phone. I had to take out the battery for a little while and then boot my phone, and 3G came back up for me.
This wasn't good enough for Rogers. They have been sending me two text messages a day (one English and one French) and then calling me (twice) with recorded messages warning me about the 911 problem and that I need to 'upgrade'. This is a serious customer satisfaction issue with me. So, I figured it'd set me back for a few days, but I did the following to downgrade my phone from Cyanogen to the Rogers Donut-Hole release:
1) Installed Windows XP mode on my Windows 7 64 Bit OS, because the HTC Sync program wouldn't work on Windows 7 64-bit.
2) Downloaded and installed the HTC Sync program on my Windows XP virtual machine.
3) Dug around and found an old JACxHERO 1.0 ROM and I flashed it, hoping that the Rogers updater wouldn't detect this as a violation and abort.
4) Rebooted the phone, and joy of joys was able to get HTC Sync to connect to my virtual machine. The JACx HERO ROM has HTC Sync inside it, which was enough to fool the installer.
5) Ran the Rogers downgrader. This ran successfully... I just had to babysit the USB 'Attach' menu. If you're not on a virtual machine, you shouldn't need to worry about it.
6) Now I have the updated Radio image, and a downgraded 1.5 Android image.
I miss 1.6 terribly already. I wonder how long it'll be before Rogers detects that I've performed the upgrade so that I can try out this new Hakuro goodness (thanks Man!) and get my phone to a decent OS again. Anyone know how Rogers is detecting the upgraded version? Are they simply looking at the Radio image version? Or do they also know what OS Build I'm running?
I also upgraded my wife's phone. I hope the SMS and Recorded message abuse will now go away.
My message to Rogers would be: Get out of my life. I already pay you far too many dollars for the privilege of holding and using an HTC Dream on your golden network. It is super nice that you regard my safety above all else, however I have never in my life called 911, and really my safety is not your responsibility. I already know about the 911 bug, and had it fixed before you decided to meddle with all of your Canadian customers by removing their network connectivity and abusing them with myriads of reminders. Get out and stay out of my life!
Have a nice day.
I've tried all the usual methods with fastboot. Flashrec doesn't work. Logging in via adb doesn't give me shell access. Someone's tried the goldcard method.
Sigh.
Haykuro, what was your process for initially rooting the Magic? Didn't we send you one and you had to hook up some wires to it to get some port #s or something? (Sorry, it was long time ago.)
If need be, I'm getting an Magic upgrade once they are in stock and I'd be willing to lend you my Dream to hack at.
Sorry to here that you did that but as of now you are fooked.
There were steps in 1 of the 5 threads that told you how to perform the upgrade without flashing the "perfected perfect" spl but it's too late now.
sorry for your luck.
Same issue as everyone else, unable to flash old image...
My phone has been unusable since the update, reception has dropped to emergency calls only in my house, and 1 bar outside.
Every hour or so I have to reboot the phone, I get some ".process" error that keeps popping up in an infinite loop.
I need the droid from telus to be released, I have to ditch this garbage.