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: (307)
In my opinion, your root is to blame for this.
Growing the old and try one-click-root, it uses the ADB bug, so it works on any firmware.

Secondly - where did you get FRG83D?
I have an operator SLCD device - I did not fly FRG83D. Probably will not arrive, so I scored and returned to MIUI

Post has been editedJiwan - 21.12.10, 11:49



Rep: (16)
Thank you, now I will try the horn. The device bought a week ago, FRG83D flew myself: rolleyes:



Rep: (16)
Jiwan @ 12/21/2010, 11:46*
About my root is guilty of this.
Growing the old and try one-click-root, it uses the ADB bug, so it works on any firmware.

One-click-root - mean UniversaRandroot ???
It does not work on FRG83 (informationUniversal Androot (post # 4972666)And I tried it myself.
I read somewhere that in FRG83 corrected something safe, maybe this is the problem?
How to do unroot?
And if I looked stupidly now on the caste-firmware, the problem will disappear?



Rep: (307)
No, this is:
http://forum.xda-developers.com/showthread.php?t=803682

Turn on the phone in debug mode, you run the program - it uses the hole in ADB makes the root.
Works on any firmware and almost all devices, because The vulnerability of the ADB itself is not android

P.S. Do not forget the driver on USB put

Post has been editedJiwan - 21.12.10, 14:05



Rep: (16)
Thank you, I used this. Root is successful, but when unroot hangs)
Getting mount path ...
/ dev / block / mtdblock3
Ok

Remounting system with read-write access ...

Ok

Removing su ...

Ok

Removing Superuser.apk ...

Ok

Removing Superuser.apk ...
And that's all.

Tell me where you can find a way to roll back to an earlier firmware?



Rep: (307)
So you can put custom recovery? You throw the firmware on the memory card, we flash a custom recovery, you go to it - you flash the firmware - voila, you are on the new firmware.

Flash recovery through ADB:
adb shell
su
flash_image recovery /sdcard/nexus2.img
reboot recovery

Post has been editedJiwan - 21.12.10, 16:36



Rep: (16)
Good day!

One-click-root program is not stable, after several attempts like Unroot passed (the superuser was removed and the SU stopped running the SU). Then he rolled root and again tried to flash recovery. Still flies after rebooting: beee:

Tell me how to quickly roll back to previous firmware and try on them (without Custom Recovery and Nandroid dare, how to restore?)



Rep: (16)
Jiwan @ 12/21/2010, 16:34*
ik you can put a custom recovery? You throw the firmware on the memory card, we flash a custom recovery, you go to it - you flash the firmware - voila, you are on the new firmware.


I tried one of these:http://android.modaco.com/content/google-n...chen-2-2-froyo/

Something did not go, it seemed to hang. After turning off the power and turn on the screen only the inscription Android. I thought all. Glory to God Recovery was loaded for some reason by custom. I recovered him. Refracting is generally stable process and what should I do if everything gets and not Custom Recovery ??

In general, the kettle I am in this: thank_you:



Rep: (307)
The One-Click-Root program is not stable, after several attempts like Unroot passed
Do you hurt her chtoli?! Rut is different, so what did it and it is necessary to clean. Therefore, I also blinded.
Something did not go, it seemed to hang. After turning off the power and turn on the screen only the inscription Android. I thought all. Thank God Recovery booted for some reason by the custom.

Wipe did you hope? :)
There, in the recovery there is a WIPE menu - before moving to another on the firmware you need to wipe everything that is there. When switching to a similar firmware Wipe not necessarily
WIPE - Analogue Hard-Reset in WM
Refracting is generally stable process and what should I do if everything gets and not Custom Recovery ??

In this case, just throw off off. The firmware on the memory card, you go to the bootloader - the phone will pick it up and offered to install. Nothing wrong.
The main thing be extremely careful when flashing Hboot and Radio. You can flash the firmware itself before planning
In general, the kettle I am in this

We were all teapots. I'm literally 3 months ago I also flashed firmware and recovery, not compatible with SLCD. Instead of recovery and firmware I had one black screen - I was afraid that I need :)

Post has been editedJiwan - 21.12.10, 17:00



Rep: (16)
Jiwan @ 12/21/2010, 16:57*
Do you hurt her chtoli?! Rut is different, so what did it and it is necessary to clean. Therefore, I also blinded.

Root did (tried) in two ways, what rolling I can not say (it was necessary to record all the actions: rolleyes :)
1. As in the 1.0-FRG83-Nexusone-SuperBoot header. How to do from it ????
2. This one-click-root itself. It seems after Hanrut, the superuser was removed.
How now wrong is wrong to do - the question ????

Jiwan @ 12/21/2010, 16:57*
Wipe did you hope?

Of course not: d Can't find FAQ Thirdly on the firmware. Is it generally?

Jiwan @ 12/21/2010, 16:57*
In this case, just throw off off. firmware on memory card

And about it where you can read? And about Hboot and Radio?


I did not zadolbal yet? : rofl:



Rep: (551)
mrozanov, If you blocked the bump, then why are such dancing with tambourines when firmware mod.rekavry ??? Shee through FastBoot!



Rep: (307)
Busybox - He is the same bisibox. This program / supplement for the system kernel is expanding the basic functionality. Some programs are needed

Kernel - He is Kernel, it is the same core. As a rule, this word means the kernel of the operating system. Newbies do not need to know this, advanced users, should know what it is.

Root rights - He is the root. Simply put, these are the rights of the administrator, allow you to do what the soul pleases with your operating system. It happens complete, 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.

Hboot - On the same bootloader, on the same bootloader, on the same bootloader. Roughly speaking, this is a bios phone, this firmware that launches your device and is a connected bridge between 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.

How to enter the bootloader - Enable the device with the "Volume Down" button. Butloder navigation is performed by volume buttons. To confirm, use the "Disable" button

Radio - It is the same radio. This is a separate OS, which manages the entire periphery on the phone (camera, sound, etc.). Works on a separate processor and protected from user intervention. The operation of the cellular module and other wireless communication modules is entirely dependent both from the RADIO itself and from the compatibility of the "Radio-Butloder-Firmware"
If the firmware fails, the chance to get a non-working brick is nearing 99%.Not treated, so before the firmware always check the checksum MD5!

MD5 - On the same MD5. Hasching algorithm. To explain for a long time and tediously therefore briefly for the news - in the topics for radio firmware, bootloader and other things, as a rule, they write a string with a checksum of MD5. The checksum is a series of letters and numbers. If the amount of the MD5 of the file you download differs from the amount that is specified by the author of this firmware, it is impossible to flash this firmware, because The difference in sums means that the file was downloaded by broken. View MD5 by any third-party software, for example MD5Summer

Recovery - On the same recovery. This is a special. the bootloader which is loaded from the bootloader, the essence of which is to make changes to the system, since these changes cannot be made with the operating OS, to the same, according to the user, it is simply no right to modify the system (RUT rights do not count. 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 enter the recovery - Through the bootloader. Either via ADB, ADB Shell, Reboot Recovery commands.
Navigation about the recovery is carried out by the trackball.
In the original recovery, a triangle with an exclamation mark on the background of android will appear. To get to the menu, you need to press the power button and not releasing clicking on the top button.

Adb - he is 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.

Swap - He is swap. This is a special file / partition that expands RAM at the expense of the usual non-volatile memory. Due to the fact that the ordinary non-volatile memory is in tens of times more slowly than the RAM, the use of the swap serially slows down the system. It is worth using only if there is an extreme need for additional RAM.

How to create swap
- In the custom recovery, during the creation of an ext part, it is also proposed to create a swap section.

APP2SD
- Special script from DarkTremor who is deceiving the system, forcing her to think that the section on the memory card and there is a phone's memory. Used to fully transfer programs from internal memory to a memory card. The same allows you to transfer cache and Dalvik-cache.
There are 2 versions - one uses the FAT file system, another EXT file system. Difference - Option with EXT does not violate the system if you mount the phone as a flash drive, the ability to transfer any programs.
Disadvantage - firmware must be modified to be able to work with this script.
No stock firmware in the original form (without third-party changes) does not support App2SD and will not

How to enable app2sd.
- To begin with, you need to flash the firmware in which there is support for this script (see the description of the firmware used). Next, simply create an ext part on a memory card (using a custom recovery), the script will automatically turn on when loading.
Multiple teams for beginners (enter after the SU command):
A2SD HELP - will display a list of commands and a description of them
A2SD REINSTALL - reactive script
A2SD Uninstall - Disable the script, drag all programs back to internal memory
A2SD Zipalign - to transfer to each system loading
A2SD CACHESD - Reset Dalvik Kesh to a memory card
A2SD Nocache - Return Falvik Kesh back
A2SD ResetCache - Clear Kesh.
A2SD Heapsizexx - set the maximum cache size for the application in which Dalvik stores the application code. Instead of XX, you should enter the size you need without a space. The recommended size is from 18 to 32. The smaller - the faster, but there is a chance that heavy programs will fly out with errors. Their code simply does not fit into the specified size. Standard size on stock firmware - 24. Standard size on MIUI - 32.With incorrect meaning will completely kill your system, it is treated only by flashing

Sdk - On the same SDK. Developer set for android. Contains various tools for creating programs, among which the debug interface of the ADB. The same contains USB drivers for phones on Android OS.

Where to download SDK - http://developer.android.com/sdk/index.html

Fastboot - On the same fastboot. This is a logoder protocol that allows you to flash any part of the phone based on Android OS without looking at the region or signature. Initially, this feature is blocked, but it can be unlocked. Unlock automatically removes the phone with warranty. Block back unlocked fastboot DO 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 fastbut - Through the bootoder, or include a device with a pinned trackball.

Wipe - Only Wipe. Cleaning, performed in the 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 unlock bootoder :
1) Install the driver for the phone (included in the SDK)
2) Swing this file:http: //savagemessiahzine.com/forum/dl/post/392144/fastboot.zip
3) Enter the fastbut (you need to turn on the phone with a pinned trackball)
4) Open the command prompt, go to the folder in which there are files from the archive (CD command. For example, CD C: \ temp \ SDK drags you to the C: \ Temp \ SDK folder)
5) Enter FastBoot-Windows OEM Unlock

How to flash custom recovery:
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 archivehttp: //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 root rights :
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.
P.P.S. Keep in mind that for android 2.3 you need to have a radio not lower than 5.08 and a bootloader version not lower than 0.35!

Links to the most popular firmware :
MIUI ROM -http://miui-dev.com/forums/forumdisplay.ph...oogle-nexus-one
CyanogenMod7 -http://forum.xda-developers.com/showthread.php?t=723844.
Desirehd ROM -http://forum.xda-developers.com/showthread.php?t=791151
Desire ROM -http://forum.xda-developers.com/showthread.php?t=730290.
Micromod 2.3 -http://forum.xda-developers.com/showthread.php?t=872441.


----
Nevsuses are 2 species:
Operator 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:
0a15 - Amoled Nexus. Prototype.
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.
Custom recovery will not work if the version is lower than 1.8.0.0 in Amonra recovery.

Sign of incompatibility - The screen does not show anything, but the rest at the same time continues to work.
Solution - flash another firmware / recovery

------
That was a little afraid, I hope in the future it will be useful to people and stuffed it in the header

Post has been editedJiwan - 10.04.11, 07:12



Rep: (3)
ATP, useful info;)



Rep: (16)
Thanks for comprehensive information! : thank_you:

Thanks to Jiwan and MVA for 6 days figured out with its device: yes2:

Located by Caste Modaco Custom Rom Desire Port for Nexus One. Everything is working. I got radio and other interesting promgested.

I want to note one identified thing.

The phone came a week ago, the display SLCD. I also updated the firmware to FRG83D.

Unlock, Root is normal. And Custom Recovery did not want to get up. Those. I got up with all the described methods (if everything is done correctly), it worked, but after turning off the power of the phone and the subsequent load is reserved the standard again. It may be a feature of the phone, and maybe the firmware itself FRG83D (I read somewhere that protection changed there).

After flashing on the custom, the problem disappeared, Custom Recovery is loaded.

Thanks again.



Rep: (8)
We rejoice all!

Android 2.3 comes to Nexus One
[Wednesday, December 22, 2010, 10:24]
In the official Twitter of the company Google, a message appeared that the owners of the Nexus One smartphone for several weeks will receive the ability to download the version 2.3 of the Android operating system called Gingerbread.


Android 2.3 comes to Nexus One
The microblog is reported that users of the first generation of the Google smartphone should be patient, and in a few weeks they will be able to install a new version of the software wireless way.

The Android 2.3 version as a whole has no fundamentally new features, and differs from version 2.2 with only some updates in the user interface. According to experts, the Nexus One should hardly wait for the renewal to the end of this year. Most likely, it will happen after the New Year holidays.


http://hpc.ru/news/40115

Post has been edited7MagiStraT7 - 22.12.10, 19:25



Rep: (551)
7MagiStraT7, Boyan. In the neighboring topics on the N1 you do not look at?



Rep: (0)
HELP!!!

I need to get rid of custom recovery and return the original (Clockwork Mod Recovery) to receive updates by air, because There is no normal Internet right now, only 3G. Already the whole brain broke, google tortured, everywhere they write a rollback to the old recovery, but there is no place for the instructions !!!

Model:
Nexus one

Android version:
2.2

Software version of the communication module:
32.36.00.28U_4.06.00.12_7

Kernel version:
2.6.32.9-27227-G3C98B0D.
Android-Build @ APA26 # 1

Build number:
FRF85B



Rep: (551)
Alternaite @ 12/22/2010, 21:52*
Everywhere they write like a rollback to the old recovery, and there is no place for the instructions !!!

In the header themes did not try to peek?From herePerform p.p. 1-8, only instead of ERD79 use FRF91 (references to it again in the header).



Rep: (1)
http://www.3dnews.ru/news/google-android-2...neskolko-nedel/



Rep: (42)
7MagiStraT7,

About the degree of outdars of this news will not say anything.

And about the "no" fundamentally new features, see the wrote did not even bother to see what's new in 2.3
http://developer.android.com/sdk/android-2.3.html


Full version    

Help     rules

Now: 30.01.21, 06:59