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
Related
My phone is running build FRF33B (googling this build number returned no results at all). It was a non public build. I got the phone from Adobe as part of a (kongregate) promotion to get flash developers to edit some games so they could run on froyo, and hence I really don't know what was done to the phone before I got it (there's an unlocked symbol when it boots, and even though it's a t-mobile nexus I'm using it on AT&T's network).
FRF33B is nice and usable (but full of minor bugs which get irritating after a while), and I'd really like to update to the latest stable build, but it's not receiving any of the OTA updates, and trying to install any manually gives me a package signing verification failure.
Does anyone here know how I can update the phone? Do I need to downgrade it somehow? Do I need to root it? Any help would be appreciated.
Downgrade to erd79 would be my best suggestion and it will update to frf91 I hope that helps and if u need a update zip let me know and I can email it to u
Sent from my Nexus One using XDA App
Or just unlock your phone, put a custom recovery, and install whatever ROM you want. Look at the sticky in the development section for details.
Option 3: Search around for the FRF91 Universal update.zip, copy it to your SD card, and flash it via stock recovery.
rohandhruva said:
Or just unlock your phone, put a custom recovery, and install whatever ROM you want. Look at the sticky in the development section for details.
Click to expand...
Click to collapse
ok I've done this, and flashed the universal FRF91, now the phone is stuck on the animated X, is this normal? Do I just have to wait or did I do something wrong?
edit: it looks like it just rebooted itself.... still not getting past the animated x part though
edit: wiped the phone and tried again, now it works... got to set up everything on the phone again though and download my apps again... oh well. thanks for the help
I was trying a new ROM today, but decided to switch back to my backed up ROM that I did just before I flashed it with the new ROM. Since then, not all of my apps are showing up in the "Download" section of the market. If I search for an app that is installed, it will show it as being installed, but will not show up in the download section. I've tried running it as AT&T and with Market Enabler faking T-Mobile.
Has anyone else experienced this? If so, what do I do?
Thanks in advance!
Some of my purcheased apps are not showing after installing the new firmware and I can't find them on the market.
MarketAccess faking T-Mobile didn't help... thank God for nandroid
I am having the same issue. Can't even find Asphault HD that I paid for. I just don't want to do a nandroid right now. Im sure something will work out.
I just updated my device to the last version 2.3.3 gingerbread.
Everything was working good until I tried to make a call.
I have full service signal, but the problem is that I cannot hear anything and from the other side cannot hear me too.
however, is not a hardware problem, because I can make calls using Skype or any other similar app without problems.
my device is in S-Off and I used ClockworkMod Recovery (downloaded from another thread here) to Install the Rom.
first, I downloaded the Rom from a chinese website and then I tried with another one (non chinese)
but...both with the same problem, So I guess is not a ROM problem.
I'm trying to update from a 2.2.1 version also downloaded from a chinese website (I bought my cellphone in China).
I have tried with some RUUs from this forum, but I'm also having the problem 170 & 171 usb conexion.
I tried to explain everything full detailed. Hope someone could help me!
(I was looking for answers in other threads but with no success)
Thanks.
Hi there,
I had the same problem as you only a few weeks ago after installing a custom rom as well going from froyo to gingerbread.
The problem lies with the radio. You will need to upgrade your radio version. In doing so you will get sound from voice calls back.
Here is the thread I followed that will show you how. At the bottom of the first post you will have the list of radio versions as well as with which RUU it should go with.
http://forum.xda-developers.com/showthread.php?t=1129014
Hope it works for you, good luck!
System92
Thanks for your quick response!, I will check right now!.
Tell you later!
---------- Post added at 09:20 PM ---------- Previous post was at 09:08 PM ----------
can you tell me which Rom and Radio you used please?. and Did you use some .exe Ruu?.
Thanks!
I am using CyanogenMod Nightly builds, which are based on Android 2.3.5 now. My radio is 20.2810.30.085AU_3805.06.03.16 (last hyperlink from the list) and everything runs well.
No I didn't use a .exe RUU
I need to bother you again!. is this version size just 78Mb?. (http://forum.xda-developers.com/showthread.php?t=1015532)
others Rom I downloaded was all above 200 Mb.
If it's like the ones on the official site, it is probably zipped (explaining the smaller size, +/- 80mb).
http://download.cyanogenmod.com/?type=nightly&device=vivo
Thank you very much System92, I just Installed the same Rom and Radio as you did and It worked perfectly!. (by the way, It's a great Rom with a fantasctic interface!)
Thanks Again!
Your welcome Bastian_n, I'm glad you got everything working!
CM7 is basically what stock Android looks like without Sense UI. Although with some tweaking you'll find that you can still customize it to your liking!
Have fun!
one last question. I cannot find the market in this version? Should I do something more? maybe patch it, or Install it as an upgrade?
Bastian_n said:
one last question. I cannot find the market in this version? Should I do something more? maybe patch it, or Install it as an upgrade?
Click to expand...
Click to collapse
Yes with the CM 7 Rom you will have to install the Google Apps separately.
Google apps may not have been included in the rom's installation. All you will have to do is download the Google Apps from HERE. Go to the very bottom of the page and click on "Download" for CyanogenMod 7.
Next, follow these instructions:
Once booted you might find some apps are missing, namely the Android Market, Gmail, etc. If this has happened, you will need to flash the Google Apps pack. To flash, copy the Google Apps to the root of the SD card, boot into the custom recovery image, and flash the Google Apps package like you flash any other ROM (do not wipe data after flashing the Google Apps package). SOURCE
Click to expand...
Click to collapse
I'm facing a problem very similar to the one described in this thread.
As one can see in the picture, the screen gets all blue.
After trying so many things, I came to the conclusion it's NOT a hardware problem because if I go back to stock GB, the screen is fine.
It's also fine if i install ICS, with CWM 5.x.
On the other hand, if I go to any JB ROM, tryied many ROM's and several kernels (mackay, semaphore, devil, ...), all of them brings the same blue screen.
To me, it seems to be a problem with CWM version 6 or above. Which is kind of strange, because I couldn't find anyone else having the same problem, except for the thread above.
So my questions are:
1) is there a way to have JB, but keep stock recovery instead of CWM? Or maybe have JB 4.3 with CWM 5.x ?
2) maybe there's a place where CWM keeps its settings and I can go there to delete them and/or reset them?
Some history:
I managed to install JB 4.2.2 and it was working for over 1 month. One night my wife installed an app called Jater Calendar and started playing with its color settings. The battery went dry and the next morning the phone booted up all blue.
I've already tried to install that app again and try to find some "restore settings", but I couldn't find anything.
Maybe it's just a coincidence, some app shouldn't change CWM settings like that. Or could it?
MrCabana said:
I'm facing a problem very similar to the one described in this thread.
As one can see in the picture, the screen gets all blue.
After trying so many things, I came to the conclusion it's NOT a hardware problem because if I go back to stock GB, the screen is fine.
It's also fine if i install ICS, with CWM 5.x.
On the other hand, if I go to any JB ROM, tryied many ROM's and several kernels (mackay, semaphore, devil, ...), all of them brings the same blue screen.
To me, it seems to be a problem with CWM version 6 or above. Which is kind of strange, because I couldn't find anyone else having the same problem, except for the thread above.
So my questions are:
1) is there a way to have JB, but keep stock recovery instead of CWM? Or maybe have JB 4.3 with CWM 5.x ?
2) maybe there's a place where CWM keeps its settings and I can go there to delete them and/or reset them?
Some history:
I managed to install JB 4.2.2 and it was working for over 1 month. One night my wife installed an app called Jater Calendar and started playing with its color settings. The battery went dry and the next morning the phone booted up all blue.
I've already tried to install that app again and try to find some "restore settings", but I couldn't find anything.
Maybe it's just a coincidence, some app shouldn't change CWM settings like that. Or could it?
Click to expand...
Click to collapse
Just to clarify some of your questions:
-CWM 5.x.x.x is only compatible with Gingerbread and ICS. JB can only use CWM 6.x.x.x (as far as I've see for the S anyway). So no, you can't use CWM5 on Jelly Bean...
-I don't think CWM has this setting in recovery. Other kernels such as Semaphore with its own custom recovery might.
I took a look at the other thread and what xsenman and you posted, and this SEEMS like a hardware fault but isn't... I mean if colour corrections apps + advanced device settings don't work, then this is usually beyond the software.
Which version of Mackay have you tried- stock CM colours or Voodoo? Or have you tried both?
EDIT: Hold on a moment. You have an I9000B...
I9000B roms are NOT the same as the international I9000.
Hmmm.
Try Helly Bean- and make sure you get the I9000B version- and see if that changes anything. Or you could try CM builds for the I9000B (the code for it is galaxysbmtd).
I don't think its very likely but it MAY be due to the device (and therefore the kernels, even if they're only miniscule) being different.
Sent from my GT-P7510 using Tapatalk HD
Thank you very much for your quick response.
"this SEEMS like a hardware fault but isn't"
It can't be! If hardware were faulty, it wouldn't work on ICS or GB.
"Which version of Mackay have you tried- stock CM colours or Voodoo? Or have you tried both?"
Both, 0.199 Final CMC and VC. Also tried Devil3 (CMC and VC), GearKernel (JB, JB3, JBPlus) and Semaphore JB 2.9.12b.
All of them load the logo fine for 1 second, then it flashes really fast and becomes blue.
I'm wondering whether its to do with the fact that you flashed roms that weren't meant for the I9000B.
Try flash this- make sure you download the I9000B version- and see if the results are the same: http://forum.xda-developers.com/showthread.php?t=2012061
Sent from my GT-P7510 using Tapatalk HD
Yes, I know that ... the versions of CM I am using are all for i9000B. I even tried the i9000 (without B) to see what happened. It's also blue and the touch doesn't work.
I also tried Helly Bean (the 4.1.1 or 4.2.2 version, I don't remember which), same blue effect.
MrCabana said:
Yes, I know that ... the versions of CM I am using are all for i9000B. I even tried the i9000 (without B) to see what happened. It's also blue and the touch doesn't work.
I also tried Helly Bean (the 4.1.1 or 4.2.2 version, I don't remember which), same blue effect.
Click to expand...
Click to collapse
Hmmm.
If you're on 4.2.2... Have you tried this as well? (sorry, I know I'm probably not helping too much but its better to try everything and see if SOMETHING happens I guess)
http://forum.xda-developers.com/showthread.php?t=2105611
Sent from my GT-P7510 using Tapatalk HD
Yes, I had tried this one. It's the same file I downloaded yesterday.
The results are the same.
MrCabana said:
Yes, I had tried this one. It's the same file I downloaded yesterday.
The results are the same.
Click to expand...
Click to collapse
Damn. Then I'm sorry, I really have no idea what's going on :/
The only thing I can think of is to ask your wife what exactly she did before that happened using that app...
Or (I'm not sure whether this is possible so someone else may have to correct me) somehow grab a logcat. I'm not experienced with logcats so I can't help you here: but there may be a possibility that taking a logcat, especially during booting (because you mentioned something like it being normal for one or two seconds before going blue) might reveal something, but as I said, I really don't know...
Try PM a developer you can get in touch with and see if they can do anything about it.... Or alternatively (if you ahven't already) try post in the CM thread and pawitp might know something.
Sent from my GT-P7510 using Tapatalk HD
This blue screen problem is very common
Hi
It seems that this blue screen problem is very common in this forum.
Did someone manage to solve this problem, or is familiar with a working solution?
Just in order to be organized and help others, here is a reference to some of the users and their posts regarding this problem:
MrCabana in [Q] Samsung Galaxy S i9000B blue screen problem
kssthomas in [Q] Samsung Galaxy S blue screen error, which also posted a video in YouTube - Samsung Galaxy S i9000 - Blue Screen problem
IntelVN in [Q] [PROBLEM] Blue Screen On GT-I9000
The only thing that I got from all of these threads is that it's probably because of CWM 6.x and above, and that in CWM 5.x everything is okay. (Thanks a lot to MrCabana for this conclusions)
So, did someone manage to solve this problem, or is familiar with a working solution?
Edit: I posted a thread in which I summarize all I know about this issue.
Edit: This issue is solved. Please look in my thread for more information.
need4steer said:
Sorry, I never found a solution to this problem.
Ended up buying another digitizer and after that, it started working again with CWM 6.0 and above.
Even though the problem seems to be "solved", I refuse to accept that as a hardware problem since (again) it was working fine with CWM < 6.0 even with the (maybe) broken screen.
Click to expand...
Click to collapse
MrCabana said:
need4steer said:
Sorry, I never found a solution to this problem.
Ended up buying another digitizer and after that, it started working again with CWM 6.0 and above.
Even though the problem seems to be "solved", I refuse to accept that as a hardware problem since (again) it was working fine with CWM < 6.0 even with the (maybe) broken screen.
Click to expand...
Click to collapse
Really?
Will you please describe in details the steps you did in order to solve this problem?
Edit: I posted a thread in which I summarize all I know about this issue.
Edit: This issue is solved. Please look in my thread for more information.
Click to expand...
Click to collapse
There are no steps. I just replaced the screen digitizer.
MrCabana said:
There are no steps. I just replaced the screen digitizer.
Click to expand...
Click to collapse
Well, thank you for letting us know.
So weird that your screen was fine with CWM 5.x and ICS, and bad and bluish with CWM 6.x and JB, and still a hardware replacement solved it.
What caused you to finally replace it although it doesn't seemed as a hardware problem?
How did you know to replace this specific part?
Edit: I posted a thread in which I summarize all I know about this issue.
Edit: This issue is solved. Please look in my thread for more information.
Hello guys,
I have a samsung gt-i9000 with cyanogen 10.1.3 and a few days ago I had experienced some problems, the home button stopped working. I tried quite a few things, based on the info I found on this site and others (like factory reset), but no joy.
SO I thought to myself, better reflash the ROM, but to be honest, if I do that, I might as well install the latest one (10.2.1), and so I decided to do that, but before I start I have a few questions:
I had a look around but I couldn't really find a definite answer to the following questions, so I thought I might post here.
1)Has anybody encountered any issue on the gt-i9000 with the latest ROM?
2)Can I backup all my apps, upgrade the ROM and then reinstall everything from the backup, rather than downloadeing all the apps again? I have never done that before, so I am not sure if it is possible
3)I had a look at the cyanogen mode site and found the relevant info http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd, but I was wondering something: occasionally on my phone a message appears
and asks me whether I want to update the ROM to the latest available one. I have always dismissed that, but I am thinking, can I do the upgrade from there without going through the trouble of reflashing
it (following the instructions above), or is it essentially the same thing?
4)In the instructions it says "The install guide assumes the Galaxy S is running Android 2.3.". Now, last time I have upgraded - from cyanogen 7 to 10.1 - I attempted to install directly 10 over 7 and things
went horrible wrong. I then reflashed the ROM to 2.3 and then installed cyanogen 10.1 and it was OK. DO I have to do the same thing again and install 2.3. first and then 10.2? If so where do I get 2.3 from?
Thanks
Sorry, can somebody move this under questions, just realized that this isn't the right place.
duratto said:
Hello guys,
I have a samsung gt-i9000 with cyanogen 10.1.3 and a few days ago I had experienced some problems, the home button stopped working. I tried quite a few things, based on the info I found on this site and others (like factory reset), but no joy.
SO I thought to myself, better reflash the ROM, but to be honest, if I do that, I might as well install the latest one (10.2.1), and so I decided to do that, but before I start I have a few questions:
I had a look around but I couldn't really find a definite answer to the following questions, so I thought I might post here.
1)Has anybody encountered any issue on the gt-i9000 with the latest ROM?
2)Can I backup all my apps, upgrade the ROM and then reinstall everything from the backup, rather than downloadeing all the apps again? I have never done that before, so I am not sure if it is possible
3)I had a look at the cyanogen mode site and found the relevant info http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd, but I was wondering something: occasionally on my phone a message appears
and asks me whether I want to update the ROM to the latest available one. I have always dismissed that, but I am thinking, can I do the upgrade from there without going through the trouble of reflashing
it (following the instructions above), or is it essentially the same thing?
4)In the instructions it says "The install guide assumes the Galaxy S is running Android 2.3.". Now, last time I have upgraded - from cyanogen 7 to 10.1 - I attempted to install directly 10 over 7 and things
went horrible wrong. I then reflashed the ROM to 2.3 and then installed cyanogen 10.1 and it was OK. DO I have to do the same thing again and install 2.3. first and then 10.2? If so where do I get 2.3 from?
Thanks
Click to expand...
Click to collapse
duratto said:
Hello guys,
I have a samsung gt-i9000 with cyanogen 10.1.3 and a few days ago I had experienced some problems, the home button stopped working. I tried quite a few things, based on the info I found on this site and others (like factory reset), but no joy.
SO I thought to myself, better reflash the ROM, but to be honest, if I do that, I might as well install the latest one (10.2.1), and so I decided to do that, but before I start I have a few questions:
I had a look around but I couldn't really find a definite answer to the following questions, so I thought I might post here.
1)Has anybody encountered any issue on the gt-i9000 with the latest ROM?
2)Can I backup all my apps, upgrade the ROM and then reinstall everything from the backup, rather than downloadeing all the apps again? I have never done that before, so I am not sure if it is possible
3)I had a look at the cyanogen mode site and found the relevant info http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd, but I was wondering something: occasionally on my phone a message appears
and asks me whether I want to update the ROM to the latest available one. I have always dismissed that, but I am thinking, can I do the upgrade from there without going through the trouble of reflashing
it (following the instructions above), or is it essentially the same thing?
4)In the instructions it says "The install guide assumes the Galaxy S is running Android 2.3.". Now, last time I have upgraded - from cyanogen 7 to 10.1 - I attempted to install directly 10 over 7 and things
went horrible wrong. I then reflashed the ROM to 2.3 and then installed cyanogen 10.1 and it was OK. DO I have to do the same thing again and install 2.3. first and then 10.2? If so where do I get 2.3 from?
Thanks
Click to expand...
Click to collapse
1) Didn't use CM, been on OmniROM
2) You can use Titanium Backup
3)Yeah, you could do that, update it via CMUpdater
4)Just before you install a ROM with a higher android Version, always wipe /system partition.
cool thanks!