Google Nexus One - Official firmware



Rep: (53)
Official firmware forGoogle nexus one and amendments to them
PictureGoogle nexus one
Description | Discussion » | FAQ » | Official firmware » | Not the official firmware (custom) » | Purchase » | Accessories »

Android Gingerbeard (2.3.4) Meet

    System Applications (installation) Internet, Communication Contacts Multimedia Other
    В© Jiwan
    WhatBusybox?
    Busybox - He's the same bizybox. This is a program / add-on for the system kernel that extends the basic functionality.

    WhatRootthe rights ?
    Root rights are the same root. Simply put, this administrator privilege allows you to do what your heart desires with your operating system. It happens full, temporary, permanent, etc.
    Previously, in order to get the rights of the root, you had to unlock the bootloader, now, when a bunch of holes in the android came out, a bunch of different methods of getting the root without unlocking appeared.
    The easiest way to get root is SuperOneClick.
    It uses a vulnerability in ADB, so it works on any firmware of any version.

    WhatBootloader?
    bootloader - he is the same Hboot, he is the same bootloader, he is the same bootloader. Roughly speaking, this is the BIOS of the phone, this is the firmware that launches your device and is a connected bridge between the OS and Radio.
    If the firmware fails, the chance to get a non-working brick is nearing 99%.It is not treated.
    Stitch the bootloader from the amole nexus to the nexusCATEGORICALLY CANNOT.

    WhatHboot?
    see bootloader

    How to unlockBootloader?
    1) Download this file://savagemessiahzine.com/forum/dl/post/392144/fastboot.zip
    2) Enter the fastboot (You need to turn on the phone with the trackball clamped)
    3) Open the command line, go to the folder where the files from the archive are located (CD command. For example, cd C: \ Temp \ sdk will drag you to the C: \ Temp \ sdk folder)
    4) Enter fastboot-windows oem unlock

    How to enterBootloader?
    How to enter the bootloader - turn on the device with the "volume down" button pressed. Navigation through the bootloader is done with the volume buttons. To confirm, use the button "Turn off"

    WhatRadio?
    Radio - It is the same Radio. This is a separate OS that manages the entire periphery on the phone (Camera, sound, etc.). Works on a separate processor and is protected from user intervention. The operation of the cellular module and other wireless communication modules depends entirely on both Radio itself and the compatibility of the “radio-bootloader-firmware” bundle
    If the firmware fails, the chance to get a non-working brick is nearing 99%.It is not treated.

    WhatRecovery?
    Recovery - it's the same recovery. This is special. The bootloader that is loaded from the bootloader, the essence of which is to make changes to the system, since these changes cannot be made while the OS is running, and by the standard, the user simply does not have the right to modify the system (Root rights do not count because they are Initially, the user does not have).
    The original purpose of the recovery: install updates for the phone or completely remove user settings
    There are modified recovery, also referred to as custom recovery that significantly
    increase the chances of recovery. They allow, for example, to flash custom firmware, give access to the memory card without booting the OS, clean the Dalvik cache, etc.

    AmonRA, the creator of custom recovery, strongly discourages updating the bootloader if you have custom recovery, because When updating the bootloader, changes are made to the recovery, which leads to glitches in the latter.

    How to enterRecovery?
    Log recovery is possible through the bootloader. Either through ADB, adb shell commands, reboot recovery.
    Navigation about the recovery is carried out by the trackball.

    What's thatAdb?
    ADB - he is an adb. (ADB - Android Debug Bus) This is a special interface designed for debugging devices based on the Android OS. Included in the SDK. Gives access to the phone through a computer, even without a loaded / broken OS.
    To access the phone while the OS is running, you need to enable debugging mode (USB debugging) in the phone properties.

    WhatSdk?
    The SDK is the same. (SDK - Software development kit) Developer kit for OS Android. It contains various tools for creating programs, including ADB debugging interface. Also contains USB drivers for phones on Android OS.

    Where can I downloadSdk?
    WhatFastboot?
    Fastboot is the same fastboot. This is the bootloader protocol, which allows you to flash any part of the OS-based phone android regardless of the region or signature. Initially, this feature is blocked, but it can be unlocked. Unlocking the phone automatically removes the warranty. Block back unlocked fastbootDO NOT. When the bootboot is unlocked, an open lock is drawn at the bottom of the screen, and the bootloader itself says * UNLOCKED *

    I want to note that it is safer to flash a bootloader or radio through a fastboot than through a recovery, because F
    Stut conducts integrity testing but this does not guarantee the absence of problems during the firmware.

    How to enter modeFastboot?
    You can enter through the bootloader, or turn on the device with the trackball clamped.

    WhatWipe?
    Wipe - it's the same wipe. Cleaning is performed in recovery. Clears the selected partition. Possible options:
    Wipe ALL userdata - Clears all sections listed below except for the last two.
    Wipe / data - Clears the / data section where user data is stored.
    Wipe / sd-ext - Clears the EXT section on the memory card (in case it is present)
    Wipe /sdcard/.android_secure - Clears programs installed on a memory card. (Froyo app2sd)
    Wipe / Cache - Clears the / cache partition where the cache is stored.
    Wipe / Dalvik-Cache - Clears partitions in which Dalvik cache can be stored.
    Wipe battery stats - Clears battery usage statistics
    Wipe rotate settings - Clears the phone's sensor settings.

    It is often said that wipe is an analogue of Hard-reset in WM, but since WM, in contrast to android, uses ROM memory-image - in case of OS crashes as a result of picking, full-wipe will not restore the system. it will just clean the broken system, and it will still not boot.
    Wipe should be done when moving from one firmware to another, it is done BEFORE flashing. Otherwise, you will get a dump from 2 firmware, which at best will be buggy, at worst it will not load.

    When switching to a similar firmware, for example, from the old version to the new one, it is enough to make a wipe cache and a wipe of the dalwick cache.
    When switching to a new kernel, it is enough to make a wipe cache and davick cache

    How to flash customRecovery?
    Method number 1* Need unlocked bootloader*:
    1) Download the recovery you liked and throw it into the folder where you have adb and fastboot
    2) Enter the phone in fastboot mode.
    3) In the command line, enter fastboot flash recovery "here the name of the recovery without quotes"

    Method number 2, unlocked bootloader is not needed:
    1) You will need root explorer, root and terminal rights (Instead of the terminal, ADB will come down)
    2) Download this archive//savagemessiahzine.com/forum/dl/post/737671/Archive.rar
    3) Throw the file nexus2.img in the root of the memory card.
    4) Using root explorer, throw the flash_image file into the / system / bin / folder
    5) In order in the terminal, enter the following commands:
    su
    flash_image recovery /sdcard/nexus2.img
    reboot recovery

    5a) If you are using ADB, enter the following commands in order:
    adb shell
    su
    flash_image recovery /sdcard/nexus2.img
    reboot recovery

    How to get rightsRoot?
    1) Download the super-one-click-root program from here:
    http://forum.xda-developers.com/showthread.php?t=803682
    2) Make sure that the setting mode is enabled and the drivers for the phone are installed.
    3) Connect the phone to the computer
    4) Run the program and poke root.

    How to flash custom firmware
    1) Install custom recovery
    2) Download the firmware and shove it on the memory card
    3) Go to the recovery
    4) Select the Flash from zip item, then select your firmware and the firmware process will begin.DO NOT FORGET BEFORE THE FIRMWARE MAKE A WIPE
    P.S. For some firmware you need to disable signature verification. This is done there in the same recovery, point other, then Toggle Signature Verify.
    __________________________
    Nexus are of 2 types: Camera and original. AMOLED and SLCD.
    The original Nexus - delivered only with AMOLED screens, sold and maintained by Google itself. Since the summer of 2010 there are no sales, support has been transferred to the manufacturer of HTC.
    Get updates from Google itself.

    Camera nexus are the same as nexus, but unlike ordinary nexus, operators support them. These are Korea Telecom, Vodafone, Videotron, etc.
    Since summer 2010, only SLCD screens are installed on camera Nexus.
    Unlike the usual nexus, on the operator nexus there are firmware supplied from the operators, with various additions / differences such as the presence of a Chinese or Korean keyboard, a dictionary, etc.

    How to determine the type of nexus:
    In the bootloader version of microp:
    0b15 - AMOLED Nexus.
    0c15 - SLCD nexus.

    Note: On SLCD nexus, firmware in which there is no SLCD support will not work. These include any version of Android 2.1 and some others.
    Some XDA users also say that the original FRF91 from the amoled nexus does not work for them.
    Also, custom recovery will not work if the version is lower than 1.8.0.0 in AmonRA recovery
    Instructions :
  • Official and leakage of firmware based on android 2.2
  • Installing the original firmware
  • Firmware for Google nexus one based androyd 2.1
  • firmware updates at the official way to the presence of the modified stitched rekaveri
  • Rollback to the original ERE27 firmware and subsequent Android 2.2 firmware (Froyo)
  • Modified firmware recovery RA-nexus-vX.X.X
  • Install Busybox
  • Getting Root rights
  • Unlocking bootloader'a
  • Video instructions
    Program for your phone :
  • Nexus unlock program
  • ROM Manager
  • Keyboard with Russian input from HTC desire with a bunch of changes
    Official firmware
  • ATTENTION. ALL WRITTEN BELOW YOU DO AT YOUR OWN RISK
    PASSIMG firmware contains all of the system partitions, so that after the installation of all data will be erased, including recovery. In addition to the flash card.
    1. Download the correct firmware. rename it in PASSIMG.zip and put it in the root of the flash card.
    2. Turn off your phone.
    2. boot into bootloader (when the phone is switched off, hold the Volume Down key and the power key and hold)
    3. The phone will start to scan for updates on a USB flash drive. and when you find PASSIMG.zip will scan the file and will tell which sections in it and there are 2 options pridolzhit
    install the firmware - the volume up key and stuvit firmware - Volume Down key.
    press the volume up keyOr turn off the phone before installing the firmware(As long as it does not prompt you to restart it by pressing the Volume Up key).

    If after installing superboot you broke wifi. install or boot.img stock of your firmware or install superboot with himem also for your firmware version. 1 option should definitely help.

  • ERD79 , Mirror on the people . The first version of the firmware. Release Date 2009.12.19. insecure boot , superboot , Superboot with himem
    ERE36B, Mirror on the people. Version 7 beta. Release Date 2010.02.06.insecure boot, superboot, superboot with himem
    EPE54B, Mirror on the people. Version 9 beta. Release Date 2010.02.25.insecure boot, superboot, superboot with himem
    EPE68, Mirror on the people. Version 10 Release Date 2010.03.13. insecure boot, superboot, superboot with himem (Suitable from EPE54B)
    EPE76, Mirror on the people. Version 11 Release Date 2010.03.18.insecure boot, superboot, superboot with himem

    There is also a firmware ERE27 it is updated over the air firmware ERD79
    It also exists in the form of a manual update ERD79 with the original firmware. The complete file is not found.
    ERE27release date approximately 2009.12.25.insecure boot, superboot, superboot with himem

    insecure boot - no root (su) and superuser.apk but with the possibility of installing it. And with adb remount access (You can record in the system directories).
    superboot - With root (su) and the application to access adb remount (You can record in the system directories)
    superboot with himem - With root (su) and the application to access adb remount (You can record in the system directories) + increased memory capacity for applications.

  • Official and leakage of firmware based on android 2.2
    FRF50 first firmware based on android 2.2 is available via OTA only for phones by Google poderennyh Release date approximately 2010.05.22 FRF72 vtoroya firmware based on android 2.2 is available via OTA only poderennyh by Google phones FRF83 third version of firmware based on android 2.2 is available via OTA only poderennyh by Google phones FRF85B The fourth version of the firmware based on android 2.2 is available via OTA and manual updates FRF91 fifth based on the firmware version of the android 2.2 is available via OTA and manual updates FRG33 latest leaked firmware based on android 2.2 FRG83 firmware update based on android 2.2.1. is available via OTA and manual updating firmware over FRF91 FRG83D latest firmware update based on android 2.2.1 FRG83G latest firmware update based on android 2.2.2

    Instructions for the firmware update via the native rekaveri with already stitched modified
    • native rekaverior stock rekaveri included in the drain firmware.
    • Modified Recoverystitched separatelyby instrukitsii
    • insecure boot - no root (su) and superuser.apk but with the possibility of installing it. And with adb remount access (You can record in the system directories).
    • superboot - With root (su) and the application to access adb remount (You can record in the system directories)

  • Official and leakage of firmware based on android 2.3
    • HBOOT 0.35.0017 You need to install the firmware on the basis androjda 2.3
    GRI40 firmware based on android 2.3.3 is available via OTA and manual updates GRJ22 firmware based on android 2.3.4 is available via OTA and manual updates

With the emergence of will append here.

Post has been editedSadowplay - 08.01.19, 02:41



Rep: (0)
someone can put in as a instalil YouTube ???



Rep: (306)
1. Problems with falling asleep \ waking up the device

Me too. The core of stock without overclocking. Xs why. Just minutes ago, at 15-20 spillage device hung on lokskrine and went to reboot. Prior to that, so the same throughout the day 2-3 times stuck on lokskrine (on what not to react), but in the reboot did not go - safely droops
2. Problems with the indication of a missed call, a trackball (or rather its absence)
Did not pay attention
3. Wafer periodically loses connection with netom - regularly icon changes from gray to green status

I noticed, but it does not affect the Net itself
4. Problems with the proximity sensor

Works fine
5. Problems with the Auto adjust backlight.

There is such

So as mentioned disadvantages of me:
1) Low speed of animation. After the old firmware cuts the nerves that animation a la 15kadrov per second. Xs why, in some other places on the contrary the speed greatly increased. Actually this is the only real moment of which I am concerned.
Games so as brake work, although it should be the other way around ??!
2) Often buggy touch screen very often. :( The one bug with the screen turned off, so why ??!

On the positive side:
1) A very strong umenshelis zadderzhki - felt immediately, e.g. press a dialer - dialer immediately climbs.
Came the call - off before 2.2. first 2 times to blink a trackball, and only then sleepily cut one machine. Now the same fashion instantly turn on. In other places so that feel the same zadderzhki decreased. Apparently that's gone Kuzia 65mb RAM :)



Rep: (2)
And what kind of bug with the screen off?
And yet, there is a solution with a trackball -http://www.google.com/support/forum/p/Goog...565ba&hl=en
Only here with a reduced convenience store, I can not even download the free program. Can someone give .apk?



Rep: (107)
deGhost,
Strange, but in a market this program is not found. I found it through the AppBrain and installed. Treboll works and mega in different colors after that.



Rep: (2)
dron3d @ 28.02.2011, 00:35*
I found it through the AppBrain and installed.

But it was not possible to me, or the market opens, or hangs on .. You can install APK do? Through the same EU eksplorer. I will be grateful!



Rep: (327)
And no one ran into the problem that in previous firmware occasionally, but manifested such an inadequate perception of taps on the screen, or a sudden loss of signal where it chasm simply can not? Yet, sometimes, the device is usually perceived as the multiple press ... There was not one of these bugs at least once in all the time to use the carrot? :)



Rep: (5)
Here she is:http://ru.androlib.com/android.application...lite-zwxAw.aspx

On Market it is called "Svetovovoy flow-lite" :-]

Chota not think like arc to the post priattachit?
in zipe not downloaded in jpg pereimenoval- does not want ...

Post has been editedflumberto - 28.02.11, 12:08



Rep: (1)
Tell me, ladies and gentlemen, and all after the update is fiercelyguzzles battery?
I have night eating 40% vlegkuyu. Until the end of the day - do not live without recharging ...



Rep: (5)
For me, it began to work longer ...
Previously, only enough light day, and yesterday lasted almost a day: -]



Rep: (0)
People who have already made Root rights to 2.3.3?



Rep: (214)
wer_wolff
on the last page of the



Rep: (107)
Rocas @ 28.02.2011, 11:48*
Tell me, ladies and gentlemen, and all after the update is fiercely guzzles battery?
I have night eating 40% vlegkuyu. Until the end of the day - do not live without recharging ...

It is not the word! The battery on the eyes melting !!! before it was stock FRG83D c radio 32.50.00.32U_5.12.00.08 (see here) Battery problems just forgot.
And now it began again!



Rep: (5)
My ten cents:


1. Problems with falling asleep \ spillage
-No such.
2. Problems with the indication of a missed call, a trackball (or rather its absence)
-Pro trackball pair of posts above.
3. Wafer periodically loses connection with netom -Icons regularly goes from gray to green status
-I understand, color is the indication of the data transfer process. Call quality is not affected. How was a normal connection to the 2.2.2, and right now - I do not complain; -]
4. Problems with the proximity sensor
- the mneya this was when the machine was smashed to smithereens sensor glass. Precu hardest was broken in the place where the sensor is located. And it's not proizhodit periodically and after each call. Oh, and then ... I namuchalsya Indeed, saved only charging or had to wait for two minutes. But glass has long been varied and I enjoy almost "molnienostnym": - D response that 2.2.2 was that now. The gingerbread is likely to increase the sensitivity of the sensor. Try to remove the protective film from the glass, if any.
5. Problems with the Auto adjust backlight
- there is. But it is rather not a bug, but a question of "taste and color markers"; -] To me, if mneya asked to switch back to a smooth brightness adjustment, but without the animation of falling asleep - I would refuse: -]



Rep: (161)
2.3.3 liked me more. Subjectively, battery lives longer.



Rep: (306)
Both funny notice - please back to 2.2 - launched DD - inhibits much stronger than 2.3.3.
And I thought it was stupid, they had a good optimization, once again in the last update time as a machine gun fly ...



Rep: (11)
Good day, I have a nexus operator FRG83D firmware updates, no, it's normal that the update has not yet been reached, you can manually check how the updates ?????



Rep: (4)
fbi_73 @ 28.02.2011, 21:07*
Good day, I have a nexus operator FRG83D firmware updates, no, it's normal that the update has not yet been reached, you can manually check how the updates ?????


steps -Google Nexus One - Discussion (Post # 6689004)



Rep: (1)
flumberto @ 28.02.2011, 11:59*
For me, it began to work longer ...

Tyson @ 28.02.2011, 16:05*
Subjectively, battery lives longer.

A vayfay you always on? While the theory is verified that crap poptyki zakonnektitsya vayfay in sleep mode ...



Rep: (3)
all in dark colors, the phone has become a grim ...
but the animation is off-fly screen: D

Please tell me how to get to the ROOT 2.3.3? For me, not rust.



Rep: (20)
Please tell me how to get to the ROOT 2.3.3? For me, not rust.

It's very simple) for downloading drivers yusb nexus download superoneclick. Click Root, ready) if Ruth can not be obtained, switch off the phone, connect on yusb, click Root, wait until you see the words "veyting odds device", then vklyuchaetsya phone, program it finds, and by the time the phone is switched on, it has already It will rutnut, good luck!)

Post has been editedSelidroid - 01.03.11, 00:11


Full version    

Help     rules

Time is now: 04/04/20, 18:31