I bought the nexus one from a someone on craigslist and he installed the CyanogenMod 5.0.7.1 on it. It is running firmware 2.1 update 1. Now here's the problem. When I go to "Settings" then "About Phone" the first option is "Status." The "Check For Updates" option does not exist. Do you guys think this is something caused by the mod and do you think installing the stock rom, using the original shipping tutorial found on this forum, will resolve this issue. I called google and HTC and they have never heard of this problem and I also looked for anyone else having the same problem online but found nothing.
Thanks for your help.
zfa32937 said:
I bought the nexus one from a someone on craigslist and he installed the CyanogenMod 5.0.7.1 on it. It is running firmware 2.1 update 1. Now here's the problem. When I go to "Settings" then "About Phone" the first option is "Status." The "Check For Updates" option does not exist. Do you guys think this is something caused by the mod and do you think installing the stock rom, using the original shipping tutorial found on this forum, will resolve this issue. I called google and HTC and they have never heard of this problem and I also looked for anyone else having the same problem online but found nothing.
Thanks for your help.
Click to expand...
Click to collapse
Updates are not available/do not work from custom ROMs. Google and HTC will not help you with custom ROM issues. You'll have beyond the latest updates by flashing custom ROMs. Though I don't know for sure, but putting the phone back to stock should make this work correctly.
if you would like to have option for update download rom manager and there is option for stock roms download install bam there you go
CM has that option removed. If you were on a stock image then that option would be there. ALso, I think enom's roms have that option still visible.
Is the Rom manager available on market? If not could you post the link to it.
Thanks.
-------------------------------------
Sent via the XDA Tapatalk App
Im running frf83 on my rooted nexus one, i have found a few versions of frf85b and frf91, flashing them comes up successful but when i restart, settings says im still at frf83.
Ive heard that you can now unlock without affecting the bootlocker, so am i getting the wrong files? If so can anyone point me in the right direction? (im not an advanced user but im not too bad)
Please help thanks
PS i tried to post links of the files i have but wasnt allowed. they were both from htcpedia. com.
I'm also looking for a usable+deodexed FRF83-FRF91 update.zip.
This is the official download but I cant apply it because of the custom recovery, and all the files have a ".p" suffix (patch files)
http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-FRF83.4bf74f06.zip
If nobody responds I will go back to the stock recovery and try again.
I'm averaging 3 reboots/hangs a day on FRF83...
i have the same issue... i cant update from frf83 that is installed. i am getting OTA updates and nitifications but adter reboot its frf83 again, i too have a custom revovery and i dont know how to go back to stock
Any luck with solving this?
Have you tried this perhaps?
http://forum.xda-developers.com/showthread.php?t=710519
I simply backed up and did a clean kang-o-rama install
[Q]FRG83G update for [KERNEL]2.6.32.9-g6624e39 [email protected] #1 && 3G DNS issues
Hi xda community
This is my first post in this forum. I am the new user of google nexus one phone. I bought it outright in Australia and it was delivered from a warehouse in Hongkong.
I am pretty sure that phone is not rooted as I can't run rooted apps. Thats alright I don't want to root my phone.
Only thing which I am curious about is how come I have this kernel instead of the default google nexus one kernel (which gets updates from Google server straight away). Is it normal ?
I've searched through different forums and xda as well and found out that probably this kernel is tweeked by vodafone and all the nexus one from vodafone has this kernel. Is this correct ?
As you may have gathered, I have opened up this thread because I haven't received android 2.2.2 update released by google. Currently I have FRG83D and I got this update as soon as I turned my phone ON for the very first time few weeks ago.
When I tried manually updating it using the method prescribed by techs, I get signature verification failed error always. I've tried downloading file numerous times from google server and its definitely not the file. Probably its related to this kernel.
Can one of you please guide that why am I unable to get the FRG83F update ?
2nd issue is, which is a major one. On 3g, I always get browsing issues because of DNS failure. yahoo messenger remains connected, which is good. Its just browsing which fails using domain name.
I've done ping tests. Ping to IP pass, but Ping to domain fail. Only work around is that I have to restart 3g by either going into airplane mode or by selecting 2g and then unticking it, or by resetting the APN. This is really annoying cuz if my screen goes off after few minutes on idle time, DNS starts failing again and I have to keep on going through the same cycle of resetting 3g connection.
I am not using any 3rd party app to manage 3g or wifi. SMODA widget works fine to enable, disable 3g but after few minutes of idle time, DNS starts failing again.
I've tried using gscript lite, but it doesn't work on an unrooted phone. I cannot use setprop method as well cuz phone is not rooted. Is there any other method using which I can harcode the dns for 3g connection ?
WIFI works fine.
Can you please guide me a way to fix this issue ?
Kind Regards
Looks like you have one of the network supplied N1's, which have slightly different software.
Rusty! said:
Looks like you have one of the network supplied N1's, which have slightly different software.
Click to expand...
Click to collapse
Thanks for replying Rusty.
Does this mean that I will get OTA eventually ? or My only option is to flash the Rom with the Google Stock ROM ?
Should get it eventually yes, what you do depends on your level of patience
haha. Thanks Rusty I'll wait for few days and will contact u if needed any help.
lmk0 said:
This thread is growing way too fast to see if someone already figured out a possible solution, but this is for everyone getting the Status 7 errors...
I kept getting the Status 7 error too. My Nexus One was CM6.1, rooted and unlocked, etc
I followed instructions from this post by guitar east... http://forum.xda-developers.com/showpost.php?p=11618802&postcount=972
But I still ended up with Status 7...
Long story short, I did some troubleshooting and eventually figured it out. When running the update.zip from Recovery, it looks for the previous version. They all have dependencies on the previous version.
Think of it as a chain.
It had nothing to do with what ROM I had or if it was rooted. It simply needs to be done in order, i.e. FRG33 > FRG83D > FRG83G > GRI40
So download the following (sorry I don't have the links - mods feel free to udpate). Follow the instructions in the post mentioned above from guitar east. That includes the PASSIMG.zip steps, copy signed update zips to SD, rename to update.zip, reboot, recovery, etc, etc a few times BUT DO ALL OF THEM AND DO THEM IN ORDER. You'll be running Gingerbread in no time.
I used:
Passion-FRG33.zip
ecb21b752065.signed-passion-FRG83D-from-FRG83.ecb21b75.zip
2854b06b22b9.signed-passion-FRG83G-from-FRG83D.2854b06b.zip
81304b2de707.signed-passion-GRI40-from-FRG83G.81304b2d.zip
Try it out, worth a shot, and it may fix your Status 7 errors too!
And since I actually posted, might as well give everyone here at XDA all my thanks they have deserved over the years. A googol thank yous!
Click to expand...
Click to collapse
XDA - FORUM rocks. I had an unlocked Nexus one with the kernel version [KERNEL]2.6.32.9-g6624e39 [email protected] #1 and I bought it outright from HONGKONG. I didn't want to root the phone and didn't want to risk bricking my phone either. My phone had FRG83D and upgrade to FRG83G was failing with the error "signature verification failed"
I read this champion's post and used XDA-Forum Nexus wiki @ http://forum.xda-developers.com/wik...us_One/Guides_&_Tutorials#Flashing_custom_ROM and downgraded from FRG83D to FRG33 stock ROM using PASSIMG.ZIP method and then upgraded to FRG83, FRG83D, FRG83G and finally to GINGERBREAD
I could not have done it with out this forum. You guys rock. Keep up the good work.
Thanks for all your efforts guys.
neXus-sniper said:
XDA - FORUM rocks. I had an unlocked Nexus one with the kernel version [KERNEL]2.6.32.9-g6624e39 [email protected] #1 and I bought it outright from HONGKONG. I didn't want to root the phone and didn't want to risk bricking my phone either. My phone had FRG83D and upgrade to FRG83G was failing with the error "signature verification failed"
I read this champion's post and used XDA-Forum Nexus wiki @ http://forum.xda-developers.com/wik...us_One/Guides_&_Tutorials#Flashing_custom_ROM and downgraded from FRG83D to FRG33 stock ROM using PASSIMG.ZIP method and then upgraded to FRG83, FRG83D, FRG83G and finally to GINGERBREAD
I could not have done it with out this forum. You guys rock. Keep up the good work.
Thanks for all your efforts guys.
Click to expand...
Click to collapse
Thank you so much for that post
(in case it's not obvious, I had the same problem you had, and I did exactly what you did, and now I have Gingerbread on my Nexus One )
Awesome .. To be honest credit goes to the lmk0
Can I please ask what version of baseband/radio did you have when you were on the htc-kernel and what version is it running now after the gingerbread update?
I forgot to note down the previous version of baseband/radio but it was different to what I have now. Now it is :
Baseband : 32.21.00.32U_5.08.00.04
Kernel: 2.6.35.7-59423-g08607d4 [email protected] #1
Also I have SLCD verion of nexus one.
neXus-sniper said:
I forgot to note down the previous version of baseband/radio but it was different to what I have now. Now it is :
Baseband : 32.21.00.32U_5.08.00.04
Kernel: 2.6.35.7-59423-g08607d4 [email protected] #1
Also I have SLCD verion of nexus one.
Click to expand...
Click to collapse
Thanks for the quick reply. That's great as I have a SLCD one too with the same htc-kernel and am looking to upgrade it to gingerbread as well.
Just one more thing, did you use this file "766a101ae02c.signed-passion-ota-60505.766a101a.zip" to upgrade from FRG33 to FRG83 as I have read on other threads that FRG33 file actually has the newer radio (v5.08) whereas this FRG83 has the older one (v4.06) so your baseband actually gets downgraded in the process. Did you anywhere had to manually update the radio as v5.08 is the minimum requirement for gingerbread.
My current radio/baseband is "32.50.00.32U_5.12.00.08" which is what I think you would have had originally on the htc-kernel as well.
As far as I remember, mine was similar to ur one as well. Yes I used "766a101ae02c.signed-passion-ota-60505.766a101a.zip to upgrade from FRG33 to FRG 83 and then I upgraded to FRG83D and then FRG83G and then gingerbread.
Basically vodafone tweaked the radio to use on their network. I don't know why. But as soon as you will update to gingerbread radio will be : 5.08.00.04
I dont think radio matters. As I said, I didn't care about the radio and just followed the procedure. But I can't gaurantee anything as I don't know much difference in radios. When you will downgrade to FRG33, radio version will change and it will be 4.* something but it didn't halt or cause issues with upgrades.
I hope I've answered ur question. BTW U can get sotck roms from the following link:
http://shipped-roms.com/index.php?category=android&model=Passion (Nexus One)
If you'll do it, Just do it in sequence. Downgrade method is PASSIMG.ZIP one. For upgrades U'll use update.zip
neXus-sniper said:
XDA - FORUM rocks. I had an unlocked Nexus one with the kernel version [KERNEL]2.6.32.9-g6624e39 [email protected] #1 and I bought it outright from HONGKONG. I didn't want to root the phone and didn't want to risk bricking my phone either. My phone had FRG83D and upgrade to FRG83G was failing with the error "signature verification failed"
I read this champion's post and used XDA-Forum Nexus wiki @ http://forum.xda-developers.com/wik...us_One/Guides_&_Tutorials#Flashing_custom_ROM and downgraded from FRG83D to FRG33 stock ROM using PASSIMG.ZIP method and then upgraded to FRG83, FRG83D, FRG83G and finally to GINGERBREAD
I could not have done it with out this forum. You guys rock. Keep up the good work.
Thanks for all your efforts guys.
Click to expand...
Click to collapse
Hi,
I got the same problem as you! Can you please teach me how to do it step by step? I am not good at computer stuff....
Many thanks!!
konisan
Hoping to upgrade from 2.2.1 to stock 2.3.3 on SLCD Nexus One
Hey guys!
I am new to world of root to pure android and custom roms so I have bought a Nexus One (updated OTA from Vodafone AU to 2.2.1) quite recently in the last few weeks so I could play around with it, knowing that factory installed roms were available in case I screw up something. To begin with, I know that this thread is very relevant to my case and I was hoping to update the phone to stock 2.3.3 before I could go back and start installing custom roms later. Sure, I could have bought the Nexus S and just started from there but I wanted to own a phone that I could update myself (plus Nexus One looks better imo )
My N1 specs:
Nexus One PUT ship S-ON
HBOOT- 0.35.0017
MICROP - 0c15
Touch Panel - SYNT0103
Radio-5.12.00.08
Baseband version: 32.50.00.32U_5.12.00.08
Kernel version: [email protected]#1
Build number: FRG83D
I have done quite a bit of research and I thought I could just manually update it but I have read from this thread that each revision of android was dependent on the previous version. So I normally would get the same error message as most people with (E:signature verification failed. Installation aborted)
I am aware that Vodafone AU may have installed their version of 2.2.1 onto my N1 via OTA so I was also contemplating to revert from FRG83D down to stock FRG33 and work my way back up again. But reading the XDA wikis and more forum threads, I have found out that my N1 is a SLCD version and I would risk bricking the phone and end up with the red trackball of death.
So I am asking all you pros out that, what is the best method I could safely update my 2.2.1 N1 to stock 2.3.3 not custom roms? I have gone through many forum threads and they are usually specific to their AMOLED brothers and custom roms too.
Please spare some time and advice to help a newbie!
Thanks
It's pretty easy, but you're going to have to root.
Use SuperOneClick to root the phone, then install ROM Manager from the Market. Use ROM Manager to flash Clockwork recovery, and install this zip: http://www.multiupload.com/7PFE6QVIEO
You're now on stock GRI40 and so will be able to update to 2.3.4 using the stock Google update.
Thanks Rusty!
I'll give it a go! I thought no one else was going to read this thread again! I'll ask again if I stumble but thank you for responding.
Cheers!
There is an even easier way actually. Will still wipe the phone though.
Here is a link to an FRG83G passimg: http://tinyurl.com/6bym3vg
Rename it to passimg.zip, stick it on the root of your SD card and power the phone off. Hold Vol- and power on, the phone will find the file and ask to install. Say yes and shortly you will be on Google's FRG83G build, which will OTA itself to GRJ22 at some point.
Oh I thought the PASSIMG method only worked with AMOLED screen N1s.
Wouldn't I brick my phone this way if I downgraded the HBOOT on my SCLD N1?
It wont downgrade the HBOOT, FRG83G was the update that pushed the .35 HBOOT out to phones that didn't have it, and SLCD support was included in the FRG33 passimg.
Wow! That's awesome and really good news to hear!
I will definitely give a shot with that PASSIMG method now! I believe that this method would bring me to the google stock rom level of 2.2.2?
Will the stock roms available on the wiki would work from this FRG83G build > GRI40?
Okay so here's my issue. I have been trying to root and reflash my phone for hours now but every guide I find uses a different radio than I have installed. I am using 2.42.02.10.29 and my computer fails to recognize that I have an android device connected whenever I run adb or any other program. Anyone have an idea on a quick fix?
Sorry if this is a silly question but I cant find any up to date guides for my radio anywhere and the most recent posts on the Hero are about 6 months old X)
Thank you!
The radio version does not matter if you are trying to root. The software version does. There are plenty of guides here for all of the released SW versions, I recommend Regaw's as it worked fine for me, but that was a version or two back(2.31blahblah.5) I'm assuming you have already downloaded the SDK and installed that crappy HTC sync, which you can uninstall once you have the drivers installed. All that done, check to make sure that USB debugging is checked and follow the appropriate guide.
Good luck!
yes I have the sdk and I installed and uninstalled sync already, I will look through the guides again and see if I can find another for my software version then
thanks!
update: I was looking at the correct number my phone is on the the same baseband verson as the radio version. And still no root method I can find to use that Baseband. I guess I need to find a way to update the baseband so... back to the forums
Ascrius said:
update: I was looking at the correct number my phone is on the the same baseband verson as the radio version. And still no root method I can find to use that Baseband. I guess I need to find a way to update the baseband so... back to the forums
Click to expand...
Click to collapse
Umm, baseband is the radio.
Dude the radio doesn't matter in rooting. As long as you don't flash a GSM radio you will be fine. The radio you have is compatible with Aosp roms and sense roms. When you get rooted you can even change it if you like. But read extensively on that. Real "extensively" can't express that enough. But just for getting started,your radio/baseband is fine. You can find several ways of rooting in the forums. Cdma that is.
Something.About.Me.U.Dont.Like.
Its.Cool.I.Understand.AWAH
I'm just gonna add 1 more note. Your baseband is the most current version from sprint, and as others have said, will not affect your ability to root. The only thing that you cannot do with that baseband is flash the unrevoked forever s-off. But that is not the same as rooting.
Sent from my HERO200 using XDA App
I need help please. My phone is not in a good place.
Here's my current state:
AOSP 2.3.2 (Gingerbread) [02/09/2011] installed
Home Button doesn't work
Phone Button doesn't work
No Market app installed so can't download anything
Browser works
Incoming calls don't work
Outgoing calls do work
Lock screen doesn't show up
Probably many more issues with things I haven't tested
Here's how I got there:
1) Installed AOSP 2.3.2 (Gingerbread) [02/09/2011] with Firerat's Mod
2) Everything seemingly worked well. Was prompted by Market to install all of the google apps
3) The apps from Marketplace didn't install. I ended up finding the "fix the Market" link on the Wiki and that solved the problem
4) Installed the core apps but some wouldn't install - like Voice Search - failing with an Insufficient Space error I believe
5) Started revisiting the parameters for the Firerat mod (mtdpartmap.txt) and reflashing the FR-boot
6) Didn't solve problem so decided to flash/wipe/reinstall AOSP 2.3.2 again
7) Got me to the state I'm in now. I tried 3 more times, still this is happening.
Going to try now with the 20110210 build and see if that's better. I see there's a fix for the lock screen so maybe it's related. Meanwhile, has anyone seen these symptoms before?
Thanks!
marc2112 said:
Going to try now with the 20110210 build and see if that's better. I see there's a fix for the lock screen so maybe it's related. Meanwhile, has anyone seen these symptoms before?
Click to expand...
Click to collapse
Sorry to hear about that, but I would recommend you to follow the steps from here: http://romrepo.info/wiki/index.php?title=Install_from_another_ROM. Try doing it without Firerat's MOD. Perform step # 2 - 2 to 3 times, before you flash the ROM.
Try and report back. Hope it helps.
SOLVED
2/10/2011 update solves this problem!
When you flash a different Ron, you need to go through the whole from process starting with fr- recovery after wiping/formatting everything. I have had troubles with 2/10. Maybe bad download. I get a weird keyboard error and it wants to send Google a report and can't get by that to start signing in.
I flashed on top of 2/6 yesterday, but still had VVM problems. I finally got that sorted out with 2nd method in GB wiki and started new TB folder.
Sent from my HTC Hero CDMA using XDA App