Related
I installed the leaked 2.2 update (without the updated radio) and my GPS isn't working. It seems that it just can't get a fix on my location.
Does anyone know if this is a common problem with a fix? Or do u think it is because I did not install the radio update?
-- related to the radio, when it first leaked people were hesitant to install it because the official radio could possibly be different. It seems that a lot more people are installing it since the leaked 2.2, is the previous concerns thrown out of the window? Or is there still a chance that the official radio update will be better/different?
In many countless posts about upgrading to the Leaked Froyo 2.2 build, They say upgrade the radio or many features like the camera etc will be messed up and force close.
Sure upgrading your radio will fix these problems, but I don't think you will get pushed the offical OTA either way...but we shall see.
yea thats what i assumed was the problem, but i wanted to check if anyone had any ideas.
but with regards to the OTA, once its released wont it be rooted and available to be flashed (with new radio) just like we're installing the leak? my worry is, will the radio be different?
Hi all, I'm quite new to this forum and I hope I dont break any netiquette with my question.
Now I have a N1 I bought on ebay, used, rooted and perfectly functioning.
I don't remember how, but I was able to update it to FRG83D downloading the rom, renaming it, copying on my sdcard etc ...
Now ...
I can't update to FRG83D.
I understood that having a rooted N1 NO OTA UPDATE shall ever work for me, not the manual update is available.
I was able to skip the "no signature verification" error suing clockwork mod, but i can't install the patch anyway, the system alway replies "assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk" ... then a serie of letters and number follows.
I know nothing about this, I must confess, but my suspect is that the update fails because something doesn't match between the update and the ROM which is working on my N1 (which is by the way the original one build frg83d
baseband version
32.36.00.28U_4.06.00.12_7
kernel
2.6.32.9-27240-gbca5320 android-build apa26 #1
Any sugestion ?
I mean and idea about where I can download a FRG83D version suitable for my phone ?
If you just want stock with very little tweaks, may i suggest Geo's Rom. It's basically the latest stock rom w/ superuser, busybox, trackball alert etc. Runs amazing too =)
As for breaking any netiquette, you're suppose to post this in the questions forum not the general. Have fun with your phone.
worked!
Thanks Mokurex!
It worked.
It's unbelievable.
I spent three nights in search of an answer, and then you solved it in few seconds.
I'm new to Android, and I must confess that I'm quite disoriented.
There hare hundred of versions, produced by individuals, companies, etc ... The one I used, I mean the one you suggested me, seems to be the fruit of an individual's work in the US.
It's ok to me, sounds and works good.
But It's not the original one, I mean the one released by ... Google ? or ... what ?
It doesn't matter, but I just want to say that it would be easier for us all, newbies, to have some clear guidelines on this, an online guide for dummies, something or somebody who would explain us the difference between a odexed or deodexed versions, what are the pro and cons of rooting a N1, the fact that rooted phones loose the OTA update (which is very VERY painful for us newbies, etc ...).
I understand that we can rely of forums and on kind people like you, but having some clear cut guidelines would be very useful.
... and looking at the future ... I guess I'll have the same problems when I'll have to update to Gingerbread.
I's very frustrating to search the web for a suitable ROM for your phone ...
stefanopelloni said:
[snip]
But It's not the original one, I mean the one released by ... Google ? or ... what ?
Click to expand...
Click to collapse
No, it's not the original. That one is deodexed, so any future OTA updates will not work (as Google's stock ROMs and updates and not de-odexed). You will have to wait until someone repacks the update, then apply it.
stefanopelloni said:
[snip]
It doesn't matter, but I just want to say that it would be easier for us all, newbies, to have some clear guidelines on this, an online guide for dummies, something or somebody who would explain us the difference between a odexed or deodexed versions, what are the pro and cons of rooting a N1,
Click to expand...
Click to collapse
Did you read the wiki? There are lots of posts/threads/guides available.
stefanopelloni said:
[snip]
the fact that rooted phones loose the OTA update (which is very VERY painful for us newbies, etc ...).
Click to expand...
Click to collapse
What are you trying to say? Phones running a rooted, but otherwise stock ROM will certainly received the OTA updates. Now if you use a non-stock ROM, you may or may not receive the OTA update. But whether you receive it or not, you will not be able to apply it as is, until someone repacks it (unless you are using the stock ROM, rooted or not).
I believe you have to use the stock recovery as well if you wanted to update via OTA.
If you want to get Gingerbread by way of OTA, then revert to stock rom and recovery. Everything you need is in the sticked thread in the development section.
Mokurex said:
I believe you have to use the stock recovery as well if you wanted to update via OTA.
[snip]
Click to expand...
Click to collapse
No, you do not. You just need a newer version of Amon_RA (1.9+) or CWM.
Thank you for the correction.
Efrant, Mokurex,
perhaps it's my problem.
My original plan was to restore my phone is a status capable of receiving OTA updates. Considering that I'm not an IT expert it would be easier for me ho have such a phone.
Wandering on the web, I discovered that rooted phones are not eligible for OTA updates.
And most important of all, I'm not eligible to manually update is as well using the patches on the net (signature verification errors ... and many others seen above).
Mokurex helped me a lot (actually, solved my problem by now) suggesting that version of the ROM (I mean Geo's one) but it's the fruit of a work of an individual. I'm very grateful to him as well, but who knows about the future. Will Geo provide a similar version of Gingerbread as well ? Because without him I can't upgrade.
Efrant, got your remark.
I have CWM, latest version, I also bought the premium version (in oder to show to the programmer of it my appreciation) but in my case it just doesn't work.
With it, I can bypass the signature issue, but then I got stuck at assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk
Oh, by the way, I also tried to go back to ERE27 or something like that (unrooted version etc ...) but the mobile just doesn't work at all ...
I understood that the only way to unroot my phone (actually, any phone) and qualify for the OTA is via SDK.
... but I'm afraid it's just a bridge too far for my poor knowledge.
Geo has been quick to update his rom to the newest version. To upgrade to gingerbread, i'd assume that it would be like flashing any other custom rom, but there might be a bit more steps involved.
If you want completely stock, no root whatsoever, go here.
stefanopelloni said:
[snip]
Wandering on the web, I discovered that rooted phones are not eligible for OTA updates.
And most important of all, I'm not eligible to manually update is as well using the patches on the net (signature verification errors ... and many others seen above).
Click to expand...
Click to collapse
I said it before, and I'll say it again: rooting has no bearing on the phone's ability to receive and install OTA updates -- what matters is which ROM you have. I rooted my phone when I bought it, and it had Eclair on it. I have received EVERY OTA update without any problem.
stefanopelloni said:
[snip]
Efrant, got your remark.
I have CWM, latest version, I also bought the premium version (in oder to show to the programmer of it my appreciation) but in my case it just doesn't work.
With it, I can bypass the signature issue, but then I got stuck at assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk
Click to expand...
Click to collapse
That is probably because you were not using a stock ROM...
stefanopelloni said:
Oh, by the way, I also tried to go back to ERE27 or something like that (unrooted version etc ...) but the mobile just doesn't work at all ...
I understood that the only way to unroot my phone (actually, any phone) and qualify for the OTA is via SDK.
... but I'm afraid it's just a bridge too far for my poor knowledge.
Click to expand...
Click to collapse
If you want a stock ROM, you can go here: http://developer.htc.com and download a Nexus One image to your sdcard, rename it to PASSIMG.zip and boot the phone into bootloader (by holding the trackball and powering up the phone). It should automatically detect the file and allow you to flash it.
Files from the site are official. If you get them from anywhere else, you can't really know what's been modified.
Dear Efrant,
if you were a girl, and in Italy, I would probably kiss you.
Now I have a bright-clear picture of the situation.
During the next holiday, I'll try and flash a stock version of the OS and then try the OTA update.
By now, the version mokurex suggested me work brilliantly and after so many nights wasted in a desperate search of an answer my myself i'm going to have a break.
... but thanks a lot. thanks indeed !!!
Sorry to disturb you again Eftant.
The fact is that today decided eventually to follow your step, but encountered another unexpected problem.
downolaed the original HTC rom - done
renamed it passimg.zip - done
turned on the N1 pressing trackball - done
expected detection of PASSIMG.zip - done
opening passimg.zip - done
checking passimg.zip - done
and then .. nothing
once the N1 load the passimg.zip file (i notice it from a loading bar on the upper right conder of the phone) it just allow me to
1)run bootloader agan
2) lock sim
3) restore something ...
... and that !
No possibility to "flash" rom as you wrote.
Did I miss anything ?
I see from the web that a lot of people bring back the N1 to the stock image using SDK from PC (MAC in my case) but the steps are not so clear considering the fact that I'm not that comfortable with the shell and the Android SDK is not intuitive (... to me).
Thanks in any case for your attention!
Try wiping your device then download the FRF91 image from the same site, rename it to PASSIMG.zip and save it to the root of your sdcard. Put your sdcard back into your device, and boot into the bootloader (by holding down the trackball as you push the power button). Once it flashes, wait for the OTA to FRG83G. Some users have said that the later images don't work using, particularly if you have updated to the 0.35 version of the bootloader.
A while back, just before the 2.2 OTA update came out for ATT locked streaks I received a replacement streak from dell. I didn't have it long enough before I applied the update to remember if the compass or sensors were working, but I seem to remember the screen would auto rotate just fine.
After the update the screen would not auto rotate at all. I spent a while looking into fixing it, trying things like srchild.com's calibrate-sensor-on-upside-down-dell-streak-after-froyo-22-android-upgrade
But I have a slightly different version of the menu's than that tutorial shows and nothing I did fixed the auto rotate so I eventually just learned to live with it in landscape mode for a while.
Now I realize that no compass or sensor based apps work. I've installed sensor monitor apps and they show no data. The "Calibration" application that shows bubble levels doesn't move at all. I'm starting to think it is a hardware problem but like I said, I am almost sure that screen rotation worked before the upgrade on this device.
Is there a way to verify for sure before calling dell. Their support was a nightmare to deal with the first time.
TIA
Why go through the trouble? Why not root your Streak and flash a custom ROM. They perform much better.
If you don't like them then you could always use the QDL tool to get back to stock but everyone here knows the OTA updates wreak havoc for almost all Android devices
cdzo72 said:
Why go through the trouble? Why not root your Streak and flash a custom ROM. They perform much better.
If you don't like them then you could always use the QDL tool to get back to stock but everyone here knows the OTA updates wreak havoc for almost all Android devices
Click to expand...
Click to collapse
A new ROM, stock or custom, won't fix the problem if there is a hardware issue. Installing a different ROM might help troubleshoot the problem. I would suggest a stock ROM so that if the problem persists there is no questions concerning the warranty. 353 is the latest AT&T ROM and can be downloaded here.
You don't have to root and then install StreakDroid, you can install SD without rooting first.
The updates I have gotten for the Streak have been excellent. I run Stock 351. My streak was purchased unlocked from Dell. In addition the OTA update I got for my Moto Backflip was a huge improvement and the update on my wife's Inspire that enabled the setting to install non-market apps works fine. I would have to say that not everyone here agrees with your assessment of the OTA updates.
To the opening poster I would suggest a reset or reinstall of 353 and then test with no apps installed.
I should've specified the OTAs from DELL are notorious for causing issues.
And you are correct, not everyone here would agree with them, but if you like to tweak and play, then a stock ROM doesn't offer much flexibility, not to mention performance wise.
When I first got my Streak I bricked it, then I revived it with the QDL tool and then went to StreakDroid. Then I even went back to stock to have a baseline to compare with the StreakDroid beta I'm currently using, and I have to say, stock is just that, stock, it's two worlds, performance and battery on stock just don't compare to any of the custom ROMs.
I know this isn't the place for this discussion but I couldn't help but make my point. If you like the stock ROM, I'm happy for you, but I for one have never been much to settle for less, I'm always looking for the latest thing.
Having not looked into updating android a great deal I'd appreciate any corrections if I'm mistaken on this, but I do believe the over the air update that was installed is the 353 version.
My Streak currently reads:
Baseband version: GAUSB1A135331-US
Build number 15697
marvin02 if you still think downloading and installing the the 353 ROM you linked to would help diagnose the issue I'd be more than happy to, please let me know.
cdzo72 I do plan on installing custom rom's and even getting into Android development in the near future but I do not have time for it yet. I would like to make sure I do not have a hardware problem before installing any custom rom's because it will be easier (less time consuming for me) to make a warranty claim if I need to. Unfortunately right now functional and limited is better than cutting edge and time consuming for me when it comes to my Streak.
data_loss said:
. . .
My Streak currently reads:
Baseband version: GAUSB1A135331-US
Build number 15697
marvin02 if you still think downloading and installing the the 353 ROM you linked to would help diagnose the issue I'd be more than happy to, please let me know.
. . .
Click to expand...
Click to collapse
A fresh install would eliminate (mostly) the possibility that your problem is caused by software, not hardware. If you still have the stock recovery on your phone you can just download the .pkg file, put it on your SD Card, rename it to update.pkg and boot into recovery to install.
I do still have the stock recovery.
I downloaded and installed the 353 ROM. It appears that the sensors are not working (no auto screen rotation). I also tried a factory reset after the update just for giggles, no change.
If I'm not mistaken the Streak_104_4399_21.pkg that can be downloaded from the streakdroid site is the official att&t 1.6 ROM. Would it be worth downloading and downgrading to that to test?
Or at this point do I just endure the call to dell support?
Is there any kind of documentation available for the fastboot menu on the streak? There seems to be options available for sensor stuff in there but I don't want to be just clicking through them without knowing what they do.
One hour on the phone ( which was not much fun ) and a couple days later and I have a replacement. It is a refurb, but in good condition and it works. Thanks all for the help.
Sent from my Dell Streak using XDA App
Alright, so I'm quite cautious before I proceed with the update but I've been hearing mixed results with the 2.3.5 update. I pretty much have the update ready to go in the ext SD card.
I was wondering since my phone is fairly new and stock, have the problems experienced by users who updated to 2.3.5 (such as null IMEI and touch screen issues) only affected those who have rooted and are running different roms? or could it affect me if I do an update to 2.3.5?
As for null IMEI, what significant impact would it have on my phone?
I'm really keen to go on Gingerbread as there doesn't seem to be any OTA updates to 2.3.5 here in NZ...
Current Android Version: U8800 V100R001C00B136
Cheers
I have been upgrading from stock 2.2 and did not have any problems at all. All went smooth and everything is working as it should. I am using 2.3 beta 1 update, because it has unlocked bootloader, otherwise it is preety much the same as final 2.3 release.
oh, do the problems people experience persist in beta 1? or over the official one?
Like I said, I did not have any problems with it and I had stock phone just like you (no costum rom, no costum partition). I know people have reported many problems with these updates but it works for me. If someone has different experience please post it and write in what state your phone was before update ( costum rom, partition, etc...)!
when I got my brand-new phone from the store, it was 2.2 but rooted (!) and no g-apps.
The update to 2.3 was no problem and everything works fine.
no root any more, but I don´t need it anyways.
Wurstwa55er said:
when I got my brand-new phone from the store, it was 2.2 but rooted (!) and no g-apps.
The update to 2.3 was no problem and everything works fine.
no root any more, but I don´t need it anyways.
Click to expand...
Click to collapse
did you update to the beta builds or the 'original' build? I guess I won't have to back up if its only a rare minority experiencing these faults.
Stephen289 said:
I was wondering since my phone is fairly new and stock, have the problems experienced by users who updated to 2.3.5 (such as null IMEI and touch screen issues) only affected those who have rooted and are running different roms? or could it affect me if I do an update to 2.3.5?
Click to expand...
Click to collapse
I have a U8800Pro so I can't offer you an answer as to whether you should upgrade, but all I can say is:
If your phone is rooted, use http://forum.xda-developers.com/showthread.php?t=1325036 to back up your IMEI. It's worth it anyway, even if you don't plan to upgrade
From what I've read, touchscreen issues seem to be occuring for those with Atmel screens (and there's a report of an Atmel screen going bad on its own anyway), not those with Synaptics ones. This is what I've gleaned by reading U8800 threads; again, I have a U8800Pro (which all come with Synaptics screens). You can use the tool Elixir from the Market or dial #*#2846579#*#* and navigate through the menus to find out what touchscreen you have
im planning on installing a custom rom at the very least since the stock rom is giving me some software glitches. i wanted to know if theres any problem with the new update that would prevent me from rooting, or is just best to update to the newest version while its still on stock
shatheone said:
im planning on installing a custom rom at the very least since the stock rom is giving me some software glitches. i wanted to know if theres any problem with the new update that would prevent me from rooting, or is just best to update to the newest version while its still on stock
Click to expand...
Click to collapse
if your talking about the AT&T XT2 it can be rooted on any version
problem right now is Huawei's bootloader unlock page is gone and you'll have to try DC unlocker to pay for a bootloader unlock
I was talking about the original XT, I updated since I see most of the road support the latest version