WANTED: Sticky guide for newbies - Xoom General

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!

Related

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] Unlocking HTC Desire HD using HTCDEV method and installing CyanogenMod

I'm pretty new here but as I documented the process of modding my own phone I thought I'd share it with you. I didn't invent any of these processes and this information is available from many different sources. I've tried to credit any source material that I've used verbatim. I am by no means an expert.
Please reply back with any corrections and I'll be happy to edit the post.
This guide describes how to take a HTC Desire HD (mine was fully patched with OTA updates including Sense 3.0), unlock it and install CyanogenMod onto it. It worked for me but it might not for you. I don't take any responsibility for you turning your phone into a brick!
Pro Tips
Remember, in any steps requiring the phone to be powered off, just give it a minute to make sure that it is properly turned off.
Understand what's happening! If you get what's going on, you've more chance of fixing it if it goes wrong. This process describes how to use HTCs official method to unlock the bootloader. This allows you to change the operating system on the phone. The phone contains a recovery system which we an engineer can boot into to replace the main operating system if it becomes unbootable. We are going to replace this stock recovery system with a modified one which allows us do fiddle about with the phone's internal partitions. Once we have the modified recovery system in place we use it backup the existing phone operating system and replace it with a modified one. We can also use it to restore the original one again if things go wrong.
Read all of the instructions properly first! Don't go off half-****ed!
As far as I'm aware you can't reverse the official HTC bootloader unlock (i.e put your phone back *exactly* as it was) and it may effect your warranty. You have been warned!
Unlock the Bootloader
INFO: You can use the HTCDEV unlock bootloader method from HTC as an 'official' means of unlocking the bootloader. Confused? Check out the official site: http://htcdev.com/bootloader/ I'm not going to describe it step by step here because HTC do that quite well enough themselves.
Quick tip. If when going from one step to another on the HTC website you come to a white screen, that may be because you've been logged out. Just go back to the first page, log in again, then go back to the last step you completed.
Another quick tip. Make sure you properly install everything HTC tells you to. We'll need it all later...
Installing recovery mode
INFO: The stock recovery mode itself is pretty basic and can't do much, so we need to replace it with a custom recovery image.
We're going to use the clockworkmod recovery image which you grab from here: http://dl.dropbox.com/u/4518713/archive/recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-ace.zip (originally seen here: http://forum.xda-developers.com/showthread.php?t=1118865)
Make sure that the fast boot mode on your phone is disabled. You can find this in your power settings menu.
If the phone is connected via a USB cable then unplug it.
Power off the phone using the power button and leave it alone for a minute.
INFO: To flash the new recovery image to the phone, you need to reboot the phone into the bootloader so that you can select a new image to boot. The bootloader is known as HBOOT.
Boot into HBOOT by holding down the 'volume down' button and pressing the power button.
By default FASTBOOT is selected so just press the power button to access it.
Attach the USB cable and note that FASTBOOT changes to FASTBOOT USB
On your PC open cmd prompt and cd to the platform-tools directory of the android sdk. Mine is at C:\Program Files (x86)\Android\android-sdk\platform-tools>
Copy the .img file from the clockworkmod zip file we downloaded earlier to the platform-tools directory. Rename it recovery.img
Go to your command prompt and issue this command:
Code:
fastboot flash recovery recovery.img
INFO: The recovery image will then be written to your phone, and as long as everything went well you'll get a message saying OK.
Ensure that BOOTLOADER is selected in the HBOOT menu and press POWER button to select it. Now you're back at the HBOOT menu.
Use the volume buttons to highlight RECOVERY and press the power button to select it. After showing you the HTC logo, the phone should boot into recovery mode!
Backing up your phone
Using the volume buttons to select move to the 'backup and restore' option in the menu. Use power to select and use the backup option. This backs up your current phone setup to the SD card.
Select power off to turn off you phone. Leave it a few secs - select reboot system now.
When your phone is backup and running, mount it in mass storage mode and navigate to the root of your SD card. See the folder called 'clockworkmod'? copy that along with everything in it to your computer and put it somewhere safe. That's your backup. If needs be, you can use this backup your phone back to the original state!
Installing CyanogenMod (other mods may vary)
Mostly taken from http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide with some extra stuff that messed with me when I tried to do it.
Download the latest version of CyanogenMod from http://download.cyanogenmod.com/?type=stable&device=ace
Download the Google Apps for the device. http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
Place the CyanogenMod update.zip file on the root of the SD card.
Place the Google Apps .zip on the root of the SD card also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and the power button to select.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
And the option to wipe the Dalvik cache
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Select Install zip from sdcard
Select Choose zip from sdcard
Select the Google apps zip
These extra steps seem to have been required by people in this thread. All credit due to marsdta and theluckster for their suggestions. I've edited this guide to include the instructions here where they are more visible.
On your computer extract the ROM zip (e.g. update-cm-7.1.0-DesireHD-signed.zip) and there should be a file inside it called boot.img. This should be flashed automatically, however for some reason via the HTCDEV method it is not.
To do it manually, you need to enter fastboot mode, as per the instructions above:
Boot into HBOOT by holding down the 'volume down' button and pressing the power button.
By default FASTBOOT is selected so just press the power button to access it.
Attach the USB cable and note that FASTBOOT changes to FASTBOOT USB
Then on your PC, in the directory you extracted the zip file run:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Once the installation has finished, select Go Back to get back to the main menu, and select the Reboot system now option. The phone should now boot into CyanogenMod.
Now wait for what seems like an incredibly long time with the phone showing the 'htc' screen.
INFO: The phone should now boot into CyanogenMod!
Restoring your phone - When things go wrong
OK, so you flashed a bad mod. Time to restore.
First up, put the backup you made in the previous step onto the root of your SDcard (if it isn't already there). Then, I came across this video which seems to explain things pretty well
http://www.youtube.com/watch?v=mUYGe8mmNWU
The basic gist of it is, boot into recovery mode, format the cache, data and system partitions, wipe the Dalvik cache, then restore the backup from your SD card.
Wow thanks a lot!
I personally have 1 problem:
Step 12 of the "installing recovery mode" when i type in the command in command prompt is says:
'error: cannot load recovery.img'
I placed it in the same folder as fastboot en renamed it "recovery.img".
I unlocked the bootloader succesfully btw..
Any thoughts?
I think you should contemplate using attn1's ace hack kit to gain bootloader unlock instead of voiding your warranty.
Hunt3r.j2 said:
I think you should contemplate using attn1's ace hack kit to gain bootloader unlock instead of voiding your warranty.
Click to expand...
Click to collapse
Well I've already unlocked the bootloader through htcdev.
But tried the Attn1's as well...ended up saying:
/data/local/tmp/goldcard.img: cannot open for read: No such file or directory
starting downgrade...
** The phone will now reboot into HBOOT.
** It will then check the file just sent.
** If everything is okay, the phone will
** prompt you to continue by pressing
** VOLUME UP. It will reboot, flashing twice.
The phone did not prompt me to continue by pressing volume up.
When i start clockwork recovery it states i should root my phone...
So a lot going wrong and i can't figure out what..
how long the htc screen? I'm waiting for a looooong time
Thanks for the tutorial. I've followed the instructions and managed to unlock the bootloader and install ClockworkMod, however after flashing CM7 and rebooting it is stuck on the H3G boot screen (isn't flashing CM7 supposed to overwrite the boot logo?). I'm trying to flash:
update-cm-7.1.0-DesireHD-signed.zip
gapps-gb-20110828-signed.zip
I've double checked /data, /system, /cache and Dalvik-Cache have been wiped before flashing but still no avail
Here are the versions from the bootloader:
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011, 14:28:19
I am able to restore the backup, but flashing any other ROM just doesn't boot.
The guide is missing one key step . Flashing the boot image.
So after flashing your from boot back into boot loader and flash your roms boot.img.(just copy it over to your fast boot file)
Then run the command
Fastboot flash boot boot.img
Reboot . Done.
You'll have to do this every time you flash different roms. 4ext has a nice feature of doing this for those that have HTC unlocked you should try it out
Sent from my Inspire 4G using XDA
Awesome, thanks marsdta! It is working now, good work!
thelucster said:
Awesome, thanks marsdta! It is working now, good work!
Click to expand...
Click to collapse
can you repeat it more clear for me because i have the same problem.
Thank you Thelucster. You have saved me from a big mistake.
crom1 said:
can you repeat it more clear for me because i have the same problem
Click to expand...
Click to collapse
First flash the Cyanogen ROM and Google Apps, as per the instructions above. Then on your computer extract the ROM zip (e.g. update-cm-7.1.0-DesireHD-signed.zip) and there should be a file inside it called boot.img. This should be flashed automatically, however for some reason via the HTCDEV method it is not.
To do it manually, you need to enter fastboot mode, as per the instructions above:
Boot into HBOOT by holding down the 'volume down' button and pressing the power button.
By default FASTBOOT is selected so just press the power button to access it.
Attach the USB cable and note that FASTBOOT changes to FASTBOOT USB
Click to expand...
Click to collapse
Then on your PC, in the directory you extracted the zip file run:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I didn't set notifications on this post and forgot it existed till today. I've updated the guide with the information posted by marsdta and theluckster to make things clearer. Sorry about any confusion caused by missing that step out.
the boot screen shows cyanogen(mod)7 instead of the regular HTC sign!! Following each and every step I landed up here. And now I am stuck, cuz this boot screen has been there for like half-an hour....does it mean something is wrong or does it take this much time to load first???
Hello,
for HTC dev unlocked bootloader (about what is added after step 15 in "installing cyanogen" phase) : it seems that the boot.img must be flashed before installing the .zip from sdcard.
I got stuck for that. Could be worth to make it clear.
Great tutorial anyway, thank you !
zarkenciel said:
Hello,
for HTC dev unlocked bootloader (about what is added after step 15 in "installing cyanogen" phase) : it seems that the boot.img must be flashed before installing the .zip from sdcard.
I got stuck for that. Could be worth to make it clear.
Great tutorial anyway, thank you !
Click to expand...
Click to collapse
It shouldn't matter. I've seen people do it both ways and it worked fine for them.
@ash win. Your in a boot loop. Did you do a full wipe before flashing? Could be just a bad flash. Go back and reflash the rom and boot.img. you should also verify the md5hash to make sure yous didn't get a corrupt download file.
Just finished the tutorial, works perfectly. Thanks for writing it.
Does this unlock you from the network, i.e. is this the alternative to paying £15 for an unlock code?
I do understand this is for modding and flashing to a new ROM, but I am wondering if it also unlocks the phone from your network (or maybe that is IMEI based).
This is not for any illegal purposes, just I fancy a new ROM and I am now out of contract, so happy to experiment with flashing.
ohforfs said:
Does this unlock you from the network, i.e. is this the alternative to paying £15 for an unlock code?
I do understand this is for modding and flashing to a new ROM, but I am wondering if it also unlocks the phone from your network (or maybe that is IMEI based).
This is not for any illegal purposes, just I fancy a new ROM and I am now out of contract, so happy to experiment with flashing.
Click to expand...
Click to collapse
No, you need the aahk for that. That gives you sim unlock as well. Just Google attn1 aahk and you'll find it
marsdta said:
No, you need the aahk for that. That gives you sim unlock as well. Just Google attn1 aahk and you'll find it
Click to expand...
Click to collapse
Thanks - very kind of you to point me in the right direction, I've found it
Hi,
and how do i root my phone after HTCDev Unlock??
I want install the Custom Rom "Sabsa Prime". Do i need root to flash it?
Sorry for my bad english.
You may also want to include wiping battery stats in the advanced option of cwm in your guide

Step by step procedure to root mz604 and flash ics custom rom

Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
• Your custom ROM will be: http://goo.im/devs/teameos/roms/nightlies/wingray/
• Your GOOGLE APPs (GAPPs) would be: gapps-ics-20120429-signed.zip http://goo.im/gapps
Full thread in details can be found here: http://forum.xda-developers.com/showthread.php?p=20479464
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html • Recovery Image: http://goo.im/devs/teameos/recoverie...ecovery-r6.img
• GAPPS: http://goo.im/gapps, your GAPPs would be: gapps-ics-20120429-signed.zip
• ROM: http://goo.im/devs/teameos/roms/nightlies/wingray/
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to:
Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 40 - 50 seconds).
Advice: purchase Startup Manager from the market. Remove unwanted user programs from the startup. That will boost the boot time of your xoom. and don't remove superuser or superSU.
To have better battery life, from the market buy JuiceDefender ultimate. configure it as aggressive. don't worry, it is ok. This will give you around 2 hours of extra battery life than the promised 10 hours. Keep that in the startup.
You may need after that to install terminal emulator from the market if not already installed by the ROM to check if you have root permissions. Just type "su -" you will be prompted with superuser check. Click allow. and then type "id" You will see your id is root.
Should you require further details or assistance, please let me know. And enjoy the best rom customized ever for your device
Best Thanks to TEAM EOS for the great ROMs they provide.
After you are done with all that, let me know and will explain to you how to work with the pre-installed gooManager in the new ROM. It will make your life much easier to upgrade to future releases of your ROM.
Note: if you are coming from eos rom, there is no need to wipe data. Wipe cache and dalvik are enough.
If you are coming from another rom other than eos roms, or rooting for the first time, wipe data is needed as well. Enjoy...
Sent from my MZ601 using Tapatalk 2
Great guide! I was waiting for someone (I was too lazy myself) to create a guide that skipped right to the good stuff: Custom Roms.
One thing though: After "fastboot flash recovery eos-recovery-r6.img" aren't you supposed to reboot, and then immediately go into recovery, just so that the system doesn't bring back the old one? Or am a dreaming things (again)?
Hi yosterwp. My pleasure to be part of xda community mate.
Well, after flashing recovery, within adb, I am asking to reboot fastboot and and rebooting recovery. Then rebooting system is mentioned there. That is why I am asking to use the volume button and power button combinations to prevent it from going to old rom and directly go to recovery to flash eos rom
Sent from my MZ601 using Tapatalk 2
wesamothman said:
Hi yosterwp. My pleasure to be part of xda community mate.
Well, after flashing recovery, within adb, I am asking to reboot fastboot and and rebooting recovery. Then rebooting system is mentioned there. That is why I am asking to use the volume button and power button combinations to prevent it from going to old rom and directly go to recovery to flash eos rom
Sent from my MZ601 using Tapatalk 2
Click to expand...
Click to collapse
Ahh, efficient and direct for the noob in all of us! I expected nothing less from you; great job!
At step 1 of "To flash the other ROM downloaded above", I get this:
http://i.imgur.com/lsItx.jpg
What am I doing wrong?
EDIT: If it helps, when I flash the recovery image, I get this:
http://i.imgur.com/BdZRM.jpg
Is that right?
Also, when I try to enter recovery, I get this:
http://i.imgur.com/pWUZS.jpg
(and before I get that I get the same Android outline with 2 spinning cogs inside, then it changes to that)
I don't actually get into recovery (first image I posted) until I press the Vol Up and power buttons at the same time.
EDIT 2: Disregard all that!
I got it all working using this, and XxLordxX's Lord AIO Tool.
Installed the ROM and GAPPS from this though.
ICS looks so damn nice on this I LOVE ANDROID!
Hey. I am happy you got all that working
For the previous images you posted, it seems boatloader was not unlocked and that is a pre-requisite for Recovery installation.
Now that it is working, Enjoyyyyyyy ICS
wesamothman said:
Hey. I am happy you got all that working
For the previous images you posted, it seems boatloader was not unlocked and that is a pre-requisite for Recovery installation.
Now that it is working, Enjoyyyyyyy ICS
Click to expand...
Click to collapse
Hmm. I ran through the bootloader unlocking on the device, changing the option with the arrow keys then it said
"Formatting UDA" then said it was finished..
Anyway, it's working now, and CWM works (obviously, as I now have the custom ROM installed).
Sent from my HTC One X using Tapatalk 2
EDIT -- never mind got it figured out!
ok i did these two steps
adb reboot bootloader
fastboot oem unlock
and the device rebooted back into HC like it was when i took it out of the box
now when i run adb devices it doesnt see it and if i do adb reboot bootloader it says device not found
dodgefan67 said:
EDIT -- never mind got it figured out!
ok i did these two steps
adb reboot bootloader
fastboot oem unlock
and the device rebooted back into HC like it was when i took it out of the box
now when i run adb devices it doesnt see it and if i do adb reboot bootloader it says device not found
Click to expand...
Click to collapse
Cool. Now ICS is ON?
wesamothman said:
Cool. Now ICS is ON?
Click to expand...
Click to collapse
yeah i found the thread to put the US rom on it, got the official HC from motodev and updated it OTA to ICS 4.0.4!! patiently waiting for JB now
Spanish Xoom?
Hi.
I have an Spanish Xoom Wifi, and I'm concerned about if this ROM (wingray):
- will work in my european/spanish XOOM?
- will allow me to change language and keyboard layout to Spanish?
- can this "english" ROM "brick" my device ? (I don't know if flashing an US or NON-Spanish rom in my Spanish device can brick it).
Thanks.
NoP_Compiler said:
Hi.
I have an Spanish Xoom Wifi, and I'm concerned about if this ROM (wingray):
- will work in my european/spanish XOOM?
- will allow me to change language and keyboard layout to Spanish?
- can this "english" ROM "brick" my device ? (I don't know if flashing an US or NON-Spanish rom in my Spanish device can brick it).
Thanks.
Click to expand...
Click to collapse
Yup. It works well on your device.
For spanish keyboard, get smartkeyboard and spanish addon. Enjoy.
Sent from my MZ601 using Tapatalk 2
Device Not found
I've installed the SDK and Motorola USB drivers as instructed.
When I attach the Xoom, I hear the device connect chime. I even saw the fastboot driver message say "complete" with the happy green checkmark.
However, when I run:
adb reboot bootloader
I get error: device not found.
I tried the LIAOT tool and it also hangs up looking for the device.
Thx for any advice.
---------- Post added 13th July 2012 at 12:20 AM ---------- Previous post was 12th July 2012 at 11:44 PM ----------
I've installed the SDK and Motorola USB drivers as instructed.
When I attach the Xoom, I hear the device connect chime. I even saw the fastboot driver message say "complete" with the happy green checkmark.
However, when I run:
adb reboot bootloader
I get error: device not found.
I tried the LIAOT tool and it also hangs up looking for the device.
Thx for any advice.
What does adb devices say? Use another USB port and use the USB cable it came with
Hahleq said:
I've installed the SDK and Motorola USB drivers as instructed.
When I attach the Xoom, I hear the device connect chime. I even saw the fastboot driver message say "complete" with the happy green checkmark.
However, when I run:
adb reboot bootloader
I get error: device not found.
I tried the LIAOT tool and it also hangs up looking for the device.
Thx for any advice.
---------- Post added 13th July 2012 at 12:20 AM ---------- Previous post was 12th July 2012 at 11:44 PM ----------
I've installed the SDK and Motorola USB drivers as instructed.
When I attach the Xoom, I hear the device connect chime. I even saw the fastboot driver message say "complete" with the happy green checkmark.
However, when I run:
adb reboot bootloader
I get error: device not found.
I tried the LIAOT tool and it also hangs up looking for the device.
Thx for any advice.
Click to expand...
Click to collapse
You need to make sure that usb debugging check box is checked under settings.
Sent from my Xoom using Tapatalk 2
rooted, flashed
Hi everyone.
I would like to thank you for all the developers here, for the information on how to do it. Without you guys I would stuck with stock honeycombe 3.2 here in the UK. I have been waiting for an official update OTA ics 4.0 for months, but still no sign if other Xoom users will ever get it.
Did it first time rooted, flashed, now running team eos wingray 4.0.4 ics, on my xoom mz604, what a huge improvement.
Thank you again for all of you!
We are here one community to help out. By the way jellybean is out for your device if you are interested.
Sent from my Xoom using Tapatalk 2
wesamothman said:
Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
• Your custom ROM will be: http://goo.im/devs/teameos/roms/nightlies/wingray/
• Your GOOGLE APPs (GAPPs) would be: gapps-ics-20120429-signed.zip http://goo.im/gapps
Full thread in details can be found here: http://forum.xda-developers.com/showthread.php?p=20479464
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html • Recovery Image: http://goo.im/devs/teameos/recoverie...ecovery-r6.img
• GAPPS: http://goo.im/gapps, your GAPPs would be: gapps-ics-20120429-signed.zip
• ROM: http://goo.im/devs/teameos/roms/nightlies/wingray/
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to:
Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 40 - 50 seconds).
Advice: purchase Startup Manager from the market. Remove unwanted user programs from the startup. That will boost the boot time of your xoom. and don't remove superuser or superSU.
To have better battery life, from the market buy JuiceDefender ultimate. configure it as aggressive. don't worry, it is ok. This will give you around 2 hours of extra battery life than the promised 10 hours. Keep that in the startup.
You may need after that to install terminal emulator from the market if not already installed by the ROM to check if you have root permissions. Just type "su -" you will be prompted with superuser check. Click allow. and then type "id" You will see your id is root.
Should you require further details or assistance, please let me know. And enjoy the best rom customized ever for your device
Best Thanks to TEAM EOS for the great ROMs they provide.
After you are done with all that, let me know and will explain to you how to work with the pre-installed gooManager in the new ROM. It will make your life much easier to upgrade to future releases of your ROM.
Click to expand...
Click to collapse
AFTER adb reboot bootloader shows me adb not found in command prompt
some archive txt tells me that adb si moved and i need to donwload platforms tools via sdkmanager....is this correct?
thanks for the guide! i need some help with this!
MARIANOTE said:
AFTER adb reboot bootloader shows me adb not found in command prompt
some archive txt tells me that adb si moved and i need to donwload platforms tools via sdkmanager....is this correct?
thanks for the guide! i need some help with this!
Click to expand...
Click to collapse
Check step 4. Your Cmd have to be in SDK/tools, wherever that us, example, c:/SDK/tools/
Sent from my MZ601 using Tapatalk 2

[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

[REF] [ROOT] [RECOVERY] [BOOT LOADER] Metro PCS LG K7 LGMS330 [Guide For Dummies]

I have not been on this site since posting my guide, i do want to let any future people reading this know that, I am not a professional. everything in this guide is using stuff from other peoples threads.... this thread is just step by step directions on how i rooted (and installed TWRP on) MY lg k7 (MetroPCs). Also i had to root before i unlocked the boot loader. Which is not safe, you should probably unlock the boot loader before you root, but i couldn't figure out how to unlock it without root access.
I AM NOT RESPONSIBLE FOR ANY THING THAT HAPPENS TO YOUR DEVICE!
YOU AND ONLY YOU CAN BE HELD RESPONSIBLE​
~BACK UP FILES ON PC, YOUR PHONE WILL BE RESET TO FACTORY SETTINGS DURING THIS TUTORIAL~
Step One: Enable Dev Options
A) open settings>about phone>software info then tap "Build Number" really fast about 10 times
B) open settings>Developer Options, then check the box labeled "Enable OEM Unlock", and the box Labeled "USB Debugging"
Step Two: Install Android SDK/ADB/USB drivers
A) go to http://developer.android.com/sdk/index.html in your browser, and click download...
B) go to https://www.microsoft.com/net/default.aspx in your browser, and click the big blue button that says .NET
Framework 4.6.1 or X.X.X depending on when your reading this...
C) go to http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html scroll down until you get to the first box, labeled Java SE Development Kit 8u91 or XuXX Depending on when your reading this, then find your OS (ex: Windows x86, Mac OS, Linux, Etc..), then select the download link
Step Three: Installing LG K7's USB Driver's
A) unlock your phone
B) plug your phone into you Computer via USB
C) pull down your notifications, Tap on the USB icon which should be labeled "Media Device (MTP)," "Send Images (PTP)," or "Charge Phone"
D) if a dialogue box pops up asking to install drivers tap install, if not proceed to step E
1) Your PC should ask you if you want to auto run, Either auto run or open the folder and run LG_PC_Programs.exe then proceed to Step Four
E) select "Media Device (PTP)," if not already selected
1) click the three vertical dots next to the magnify glass in the upper right hand corner, select install pc drivers, then tap install
Step Four: Installing Java SE
A) return to the folder where you downloaded the files in step two, install the file which contains the word java in it
Step Five: Installing Microsoft .NET 4 Framework
A) now in the same folder as step four, install the with the name "NDP461-KB3102438-Web," the name might be different then mine depending on when you are reading this
B) if it is already installed it will notify you and you can proceed to the next step
Step Six: Installing Android Studio 2.0 (SDK/ADB Drivers)
A) in the download folder from step four & five, double click the remaining file, the name should contain the words "android", and "studio" in it
B) when the dialogue box opens requesting admin rights, select allow
C) click next
D) click next
E) make sure all boxes are checked and click next
F) read the license agreement, (unless your the 99.9% that doesn't) click i agree
G) you may click next or choose where you'd like to install android studio, and where you'd like to install SDK, for this tutorial i will change make a new folder in my docs named SDK then change the SDK install dir to My Docs
H) click next
I) it will take a moment to install so just wait
(note: the progress bar will fill up, then reset, as it is installing in two separate locations)
J) when finished, click next
K) uncheck the box and click finish
Step Seven: Root your device
(Note: I rooted before i unlocked my boat loader, as i could not get it to boot into boot loader mode until i rooted it)
A) go to http://www.kingroot.net/wap on your android device and download the apk file
B) go to settings>security and check the box labeled "Unknown Sources"
C) install the apk
Video tutorial for king root here: https://www.youtube.com/watch?v=tG_ruuTPVpU
(Not my channel or video)
D) open the king root app
E) make sure you have a charged battery or your phone is plugged in as the rooting process time may vary (better safe then sorry)
F) swipe up until you see a "TRY IT" button click it
G) under "Root Access not available" tap "Get Now
H) do not turn off your phone
I) when it is done you can tap optimize now if you wish, otherwise close the app
Step Eight: Replacing KingRoot with SuperSU ~ W0lfDroid Method
A) go to http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
B) scroll down until you see the word "download:" (should be right above the related posts
C) click on the "new link" next to "Replace_Kingroot_With_SuperSU.zip"
D) extract the .zip so that the "MRW" folder is on your internal storage
(Easiest way is to download it on PC and open up your k7 in "my computer" and select internal storage and drag the MRW folder inside the .zip there)
E) go to google play and search "terminal emulator for android" or use this link if your reading this on your phone https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
F) install the first one, or use this link if your reading this on your phone https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
G) open terminal emulator
H) type "su" without the quotations
(everything typed in the terminal is case sensative)
I) type "sh /sdcard/mrw/root.sh" without the quotations
J) you might see a few errors, that is fine
K) wait until it says finished
L) when SU opens, select "update" "install" or what ever pops up
M) when it asks to uninstall, uninstall it, it is not uninstalling SuperSU it is uninstalling Kingroot,
O) if 30 minutes pass and it is still uninstalling then exit the app and then reboot the phone
DO NOT STOP HERE ~ YOU HAVE TO UNLOCK THE BOOTLOADER, and OPTIONALLY FLASH TWRP
Step Nine: Unlocking The Bootloader
A) refer to step one and double check the OEM unlock is enabled and USB debugging is turned on
(If not then please enable them)
B) search quick boot on the google play store download the first app it should be a circle with a lightening bolt
C) open quick boot
D) when asked to "allow root access?" tap allow
E) if an add pops up close it with the ex in one of the corners
F) tap on the word boot loader
G) at the top of your phone you should see " * Welcome To Fast Boot Mode : "
H) now go to your SDK dir, in my case it is C:\Users\USER\Documents\SDK
I) hold shift, then right click on the "platform-tools" folder, then select "open command window here"
J) in the CMD window type "fastboot devices" - without quotations
(everything is case sensative)
K) then type "fastboot oem unlock" - without quotations
L) then type "fastboot getvar unlocked" if that doesn't work try "fastboot getvar" or "fastboot getvar unlock" to confirm if it is unlocked
(if non of the getvar commands work you did something wrong, and i wont be able to help you, but if you followed the tutorial you shouldn't have any issues as these are the exact steps i took)
M) then type "fastboot reboot"
LEAVE THE CMD OPEN OR YOU WILL HAVE TO REPEAT steps H-I
Step Ten: Flashing TWRP
A) go to http://forum.xda-developers.com/general/general/qa-metro-pcs-lg-k7-lgms330-t3331678 and click on the latest download for twrp for me it is BETA1
if the links on that page dont work then use the links here http://forum.xda-developers.com/showpost.php?p=66282525&postcount=42
B) extract the download into your SDK folder on your PC
C) in the sdk CMD window from Step nine
D) type "fastboot devices" - without qoutation
E) ~optional, HIGHLY RECOMENDED~
1)type fastboot "boot twrp-image-3.img" - this will boot up twrp WITHOUT flashing it, just so you can make sure everything is working right
in my case it was twrp-image-3.img check your twrp file name and replace fastboot boot twrp-image-3.img with
fastboot boot INSERT YOUR FILE NAME HERE.img
2)in twrp tap reboot>bootloader
F) when bootloader mode opens back up
G) type "fastboot flash twrp-image-3.img" or "fastboot boot INSERT FILE NAME HERE.img" depending on your file name
H) when finished flashing type "fastboot reboot"
Step eleven
A) follow instructions on step one
B) the reason you must do this is because when you flash TWRP it erases your entire phone and resets it
Congrats you have Successfully Rooted, Unlocked Your Bootloader, and Flashed TWRP, to your LG K7
Well done, my friend. Well done indeed.
[QUOTE
Congrats you have Successfully Rooted, Unlocked Your Bootloader, and Flashed TWRP, to your LG K7[/QUOTE]
is this ok with the gapps 5.1 instsall .zip for twrp install or should i use a different? also, do you have a suggested camera app? awesome thread btw. Nevermind simple twrp install fixed everything.
I have tribute 5 and can't access bootloader or install SuperSU.....always fails.
How can I get this to work?
Today backup important files you need!
Is this a real method BC everybody having problems rooting this device so I ask can u make a video and add screenshots
Sent from my LG-D800 using Tapatalk
I can confirm this method works. The only different thing i did was purchase Supersume pro from playstore. Worked like it said it would. The Ls675 is rootable. But no bootloader unlock or bootloader at all for that matter. Im running MS330 with TWRP full root and have twrp backups and fastboot flashable backups via flashfire....
---------- Post added at 02:28 AM ---------- Previous post was at 02:20 AM ----------
https://mega.nz/#!CRAVWAyI!QIbo20-0ZnVqlREs7ZXF66aB_Eh3UjCEMVQbLuP1Zec
https://mega.nz/#!zBoxGIQR!buXvorPkA14Vr2Idn7uhNPHanOL6wbvcEav3MhRdjv8
https://mega.nz/#!yQBg1ayC!r3qvWfLjCAKg0e8t91J1IEtae8_EwhvYTXjawv7b_2A
Screen shots of root, flashfire backups, and device info
While it does work I can find no method using the buttons to get into twrp all the instructions I find for recovery fail so I can only boot back to it after the phone boots, thus it's worthless at this point. Also the command is fastboot flash recovery imgagename.img and you'll need to remove kingroot from administrators to uninstall.
Anyone else been able to boot directly into twrp from the off position?
zgauthier8286 said:
I can confirm this method works. The only different thing i did was purchase Supersume pro from playstore. Worked like it said it would. The Ls675 is rootable. But no bootloader unlock or bootloader at all for that matter. Im running MS330 with TWRP full root and have twrp backups and fastboot flashable backups via flashfire....
---------- Post added at 02:28 AM ---------- Previous post was at 02:20 AM ----------
https://mega.nz/#!CRAVWAyI!QIbo20-0ZnVqlREs7ZXF66aB_Eh3UjCEMVQbLuP1Zec
https://mega.nz/#!zBoxGIQR!buXvorPkA14Vr2Idn7uhNPHanOL6wbvcEav3MhRdjv8
https://mega.nz/#!yQBg1ayC!r3qvWfLjCAKg0e8t91J1IEtae8_EwhvYTXjawv7b_2A
Screen shots of root, flashfire backups, and device info
Click to expand...
Click to collapse
can you please help me i have 2 MS330 that are bricked
callihn said:
While it does work I can find no method using the buttons to get into twrp all the instructions I find for recovery fail so I can only boot back to it after the phone boots, thus it's worthless at this point. Also the command is fastboot flash recovery imgagename.img and you'll need to remove kingroot from administrators to uninstall.
Anyone else been able to boot directly into twrp from the off position?
Click to expand...
Click to collapse
Try to do the factory hard reset trick but say no at the second screen. I haven't tried it out yet but I've been reading around several sites and that's a possible solution
zgauthier8286 said:
Try to do the factory hard reset trick but say no at the second screen. I haven't tried it out yet but I've been reading around several sites and that's a possible solution
Click to expand...
Click to collapse
Just reboots. Think we're going to have to change something? Boot image? Kernel?
callihn said:
Just reboots. Think we're going to have to change something? Boot image? Kernel?
Click to expand...
Click to collapse
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Does anyone know a way to successfully root this phone? Not just recover?
Sent from my LGMS330 using Tapatalk
callihn said:
Just reboots. Think we're going to have to change something? Boot image? Kernel?
Click to expand...
Click to collapse
Of other interest 5.1 is very dendent on Google apps and move app updates to the system via TB or Link2SD fails more than it succeeds, shows they moved but app inaccessible afterwards hence brick. Mine went down trying to integrate play services and reinstalling from adb didn't help. FYI if you relock the BL it'll lock the phone with a security error too. Moving play services causes unending error screens so you can't really see if it's done moving, but I waited a good 5 minutes before reboot. Issue on fails could have been the system not being r/w. Needless to say backup, backup, backup as I hadn't because I've never had a serious issue doing that and considered it a trivial task. Anyone had good success with integrating updates and cache? Anyone restored from twrp yet?
JayCouture.com said:
Does anyone know a way to successfully root this phone? Not just recover?
Sent from my LGMS330 using Tapatalk
Click to expand...
Click to collapse
Yes! Just follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=66456635&postcount=1
zgauthier8286 said:
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Click to expand...
Click to collapse
Can you figure out why we can't boot to recovery via hardware buttons? That's critical for tinkering and testing on the go since I always have my phone but not my laptop for booting into recovery with adb. Not sure exactly where to look, probably start with a search for the words "recovery" and "safe mode" for the buttons and "security error" in the boot.img files.
callihn said:
Can you figure out why we can't boot to recovery via hardware buttons? That's critical for tinkering and testing on the go since I always have my phone but not my laptop for booting into recovery with adb. Not sure exactly where to look, probably start with a search for the words "recovery" and "safe mode" for the buttons and "security error" in the boot.img files.
Click to expand...
Click to collapse
If your rooted u can dl a reboot recovery app on the play store I have one that works like a charm. But im gonna take a look through Linux at the kernel options using make menu_config and see if there's anything I can see in there.
zgauthier8286 said:
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Click to expand...
Click to collapse
im having a problem w the security 9 error boot loop. only seem to b able to get it into download mode , not bootloader or recovery. would your boot and recovery img's help me at all ya think ? thanks !
goitalone said:
I have tribute 5 and can't access bootloader or install SuperSU.....always fails.
How can I get this to work?
Click to expand...
Click to collapse
Thanks again. For anyone that has a soft bricked LG K7 see this man! He brought my S#!? To life through teamveiwer. Thanks again. From my LG K7.
Maybe just my experience, but regarding step 10. I had to have the twrp image in SDK>platform tools, also when you get to fastboot flash twrp-image-3.img, I couldn't get it to work, until I typed it as fastboot flash recovery twrp-image-3.img. Hope this helps anyone else getting errors during this part. Thanks for the writeup.

Categories

Resources