Database Develop

[HOW-TO] Updating Nexus One If You Are NOT Rooted

I know this does not really belong to development but I figured most of the people who want to do the update will come here... Please move the thread if you deem fit, mods ^^.
Anyway, I can't confirm if the method works since I'm rooted myself, but have found the following:
Hi,
I have found out a way to update the Nexus One to the new OTA that Google is pushing through, the one including multi-touch everywhere.
Go to the URL below:
http://www.mediafire.com/?rgnjl4hqmmi
and download.
Then save on to your sd card, not in any folders, and rename it update.zip (windows users just rename it update, .zip will come by itself)
1) Turn off your phone.
2) Turn on by holding down Power and the Trackball
3)Select Bootloader (Selection instructions on the top of screen)
4)Select recovery
5)An Android-Bot will come standing next to an open box
6)Press down Power and Volume Up
7)Select apply update.zip
8) Enjoy!
All the credits go to Fabolous from AndroidForums.com
Click to expand...
Click to collapse
Source: http://forums.t-mobile.com/t5/Nexus...3;jsessionid=237BA996FE5094EB98964E024CF21502
Also, in case you don't trust the MediaFire link, here's the Google One: http://bit.ly/9vvioF
Hope it helps.

I can confirm this method works for non root users. The MT is awesome, to say the least.

When I select recovery it shows a picture of an android next to a triangle with an exclamation point in it. I renamed the file and put it in the sd card, what am i doing wrong?

Unicellular:
5)An Android-Bot will come standing next to an open box
6)Press down Power and Volume Up
7)Select apply update.zip
:\

Wysie said:
Unicellular:
5)An Android-Bot will come standing next to an open box
6)Press down Power and Volume Up
7)Select apply update.zip
:\
Click to expand...
Click to collapse
Did you try pressing power and vol up at this stage? #5 isn't really a step, it just happens. I figured this was a given, but I guess not.

indiearmy said:
Did you try pressing power and vol up at this stage? #5 isn't really a step, it just happens. I figured this was a given, but I guess not.
Click to expand...
Click to collapse
Ya I had assumed that after selecting recovery the android should be next to a box but i did vol up and power down. It is working so far!

I've downloaded the file twice and I'm getting a caution icon with the android-bot. Any ideas as to what could be wrong?
I've also use two different sdcards.
Thanks for any assistance.

B3astofthe3ast said:
I can confirm this method works for non root users. The MT is awesome, to say the least.
Click to expand...
Click to collapse
Second that...this is very cool.

Redeye said:
I've downloaded the file twice and I'm getting a caution icon with the android-bot. Any ideas as to what could be wrong?
I've also use two different sdcards.
Thanks for any assistance.
Click to expand...
Click to collapse
I got the same thing...while at that screen, just did the volume up and power button and it gave me the option to install it.

hi Unicellular,
can you be more specific, i have also the same problem, and could not see any bot near a box, after selecting recovery first colored cross is seen then a bot with a triangle comes up.

Does this use the new kernel?

Trackz said:
I got the same thing...while at that screen, just did the volume up and power button and it gave me the option to install it.
Click to expand...
Click to collapse
Thanks!! It worked.
I think I had the caution icon because of the following.
E:Can't open /cashe/recovery/command
System is back up with multi-touch goodness.

what do you mean?
"The one including multitouch everywhere??"
the multitouch for me only works in the browser maps and the gallery
is there on that includes a multitouch everywhere??

lazoman. I was at the screen with the caution and android-bot too.
It's not really a quick press of "Vol. Up + power button" I kinda just spammed both buttons until it worked.

Trackz said:
I got the same thing...while at that screen, just did the volume up and power button and it gave me the option to install it.
Click to expand...
Click to collapse
I can confirm that this worked for me too. Thanks!

This update took away the haptic feedback when I press the little dots in the main screen to go 'left' or 'right'. Anyone know how to get it back again?

Does this update also apply the new radio update?

Does this method void the warranty or violate the TOS?

What about rooted devices ?
Why can`t i use this update if my phone is rooted ?

christiankk said:
This update took away the haptic feedback when I press the little dots in the main screen to go 'left' or 'right'. Anyone know how to get it back again?
Click to expand...
Click to collapse
Those buttons don't have haptic feedback (i havent updated yet and just checked)

Home button not working??

Hey guys! I hope you can help me D:
My Galaxy S:
CM7 latest update #57 or so
Kernel: glitch v11 (also doesnt work with standard kernel)
Since today my homebutton isnt working correctly. It only works for getting into recovery and into download mode.
If i press it in the keytest in cwm recovery it isnt recognized, same when the phone is booted :-S
I reflashed the update with deleting the cache but that doesnt work D-:
Have you guys any idea? :-/
Thanks
Mario (sorry for my bad english *facepalm* ^^)
Sent from my GT-I9000 using XDA App

Does it work when the phone is booted normally?

No it doesnt.....
Should i send it to samsung? :-/
Sent from my GT-I9000 using XDA App

I'm sorry, but I think that's your only choice.. To me, it seems like a hardware-related malfunction..

Hmmm yes i think youre right.
I just tried to get into recovery only with volume up + turn on button... thats working
"
I will flash samsung original firmware, maybe it works ^^
Sent from my GT-I9000 using XDA App

If it does: great!
If it doesn't: RMA must be the way..

you have to send your phone to Samsung services it'll be best solution i think.

Dudeeee, what on earth man? RMA should only be treated as a last resort. Don't give up so easily. He hasn't even tried flashing back to stock roms.
He already said it works for getting into recovery and download mode, which indicates it's working to some degree.
OP, flash that stock firmware and tell us what happens.

snapper.fishes said:
Dudeeee, what on earth man? RMA should only be treated as a last resort. Don't give up so easily. He hasn't even tried flashing back to stock roms.
Click to expand...
Click to collapse
If you read my post correctly, you'll notice that I've suggested to flash the stock-firmware _before_ sending it as a RMA to Samsung..
snapper.fishes said:
He already said it works for getting into recovery and download mode, which indicates it's working to some degree.
(...)
Click to expand...
Click to collapse
Again, read his post correctly - he was pressing "Volume Up" + "Power On" and did _not_ mention any press on the Home-button..

Eagle3386 said:
Again, read his post correctly - he was pressing "Volume Up" + "Power On" and did _not_ mention any press on the Home-button..
Click to expand...
Click to collapse
So how do you think he has access to recovery???.......He mentionned he was able to go into recovery mode,basically,the home button works.
I'm pretty sure it's a software related problem.
Go with the stock rom first and tell us the result.

Nope.
Im on stock rom now..
The home button is not working
I got into Download mode with Volume down and Turn-on-button
I havent touched the home button at all
Dont know why thats working ^^...
Tommorow im bringin it to the Shop for RMA
OR do you have some Ideas

It is as though your home button is stuck to "on".
I fear that the next step is to rma.

duchkata said:
So how do you think he has access to recovery???.......He mentionned he was able to go into recovery mode,basically,the home button works.
I'm pretty sure it's a software related problem.
Go with the stock rom first and tell us the result.
Click to expand...
Click to collapse
The post above, compared to your latter one:
duchkata said:
It is as though your home button is stuck to "on".
I fear that the next step is to rma.
Click to expand...
Click to collapse
Do you find the inconsistency? No?
I'll help you out: at first, you paint me as a fool, because you're too blind to read my post correctly.
Just one post later, you suggest what I was suggesting since my first (or second, can't remember right now) post.
Result: read first, think second, think again, _then_ - and only then - post, but stay polite at _any_ time!

Had the exact same issue with the button working for booting into recovery and download mode.
Sorry to say this is hardware related and I hope your rma is accepted.
I took mine to the repair centre and they told be it is water damaged. I never dropped it in water though.
Also the home button is glued to the whole freaking screen. The samsung part comes as the whole lcd assembly with the buttons with it so I was quoted 245 dollars.
You can buy the button online but I digest you to have a look on YouTube for the dude that disassemble the phone. You will see how hard it is
By the way, my button stopped working for recovery as well although now of o press hard on it it does work (for booting and in the OS).
last but not least, you will learn how to use the phone without the home button
Good luck with the rma
Sent from my GT-I9000 using XDA Premium App

Removed.
................

hello guys! I have the same problem since yesterday and I would like to know how did it end for you? Is it really hardware or it can be solve by software? Thanks in advance

cholabcn said:
hello guys! I have the same problem since yesterday and I would like to know how did it end for you? Is it really hardware or it can be solve by software? Thanks in advance
Click to expand...
Click to collapse
Yes, hardware. No, can't be.

[Q] [i9001][RESOLVED]Odin stuck in flashing KQB

So a few hours ago, i tried to flash the value pack (XXKQB) ROM on my Galaxy S Plus,it started normally but sort of freezed on ˝setupconnection˝
The phone was still in download mode,and after about 20 minutes of siting there,restarted the phone since nothing was happening, and it´s safe (for now ).
It should look like this,right?(see attachment)
__________________________________________
WRONG VERSION OF ODIN heh,silly me

looks like the pic didn´t upload succesfully

I have no idea what you are doing . How did you set up Odin? did it detect your phone? Have you closed all Kies applications? You could post a link to the thread you got the download from... (Did you ask the thread where you got the download from?) Why is there only one file? Is it meant to be like that? (I know some roms can be zipped/tarred so you only need one file but is this that sort of file?)
The list can go on and on. Please provide more information... What is the status of your phone now? Can you boot up to your home screen or are you stuck at soft-brick screen? I ask this because i don't understand what safe means. I would consider a soft brick safe because i know what to do when i have one... Re-flash!
So to that image. I am assuming this is how you set up odin BEFORE you connected your phone. I would suggest tick re-partition, this WILL factory reset your phone. A suggestions not always necessary, read the thread. If you are on GB already then i don't think you need to. Also usually you are still required to have a .pit file. (I haven't flashed via odin in a long time, so things may have changed) Check you don't need one.
Finally sometimes when i flash via odin, it get stuck i think at the same point you do. I have to unplug and take battery out. If i boot up i get two symbols with a line of some sort in the middle. In this case i go back to download mode and re-flash and it flashes correctly this time.
Sorry for the long message its just the more information the better and quicker people can help. Hope i helped, if not please provide as much information as possible

domi525 said:
looks like the pic didn´t upload succesfully
Click to expand...
Click to collapse
Go back here http://forum.xda-developers.com/showthread.php?t=1581193&page=21 and repeat a question. You didnt setup ODIN right...

I just rebooted it normaly, it isn't bricked or anything like that...
Thanks!
Sent from my GT-I9001

Gusta_HR said:
Go back here http://forum.xda-developers.com/showthread.php?t=1581193&page=21 and repeat a question. You didnt setup ODIN right...
Click to expand...
Click to collapse
Ok thanks!
Fala
Sent from my GT-I9001

So everything sorted?

Talon26 said:
So everything sorted?
Click to expand...
Click to collapse
yep

Hello, ive got the same problem so what did you really do to fix the problem, change the odin version or what??

Eirik2306 said:
Hello, ive got the same problem so what did you really do to fix the problem, change the odin version or what??
Click to expand...
Click to collapse
Search for the flashing tutorial under 9001 software development
Sent from my GT-I9001 using Tapatalk

domi525 said:
So a few hours ago, i tried to flash the value pack (XXKQB) ROM on my Galaxy S Plus,it started normally but sort of freezed on ˝setupconnection˝
The phone was still in download mode,and after about 20 minutes of siting there,restarted the phone since nothing was happening, and it´s safe (for now ).
It should look like this,right?(see attachment)
__________________________________________
WRONG VERSION OF ODIN heh,silly me
Click to expand...
Click to collapse
Replace Odin, and install the files as in the screenshot, the debug mode on the phone, turn off your phone, enter in the flashing mode after 3 buttons.

[Q] Please help me, is my phone bricked?

I'm a complete noob in dire need of help. I wanted to root my phone, and read the 3 procedures mentioned in the sticky thread. The 2nd one (nvflash) seemed very well explained and was sure to work with 2.3.4 so I decided to use that. As I was in my friend's house I used his pc and installed the drivers while my phone was connected in apx mode. Then I double clicked the "install internal xp" batch file which resulted in a black window with some texts, but seeing this my friend freaked out and closed the window before the process was finished. I told him he shouldn't have done that. I then disconnected the phone and switched it on. It seemed to switch on properly. So I then switched it off again and pressed and held the power and vol down switches to see if I got cwm. This showed LG screen for a few seconds and then the screen went off.
Now whatever I try to do I can only see the LG screen for a few seconds and then the screens goes off. No power on, no recovery, no nothing. And I can only attempt to even power on once, after the screen goes off I must remove the battery before the power button does anything again.
I tried to freshly nvflashing the recovery many times, but it made no difference. Does this mean my phone is bricked? Please tell me how I can solve this as I'm really worried.

NVFlashing the recovery again *should* have worked. So we first need to make sure you're trying to start CWM the correct way.
1) Unplug phone
2) Remove battery for 10 seconds.
3) Insert battery
4) Hold volume-down, do not let go, keep pressing it.
5) Press power button, keep it pressed.
If/when you get the second LG-logo, bluish halo, you can release both buttons, not before.

Nope, that was exactly what I was doing to access the recovery. I tried it again just now and it didn't work.
It just displayed the regular LG logo and then the screen went off. I'm not sure the phone completely shuts down 'cause if I keep it like that it gets quite hot and I can't use the power button again to try to power up. Only removing and re-inserting the battery gives me another attempt.
Is there any chance this is a hardware issue?

Hardly any chance this is hardware related if it was working before the first NVFlash.
Good, next step will be to NVFlash a complete stock ROM. You will unfortunately lose any data you might have on it, but that's the price to pay.
Go here, follow the instructions precisely, skip installation of apx-driver. Report back.
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/

Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).

sean8000 said:
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
Click to expand...
Click to collapse
It works, yes, but is the original Froyo. This is just a way to get the phone up and running again.
Later you have a few choices. Either install CWM, then install you ROM of choice, or upgrade it to the latest for your region by using the LG Update tool.
EDIT. Oh, and btw, it is better to open a command-window and type the flash.bat command. If there are any errors you will still have them on-screen.

Thank you for all the help and support. I didn't get a chance to flash the rom till now (being on a vacation without a smartphone sucks). But I'll try it asap and report back.

So, how did it go?

TrymHansen said:
So, how did it go?
Click to expand...
Click to collapse
I haven't flashed it yet. I've decided to do it after I return home. I'm at my friend's house for 2 more days.

Ok, bad news. I flashed the stock rom you linked. The process went pretty smoothly. After the window got closed and the lg logo on the phone was visible 2 times, I unplugged it and installed the battery. But switching it on wasn't fruitful. It just displayed the LG logo for a couple of seconds and then the screen went off (just like before, only faster). I tried repeating the whole process, even tried to nvflash cwm once again, but nothing happened.
So is it a hardware issue? My phone is no longer in warranty period, so a hardware problem would be really bad...

So is it a hardware issue?
Click to expand...
Click to collapse
I don't know.
What would be helpful is to get a copy of the output you get when you NVFlash, it's simply the only way to verify that the flash process went ok. If you have an aborted flash it of course won't work, and may display the behaviour you describe.
EDIT: Btw, early on there were some ROMs which refused to boot properly unless the baseband was of an early variety as well.
If you feel confident the NVFlash has been successfull, smartflash an old baseband as well, see if it boots then.

Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks

gabriel2anjos said:
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
Click to expand...
Click to collapse
Now what's this "Jtag service"? (edit- I googled it and it seems to be a method of un-bricking stuff with specialized hardware or something, but I'm not sure I can have that done where I live)
Is there any way to fix the bootloader by myself?
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?

sean8000 said:
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
Click to expand...
Click to collapse
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.

TrymHansen said:
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
Click to expand...
Click to collapse
Ok, I'll try that when I have the time.
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?

sean8000 said:
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
Click to expand...
Click to collapse
If it is you're only the second person in this forum to ever brick his phone. Anything's possible I guess. Some flash cells may have been damaged the first time the power was yanked. But then we should presumably get some verification errors during flashing.
Anyway, I'm at my wits end, and I really do hope you get it up and running, but I don't have anything more to contribute. Good luck.

Corrupted bootloader means that your cellphone simply don't know what to do when you hit the power button, due to the damage. As the cell phone can't turn, the pc can't recognize it. If your cell phone were a samsung, you could try to use a jig to have acesso to the download mode. But I don't know if it would work for a LG. You could try anyway.
And if you live at big city, usually it's common to have some jtag services.
Please, dont be afraid of hitting thanks
Please, dont be afraid of hitting thanks

Ok, so I took the phone to the service center today. The guys there said its battery terminals are messed up. They said replacement terminals are not easily available, but they'll try to find some. And of course I'll have to pay for it. I guess it's still better than using the phone as a paperweight.
What do you guys think?

Good luck I managed to mess up my phone like you too. I'm from India. But the difference was that I was covered by warranty. I managed to get a bunch of hardware replaced and was up and running again.

[Q] Very slow boot up z1

Does anyone else have this problem?
Even before I Rooted, it's a minimum of 2 minutes from I press the power button to the lock screen coming on.

seggie said:
Does anyone else have this problem?
Even before I Rooted, it's a minimum of 2 minutes from I press the power button to the lock screen coming on.
Click to expand...
Click to collapse
Hmm thats unusual, mine takes arounf 40 seconds or so. what firmware are you on atm?

sofir786 said:
Hmm thats unusual, mine takes arounf 40 seconds or so. what firmware are you on atm?
Click to expand...
Click to collapse
Think I'm on the latest. I'd say 90% of the time it doesn't boot at all and I have to hold power,
volume up and down to reboot, then as I said it's 2 minutes before its usable

seggie said:
Think I'm on the latest. I'd say 90% of the time it doesn't boot at all and I have to hold power,
volume up and down to reboot, then as I said it's 2 minutes before its usable
Click to expand...
Click to collapse
I think you need to flash the software again, because it does sound like a software related issue. the fact that it doesnt boot, something isnt functioning correctly. you are one update behind but the newest update is not yet available in the uk.

sofir786 said:
I think you need to flash the software again, because it does sound like a software related issue. the fact that it doesnt boot, something isnt functioning correctly. you are one update behind but the newest update is not yet available in the uk.
Click to expand...
Click to collapse
Thanks for your help mate. Is there an idiots guide to flashing I could use? This is my first Android phone so I'm not
really sure what I'm doing yet.

seggie said:
Thanks for your help mate. Is there an idiots guide to flashing I could use? This is my first Android phone so I'm not
really sure what I'm doing yet.
Click to expand...
Click to collapse
no worries your welcome: you have 2 options, you can download sony's pc companion and do a repair or you can use flashtool to flash the firmware. If you decide to go the flashtool way heres what to do:
1. Download flashtool from here http://www.flashtool.net/download.php
2. Install the downloaded program to your C drive.
3. Next you need to get a firmware, which you can get from here http://forum.xda-developers.com/showthread.php?t=2469191.
4. Save the firmware to where the flashtool installed, should be here c:/flashtool/firmware.
5. go here http://forum.xda-developers.com/showthread.php?t=2439328 and read from part 4, it tells you how to use flashtool
hope that helps.

What a difference this has made to my phone.
Not only does it boot up in about 20 seconds, it's so much faster in general.
Again, thanks for your help mate