yashsingh1/xdaforums huggingface dataset:
[Nexus One Q&A, Help & Troubleshooting] neXus-sniper:
[Q]FRG83G update for [KERNEL]2.6.32.9-g6624e39 htc-kernel@and18-2 #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
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
Looks like you have one of the network supplied N1's, which have slightly different software.
[Nexus One Q&A, Help & Troubleshooting] neXus-sniper:
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 ?
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
Should get it eventually yes, what you do depends on your level of patience ;)
[Nexus One Q&A, Help & Troubleshooting] neXus-sniper:
haha. Thanks Rusty :) I'll wait for few days and will contact u if needed any help.
[Nexus One Q&A, Help & Troubleshooting] neXus-sniper:
XDA - FORUM rocks. I had an unlocked Nexus one with the kernel version [KERNEL]2.6.32.9-g6624e39 htc-kernel@and18-2 #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://xdaforums.com/wiki/index.php?title=Nexus_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 One Q&A, Help & Troubleshooting] Nuwanda612:
Thank you so much for that post :D

(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 :cool: :cool:)
[Nexus One Q&A, Help & Troubleshooting] neXus-sniper:
Awesome .. To be honest credit goes to the lmk0 ;)
[Nexus One Q&A, Help & Troubleshooting] DTKBS:
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?
[Nexus One Q&A, Help & Troubleshooting] neXus-sniper:
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 android-build@apa28 #1

Also I have SLCD verion of nexus one.
[Nexus One Q&A, Help & Troubleshooting] DTKBS:
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.
[Nexus One Q&A, Help & Troubleshooting] neXus-sniper:
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 One Q&A, Help & Troubleshooting] konisan:
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
[Nexus One Q&A, Help & Troubleshooting] Jono-X20A:
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: 2.6.32.9-g6624e39htc-kernel@and18-2#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
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
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.
[Nexus One Q&A, Help & Troubleshooting] Jono-X20A:
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!
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
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.
[Nexus One Q&A, Help & Troubleshooting] Jono-X20A:
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?
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
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.
[Nexus One Q&A, Help & Troubleshooting] Jono-X20A:
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?
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
Yep, that's the point of it, once you've got this sorted you can use the stock update files with no messing.
[Nexus One Q&A, Help & Troubleshooting] Jono-X20A:
Thank you very much Rusty! You have been enormously helpful!

Everything worked perfectly and soo smoothly! Haha! I don't need to worry about bricking my phone anymore. Already loving gingerbread 2.3.4

The PASSIMG method works with no dramas. The phone was updated to FRG83 build first and leaving the phone on standby for about 5mins. It had received the 2.3.4 update OTA. Perfect!!!
[Nexus One Q&A, Help & Troubleshooting] johnupatree48:
ota rom technician

Hi I have a few issues with updates getting this phone on eBay a month ago I activated successfully booted up with avast anti-theft locked extra.I did a hard reset I need a little help with update

And its error mess. I'm kind of new at this,appreciate any advice on how-tos or not to you may have

John M.
[Venue Pro General] Crimson Lotus:
Hi Guys, I haven't own a new phone in while so I decide to give WP7 a try. I have a few question regrading the DVP I just receive today. Built Date is 01/06/2011. I've heard theres a lot of issue w/ this phone, so I would like to know if my phone has any of it, like what are some of the known issue. First Off I have a few question.

1. When the Phone is in Close Position, The front of the phone wobble a little when pressed at the bottom. Is that normal?

2. How do I unlock the Phone so I can use it on AT&T's GSM Network.

Thats it for now...

Thanks
[Venue Pro General] pjfan75:
Yes, mine is the same.

I don't follow the unlocking scene too closely, but I don't think it has been successfully unlocked yet. Also even if you unlock it, you won't get 3G on AT&T.

Some others report frequent lockups, particularly on the 16GB model, so keep an eye out for that. The Marketplace app tends to crash and freeze on a lot of WP7 phones, so you can probably ignore that for now.
[Venue Pro General] JetWarrior:
How do you find out the build date of the phone?
[Venue Pro General] Crimson Lotus:
Thanks a lot pjfans, as for built date, I believe it said so on the box if I'm not mistaken.

I have one more question, How do I extend the Back light time of my hardware keyboard. I fine that it turn off way to quick, I want to extend the time in which it turns off.

Thanks.:)
[Venue Pro General] MikeDupp:
I haven't found a way to adjust the keyboard back light time out. But pressing any key lights it up again, so I usually tap the fn key if I need to turn it back on. The fn key is a press and hold key, so just tapping it once won't affect the message you are typing.
[Venue Pro General] Crimson Lotus:
Update!

Is there a way or option to add sound to your hardware keystroke as you type. I want to add the on screen qwerty sound to my hardware keyboard when i type. Hope it makes sense.
[G Tablet General] jimcpl:
Hi,

Awhile ago, when I was reviewing dmesg on my Gtab, I noticed that I was consistently getting two "bad block" messages. The Gtab itself had been running ok, so I had kind of ignored those.

In parallel with that, I've been trying to get a complete nvflash backup of the Gtab, using "nvflash -r --read X partX.img", to pull all of the partitions.

When doing this, I was able to retrieve all of the partitions from the Gtab, except for partition 11, which as I understand it, is, unfortunately the "system" partition.

I've tried this nvflash a number of times, and get the same error, "read failure". The error occurs near the end of the nvflash command, always with the same (byte?) count.

That got me started to thinking about the bad block messages I had seen in dmesg, and when I went to review dmesg again, sure enough, one of the bad blocks was in the "system" partition.

I am still on stock TNT on this Gtab. The "history" of it is:

Got/installed OTA 3389 after I powered up 1st time

Download 3452, and installed using stock recovery

Had a situation where things were FC'ing, a couple of weeks ago, so I had to install CWM, clear system/swap (2048/0), and then re-install 3452 using CWM. 3452 replaces CWM with stock recovery, so I then used stock recovery to re-install 3452 again (so, at that time, I installed 3452 twice, first with CWM, then using stock recovery).

At this point, I'm not 100% sure if the bad blocks displayed in dmesg have anything to do with not being able to "nvflash -r --read" partition 11, but I'd still like to be able to do the nvflash to backup the Gtab, so I'm hoping that someone here might have some information about these problems, and also some idea of how I could possibly eliminate the bad blocks.

Thanks,

Jim
[G Tablet General] jimcpl:
Hi,

There're the dmesg lines:

<6>[ 6.509581] tegra_nand tegra_nand: tegra_nand_probe: probing (c053bc30)

<6>[ 6.516993] tegra_nand tegra_nand: tegra_nand_scan: found NAND chip (Vendor = 0xad, DevId = 0xdc)

<6>[ 6.576725] tegra_nand tegra_nand: Block 0x186 is bad [chip=0,offset=0x30c0000]

<6>[ 6.673896] tegra_nand tegra_nand: Block 0x43b is bad [chip=0,offset=0x8760000]

<5>[ 7.109313] 7 cmdlinepart partitions found on MTD device tegra_nand

<5>[ 7.115570] Creating 7 MTD partitions on "tegra_nand":

<5>[ 7.120711] 0x000000740000-0x000001740000 : "misc"

<5>[ 7.126240] 0x000003ce0000-0x000004ce0000 : "recovery"

<5>[ 7.131927] 0x000004d60000-0x000005d60000 : "boot"

<5>[ 7.137257] 0x000005de0000-0x0000125e0000 : "system"

<6>[ 7.142361] tegra_nand tegra_nand: Block 0x43b is bad [chip=0,offset=0x8760000]

<5>[ 7.150517] 0x000012680000-0x00001ff80000 : "cache"

<5>[ 7.156331] 0x0000017c0000-0x000001bc0000 : "bootbmp"

<5>[ 7.161933] 0x000001c40000-0x000003c40000 : "logodata"

<6>[ 7.167158] tegra_nand tegra_nand: Block 0x186 is bad [chip=0,offset=0x30c0000]

I guess what I'm worried about is that if I can't nvflash read, then if I ever have to use nvflash to flash, that won't work, I.e. won't be able to recover using nvflash :(...

Jim
[G Tablet General] jimcpl:
Hi,

I've been using nvflash on Windows, so I figured I'd try the Linux version, but (sigh), I just did that, using the bootloader.bin and nvflash from Bekit's dropbox, and got exactly the same error when trying to do the --read for partition 11:

root@ubuntu:/nvflash# ./nvflash -r --read 11 jl-part11.img
Nvflash started
[resume mode]
receiving file: jl-part11.img, expected size: 209715200 bytes
/ 209584128/209715200 bytes receiveddata receive failure NvError 0x120000
command failure: read failed

Double sigh :(...

FYI, it stops with the read failed at exactly the same place that the Windows nvflash.exe did for that --read...

Since I went through the trouble of installing Ubuntu to try this, I also tried --getpartitiontable, to see if output text or binary (on Windows, the nvflash.exe in Bekit's dropbox outputs binary), and found that the Linux nvflash (from Bekit's dropbox) DOES output a text file, so at least that's ONE mystery that was solved, i.e.:

Bekit Linux nvflash - outputs text for --getpartitiontable

Bekit Windows nvflash.exe - outputs binary for --getpartitiontable

Nvidia SDK Windows nvflash.exe - outputs text for --getpartitiontable

Jim
[G Tablet General] muqali:
maybe run badblocks on that partition assuming you can access it from the shell. read only of course
[G Tablet General] jimcpl:
What is badblocks? Is it a tool already on the Gtab?

Jim
[G Tablet General] jimcpl:
Hi,

One other thing I've noticed, and been wondering about is that the size if partition 11 in the partition table is about 209mb, and the nvflash --read fails just before reading the full size. But, the actual amount of space that's used in /system is only about 113mb. Finally, the partition 11 IMG file in Bekit's recovery is also about 113mb.

So I'm wondering if maybe nvflash has some kind of Max filesize, and that's why the --read fails.

If that's the case, then the question is how Bekit pulled the partition 11 that he has in his recovery files?

Does anyone know?

Jim
[G Tablet General] jimcpl:
I've been continuing to research this, and I've some discussions mentioning that formatting /system *MIGHT* eliminate the bad block.

I tried adb'ing into the Gtab while CWM was running, but it looks like the .8 version doesn't have a format command, but I notice that CWM does have a menu item for 'format system' under mounts.

So I'm thinking:

- in CWM, format system, then

- use CWM Advanced restore to restore ONLY system

Looking for comments as to whether (1) this would be safe and (2) might get rid of the bad block?

Jim
[G Tablet General] muqali:
badblocks is a badblocks checking/recording program. I'm not 100% sure what ADB is, my understanding is it is basically like a serial tty into the OS running on the tab. Correct me if I'm wrong.

The format commands under linux would be something like

mkfs.ext2

mkfs.ext3

mkfs.msdos

et cetera.

They might also be mke2fs -options

Again, I'm not sure, I'm not familiar with Android shells and what is available under them. Try some of those though and see if you get joy.
[G Tablet General] jimcpl:
Yes, adb gives you a connection from workstation to device, you can do stuff like push/pull files and shell into the device.

When you boot into CWM (vs. TNT), there's a different set of commands avail. I'll check about what you suggested, but (1) the /system is yaffs and (2) per the post I just made, CWM already has menu item for formatting system.

Thanks,

Jim
[G Tablet General] jimcpl:
Hi,

I just tried what I was thinking of a couple of posts above:

- in CWM, format system, then

- use CWM Advanced restore to restore ONLY system

I was checking dmesg throughout, while adb'ing into CWM, and it still kept showing the bad block, so I tried it a couple of times, but the bad block persisted, so it must be a "hard" bad block that format doesn't clear :(...

Not sure where to go with this at this point. The bottom line is that:

- It appears that the bad block in the /system partition is preventing the nvflash --read from working on partition 11.

- Doing format SYSTEM in CWM doesn't clear the bad block

I'm not so much concerned about the --read problem, but more concerned about if this will result in some as-yet unforeseen problem in the future, i.e., if I do an update later, and then bad block prevents the update from working.

I'm also wondering if something like these bad blocks may be the reason for some of the "mysterious" problems I've seen posted at various times, e.g., the acore FCs and FCs appearing out of nowhere, having to re-partition, etc.? If so, these almost seem like they might be categorized as a "latent defect" type of thing?

Jim
[G Tablet General] jimcpl:
Hi,

I've posted an inquiry on VS's support website about the bad blocks. We'll see if/when they respond....

Jim
[G Tablet General] muqali:
Is there not tab completion when you're at an ADB shell?
[G Tablet General] jimcpl:
I noticed that also :)... It's kind of weird, because you can access command history using up/down arrows, ala bash, but doesn't look like it does command/tab completion. I think it's because of some kind of key mapping or something.

However, what you can do is go into "ash" (similar to bash) instead. Then tab completion works, I think. On the regular (not adb) terminal, you have to do "busybox ash" to go into ash. Not sure whether there's a native ash or if you also have to use the busybox ash in adb.

Jim
[G Tablet General] jimcpl:
FYI, I got a response to my inquiry:

"Thank you for contacting ViewSonic Technical Support. I understand that you have concerns with our ViewSonic G-Tablet. I care about your concern and I am glad you took the time to contact us.

I do apologize but we have dedicated department that supports our G-Tablets. You can contact them direct at 866-501-6405 between 9AM-9PM CST, Monday through Friday."

Is that 866 # "US merchants"?

Jim
[G Tablet General] jimcpl:
Hi,

Oh my!

Did you try the nvflash yet? It looks like the bad blocks are in both system and cache?

Jim
[G Tablet General] Nosunshine:
I'll try to get that up by tomorrow, I just reloaded Win7 and have yet to force feed it the usb drivers to get adb/nvflash working again.
[Streak 5 General] DanielNTX:
G4 TV's Attack of the Show reviews the Dell Streak and gives out a 5 out of 5: Dell Streak Tablet Review
[Streak 5 General] Krad:
awesome... totally agree

only issue i have with the phone is the camera sucks
[Streak 5 General] gasolara2002:
Nice!! The streak is by far the best over all phone i have ever owned. I'm keeping it untill the wheels fall off. LOL!!
[Streak 5 General] borijess:
I knew that had to be some smart people out there besides us. :D

Sent from the Iphone Killer
[Streak 5 General] Foxhoundep3:
finally! , you know what this means, a lot of streaks are going to be sold within the next 2 months, a lot of newbies trying to root it and stuff.

(even though i dont post much i've had the streak since it first came out :D )
[Streak 5 General] stormtrooper1:
People are starting to realize what the Streak is all about and its capabilities. It will only get better.....

Sent from my Dell Streak

AT&T DJ_Steve STREAKDROID v1.6.1

******Superuser Rooted*******
[Streak 5 General] oklahemi:
there is a god and olivia be thy name. too bad she wasnt caressing this bad boy.
[myTouch 4G Q&A, Help & Troubleshooting] mmazzuc1:
Hey guys,

So i am trying to put into recovery mode off reboot because i had a rom install that didnt run properly. When i do the volume down method, it goes to the HBoot screen, and immediately starts calculating some stuff on the screen, it doesnt let me scroll up and down to any other options. Am i missing something?