Database Users

WANTED: Sticky guide for newbies

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Help rerooting after 4.3

My wife has a rooted nexus 7 2012 wifi and she unintentionally accepted the ota Android 4.3 update. So of course it unrooted her.
I originally had a hell of a time rooting this tablet using wugfresh nexus toolkit. Took me several days to succeed and the same thing is happening again. My Windows 7 laptop keeps installing the wrong drivers even though I selected the option to disable the auto driver configuration. Also USBDeview never shows the installed Samsung adb drivers yet when I try to install them I am warned they are already installed. It's already been hours and who knows how many retries and reboots!
So even though I'm a newbie I decided to go the Android sdk route.
1. Where do I download the files I need to just root the darn tablet?
2. What do I do next?
Please keep it simple........
Anyone want to walk me through it on the phone?
Thanks

If you are new to using SDK, check this out for a well laid out tut on how to get set up and rooted.

I now have android sdk set up.
What are the commands I should issue to root?
Thanks

now you need to flash a custom recovery then flash a root zip file via windows command prompt...Have you figured out how to interface with your device and the windows command prompt? eg;
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
-then you would issue "adb reboot bootloader"
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
-then while in bootloader toggle with the volume keys to "recovery" option and press power
-now you will be in your new recovery you just flashed and you can push the zipped root file you chose to the sdcard, "adb push rootyouchose.zip /sdcard/"
-once its been pushed you can flash it in recovery and reboot, and you are now rooted
-this is the latest cwm recovery that you could flash in fastboot as described above
-this would be the root file you want to push then flash in recovery
-this may be of some help, scroll down halfway

Thank you so much for helping. You can't know how much it is appreciated.
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
Got that. It works!!
-then you would issue "adb reboot bootloader"
Worked! Got the Android on his back.
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
Is recovery image on my pc or the tablet?
Why do I have to indicate the img name here if I will later select it

When I write
Fastboot flash......... Img
I get
Unknown partition 'the image file name'
"error : cannot determine image filename for. '.......'

You need to have downloaded a recovery image, that is what you flash I linked to one on my last post, that file is called "recovery-clockwork-touch-6.0.4.3-grouper.img" so you would issue,
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img
"fastboot flash recovery" is telling it to flash a recovery file and "recovery-clockwork-touch-6.0.4.3-grouper.img" is the recovery file in this case to be flashed so, combined its, "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img"
I do not use Windows, I use a terminal instead of windows command prompt so I can't be specific as I am not too familiar with windows command prompt. With terminal it is much easier in my opinion but you need to be running nix or Mac OS to have a terminal

OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks

Anderson2 said:
OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks
Click to expand...
Click to collapse
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.

GedBlake said:
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.
Click to expand...
Click to collapse
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.

Anderson2 said:
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.
Click to expand...
Click to collapse
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it.
...but I assume your Nexus 7's bootloader is already unlocked, given it's been rooted once before.
And so swiftly skipping forward to step 2...
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.

GedBlake said:
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it. I assume your bootloader is already unlocked.
So swiftly skipping forward to step 2....
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.

Anderson2 said:
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.
Click to expand...
Click to collapse
Hello again, Anderson2...
Well, you sort of are already doing something in return.... you're asking questions.
Questions that require answers. Those answers, whoever posts them, may be of assistance to somebody else. Somebody else looking for a solution to a similar problem.
I always look upon these forums as a means of sharing. Not everybody can know everything. God knows, I don't know everything.... and I've been messing around with Android for three years now. So don't worry so much about it being a quid pro quo sort of arrangement.
I know what I know primarily as a result of my own experiences and what I've learned here from the many (in most cases, more knowledgeable) posters here on XDA. What you learn today, you can pass on to others, tomorrow (metaphorically speaking). We, all of us, stand on the shoulders of each other.
With regard to the second generation Nexus 7 (2013)... I'm afraid I really don't know much about it... but I'd be surprised if rooting it deviated significantly from rooting the first generation Nexus 7....
Namely...
1). Unlock the bootloader.
2). Flash a Custom Recovery.
3). Using that Custom Recovery, flash some SU root package... probably from Chainfire.
Anyway, I've found this tutorial here...
http://forum.xda-developers.com/showthread.php?t=2382051
...and it appears to follow a very similar template.
The Nexus 7 (2013) forum itself, which is also worth visiting, is located here....
http://forum.xda-developers.com/nexus-7-2013
Rgrds,
Ged.

HP slate 7 extreme a plain tegra note?

Just wondering if anybody's tried to flash tn7 ROMs on their s7e? And does the s7e read the same model number as the tegra note? P1640?
Sent from my SGH-I317 using xda app-developers app

I've been stuck trying to figure out how to adb on my slate 7 extreme for weeks. Tried every driver and every cord and port. So while I'd love to confirm that it is the same... I'm still not sure.

Same here looking for a root
Sent from my HP Slate7 Extreme using xda app-developers app

I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.

Mobilla said:
I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.
Click to expand...
Click to collapse
cool. What do you mean by locking up a lot? it often hang and jam? . So i guess, staying at 4.2.2 is the best for now?

skysoblue said:
cool. What do you mean by locking up a lot? it often hang and jam? . So i guess, staying at 4.2.2 is the best for now?
Click to expand...
Click to collapse
It will work fine for up to about 10 minutes, then the screen will freeze and the only way to get it back is to hold the power down for 10 seconds and reboot it.
I am back on 4.2.2 right now, but when I have some extra time I might try a few things.

Mobilla said:
I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.
Click to expand...
Click to collapse
Is it possible to just have root set up on 4.2.2? Would like to keep all partitions stock if possible (as well as the bootloader). Would this help with stability issues? Sorry if these are noobish questions but thanks in advance

Dude you gotta give us a detailed guide on rooting puuuhleeaase

nejinikko said:
Dude you gotta give us a detailed guide on rooting puuuhleeaase
Click to expand...
Click to collapse
+1
I tried a chinese program without luck. I just bought a keyboard which works with the wrong layout in 4.2 and works perfect with 4.4 which I have on my other devices..therefore I am really looking forward flashing it!

Almost plain tegra
Hi, I agree with @Mobilla I installed android 4.4.2 from this link but be extreme careful, backup your rom first, KitKat works fine but randomly android freeze all system, I tested ClockWorkMod recovery and work flashing root file SuperSU-v1.94.zip but I don't test backup from recovery, well maybe someone can help us to know why kitkat freeze chinese root method is complicated I rooted with this method I don't read chinese I click some buttons and it works. Sorry with my English, I'm from El Salvador, I speak Spanish

I couldn't run 4.4 more than about 10 minutes before locking up, so I went back to 4.2.2 (rooted).
You can download the stock 4.2.2 update.zip from HP's website if you experience the same issues
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
The rooting method is the same as for the TN7 with the exception of fastboot commands you need to specify the vendorid (e.g. fastboot -i 0x03F0 oem unlock) I didn't try the Chinese tool.
You can flash root from recovery once it is unlocked.
I tried looking for what was causing the lockup but I couldn't find anything in the logs. If anyone has any tips for hunting down the problem I would be happy to try.

CWM
Hi, I tested CWM from this link and it works with nandroids backup, but the default storage is strange: /storage/emulated/sdcard0 but in this dir I can't move or delete that backup and use storage space I use a root explorer and can't move or delete, CWM works to root the device with SuperSU-v1.94.zip :good: but not for backup, see ya!

Rooting Slate 7 Extreme
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download Nvidia Tegra Note 7 Super Tool 2.2
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot (this is what I did, you can actually just use the command "fastboot -i 0x03F0 reboot")
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.

Hi @duocdx.bt good tutotial in
9. Remove the usb cable and reboot
you can reboot with this command:
fastboot -i 0x03F0 reboot
:good:
duocdx.bt said:
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download http://forum.xda-developers.com/showthread.php?t=2627654
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.
Click to expand...
Click to collapse

sparkly81 said:
Hi @duocdx.bt good tutotial in
9. Remove the usb cable and reboot
you can reboot with this command:
fastboot -i 0x03F0 reboot
:good:
Click to expand...
Click to collapse
Thanks! Edited that in and fixed the link to the super tool. Hopefully this is clear enough to newer users such as myself Hopefully HP starts releasing stable updates for us but if not, things aren't too bad with root :good:

What can I do?
hi, I also install my hp slate 7 extreme with 4.4.2 tegra note7 version, like you my android is blocking a few minutes later, how I return to my 4.2.2 rom if I haven't the stock recovery but yes the update.zip from hp.

What can i do?
hi, I also install my hp slate 7 extreme with 4.4.2 tegra note7 version, like you my android is blocking a few minutes later, how I return to my 4.2.2 rom if I haven't the stock recovery but yes the update.zip from hp.

duocdx.bt said:
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download Nvidia Tegra Note 7 Super Tool 2.2
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot (this is what I did, you can actually just use the command "fastboot -i 0x03F0 reboot")
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.
Click to expand...
Click to collapse
Succesfully rooted my HP Slate 7 Extreme 4409ra Tablet ty!

I have a Slate 7 Extreme 4400ca, and today installed the update listed on the HP webpage:
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6617231#N147
after a non-destructive installation, 'about tablet' reports that I'm running ANdroid 4.3, kernel 3.4.57-gc102837
Not 4.4 yet, but this should be helpful.
I haven't tried rooting yet.

Just a update on a simple way to root stock 4.2.2 slate 7 extreme
http://towelroot.com
Download apk
Install
Restart
Enjoy
Worked for me.

[Q][Solved] Where should I begin as a beginner?

Edit:
[Procedure] http://forum.xda-developers.com/showpost.php?p=64841837&postcount=27
Edit/
I am creating this thread dedicated for me and other beginners "noobs".
Where should I begin as a beginner?
I am looking to unlock and root with latest MM that motorola supplies.
Things you should know about me:
I have no idea how to use adb.
I have no idea how to unlock & root or even if I should but I don't like ads.
I have no idea which firmware to use.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
I am completely lost.
I have not gotten my phone yet, I ordered it this morning and will be here Friday. I am just trying to compile sources and info.
Thanks a bunch guys, I really need help with this.

One piece of advice for starters just since you used the word noob. Never mod your phone on a low battery. You can mess a phone up enough to break offline charging, and without a removable battery that you can swap out or charge in a cradle that could get awkward in a hurry on this phone. I always make sure I'm >75% just in case. You can fastboot your way out of all kinds of trouble; but not if your battery is dead and your phone is so screwed up it is not offline charging.
Your phone will probably show up with Android 5.1.1 installed, at least I got mine about 3 weeks ago and it did. Once it is through initial setup it should want to apply an OTA to Android 6.0 right away; if not check for it in Settings -> About -> System updates and it should find one. Just let it update before you do any setup or app downloading.
Once you're on MM, before you do any setup you have to unlock your bootloader if you intend to root. You'll get all the warnings about voiding warranty and here there be dragons, so be prepared for that. Also, unlocking the bootloader will wipe your internal storage, so don't bother with any setup or app downloading before you do it.
Start with Heisenberg's thread. It is a great guide on how to setup your computer for adb and fastboot as well as all the syntax you need for unlocking the bootloader and installing a custom recovery. Make sure to get the 2.8.7.1 version of TWRP that is patched to work with the MM bootloader.
When you boot to TWRP recovery for the first time it will ask if you want to keep system read only. Keep system read only and make a backup immediately. I usually make one backup of boot, system, and data, and a separate one of just efs; don't worry if you don't understand, you'll figure it out when you get there. TWRP is all touch based and pretty intuitive. This way you have good, untouched system backup to fall back on just in case.
When it comes to rooting MM, don't use the old system install method. Flash a SuperSU from this experimental systemless root thread (I used this instead of the ivcarlos method linked to the Heisenberg thread because it is more automated and easier). I can vouch for the 2.62-20151210170034 version of SuperSU. I've used it to root stock MM on this phone 3 or 4x as I've restored backups and changed kernels. I've heard the 2.64 and above SuperSU versions are not working with this phone on MM, and the older traditional system root methods like the v2.49 version that is linked to the Heisenberg thread are causing bootloops on MM. Don't panic on first boot after the systemless root; it appears to bootloop once but comes up normally the second time.
One other thing, TWRP doesn't seem to be able to detect the systemless rooting method, and it really wants your phone to be rooted. If/when TWRP offers to automatically install SuperSU, don't let it - ever - it will keep asking. It must use the old method that causes bootloops on MM, not the new systemless method linked above.
Once you're all rooted and settled in, if you get sick of the unlocked bootloader warning you can fix it by reading up in this thread. Just be sure to read carefully and get the MM logo and not the LP logo.

Wow, thank you so much for the long type up.
Duly noted and this is a great start. May I continue here if I run into any problems?
I think ima have fun with this phone
I am into tinkering with devices, "sometimes linux" etc, like my PC OS win7x64 is modified big time, so I probably will catch on with unlocking rooting etc very quickly.
I got chillz and cannot wait!

Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.

gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.

Hitti2 said:
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.
Click to expand...
Click to collapse
Good luck :good:
I just noticed one thing that might not be entirely clear in the Heisenberg thread. It says to enable adb in the Settings -> Developer Options menu, but by default you won't have a Developer Options menu.
To get one, go into Settings -> About Phone, scroll all the way to the bottom, and tap on build number about 8 or 10 times. Your phone will say something to the effect of congratulations now you're a developer, and you'll have the menu.
Edit: i just noticed it says how to enable developer options further down the page

ty, I will need it lol.
Dev options were on my S5 too. My pops showed me how to on the S5, kinda hoping it was the same way to enable them, turned out to be. Cool.

gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
^^^This^^^
and remember what XDA is really for ...http://forum.xda-developers.com/showpost.php?p=2031989
with that, enjoy all the reading, and do not be afraid to look at other sites too, there are even videos around that can help guide you...
and there are fellow members here to help...but most questions have already been asked and answered, so search first! Cheers! :highfive:

This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
1) Be sure to get the newest TWRP that has been patched for M.
Click to expand...
Click to collapse
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?

Hitti2 said:
This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?
Click to expand...
Click to collapse
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)

[Q] Where should I begin as a beginner?
At the beginning, of course.
Sorry couldn't resist...

Naddict said:
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)
Click to expand...
Click to collapse
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?

Hitti2 said:
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?
Click to expand...
Click to collapse
after you unlock and install custom recovery, you use TWRP (the custom recovery) to create the backup...
as you are on MM, you cannot use the "all in one" application that I provided in the link...so you will have to manually install/flash your rom

Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.

Hitti2 said:
Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.
Click to expand...
Click to collapse
Clearly you are impatient (not trying to be rude here), - XDA truly is not a place to pay for someone to do it for you, XDA is about learning and development, there are several places that a search will get you what you need. Many members have also posted links above to vast amount of information (specifically this post and this entire thread here http://forum.xda-developers.com/showpost.php?p=64183396&postcount=151 and here too http://forum.xda-developers.com/showpost.php?p=64311581&postcount=171) that you should take time to read and then, as you move through these things then you ask questions.
Offering to pay to have someone do it for you is really not what this site is about.
Read, do google searches...it has been done a hundred time already mate, take the time to learn what it is you are doing before actually doing it.

I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.

Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.

Hitti2 said:
I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2031989
Hitti2 said:
Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.
Click to expand...
Click to collapse
Looks to me like several folks in there offered suggestions on how to successfully get root ...and again, as my last helpful post here...you really need to read Heisenberg's thread, that guide works, and from what I can tell, you have to use systemless root.

Ok, I will follow
Intro
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
Prerequisites:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
1. How To Unlock Your Bootloader
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
2. How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
3. How To Make A Nandroid Backup With TWRP Recovery
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
Click to expand...
Click to collapse
& I will follow
Hello guys!
I make my own ROOT (systemless, thanks for Chainfire) images for Moto X Style with Marshmallow (build MPH24.49-18). Its use "experimental" systemless SuperSU version 2.56 - more info on http://forum.xda-developers.com/show...35&postcount=2. No need replace bootloader or recovery. Still need unlocked booloader.
Because TWRP didn't work in this version of bootloader (0xA048), I cooked "su.img" in a Linux box and used "/data/local/tmp" as bridge (accessible by ADB).
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it!
For use, you need
1) unlocked bootloader.
2) if your bootloader not unlocked, make sure you have copy of your data, because this process will erase your device.
3) install ADB and FASTBOOT on your pc using minimal ADB or Android SDK.
4) install ADB drivers from Motorola or Universal ADB.
5) download provided files.
6) download SuperSU ver. 2.56 from http://forum.xda-developers.com/apps...ellow-t3219344.
Steps:
1) extract files in a folder of your choice (su.img, boot.img).
2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder.
3) enable USB debugging on Android.
4) connect your device on pc.
5) open a command prompt in a new folder.
6) type "adb push su.img /data/local/tmp" without quotes.
7) type "adb install Superuser.apk" without quotes.
8) now reboot your device into fastboot mode by typing "adb reboot bootloader".
9) type "fastboot flash boot boot.img" without quotes.
10) type "fastboot reboot" without quotes.
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
Click to expand...
Click to collapse
I still think its going to brick but uhwell.

So far so good, I've got it unlocked.
I apologize for my ignorance. I am gonna take it a step at a time.
Doing step one "unlocking" was scary but it went good.
Wish me luck!

[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.