Database Users

EPE54B (new N1- AT&T) -> FRF50 -> FRF83 & beyond (hopefully) in 20 minutes

EPE54B (new N1- AT&T) -> FRF50 -> FRF83 & beyond (hopefully) in 20 minutes
and FROYO IS AWESOME !!! Believe me , it's really worth making this effort .
Ok guys , I think it's time for me to contribute some documentation for the XDA forum. As mentioned in the Topic's header , I moved to Froyo y'day night and wanted to share the process with the AT&T N1 ppl on the forum who are ready to unlock the bootloader but are lazy/frightened to go about the so-called lengthy process.
I am a new N1 & a new android user (just a month old ) who has spent sleepless nights like some of the people in this forum and most of the people (here) waiting for the Froyo OTA to hit their N1's. After a 3 week sleep disorder I finally went in for the kill. Thanks to Paul for his guide and others in the forum because of which,this it was accomplished in just 20 minutes.
AT&T N1 (EPE54B) owners who are bold enough to unlock their boot loader ... here's the way to glory.
Senior XDA members please correct the process if you feel something is not right.
I will be using most of the info provided by Paul in his post (here) and I hope he wouldn't mind , if I use his info.And believe me guys , it seriously takes only 20 minutes.
DISCLAIMER
1) I do not take credit for any of the stuff posted here. It's mostly from Paul's guide and other sources. All credits go to the original up-loaders.
2) This is a step-by-step guide which I have prepared from the process I have followed to reach FROYO and am not responsible if it doesn't work for you.
2)You agree that by doing this process, I'm not responsible for any bricked devices.
Unlocking the bootloader will void your warranty.
This process will erase all of your phone's data.
INITIAL SETUP
1) Download android-sdk_r06-windows.zip
2) Unzip to C:\ drive so it looks like C:\android-sdk-windows\
3) Run SDK Setup.exe
4) In the screen that pops out - Double click everything so it has a red X except for green check mark next to "USB Driver Package"
( which means just have to install the USB Driver)
5) On you Nexus 1 - Navigate to 'Settings -> Application -> Development -> enable USB debugging'.
6) Connect your nexus one to the computer through the USB cable provided with your phone.
7) Wait for the PC to install the device driver.
- If it doesn't then --- 'New Hardware Found -> Point the install location to C:\android-sdk-windows\usb_driver\'
8) Once the driver is found and installed ; On your computer open a command window. 'start -> Run -> type 'cmd' -> hit 'ENTER'.
9) On the command screen: Type "cd c\" ; Hit 'ENTER' key
10) Then Type: "cd C:\android-sdk-windows\tools" ; Hit 'ENTER' key
11) Type: adb devices ; Hit 'ENTER' key
- It should say something similar to "HT123P123456 device" (this is your phone's serial number).
- If it says "cannot find" or "invalid path" etc, make sure you're typing *exactly* what the green text above says.
- If it says something else, try to reinstall the USB Driver package and restart your PC.
12) If it works, your PC is correctly recognizing the phone. Continue on to the next step!
UNLOCK BOOTLOADER
1) Turn off your nexus one.
2) Press and hold the trackball and also press the power button ( while still holding the trackball pressed).
3) A white screen with three droids at the bottom appears.
4) A RED background highlights "FATSBOOT" which changes to "FASTBOOT USB" in a second or two.
5) Now, On your computer open a command window. 'start -> Run -> type 'cmd' -> hit 'ENTER'.
6) On the command screen: Type "cd c\" ; Hit 'ENTER' key
7) Then Type: "cd C:\android-sdk-windows\tools" ; Hit 'ENTER' key
8) Now on your computer; TYPE: fastboot devices
- It should say something similar to "HT123P123456 fastboot" (this is your phone's serial number). If it doesn't say this, something is wrong.
- If you are typing fastboot devices and it just returns a blank line or ???????? (ie Windows 7 64-bit users), try using USB drivers in the PdaNet install:
http://www.junefabrics.com/android/download.php
9) If it shows the device number , then you are set to go.
10) On the command window opened previously ; TYPE: fastboot oem unlock
11) Read the screen carefully. If you click on unlock it will wipe all your DATA!! and also Unlock your phone .
12) Use the volume control keys on your nexus one to switch options and then press the power key to select the option.
13) An "unlocked padlock" appears while booting and YAY!! you are unlocked!!!!
14) Shut down your phone and boot into the boot loader ( Trackball pressed + power button )
INSTALL(FLASH) RECOVERY
1) Download the latest Amon_RA's recovery img from here
2) move it to "C:\android-sdk-windows\tools" .
3) On your computer open a command window. 'start -> Run -> type 'cmd' -> hit 'ENTER'.
4) On the command screen: Type "cd c\" ; Hit 'ENTER' key
5) Then Type: "cd C:\android-sdk-windows\tools" ; Hit 'ENTER' key
6) On you computer's command window -- Type: fastboot devices and make sure your device's number is showing up.
7) On you computer's command window -- Type: fastboot flash recovery recovery-RA-nexus-v1.7.0.img
8) It should say: sending 'recovery' (3962 KB)... OKAY . . . . . writing 'recovery'... OKAY This should take a few seconds.
9) If flashing the recovery was successful, use the menu options to boot directly into recovery, or restart your phone normally.(without going to the bootloader screen).
Rooting
1) Download the nexus-addon-0.1-signed.zip from here.
2) Copy the file onto your SD card. ( It should be in the root folder of your SD card i.e don't put it under any directories).
3) Shut down your nexus one
4) Boot into the boot loader ( Trackball pressed + power button )
5) Press the power button once ( quickly and for a very short time ).
6) The screen changes and you move to the Fastboot screen.
7) Do Not do anything for about 8-10 seconds. It scans for some files and returns to the "FastBoot Screen"
8) Now use the "volume down" button to select "Recovery" and press the power button.
9) Do this step only if you didn't use Superboot: Use trackball -> "Flash zip from from sdcard" -> nexus-addon-0.1-signed.zip
- If you get a Triangle with a ! in the middle alongside an Android for 5+ minutes, you MAY have to remove battery and re-flash recovery (I had to do this once.) (Make absolutely sure that nothing is happening on your phone, as removing the battery when it's doing something can cause a brick.)
- Alternatively, try the optional Superboot method, and then re-flash Amon_RA's recovery image.
10) Select Reboot.
Phew .. that was hard ... but here comes the best part !!!
INSTALL FRF50 with Radio
1) Download the FRF50 with Radio zip file from here (Paul's FRF50 ROM).
2) Copy the file onto your SD card. ( It should be in the root folder of your SD card i.e don't put it under any directories).
3) Rename it to update.zip and make sure it's not "update.zip.zip". ( if you have the extension names off ).
4) Shut down your nexus one.
5) Boot into the boot loader ( Trackball pressed + power button )
6) Press the power button once ( quickly and for a very short time ).
7) The screen changes and you move to the Fastboot screen.
8) Do Not do anything for about 8-10 seconds. It scans for some files and returns to the "FastBoot Screen"
9) Now use the "volume down" button to select "Recovery" and press the power button.
10) The phone now boots into Recovery.
11) Use your phone's "Trackball" to Navigate and press the "trackball" to execute the selection.
12) Run the following
a) Backup/Restore -> Nand backup
b) Wipe -> Wipe data/factory reset
c) Wipe -> Dalvik Cache
13) Then press the "volume down" button to return to the main recovery screen.
14) Now , select "Flash zip from sdcard" and in the next screen select the "update.zip" file.
15) You get an "install completed" message after about 15-20 seconds.
16) Reboot and you are into the wonderful world of "FROYO".
FRF50 -> FRF83
1) Ok, now I think you are already enjoying your delicious dessert. Let's add some strawberries to it.
2) Download the PAUL modified FRF50 -> FRF83 zip file from HERE.
3) Connect your phone to the USB cable and mount the card.
4) Remove the existing update.zip file from the SDcard.
5) Copy the downloaded FRF83 file into the SDcard's root folder and rename it to "update.zip".
6) Shut down your nexus one.
7) Boot into the boot loader ( Trackball pressed + power button )
8) Press the power button once ( quickly and for a very short time ).
9) The screen changes and you move to the Fastboot screen.
10) Do Not do anything for about 8-10 seconds. It scans for some files and returns to the "FastBoot Screen"
11) Now use the "volume down" button to select "Recovery" and press the power button.
12) The phone now boots into Recovery.
13) Select "Flash zip from sdcard" and in the next screen select the "update.zip" file
14) Wait for the most annoying 15-25 seconds and reboot.
15) VOILA , you are on the latest and greatest android update for Nexus one.!!!!

I think I'll wait, but excellent work on putting all of that together!

Thanks for the step by step. I believe another approach is to not root (just unlock the bootloader) and to flash back to the TMO ROM and use the leaked official updates. I'm trying to determine which to do.

AvengerBB said:
Thanks for the step by step. I believe another approach is to not root (just unlock the bootloader) and to flash back to the TMO ROM and use the leaked official updates. I'm trying to determine which to do.
Click to expand...
Click to collapse
As far as the info goes from this forum .. I came to know that unlocking the bootloader will void warranty. SO I felt that it's worth rooting the phone after unlocking it as we have advantages like Titanium backup and a lot more ...

I did a similar procedure, flashing my phone to ERE54B--->ERE27-->FRF50-->FRF83
I unlocked the bootloader/rooted in the process, but in the end I end.. I installed FRF50--FRF83 to my unrooted nexus one on ATT.
I wish I had tried applying the ERE27 original ROM to my phone with a locked bootloader, I don't know if it would of worked or not.
Either way, I am an ATT Nexus one on FRF83. It's quite nice

Nice instructions, good job compiling!
However, there is no need to flash FRF50 first, and then FRF83. You can just flash Paul's FRF83, and the radio separately.
AvengerBB, a prerequisite of Amon_RA's recovery image is a rooted phone. I am not sure exactly why it requires root, though.

jmorgan6 said:
I wish I had tried applying the ERE27 original ROM to my phone with a locked bootloader, I don't know if it would of worked or not.
Click to expand...
Click to collapse
It wouldn't have.

Just to clarify for me..
I understand unlocking bootloader is what 'voids' your warranty is required to root. It is also not possible to 'undo'.
Is having a 'rooted' phone what prevents you from getting OTA updates, or is having an unlocked bootloader?
If you have a phone with an unlocked bootloader, but not rooted... does google/android OS know any different? (Not warranty claims, but for S/W updates)?
Basically, if/when the ERE54B-->2.2 Update goes official, can I flash back to ERE54B and get the 'original' upgrade intended for my phone if I unroot it. Or will I from here on out have to manually update my phone?

Would you guys PLEASE take a look at this and tell me if you are having this trouble too!

nice work, very well documented, glad someone did this. Thank you.
I think I will continue to wait out the official OTA, but if I get antsy this weekend I know where to come for instructions.
stick this thread!

I have a rooted and bootloader unlocked AT&T version nexus one and I have already installed the FRF50 WITHOUT the radio. Should I go back and reinstall FRF50 with the radio before upgrading to FRF83? On by current build the phone sometimes doesn't reconnect to AT&T service once it has lost service and I need to restart the phone. Does Paul's FRF50 ROM have a radio that supports AT&T? Kinda a noob, sorry. Thanks in advance for the help.

andrewluccio said:
I have a rooted and bootloader unlocked AT&T version nexus one and I have already installed the FRF50 WITHOUT the radio. Should I go back and reinstall FRF50 with the radio before upgrading to FRF83? On by current build the phone sometimes doesn't reconnect to AT&T service once it has lost service and I need to restart the phone. Does Paul's FRF50 ROM have a radio that supports AT&T? Kinda a noob, sorry. Thanks in advance for the help.
Click to expand...
Click to collapse
You need to flash the newer 12_7 radio. The radio image remains the same for ATnT or T-mobile, the actual frequencies are decided by hardware. No need to re-flash FRF50 - just flash the new radio from here - http://n0rp.chemlab.org/android/nexus/radio-4.06.00.12_7.img
You can use "fastboot flash radio radio...img" command to flash it. After flashing new radio, flash FRF83. It is highly recommended that you flash only compatible OS and radio versions.

Man
I have followed all the steps but when I go to flash the update from the sdcard it gives me the an error that says there is no signature and install aborted. What could this be from? I have tried those steps again and again. Please help.

jmorgan6 said:
Just to clarify for me..
I understand unlocking bootloader is what 'voids' your warranty is required to root. It is also not possible to 'undo'.
Is having a 'rooted' phone what prevents you from getting OTA updates, or is having an unlocked bootloader?
If you have a phone with an unlocked bootloader, but not rooted... does google/android OS know any different? (Not warranty claims, but for S/W updates)?
Basically, if/when the ERE54B-->2.2 Update goes official, can I flash back to ERE54B and get the 'original' upgrade intended for my phone if I unroot it. Or will I from here on out have to manually update my phone?
Click to expand...
Click to collapse
You can't re-lock the bootloader without being very lucky, you need an S-OFF SPL. Just having an unlocked bootloader won't effect your ability to get OTA updates, it's custom ROMs and recoveries that do that.

If you're going through all that trouble, just use Paul's superboot to FRF83.

Finally got it to work! It didn't fix my video recording bug though. When I switch from camera to video it just freezes and reboots. Did they ever find a workaround for this? I would appreciate the help.

Shouldn't need a work around, mine doesn't suffer from it.

rohandhruva said:
You need to flash the newer 12_7 radio. The radio image remains the same for ATnT or T-mobile, the actual frequencies are decided by hardware. No need to re-flash FRF50 - just flash the new radio from here - http://n0rp.chemlab.org/android/nexus/radio-4.06.00.12_7.img
You can use "fastboot flash radio radio...img" command to flash it. After flashing new radio, flash FRF83. It is highly recommended that you flash only compatible OS and radio versions.
Click to expand...
Click to collapse
Arent you guys facing troubles with this radio?
My gps is innacurate... i think that is because of the radio image!
If with the oficial froyo it does not is fixed i will flash back my 4.04 radio!
Take a look at this to read about my trouble please!

Need some help. Everything worked up to this point.
INSTALL FRF50 with Radio
1) Download the FRF50 with Radio zip file from here (Paul's FRF50 ROM).
2) Copy the file onto your SD card. ( It should be in the root folder of your SD card i.e don't put it under any directories).
3) Rename it to update.zip and make sure it's not "update.zip.zip". ( if you have the extension names off ).
4) Shut down your nexus one.
5) Boot into the boot loader ( Trackball pressed + power button )
6) Press the power button once ( quickly and for a very short time ).
7) The screen changes and you move to the Fastboot screen.
8) Do Not do anything for about 8-10 seconds. It scans for some files and returns to the "FastBoot Screen"
9) Now use the "volume down" button to select "Recovery" and press the power button.
10) The phone now boots into Recovery.
11) Use your phone's "Trackball" to Navigate and press the "trackball" to execute the selection.
12) Run the following
a) Backup/Restore -> Nand backup
b) Wipe -> Wipe data/factory reset
c) Wipe -> Dalvik Cache
13) Then press the "volume down" button to return to the main recovery screen.
14) Now , select "Flash zip from sdcard" and in the next screen select the "update.zip" file.
15) You get an "install completed" message after about 15-20 seconds.
16) Reboot and you are into the wonderful world of "FROYO".
Click to expand...
Click to collapse
I didn't get an "install completed" message. Instead it says, "Reboot via vol-up+vol-down or menu to complete installation." Then when I reboot it goes to the android falling out of the box image, and then boots back into recovery. I can restore with the nand backup just fine, but this method doesn't seem to work for me. I believe it's the damn radio upgrade that is causing the problems because right before the reboot it says "Writing radio image...". Anybody else experienced this?

thmst30 said:
Need some help. Everything worked up to this point.
I didn't get an "install completed" message. Instead it says, "Reboot via vol-up+vol-down or menu to complete installation." Then when I reboot it goes to the android falling out of the box image, and then boots back into recovery. I can restore with the nand backup just fine, but this method doesn't seem to work for me. I believe it's the damn radio upgrade that is causing the problems because right before the reboot it says "Writing radio image...". Anybody else experienced this?
Click to expand...
Click to collapse
Have you tried doing "Reboot phone" after it boots back into recovery?

HELP - Flash gone bad (looping recovery mode)

OK, so I flashed the wrong ROM today (I9000HVJH1) and the phone now boots into recovery everytime the battery is inserted. I have tried all the tricks to get back to download mode with no luck. The device is recognized by the USB in recovery and was able to push the root update file but can not get it to apply sdcard:update.zip (just sits there and doesn't respond to the power button unless i hold it). Interesting thing is when I plug the USB in and insert the battery, it never goes to charging, it boots into recovery.
Tried:
1. Plug USB
2. Hold vol up (and down but the keys are now backwards in recovery)
3. Insert battery
and
1. Power down (removed battery)
2. Hold vol up + down + power
and
1. Hold vol up (and down too for a few hundred times)
2. Hold power until Samsung logo then release
and
all combo's with and without the USB plugged into the phone.
Beside the tricks shown on the forum, can anything think of a way to get this phone into download mode instead of it constantly booting into recovery? ADB see's the device, just no root access or knowledge of how to get it to apply the update.zip that would root the device.
Thanks~!

http://forum.xda-developers.com/showthread.php?t=741027&page=3

Wrong section. This belongs in general...
Sent from my messenger rabbit

UPDATE!!
After going to T-Mobile on Monday to buy a new Vibrant, I started to think about how to get the "bricked" one working again. I was able to admit defeat for long enough to get a new one but was bothered that I couldn't fix my old one.
I started to think about what I could and couldn't do with the "bricked" one. It would constantly boot start to Android Recovery with error about CSC. No matter what combination of buttons pressed, held, release, the darn phone would never get back to a download mode. Since it could never boot into the OS, ADB seemed impossible. The GOOD news (as it turns out) was when it booted into recovery if I disconnected the USB and reconnected, my computer recognized it and Odin saw it on COM10. I began to look at the batch file for the one click root and noticed the line "adb reboot download". I had messed with ADB the day I screwed up the phone but always tried to do commands after typing "adb shell" and without super user access, I felt doomed. Last night I thought what the heck and powered up the old Vibrant and it went straight to recovery. After another 45 minutes of trying to manually put it into download mode I opened a command prompt and typed "adb reboot download" and the freaking phone rebooted into download mode!!!! So after flashing back to stock I now have fixed the phone
So for anyone who can't get their Vibrant to stop rebooting itself into recovery here is a simple breakdown of what I did.
1 - Power up phone (mine went straight to recovery)
2 - Un-plug the USB and plug it back in (computer should recognize the connection)
3 - Open command prompt and change to the directory that has adb.exe
4 - Type "adb kill-server" and then enter
5 - Type "adb reboot download" and then enter
6 - Phone should reboot into download mode and ready to flash
Make sure you have Odin open with the pit and pda file loaded as there seems to be only a short window of time in which the phone will accept the download and get the status bar moving. If you wait too long, repeat the steps above and start the flash quickly.
I hope this helps someone out that might be experiencing the same problem as me.

[Q] HSPL4 critical error: USB not found

Hello everyone, glad to join the community. I need some help on getting WP7 to work on my HD2.
I got the phone from a friend and it has already been flashed (hope it's the right word)
and it has some version of android running on it. I downloaded HSPL4 and ran it as administrator. Got some errors about missing .dll's
but I resolved it by installing Microsoft Mobile Device Center as activesync is not available on Windows7. So, I start the boot mode
by holding volume down and power buttons but I don't get a three coloured screen, instead I get a b/w menu which looks like this:
aMAGLDR V1.12
Build: Feb 1 2011 03:46:07
by Cotulla 2011
--------------------------
Boot menu:
1. Boot WPH
2. Boot AD SD
3. Boot AD NAND
4. USB MassStg
5. USB Flasher
6. USB TTZ
7. AD Hardreset
8. AD Recovery
9. Tetris
10. Services
11. Reset
12. PowerDown
Then I connect the USB cable to computer and start HSPL4 as admin again and i get an error message saying:
CRITICAL ERROR
Flow: 00000001
Error code: 00000002
Description: USB Connect failed!
I tried selecting options 4, 5 and 6 (after which computer recognizes the phone as a USB device) and starting HSPL4 but
i got the same error. Tried googleing for answers but without much success as everyone gets the three coloured screen
in boot mode except me. The device says the current ROM is CyanogenMod-7-11072011-NIGHTLY-Desire[TyphooN_v3.7.5-MAGLDR].
Hope someone knows a way past this. Thanks!

you messed up something....
to flash HSPL4 you must boot to bootloader, not to magldr....
turn off phone and hold volume minus and power together until show three color screen... look picture in attachment
now you flash HSPL4....
also in my signature is tutorial how to flash WP7 to HD2....

Thanks for the reply. I just can't get that boot screen.. However, something seems to be wrong with that volume down button. When I'm in the MAGLDR menu and I press it sometimes it selects an option, sometimes it says:
ANDROID LOAD AT 11800000
from MicroSD
load zImage
K: /zImage
SD kernel open failed
and sometimes it highlights the option below (goes down, which I guess is what it is meant to do). The volume up button work fine, it goes up in the menu. When I boot Android both button work fine and turn the volume up and down. Any ideas? Is there any other way to get to that three color screen?

[TUTORIAL][CM11][4.4.2] CyanogenMod Tutorial for Sony Xperia Tablet Z (pollux)

I went through a lot of searching and trouble to install CM11 on my Xperia Tablet Z, and I'd like to share a tutorial I made for anyone who is also wanting to accomplish this.
All links are in Dark Green because I cannot post links yet.
1. Download and extract the ADB+Fastboot+Drivers zip (alexpja.com/sony/adb-fastboot-win.zip)
2. Now we’ll unlock the bootloader.
a. If you do not have a Phone app (like I don’t on the SGP351), you can either get the IMEI from About -> Status in the settings OR you can find the IMEI right after the IC code, nearby the barcode on the bottom of the tablet.
b. If you do have a Phone app, enter *#06# to retrieve the IMEI.
c. Save this for later use.​3. Place the tablet into fastboot mode and connect it to the computer.
a. Power off the device
b. Connect USB to computer
c. While plugging in the other side of the USB cable into the tablet, hold down the Vol + button.
d. If your speakers are on, you should a sound.
e. We have to install the drivers for fastboot. Open devmgmt.msc via the Run window or in the Start menu and in Other Devices section, you should see S1 Service or S1 Fastboot (anything containing S1).
i. If it is showing a yellow exclamation mark: Follow 3.e.i.1. If it is not, continue to 3.f.
1. We need to download Flashtool and use the driver setup. Download Flashtool (unrestrict.li/flashtool) and install it.
2. Find cmd.exe, right click it, and select Run as administrator.
a. Type in
Code:
bcdedit /set testsigning on
and press enter.
b. Reboot your computer.​3. Once you have rebooted the computer, open the folder where you installed Flashtool (default: C:\Flashtool).
4. Open up the drivers folder and open Flashtool-drivers.exe.
5. Select the first two driver choices (Flashmode and Fastboot) and select “Xperia Tablet Z Drivers” and continue.
6. A new window will appear, continue on with that.
7. A window like this may appear a few times, just press Install this driver software anyway.
8. Run 3.e.2. again and run
Code:
bcdedit /set testsigning off
. Reboot your PC now or after the tutorial.​f. The LED pulse light above it should be emitting a blue-ish color. The screen will be dark.​4. Now we’ll verify if you have fastboot running.
a. Open the tools folder that was extracted from the ADB ZIP and double-click on START.cmd to open Command Prompt in the current directory (all it does is literally open cmd.exe, you can edit the script to verify).
b. Run the command
Code:
fastboot -i 0x0fce getvar version
. If you get
Code:
<waiting for device>
, then you did something wrong. Retrace your steps! (For example, I get
Code:
version: 0.5
)​5. Go to (unlockbootloader.sonymobile.com) and continue until you reach the screen where you put type in the IMEI and an email address. Type in the first 14 digits of the IMEI (remove the last one) and your email address (not sure if name is required). You should get an email instantly with the key.
6. In the Command Prompt, run
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY is the key you received in the email from Sony.
7. Download whatever release you would like to use on the tablet (I’m using CM 11 nightly) from (download.cyanogenmod.org/?device=pollux)
a. Optional: Also download gapps for Google apps such as Gmail, Google Play Services, etc. (wiki.cyanogenmod.org/w/Google_Apps)​8. Extract the ZIP file (but don’t delete it either) and copy boot.img to the tools folder.
9. If your device is still turned off, turn it on and enable USB storage mode. Copy the CM zip to either the internal storage (sdcard) or, if one is inserted, the microSD card (sdcard1).
10. Place it into fastboot mode again (#3).
11. Go back into the Command Prompt and enter:
a.
Code:
fastboot -i 0xfce flash boot boot.img
b.
Code:
fastboot -i 0xfce reboot
c. Enter recovery.
1. Once it shuts down, rapidly tap the Vol + button in order to get into the recovery.
2. Grep_The_Truth's tip: Look at the LED. It will turn orange and afterwards it'll turn purple. You want to press Vol+ as soon as it changes colors.​12. Select “wipe data/factory reset” and wipe it. Afterwards, go back to main menu.
13. Select “Install zip” and either select “Choose zip from /sdcard” (internal storage) or “Choose zip from /storage/sdcard1” (microSD card).
I’ve had varying experience with installing from the /sdcard because sometimes it doesn’t want to mount /data while wiping (/data/media which is /sdcard is safe in wipe) the tablet, so if you were to install the zip from /sdcard with the error present, it would screw things up. I prefer the microSD card route (/storage/sdcard1), and you don’t even need a big one. 512MB works just fine. The actual path would be /sdcard/0/ when looking for the cm.zip in the internal storage.
14. When you have chosen to install from either /sdcard or /storage/sdcard1, select the cm.zip and install it.
a. If you downloaded gapps.zip, install it the same way as you did with the cm.zip.​15. Go back to the main menu now and select “reboot system now”
a. Once, I had the option to install root access before rebooting, I declined (was planning on rooting after tutorial) but it gave me root anyway.​
That’s it! You can now use CyanogenMod with the Sony Xperia Tablet Z.

Getting in to recopvery
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
c. Once it shuts down, rapidly tap the
Code:
Vol +
button in order to get into the recovery.
Click to expand...
Click to collapse
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.

Grep_The_Truth said:
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Click to expand...
Click to collapse
I'll add it along with mine, because I can do it with no problem.

alexpja said:
I'll add it along with mine, because I can do it with no problem.
Click to expand...
Click to collapse
alexpja Thanks for your tutorial, this is very detailed and easy to follow.
my Xperia is SGP321.
I put it into practice and the results it gives me the "oem unlock" is:
FAILED: (remote: Command nor allowed).
I guess you should treat my tablet has the bootloader locked and not allowed (for now??) the unlocked.
I hope someone gives us the opportunity to unlock the devices and in the future can be unlocked.

I had the same experience where at times the steps were a little confusing, especially for a beginner. Each set of instructions would either leave something out or skim over it as if everyone already knew it. That's understandable since they were probably written for that audience. I soft-bricked my SGP311 at least 10 times.
I was even going to write something like this but I got lazy.
One suggestion I would offer is to request the bootloader unlock key first since it sometimes takes a little while and a person can reduce the possibility of having to stop and wait just when they are making progress.
And for anyone going this route for the first time, don't make my mistake - flash exactly what the instructions say to flash, particularly boot.img. Once you have that recovery flashed you have a lot more control over your device. If something goes wrong in a following step like getting boot loops you can still fix it. But if you get annoyed and start poking at it then you can mess up the recovery. Then you have to reset everything to stock and just about start over.
While I don't want to say something stupid like claiming the tablet is indestructible, I found that whether I got stuck in a boot loop I couldn't get out of or screwed it up so bad that all I could get from the tablet was an occasional LED flash, I could always restore it using Emma. It's annoying to have to start all over but it's a huge relief when it boots normally.

for me flashing was fine and without any error but my Tab doesn't boot up with CM flashed...any idea?

Hanging at reboot
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.

Guess my bootloader won't be unlocked. This is A lot of work. Good job on the write up though maybe one day I'll tackle it.

BOOT LOOP Step 9
All was going well, but step 9 powering on device, now its looping.....Ill use flash tools to put jelly bean on and try again, since i was trying with kitkat...why i suspect kitkat is the issue, before i used to be able to unlock and lock boot-loader with jelly bean but with kitkat it didn't work, which i then forced it via cmd

No GPS
I used the tutorial for my Pollux Windy (WiFi Only) and used the latest nightly. everything went well but my GPS is now broken. Is this a known issue?

kevinsickles said:
Is this a known issue?
Click to expand...
Click to collapse
yep! use search to find out more.

mulebreath said:
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Click to expand...
Click to collapse
Hi,
I've been trying with my Xperia Tablet Z Wi-Fi SGP311. Ran into the same problem. On reboot command the LED was stuck on red for 10 minutes and the cmd window was still open. I unplugged the USB and the LED would not turn off. Tried some things, I don't remember specifically what, but it got the LED to turn off. Now my device can't be detected. I've downloaded Emma and it is not recognising my tablet. I've tried to plug the USB in while hold Vol +, Vol -, and the Power button. No detection for any. All I can do with my tablet is make the LED flash white, purple and red in rapid succession by holding Vol + and Power for 5 seconds.
Anyone know what's happened? I suspect I've completely bricked it :L
EDIT: Apparently there are different modes which you can cycle through. If you hold down Vol + and Power for 5 seconds, the LED will flash according to which mode the tablet is in. The different modes give these flashes:
- 1 White flash
- 3 Rapid which flashes
- A white, purple and red flash in quick succession
To switch between the modes, I hold down Vol+ and Power, and after 5 seconds it will take around 3 more seconds to change modes. One of these modes will not appear unless plugged into a PC. What do these mean and can I do anything with it? Tablet is still bricked.
EDIT2: I've managed to get Emma to recognise my tablet. Turns out the modes do have different purposes. I should be fine now, problem solved. I will just leave the solution here in case anyone runs into the same problem.
Unplug your device and hold Vol + and Power for 10 seconds. At the 5 second mark your LED should flash white ONCE. Keep both buttons held and within 5 more seconds, your LED will flash white THREE times consecutively. This will allow you to enter Flashmode (plug in USB while holding Vol -) and Fastboot (plug in USB while holding Vol +). For Emma to recognise your device, enter Flashmode and you can restore and try again.

Bootloop
I've tried many times to flash cyanogenmod onto my Xperia Tablet Z (SGP311). This is a Wi-Fi only tablet and I have downloaded the versions of CM from (download.cyanogenmod.org/?device=pollux_windy) I've followed all of the steps and tried all of the versions of CM down to 10.2 (I used GApps10.2 for CM10.2). Each version gets stuck in bootloop. I've cleared all data (in CWM - wipe data/factory reset, wipe cache partition, wipe delvik cache) before flashing CM and GApps; however, when I try to clear data I get an error. This is what the tablet says:
-- Wiping Data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cacha
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skiiping format...
Data wipe complete.
Click to expand...
Click to collapse
I'm thinking the "Error mounting /data" is the problem, but I'm not entirely sure, nor am I sure of how to fix it.
Any suggestions?
EDIT: Turns out I'm just really bad with Android stuff. I ended up flashing the original Xperia software, unlocking the bootloader (according to this tutorial's instructions), then I downgraded to 4.1.2, rooted my tablet (forum.xda-developers.com/showpost.php?p=53063218&postcount=14) and installed the PhilZ and TWRP custom recoveries. I didn't get to use them in the end. For some reason CWM kept coming up no matter what combination of buttons I pressed while rebooting. After downgrading and rebooting, I followed the rest of the instructions on this tutorial (from step 7). This time I got no errors while cleaning the disk, cache and delvik cache. Flashed the zip files, rebooted the device and voila, Cyanogenmod11!
Again, I'll leave this edit here in case someone runs into a similar problem. I couldn't get any version of CM until I rooted first.

I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!

tp_88 said:
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
download a proper stock (not bricked) firmware for your device and flash with flashtool.

Rootk1t said:
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Click to expand...
Click to collapse
What makes you think that the stock firmwares I've tried are bricked? I've since my post tried one which I downloaded through Flashtool - same result.

[Q] Hard Brick fastboot issues

Ok so here's what happened.
Couple days ago I mistakenly selected "install now" while attempting to postpone the OTA on my VS980. Phone was rooted on stock ROM via stump root and I had not installed a custom recovery yet.
Phone then would only show the LG screen and display an error. No download mode or recovery.
So I utilized a VM running Ubuntu and pushed the sdl1, aboot, rpm, tz and TWRP 2.7 to the phone.
upon restart of the phone It would only start up into fastboot mode. The only other thing it would do is bring up the hardware key mode ( done by pressing vol-, pwr, vol+ at the same time)
Phone would report two errors upon being plugged into the computer and the computer only recognizes the phone as an adb device in device manager
"EP1/out FAIL nfo=40pg0=f910700"
"usb_read() transaction failed"
So I installed the adb on windows and in terminal on Ubuntu. I also installed the unified LG drivers, SDK and the google USB drivers. I now get the same error messages but the fastboot mode now constantly resets.
here is what it goes through
"fastboot mode started"
"reset"
"portcharge"
"fastboot: processing commands"
"reset"
"EP1/out FAIL nfo=40pg0=f910700"
"portcharge"
"usb_read() transaction failed"
"fastboot: oops!"
"fastboot: processing commands"
"reset"
"EP1/out FAIL nfo=40pg0=f910700"
"portcharge"
"usb_read() transaction failed"
"fastboot: oops!"
"fastboot: processing commands"
this goes on and on....
any ideas on where to go from here?

You could try pushing fal.img like you've pushed those other files, rather than using the fastboot.

Id love too, but my comp isn't recognizing the phone when plugged in

Were you in bulk mode originally when you wrote the partitions to the phone? If so, i'm surprised you can't enter twrp. Just to rule out and error, be sure you're holding down power for no less than 15 seconds to power off the phone all the way. Then press and hold both volume down and power simultaneusly until the lg logo comes up. Then quickly release both buttons and immediatly press and hold them both again until the factory reset screen comes up. Accept factory reset to enter twrp.
If that is all a rehash, so be it. Just want to make sure you're using the correct method. Many people fail to hold down power long enough on the initlal shutdown making all the steps after that a moot point. Also you don't want to be connected to usb when doing the above procedure.