Database Develop

Not a Complete Noob but still STUCK.......

First off, I have an HTC Tattoo. I ran the update from the HTC website which updates the firmare. I assumed wrongly that HTC were finally updating from 1.6 to 2.1. I now have the updated Orange 1.6 installed in my Tattoo.
None of the rooting files or instructions work. I cannot roll back the firmware either and update............ I would really like to get 2.1 installed into my handset but I have tried for almost 1 week now with EVERY method I can find but still keep getting either no space errors or some other annoying text...........
I would appreciate any help with this. Please dont flame me or tell me to go and read another page on these forums about how to root my phone. I can assure you I have been on them all and I have read them all, and I do mean them ALL............... None of them work with this updated ROM image.
Firmware 1.6
Baseband 13.29a.55.13H_3.35.07.35
Kernel 2.6.29-g6561203 ([email protected]#133)
Build 1.67.61.43 CL#97826 release-keys
Software Version 1.67.61.43

To rollback, you have to create a goldcard and install the latest official RUU
follow this guide:
http://forum.xda-developers.com/showthread.php?t=603286
(is useless repeat the same here..)

Aha! Must be the problem I was having! Thanks for the info.
Sent from my HTC Tattoo

Shand359 said:
First off, I have an HTC Tattoo. I ran the update from the HTC website which updates the firmare.
Click to expand...
Click to collapse
Where did u get that option? Eather theres some section I cant find, or I dont have such an oportunity....

OK, I managed to get it flashed now to Android 2.1 after much head banging and crying............... for some reason it worked this time. Not sure what I did differently but it now has 2.1 on it. Not the most stable of systems especially when you use the live wallpapers but if u ignore these then it works very well..........
In the end I had to flash to 1.67.405.6 WWE then apply root and the the 2.1 file but at least I have it now...........

Nice! Now, I think this 3d should be closed..

Non-public froyo build updating issues

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

[Q]FRG83G update for [KERNEL]2.6.32.9-g6624e39 [email protected] #1 && 3G DNS issues

[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?

[Q] N1 not receiving update notifications

I just got a used N1 and am using it on TMO as an upgrade from a MyTouch 3G. It was sold as being fully stock (no root, no unlocked bootloader, but I don't know how to verify that), and it is the holiday model (with the QR code on the back)
When I booted it up, it came to the main launcher (it didn't take me through the setup wizard). It looks like the last user did a full wipe (maybe not, because I thoguht that would make the setup wizard popup if they did). It was running 2.2.1 (I think) and had an update for 2.2.2 immediately ready to install. So, I let it install the update, which went smoothly and it's now running 2.2.2, with baseband 32.36.00.28U_4.06.00.12_7 and kernel 2.6.32.9-27240-gbca5320android-build apa26 #1.
I have been patiently waiting for my gingerbread update, and it has not arrived. I figured since 2.3.4 was rolling out, they stopped 2.3.3 updates and that was why I didn't get it. Now that 2.3.4 has rolled out, I still haven't got any updates, even after doing a checkin.
Does anyone have any ideas why I am being forgotten, and how I can go about updating my phone? I will not root or unlock the bootloader - I'm keeping this thing 100% stock and not willing to take any risks with it.
Thanks in advance,
Mike

Update don't get push to everyone at the same time. Be patient

OK, thanks. So it might be normal that I haven't gotten 2.2.3, let alone 2.3.3 yet? From what I've been seeing in other threads, the OTA update being pushed out now is from 2.3.3 to 2.3.4, so that wouldn't work directly from 2.2.2

You can always do a manual update and not have to wait for the OTA. Just download the corresponding files and rename it to "update.zip" and place on your SD card. Boot into recovery and apply update.zip. You remain 100% stock, but no wait.
And no, you need to go to 2.2 before going to 2.3.3 before going to 2.3.4. The OTA's are generally incremental updates.

Can't update to 2.3.3

I'm currently running 2.2.2 OS Build FRG83G. The phone has downloaded the system update but refuses to install it. I keep getting "zip verification failed". I've even tried a manual update with the same results. The phone is rooted and unlocked if that helps. How do I get this phone to update to Android 2.3.3 Gingerbread ?

You have to be stock to apply official updates. Sense you are rooted, why not just flash one of the stock rooted builds in the dev section?

Hmm ok, I will go do that then and see if that works.

<snip><snip><snip>

I am having a similar problem. I have a brand new N1 with 2.2 build 2.16.405.1 CL223106, do you know if I can jump right to 2.3.4 without first going to 2.2.3? Whats with my build number? Why doesn't it show FR....? I tried the #*#checkin*#* and am getting nothing OTA. Thanks.

You may have carrier specific build. Are you with Vodafone, or Videotron, etc?

Shouldn't be with Vodafone or Videotron. Its a PB99100 and should be for Tmobile. I bought this new from a 'questionable' site on the internet and now I'm freaking out. I do get 3G with my tmobile sim card.

Just because it works on T-Mo, doesn't mean it doesn't have a ROM from another carrier. It's possible you got some back stock from a carrier that tweaks their ROM...
I don't recognize the build number, so I couldn't say for certain, but it doesn't sound like a Google build...
You can switch to a stock ROM very easily by following the unroot/restore guide in the wiki. It will wipe your phone, so you may wasn't to backup what you can first (MyBackup is about the best non-root option).

Since you bought a version from a questionable source, does it happen to have a lock symbol at the bottom of the 'X' when you boot up? If so, it will make it sooo much easier to get your phone to a modern version. You could still stick with Google's Stock Android, or you could go with a better (in my opinion) 3rd party ROM like CyanogenMod.