> Attention!

We strongly recommend to readRules section "Android - firmware"

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



Google Galaxy Nexus - Firmware



Rep: (655)
Google Galaxy Nexus - Firmware
PictureSamsung Galaxy Nexus, Samsung GT-I9250
Description | Discussion � | Games � | FAQ | Purchase � | Accessories� | Firmware � | Marriage � | Embellishments � | LineageOS � | Slim bean � | Paranoid Android � | MIUI � | Ubuntu os � | Google nexus club �

Important information!
Attention: There is an oral statement of Samsung SC that using programs that create a swapfile (swap file) on our device using internal memory may result in its failure.
Also, personally from myself, I do not recommend formatting the system in f2fs. Too often there are messages about memory problems after this action.
"Why only me without JellyBean 4.3?"
Dear user, if you are faced with this problem, do not panic. Just follow the following points:

    1. You need to know the name of our update provider. (There are several ways to choose from how to do this)
    a) Supplier information is contained in Google Maps.Settings->About the program->Device
    b) You can download and install the utilityGN Official Update Checker.
    c) Or you can useQuadrant standart. Go toSystem informationand see what is written next toProduct(thankDRULEZZZ )
    2. You learned the name of the supplier, namely) If the program displays the word"yakju" or "takju" then try speed up getting updates .b) If the program displays not yakju , you should set 4.3 yourself. How to do it - spoiler "Instructions" In the future, all updates will come through the air and put themselves with your permission.
Question: What isyakjuand why is everything so confusing? Answer: Galaxy Nexus phones get updates either from Google directly or from Samsung. yakju - This is a phone marking, indicating that it receives updates directly from Google, all other words (derived from yakju , eg yakjuxw ) denote getting updates from Samsung. However, Samsung for some reason rolls out the firmware much later than Google. Question: Does the update somehow depend on the place of purchase (PCT or gray)? Answer: Not. It doesn't matter where the device was purchased or even made.
Drivers and Utilities
Instructions
Basic instructions:
  1. Instructions for beginners, including:
    • Unlocking bootloader;
    • Getting a root;
    • Installing custom recovery;
    • Change the update provider;
    • Return to the factory state on any version of the firmware;
    • Manual upgrade to any firmware version.
  2. Installing the official image without erasing data (for example, 4.2, the bootloader is already open)
  3. Change vendor with Nexus Root Toolkit
  4. One-click recovery installation
  5. Full backup / system recovery for non-rooted devices with a blocked bootloader
  6. ADB Backup - Myth or Reality? (backup of user data)
  7. Installing third-party firmware / kernel / radio module / modification.
  8. Firmware backup of the official image via CWM
  9. Install OTA update
  10. Working with the Galaxy Nexus Toolkit (for example, v7.8)
  11. Route + twrp_2.3.2.1 recovery + off-firmware 4.2.1 in one click
  12. Dual boot instruction (Android + Android, Android + Ubuntu Touch)
  13. Formatting memory in f2fs
Other instructions:
  1. Add paths to adb and fastboot utilities in Path (access via command line from any directory)
  2. Recovery of the killed bootloader
  3. Accelerate the creation / restoration of nandroid backup in CWM
  4. Processor Undervoltage Information
  5. Create IMEI backup
  6. Repair IMEI
  7. Repair IMEI from backup
  8. SIM Unlock Application
  9. IMEI Repairfromtrue-satan
  10. One of the options to restore the firmware after complete data cleaningfromalsamoy
Frequently used adb commands:
    More detailed list of ADB / Fastboot commands
  1. adb install<local>// Install the application from the computer. Only valid .apk
  2. adb push<local><remote>// Copy files from computer to phone. Any files allowed
  3. adb pull<remote><local>// Copy files from phone to computer. Any files allowed<local>- path to a file on a computer, for example c: androidgamesgame.apk<remote>- the path to the file on the phone, for example /sdcard/games/game.apk.What is highlighted in green, do not need to be entered into the command line / terminal!
Firmware catalog
Official firmware
Unofficial firmware
Attention! Many references to firmware 4.1.x-4.3.x are irrelevant. Links are left for review.
4.1 - 4.1.2
4.2 - 4.2.2
4.3
4.4
5.x.x
6.x.x
Google apps

Root
Stitch through CWM or TWRP
Attached fileUPDATE-SuperSU-v1.89.zip(1.13 MB)

(SuperSU for 4.2 is preferable)
Attached filesuperuser_3.0.7_elite_update.zip(733.84 KB)
Radio modules, bootloaders, kernels, recovery
Radio modules and bootloaders
Flash img images via Fastboot
The latest bootloader ->Attached filebootloader-maguro-primemd04.img(2.25 MB)

fastboot flash bootloader bootloader-maguro-primemd04.img
zip for recovery

The latest radio module is>Attached filexxlj1.img(12 MB)

fastboot flash radio xxlj1.img

The firmware of communication modules for GSM versions have several types. The most common:
  • UG - Canada and North America
  • XX- Europe
Before flashing, check your version of the radio module in the Settings - About phone menu
Full list of radio modules
Kernels
Recovery
Everything for cores
Utility
Reviews
Survey Screenshots
FAQ

K
There is no curator in the subject. If there is a user in the subject who wants to become a Curator and the correspondingRequirements for candidates, he can apply in the topicI want to be curator(after having studied the topic header and all materials for curators).
Prior to the appointment of the curator, on filling caps, please contactmoderatorssection through a buttonPictureunder the messages to which you want to add links.


Post has been editedSadowplay - 29.12.18, 20:49
Reason for editing: Stock kernel for 4.3 (JWR66Y) with TTL commit support



Rep: (7)
8orms @ 25.01.2012, 00:03*
According to Prisoedenyayus maiklnik.
I rummaged about 12 links to the superbut, and everyone leads tohttp://www.filesonic.com/file/4047388074which is unavailable.

Found a working link to version v2 -http://www.android-advice.com/file-downloa...s-superboot.zip


Do not look, I'm fine and conveniently accessed using Galaxy Nexus ToolKit.
A -101 error crashes constantly. But then I get out of the convenience store and after a while I get a message that the program is installed. How this happens is not understood.



Rep: (418)
Wugfresh Galaxy Nexus Root Toolkit v1.3

Drivers:
This will automatically:
Install the "Verizon_Wireless_I515_Galaxy_Nexus_USB_Drive r_v1. 4.6.0.exe "
Provide the end user detailed instructions for manually configuring their drivers.
Driver configuration is a two step manual process:
Your device has to be configured once when its ON and again when its in BOOTLOADER
You have to manually configure these drivers through device manager.
Follow the onscreen instructions for driver configuration, or refer to post # 2 for more details.

unlock:
This will automatically:
This will unlock your device which will also inexorably factory reset your device.
Factory resting means that, ALL your user app settings and files will be erased.
So ... please take the steps necessary to preserver your important data.
I recommend backing up all your picture, music files, and such manually by just:
Plugging your device into your computer and using drag and drop to copy them over
Then use the backup feature of the toolkit to make a full backup of your apps and settings
See "backup and restore"

Root:
This will automatically:
Push su.zip (Superuser.apk) to your sdcard
Flash clockwork mod (this is specific to your device model; ie CDMA version vs. GSM version)
Provide on screen instructions for completing the rooting procedure
Launch a script which automatically enters adb shell commands to rename the file "recover-from-boot.p" to to "recover-from-boot.p.bak to ensure permanent clockwork
* If your computer says it can not find su.zip then you probably forgot to do the initial install ... do it.
* If you did do the initial install, then the problem is still related to that.
* Your su.zip along with clockwork img, all should be in the directory

Code: \ android-sdk-windows \ platform-tools

Flash Stock + Unroot:
This will automatically:
Download the latest 4.02 android release for your specific model (CDMA / LTE vs GSM / HSPA +)
Hashcheck the resulting download once it's finished to verify the files integrity. If it passes:
Extract the .tgz factory image package in the proper manner to a specific sub directory in your GnexToolkit folder
Flash the stock images to your device in a highly controlled and ordered fashion.
Allow you to bypass the download and extract phase in the future if you have already done it before
Allow you to point the program to ANY android factory image package, and let the program take care of the rest
This process also includes a user input box governed hashcheck verification step to ensure the files integrity.
Has an option to start the flashstock process from bootloader mode incase the user is bricked and can not boot ups charged first!
Flashing stock will also inexorably unroot your device.

OEM lock:
This will automatically:
Re-lock your device back to original equipment manufacture specifications.
You must use the "flash stock + unroot" feature first before being able to use this option successfully.

Backup Apps + Data:
This will automatically:
Initiate a backup of all your apps and app data
User will be prompted to enter a password on there device to protect their backup file
Once the backup is complete it will be stored on the users computer in the directory:
And the file name will automatically be generated as the date and time the backup was made
Note: this does not backup all of your SDcards contents: So its up to the end-user to backup any picture or music files they have.
This only backs up apps + app data
The user is given the option to backup system apps as well

Restore Apps + Data:
This will automatically:
Initiates a customized browse to file window which asks you to locate the android backup files (* .ab) you would like to restore
This browse to file window automatically defaults to the proper location of your backups

Code: \ android-sdk-windows \ nexusbackup
Once the user selects the backup file, the program will automatically initiate a restore operation
User will be prompted to enter the password they set in order to restore their file
When the correct password is entered the file will be restore.

Quick tools:
Provides the end user an easy one click method for rebooting their device
Rebooting their device into bootloader mode, and checking if their device is recognized.

Flash to partition:
Provides the end user an easy one click method for flashing any img file to any partition on their device
Is designed to make modding on the nexus as simple as selecting the file you wan't to flash and pressing ok
Has the option to boot img files as well, to try them out temporarily before flashing them permanently

Instructions:
Do not plug in your device until this program prompts you too!
Install the program by double clicking the GnexRootToolkit.sfx.exe
This will extract the contents to C: \ GnexRootToolkit
Place a shortcut on your Desktop
Launch the program for first use
Use the "Drivers" option to make sure all your drivers get configured properly.
This is a crucial step. Nothing else will work otherwise, so make sure your drivers are properly configured before you try doing anything else with this program.
Follow the onscreen driver instructions carefully and you should have no problems.
Use the "Backup Apps + Data" if you want to preserve your apps and settings for restoration after you unlock and root.
Then use the "Unlock" to unlock and the "Root" to root ... Tada! Enjoy your unlocked and rooted device. ^ _ ^
Then whenever you need to go back to square one just use the "Flash stock + Unroot" and "OEM lock" features.
Remember that this option can also be used if you completely brick.
This should bring you back to a fully locked stock factory state.

Version 1.3 - This program contains all the files needed to unlock and root the device receiving or return all to the drain, and re-lock the it.
You can also use this software to backup all of your applications, system applications, and data and easily retrieve them later in one click.
You can sew or download any files IMG
You can also sew any existing or future official assembly.
Do you update the device has never been easier.
And now with the latest version (1.3), you can configure the drivers automatically.
Attached fileroottool.jpg(186.49 KB)


It seems easier to have nowhere to go;)
Free translation, find the error, correct. Who wants to can and to transfer all
a source

Download Toolkit v1.3
checksums:
File size: 40.5 MB
CRC-32: 60173e80
MD4: ce769bb081167b821b02518f49cb9374
MD5: ae6dda67dc46026cd1684464137ecbc8

Post has been editedgralexon - 26.01.12, 15:36



Rep: (418)
Instructions for the firmware Android 4.0.2 (ICL53F) through ODIN
WITHOUT wipe WITHOUT rekaveri WITHOUT BUTLODERA!

So, you have decided to re-flash the phone and want to get a newer version of the official firmware.

Firmware via Odin.
Odin - a special service program with which you can install on your phone any firmware modem language pack. Including can be installed and the official firmware.
Official (and custom) firmware are of two types - single-file and trehfaylovye. I will not go into detail in their differences. I will mention only one point. If you have any unexplained problems with your phone, and you fundamentally do not like it - I beg 3 firmware file (but remember that trehfaylovaya firmware with PIT file will remove all your data from your phone). In all other cases - Single-sew safely.


You have chosen the official firmware Android 4.0.2 (ICL53F) and download it. A link at the end of the post (CF_YAKJU_ICL53F_nowipe_nobootloaders_norecovery.zip)

In order to flash a phone through Odin is necessary to make a number of preliminary actions:
- Log into the computer as an administrator.
- Set Odin on your computer.
- Disable antivirus software.

o After extracting archive with the firmware you will see a file with the extension .tar
o In the Option section Odin set jackdaws opposite points Auto Reboot and F.Reset Time. Re-Partiton do not touch!
o put the check in front of PDA. You specify the path to the unpacked file: CF_YAKJU_ICL53F_nowipe_nobootloaders_norecovery.tar
o Jackdaws opposite PIT, BOOTLOADER, PHOHE and CSC to put it is not necessary!

After setting up Odin you proceed to the next step.
- (!) Take only the original usb cable and connect it to the rear usb port on your computer.Do not connect via USB 3.0 !!!
- Turn off the phone.
- Enter the phone in download mode by simultaneously pressing Volume Down + Power button.
- Connect your phone to your computer.
- to see that ID: COM lit yellow.
- Press in Odin Start.
- Do not touch the phone until the Odin in the top left window turns green with the word PASS, and in the Message box does not appear one after the other inscriptions: RES OK !! Removed !! Completed .. All threads completed. (Succeed 1 / failed 0)
- After that, disconnect your phone and wait for the first boot, which takes longer than usual, about 3-4 minutes.

Attached Image


Attached fileOdin3_1.85.zip(198.51 KB)

CF_YAKJU_ICL53F_nowipe_nobootloaders_norecovery

Full Google release the original image can be foundhere

Post has been editedK-User - 23.02.12, 11:21
Reason for edit: link corrected, + from nabatchikoff



Rep: (418)
Unlock root Version: v2.2.1

Attached Image


There was an application called Unlock Root, which is truly impressivelist of supported smartphonesand versions of the Android OS. Perhaps today it is the most versatile tool that will be able to get root access on almost all smart phones that are released onto the market.
According to the developer, Unlock Root allows you to get on Route milestones smartphones with Android versions from 2.1 to 4.0.3.
Our Galaxy Nexus is also on the list, it is necessary that someone checked and then the tool can be added to the cap: yes2:

Apply Unlock Root is very simple.

Be sure to obtain root adb driver must be installed on your device!

1. The device needs to be translated in debug mode Usb. SETUP-application development, debugging on usb. (Settings>Applications>Development>USB Debugging).
2. Connect the device to your PC.
3. Run UnlockRoot.exe application.
4. Hit "Unlock Root".

After rebooting, your smartphone you get the system as root.

Download Unlock RootAttached fileunlockroot22_eng.rar(8.1 MB)

Hamster



Rep: (418)
Samsung Galaxy Nexus: Koush ClockworkMod Recovery with support Touchscreen beta5

I have alreadylaid outversion of Nathan and description of how to sew.
look Nowvideoby Koush

I personally like the updated version of Nathan. Videohere
Paid version is onmarket
Buttons are now generally do not need! Moving folders flick of your finger up or down to confirm the selection (or input button incl.) A stroke from left to right.
And if chirkanote right to left anywhere, then get to the main menu rekaveri. Simply super!

I gathered to you, both in adb.rar ClockworkMod file.
Who wants version of Koush, he writes on the command linecwmr_touch_beta5_maguro.img
Who liked more from Nathan, whiletouch-tuna.img

Repeat manual as a flash:

1) Download the archiveAttached fileadb.rar(17.92 MB)

unpack it into a folder, for example: \ adb
2) On the phone, turn on debug mode for USB: "Settings" ->"For Developers" tick "USB debugging"
3) Turn off the phone, connected to a PC via USB and enter the bootlader mode (we press the Volume Up + Volupe Down + Power)
(I proceed from the assumption that you have already installed the driver. If not go to the cap).
4) Do you write on a computer from the command line (in the folder where is the adb, to go to her cd c: \ adb) command:fastboot flash recovery cwmr_touch_beta5_maguro.imgorfastboot flash recovery touch-tuna.img
5) After the command press Enter. You will see a line that says writing recovery OKAY
6) Not turning off the phone to switch the volume recovery mode and are starting

The operation takes less than two minutes
Good luck

Add a hat, but then again lost

Post has been editedgralexon - 31.01.12, 20:18



Rep: (403)
Patriot500 @ 04.02.2012, 23:23*
Galaxy Nexus, as the previous Nexus S, sold not attached to the operator

As it turned out, there are versions of locked to the operator
Patriot500 @ 04.02.2012, 23:23*
With locked bootloader is like?

Glossary- Bootloader
Highlight the desired:
Bootloader allows you to change the device firmware, as well as to connect to a PC in fastboot mode.

respective locked bootloader does not allow to make changes to the firmware



Rep: (958)
to all: I recommend to save a backup copy of your IMEI, so as it turns out that he - as has happened on previous Google Phone - may well fall off on 004999010640000 at the next firmware. do the following:

1. Set the apparatus on the terminal emulator, for example,this;
2.skinte (mail, text file, url through chrome-to-phone) to the machine following command
dd if = / dev / block / platform / omap / omap_hsmmc.0 / by-name / efs of = / sdcard / my_efs_backup.img

3.skopiruyte command, open the Terminal and typesu Press enter and enable the terminal to access the superuser;
4.uderzhivayte finger on the screen of the terminal to the pop-up menu, click "Paste." execute the command by pressing the enter;
Attached Image

5. For reinsurance also copy directory/ factory together with all files (in fact, the same backup, but now we do not maintain a complete image of the hidden 20-MB partition and its specific content);
for those who do not see the directory / factory: from the computer when connected via USB can not see it. install on the device type manager fileRoot explorerand navigate to the root level of the file system "/ "

6.peremestite generated at the root of / sdcard filemy_efs_backup.img (20 Mb) + copy directory / factory on the computer, in a safe place;
You can also make a backup of efs and other system partition directly from your PC via ADB, detailshere

***

You can save nv_data.bin representing the greatest value without the root, to unlock this bottle, put rekaveri ClockworkMod, go into it, and execute the following commands from the computer:
adb shell
mount / data
exit
adb pull /data/radio/nv_data.bin c: \
The file appears in the root of drive C:

***

update: there's an easier way to save it is an image, utilityEFSBackup_v0.1from the forum xda-dev (Need r00t). After clicking on "Backup Now!" and a short wait at the root of / sdcard will be 20 MB file with a name like: efs_backup_chislomesyats.god.img
Attached Image
Attached fileEFSBackup_v0.1.apk(10.25 KB)


Post has been editedkrasnoff - 26.03.12, 13:47
Reason for editing: GUI-tulza for backup + free way to Ruta



Rep: (403)
Nezemnoi666, answer my questions - Samsung Galaxy Nexus - Firmware (Post # 11276704)
gralexon better safe than nedobdet. in the header reads " possibly change IMEI ". backup in any case will not prevent, so far failed to identify the culprit formation flying IMEI. on the Nexus S is the first was too, then fixed a



Rep: (21)
IMEI repair instructions

Incredibly, I retrieved IMEIwithout backup! Thank you very much to everyone who helped, especially the userzhsv . Without him I would not have worked.
I will try to briefly describe an exemplary algorithm. Not sure it quite accurate, because I for these 2 days have tried so many things that was going to hammer on this business. So, you need to:
Root,busybox from Market, CWM, adb (or GN toolkit), odin (maybe not necessary). Everything is done in airplane mode or without SIM cards.
The most important thing,full copy partition / factory!(Even if the woman have already flew, still make a copy) Just copy it somewhere on your PC in a safe place.
I flashed onestock firmwarewith a birdie on the EFS partition cleaning. Then I put the root, busybox and CWM. We go to the CWM, connect body via USB. Most likely, it will be defined as a strange device. We find it in Device Manager, put on his Android ADB device driver. Now you can connect via adb, when the body is in rekaveri.
At the command prompt, go to the folder where the SDK - sdk \ platform-tools \ and we write:
adb shell
setprop ril.barcode 123456789 (instead of numbers, bear that is needed)
mke2fs /dev/block/platform/omap/omap_hsmmc.0/by-name/efs
setprop ril.barcode 123456789
reboot

I do not know whether you want to, but I repeated the operation above again, but not in rekaveri, but simply enabled phone. Now the team are:
su
umount / factory
setprop ril.barcode 123456789 (instead of numbers, bear that is needed)
mke2fs /dev/block/platform/omap/omap_hsmmc.0/by-name/efs
setprop ril.barcode 123456789
reboot

After that, look, there remains something to see / factory. If there is only one folder, or nothing at all, then everything is OK. If not, then do a full wipe and sew some of rekaveri ROM (again, do not know whether, just as I did need no longer raschityvaya that IMEI will return. He would put AOKP). If / factory cleared, so all went well. Now you will not run GSM-module :) Do not worry, go to the root explorer and copy the backup / factory in its place. Reboot, and IMEI is back!

Post has been editedDimezis - 19.02.12, 23:44
Reason for editing: for hats



Rep: (21)
makcunknown
No, definitely need a backup. If I had not filled the backup back, it would have sat without radio module. I do not know exactly where and how the bear is encoded and when it changes, so if you want to, it is best to exactly replicate the algorithm described me. And not the fact that he works for not being native.



Rep: (170)
Dimezis, Congratulations on winning :)

It would be nice to work out a method, and an accurate statement, we need more volunteers with the default imeyami.

In any case, as soon as Ruth made on the machine to do backup / factory (efs, mounted as / factory) just in case. Then to not be excruciatingly painful if you make a mistake somewhere.

HaveNezemnoi666 a slightly different problem, he does the radio not working somehow even like the fact that it the device is locked by some statement or he beg something insane. His thinking would also save a backup efs.



Rep: (170)
Nezemnoi666, and what gives now here this team?
adb shell
su
getprop | grep gsm.



Rep: (403)
Nezemnoi666, before you write commands, you must first go to the folder which contains the fastboot.exe, with the command cd, eg cd c: / fastboot / or cd c: / root, if you do according to the instructions from this thread (check where you lay this file). Read the first 5 points of instructions - Samsung Galaxy Nexus - Firmware (Post # 10151677)

in instructions to return the phone to its original state it's all there. be careful!

Post has been editedlemon174 - 08.02.12, 15:02



Rep: (1533)
Goodnight.

Today I released the appAlsamixerThose who have root-rights and a desire to get the record with a line throughCallrecorderattention please.

1. Download the app
2. If not installed busybox - the program will offer to install it (to send to the market)
3. If ALSA is not installed, install it progaramma.
4. If the previous paragraphs are successful, it will display a list of all ALS devices.
5. Look for a device called "AUDUL Voice UL" / "AUDUL Voice DL" and if it is, then expose him to "111" (or any other in the area of ​​tolerance)
6. Check the entry through theCallrecorder(In the setting of record must go through the standard API, and recording all sources should be checked)
7. If something is written, that's fine. If not, then check out similar devices. Those. at random, you can chance upon entry with line :) and remembers the default values, so you could still return.
8. Have fun.

If you have any questions or suggestions - please write me an email (<my nickname is>@ Gmail.com)

Post has been editedskvalex - 12.02.12, 19:43



Rep: (958)
Undervolting (Lowering the value of the supply voltage to the CPU) in the subject, if I am not mistaken, in particular have not yet discussed, so I decided to share my thoughts on the methodology of the process by the example of my interest at the moment more than any other core Leankernel (Specifically: 1.10.0 exp2 180MHz).

Lyrics: As everyone knows, two identical production batches (and accordingly, and processors) does not exist: micron difference in the thickness of one of the many layers of silicon "sandwich", caused by a subtle difference as the widest assortment of raw materials or minor deviation from the multi-technology, can greatly affect a processor stability (including and because of this "desktop" hunt overklokery processors from specific parties specific factory). Therefore, the manufacturer (and behind him a developer) for reinsurance hold more than sufficient voltage values ​​for each of the working frequency of the processor. It follows that most users have excessive voltage ingeniously disperses into a banal heat instead work to increase battery life. Well, what if you have the same, the reference processor, easily passed all factory tests on the upper limits of quality standards, tolerances, and which need less energy medium? Well, why not check out, because the benefit is obvious.
I want to clarify that for writing this message, I took only because I myself managed to achieve visible results, and I am convinced that the other owners of the GN can also contribute to the overall reduction in energy consumption of their vehicles through more and andervoltinga. After all, the true: personally I have a voracious machine, perhaps, have not yet been, and I have had a lot. The author of these lines, and so there is a "fad" for every rational optimization, and with the advent of GN it threatens to develop into a small obsession: 0)

We will need:
- any type of CPU-TweakerVoltage controlwho knows how to set the min / max CPU frequency and voltage change (for me it's all in the section "Performance" in the embedded firmware "Rom Control");
- unique in its kind test tulzaStability Test(She is one can not only sort out the frequency of an exercise test, but also constantly changing on the fly governor!);
- not mandatory for installation, but is able to be usefulCool tool. if you see the time freezes, you can manage to understand what frequency zaliplo and even, thanks to the schedule, at which stage (when the frequency of picked up, when resetting, while working on it);
- free time (attention process is not required, but you should be able to occasionally cast an eye on the machine's display, and more often than usual to recharge it);

Search Method lowest possible voltages:
1. first of all, prior to all experiments were performed a full-Nandroid backup. if the space on the drive back to back, clear the cache before the procedure: it will reduce the overall size of nandroid-image;

2. expose constraints for system available to it (and run applications) frequencies. to accelerate and simplify the catching failures work only with a pair near each other frequencies. I started from the top down: max CPU 1200MHz, min CPU 920MHz, any Governor. the essence of this limitation is that the test mode scaling utility Stability test will be limited to only two frequencies, and will jump from one to another and changing their Governor are much more likely than if the frequency was>2.
1200-920 for the following pairs are 700-350, 350-180 (here, it is understood only nastrivaem 180). 1350MHz frequency 1420 and I have not used, so do not work at all with them;

3. starting to reduce the voltage to the first frequency of the test pair. but to start looking for, be sure to find and always used to deactivate your tweaker CPU-point "start at boot", "apply settings at boot", "to apply the settings after a reboot", etc.
important: will continue friezes / reboot, and if at the time of deep frieze (in my experience, 80-90% Friesians ~ 5-10 seconds later ends automatically reboot) the device was charged, first unplug it and then remove the battery. yes, mentally get ready to open the cover and do not rush to put it in place, the battery inside the tightly held when putting the unit carefully.
So, boldly and resolutely 75mV throw down, and then all 100mV. for example, in my config for 1200MHz frequency voltage defoltnogo = 1300mV. 1200mV set and apply the change. If Cool Tool is installed and running, look at the current frequency if there is 920MHz, so we need to somehow "move" that sprang up to 1200MHz. Task Manager, for example, run. if 1200Mhz reached and hung, so you can still reduce naprugu. returning to tweaker, we remember the current value and resets have less of 25mV. use change and repeat the simulation activity. as a result, the next time reduction (eg 1100mV) apparatus inevitably hangs, rebutnotsya (help him in this, if you want), and after loading the frieze we return the previous value (ie, if it was set in 1100 1125mV);

4. empirically testing "grope" combination frequency / voltage in the program "Stability test". program provides us with two options check: Simple Classic stability test (Governor does not change), and the right Scaling Stability Test (automatic change of available frequencies and the Governor, are moving all their possible combinations). There is also a CPU + GPU Stability test (full details), but the video we are not persecuted, and leave this regime beyond, although sedation can make it go away at the end of the procedure, along with a final test (see para. 5). Of course, we choose the "Scaling Stability Test" and chased it for 15-20 minutes. if hung / rebutnulis before the expiration of this time, well: after reboot add + 25mV and run the tests again.
before starting the test check on the spot whether to set tweaker limitation on minimum / maximum frequency.
Thus, the transition from one combination frequency / voltage to another, not forgetting the need to install a new pair of min / max (described in paragraph 2) after creation of a stable pair from near to each other frequencies. and moving: 1200-920, 700-350, 350-180;
illustration work "Scaling Stability Test"
Attached Image


5. final, the longest test: pushing the boundaries of the available frequencies within the system planned for continuous use (eg, max CPU 1200MHz, min CPU 180MHz), and run the "scaling test" commercials an hour or two. You can and should be something else to do in the testing process, further impacting the system. later and can additionally CPU + GPU Stability test (full details) drive.
and if all is well, then all is well :)

***

for example my frequency / voltage. aokp milestone.3 + Leankernel 1.10.0 exp2 180MHz and it is only with a minimum 230Mhz

1350MHz 1200mV
1200MHz 1125mV
920MHz 975mV
700MHz 900mV
350MHz 775mV
230MHz 725mV (this rate is only available in the kernel Leankernel 1.10.0 exp2 230MHz)
180MHz 700mV (this rate is only available in the kernel Leankernel 1.10.0 exp2 180MHz)

stress white with the word current - Defaulted
gray voltage to the word saved - lower
as you can see, the difference is significant! these seemingly minor microtension ineptly scattered in space.
Attached Image
Attached Image


perhaps something else Play around / Correct, but in general it seems to limit specific to my machine.

update: I added stress to 1350MHz. still I try and use the same frequency.


Important notes:
- If all this sounds complicated, try to start small: to optimize only one, for example, the highest frequency on your machine. Well, after you require (in order to ensure efficiency of the system) time, proceed to the rest of the frequencies;
- share, please their experimentally obtained data frequencies and voltages! indicating the firmware and kernel is in the message, because when delayed viewing your signature may already be another;
- do not make more than one voltage changes at a time. proceed to the next only after full confidence in the stability of the previously entered values;
- scaling test try to spend longer, at least 20 minutes per amendment made to the table of voltages. for themselves after working hard, and repeated tests may take more time;
- do not look for a linear dependence with the results of other users, consider them as an approximate reference point;
- that there was no doubt about the usefulness of doing, remember: the ones of 10-15 and even 20% energy savings by about the same percentage (screen factor reduces these numbers) will increase battery life. those. at least an hour longer than usual whenintenseusing the device worked. consider that it is a programmatic way to increase the battery capacity;
- do not worry, if your machine does not allow to significantly reduce the stress, at least you will have no reason to reproach myself for inaction, you will know your machine capacity limits will gain experience that will be useful when setting up the future of mobile devices;
- there are already applied to the kernel developer andervoltingom, but they, too, can and must adjust to a processor;
- all above inscribed never the ultimate truth, but only my opinion. criticism and refinement willingly accepted. It would be very interesting to exchange experiences on the subtleties hidden from me andervoltinga with knowledgeable people;


update: The answer to the question: "Is there any benefit from andervoltinga?"

Post has been editedkrasnoff - 28.02.12, 12:01



Rep: (8)
SMS not sent - decided

Faced with this problem after another flashing.

It turned out that the SMS service center processing (SMSC) loss and it can not be updated or request a room with an operator.
After a brief search in the internet and tests found a solution:
1. go to the radio settings: * # * # 4636 # * # *
2. See "Phone Information" in line SMSC: __________ click on the "Update"
3. If the field is filled with the type code: 07917710002025f5, then everything's okay, and after pressing the button next to "Update" you can go. Everything will work.
4. If it does not (returns "00") or after manual input of an operator center code gives the error "update error", then go to step 5
The fact that the SMSC enter direct telephone operator will not work. Galaxy Nexus will not accept a phone number, it needs special code (the one that, in paragraph 3)

5. take out the sim card, insert into any other phone (I usedHTC Sensation). Solicit or enter the SMS service center number manually. Save.
6. When you return back to the Sims Galaxy Nexus will work.



Rep: (4)
Sim Unlock Galaxy Nexus

To unlock, you will need to have root on your phone and connect it to the PC in developer mode so that you work remotely command line (infa about how to install drivers and the like to be in the header).
Just maybe, we need the BusyBox, the application is placed from the Market and installed by default. (The fact that it is necessary, I'm not sure, but I think the team that yuzayutsya in the patch, require his presence.)
Take the patch (this is the text that you want to push in txt, and change the extension to .bat) me there a line related to the ADB:
set sdk = "c: \ Program Files \ Android \ android-sdk \ platform-tools \ adb.exe"
on that where you have it or do it empty and run from the folder with the ADB).

text patch
title Galaxy Nexus GSM Unlock

pause
cls

REM set your path to adb.exe here
set sdk = "c: \ Program Files \ Android \ android-sdk \ platform-tools \ adb.exe"
echo using adb.exe:% sdk%

echo basic pretasks:
% Sdk% root

% Sdk% shell su -c "mount -oremount, rw / dev / block / mtdblock3 / system"
% Sdk% shell su -c "mount -oremount, rw / dev / block / mtdblock3 / mnt / sdcard"
% Sdk% shell su -c "mount -oremount, rw / dev / block / mtdblock3 / factory"
% Sdk% shell su -c "mount -oremount, rw / dev / block / mtdblock3 / data"
% Sdk% shell su -c "mount -oremount, rw / dev / block / mtdblock3 /"
% Sdk% shell su -c "chmod 777 / data"
% Sdk% shell su -c "chmod 777 /factory/nv.log"
% Sdk% shell su -c "chmod 777 /factory/nv_data.bin"
% Sdk% shell su -c "chmod 777 /factory/nv_data.bin.md5"
% Sdk% shell su -c "chmod 777 /data/radio/nv_data.bin.md5"
% Sdk% shell su -c "chmod 777 /data/radio/nv_data.bin"
% Sdk% shell su -c "rm / tmp00"
% Sdk% shell su -c "rm / tmpff"
% Sdk% shell su -c "rm / data1"
% Sdk% shell su -c "rm / data2"
% Sdk% shell su -c "rm / data3"
% Sdk% shell su -c "rm /mnt/sdcard/nv_data_mod/unlock/nv_data.bin"
% Sdk% shell su -c "rm /mnt/sdcard/nv_data_mod/unlock/nv_data.bin.md5"

PAUSE

echo unlocking:

% Sdk% shell su -c "echo 'SC-04D nv_data.bin backup + sim unlock'"
% Sdk% shell su -c "mkdir / mnt / sdcard / nv_data_mod /"
% Sdk% shell su -c "mkdir / mnt / sdcard / nv_data_mod / factory"
% Sdk% shell su -c "mkdir / mnt / sdcard / nv_data_mod / unlock"
% Sdk% shell su -c "mkdir / data / radio"
% Sdk% shell su -c "cp /factory/nv_data.bin /mnt/sdcard/nv_data_mod/factory/nv_data.bin"
% Sdk% shell su -c "cp /factory/nv_data.bin.md5 /mnt/sdcard/nv_data_mod/factory/nv_data.bin.md5"
% Sdk% shell su -c "cd / mnt / sdcard / nv_data_mod /"
% Sdk% shell su -c "echo -en \\ x00> tmp00"
% Sdk% shell su -c "dd if =. / Factory / nv_data.bin of =. / Tmpff bs = 1 count = 30 skip = 16"
% Sdk% shell su -c "dd if =. / Factory / nv_data.bin of =. / Data1 bs = 1 count = 1,572,969"
% Sdk% shell su -c "dd if =. / Factory / nv_data.bin of =. / Data2 bs = 1 skip = 1572999 count = 5090"
% Sdk% shell su -c "dd if =. / Factory / nv_data.bin of =. / Data3 bs = 1 skip = 1578090"
% Sdk% shell su -c "cat data1 tmpff data2 tmp00 data3> /mnt/sdcard/nv_data_mod/unlock/nv_data.bin"
% Sdk% shell su -c "md5sum /mnt/sdcard/nv_data_mod/unlock/nv_data.bin | tr '\ n' 'X' | sed 's / * //'> / mnt / sdcard / nv_data_mod / unlock /. nv_data.bin.md5 "
% Sdk% shell su -c "od -x ./factory/nv_data.bin> factory.dmp"
% Sdk% shell su -c "od -x /mnt/sdcard/nv_data_mod/unlock/nv_data.bin> unlock.dmp"

% Sdk% shell su -c "rm /factory/nv_data.bin"
% Sdk% shell su -c "rm /factory/nv_data.bin.md5"
% Sdk% shell su -c "rm /data/radio/nv_data.bin"
% Sdk% shell su -c "rm /data/radio/nv_data.md5"
% Sdk% shell su -c "rm /data/radio/nv_data.bin.md5"
% Sdk% shell su -c "rm / tmp00"
% Sdk% shell su -c "rm / tmpff"
% Sdk% shell su -c "rm / data1"
% Sdk% shell su -c "rm / data2"
% Sdk% shell su -c "rm / data3"

% Sdk% shell su -c "cp /mnt/sdcard/nv_data_mod/unlock/nv_data.bin /factory/nv_data.bin"
% Sdk% shell su -c "cp /mnt/sdcard/nv_data_mod/unlock/nv_data.bin.md5 /factory/nv_data.bin.md5"
% Sdk% shell su -c "cp /mnt/sdcard/nv_data_mod/unlock/nv_data.bin /data/radio/nv_data.bin"
% Sdk% shell su -c "cp /mnt/sdcard/nv_data_mod/unlock/nv_data.bin.md5 /data/radio/nv_data.bin.md5"

% Sdk% shell su -c "chmod 777 /factory/nv.log"
% Sdk% shell su -c "chmod 777 /factory/nv_data.bin"
% Sdk% shell su -c "chmod 777 /factory/nv_data.bin.md5"
% Sdk% shell su -c "chmod 777 /data/radio/nv_data.bin.md5"
% Sdk% shell su -c "chmod 777 /data/radio/nv_data.bin"

echo press any key to reboot
PAUSE

% Sdk% shell su -c "reboot"

EXIT

The first discussions on this topic, I saw another Japanese site, the exact roots are not known.
The original information is taken from threadxda-developers.

For newer firmware I recommend using FuxkDocomoV3.1

Post has been editedShadow_Alexey - 15.09.12, 14:30
Reason for editing: design



Rep: (958)
This guide is written for those who have decided to:
To make the his first step away from the "factory firmware"
Change of supplier for updates
yakju
Return the unit to the factory state (required if you go to the SC)
Manually upgrade to a full official image


To do this, you must have correctly installedadb / fb-driver and utilities Fastboot (description) and Adb (description) .
In the future, using the command line, you can easily make with your device for other instructionsanything you want .
Despite the apparent complexity of the (work with the command line), it is the method recommended by Google and appears in all instructions for working with Android-devices. By the way, and do not need to print anything: highlight a line of manual commands with the mouse, copy it to the clipboard, insert a command prompt and press Enter. You will be amazed how this really easy.


Installation instructions adb / fb-driver and utility fastboot
We will need:


Step one: Moving a file driver_and_fastboot_for_GN.zip the root of the C: drive and unpack it so
without accruing any nested one into another folder:
Attached Image
At the C: drive directory should appearAndroidc located insidedriverandtools.

Step two: Turn off the device, connect it to the USB-port of the computer cable and without delay stifle simultaneously three buttons: volume up, volume down and power button. If you did everything correctly, you'll see lying on his back under the inscription "Start" droid
Attached Image
Also in the bottom row should appear with the word "Fastboot" (in the photo it does not exist).

Almost immediately, Windows will notify you of the discovery of a new device; without paying attention to it, go to the device manager (usually just right-click on "(My) Computer" ->Properties ->Device Manager) is in the "another device" "Unknown device" (or "Android 1.0") c exclamation mark in a yellow triangle, and double-click on it:
Attached Image

Click "Update Driver", abandon the search for the network and select a local search for the driver, sending it to the directory C: \ Android \ drivers and allowing to look in the folder:
Attached Image

If the warning "Windows Security (failed to verify the publisher)" appears ->Anyway to install the driver. As a result, the computer disk poshurshat notify us of a successful installation:
Attached Image


Step Three: .Otkryvaem command line. To do this, click "Start" in the search bar we collect cmd And run the file found cmd . WinXP users gain cmd in the "Run" and shake Enter
Attached Image

Open friendly vzmargivayuschee cursor black small window in which we write in English letters:cd c: \ android \ tools and press Enter (cd - abbreviation c hange d irectory):
Attached Image

We were in the directory where it isfastboot.exe Now we see that we have done everything correctly and that the device is available. To do this, enter the command, which will show the connected devices - fastboot devices and we see the following:
Attached Image

If, instead, we see "waiting for devices ..." or something like that, there's a good reason to reboot / reconnect the device correctly (three buttonsafterconnection to USB-port) / not remember whether there were alternate versions of previously installed drivers.

Congratulations! You have just done, in fact, the biggest and most difficult job. In the future, from the third step, start all operations that can be performed through fastboot.

Note:
- GN driver besides supporting other samsungi, HTC, ASUS tablets;
- everything written above was done on a "clean" computer (on which there was nothing having to do with Android and Samsung) specifically for the creation of this manual



Unlocking the bootloader, custom rekaveri, root
Thus, the device is connected in fastboot mode and-found (serial number responds to the command:
fastboot devices
We continue to improve.

Bootloader unlocking (Also known as bootloader, it also bottles).
This is a necessary action for setting of a custom function rekaveri ClockWorkMod and custom ROMs.
Attention! This operation resets guglofon to factory settings fully clearing the contents of its memory. Temporarily move your content to a PC.
We type in the command line (or copy / paste):
fastboot oem unlock
Reaffirm their actions are consistent volume / power buttons. On the next reboot to see the symbol of "half-open lock" in the bottom of the screen, then it's done: bottle unlocked.
Go ahead: Do not disconnect the cable, and after the first load detection system and MTP-device, open it in Windows Explorer, create a directory on the drive with a name like:! _AaAaA(Hereinafter will be very easy to quickly get into it from rekaveri) and save it in a file with the selected custom firmware + file with Gapps (from Google applications on custom bikes usually come separately).

Installing custom rekaveri and ROM'a
For information: established at this stage without root-rights rekaveri disposable, ie fly off at the next reboot. That's why we and useful prudently saved on the device with custom firmware files and GAPPS.
Download the file of a custom rekaveri:Attached filerecovery-clockwork-6.0.2.3-maguro.img(5.85 MB)

Connect the device in fastboot mode, move the downloaded file to the directory rekaveric: \ android \ tools, Rename it for ease ofrecovery.imgand type (or copy / paste) command:
fastboot flash recovery recovery.img

Quickly will fly on the information sent to the data unit, and we're not resetting the unit set custom firmware, which leaf through the volume buttons until "Recovery mode", press the power button, wait a bit, then "install zip from sdcard" ->"Choose zip from sdcard" - select the desired file, confirm a selection, it is expected immediately without leaving the catalog file is stitched with "gapps", ->Go Back, reboot.

Obtaining rights "superuser" (root, su,) Note:Almost all custom bikes already rutovany!
For version 4.2.2 of the official ROM necessaryAttached fileSuperSU_1.25_Pro_CWM.zip(1 MB)
We already sewn delivered through CWM. For version 4.3 or older to sew Super SU is not lower than 1.51 (Spoiler "firmware" - "Ruth")
Custom rekaveri fly down the drain, but it (having Root) can be set later by ROM Manager or even locally from the unit (via a terminal emulator)deciding his disappearance so



Change to update supplieryakju/ Return to the factory 4.2.2 / manual update on the full image 4.2.2, root, lock
Introduction:For this tutorial I'm assuming that you already have a properly installed ADB-driver and utility of the Android SDK (described above in the first part), personal data stored on a computer and unlock the boot loader (see. above at the beginning of the second part).

Q: Do I change the update supplieryakju/ Return unit to factory condition with ROM drive 4.2.2 / manually upgrade to the full image 4.2.2
A: If you have not unlocked bootloader do it now with:fastboot oem unlock
We see this request, Choose the Yes button (all data will be lost ). Reboot and re-enter the bottle.
1.Perehodim onpage full of images of the firmware for guglofonovand in the section "Factory Images" yakju "for Galaxy Nexus" maguro "(GSM / HSPA +)" download the image of version 4.2.2 (JDQ39) entitled,yakju-jdq39-factory-b2ebb5f3.tgz
Attached Image

2.Raspakovyvaem archive folders inside C: \ Android \ tools so that all five files were close to the utility fastboot.exe
Attached Image

3. In the Windows command prompt, write (to accelerate recommend select, copy and paste commands, right-click), pressing Enter after each command and waiting for its execution:
cd c: \ android \ tools
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlj1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-jdq39.zip

Actually, that's all. Screen all uncomplicated process:
Attached Image


Q: Do I get Ruth (I recommend to get it, even if until it seems unnecessary. installed but inactive Ruth contrary to popular myth is completely harmless)
A:
Download fileAttached fileSuperSU_1.25_Pro_CWM.zip(1 MB)
and place it in the / sdcard
PutAttached filerecovery-clockwork-6.0.2.3-maguro.img(5.85 MB)
in one directory with fastboot.exe (already downloaded it), enter the device in bootloader again, and execute the command:
fastboot boot recovery-clockwork-touch-6.0.2.3-maguro.img

At one time boot ClockworkMod custom rekaveri, which act as: mounts and storage ->mount / system ->Go back
install zip from sdcard - choose zip from sdcard (specify the path to SuperSU _..._ Pro_CWM.zip) - yes / install - Go Back - reboot system now

Q: Do I lock the bootloader back
A: cnova enter it, including a three-button device, and perform a single command:
fastboot oem lock

Attached Image


Post has been editedshuric164 - 25.07.14, 15:23
Reason for editing: manual adjustment



Rep: (958)
cherh @ 20.02.2012, 09:56*
There is a description how to make a backup, but there is no description as to restore it.

based on the logic of command parametersdd enough swap i nput f ile<-> o utput f ile
those. for the backup command:
dd if = / dev / block / platform / omap / omap_hsmmc.0 / by-name / efs of = / sdcard / my_efs_backup.img

to the restaurant:
dd if = / sdcard / my_efs_backup.img of = / dev / block / platform / omap / omap_hsmmc.0 / by-name / efs

I would experiment conducted offline, with a checked Simcoe and pre-jammed / move files from the directory / factory so that it was possible to visually see the positive results of the command.

upd: opened properties efs on the way /dev/block/platform/omap/omap_hsmmc.0/by-name/efs and found that such a long way just a link to the / dev / block / mmcblk0p3 :
Attached Image

those. Now this team is more correct, KMK (taken from a topic about SGS2 and tweaked)
to the restaurant:
dd if = / sdcard / my_efs_backup.img of = / dev / block / mmcblk0p3 bs = 4096

Oh, and for the backup command can also be shortened

***

to all: prog author ktool He turned his gaze on GN, so that soon the backup / resto will be easier

Post has been editedkrasnoff - 20.02.12, 12:28



Rep: (958)
anFo @ 20.02.2012, 16:47*
I looked for explanations of items values ​​at the core governor leankernel on the forum, but did not find. Who can explain their meanings?
Let's try to explain only the wording of the question a bit vague. What kind of items do not understand?
description leankernel
FEATURES
Patched to latest in Linux 3.0.x branch: 3.0.20, which was released 2/6/12 (lots of new / updated kernel code).
All unnecessary kernel components removed to make kernel lean and fast!
OC to 1.35Ghz (Michael Huang, optimized by me). Boot speed is maxed at 1.2ghz within kernel (in addition to ramdisk) for stability.
GPU overclock to 384mhz and undervolted.
User voltage control (Michael Huang, fixed and enhanced by me).
InteractiveX V2 (screen-off hotplug of cpu1) added. Select it using setcpu if you want to use it.
Ramdisk tweaks (sysctl, vm, filesystem speed, etc.)
SWAP & zram (next generation compcache) support. Run "zram enable" in terminal.
init.d support in ramdisk.
HotplugX governor (Hotplug optimized and modified for screen-off suspend).
cpufreq backport from Linux 3.3
rcu code backport from Linux 3.3
other linux 3.2 / 3.3 backports: dm, futex, voltage regulator, memory compaction, etc.
Undervolted by default (1.35ghz / 1325, 1.2ghz / 1300, 920mhz / 1250, 700mhz / 1150, 350mhz / 950)
Experimental version features (in addition to stable build):
Two extra slots (180mhz or 230mhz) and 1.42Ghz. (These slots will not work for everyone - USE AT OWN RISK)
ColorControl from Ezekeel
PerformanceX, ConservativeX
lkflash - script to flash latest versions of leanKernel from Terminal (type "su" without quotes, hit enter, then type "lkflash" without quotes and then hit enter)
checkv - voltage checking script - detailed at bottom of this post.

If a question by the Governor, the Russian Internet information about their many differences, if briefly, Governor - a processor operation control profiles with a different slant. Specifically leankernel recommend using the modified kernel creatorhotplugx (It actively suppresses the second core at the slightest hint of failure to act is not particularly tupya while even 180MGts).

upd: rutzviki to have two threads about leankernel: in a branch of thecdma-versionandgsm-version GN. more lively first (although there were no differences in the core is not just in the states of cdma-shnyh owners more), if to search messages by author, you can find a lot of interesting things: it very well and everything is clear explains, even with a weak knowledge of the angelic ( like me) almost everything is clear immediately.

upd2: indicative voltage for 2.1.0 stable: 350MHz - 725mV, 700MHz - 875mV, 920MHz - 975 mV, 1200MHz - 1125mV
1350MHz is not regulated (some mistake in the implementation of UV: able to put 600mV).
because of the small difference between the voltages of 180/230 and 350 decided to sit for a while on stable
reference values ​​for UV keankernel 2.1.0 stable
Attached Image


Post has been editedkrasnoff - 21.02.12, 07:30
Reason for editing: UV stress


Full version    

Help     rules

Time is now: 17/05/20, 10:14