Database Users

[Q] FRG83D update on a rooted N1

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.

How do you know when there is a new firmware out?

Hey guys,
I was wondering if there is some kind of trick or way to know when a newer firmware is out.

That's a good question. Besides finding out here in the forums, if there is a new official firmware will it download automagically?

One known source is www.samfirmware.com
It is not official and should be taken carefully but very useful.

There is a guy called Quattrofromagi who (we think) is a Samsung insider who posts details of new ROMs on Twitter, but if you're not experienced with flashing it's probably better to wait until one of the guys who know what they're looking at have a look and then post about it on here. A great many people got caught out with the signed bootloaders when JM6 came out because of rushing to flash from downloads from FUS or Samfirmware.

Well, if you are looking for stock ROMs or firmwares from Samsung, you can always connect via Samsung Kies to see if you have an update. But trust me its very very late/old and Kies is not really updated that often. Samsung thinks its too much work.
Samfirmware.com is more upto date with the latest official release of firmwares for each continent. However, because they are official releases they also contain the 'bootloader protection' gimmick that Samsung is pushing out. This was a headache at the start of 2011 but thanks to Chainfire and Rotohammer there is a solution to remove the bootloader lock now. Basically, they are locking down the bootloader so people can't install their own ROM unless they are from signed by Samsung and you get it from Kies. Obviously, this is due to carriers complaining (north american carriers) that people are activating the phone features of the tablet by updating their firmware to another continents' firmware, like Europe or Asia where they allow customers to make calls on their tablet.
Your best bet is to follow the forum here and look at what others are putting on. The best part is obviously, there are going to be a lot of posts about people testing the latest firmware, their experiences and how they worked out the kinks. I know it's daunting going through the posts but it can be quite informative in case you meet the same problems as others.
For your info, the best ROM right now that is stable and well tested is JMEv4 by Rotohammer.
The next ROM people are working on now is MoDaCo's kernel and ROM running ext4 filesystem because of its speed. And the overclocked 1.2Ghz kernel is also available for EURO tabs made by richardtrip to mix with any other ROM of your choice. These are currently still not stable but are working and will be ready very soon.
Hope that helps.
Hope that helps.

Thanks for the info. Very helpful.

2.2.2 streak rom question

I just recently picked up a dell streak. It's brand new with what I'm guessing it the latest shipped rom which is build number 15274 running android version 2.2.2
All I see is custom roms and reflashing back to other roms to root....blah blah blah...is there a way to just root my current rom and not have to flash a completely new one? I'm all for supporting the community, I'd just like to keep this as device as clean as possible and remove all the bloatware.

InGeNeTiCs said:
I just recently picked up a dell streak. It's brand new with what I'm guessing it the latest shipped rom which is build number 15274 running android version 2.2.2
All I see is custom roms and reflashing back to other roms to root....blah blah blah...is there a way to just root my current rom and not have to flash a completely new one? I'm all for supporting the community, I'd just like to keep this as device as clean as possible and remove all the bloatware.
Click to expand...
Click to collapse
Download SuperOneClick v1.5.5 and root away. Dont forget to put your phone into USB debugging mode before rooting, its very important that you do that. Or just follow the steps in this link http://forum.xda-developers.com/showthread.php?t=925853 good luck.

Wow thanks, I totally skipped over that post!!! I guess from what I was reading I was expecting the whole process to be a lot more complicated.
Thanks a ton!

Anytime.
«---:: ((รєภҭ ғг๏๓ ҭђє ๓๏ҭђєг ๏ғ คใใ קђ๏ภє'ร ๔єใใ รҭгєคк!)) ::---»

How come Dell don't push out the 2.2.2 version OTA to their customers?
I check for updates every day, but have just once received any. (2.2)
Their way of saying; "we just don't give a f*ck about our customers"?

You should have gotten that update weeks ago. It's been OTA for probably about a month now. And I don't know how much you've read, but a lot of what happened with not updating from 1.6 was probably AT&T's fault because they wouldn't okay the build (speculated). Dell had the source up for 2.2 for a long time, if I remember correctly.

I'm on unlocked stock EU ROM since day one. Just to clarify.
Do you mean the 2.2.2 was shipped OTA, for EU users too?

Ohhh. Didn't notice you were on EU. I don't know if Dell released one for EU yet (probably hasn't since you don't have the option to OTA). Just remember that it's not just the phone maker responsible for updates, the carrier has some say in it, too. Are you still on 1.6? Because you could always try out DJ Steve's ROM if you wanted to try something different.

No, the one OTA update I received, was the 1.6 --> 2.2 on last October.
Since then - nothing. I guess it's only in America people get the 2.2.2.
Thanx for taking time to reply.

No problem, haha. I hope you get it soon

I really want the update to, I'm in the Uk and I'm still on 2.2, I would do it myself but its just to complicated and don't wanna mess up my phone. Has anyone in the Uk got the 2.2.2 upgrade? And to be honest I really wont the 2.3 upgrade, but seeing as we still don't have the 2.2.2 upgrade, I think we'll be waiting a long time :'(

2.2.2?
If someone updated from 1.6, to the "non official" 2.2, is there any difference between it and 2.2.2?

2.2.2 is supposedly immune to the malware loaded from the 50 or so infested apps that Google removed recently from the market.

nTelos Milestone X 4.5.604 update

I've seen a lot of traffic since Monday about the nTelos Milestone X 4.5.604 update to GB. No one seems to have brought it up to here, but the update has bricked quite a few phones. My phone was bricked by a unsuccessful update, wasn't rooted, was stock. Boots in bootloader now.
Now the issue is, nTelos can't fix it, and their new policy is only to give refurbs as warranty. My phone is 2 weeks old, don't really want a refurb, and have a backup Milestone to use, in the meantime.
Anyone have anyway a way to get a hold of the sbf file? Any help would be appreciated.
It also looks as if the old sbf file (2.2.1) is an automatic brick also.

I think you need to call customer service and ream out a manager. Bottom line is the software update that "they and Motorola" pushed bricked your new, not refurb phone. It's not like you rooted it or installed a custom rom, or ran over it, or dropped it in the toilet. Their recommended software update bricked it. I would not stand for it.

Yay, I am no longer the only one here on nTelos!
Anyway, I recently OTA'd to the 4.5.604 update, and it went fine, even despite me being out of state. I was really surprised. But yeah, if you just got the phone, they should give you a replacement. They were more than willing when my MIN settings were messed up to send me a new phone, but they just took care of that over the phone.
I wish someone would release the .604 SBF for nTelos.

They didn't have any refurbs in stock (makes you wonder), so they replaced it with a new phone. Also, the employees haven't done the update....
I had a Samsung phone for 3 days with them, before the X. It's screen would lock up, so tech support told me to take it to the store. I did, and they replaced it with a refurb (without informing me). I got home, saw b-stock on the box. Additionally, it had the same issue (a model flaw apparently). They refused to do anything, so they got the phone back during the trial period.
That's how I got the X. I raised 4 kinds of hell. They gave me the X to shut me up.

success
I didnt have any issues here. I updated mine this morning.

My wife's identical phone also did not have a problem. So it's hit or miss.

nTelos 2
So far I havent been really impressed by the customer service and such. I too am with ntelos, I didnt know that I could find this many people!! Starting to learn with the milestone x what not to do. I would like to find a good guide and a rom that works with this phone. Still googling...

I have this phone with ntelos and I've used Miui and Liquid Gingerbread. I've also heard that gummyjar and liberty work as well but I've never tried them myself. miui is my fav thus far.

What process or guide did you use? I dont think that I have seen any out there. Also where did you get the ROM's? All that I have found havent been valid...Thanks in advance..

Well there used to be a forum for just ntelos android owners but it disappeared for whatever reason. I learned most of this stuff on that forum, so I'll try to help if I can.
You'd flash the rom just like you would if you were on any other carrier.
As for a guide, (and assuming you've already rooted your phone) addictivetips has a good one titled "How To Install A ROM Or App From Zip File To Android Device From Recovery" (Sorry the forums don't let me post links yet)
I've used this article a lot.
When looking at a rom I generally make sure it meets three requirements:
1. It's made specifically for the droid x or milestone x.
2. It doesn't flash a radio from another carrier. (I don't understand all the technical details so someone can correct me here. Almost all of the roms that I've found don't do this so you're safe. I just make sure in the description that it doesn't mention anything about flashing a radio.)
3. It is based off the Gingerbread kernel (since that's the version I'm running).
I'll try to post some links to some roms tomorrow. I've only tried a couple versions of miui and liquid Gingerbread. Let me know what else you need.

jdbell3 said:
Well there used to be a forum for just ntelos android owners but it disappeared for whatever reason. I learned most of this stuff on that forum, so I'll try to help if I can.
You'd flash the rom just like you would if you were on any other carrier.
As for a guide, (and assuming you've already rooted your phone) addictivetips has a good one titled "How To Install A ROM Or App From Zip File To Android Device From Recovery" (Sorry the forums don't let me post links yet)
I've used this article a lot.
When looking at a rom I generally make sure it meets three requirements:
1. It's made specifically for the droid x or milestone x.
2. It doesn't flash a radio from another carrier. (I don't understand all the technical details so someone can correct me here. Almost all of the roms that I've found don't do this so you're safe. I just make sure in the description that it doesn't mention anything about flashing a radio.)
3. It is based off the Gingerbread kernel (since that's the version I'm running).
I'll try to post some links to some roms tomorrow. I've only tried a couple versions of miui and liquid Gingerbread. Let me know what else you need.
Click to expand...
Click to collapse
i cant get my x to flash the recovery so i can install roms. any ideas?

[Q] 2.3.5 update

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