Database Users

ONLY - Technical Support - ONLY

Disclaimer: As in every case your choice to flash any memory on your phone is YOUR decision and you run the risk of making a expensive Paperweight. Research Flashing and read post about new Rom's or Builds to learn from others mistakes.. There are a lot of risk takers here on XDA that will be glad to bite the bullet to help the community with rom stability and issues. But ultimately you CHOOSE to flash your phone Not us.
I created this thread for new users unfamiliar with Flashing and modding their phone to get technical Support for any technical Issue that comes up regarding the phone. However Please Avoid Posting things such as "I am bricked how do I fix" or "Help my phone doesn't Start up" Because they will not allow the more experienced users to Help you.
Suggestions:
1. List the following in the reply
- What Model Is your Phone (Should Be HTC Dream AKA Tmobile G1)
- What SPL are you using (Boot Holding Power + Camera then first line)
- What Recovery Image are you using(Stock, Jesus Freakes 1.42, 1.43 or HK)
- What Rom is Currently Loaded (Booted up go to Settings-> About Phone)
- What Radio do you have currently (Settings -> About Phone)
2. What are you Trying to do (Ultimate Goal)
3. What steps has you taken (In Detail please)
4. Once you problem has been resolved please Edit your Original Post indicating that it was resolved.
Thanks In advance for Keeping this thread Neat.
Some Reading Material for you:
APN Info Thread
General Questions Thread
G1 Wiki Thread
G1 Tips and Tricks Thread

jf recovery 1.43
doesnt seem like i need it because ive flashed beta 3 using 1.42 but i want it cause it has to have some capability that 1.42 doesnt right? Only problem is I have no idea how to flash it. I tried renaming the 1 in "haykuros hero rom" post to update.zip and it still said 1.42 when i went back 2 recovery. I dont use fastboot or adb or anything because I am a capital "N" noob and nothing seems to ever say how to do any of this stuff using a mac so.... that being said...can you help?
1. tmobile g1
2. haykuros latest spl
3. 1.42
4. ion
5. latest radio
goal: 1.43 recovery
steps taken: saw a lot of people ask the same question. searched. went back to the rooting thread attempted to enter the commands by pressing alt+x in the recovery console the way they were listed and placed the recovery.img file i unzipped from the hero thread on my sdcard. no luck.

build..?
I did my first fastboot recovery, even though I didn't need to. Pretty decent operation. Just wanted to get the feel of it. I think I'll be using nandroid and fastboot a whole lot in the near future
Goal: To either build myself, or at least play a part in the building of one sweetest ROM's. I guess i'll start small, with a theme.
(it's been a 12 pack of Mountain Dew and B movies kinda night.)

CC CEO said:
doesnt seem like i need it because ive flashed beta 3 using 1.42 but i want it cause it has to have some capability that 1.42 doesnt right? Only problem is I have no idea how to flash it. I tried renaming the 1 in "haykuros hero rom" post to update.zip and it still said 1.42 when i went back 2 recovery. I dont use fastboot or adb or anything because I am a capital "N" noob and nothing seems to ever say how to do any of this stuff using a mac so.... that being said...can you help?
1. tmobile g1
2. haykuros latest spl
3. 1.42
4. ion
5. latest radio
goal: 1.43 recovery
steps taken: saw a lot of people ask the same question. searched. went back to the rooting thread attempted to enter the commands by pressing alt+x in the recovery console the way they were listed and placed the recovery.img file i unzipped from the hero thread on my sdcard. no luck.
Click to expand...
Click to collapse
Installing JF Recovery 1.43 is just like any flash update for a rom...
You find and download the recovery file. Rename it to update.zip (Keep in mind that windows by default hides the.zip part so if you rename it to update.zip windows actually sees it as update.zip.zip.. This is a common problem.
Then Boot to SPL by powering off your phone and powering up with Home + Power Key.
Once loaded then hit Alt + L (If you don't have a modded Recovery already) and then If you have to wipe(which I usually do) Alt-W then you need to load the new firmware with Alt + S.
If all goes well it will load the new recover image and will reboot back into Recovery mode in which you just Home + Back to Exit and reboot.

I don't wanna step on anyones toes but I believe to load the new image after wipe it'll be alt + s....

Hero beta's
I've triend to install both Beta 2 & Beta 3 of the Hero build, but evertime it got to the setup screen it would force close. What can I do to get past this problem?

mvanwyk83 said:
I've triend to install both Beta 2 & Beta 3 of the Hero build, but evertime it got to the setup screen it would force close. What can I do to get past this problem?
Click to expand...
Click to collapse
With the beta 3 update update on your sdcard boot into recovery and wipe then flash then wipe again then reboot.
If you have a2sd already Use the adb recount Command and then adb shell to delete the system/sd/ folder.

Just a quick question:
I'm currently running
the Android 1.5r2 based Cyanogen build v3.3.1
1.43 recovery img
Hardspl
The latest radio update (the one with the I as the last character)
I would like to update to Haykuro's new bootloader to get more space and to be ready for the upcoming haykuro build, but I'm a bit scared by all the reports of phones getting bricked.
So my question is, if I install it using the update.zip on sd-card method, is there any chance of a brick?
Let me point out that I don't have a microsd card reader available, so I wont be able to flash the build I'm currently using right after updating the SPL. So far it's not entirely clear to me whether this can be a problem.
tia

Curunir said:
Just a quick question:
I'm currently running
the Android 1.5r2 based Cyanogen build v3.3.1
1.43 recovery img
Hardspl
The latest radio update (the one with the I as the last character)
I would like to update to Haykuro's new bootloader to get more space and to be ready for the upcoming haykuro build, but I'm a bit scared by all the reports of phones getting bricked.
So my question is, if I install it using the update.zip on sd-card method, is there any chance of a brick?
Let me point out that I don't have a microsd card reader available, so I wont be able to flash the build I'm currently using right after updating the SPL. So far it's not entirely clear to me whether this can be a problem. Tia
Click to expand...
Click to collapse
Before you consider flashing the new spl. Make sure you have a pvt revision board. Power + camera when turning on your phone. It will be at the top. If it says dvt don't flash.
You also need the 26I radio firmware.
If you do not have a memory card reader or a second memory card ten do not flash the new spl. Once you flash the spl, your phone will not boot until you flash a new Rom onto it
I believe this is correct. Anyone with experience care to confirm?

Actually now that I am rested and thinking straight.. Don't you load a recovery image by loading the recovery.img file on your sd card and booting to Bootloader?
Man I was sick and tired last night =)
Go to My Hero Thread and in the first post is the JF 1.43 Zip file you can use to Flash to JF 1.43 in update.zip format.

ubernicholi said:
With the beta 3 update update on your sdcard boot into recovery and wipe then flash then wipe again then reboot.
If you have a2sd already Use the adb recount Command and then adb shell to delete the system/sd/ folder.
Click to expand...
Click to collapse
Now is that process the same for Beta 4??

,
mvanwyk83 said:
Now is that process the same for Beta 4??
Click to expand...
Click to collapse
Should be. Can anyone confirm?

I put some music on beta 4. The album cover is in my pics but doesnt show where it should when playing music, do i need to somehow manually put it there?
Am I asking this in the right place even? thanks

1.
Tmobile G1
SPL: DREA100 PVT 32B
Firmware version: 1.5
Baseband Version: 62.50S.20.17H_2.22.19.26I
Kernel Version: 2.627-00392-g8312baf [email protected]
Build Number: dream_devphone-userdebug 1.5 CRB21147201 test-keys
2. Upgrade to the Dudes Build (http://forum.xda-developers.com/showthread.php?t=507151) and backing up all my data and apps
3. Tried to update (by naming his build update.zip and updating) and also tried backing up data using the commands in his post (listed above)

cronin4392 said:
1.
Tmobile G1
SPL: DREA100 PVT 32B
Firmware version: 1.5
Baseband Version: 62.50S.20.17H_2.22.19.26I
Kernel Version: 2.627-00392-g8312baf [email protected]
Build Number: dream_devphone-userdebug 1.5 CRB21147201 test-keys
2. Upgrade to the Dudes Build (http://forum.xda-developers.com/showthread.php?t=507151) and backing up all my data and apps
3. Tried to update (by naming his build update.zip and updating) and also tried backing up data using the commands in his post (listed above)
Click to expand...
Click to collapse
What errors did you get or what problems are you having?

stuck on android screen
hey guys, this morning i got the OTA cupcake update, and my phones been running fine all day, however, i just restarted it and its stuck on the android logo screen, it shows the shine going through the logo like it is loading but after a few seconds it stops, then does it again, is my phone shot? please, any help will be greatly appreciated

rschuman90 said:
hey guys, this morning i got the OTA cupcake update, and my phones been running fine all day, however, i just restarted it and its stuck on the android logo screen, it shows the shine going through the logo like it is loading but after a few seconds it stops, then does it again, is my phone shot? please, any help will be greatly appreciated
Click to expand...
Click to collapse
Wipe your phone. Press and hold home+power. Continue to hold it till youe see a caution triangle. Press alt+l and then alt+w when its done select reboot from the top of the list. Good luck

Quick Question
I am running the newest of everything, currently on Hero BUild 4
What actions should be taken to downgrade to the older SPL. I am getting extremely bad battery with this and can't handle it.

Mast3rmatt said:
Quick Question
I am running the newest of everything, currently on Hero BUild 4
What actions should be taken to downgrade to the older SPL. I am getting extremely bad battery with this and can't handle it.
Click to expand...
Click to collapse
From what I know, its a bad idea to downgrade your spl. Check you screen brightness and your screen time out if you are running an overclock program, try setting it to 384 max 128 min. Double check to make sure your screen actually times out. See if your wifi is running, as well as your gps. If you use twidroid change the rate from 5 minutes to 1 hour

i have to wipe my entire phone and loose everything now!!?

I'm incompetent. Is there anything I'm missing?

When I first became active, I rooted my phone, I made a recovery off the original recovery rom. I updated to the what my phone says is the unofficial modaco rom v1.3 + an update
+ a theme.... bu then me and my girl split and my recovery images were on a flash device she had. I see some stuff about an updated version of recovery... talk of radio's amongst other things.
I'm assuming I just most likely need to flash back to an original root and then possibly the instructions I need to get the new recovery image as well as the 2.0 stuff on my phone. <--- is this basically what I need to do???

Cloned2 said:
When I first became active, I rooted my phone, I made a recovery off the original recovery rom. I updated to the what my phone says is the unofficial modaco rom v1.3 + an update
+ a theme.... bu then me and my girl split and my recovery images were on a flash device she had. I see some stuff about an updated version of recovery... talk of radio's amongst other things.
I'm assuming I just most likely need to flash back to an original root and then possibly the instructions I need to get the new recovery image as well as the 2.0 stuff on my phone. <--- is this basically what I need to do???
Click to expand...
Click to collapse
Flash a new recovery....fisrt things first
Then do factory data wipe from recovery.
You should probably reformat your SD card...
Wipe Dalvik....
then flash any of the good ole' zips that are up now..
Personally before I do any more flashing I am waiting on sprint release OR this new "Toasts Awesome Sauce" I see in another thread...if it blows everyone else away speed wise....I hope they got OC working.
Only reason I am waiting for an official sprint is because I am sick of wiping my phone ~ to lazy to back up ~.

Cloned2 said:
I'm assuming I just most likely need to flash back to an original root and then possibly the instructions I need to get the new recovery image as well as the 2.0 stuff on my phone. <--- is this basically what I need to do???
Click to expand...
Click to collapse
You don't have to install the new recovery to flash the 2.x ROM's. However, the new RA 1.6.2 was updated and had some bugs fixed, with also a little more added features, so it's probably worth your time to download and flash.
To flash a 2.x ROM, just do as you did before, find one you think you might like, download it and then copy it to your SD Card, after that its a matter of Nadroid back up and then flashing the new ROM.

thanks for the heads up guys.
I just couldn't be sure if there were things that needed to be changed outside of just flashing the new roms.
Back when i was more active I recall there being some roms that you couldn't flash from but a factory reset will revert me out of my modoca flash so that, that problem doesn't potentially crop up?

eris 2.1 to 1.5 downgrade

my girlfriend hates the OTA 2.1 cause there is so much not working now
so i was wondering if there is way/tutorial to downgrade from the crappy 2.1 OTA back to original 1.5 without rooting
if not what is there a tutorial for rooting then downgrading
Edit:
since i have a moto droid and my girlfriend didnt care much about rooting till now what type of things are diffrent when rooting the eris compared to droid (OCing, roms, themes, nandroid backups, ect.)??

Check out this link to root the eris: http://forum.xda-developers.com/showthread.php?t=647707
I'll post again once I find the 1.5 rom, although I think it may have been removed.

After searching it appears that jcase took the download down at the request of a few users.
So, what I would do is root then flash some of the new roms that have come out. Personally, I'd give either CyanogenEris or Senseless a try because they are AOSP based (like your droid is).
If you are into the Sense scene, I would check out the plethora of roms listed here: http://forum.xda-developers.com/showthread.php?t=649705

so your not able to just downgrade?? cause thats all my girlfriend really wants
and are the 2.1 roms(with sense ui cause for some reason my girlfriend likes it) based off the leaks or the official 2.1 and do they run better then the official 2.1
Edit: that tutorial is for stock 1.5 not 2.1

Downgrade instructions are here http://androidforums.com/all-things...ot-thread-apps-roms-updated-05-06-2010-a.html
Full Downgrade from 2.1root (any) to 1.5 stock - FULLY WORKING
THIS IS NOT FOR LEAK USERS SO DON'T ASK
If it bricks your phone, not my fault (it shouldn't and I hope it doesn't).
Please read and follow the directions included.
unzipme.zip md5sum: 0ed3c91d7574367d65428b3bc230f217
http://www.multiupload.com/6UE7AUN810
This is fully working, I just did a full reflash to 1.5, including the kernel, the system software, the radio firmware, recovery image and the bootloader.
This must be done from a PC with Fastboot, which comes with windows. Linux/Mac users will have to find it and compile it. You will need to have Amon's recovery image installed to use this downgrade, at the end we will overwrite his image with the stock one.
Inside unzipme.zip are three files
downgrade.zip md5sum: c440c87f1e67f4b62e05da0d255e80e9
-Do not unzip/open/alter this file
--Contains your kernel, radio firmware, and system.
recovery.img md5sum: 71a4b633bdb32de9dcdd8953fef43cdc
--stock recovery image
hboot.nb0 md5sum: 38899da4e5e002e3be22900f5f4eb6f7
--Original bootloader
Step one:
Put hboot.nb0 and recovery.img in the tools dir of your sdk.
Put downgrade.zip on the sdcard of your phone
Step two:
Turn your phone off, then turn it back on holding the power button (red) and send button (green). Once in the boot loader press volume down, then volume up to get to Amon's recovery image. Go to wipe, wipe dalvik cache, and do a factory reset (aka wipe data). Then choose flash zip from sdcard, and flash downgrade.zip. The phone will flash the kernel, and system softare, then ask you to reboot. Let it reboot so it can flash the radio, it will restart back in the recovery image. You can power down your phone now.
At this point if your just wanted 1.5 back, you are done.
If you want the original bootloader and recovery image, (ie 100% stock) continue on.
Step three:
Plug your phone into your PC. Power your phone on using the power button (red) and send button (green). Your phone should now be sitting back at the bootloader screen and say FASTBOOT USB. Now on your PC, go to the sdk tools dir in command line. Issue this commanhttp://www.multiupload.com/6UE7AUN810d
Code:
fastboot flash recovery recovery.img
Let it flash, when done wait a minute (just to make sure).
Then issue this command
Code:
fastboot flash hboot hboot.nb0
Once this is done, wait a minute then pull your battery and restart your phone.
You are now back at factory stock.
Click to expand...
Click to collapse
Personally I'd stop after step 2 in case you ever want to flash a rom in the future.
Woops, I missed that she's not rooted. You could root it and go back down to 1.5.

tiggerxplur said:
so your not able to just downgrade?? cause thats all my girlfriend really wants
Click to expand...
Click to collapse
In theory you could downgrade using the same methods as going from RUU 1.17-1.16 (since they have the same bootloader version and are both signed), but I don't know that anyone on 2.1 OTA has tried that.
Even if you got it to downgrade she'd be bugged constantly about the OTA (every 2 minutes I believe), which would suck for her. Also it takes up ~100MB of space on her phone too, so I would just go with rooting.
tiggerxplur said:
Edit: that tutorial is for stock 1.5 not 2.1
Click to expand...
Click to collapse
The root process is exactly the same for 2.1 OTA users, but will not work if it's a 2.1 leak.
At this point all the roms are based on 2.1 OTA or another person's 2.1 rom and most of them run better than the 2.1 OTA.
It's really just a trial-and-error process. Some users will swear by one rom and hate another, while others will swear by a different rom.
I'd have her look at all of the roms and pick one based on looks, because it sounds like she won't use most of the advanced features anyways.

nindoja said:
In theory you could downgrade using the same methods as going from RUU 1.17-1.16 (since they have the same bootloader version and are both signed), but I don't know that anyone on 2.1 OTA has tried that.
Even if you got it to downgrade she'd be bugged constantly about the OTA (every 2 minutes I believe), which would suck for her. Also it takes up ~100MB of space on her phone too, so I would just go with rooting.
The root process is exactly the same for 2.1 OTA users, but will not work if it's a 2.1 leak.
At this point all the roms are based on 2.1 OTA or another person's 2.1 rom and most of them run better than the 2.1 OTA.
It's really just a trial-and-error process. Some users will swear by one rom and hate another, while others will swear by a different rom.
I'd have her look at all of the roms and pick one based on looks, because it sounds like she won't use most of the advanced features anyways.
Click to expand...
Click to collapse
yea she doesnt care for the advanced things i have tried to get her to use another home replacement app like helix cause i know sense ui is a resource hog but she likes it too much and doesnt wanna try and get used to something new but i will talk her into rooting and choosing a rom she might like thanks for the help
i had a rom before 2.1 for the droid that didnt block the ota and it was very annoying it varied between 2 minutes to ten minutes

is there an app like rom manager to switch between roms like the droid

I went from 2.1 OTA back down to 1.5 using the RUU MR2 on the computer. Worked like a charm!

downgrade leak 2.1 to 1.5 stock
Is there anyway to downgrade this horrible 2.1 leak back to the stock 1.5 version.

damon428 said:
Is there anyway to downgrade this horrible 2.1 leak back to the stock 1.5 version.
Click to expand...
Click to collapse
No...... x10

Please Delete. Duplicate.

If its been said once, it's been said a thousand times here,
"can I root the 2.1 LEAK?"
As always the answer is HELL NO!!!!
"can I root 2.1 OTA?"
Yes.
"can I downgrade 2.1 OTA to 1.5"
Yes.

help! i'm stuck! (with generic 2.1)

Hi, i have a problem, I need some help solving it.
I have branded Hero (G2 Touch) on T-Mobile. Being tired of waiting for T-Mobile to release their branded 2.1, I followed some instruction on this board and installed generic 2.1. Sadly, the instruction used the RUU for directly installing 2.1 and I did this^^
When I try to install an old 1.5 RUU (t-mobile or generic) I always get the error 140 bootloader version.
I then tried the rooting method, now I managed to install the Amon Ra's Hero Recovery and that works quite good, as I now can use nandroid again (I couldn't do since the 2.73 update).
I managed to restore some backups that were on 1.76, and I had android 1.5 installed again, but still I couldn't install the 2.73 RUU, still getting the bootloader error.
Now, either somebody can tell me how to install the RUU, so I can get back to original t-mobile ROMs and can use OTA to get from 2.73 to android 2.1,
or, somebody could send me a nandroid backup with 2.73 installed.
there might be another possibility: I extracted the rom.zip from the T-mobile 2.73 RUU and tried installing it via recovery... I got an error while opening the file (bad).
has anybody an idea how to solve my problem? pls don't tell me 'install custom roms' i heard that often enough and simply don't want to (though I might give it a try as soon as working sense 2.2 ROMs are ready)... i want to get back to official T-Mobile ROMs
thanks

JW 301 said:
Hi, i have a problem, I need some help solving it.
I have branded Hero (G2 Touch) on T-Mobile. Being tired of waiting for T-Mobile to release their branded 2.1, I followed some instruction on this board and installed generic 2.1. Sadly, the instruction used the RUU for directly installing 2.1 and I did this^^
When I try to install an old 1.5 RUU (t-mobile or generic) I always get the error 140 bootloader version.
I then tried the rooting method, now I managed to install the Amon Ra's Hero Recovery and that works quite good, as I now can use nandroid again (I couldn't do since the 2.73 update).
I managed to restore some backups that were on 1.76, and I had android 1.5 installed again, but still I couldn't install the 2.73 RUU, still getting the bootloader error.
Now, either somebody can tell me how to install the RUU, so I can get back to original t-mobile ROMs and can use OTA to get from 2.73 to android 2.1,
or, somebody could send me a nandroid backup with 2.73 installed.
there might be another possibility: I extracted the rom.zip from the T-mobile 2.73 RUU and tried installing it via recovery... I got an error while opening the file (bad).
has anybody an idea how to solve my problem? pls don't tell me 'install custom roms' i heard that often enough and simply don't want to (though I might give it a try as soon as working sense 2.2 ROMs are ready)... i want to get back to official T-Mobile ROMs
thanks
Click to expand...
Click to collapse
You'll need to use this guide (http://villainrom.co.uk/viewtopic.php?f=46&t=375) to make a goldcard, and downgrade using the HEROIMG.zip method (google it)

it doesn't work... I took the rom.zip, renamed it HEROIMG.zip and put it on my sdcard.
hboot finds it, loads it and then says "Main Version is older! Update Fail! Do you want to reboot device?"
what can I do now?

Have you checked to see if your goldcard has definitely worked?

it definitively is a goldcard, as I used it to install generic ROM on T-Mob device... still doesn't work now... but the problem is not that I try to install a ROM that's not meant for my device (thats what I understood goldcard does), but the problem seems to bee the bootloader-version the 2.1 RUU brought.
what can I do now?

Same thing happened t me a while back, I just re-tried every step from scratch and it worked the third time...!

what exactly did you do then? I tried so many things, at least I want to know, which steps to repeat over and over again

Just going to have a look at it for you, I am going through the processes as we speak so if I find a solution I will post back.
@JW 301 post the info in settings > About Phone
- Model number
- Firmware version
- Baseband version
- Kernel version
- Build numbr
- Software version

- Model number: HTC Hero
- Firmware version: 2.1-update1
- Baseband version 63.18.55.06PU_6.35.15.11
- Kernel version: 2.6.29-063c4d24 [email protected] #1
- Build number: 3.32.405.1 CL191507 release-keys
- Software version: 3.32.405.1
I want to get back to 2.73.111.26 (that is a T-Mobile ROM) so I can apply official T-Mobile OTA updates (by the way, I managed to get to VillainROM 12.0 yesterday, but went back. I want to use official ROMs...)

See new post here;
http://forum.xda-developers.com/showthread.php?p=7600524#post7600524

Had the same problem, I mean, EXACTLY the same.
This is what sorted it for me:
http://forum.xda-developers.com/showthread.php?t=726118

God, I just KNEW I shouldn't have even tried to root... Please help =(

I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help

ap3604 said:
I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
Click to expand...
Click to collapse
Does the phone still function? Making calls, sending texts.. etc?
If so, then whats the problem? The radio update was probably included in the ROM you flashed, if you're experiencing problems, search the forum for the Radio you want and instructions on how to flash
Be careful though, you can brick your phone when flashing a radio.. so make sure you read the instructions..
Good Luck

S_Dot said:
Does the phone still function? Making calls, sending texts.. etc?
If so, then whats the problem?
Click to expand...
Click to collapse
2 things I am worried about:
1. Before I rooted and changed the radio, I could check for system updates and it would say I could to update to 2.2.1 ota... Now, after I unrooted and got it back to stock 2.2, I would check system updates and it no longer gave me the option to update to 2.2.1 (I had to manually do this)
This worries me since I don't want to miss out on all future ota updates if my radio has been screwed up when I flashed one earlier.
2. Radio has been slower since upgrading manually to 2.2.1 but still having the old radio in place.
Isn't the each radio optomized for the particular android build?
Also what about rooting causes the phone not to get the new ota update? Is it the changing of its radio?

What country is yor phone? And with what build did it came after warranty?
My guess the radio is just part of the update (if you flashed a stock rom)
I recently bought my nexus in holland it came with FRF91
And 5.08.00.04 radio so

Radio isn't per build.
There was a major change to adjust to Froyo in 4.06 radio, all the above are compatible with it, all the 4.04 and below are compatible with Eclair and not suitable for Froyo.
2.2.1 includes 5.08 anyway. Your not getting OTA doesn't have anything to do with radio.
You can flash any radio you want when you're rooted, using the guide found in Wiki.

Yeah I've benefited from newer radios. Dont sweat it your rooted, this is good.
Sent from my Nexus One using XDA App

ap3604 said:
Also what about rooting causes the phone not to get the new ota update? Is it the changing of its radio?
Click to expand...
Click to collapse
It's the rom and recovery.
I really would not get stressed out about this. Worst case scenario is that you have to come on xda every so often and flash the update manually.

LOL, if ur on CM6 u already have 2.2.1 and worrying about future otas, root user update to latest version normally before unrooted people and u should have to problem updating, if u want to revert back to the old boring stock version just flash one of the shipping roms in bootloader by renaming them to PASSIMG.zip

ap3604 said:
I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
Click to expand...
Click to collapse
1) From where did you upgrade to 2.2.1?
if you upgraded from rom manager or any ROM given by developer, they remove the radio and provide it as a separate update file.
http://www.tap3w0rm.com/hosted/android/radios/nexus-1/FRF50-radio-4_06_00_12_7.zip is the update for radio you want.
2) However, Radio update is not what you want. "Recovery" is what you want. Recovery is a piece of software that allows you to flash custom ROMS. did you install Amon's recovery or Clockwork (from ROM Manager) recovery?
You will not get OTA if you have one of these custom recoveries. you will need the stock recovery.
3) In short, you need to flash your phone with a completely stock google ROM.
follow these instructions
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus

hmmm interesting...what makes you wanna unroot besides OTA? From what I see that's virtually no advantage to go back to stock rom
If you really want official OTAs, just make sure you check xda often when those are pushing out. There will be stock OTA updates hanging around.

Try this:
http://djmcnz.batteryboss.org/Kang-o-rama/froyo/radio/froyo-radio-update-signed.zip
Flash it from custom recovery. It will reboot, unpack the radio, reboot again in a few minutes, and you should end up back on the 4.06 radio. For what it's worth.
If you want to go back to totally stock unrooted, the most complete way to do so is using a PASSIMG file.

arkavat said:
However, Radio update is not what you want. "Recovery" is what you want. Recovery is a piece of software that allows you to flash custom ROMS. did you install Amon's recovery or Clockwork (from ROM Manager) recovery?
You will not get OTA if you have one of these custom recoveries. you will need the stock recovery.
Click to expand...
Click to collapse
I installed Clockwork recovery when I first did the Cyanogen flash so how do I know if I still have it on my phone blocking OTA updates?
I had an old 2.2.1 update.zip on my SDcard from an old Nexus One that I sent in through a warranty swap.
Then I powered off and did the whole Volume Down + Power button.
I get the screen with the 3 androids on skateboards and clicked on Recovery
I press on recovery
When I see the triangle with exclamation mark I press power button + volume up and the only options I see are reboot system now, install update.zip from sd card, factory reset, wipe cache
I click on install update.zip (2.2.1) and reboot system now so the phone reboots but I still am stuck with the old radio. How do I know if I have stock recovery and will get OTA updates from now on?
arkavat said:
In short, you need to flash your phone with a completely stock google ROM.
follow these instructions
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Click to expand...
Click to collapse
I tried the steps exactly (PASSIMG.ZIP on sd card) but when I do the power + volume down step 7 doesnt happen. There isn't any screen looking for update files. I get the screen with the 3 skateboarding androids instead and no way to get the PASSIMG.ZIP file to work.

Can't you download a unrooted 2.2 rom from rom manager and then ota once its installed? Dont quote me though I've never actually tried to unroot
Sent from my Nexus One using XDA App

ap3604 said:
I tried the steps exactly (PASSIMG.ZIP on sd card) but when I do the power + volume down step 7 doesnt happen. There isn't any screen looking for update files. I get the screen with the 3 skateboarding androids instead and no way to get the PASSIMG.ZIP file to work.
Click to expand...
Click to collapse
On my phone this is what I get in bootloader mode...
I start up the phone holding down the trackball, and I get the Fastboot with the skateboards. The first menu option, BOOTLOADER, is highlighted. I press Power and I get to the HBOOT screen (also with skateboarding androids). I wait 5-10 seconds and it checks for a PASSIMG on SD. Since I don't have one, it finds nothing and returns me to HBOOT.
Or alternately I boot while holding volume down and I get HBOOT directly. In 5-10 seconds it checks for PASSIMG. The only time it won't do that is if my SD is not installed.
You're saying that on yours it doesn't check for PASSIMG at all?

I am in a somewhat similar boat (though not exactly), a colleague of mine purchased a used Nexus One off of fleebay and it came rooted running Cyanogen 6 with Clockwork Recovery (for the Recovery Image).
My colleague wants it to be completely stock (which I do not understand as I find Cyanogen 6 to be far better) and asked me the resident Android guy if I could help.
I figured PASSIMG.zip was the way to go and downloaded the stock rom from developer.htc.com and renamed it PASSIMG.zip. I put the PASSIMG.zip file on his SD card and booted into the bootloader. It checks the PASSIMG.zip image but does not offer me option to install it. It simply checks it and then offers me the normal 4 options.
Any thoughts?
Dan

Read the Wiki, it has specific reference to FRG83 stock ROM now, which refuses to work in PASSIMG mode.

dan1431 said:
I am in a somewhat similar boat (though not exactly), a colleague of mine purchased a used Nexus One off of fleebay and it came rooted running Cyanogen 6 with Clockwork Recovery (for the Recovery Image).
My colleague wants it to be completely stock (which I do not understand as I find Cyanogen 6 to be far better) and asked me the resident Android guy if I could help.
I figured PASSIMG.zip was the way to go and downloaded the stock rom from developer.htc.com and renamed it PASSIMG.zip. I put the PASSIMG.zip file on his SD card and booted into the bootloader. It checks the PASSIMG.zip image but does not offer me option to install it. It simply checks it and then offers me the normal 4 options.
Any thoughts?
Dan
Click to expand...
Click to collapse
Try as update.zip through custom recovery? Then clear the custom recovery by flashing stock one...then delete superuser.apk + unroot?

liam.lah said:
It's the rom and recovery.
[snip]
Click to expand...
Click to collapse
Actually, it's just the ROM. Even if you have a custom recovery: a rooted, stock ROM will still receive OTA updates...

Yes but on quite a few custom recoveries, it will fail to install due to the signature.

Rusty! said:
Yes but on quite a few custom recoveries, it will fail to install due to the signature.
Click to expand...
Click to collapse
True. If you are using anything earlier than Amon_RA 1.8 or the latest ClockworkMod, it won't install.