Related
This guide is for you that have a new Xoom (WiFi only, US model) with Android 3.1 and want to
- get root access
- enable the external SD card unit
Please note that Android 3.2, which now is available for the US Wifi models, make this guide more or less obsolete. If your aim is to have root access, then there are probably simpler methods.
What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and dont try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned!
I strongly recommend you to read the entire guide before trying this. In fact, read it twice to ensure that you have understood everything. If there is wierd stuff that you dont understand, dont hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but noone (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
If someone else adapts this guide for the EU model or the 3G model, feel free to drop me an IM and I will update the guide for these devices too. Until then, this has only been tested on a WiFi only, 32 GB device bought in the US. If you brick your 3G or EU bought model, dont call me ...
0. Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity)
2. Install Java SDK and Android SDK tools (for adb and fastboot commands)
3. Unlock the device for flashing (allowing replacement of recovery and boot images)
4. Install a modified recovery image (ClockWorkMod recovery for Android)
5. Root the device (Allow r/w access to the device filesystem)
6. Flash a kernel that supports the SD card (SD card access, overclocking etc.)
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows XP x86 SP3. Windows 7, Mac and Linux users will probably have to do some steps differently.
Update July 7: I have tested the procedure on Windows 7 x86 now and the procedure is identical to Windows XP.
1. Install the latest Motorola USB drivers
The installation file can be found here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2. Installation of development software
Java SDK 6 and Android SDK (for Honeycomb at least) need to be installed. You can find the installation kits here.
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
http://developer.android.com/sdk/index.html
2.1 Install them as any other software.
2.2 What I had to do was to manually modify the PATH environment variable. I use Windows XP so I did that by right clicking on My Computer, choose Properties and select Advanced. Here I added the path to platform-tools and Tools
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\QuickTime\QTSystem\;D:\Java\Android-sdk\platform-tools;D:\Java\Android-sdk\tools
Note: If the Android SDK complains that the Java Dev Kit cant be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
2.3 Test that ADB and FASTBOOT works. You should open a command window and go to your Android installation directory. Plug in your Xoom to your computer and write 'adb devices'. Your Xoom should now be listed like this
C:\Documents and Settings\Anders>adb devices
List of devices attached
0288414343813157 device
Did your device not show up? Make sure that you have USB debugging enabled in Settings / Applications / Development
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to rescure important data before you start.
3.1 Power up and start the Xoom
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'My Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal, but now ready for step 4
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
4.1 Boot into flash mode with 'adb reboot bootloader'
4.2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
4.3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.4 Enter CWM with the following procedure
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. There are ways to prevent this (see posts below), but I recommend you to redo step 4 instead of messing with removal of system files. But both methods would probably work. Experiment!
5. Rooting the Xoom
The root zip file is located here
5.1 You need to transfer the ROOT zip file to a working micro SD card. You can do this on a computer or cell phone, but the ROOT zip must be located in the root directory of the SD card.
5.2 Insert the now prepared SD card in the Xoom
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option
5.4 Select 'Install ZIP from sd card'
5.5 Select 'Choose ZIP'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install the ROM Manager app and start it. If the rooting was successful, then ROM Manager should start without any complaints.
6. Flashing a new kernel that supports SD cards (and maybe more ...)
The kernel that I used is described here http://forum.xda-developers.com/showthread.php?t=978013
The kernel zip file is located here
6.1 This step is identical to 5, but swap the ROOT zip towards the KERNEL zip. For simplicity, you may want to prepare the SD card with both zip files at the same time in step 5.1 ...
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
okantomi said:
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Click to expand...
Click to collapse
Of course, done
juDGEY2k10 said:
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
Click to expand...
Click to collapse
This is only tested on a US device. OP updated.
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
When you unlock your Xoom, it will wipe all user data.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
You're right. I rooted 1st and flashed CWR later. I then used brd's method to update to 3.1, re-root and flash the new bootloader and kernel. So there is a step missing after Step 3. I'm sorry, I don't remember exactly how to do this from HC 3.1. (meaning what files to use) as I was on HC 3.0 at the time.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
Yes it will. Read 3.4 again, it will do factory reset.
The root file may vary from case to case, but the procedure is the same AFAIK. I used the one that "charge light off"... There are probably others too.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
This is true, and I will update the OP to reflect that.
So has anyone followed this guide successfully yet? I don't really want to be the first...
yordikins said:
So has anyone followed this guide successfully yet? I don't really want to be the first...
Click to expand...
Click to collapse
Hi
I did!. And you know that someone gotta be first (actually second). Why not take the credit?
pingvinen said:
This is true, and I will update the OP to reflect that.
Click to expand...
Click to collapse
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Abracastabya said:
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
cam30era said:
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
Click to expand...
Click to collapse
Sounds good and thanks B-)
Sent from my Xoom using XDA Premium App
Tnx . Very help full .
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
rmcsc said:
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
Click to expand...
Click to collapse
Try again, and remember that timing (3 seconds) are key to success ...
I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.
I'll update in a few. Thanks!
Sent from my T-Mobile G2 using Tapatalk
Okai right now im on Cyanogenmod 7 android version 2.3.7
along with the kernelsystem 2.6.32.9-FPX
MOD version CyanogenMod-7.2.3-RC0-xperiaPlay-R800i-Kang
And i rly wanna get some ice cream on but im not sure how to do it.
do i need to flash some kind of stock rom on first or how do i porgress ?
If sone kind soule would take the time to write a short step by step guide i would be happy
my bootloader are ofcause unlocked.
i have Android SDK installed on the PC. along with ADB and drivers
i have FlashTool installed.
Thanks in advanced.
nyvang101 said:
Okai right now im on Cyanogenmod 7 android version 2.3.7
along with the kernelsystem 2.6.32.9-FPX
MOD version CyanogenMod-7.2.3-RC0-xperiaPlay-R800i-Kang
And i rly wanna get some ice cream on but im not sure how to do it.
do i need to flash some kind of stock rom on first or how do i porgress ?
If sone kind soule would take the time to write a short step by step guide i would be happy
my bootloader are ofcause unlocked.
i have Android SDK installed on the PC. along with ADB and drivers
i have FlashTool installed.
Thanks in advanced.
Click to expand...
Click to collapse
At the moment the best ICS ROM is probably DarkForest. The thread for this has a pretty good little guide on how to install.
Apparently you need to flash the official ICS beta from Sony's site as a base then you can flash any ICS kernel (e.g. DoomLord) and Flash DarkForest through recovery. Worked for me and the ROM is pretty much flawless. Hope this helped!
are wifi and 3G working ?
nyvang101 said:
are wifi and 3G working ?
Click to expand...
Click to collapse
Are you GSM or CDMA? GSM - Yes to both. CDMA - Yes to wifi, no to 3G
I went straight from CM7 to CM9 without any problems. I did (ofc) flash the CM9 kernel.
ridder215215 said:
I went straight from CM7 to CM9 without any problems. I did (ofc) flash the CM9 kernel.
Click to expand...
Click to collapse
True, but CM9 and ICS are two different beasts.
Sent from my R800x using XDA
netizenmt said:
True, but CM9 and ICS are two different beasts.
Sent from my R800x using XDA
Click to expand...
Click to collapse
If you want to get technical, CM9 is based on ICS. The newest version is based on 4.0.4, which is Google's latest. Sony's ICS would be comparable to CM9, in that it's a modified version of the AOSP. So, yeah, CM9 is the most stable version of ICS available for the R800 line. Just not the official version.
I'll try to make a step by step tutorial. I only know it for CM9, but as lightningdude said, it's probably the most stable ROM.
1. Make sure you have all the drivers installed, and have an usb cable, port and your phone near you.
2. Download the CM9 rom from this thread: http://forum.xda-developers.com/showthread.php?t=1447542
3. Open (don't extract!) it with WinRAR or your program of choice. Copy the boot.img to the folder your fastboot.exe is in. Then, put the zip file on your phones memory card.
3.5 (optional) Also download the gapps and put it on your memory card. This is google play, maps etc.
4. Put your phone in fastboot mode (hold the search key while connecting it to your pc using the usb cable. The notification light should light up blue. When it's blue, you can release the search key.
5. I assume you have Windows Vista or 7. If you do, shift-click on a empty place in your fastboot folder and click "open command prompt here" or something similar.
6. Flash the kernel using this command: fastboot -i 0xfce flash boot boot.img
7. Reboot the phone using this command: fastboot -i 0xfce reboot
8. While the phone is rebooting, spam the volume down key. You will now go into CWM recovery. Use the volume keys to navigate, and the home key to select.
9. Press wipe data/factory reset. After that, also wipe your cache.
10. Select "install zip from sdcard", then "choose zip from sdcard". Navigate to the zip you put on the sdcard during step 3. It will now install the rom.
11. (optional) Also install the gapps, same way as the rom itself.
12. After you finished installing, press reboot system now, and it will boot CM9.
If I made any mistakes, please let me know.
I am not responsible for any bricked phones, broken GPU's, force-closes and killed pets.
If this helped you, I would appreciate a "thanks".
Good luck!
ridder215215 said:
I'll try to make a step by step tutorial. I only know it for CM9, but as lightningdude said, it's probably the most stable ROM.
1. Make sure you have all the drivers installed, and have an usb cable, port and your phone near you.
2. Download the CM9 rom from this thread: http://forum.xda-developers.com/showthread.php?t=1447542
3. Open (don't extract!) it with WinRAR or your program of choice. Copy the boot.img to the folder your fastboot.exe is in. Then, put the zip file on your phones memory card.
3.5 (optional) Also download the gapps and put it on your memory card. This is google play, maps etc.
4. Put your phone in fastboot mode (hold the search key while connecting it to your pc using the usb cable. The notification light should light up blue. When it's blue, you can release the search key.
5. I assume you have Windows Vista or 7. If you do, shift-click on a empty place in your fastboot folder and click "open command promt here" or something similar.
6. Flash the kernel using this command: fastboot -i 0xfce flash boot boot.img
7. Reboot the phone using this command: fastboot -i 0xfce reboot
8. While the phone is rebooting, spam the volume down key. You will now go into CWM recovery. Use the volume keys to navigate, and the home key to select.
9. Press wipe data/factory reset. After that, also wipe your cache.
10. Select "install zip from sdcard", then "choose zip from sdcard". Navigate to the zip you put on the sdcard during step 3. It will now install the rom.
11. (optional) Also install the gapps, same way as the rom itself.
12. After you finished installing, press reboot system now, and it will boot CM9.
If I made any mistakes, please let me know.
I am not responsible for any bricked phones, broken GPU's, force-closes and killed pets.
If this helped you, I would appreciate a "thanks".
Good luck!
Click to expand...
Click to collapse
You helped a lot with my installation of CM7 thanks! I went from generic stock to cm7. A question if I may, do I need to do anything with the baseband? It's says "8x55A-AAABQMAZM-203028D-56" right now.
3dawg said:
You helped a lot with my installation of CM7 thanks! I went from generic stock to cm7. A question if I may, do I need to do anything with the baseband? It's says "8x55A-AAABQMAZM-203028D-56" right now.
Click to expand...
Click to collapse
Not on CM7, or CM9. At least not for me. I have the same
ridder215215 said:
Not on CM7, or CM9. At least not for me. I have the same
Click to expand...
Click to collapse
Thank you.
When i boot everything works fine. im asked to put in my pin i do so and another screen comes up asking for pin to unlock network. and when i plug my pin it fails. is that due to the baseband version ?. shuld i have flashed 113 and not 115 ?
i got no network on my phone. and yes its a GSM version
nyvang101 said:
When i boot everything works fine. im asked to put in my pin i do so and another screen comes up asking for pin to unlock network. and when i plug my pin it fails. is that due to the baseband version ?. shuld i have flashed 113 and not 115 ?
i got no network on my phone. and yes its a GSM version
Click to expand...
Click to collapse
115 should be fine, but I never had to enter a pin for my phone (gsm too). Maybe someone with the same carrier as you knows.
EDIT: November 14, 2012: As of today this is applicable to all three versions of the Galaxy Nexus: maguro (GSM/HSPA) and toro (Verizon CDMA/LTE) and toroplus (Sprint CDMA/LTE). I have also updated the adb and fastboot files to the latest versions as of today.
I have created this thread to give a step-by-step on how to flash the latest yakju/takju (or mysid for toro users) build available on Google's developer site. (These are full ROMs. See this thread for updating to latest OTA build using incremental updates.)
This method works for earlier builds as well, and is essentially a "return-to-stock" method.
You can easily convert ANY GSM/HSPA (i.e., maguro) device to stock yakju (or takju) from any non-yakju build (yakjuxw, yakjuxs, yakjuux, yakjusc, yakjuzs, yakjudv, yakjukr, yakjujp, yakjuxe, etc.).
For toro and toroplus devices (i.e., Verizon and Sprint devices), this will return your device to stock.
I will no longer be be providing support in the previous thread here, as it has over 1,000 replies and a lot of confusing information/misinformation.
Note: There are other methods that are abbreviated and/or faster, but I wanted to spell out each step in the process for the purposes of learning. I'm a big believer in doing things manually before using a "toolkit", much the same way that, in school, we are taught to do math first, before being allowed to use a calculator. I will continually add to this post to make it clearer as we go along.
So, without further ado:
How to flash yakju/takju on your GSM/HSPA Galaxy Nexus (or how to flash mysid on your Verison CDMA/LTE Galaxy Nexus and mysidpr on your Sprint CDMA/LTE Galaxy Nexus)
Step-by-step
Notes:
1) For the n00bs: read the entire post before proceeding;
2) This method is EXACTLY the same as a "return to stock" method. If you follow this (including the optional steps in part D), you will be fully stock.
3) yakju is a generic build, meaning no specific localizations. There are reports that yakju does NOT contain certain dictionaries (such as Norwegian, Swedish, Danish, and possible others). So, if you currently have these dictionaries, and want to keep them, do not flash yakju or takju.
4) MacOS-specific instructions: a) replace fastboot in the steps below with ./fastboot-mac and b) no drivers required.
A. Install the drivers
1) Do not install the Samsung drivers or the pdanet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
2) Download the drivers from here;
3) Install the drivers. This step is the only part of the entire process that is not easy to explain, and may cause users some issues, depending on what drivers they had installed previously, what OS they are using, etc. etc. Bourne-nolonger has put together a very detailed step-by-step on how to install them. If you don't know how to install them, have a look at his post here. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). If you are using Windows 8, you will need to do this before installing the drivers.
B. Backup your data
1) Backup all your personal data (e.g., photos, music, etc.) OFF of your device and onto your computer by using whatever method you want that works for you, e.g., MTP, ADB, email, Dropbox, Box.net, whatever.
2) This method will wipe your entire device, including the /sdcard folder, so once you do this, you will not be able to retreive anything that was on your device previously.
3) Once you have backed up your data, you may want to back up your current build (not required). If so, follow the instructions in this thread.
C. Download the required files to your computer and extract them
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the platform-tools-v16.zip attachment from this post and extract the contents to the directory created in step 1.
3) Download the version of Android you want from here. So, let's say you want the yakju JRO03C image, go to the JRO03C link that is under the heading Factory Images "yakju" for Galaxy Nexus "maguro" (GSM/HSPA+). Older versions are no longer available on that site; however, oldblue910 has provided a mirror on his site: Random Phantasmagoria.
4) Download the appropriate version (for your computer) of 7-zip from here and install it.
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files (or seven for toro and toroplus devices) ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
7) Reboot your device into bootloader mode (by turning it off, hold volume up and volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located) and do the following:
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot (not required if you did not do step 5): fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-maguro-i9250xxla02.img (or whatever the name is of the radio image that you downloaded).
8) Reboot (not required if you did not do step 7): fastboot reboot-bootloader
8a) Verizon and Sprint devices only -- flash the LTE radio: fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (or whatever the name is of the radio image that you downloaded).
8b) Verizon and Sprint devices only -- reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 5 below for optional items.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
E. Optional -- Root
1) After finishing this process, if you want to root, see here.
Notes on optional items and other issues:
1) This note is NOT for n00bs. To be on a "yakju" (or takju) build, all you need is the system and data images. If you want to flash the newer bootloader, radio, kernel (boot image) or recovery, go ahead. If you want to flash a different ones go right ahead, that is fine also.
2) Yes, you will receive the OTA update notification (when it is available) for the next update, regardless of which bootloader, radio, kernel or recovery you are running.
3) BUT, being on yakju or takju does NOT mean you will get the OTA notification immediately when it is announced/available. It could still take minutes or months (yes, months) following the first person who got it, before you get it. The advantage of yakju and takju , is that the updates are available before the other builds, so you can manually install them yourself. See here.
4) WHEN you get the update notification, IF you want it to install automatically, you will need to ensure that that you are using the corresponding boot, radio and recovery images for the .tgz package you downloaded. Otherwise, the update will not install automatically, but it will install using a custom recovery like CWM. See this thread for details.
5) This note is NOT for n00bs. There has been a lot of uncertainty and questions around stock ROMs and losing/wiping data. You CAN flash a stock ROM WITHOUT losing the data stored in /sdcard (and possibly even all apps and app data, although this depends on which apps you have installed). This can be done by skipping step 10 in part D. However, if your device goes into a boot loop, you will need to boot CWM, and wipe data <-- this will wipe your apps and app data, but not /sdcard.
6) Jelly Bean requires a newer bootloader. I would not flash anything earlier than LA03, or you may have issues.
Notes on the bootloader:
1) Do NOT re-lock your bootloader after you are finished. The is no need.
2) Having an unlocked bootloader does not affect anything related to the ROM/GoogleWallet/OTAs. Nothing at all.
3) If your bootloader is locked, you CANNOT use fastboot commands. This is pretty much the only thing it affects.
4) If your bootloader is locked, and you need to unlock it, it will wipe everything, including /sdcard. This is the major drawback of re-locking your bootloader.
5) ONLY re-lock your bootloader if you need to return your device to the store. The command is: fastboot oem lock
6) As of June 2, 2012, a method has been found to unlock the bootloader without wiping (but root is required), and segv11 put it together in an app for us. See here. So, if you have root, there is no issue with re-locking the bootloader if you want -- just make sure you don't lose root, or you will have to wipe to unlock it again.
[HOW-TO] Install official JRN84D (Jelly Bean 4.1) on your GSM Galaxy Nexus
EDIT: As of Jul 27th, 2012, this information is no longer required -- the yakju/takju JRO03C factory images are now posted on Google's site here.
Here is my take on how to flash JRN84D (official) on ANY maguro (i.e., GSM/HSPA) Galaxy Nexus, regarless of what build you are currently running.
Notes:
1) Doing it this way will leave you with an official JRN84D ROM, and you will receive future updates, assuming that there are any for JRN84D (which is almost certainly the case).
2) Method 2 assumes that you have: a) the drivers properly installed, b) an unlocked bootloader, and c) you have downloaded the attachment in the first post of this thread.
3) Both these methods will require you to wipe your data, but NOT the files you have in /sdcard. (I tried to get it to work without wiping data, but I couldn't get it to work. This is not to say that it won't work for all of you, but I can guarantee that it will work if you wipe.) The Play Store will automatically re-install all your apps, and your can restore the app data with Titanium Backup (root required of course).
4) I have had NO issues whatsoever so far with the OS. There are some apps, however, that are not yet compatible with Jelly Bean (like CallRecorder).
5) Jelly Bean requires a newer bootloader. Do not try to flash this without having LA03 or newer, or you may have issues.
Method 1: CWM 5.5.0.2 recovery already installed
1) Download takju JRN84D from here (this is Koush's repack) to your computer and rename (or delete) this file: /system/etc/install-recovery.sh. Use 7zip to do this, not WinZip or WinRar or whatever. This will prevent the ROM from overwriting CWM with the stock recovery. If you want to have the stock recovery so that future updates will install automatically, leave the ROM as is. (We all know that if you have CWM, you will have to install the update manually through CWM -- it will not install automatically, but it will install just the same, right? ) Note: Some users have reported that they could not flash the zip after deleting the install-recovery.sh file. If it doesn't flash for you after you deleted the file, just re-flash the unmodified zip.
2) Move the file to /sdcard on your phone.
3) Download the CWM-flashable version of the XXLF1 radio from here and the CWM-flashable version of the LC03 bootloader from here to /sdcard.
4) Backup your app data using Titanium Backup. Root is required for this step. Alternatively, if you do not have root, you could try using this, but no guarantees it will work.
5) Reboot your phone into CWM.
6) Select "wipe data/factory reset" and select "Yes -- delete all user data"
7) Select "wipe cache partition" and select "Yes - Wipe Cache"
8) Select "advanced" and select "Wipe Dalvik Cache" and select "Yes - Wipe Dalvik Cache"
9) Select "*****Go Back*****" to return to the main menu
10) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the bootloader file you downloaded, and flash it.
11) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the radio file you downloaded, and flash it.
12) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the JRN84D file you downloaded, and flash it.
13) Optional -- If you want root, flash one of the attachments the same way. (Either ChainsDD's Superuser or Chainfire's SuperSU. Note that you may have issues with Superuser, as it has yet to be updated.)
14) Go back to the main menu and select "reboot system now".
15) Done! Enjoy stock Jelly Bean 4.1
Method 2: Stock recovery (or any other recovery aside from CWM 5.5.0.2) installed
1) Download CWM from here to the same directory on your computer as your fastboot file, and rename it to cwm.img.
2) Download takju JRN84D from here to /sdcard on your phone. (This is Koush's repack.)
3) Download the CWM-flashable version of the XXLF1 radio from here and the CWM-flashable version of the LC03 bootloader from here to /sdcard.
4) Backup your app data using Titanium Backup. Root is required for this step. Alternatively, if you do not have root, you could try using this, but no guarantees it will work.
5) Reboot your phone into fastboot mode (turn off and press vol up + vol down + power) and plug into your computer.
6) Open a command prompt in the same directory as your fastboot file and type: fastboot boot cwm.img
7) On your device, CWM should be booted up. You can unplug your device from your computer if you wish. From now on, everything is done on your device.
8) Select "wipe data/factory reset" and select "Yes -- delete all user data"
9) Select "wipe cache partition" and select "Yes - Wipe Cache"
10) Select "advanced" and select "Wipe Dalvik Cache" and select "Yes - Wipe Dalvik Cache"
11) Select "*****Go Back*****" to return to the main menu
12) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the bootloader file you downloaded, and flash it.
13) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the radio file you downloaded, and flash it.
14) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the JRN84D file you downloaded, and flash it.
15) Optional -- If you want root, flash one of the attachments the same way. (Either ChainsDD's Superuser or Chainfire's SuperSU. Note that you may have issues with Superuser, as it has yet to be updated.)
16) Go back to the main menu and select "reboot system now".
17) Done! Enjoy stock Jelly Bean 4.1.
As always you are king =]
- Google Galaxy Nexus
Thank you very much. As someone who is completely green at the android thing, I made it through this instructional with barely a hick-up. I think if I had done as you said and read through the entire post before starting then I might have saved myself some time.
THANKS!
efrant said:
A. Install the drivers
1) Do not install the Samsung drivers or the pdanet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
Click to expand...
Click to collapse
If I have pdanet drivers installed and I can do successful fastboot and adb devices commands does that necessarily mean I am good to go? Or would you still recommend replacing them before I start flashing?
what's the benefits of this over the Gnex toolkit? Just curious as I'm new to the nexus
Sent from my Galaxy Nexus using Tapatalk 2
NCguy said:
If I have pdanet drivers installed and I can do successful fastboot and adb devices commands does that necessarily mean I am good to go? Or would you still recommend replacing them before I start flashing?
Click to expand...
Click to collapse
If you have them installed and fastboot is working fine for you, then you are ok.
Thegodfather156 said:
what's the benefits of this over the Gnex toolkit? Just curious as I'm new to the nexus
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You actually see what is happening step-by-step in this method, in the hopes that you will learn something.
A toolkit does not run you through the steps, so it breeds a new wave of users who don't know how to use fastboot and don't know how to troubleshoot.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
efrant said:
You actually see what is happening step-by-step in this method, in the hopes that you will learn something.
A toolkit does not run you through the steps, so it breeds a new wave of users who don't know how to use fastboot and don't know how to troubleshoot.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
Click to expand...
Click to collapse
Great thats why I'm here. I wanna learn more about how android works. Thanks for this thread. Also I've read that before. I'm not that noobish
Sent from my Galaxy Nexus using Tapatalk 2
Does usb debugging have to be turned on for this? Also I have the samsung drivers installed, if fastboot recognizes my phone does that mean that they work correctly?
SirRomie said:
Does usb debugging have to be turned on for this? Also I have the samsung drivers installed, if fastboot recognizes my phone does that mean that they work correctly?
Click to expand...
Click to collapse
No for your first question, and most likely yes for your second.
Amazingly simple guide. I finally got around to doing this, much thanks!
efrant said:
You actually see what is happening step-by-step in this method, in the hopes that you will learn something.
A toolkit does not run you through the steps, so it breeds a new wave of users who don't know how to use fastboot and don't know how to troubleshoot.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
Click to expand...
Click to collapse
This is the main and only reason why I don't use toolkits. Excellent work!
Sent from my Galaxy Nexus using Tapatalk 2
I just want to start this post by saying I am very new to this and I do not want to screw anything up. I have the correct files and drivers ready, but when I type the command "fastboot oem unlock" my phone says it is already unlocked. Just to be clear bootloader and being factory unlocked to use with any carrier are two different things?
Also if my phone's bootloader is unlocked, that could mean that the previous owner tinkered with this phone (I think), so am I able to just type in all of the commands that follow the unlock step without issue? Should I wipe my phone anyway? I am going from 4.0.1 yakjuux to 4.0.4 yakju and if so before or after fastboot is done?
SirRomie said:
I just want to start this post by saying I am very new to this and I do not want to screw anything up.
Click to expand...
Click to collapse
No problem. We are here to help!
SirRomie said:
I have the correct files and drivers ready, but when I type the command "fastboot oem unlock" my phone says it is already unlocked. Just to be clear bootloader and being factory unlocked to use with any carrier are two different things?
Click to expand...
Click to collapse
Yes, they are different.
SirRomie said:
Also if my phone's bootloader is unlocked, that could mean that the previous owner tinkered with this phone (I think), so am I able to just type in all of the commands that follow the unlock step without issue?
Click to expand...
Click to collapse
Yes and yes.
SirRomie said:
Should I wipe my phone anyway? I am going from 4.0.1 yakjuux to 4.0.4 yakju and if so before or after fastboot is done?
Click to expand...
Click to collapse
The procedure will wipe (assuming you do step 10 in part D).
Thanks efrant for all of your help! I have managed to get 4.0.4 working, however, my playstore doesn't work... It says server error retry also my phone is from the UK so it says playshop now. Anyway to change this and also get it working?
EDIT: clearing data worked. It still says playshop though. Would downloading another locale help? I don't think there was a locale change on the other build yet it said store and not shop.
flashing alternative radios
Hi efrant,
I have previously done this method and loving 4.0.4. Now I am wondering about trying different radios, as I am in Australia
To flash a new radio in fastboot, do i just type:
fastboot flash radio (radio-maguro-i9250xxla02.img) <- whatever the name of the radio image is
Or do i have to reboot the bootloader, and flash all the other stuff first?
After I flash the radio, do I just reboot the bootloader and that is that... or do I need to flash the system partition, boot partition and erase the cache too?
If I change the radio, I have to return it back to XXLA2 for future OTA updates to install successfully, right
Running:
Stock Android 4.0.4
19250XXLA2
3.0.8-gda6252b
IMM76I
sagiballs said:
Hi efrant,
I have previously done this method and loving 4.0.4. Now I am wondering about trying different radios, as I am in Australia
To flash a new radio in fastboot, do i just type:
fastboot flash radio (radio-maguro-i9250xxla02.img) <- whatever the name of the radio image is
Or do i have to reboot the bootloader, and flash all the other stuff first?
After I flash the radio, do I just reboot the bootloader and that is that... or do I need to flash the system partition, boot partition and erase the cache too?
If I change the radio, I have to return it back to XXLA2 for future OTA updates to install successfully, right
Running:
Stock Android 4.0.4
19250XXLA2
3.0.8-gda6252b
IMM76I
Click to expand...
Click to collapse
All you have to do is to boot into fastboot mode, and type: fastboot flash radio (radio-maguro-i9250xxla02.img) <- whatever the name of the radio image is
I would also type the following: fastboot erase cache
And then reboot: fastboot reboot
Nothing else.
As for your second, yes, you will need to flash back to XXLA2 for future OTA updates to install successfully.
Well I managed to get everything working. The guide made it as simple as can be. The set-up was the main hurdle, but once everything was downloaded and unzipped, it was a piece of cake.
Thanks again efrant for making this! I finally am happy with my Nexus.
chubiprince said:
Hi... I am not really an expert with this things, so I would just like to ask you if I am doing the right way. I am not an Android expert, and I am really new to this kind of thing.
Click to expand...
Click to collapse
Please don't quote massive amounts of the first post. There is no need.
chubiprince said:
- I have none of these in my laptop, so I will just skip these right?
Click to expand...
Click to collapse
Not sure what you are asking. The post says do NOT install those drivers. If you haven't, then why are you asking if you should skip them?
chubiprince said:
- Uhmmm, yeah. I don't know how to install it. Install it where? My GNex? Or in my laptop?
Click to expand...
Click to collapse
If you are asking this question (i.e., do I install the drivers on my GNex or on my laptop), then, no offence, but you have bigger problems that what can be solved by me telling you what to do. You should try and do a bit more reading, before attempting this.
chubiprince said:
- Will this toolkit (http://www.tested.com/news/feature/...-data-from-your-galaxy-nexusno-root-required/) affect in updating my GNex?
Click to expand...
Click to collapse
No it should not.
Easiest guide to flash a custom ROM and custom kernel
Lets accept it,we all have been here,confused what should do after i root/boot unlock
we think i know enough so lets get this going but then, we get stuck in the splash/welcome screen and we think **** this was such a bad idea
SO i created this thread for anyone who ever is confused,lost,seeking help.
IF YOU FIND THIS THREAD HELPFUL, BE SURE TO RECOMMEND IT TO OTHERS AND PRESS THE THANKS BUTTON :d
Thread Contents
1.Common terms/Android Slangs
2.Basic Requirements
3.Download links for Recovery Images for PRIMO U/ PRIMO C]
4.How To flash recovery
5.FAST BOOT FILES(download links) : HTC ONE V DRIVER (DOWLOAD LINKS)
6.How To Back Up Your Current Rom
7.Installing Your ROM
8.Choose Your Kernel(download links)
9.Flashing The Kernel[windows]
*Flashing The Kernel[MAC]
10.people who have already flashed a ROM and are confused how to upgrade it
11.Upgrading KERNEL
12.Stuck in Bootloops, Cant Pass the HTC welcome Screen
13.Some tips from me
Click to expand...
Click to collapse
Hope u have successfully rooted and boot unlocked
Common Terms/Android Slangs
a small guide on some of the android terms my Diablo67
Bootloader:This small program's only job is to load other data and programs which are then executed from RAM.Often, multiple-stage boot loaders are used, during which several programs of increasing complexity load one after the other in a process of chain loading.
Fastboot:A diagnostic protocol used primarily to modify the flash filesystem in Android smartphones from another computer over a USB connection. It is part of the Android Debug Bridge library.
Utilizing the Fastboot protocol requires that the device be started in a boot loader or Second Program Loader mode in which only the most basic hardware initialization is performed. After enabling the protocol on the device itself it will accept any command sent to it over USB via a command line. Some of most commonly used fastboot commands include:
•flash - Overwrites a partition in flash with a binary image stored on the host computer.
•erase - Erases a partition in flash.
•reboot - Reboots the device into the either the main operating system or the system recovery partition.
•devices - Displays a list of all devices (with Serial #) connected to the host computer.
Flashing:The ROM memory used in smartphones and tablets etc. is often same as flash memory found in SD cards and USB flash drives, simply optimized for better speed and performance while running the operating system.
Kernel:A kernel is a layer of code that allows the OS and applications to interface with your phone's hardware. The degree in which you can access your phone's hardware features depends on the quality of code in the kernel. The homebrew (rooting) community for HTC has made several kernel code improvements that give us additional features from our hardware that the stock kernel does not. When you flash a custom ROM, you automatically get a kernel. But you can also flash a standalone kernel ROM on top of the existing one, effectively overwriting it. These days, the difference in custom kernels is less about new features and more about alternate configurations. Choosing a custom kernel is basically choosing one that works best with your ROM.
Nandroid:To backup the current running rom.
Recovery Mode:A small separate operating mode you can boot your device into, used for device administration. Two popular custom recovery modes are Amon Ra and Clockwork.
Basic Requirements
1.A Boot-unlocked and Rooted HTC One V
2.Charge it till above 75% battery
2.A PC(this guide is for now only for windows)
3.usb cable
4.HTC driver download here or HTC SYNC
5.FastBoot Files[ click here>>> download them and put in a folder in c drive ]
> example c:\fastboot or c:\android
6.A recovery image(for image scroll down)
7.A Rom(thats ur choice)
8.boot image(scroll down)
9.put the rom(.zip file) in sd card
Here Are The Recovery Images
Recovery Images[PRIMO U/GSM]
1. CWM 6 by Lloir
2. TWRP 2.6.0 <<Ill Recommend [very user friendly]
3. CWM v5 Touch Recovery
Recovery Images[PRIMO C/CDMA
1. [VM/PRIMOC][RECOVERY] CWM Recovery
2. [VM/PRIMOC][RECOVERY] TWRP2 Recovery
3. [RECOVERY] [PRIMOC/CDMA] CWM 6.0.1.5
How To flash recovery
HOPE U HAVE THE FAST BOOT FILES
[IF NOT]
click here download them and put in a folder in c drive
example c:\fastboot)
>>Now enter Fast boot(power button +volume DOWN(for 15 + sec))<<<
u might have arrived at Hboot boot mode>>> now move up down by pressing the volume buttons and select fastbootwith the power button
Flash it via cmd(command prompt)
Enter these commands
Code:
[B][COLOR="Red"]fastboot flash recovery recovery.img
[/COLOR][/B]
How To Back Up Your Current Rom
(must for first time flashers)(nand=backup of current ROM)
1. Once the CWM/TWRP recovery installed:
Now enter Fast boot(power button +volume DOWN(for 15 + sec))
now move up down by pressing the volume buttons and select fastbootwith the power button
2. Once you are in the RECOVERY menu:
click backup and restore
click backup
the backup process is running. It will be a max 20 minutes to complete.
(optional step just to be sure)
3. once complete, check whether the backup is successful
click backup and restore
click restore
you will see your backup files, for example 2012-11-27 11-7
it should complete with in a span of time
4.Now if that is over go back to the previous menu
use the back button
click reboot system now to boot your device
Installing Your ROM
5.just do a factory reset and wipe cache, then click on install from sd card
6.flash it(the ROM in ur sd card shud be in a .zip format)
7.NOW.DON'T REBOOT UR PHONE GO TO FAST BOOT MODE (VOLUME DOWN+ POWER BUTTON)(or there will be a option to reboot into bootloader)
Choose Your Kernel
9.download whichever kernel u want
[CDMA/PRIMO C]
SuperSick kernel Click ME
SICK kernel PRIMO C/CDMA click here
[GSM/PRIMO U]
SuperSick kernel Click ME
SICK kernel CLICK here
TITANIUM KISS kernel SENSE users CLICK here
HELLBOY kernel FOR AOSP based ROMS(cm9/cm10/AOKP/PA)USE THE LATEST ONE FOR 4.2.2 >click<
Flashing The Kernel[windows]
8.HOPE U HAVE THE FAST BOOT FILES (if not click here download them and put in a folder in c drive)
rename it boot.img and put it in the folder as the fastboot files
GO TO FAST BOOT MODE (VOLUME DOWN+ POWER BUTTON)(or there will be a option to reboot in recovery)
10.flash it via CMD
Enter these commands
Code:
11.[B][COLOR="Red"]Fastboot flash boot boot.img [/COLOR][/B]
12.[B][COLOR="Red"]fastboot reboot[/COLOR][/B]
Flashing The Kernel[MAC] by kalaker
kalaker said:
Go developer.android.com and download the SDK & move it to your home directory ("~" or /Users/<username>)
Go to <sdk-location>/tools and launch "Android"
Download the platform tools
Open terminal
Open Finder to <sdk-location>/platform-tools
In terminal, type "sudo cp"; drag adb from the Finder window into the Terminal window; type "/usr/bin/"; hit enter
Enter your password
Repeat the above three steps, but drag "fastboot" instead of "adb"
Close terminal
Open terminal (it sounds weird, but just do it)
Now, and forever, do this to install a kernel:
Download kernel
Connect phone to computer
Make sure USB Debugging is enabled (Settings>Development>USB Debugging)
In terminal, type "adb reboot bootloader"
In terminal, type "fastboot flash boot"; drag in the kernel from finder; hit enter
Examples:
Code:
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
adb reboot recovery
fastboot flash boot /Users/Username/Downloads/boot.img
Click to expand...
Click to collapse
13.enjoy
First boot takes some time have patience......be sure to ask questions or doubts
Ok For people who have already flashed a ROM and are confused how to upgrade it
Upgrading ROM
1.download your needed ROM
2.put in SD card
3.boot into recovery
4.no need to wipe everything,wipe caches(and if the dev says to full wipe do it)
5. (Unless u come from a different ROM eg.From Amazing Sense To CM10, in this case a factory reset i needed
6.flash the ROM
7.reboot
8.flash GAPPS
9. enjoy
Upgrading KERNEL
1.boot in bootloader
2.do the required steps(as mentioned above)
3.wipe caches
5.enjoy
Stuck in Bootloops, Cant Pass the HTC welcome Screen
ok, calm down, everyone has this problem while flashing, i get it so many times, they can cause by the following reasons
bad flash
wrong rom
you forgot to flash the kernel
wrong kernel
messed up the order in flashing
ok,
1.Bad flash-this occurs if the .zip file is corrupted
solution:= re flash the ROM, if still no, download the file again and try
2.wrong ROM- u may have downloaded a ROM that is not for ur device or a ROM which is of not ur description
for example u might me a PRIMO C device/CDMA and u downloaded a PRIMO U/GSM ROM
3.Wrong Kernel-Kernel is the link between ur software and hardware, if u flash the wrong one like the case mentioned above , download the correct one and re flash
4.[ FLASHING YOUR KERNEL SHOULD BE THE LAST STEP][UNLESS U HAVE A S-OFF DEVICE]
Ok Some Tips Which May Help You
1.Battery Draining fast?
-----get an app called BetterBatteryStats,run it over night.then next morning open it and check whats waking your device
Click to expand...
Click to collapse
2.Can i use scripts?
-----Your wish, the rom works perfect,running a script can ruin it in some cases(chill,even i run some)
Click to expand...
Click to collapse
3.Good/best/recommended ROMS?
-----all roms are good in their own way, but i can give u a list of recently updated roms
-----1.sphongle(4.2.2) 2.Slimbean 3.Cm10
Click to expand...
Click to collapse
will add more cheers
Hope this helps u
another get thanks quick scheme thread?
Sent from my One V
paarthdesai said:
another get thanks quick scheme thread?
Sent from my One V
Click to expand...
Click to collapse
LOL :silly:
no i plan to help!
My works
You call that work ??
Those are just tips
Y do u have a problem with that
Sent from my One V
No but that work word is pissing me off ..... For using it in a inappropriate place
donhashem.dh said:
No but that work word is pissing me off ..... For using it in a inappropriate place
Click to expand...
Click to collapse
Don't read it
Sent from my One V
to clarify, step 6: "flash" should be edited to say " install ROM from zip" to avoid the "flash" misconception associate with flashing kernels:good:
more detailed work should be there.. like you said install cwm or twrp.... give a link to where they are embedded in the words will be good...
and the above goes for the flashing rom part also...embed the link to the dev section
make it easy and tidy instead of all those ugly looking clutters you did
Sent from my One V
will work into that!
did it!
cybervibin said:
flash it via cmd
Enter these commands
Fastboot flash recovery recovery.img
Click to expand...
Click to collapse
You forgot to mention to boot into fastboot. No offence, but it has to be much better written. Its not noob friendly at all.
m sorry abt that! guess missed it! wrote the thread throygh my phone!
any other problems i corrected the one u said!
cybervibin said:
m sorry abt that! guess missed it! wrote the thread throygh my phone!
any other problems i corrected the one u said!
Click to expand...
Click to collapse
Yeah, you could try creatign sub sections, like thinigs to have before swap, then steps after that. Eg in step 1 you say
>>Now enter Fast boot(power button +volume DOWN(for 15 + sec))<<<
and
1.Flash CWM 6 by lloir
or TWRP 2.3.1.0 ill recommend TWRP
>>PRIMO C /CDMA click here<<
To flash recovery HOPE U HAVE THE FAST BOOT FILES(IF NOT click here download them and put in a folder in c drive
example c:\fastboot
Click to expand...
Click to collapse
First you mention the ROM, then out of the blue you mention recovery. ROM should be introduced after a nand backup. You should also explain in short what a nand backup is. A sentence with an analogy is sufficient. I am a software developer and I would like to share a rule that I follow: If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Dont get me wrong, I am not trying to insult or berate or anything, but I got it read by a friend who wants to flash his One V, and he got back to me with more questions than the guide answered. There a some step holes in the guide, and you have to write is as if you are a noob
Lastly, thanks a lot, this particular guide and your answers have been really helpful to me and the community.
Cheers!
now ill consider that! hard being a noob!
thetuxracer said:
If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Click to expand...
Click to collapse
Nice, I liked this!
Sent from my One V using xda app-developers app
soham_sss said:
Nice, I liked this!
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
thetuxracer said:
Yeah, you could try creatign sub sections, like thinigs to have before swap, then steps after that. Eg in step 1 you say
First you mention the ROM, then out of the blue you mention recovery. ROM should be introduced after a nand backup. You should also explain in short what a nand backup is. A sentence with an analogy is sufficient. I am a software developer and I would like to share a rule that I follow: If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Dont get me wrong, I am not trying to insult or berate or anything, but I got it read by a friend who wants to flash his One V, and he got back to me with more questions than the guide answered. There a some step holes in the guide, and you have to write is as if you are a noob
Lastly, thanks a lot, this particular guide and your answers have been really helpful to me and the community.
Cheers!
Click to expand...
Click to collapse
how about now, noob friendly enough?
Yup, pretty cool! If there was a way to thank again..
ty!! please keep the recomendations coming!
I will be telling you how to put CM 10 on your device without root, as root will automatically come to your device when you are done with CMing. This method works for every phone. I used FXP208-cm-10-20130223-UNOFFICIAL-anzu.zip for my Xperia Arc LT15i. Just check under the project status tab if you want to know if your device is supported. You can also use CM 9, 8 or 7 if you like, the method is the same. Please consider the fact that that this will void your phone's warranty. (Who cares?)
Note:
You do not need root for this.
You need to unlock your phone's bootloader for this.
Downloads:
Fastboot mediafire.com/?47eu9m848c5wbi0
CyanogenMod freexperiaproject.com
Google Apps goo.im/gapps/gapps-jb-20120726-signed.zip
Sorry I could not put links... I am not new to Android and CM but I am new to xda so they did not let me put links
Instructions:
1. Extract the CyanogenMod zip and Fastboot zip files to a convenient location.
2. Copy boot.img from the CM folder to the Fastboot folder. There should now be 5 files in the Fastboot folder.
3. Connect your phone to your computer as you normally would.
4. Place Google apps and CM on the root of your SD card in .zip file format.
5. Disconnect your phone and reconnect in fastboot mode. Just search Google for how to connect phone in Fastboot mode.
6. Go to the Fastboot folder. Open a command window and hold the shift button and right-click.
7. Select the " Open command window here " option.
8. Type
Code:
fastboot flash boot boot.img
The boot image will be flashed to your phone. Disconnect your phone from PC
9. Boot your phone. When the FreeXperia logo comes press the back button like CRAZY until your phone goes into ClockworkMod recovery.
10. Go to advanced. Select 'wipe dalvik cache' and select yes.
11. Go back to main menu and select 'wipe data/factory reset' and select yes.
12. At the main menu select 'wipe cache partition' and yes.
13. Go to mounts and storage and select 'format /system'.
14. From the main menu select 'reboot system now'
15. Setup your phone.
16. Install updates.
17. Enjoy.
If you found this post helpful then please press the thanks button on the left
Or, you could've just flashed a pre-rooted kernel like Advanced Stock.
There's a video in my Arc guide too explaining how to install CM.
Sent from Myushi
MarcSinger said:
Or, you could've just flashed a pre-rooted kernel like Advanced Stock.
Click to expand...
Click to collapse
Here we are trying to CM, not root.
KabbageX said:
Dude, here we are trying to CM, not root.
Click to expand...
Click to collapse
Yes, NOW you are. AFTER you edited your post, in which you clearly mentioned having problems with rooting and cited this as a method of rooting your device/getting CM10 installed. Besides, there's already a detailed tutorial on installing Cyanogenmod on their own website:
http://wiki.cyanogenmod.org/w/Install_CM_for_anzu
MarcSinger said:
Yes, NOW you are. AFTER you edited your post, in which you clearly mentioned having problems with rooting and cited this as a method of rooting your device/getting CM10 installed. Besides, there's already a detailed tutorial on installing Cyanogenmod on their own website:
http://wiki.cyanogenmod.org/w/Install_CM_for_anzu
Click to expand...
Click to collapse
He is new to forum and excited.Give hime a break.
MarcSinger said:
Yes, NOW you are. AFTER you edited your post, in which you clearly mentioned having problems with rooting and cited this as a method of rooting your device/getting CM10 installed. Besides, there's already a detailed tutorial on installing Cyanogenmod on their own website:
http://wiki.cyanogenmod.org/w/Install_CM_for_anzu
Click to expand...
Click to collapse
Ok
Very Helpful
Allow me to change step #17 to:
17. Download Swapper2 and install.
and NOW #18. Enjoy
AdibSul said:
Very Helpful
Allow me to change step #17 to:
17. Download Swapper2 and install.
and NOW #18. Enjoy
Click to expand...
Click to collapse
I am glad I could help.