first I think you guys are the best you have shown that the Android platform is all they said it would be, before they screwed it down. I have a UK G1 with cupcake 1.5. last night an update OTA change my buid to build CRC1. has any one tryed to root one yet. Or has the downgrade method been patched
phirejack said:
first I think you guys are the best you have shown that the Android platform is all they said it would be, before they screwed it down. I have a UK G1 with cupcake 1.5. last night an update OTA change my buid to build CRC1. has any one tryed to root one yet. Or has the downgrade method been patched
Click to expand...
Click to collapse
Haven't seen any one trying to root yet. You can be a gracious guinea pig and try it?
Related
I have seen this question plastered all over the board, but no one has "officially" answered it. There have been a "it should", "it might", "maybe it will". I don't need those type of answers lol. My question is, has anyone officially and successfully rooted the official cupcake OTA. I had root on my last G1 and had to send it back due to some issues. So I have a complete fresh G1 that was already updated to Cupcake OTA so there isn't an option for me to use Fast Boot. I am on the latest version of the radio release 2.22.19.26I. If I downgrade to RC29 using the old school method, will I run into any problems. Please only reply if you have already done this yourself. Dont need any maybes lol don't know if Tmobile will give me another G1.
Firmware: 1.5 official Cupcake
Radio: 2.22.19.26I
Build: CRB43
Thanks for any assistance.
Oh and I have used the search buttons with no results.
Did it last week with a 1.5 OTA.
And the how to root thread is full of people saying that they successfully downgraded and rooted their 1.5 OTA phones, so you didn't look very hard.
Thanks for your $.02...
Going to go root right now.
Hey there sorry for opening a new Thread but i found nowhere something about my problem... I have my G1 since it's released and i noticed that something is wrong with it. After updating to Cupcake (no root) i noticed that the Radio (Baseband) version is wrong. It should be 62.50S.20.17H_2.22.19.26I but it is 62.33.20.08U_1.22.12.29.
Here is what my phone says:
Model number
T-Mobile G1
-----------------------------
Firmware version
1.5
-----------------------------
Basband version
62.33.20.08U_1.22.12.29
-----------------------------
Kernel version
2.6.27-00393-g6607056
[email protected]#1
-----------------------------
Build number
CRC1
Please help me! I don't know what to do! Should I go to T-Mobile?
Woah, that's pretty weird. I assume you're unrooted? Otherwise you could just flash this
yeah it's unrooted. I tried to root it with the Goldcard method (So I don't have to change the SPL) to see if i get the right Radio after rooting it but it was still the same. Nothing changed. I had the wrong Radio on the official Build than I rooted it, installed the Radio, installed Dude's Cupcake and it was still the same. Now I'm back on the official Build and nothing changed. I thing about going to T-Mobile tomorrow...
mattmaso said:
yeah it's unrooted. I tried to root it with the Goldcard method (So I don't have to change the SPL) to see if i get the right Radio after rooting it but it was still the same. Nothing changed. I had the wrong Radio on the official Build than I rooted it, installed the Radio, installed Dude's Cupcake and it was still the same. Now I'm back on the official Build and nothing changed. I thing about going to T-Mobile tomorrow...
Click to expand...
Click to collapse
You flashed the radio after root but it was still the old one?! Sorry I can't help, I've never heard of that before :-S
AdrianK said:
You flashed the radio after root but it was still the old one?! Sorry I can't help, I've never heard of that before :-S
Click to expand...
Click to collapse
yeah exactly and now i flashed it back to the offical RC7, RC8, RC9 and than there came the autoupdate... now I'm back on CRC1. And no problem.... thanks for trying.. I go to T-Mobile tomorrow and give it to repair...
I have been checking the massive froyo thread since it was on page 7 (now its > 120 pages) but still no love for AT&T/Rogers Nexus one.
My phone is unrooted and running stock rom with Firmware on 2.1-update1 and build EPE54B. Can people who have froyo on their at&t nexus one please post a step by step guide?
Should be the same method and file as that used for the T-mobile compatible phones.
id really like this answered too..i dont want to take a risk and brick my N1.. so far all the guides are ERE27..
The update zip as it stands is only for ERE27-FroYo... sorry.
unleashed12 said:
id really like this answered too..i dont want to take a risk and brick my N1.. so far all the guides are ERE27..
Click to expand...
Click to collapse
pjcforpres said:
The update zip as it stands is only for ERE27-FroYo... sorry.
Click to expand...
Click to collapse
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
I saw many at&t owners have froyo successfully flashed. They flashed to ERE27 first. Does that need rooting?
Thank you for this information.
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
Anyone tried this?
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
the update file is labeled signed-passion-FRF50-from-ERE27.1e519a24.zip
ATT/Rogers version is running build EPE54B. The update is from ERE27 to FRF50
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
I guess the 20 pages of 100% stock AT&T guys not being able to flash this are just morons then.
The update zip only lets you go from ERE27 to FroYo. Those with an "AT&T version" and FroYo had to flash ERE27 first... that also means unlocking the boot loader.
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
pjcforpres said:
I guess the 20 pages of 100% stock AT&T guys not being able to flash this are just morons then.
The update zip only lets you go from ERE27 to FroYo. Those with an "AT&T version" and FroYo had to flash ERE27 first... that also means unlocking the boot loader.
Click to expand...
Click to collapse
jasrups said:
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
Click to expand...
Click to collapse
That sucks.
Same problem with the european stock shipping ROM (EPF21B).
Can't wait to be able to get Froyo without unlocking.
my bootloader is unlocked..going to go ahead and try to flash pauls rooted version.
jasrups said:
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
Click to expand...
Click to collapse
What a bummer! Yeah I have waited this long to preserve my phone's virgini.. I mean warranty so I guess I'll wait longer.
At least its good to know that the build for at&t and rogers is the same!
I have the AT&T N1, and earlier today I flashed and formatted my phone back to new. I now have Froyo and it's working fine.
Kpow said:
I have the AT&T N1, and earlier today I flashed and formatted my phone back to new. I now have Froyo and it's working fine.
Click to expand...
Click to collapse
is your N1 rooted or stock?
MEGABYTEPR said:
is your N1 rooted or stock?
Click to expand...
Click to collapse
Clearly rooted and unlocked bootloader, otherwise he wouldn't have been flashing anything.
thread title misled me.
eric b
I have successfully flashed Froyo on my (AT&T) N1 with this:
http://android.modaco.com/content/g...com/309286/frf50-froyo-pre-rooted-update-zip/
I previously was on CM 5.0.6 with Amon RA Recovery v1.7.0.
I wiped and installed the update, it did flash a new radio. Rebooted and Froyo was waiting for me!
Hope this helps anyone that is not sure.
I've got a friend who's still on 1.6 who's looking to get himself rooted/Custom ROMed. Problem is, I'm not sure yet (havent' gotten a chance to talk to him) if his PRI is 1.73 or the new 2.20. I ask because the ROM I want to give him requires 2.20 for MMS.
Would flashing the official Sprint RUU (the *.5 one, the one that still has the root exploit) update his PRI?
LiquidSolstice said:
I've got a friend who's still on 1.6 who's looking to get himself rooted/Custom ROMed. Problem is, I'm not sure yet (havent' gotten a chance to talk to him) if his PRI is 1.73 or the new 2.20. I ask because the ROM I want to give him requires 2.20 for MMS.
Would flashing the official Sprint RUU (the *.5 one, the one that still has the root exploit) update his PRI?
Click to expand...
Click to collapse
i had to update to the new .6 to get the 220 pri. then i ran the .5 and rooted.
tailsthecat3 said:
i had to update to the new .6 to get the 220 pri. then i ran the .5 and rooted.
Click to expand...
Click to collapse
Alright. Good to know. Thanks!
hey guys
last 4 days before my nexus one working good on froyo..but before 2 days it show me 4 color screen and stuck there ..
so thats why i flashed with PASSIMG FRF91...now my phone get restart and hang sometimes...and there is also low stand by time problem in FRF91..
so anybody can tell me how can i downgrade to FRF85b again...
waiting for reply..also give me link of which file i wana flash on my phone..
thank you in advance...
You should use the FRG33 passimg as per Wiki, then upgrade to FRG83D.
Also, wrong section.
my hboot is 35
norfo said:
You should use the FRG33 passimg as per Wiki, then upgrade to FRG83D.
Also, wrong section.
Click to expand...
Click to collapse
ok as u said i need to use FRG33 ( FRG33 is upgraded version than FRF91 ?)
Just grab the image from here: http://developer.htc.com/
Have you tried the last update (FRG83D)?
Although if you want the FRF85D, first flash the FRF50 update (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/update-nexusone-FRF50-signed.zip) and then upgrade to FRF83 with oficial recovery (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF83-From-FRF50.zip) and finally upgrade to 85D (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF85B-From-FRF83.zip)
http://android.modaco.com/content/g...es-zip-online-kitchen-optional-root-insecure/
my nexus one is korean n1 and its on hboot 0.35
gerar_f said:
Have you tried the last update (FRG83D)?
Although if you want the FRF85D, first flash the FRF50 update (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/update-nexusone-FRF50-signed.zip) and then upgrade to FRF83 with oficial recovery (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF83-From-FRF50.zip) and finally upgrade to 85D (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF85B-From-FRF83.zip)
http://android.modaco.com/content/g...es-zip-online-kitchen-optional-root-insecure/
Click to expand...
Click to collapse
hey dude my n1 is korean n1 with hboot of 0.35 ..so downgrade to FRF85d will not cause any problem or not?
i dont wana update my N1 becasue if i update than i cant be able to root or install cynogen mod rom to my phone (if i need).
My phone was working fine before i update to FRF91 (No restart problem or hang so thast why i wana downgrade back)..
can u tell me how to flash FRF50 update to nexus one
gerar_f said:
Have you tried the last update (FRG83D)?
Although if you want the FRF85D, first flash the FRF50 update (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/update-nexusone-FRF50-signed.zip) and then upgrade to FRF83 with oficial recovery (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF83-From-FRF50.zip) and finally upgrade to 85D (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF85B-From-FRF83.zip)
http://android.modaco.com/content/g...es-zip-online-kitchen-optional-root-insecure/
Click to expand...
Click to collapse
hey dude i have download frf50 update..can u tell me how can i flash frf50 to my frf91 nexus rom...? can i flash by changing name to PASSIMG or can i change the name to Update.zip??
reply please soon
swapniladsure said:
hey dude my n1 is korean n1 with hboot of 0.35 ..so downgrade to FRF85d will not cause any problem or not?
i dont wana update my N1 becasue if i update than i cant be able to root or install cynogen mod rom to my phone (if i need).
My phone was working fine before i update to FRF91 (No restart problem or hang so thast why i wana downgrade back)..
Click to expand...
Click to collapse
Korean N1 was released with 2.2(FRF91) from the start, IIRC. So I don't know if downgrade is possible. (And, you can still root your device via rageagainstthecage exploit after upgrading it to 2.2.1(FGR83))
can i able to install custome rom after update to fgr83 as u say
LFact said:
Korean N1 was released with 2.2(FRF91) from the start, IIRC. So I don't know if downgrade is possible. (And, you can still root your device via rageagainstthecage exploit after upgrading it to 2.2.1(FGR83))
Click to expand...
Click to collapse
hey dude if i update to fgr83 and after update if my phone work well than it is ok ( not get restart) but if after update my phone again get restart while surfing or using any apps ..than it is possible to root and install custom cyanogen mod rom on my nexus one??