Database Users

WANTED: Sticky guide for newbies

Hi all
I have several years experience from rooting and applying all kinds of ROM's om both Symbians, Motorola OS, Android and WM devices but I am completely stuck when trying to "fix" the problem with non-existing SD card support on the Xoom.
What I have been looking for is a guide that walks you through Unlocking, Rooting, adding CWM and finally replaces the kernel with a "better" one. I have of course found all kind of guides on any of the topics above, but all of them assumes that you already have performed one or another of these steps.
So if anyone could be an angel and summarize the steps (links are ok) with the assumption that the reader (I) have
- oem locked
- no cwm installed
- unrooted
- Wifi only
- updated 3.1 honeycomb device.
I will certainly cry of joy if someone can do this for the good of the community. I am sure that many like I have already tried both this and that, and bricked or soft-bricked (I did) their devices while trying to get the god damned sd card to become functional . My own device has now been resurrected from coma (RSD Mode 2) and is now alive again, thanks to "fastboot oem unlock" but I can not for my life get the CWM to work. I have installed the recovery-Tiamat-R4c-100611-1150-cwm.img with fastboot. No errors reported either on the tablet och in Windows during flashing. But when pressing VolUp during boot, I just get stuck in "Starting RSD protocol support 3". I can boot normally if I dont press any button. Fastboot mode works too.

Below is a slightly modified of Land Master's NOOB guide. I have only updated a couple of links. I followed this guide when I originally rooted my Xoom, and it worked perfectly. But note that I have not tested this with the updates. All credit for this goes to Land Master!
USE THIS, AND ASSUME ALL RISKS. IT HAS NOT BEEN TESTED WITH THE UPDATED LINKS!
WIFI ONLY! WIFI ONLY! WIFI ONLY!
If you use this guide, or any other guide for that matter, make sure that you read it, reread it, (10 times!) and fully understand every step. One hour now, spent studying this, will save you 10 hours of headaches later. Make sure you follow every step EXACTLY!
"This tutorial was written for the NooB’s among us (like me) that are new to this stuff and are having a hard time “piecing together” all of the steps. While I am actually a not quite a beginner, NONE of these steps/methods/files have been developed by me. I have simply compiled the procedure in a document that I hope will be useful. With this in mind all the credit belongs to the many individuals that contribute in the XDA Developers forum. I have reviewed many posts by many people and have used all of the information along the way.
A)*Installing ADB
ADB stands for Android Debug Bridge and simplistically stated will be used to send commands to your XOOM using the keyboard on your PC. In essence your PC will be acting like a terminal. ADB is included in a package known as the Android SDK. The following steps should be taken to insure a successful install of the SDK, therefore giving you access to ADB.
1.*Install Java JDK :*http://www.oracle.com/technetwork/ja...ad-346242.html
a.*Download appropriate Java SE Development Kit (JDK) from link above
b.*Double click to Install JDK
c.*Accept Setup Defaults
2.*Install SDK Starter Package:*http://developer.android.com/sdk/index.html
a.*Download SDK Starter Package from link above. There are versions available for Microsoft Windows, Linux and Mac OS X. In case of Windows, both an installer and a zip file are available but there isn’t any need to use the installer as a formal installation is not required. Download the ZIP file.
b.*Once you have downloaded the SDK, simply extract the compressed file to a location on your computer. In our case, we have extracted it to the root of our C drive and that makes*C:\android-sdk-windows*the installation location of the SDK. From here onwards, we shall be referring to this location as the ‘SDK folder’.
3.*Download the SDK Platform Tools using the SDK Mamager.
a.*Browse to the SDK folder and launch SDK Manager.
b.*When launching it for the first time, it will present you with a window to choose packages to install. The first option begins with ‘Android SDK Platform-tools’. Make sure it is checked, and uncheck all the other packages for now. You can check/uncheck a package by simply double clicking on the package. Again, the only package you want to install is the Android SDK Platform-Tools.
c.*Once the process is done, you will have a ‘platform-tools’ folder inside your SDK folder. That folder will include ADB and all its dependencies.
d.*Make a copy of the File “fastboot.exe” which is in the “tools” directory and place it in the “platform-tools” directory.
B)*Install XOOM USB Driver
Just to be sure your XOOM is recognized by your PC it is recommended that you install the latest USB drivers for your system.
1.*Install MotoHelper :*http://www.motorola.com/Support/US-E...arging-Drivers
a.*Download the Driver with MotoHelper from the Link above
b.*Double Click downloaded file and follow on-screen instructions to install.
C)*Unlock Bootloader
Unlocking the bootloader gives you full control over the device so you can flash new Recovery’s, kernels, ROM’s, ETC.*THIS STEP*WILL DELETE ALL DATA AND SETTINGS ON YOUR XOOM.
1.*Put XOOM in Debug mode
a.*On the device, go to home screen, press*Apps*> >Settings>>Applications>>Development, and enable*USB Debugging.
b.*Now connect your XOOM to the PC via USB. New hardware installation should begin and it will start looking for and installing the drivers.
c.*A prompt should appear that states the drivers were installed successfully. On my PC the AutoPlay Device Options also appeared. I clicked “Open Device to View Files” and saw the device Storage with 27.8 GB free of 28.7 GB.
2.*Execute ADB Commands
a.*Open a command prompt by navigating to the ‘SDK Folder’, Holding the shift key, right clicking on the “platform-tools” folder and selecting “Open Command Window Here” from the popup menu.
b.*In the new command window type:*adb reboot bootloader*and press enter.
c.*Wait for the Dual Core screen with “Starting Fastboot protocol support” in the upper left corner to appear and then type:*fastboot oem unlock*in the command window and press enter. You should see: “To continue, follow instructions on the device’s display…”.*
d.*Read the WARNING on you XOOM and either Continue Below or Cancel following the on-screen instructions.
e.*If you decided to continue then on the XOOM Push Volume Down Button to change the selection from “Cancel” to “I accept” and then press the Volume Up to select that choice.
f.*You will be questioned again so Push Volume Down then Volume Up to confirm you want to UNLOCK your device. You will see “Device Unlock operation in progress…” “Formatting UDA”
g.*When the operation completes the device will read”Device unlock operation done – rebooting…” and the device will reboot. The windows new hardware “gong” will sound a couple of times during this procedure. After this step when my XOOM rebooted I also saw an “MTP Device” driver Install dialog box on my PC. Unplug the device, and quickly perform the initial set-up. You can “Skip” any steps that will allow you to (like WiFi setup). Just get back to the home screen and continue below:
h.*Verify that USB debugging is still enabled and if not re-enable it as outlined above.
i.*Re-connect your XOOM to the PC and close any AutoPlay dialog.
D)*Install Custom Recovery
A custom recovery allows you to flash files created by community developers such as ROM’s, Radios, Kernels, Themes, ETC. It also allows you to perform special tasks such as system backup’s, partitioning, cache wiping, ETC. As of 6/19/2011 the generally accepted custom recovery for the XOOM is ClockworkMod Recovery v3.2.2.0
a.*Download Clockwork Mod recovery image (not .zip file) from here:http://forum.xda-developers.com/show....php?t=1074979*
CAUTION: Do not install CWM 4.0.0.X from ROM manager!
b.*Place the File “recovery.img” that you just downloaded in the “platform-tools” directory
c.*In the previously open command window (if you closed it then re-open as described above) type:*adb reboot bootloader*and press enter.
d.*The device will reboot into bootloader mode (as described above) and when this completes type:*fastboot flash recovery recovery.img (name must match name of file)
e.*Check the screen of your XOOM and see: “Flashing StorMgr partition recovery STATUS: - done!*
f.*Type:*fastboot reboot*in the command window and press enter.
g.*Wait 3 second after the Moto logo is seen, then pushed Vol Down
h.* Android recovery menu visible, press Vol Up. Go straight into CWM.
i.*Navigate in ClockworkMod Recovery by using the volume up/down to “move” and the power button to “select”. Look for reboot system, highlight it and hit the power button. Your zoom will reboot normally.
OPTIONAL STEPS
l.*At some time later (AFTER YOU ARE ROOTED) to avoid the need to execute ADB commands to enter recovery, I suggest you look for a free application called “Quick Boot”, by Sirius Applications from the market.*
m.*Once Quick Boot is installed run it and simply select “Recovery” to boot into ClockworkMod.*
Next Step: Following Public Animal's guide to rooting >*http://forum.xda-developers.com/show....php?t=1075260*
Last step (optional) install Tiamat 1.0 ROM >*http://forum.xda-developers.com/show....php?t=1117004

Thanks a lot! I am with you all the way to step H (adb reboot recovery). This step ends with the Android, yellow triangle and an exclamation mark. Nothing more. So something must be wrong with the recovery image.
In both your links and other links to the recovery image, the name "recovery-solarnz-XXXXXX-XXXX.img" is used. But the links always leads to the image "recovery-Tiamat-R4c-100611-1150-cwm.img" instead. Could this be the problem? If so, what should the XXXXX be replaced with (for googling).
Thanks again for the guide. Sooner or later I *will* succeed!
Edit: Could this post be something that explains why my CWM flashing does not succeed? http://forum.xda-developers.com/showpost.php?p=13747198&postcount=18
And since the device still not is rooted, I can not rm the suggested files ... gaaah

pingvinen said:
Thanks a lot! I am with you all the way to step H (adb reboot recovery). This step ends with the Android, yellow triangle and an exclamation mark. Nothing more. So something must be wrong with the recovery image.
In both your links and other links to the recovery image, the name "recovery-solarnz-XXXXXX-XXXX.img" is used. But the links always leads to the image "recovery-Tiamat-R4c-100611-1150-cwm.img" instead. Could this be the problem? If so, what should the XXXXX be replaced with (for googling).
? http://forum.xda-developers.com/showpost.php?p=13747198&postcount=18
And since the device still not is rooted, I can not rm the suggested files ... gaaah
Click to expand...
Click to collapse
Not sure that I've completely understood your question, but when you type:*fastboot flash recovery recovery.img, make sure to replace the words "recovery.img" with the actual name of the recovery image file.

cam30era said:
Not sure that I've completely understood your question, but when you type:*fastboot flash recovery recovery.img, make sure to replace the words "recovery.img" with the actual name of the recovery image file.
Click to expand...
Click to collapse
Of course I do. Here is what I type
D:\Java\android-sdk\platform-tools>fastboot.exe flash recovery recovery.img
sending 'recovery' (3998 KB)...
OKAY [ 0.500s]
writing 'recovery'...
OKAY [ 1.031s]
finished. total time: 1.531s
D:\Java\android-sdk\platform-tools>
The tablet says "Flashing StorMgr partition recovery STATUS: - done!
I will try once more with the "timing trick" from this thread
http://forum.xda-developers.com/showthread.php?t=1078019

pingvinen said:
Of course I do. Here is what I type
D:\Java\android-sdk\platform-tools>fastboot.exe flash recovery recovery.img
sending 'recovery' (3998 KB)...
OKAY [ 0.500s]
writing 'recovery'...
OKAY [ 1.031s]
finished. total time: 1.531s
D:\Java\android-sdk\platform-tools>
The tablet says "Flashing StorMgr partition recovery STATUS: - done!
I will try once more with the "timing trick" from this thread
http://forum.xda-developers.com/showthread.php?t=1078019
Click to expand...
Click to collapse
The name of the file is "recovery-Tiamat-R4c-100611-1150-cwm". So you should type:*fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img

It actually worked! What I did was this
1. adb reboot bootloader
2. flashed the same recovery image that I mentioned earlier
3. fastboot reboot
4. applied the 3 second wait once the Moto logo was seen, then pushed Vol Down
5. Android recovery menu visible, press Vol Up. Now I got straight into CWM !!!
6. (prepared the sd card on my SGS with the zip files)
7. Choosed Install zip from sd card and flashed the wifi-root image
8. Reboot the tablet and verified with RomManager that I now had root
THANK YOU VERY MUCH FOR NOT GIVING UP ON ME

cam30era said:
The name of the file is "recovery-Tiamat-R4c-100611-1150-cwm". So you should type:*fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
For simplicity I renamed the zip to recovery.zip before copying it to the folder and flashing it (see next post also!)

I am going to modify the instructions. Is this correct for what you did?
"f.*Type:*fastboot reboot*in the command window and press enter.
g.*Wait 3 second after the Moto logo is seen, then pushed Vol Down
h.* Android recovery menu visible, press Vol Up. Go straight into CWM.
j.*When my device rebooted into recovery I also saw additional Device Drivers install. This took a little while and I waited to do anything until I received the “Device Driver Installed Successfully” dialog."

cam30era said:
I am going to modify the instructions. Is this correct for what you did?
"f.*Type:*fastboot reboot*in the command window and press enter.
g.*Wait 3 second after the Moto logo is seen, then pushed Vol Down
h.* Android recovery menu visible, press Vol Up. Go straight into CWM.
j.*When my device rebooted into recovery I also saw additional Device Drivers install. This took a little while and I waited to do anything until I received the “Device Driver Installed Successfully” dialog."
Click to expand...
Click to collapse
Yes, everything except the last step (j). I did not see anything on the computer screen. But now I have managed to install CWM, root it and install Tiamat 's latest kernel. The external sd card is now visible inside /sdcard/external! Success!

pingvinen said:
Yes, everything except the last step (j). I did not see anything on the computer screen. But now I have managed to install CWM, root it and install Tiamat 's latest kernel. The external sd card is now visible inside /sdcard/external! Success!
Click to expand...
Click to collapse
Post updated with your input. Thanks for being the first guinea pig!

cam30era said:
Post updated with your input. Thanks for being the first guinea pig!
Click to expand...
Click to collapse
This is an amazing guide! cam30era you and LandMaster are the bomb!
May suggest one thing? When reading it through, I think a real noob might be confused with the asterisks that are on either side of many of the adb commands.
Anyway this should definitely be a sticky!

actually I sat down and wrote my own guide, starting from scratch and ensuring that every assumption and requirement was explained. I called it "idiots guide to ..." . Maybe it would be a good idea to consolidate the best from both guides into a -definitive guide-. What do you think?
Oh, the thread is in the Android development forum. Mod is welcome to move it if so needed

pingvinen said:
actually I sat down and wrote my own guide, starting from scratch and ensuring that every assumption and requirement was explained. I called it "idiots guide to ..." . Maybe it would be a good idea to consolidate the best from both guides into a -definitive guide-. What do you think?
Oh, the thread is in the Android development forum. Mod is welcome to move it if so needed
Click to expand...
Click to collapse
Excellent idea. Go for it.
Sent from my Xoom using XDA Premium App

CWM won't boot.
For the life of me I can't understand what I'm doing wrong. US Wifi Xoom with 3.1, bootloader is unlocked, but not rooted. I use fastboot to flash the latest recovery img, 3.2.0 I beleive. Says it's successful, but like many on here when I either use "adb reboot bootloader" or if I time it and press volume down to get into the recovery, I only get a picture of the robot with the triangle. I can press volume up+power and I get the stock recovery.
I've read every post I can read but most people who have resolved the same issue were just not flashing the correct image. Which I'm sure I'm doing correctly.
Amy help would be appreciated.

bloglos said:
For the life of me I can't understand what I'm doing wrong. US Wifi Xoom with 3.1, bootloader is unlocked, but not rooted. I use fastboot to flash the latest recovery img, 3.2.0 I beleive. Says it's successful, but like many on here when I either use "adb reboot bootloader" or if I time it and press volume down to get into the recovery, I only get a picture of the robot with the triangle. I can press volume up+power and I get the stock recovery.
I've read every post I can read but most people who have resolved the same issue were just not flashing the correct image. Which I'm sure I'm doing correctly.
Amy help would be appreciated.
Click to expand...
Click to collapse
Try pingvinean's guide for "idiots " (no disrespect intended, that's the real name) in the development section.
Sent from my ADR6300 using XDA Premium App

cam30era said:
Try pingvinean's guide for "idiots " (no disrespect intended, that's the real name) in the development section.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
Thank you! Completely missed the part about the recovery being overwritten if I missed the timing and booted into honeycomb.

bloglos said:
Thank you! Completely missed the part about the recovery being overwritten if I missed the timing and booted into honeycomb.
Click to expand...
Click to collapse
Hehe, no disrespect but since the bookshelves are drenched in "for dummies" and "for idiots", I thought it might be ok to use that title. Glad that you finally succeeded!

How I went from rooted stock 4.5.9.1 to Cyanogen Pre-Beta

Hey,
I am in the process of going from stock (rooted) GB and wanted to document my steps. I am not a developer, I have no idea what I am doing, everything here is from links/guides elsewhere.
If you know of a faster/easier way to do it, please respond and I will update as required!
How can I Backup text messages/missed calls etc to cyanogen?
My System:
AT&T Atrix 4g with Stock Gingerbread OTA update (rooted)
Windows 7 x64 laptop
Guide:
My general understanding is as follows:
1. Unlock Phone
2. Download and Install CWM
3. Install Cyanogen
1. To unlock the phone we need to first get a few applications installed, I am running windows 7 so below are the files.
RSDLite 5.3.1 link
x64 Windows drivers
AT&T Unlocker
After downloading, install the first two packages, the third package will be used to unlock your bootloader:
Open a command prompt window
On Windows, press Start and type “cmd” then press the enter button
Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example: cd C:\Users\Kenneth\Desktop\fastboot-package)
cd your directory here
Power down your Atrix device
Hold the power button and the downward volume button until you see “Fastboot”
Let go of the buttons and press the upward volume button once
You will now see “Starting Fastboot protocol support”
Plug your device into a USB port in the back slot of your computer
Front slots sometimes do not have enough power to stay connected to the device.
Type the following command:
fastboot oem unlock
You will now receive a warning along with a unique device ID
Type the following commands using your unique device ID in place of the ####:
fastboot oem unlock ####
fastboot reboot
Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
Click to expand...
Click to collapse
2. CWM
CWM Download
how to install:
Windows:
unzip recovery-en-goapk.zip to D:\
open a CMD in windows.
fastboot flash recovery D:\recovery-en-goapk.img
Linux:
unzip recovery-en-goapk.zip to you home
mot-fastboot flash recovery ~/recovery-en-goapk.img
mot-fastboot reboot
3. Install Cyanogenmod
Download:
Cyanogenmod *REQUIRED*
GOOGLE Applications *Install if you want Market, Gmail, etc*
Restart into CWM
Wipe Dalvik
Wipe cache
factory/data reset
flash pre-beta.zip
wipe Dalvik
wipe cache
factory data/reset
reboot
IT COULD TAKE A LONG TIME TO BOOT, JUST WAIT UP TO AN HOUR
*Cyanogenmod*
Thanks to OP's and posters in the following locations:
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
http://forum.xda-developers.com/showthread.php?t=1136261
http://forum.xda-developers.com/showthread.php?t=1138541
http://forum.xda-developers.com/showthread.php?t=1206026

was this honestly needed?

You forgot the part where you have to flash pudding, which will softbrick your phone temporarily. This happens to all phones on stock GB when attempting to unlock them.
RSD flash the pudding sbf
phone will error with 0x1000 No OS found
choose fastboot
enter the documented unlock commands

firefox3 said:
was this honestly needed?
Click to expand...
Click to collapse
If it stops ONE person from asking for a guide on how to do this... it was needed.

how to install:
Windows:
unzip recovery-en-goapk.zip to D:\
open a CMD in windows.
fastboot flash recovery D:\recovery-en-goapk.img
Click to expand...
Click to collapse
This section has always bothered me because it can be confusing. Instead of referencing D:\ at all simply telling users to extract the img to the folder where they've installed the fastboot package would be clearer. Also at least some mention should be made of the fact that there is now a second CWM option running around in the dev forum which works with rom manager. It can be installed in exactly the same way as Tenfar's but to get it to work with rom manager you need to install the generic rom manager CWM through rom manager first, and then install the CWM version available in the dev forum.

sjbayer3 said:
How can I Backup text messages/missed calls etc to cyanogen?
Click to expand...
Click to collapse
search for mybackup root in the market. its free. =]

Congrats on being one of the few newbies who know how to read instructions.

It does help and I used rom manager to reinstall the updated version of cmr-at&t cmr- 4.0.1.4.atrix2 it has an sd.ext to view files in external sd and an. Asks if you want to delete s-ext during data factory reset just say no or you will ! fubar if that's were your .zip files are
Sent from outerspace from an unlocked alienv3 overclocked /faux123 kernel
Thanksyou. for all the great work !!!!!!!!
@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@

[GUIDE] Upgrading your Verizon r800x to CM9

Recently I posted about Sony/Verizon finally allowing meid unlock of the r800x.
I thought I'd come back and write up a little guide to help those of you that are wanting to upgrade your Verizon r800x device to a fresh install of CM9.
Things You'll Need
Unlocked Bootloader
Xperia Fastboot Drivers
Android SDK
Cyanogenmod 9 (I used the 2012-11-25 nightly)
Flash Tool (Links are under installation)
Verizon's 2.3.4 TFT
Gapps for CM9
Keiran & Atarii's CDMA Fix (There are some touchpad fixes out there too but I'm not covering those as I chose not to use them)
Recovery Play
Setup Stage
Download everything listed above.
Install Flash Tool and copy Verizon's 2.3.4 TFT into Flash Tool's firmware folder
You'll want to get Android SDK installed.
In the SDK manager, you want to be sure to have platform tools and Google USB driver checked and installed.
Unlock your bootloader following the steps on Sonys Unlock Bootloader webpage. Congrats your bootloader is now unlocked.
Start your phone and connect your usb connect your SD card to the PC.
Make a folder to store your rom setup files and copy the Cyanogenmod 9 Zip, Gapps, and Keiran & Atariis CDMA Fix Zip to that folder. Unmount USB Storage.
Back up your app data using Titanium Backup or some other tool to your SD card.
Navigate to the install path of your Android SDK and locate the platform-tools folder.
Open up the CM9 Zip file and extract boot.img to the platform-tools folder.
Also copy the recoveryPLAY.img to the platform-tools folder.
Run the command prompt and navigate to your platform-tools folder. Keep the command prompt open throughout this whole guide.
Code:
cd c:\program files\android\android-sdk\platform-tools
for example
Disconnect your USB cord from the phone and shut the phone off. Hold the search button and plug the USB cord back in.
You should see a blue light. If windows can't find the drivers for your fastboot, point it to the platform-tools folder.
Run the following code and when that is complete run the 2nd command:
Code:
fastboot boot recoveryPLAY.img
fastboot reboot
Unplug your usb and press the back/return button on your phone until you see ClockworkMod show.
Navigate to backup/restore and choose to backup your phone (home is up, list is down, search is enter). We are doing this incase something goes wrong with with your Cyanogen install, in which case you will simply restore your phone.
Poweroff the phone.
Start Flash Tool, press the lightning icon and select flash mode. Select Verizon's 2.3.4 TFT and click next.
Hold the back button on your phone, insert the USB cord, and press the power button to start flash mode when flash tool asks you to.
Boot your phone and activate your service using verizons *228 program. After the phone reboots, turn it off.
Back at your command prompt, run the following codes and then immediately unplug the USB cord.
Code:
fastboot flash boot boot.img
fastboot reboot
Your phone should start and you should see a FXP boot screen, start pressing the volume down button to enter into recovery.
Navigate through clockworkmod using your vol up/down keys and choose the install zip from SD option (home is enter).
Select choose zip from SD card and navigate to your CM9 zip you copied to your SD card earlier. Select yes.
After install completes, repeat the step above but this time choose your Gapps Zip file.
Lastly repeat the step again and this time choose Keiran & Atariis CDMA Fix Zip.
Reboot your phone and hopefully if everything went well, your phone will start up into the OS after a minute or two.
Go through the setup that pops up (you shouldnt need to activate your service, you did that previously in the fresh 2.3.4 install).
Lastly open up voice dialer and say Open APN and it should come up with an option to Open APNs. Select it.
That should bring you to a screen and there should be an option for Verizon Wireless, select that and return to your home screen. You're done.
If for whatever reason you encounter problems. Boot into recovery and restore your 2.3.4 backup.
I am not responsible for any botched upgrade attempts. You assume the risk when you unlock your bootloader and all modding attempts made on it.
This guide was writen as a suggested route one can take for upgrading your phone and any problems encountered along the way were not my doing.
Search the Xperia Play Forums if you encounter any weird problems.

This is a great guide! Good luck CDMA users! First
Sent from my Xperia Play using xda app-developers app

You'll need a kernel too. Get LuPuS CM9 Kernel, and get rid of the recovery thing. LuPuS comes with it built in.

DubleJayJ said:
You'll need a kernel too. Get LuPuS CM9 Kernel, and get rid of the recovery thing. LuPuS comes with it built in.
Click to expand...
Click to collapse
I used the one that game with the cm9 download. But people are free to try whatever they want.

DubleJayJ said:
You'll need a kernel too. Get LuPuS CM9 Kernel, and get rid of the recovery thing. LuPuS comes with it built in.
Click to expand...
Click to collapse
how do i get rid of recovery and is this safe? also whats the point?

frozty95 said:
how do i get rid of recovery and is this safe? also whats the point?
Click to expand...
Click to collapse
What I meant was, skip the recovery part, and don't flash the kernel that comes with CM9. Get LuPuS CM9 kernel. Has it's own built in CWM (6.0) and it's great. Tons of useful features.

Thanks For The Guide it helped alot!

Help. Bootlooping?
Thanks for writing this guide. I"ve read that the initial boot in to CM9 takes forever, but how do I decide if I've waited too long and I'm bootlooping? Also, all of the procedures I've read talk about fixing a boot loop by returning to the stock firmware. I want CM9 and don't want to return to stock.
dt674 said:
Recently I posted about Sony/Verizon finally allowing meid unlock of the r800x.
I thought I'd come back and write up a little guide to help those of you that are wanting to upgrade your Verizon r800x device to a fresh install of CM9.
Things You'll Need
Unlocked Bootloader
Xperia Fastboot Drivers
Android SDK
Cyanogenmod 9 (I used the 2012-11-25 nightly)
Flash Tool (Links are under installation)
Verizon's 2.3.4 TFT
Gapps for CM9
Keiran & Atarii's CDMA Fix (There are some touchpad fixes out there too but I'm not covering those as I chose not to use them)
Recovery Play
Setup Stage
Download everything listed above.
Install Flash Tool and copy Verizon's 2.3.4 TFT into Flash Tool's firmware folder
You'll want to get Android SDK installed.
In the SDK manager, you want to be sure to have platform tools and Google USB driver checked and installed.
Unlock your bootloader following the steps on Sonys Unlock Bootloader webpage. Congrats your bootloader is now unlocked.
Start your phone and connect your usb connect your SD card to the PC.
Make a folder to store your rom setup files and copy the Cyanogenmod 9 Zip, Gapps, and Keiran & Atariis CDMA Fix Zip to that folder. Unmount USB Storage.
Back up your app data using Titanium Backup or some other tool to your SD card.
Navigate to the install path of your Android SDK and locate the platform-tools folder.
Open up the CM9 Zip file and extract boot.img to the platform-tools folder.
Also copy the recoveryPLAY.img to the platform-tools folder.
Run the command prompt and navigate to your platform-tools folder. Keep the command prompt open throughout this whole guide.
Code:
cd c:\program files\android\android-sdk\platform-tools
for example
Disconnect your USB cord from the phone and shut the phone off. Hold the search button and plug the USB cord back in.
You should see a blue light. If windows can't find the drivers for your fastboot, point it to the platform-tools folder.
Run the following code and when that is complete run the 2nd command:
Code:
fastboot boot recoveryPLAY.img
fastboot reboot
Unplug your usb and press the back/return button on your phone until you see ClockworkMod show.
Navigate to backup/restore and choose to backup your phone (home is up, list is down, search is enter). We are doing this incase something goes wrong with with your Cyanogen install, in which case you will simply restore your phone.
Poweroff the phone.
Start Flash Tool, press the lightning icon and select flash mode. Select Verizon's 2.3.4 TFT and click next.
Hold the back button on your phone, insert the USB cord, and press the power button to start flash mode when flash tool asks you to.
Boot your phone and activate your service using verizons *228 program. After the phone reboots, turn it off.
Back at your command prompt, run the following codes and then immediately unplug the USB cord.
Code:
fastboot flash boot boot.img
fastboot reboot
Your phone should start and you should see a FXP boot screen, start pressing the volume down button to enter into recovery.
Navigate through clockworkmod using your vol up/down keys and choose the install zip from SD option (home is enter).
Select choose zip from SD card and navigate to your CM9 zip you copied to your SD card earlier. Select yes.
After install completes, repeat the step above but this time choose your Gapps Zip file.
Lastly repeat the step again and this time choose Keiran & Atariis CDMA Fix Zip.
Reboot your phone and hopefully if everything went well, your phone will start up into the OS after a minute or two.
Go through the setup that pops up (you shouldnt need to activate your service, you did that previously in the fresh 2.3.4 install).
Lastly open up voice dialer and say Open APN and it should come up with an option to Open APNs. Select it.
That should bring you to a screen and there should be an option for Verizon Wireless, select that and return to your home screen. You're done.
If for whatever reason you encounter problems. Boot into recovery and restore your 2.3.4 backup.
I am not responsible for any botched upgrade attempts. You assume the risk when you unlock your bootloader and all modding attempts made on it.
This guide was writen as a suggested route one can take for upgrading your phone and any problems encountered along the way were not my doing.
Search the Xperia Play Forums if you encounter any weird problems.
Click to expand...
Click to collapse
---------- Post added at 10:46 AM ---------- Previous post was at 10:23 AM ----------
swing4thefence said:
Thanks for writing this guide. I"ve read that the initial boot in to CM9 takes forever, but how do I decide if I've waited too long and I'm bootlooping? Also, all of the procedures I've read talk about fixing a boot loop by returning to the stock firmware. I want CM9 and don't want to return to stock.
Click to expand...
Click to collapse
I fixed it: I booted in to Recovery mode by holding the volume down button and then I used it to wipe user data. Then rebooted and booted in to CM9 in less than 2 minutes.

Is there any way to do this with out activating your phone? I have a Galaxy Nexus and don't wan to deactivate it just to flash a rom.

LAcube said:
Is there any way to do this with out activating your phone? I have a Galaxy Nexus and don't wan to deactivate it just to flash a rom.
Click to expand...
Click to collapse
Um i'd assume so. But this is for the xperia play, not galaxy nexus. Try checking Galaxy Nexus Forums

swing4thefence said:
Thanks for writing this guide. I"ve read that the initial boot in to CM9 takes forever, but how do I decide if I've waited too long and I'm bootlooping? Also, all of the procedures I've read talk about fixing a boot loop by returning to the stock firmware. I want CM9 and don't want to return to stock.
---------- Post added at 10:46 AM ---------- Previous post was at 10:23 AM ----------
I fixed it: I booted in to Recovery mode by holding the volume down button and then I used it to wipe user data. Then rebooted and booted in to CM9 in less than 2 minutes.
Click to expand...
Click to collapse
Yeah i actually had this happen to me a few times on other roms. It usually boils down to wiping cache/dalvik after the install, and sometimes user data.

No worries, found what I needed.

Nice guide, but going from GB to ICS on XP is more of a downgrade...
Sent from my R800x using xda app-developers app

so the Verizon's 2.3.4 TFT both links wont work what can i do ?

dt674 said:
Um i'd assume so. But this is for the xperia play, not galaxy nexus. Try checking Galaxy Nexus Forums
Click to expand...
Click to collapse
Sorry, I didn't explain my self right. Since the phone I'm currently using right now is Galaxy Nexus and is activated and my Xperia Play is not in service, is there another way to flash CM9 without having to activate your Xperia Play? (Step 21)

When i do the fastboot flash boot boot.img it says everything did well but my phone wont boot. I dont know what im doing wrong...

The Verizon's 2.3.4 TFT file seems to be down.

the links for verizons android 2.3.4 no longer contain the file. can anybody point me to the right direction where i can obtain the file.

Problem with step 19
Hi guys
flashtool is not recognizing the Verizon's 2.3.4 TFT file. i copied and pasted the file in the firmware of the flash tool but its not showing up in the firmware section. I notices that the file extenetion is .ftf inseted of .tft i changed the extention to .tft but it still didnt show up.

I don't know what tft is (it's FTF) but I have the 2.3.3 (.88) and the 2.3.4 (.57) both on my dropbox account. Just click my link and foloow it to the correct folder and file. Enjoy.

[Beginners Guide] Unlock & Custom ROM your TF300

I have been asked to port my "Beginners Guide" from the TF700 forum for the TF300. Since both tablets are very similar, that was not too hard to do
If I have missed to update a link specific for the TF300, do let me know please.
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
These instructions assume that you are on the latest Asus bootloader: 10.6.1.27.5
To determine which bootloader you currently have:
From an "Off" state, boot the tablet with Volume Down and Power into the bootloader menu. Read the small script in the upper left. You'll see
US_epad-10.6.1.27.5-20130801" or similar.
US or WW, JP, CN is your SKU or region
10.6.1.27.5 is your bootloader version
20130801 is the build date (and immaterial in most cases).
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
This is just common sense. It is not inherently risky to flash custom ROMs. But something can wrong at any time and you have to be careful. If you are, this is a safe procedure.
Basically the process of flashing a custom ROM on the TF300 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recovery​
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Go to Asus website: https://www.asus.com/support/Download/28/1/0/9/8BmzkQ4yoz5WzBrW/32/
Choose "Android" for OS and look for the "Utilities" on the resulting page.
Download the Asus Unlock Tool v7 (not v8! It says v7 is for ICS but it'll work fine on JB - see below)
The tool downloads as a .rar file which is an archive you have to decompress. 7zip is a free and very good Windows tool that will do it for you
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk you extracted from the .rar archive to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
Update 2/15: Google added another wrinkle: It now checks even sideloaded apps and refuses to install them if they are considered not secure. The Unlock tool seems to fail their test. v8 does not install at all anymore. v7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet
July 2015: And another wrinkel... It seems to be pretty consistent now that the Unlock Tool hangs on the Google account password step. I suspect something changed on the Google side. It probably doesn't allow the tool to check/compare the password anymore. There have been quite a few security changes lately and the unlock tool never gets updated so I suspect that Google now is blocking access by the tool to it's servers.
The work-around is easy enough: Delete the Google account from the tablet (Settings > Accounts), then run the tool again. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool
Click to expand...
Click to collapse
This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never.... This problem is widely discussed on several forums. Google it if you hit that roadblock.
To check if you are unlocked, boot the tablet and read the tiny script. It should say:
The device is unlocked.
Installing a custom recovery on your tablet
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up. Try it but do not push Volume Up when the 'Wipe data' icon is flashing!​
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it to get the drivers, then uninstall the program from your PC if you don't want it. The drivers will stay.
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows Vista, 7, 8, 10:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for adb) and the corresponding drivers. Takes about 15 seconds.
On Windows 8 and 10 you need to turn off the driver verification feature. Here's a great video on how to do it:
https://www.youtube.com/watch?v=afrvSGiMAtk
Or - even better - here's a quick command line toggle to achieve the same (thank you @Jack_Hardin):
Jack_Hardin said:
If you're running W10, you can disable Device Driver Signing without following the procedure in the linked video, but by (more simply) right-clicking on the Start button, selecting Command Prompt (Admin) and then typing:
Code:
BCDEDIT /set nointegritychecks ON
Doing the same with OFF at the end of the string, as easy to guess as it looks, will reenable them.
Click to expand...
Click to collapse
Jack_Hardin said:
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Win7 and Win8 users seem to have the best luck wth the drivers sbdags provided here: http://forum.xda-developers.com/showthread.php?t=2646279
It's fine if you want to use his Recovery Install Tool from that thread. But I highly recommend you familiarize yourself with basic fastboot commands! There are lots of tuturials all over the web.
Linux:Check out this site https://code.google.com/p/adb-fastboot-install/
iOS:[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers or:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8: Shift + right click and select "Open command window here".
For Win XP click here
select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
Click me: View attachment 3070087
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the drivers I linked to above. And if Windows does not cooperate at all, PM me and I can hook you up with a Puppy Linux live CD with fastboot/adb set up already.
Let's assume everything is good:
On your computer go here: https://dl.twrp.me/tf300t/
Download the latest version of TWRP.
FYI ONLY: If, for whatever reason, you want to format your data partition:
Formatting /data starting with TWRP 2.7.x and later takes a lot longer than in previous versions (up to 90 minutes). LET IT FINISH. DO NOT INTERRUPT THE FORMATTING.
Rename the file to twrp.blob and place it into the same directory as your fastboot.exe. Note: More recent versions of TWRP download with an .img extension. Leave the extensions as is, rename the first part to watever is easy to type
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
or
Code:
fastboot -i 0x0B05 flash recovery twrp.img
This will flash the recovery to the recovery partition
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
You may get a dialog in TWRP offering to root the stock rom. You can accept or cancel it - doesn't matter. I assume you are going to install a custom rom and they are rooted anyway.
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet. TWRP is very user friendly. You basically cannot do anything of consequence "by accident", so don't be shy.
To create your Nandroid (a full system backup) touch "Backup", leave the default selection as they are and swipe the button to create a nandroid of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Hint:
It's a good idea to have at least one good nandroid on external media. Sooner or later you will format your data partition and if you're like me, you may forget to backup your nandroids in the heat of the moment..
Installing a custom ROM
From here on out it's as easy as downloading the installation file of your custom ROM, booting into TWRP, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you see a "signed" in the zip file name (best_rom_ever_signed.zip), make sure you check "verify zip signature" under the "Install" menu. Some devs sign their ROM zips - a better way to ensure file integrity than md5 sum.
Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: http://forum.xda-developers.com/transformer-tf300t/development
It is mandatory to do a Factory Wipe in TWRP before installing a custom ROM or going from one ROM base to another (a so called clean install).
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES - AND I REPEAT: NEVER! - use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
FREE ADVICE
There are alternative methods to flash a recovery to your device using apps like GooManager (currently not supported anyway), TWRP Manager or Flashify from the Play Store which do it right from your tablet. These apps "save you the trouble" of getting ADB and fastboot set up and working on your PC. These methods still exist and they do work - mostly - and if you have root. But I would not recommend them.
If you are not willing to invest the time to learn the basics about ADB and fastboot (google "adb fastboot xda tutorial") and install the necessary drivers on your PC, you should not be flashing anything to your tablet!
GET ADB AND FASTBOOT WORKING!
Sooner or later you will do something stupid (I have done it and so will you) and ADB/fastboot may save your bacon IF you had it working when you didn't really need it.
Hit the 'Thanks' button and rate the thread 5 stars if this helped you
Click to expand...
Click to collapse

Save it for later

Mine

sbdags said:
@stamatis could we sticky this please.
Brilliant post Bernd :good:
Click to expand...
Click to collapse
Can we make that happen here to @stamatis
Thx Josh

Nice one Bernd! :good::good:

boot sequence
Hi,
Is normal to see three TUX and some phrases at the power on ?
Can I hide it ?
tnkx
Nicola

You mean the penguins?
That's normal I'd you're running a Rom that uses _that's preinit scripts. You can't hide them - why would you?

thank you SO much
I love you!
Wow, I've never had so much trouble rooting a device before! And days ago, I rooted my T700 without any problems. So, I guess I should have expected the hubby's TF300T to be problematic! Recoveries didn't work, I tried multiple ones. Eventually, I had a recovery that didn't recognize any partitions. I used fastboot to erase them all and put the stock ROM back on--wouldn't boot up. This thread was an immense help! I've moved the other recoveries and ROMs into my non-working folder!
Thanks again!
Lynne

Awesome
What a well written guide! I have a decent understanding of fastboot and adb (although minimal experience), and I perfectly understood every step.
My advice to all newbies like me.... Read stuff ALL of the way through (and understand it), BEFORE stepping off in it.

ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris

scuzzo said:
ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris
Click to expand...
Click to collapse
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh

lj50036 said:
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh
Click to expand...
Click to collapse
hello,
bootloader is unlocked or at least it says it is at the boot screen.. "your device is unlocked"..
real time... just swapped ports... its says it pushed the recovery.... so... will continue along this path.... and see how it goes.... i think its good to go... just as you suggested... port swap... cool... i bought this just so i could root it and put the kit kat kis rom on it.... thanks for your help and big ups to OP.... great guide ...
thanks again.!

Nice guide!
I've been wanting to put a custom rom on my transformer for a long time. This guide worked like a charm.
The only problem I had was when I tried to flash TWRP recovery, but switching USB port fixed that problem.
I flashed the latest CM12.1 nightly and it works fine.
Many thanks!

Help please, I'm stuck!
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks

You won't see anything on the tablet screen, but what does the command window say?
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk

berndblb said:
You won't see anything on the tablet screen, but what does the command window say?
The command window didn't say anything, just blinking cursor after my command line
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Mishka79 said:
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks
Click to expand...
Click to collapse
Thanks,
After writing the question, I've restarted my tablet and did all the steps again.
The second time everything worked as it should. :good:
thanks for your great guide

Really great guide
Amazing guide thanks for the help

Thank you for this good tutorial but I have one question.
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!

ANDROIDYER said:
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!
Click to expand...
Click to collapse
I have not used CM in quite a while but I think you have to enable root in Developer Options. I think it is not enabled by default.
If hat does not work you can go to Chainfire's website and download the flashable SuperSU and just flash it in recovery

Thanks and a couple of notes on TF300T
Thanks so much for the great guide. My 300TF was nearly bricked due to slowness and freeze-ups. I'd stopped using it. The process worked and am now running KatKiss. Couple of problems and their solutions for anyone who may have the 300TF:
-When trying to "Unlock Bootloader" I kept getting to "enter Google password" but when I did so (correctly) it was not accepted. The solution was to do another factory reset and NOT install google services. Didn't ask for password after that.
-Used fastboot command line to install "twrp.blob" but nothing happened and it timed out. I had to take out other usb connect programs first (in my case "easy-tether" and my LG phone connect app.) After that everything went as per your guide.
Thanks again
Geneg

Sony Z5 Compact [E5803] (suzuran) Recovery install / root

QUICK STORY:​I UPDATED THE LINKS LINEAGEOS OFFICIAL WEBSITE REMOVED THEM! THESE ONES WORK.
Hi everyone, me and my friend we searched the whole internet for a compatible official recovery, which was impossible, and we were able to find one, after we flashed it we noticed that it was very unstable and it didn't recognize our SD CARD. The ROM and GApps were on that SD card. The system was not booting, the classical SONY logo was stuck. So after recompiling my own version of this recovery I was able to read the sd card. I know it's hard to root XPERIA phones, that's why I wanted to publish a working version for E5803. Not tested on E5823 but theoretically it should work, which you can do on your own risk.
Feel free for the thumbs up :good: :good:
I'll give the links using BASE64 encryption. Use 'base 64 decode . org' without spaces. Enter the random text and get the link.
THE PROCCESS:
Know that you are doing this on your own risk.
READING THIS TUTORIAL TILL THE END BEFORE ACTING.
Backup your device before even starting.
Your bootloader unlocked in your developer options (to enable developer options [system Info] --> [Build Number / tap 7 times]). Don't forget to enable USB Debugging, that's in the developer options too.
DOWNLOAD THE RECOVERY IT'S WORKING and tested (and compiled by me ): aHR0cHM6Ly9kcml2ZS5nb29nbGUuY29tL29wZW4/aWQ9MWljTWdNeEpsS0ZrSUN3WERRTEhPWXVoWkc3WGRLTnB4
Download ADB on your PC you can just install Minimal ADB and Fastboot. aHR0cHM6Ly9hbmRyb2lkbXRrLmNvbS9kb3dubG9hZC1taW5pbWFsLWFkYi1hbmQtZmFzdGJvb3QtdG9vbA== After that your PC has to grant access to your phone via ADB. To do that open Minimal ADB and fastboot and type
Code:
adb shell
. Make sure your phone's screen is unlocked while doing that and of course your Phone has to be plugged in. A pop-up will appear, you have to accept it and CLICK REMEMBER. Don't forget that one.
Make sure you install Your Xperia Z5 Compact Drivers. Use this link: aHR0cHM6Ly9kZXZlbG9wZXIuc29ueS5jb20vZmlsZS9kb3dubG9hZC94cGVyaWEtejUtY29tcGFjdC1kcml2ZXIv To install them extract the files, and and right click the files ending with .inf , after that you can click install. Do that to both of the .inf files in the directory.
Get your BOOTLOADER CODE using this link: aHR0cHM6Ly9kZXZlbG9wZXIuc29ueS5jb20vZGV2ZWxvcC9vcGVuLWRldmljZXMvZ2V0LXN0YXJ0ZWQvdW5sb2NrLWJvb3Rsb2FkZXIv Scroll down and Select your device, after that just Accept and tick the boxes below, and enter your IMEI number and click submit. If you have 2 SIM Cards you have technically 2 IMEI numbers, enter your first IMEI and click submit. Save that code very very well.
Now enter your fastboot mode by typing
Code:
adb reboot bootloader
. Then you wait for your blue light on your cellphone. After that you have to type this code
Code:
fastboot oem unlock 0x<insert your unlock code>
. Insert your code in that 'insert your unlock code' area but don't forget to remove the brackets around, and no space after '0x'. Voila! You unlocked your bootloader!
Now you have to flash the recovery using:
Code:
fastboot flash recovery /pc_file_path/twrp.img
. The file path has to be given on your PC. If it worked you can simply type
Code:
fastboot reboot
to reboot your system. After that use you can boot to your recovery using
Code:
adb reboot recovery
. Of course you have to say (optionally) Allow modifications and don't show that again, to the pop-up that will appear.
NOW JUST IN CASE you are the unlucky person and can't boot to your recovery do the following steps: First use
Code:
fastboot boot imagepath.img
to boot to your recovery but temporary, while doing this you have to be in the fastboot mode. Then after the boot to your recovery make sure that your ROM, GApps and RECOVERY.img file is on your sd card / internal storage. In recovery mode click install and say install image and select your .img file you wanted to install. now reboot to your recovery again, after shutting down your device. It'll work this time. If you just wanted to install a recovery, boot your system and do what you want, or install Magisk or SuperSU, your call.
If you want to install a custom ROM you can install your ROM and GApps you want to your own way. Just for an example I'm giving a LineAgeOs 14.1 ROM link which has no bugs I noticed: aHR0cHM6Ly9kcml2ZS5nb29nbGUuY29tL29wZW4/aWQ9MUVvS3VlbzNjTmVBRmlOaEVXYTBiX2ZWVDFkUkhQREti and the mini GApps for the minimalistic Google Apps setup: aHR0cHM6Ly9vcGVuZ2FwcHMub3Jn
Select ARM64, Android 7.1 and mini and click that download button after the choices you made.
After those downloads, or if you have the files copy them to your device memory or sd card. You can do that outside the recovery mode. Now wipe your System, Cache, Dalvik-cache, Data, but not internal storage if your ROM files and stuff are there. If they are on your sd card you can wipe your internal storage. If your files are on your micro-sd don't wipe your micro-sd (just a fact don't forget that).
Now click on install, then select your lineageos file or custom ROM swipe for the install, do the same for the GApps after that. Now you can reboot and wait, that can take 10 minutes or something like that.
Don't forget to say thanks :good:
Have a nice day and good 'rootings'

How are we supposed to use the download links?
[Edit]
My bad, I didn't read what I was supposed to read.
Sorry...

Kestnix said:
How are we supposed to use the download links?
[Edit]
My bad, I didn't read what I was supposed to read.
Sorry...
Click to expand...
Click to collapse
It's fine but the problem is they removed the links recently but I'll update the link ASAP. As I can see you guys can't download the official LineageOS ROM for now.

Thanks for the great guide!
Everything went smoothly, but when I try `adb reboot recovery` or `fastboot boot <img>` it reboots to a blank screen. Any ideas?
Edit:
Volume down + power gets me into TWRP, but then I borked everything trying to install magisk. Thanks again!

spdqbr said:
Thanks for the great guide!
Everything went smoothly, but when I try `adb reboot recovery` or `fastboot boot <img>` it reboots to a blank screen. Any ideas?
Edit:
Volume down + power gets me into TWRP, but then I borked everything trying to install magisk. Thanks again!
Click to expand...
Click to collapse
Your Welcome

Guys I need help, how do I boot to twrp without pc I'm using a sony e5803 because when I type "adb reboot recovery" it just boots to my home screen. I also tried "fastboot boot imagepath.img" and it says FAILED (remote: 'dtb not found") Can anybody help?
Edit : I got to work now, I figured out that the problem is is didn't update my android i was still on lollipop when I flash a global firmware and flash twrp it work fine.

Thanks - Still working fine. Great guide.

thanks