Database Info

[Q] My Asus TF300T is on stock Android 4.0.3, what to do next?

The darn thing just started nagging me with an update notice that comes back every ten minutes. I read somewhere that updating is going to stop me from doing certain advanced things, so I finally got the last push to go for either CM10 or CleanRom, depending on which one gives me the most advanced and pleasant experience.
But before doing so, it's recommended to get some kind of flash info file or something from it that doesn't come out when upgraded to the latest firmware but does on the old 4.0.3. What would be the best way to go from now on?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Found something myself, thank me very much!
http://androidroot.mobi/t3_nvflash/
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

do yourself a favor if you gonna go with a custom rom, Energy rom and TWRP recovery!

What are their advantages when compared to CM10 or Clean?
Sent from my Galaxy Nexus using xda app-developers app

This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...

Lex_Michdeandroid said:
This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...
Click to expand...
Click to collapse
Your tablet will say it is unlocked in the upper left part of the screen when The Asus logo appears at boot.
Sent from my Transformer Pad TF300T using Tapatalk HD

Hi, if your tablet is still on stock 4.0.3 (ICS bootloader), I recommend doing NVflash first
http://forum.xda-developers.com/showthread.php?t=1894867
If you have already updated to JB bootloader it won't work.

It doesn't say Unlocked, so I guess that's why I don't see the USB option when I try to get into Fastboot?
I'm also not able to get ADB commands recognized on my win7x64... Am I doing it wrong? What's the proper method/order of events here? Isn't there a really n00b-proof version of a guide here, or is it something I should write as soon as I get out of this mess and get it working?
Sent from my Galaxy Nexus using xda app-developers app

Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596

pjc21 said:
Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596
Click to expand...
Click to collapse
Perhaps I'm not really looking in the right location, but the Asus website says I need to choose an operating system and gives me no option to choose. This way I'm not able to download the apk...
Edit:
Tried clicking the links with the tab and it started the download... Device now has an unlocked bootloader. On to the next one...
Edit2:
Ah, now I get it. Pay attention to where that Android SDK stuff is being installed. Mine got installed in the folder I unpacked the installation files! So somewhere 256 folders deep on the Desktop was the right 'adb.exe' file. Make sure the tf300_nvflashpack files are in the same directory and open the command prompt there. After that I got back to the http://androidroot.mobi/t3_nvflash/ website and entered the commands. One moment please, back in a flash!
Edit3:
Now I have 5 files in /mnt/sdcard/AndroidRoot and I uploaded them to my Dropbox. I'm guessing they are the right files...
blob.bin
blob.log
bootloader.ebt
create.bct
recovery.bct
To be sure I uploaded them all.
Copied these files into the SDK folder, along with the other zipped files for nvflash so the nvflash command works to get the other three backup files.
Edit4:
Went on following the guide and checked the video to see if I was really going the right way. Finally I have all files backed up. Goddamn what a journey, but it makes you grow a pair of balls. Now on to the next hurdle, getting a proper ROM, because stock is really getting on my nerves.
So CleanRom, CM10 or Energy ROM? Should I first upgrade to JB? Without or with the popup I'm constantly getting?

Lex,
You have alot of the same questions I do/did, and I have your original post open in another window to respond to all your questions. I'm working on writing a guide for all this stuff so this is rather helpful. If I respond to a question twice, please forgive me as I'm literally just going down the list and answering em as I read em.
In your first post, the file you're referring to is gathered via NVFlash. I haven't used NVFlash yet, but what I understand is that if you use this tool it basically backs up your ICS (4.0.3) bootloader information. The newest firmware change is to Android Jelly Bean (4.1.1) and that re-locks your bootloader. Once you go to JB, you cannot go back. So this servers as a backup (again, this is just how I interpret the information from their website. I don't know how correct my interpretations are, and have actually opened a thread to ask for clarification about this program).
For the drivers, all I did was download the android SDK and install the 'android tools' and "extra - google drivers' from the list. My laptop was just recently wiped-out so I have no prior drivers installed, nor have I connected my tablet to my computer yet (just got a replacement tablet last weekend). I didn't use the universal driver or any other add-ons. Just use the SDK, it will install drivers, and then it will detect your device. I verified this by typing "adb devices" in command prompt and it detected the serial # of my device.
Within that same post, you had some confusion about ADB. It's just an executable, and you have to use the command prompt window from whichever directory it is installed to. So once you unzip the Android SDK or wherever you installed ADB to, use the command line commands "cd directory/where/adb/is/installed" to navigate to it, or use shift + right click within that folder and it will have an option to "open command prompt here" with admin privileges. That makes life a bit easier. Other people also install their SDK to C:\android\SDK or something similar, so it's less to type.
In order to determine if your bootloader is unlocked, look at your tablet in the top left hand corner when it boots up. It will say "Device is unlocked" and list a bunch of numbers (which if I remember correctly would just be the firmware information). Your device will not be unlocked until you actually download the unlock tool from asus' website and push the file via adb to your tablet and install it. That is, you have to take a very specific, very advanced overt action to unlock it. Nothing else and no one else can do it for you nor can it be done accidentally.
Next post (#8 in the thread): You are correct that fastboot will not show unless you are unlocked. I just verified this on my not-unlocked, not-rooted new tablet, and cannot enter fastboot mode. Your ADB commands wont work if your drivers are not correctly installed.
Post #10: You have to select "Android" under the OS drop-down box to find the unlocker app. As for the location of the ADB.exe, mine was found in this subfolder within the android SDK: <whereveryouunzippedit>\Android SDK x86_64\adt-bundle-windows-x86_64\sdk\platform-tools
That folder contained the correct (and I think only) adb.exe I needed.
For your last part, I think you should try out a number of ROM's to see which you like best. I've tried all the major ones (CM9, CM10, CleanRom, Hydro, Blackbean, and some of the stock rooted/de-odexed) ROMs and used Blackbean for the longest time because of how slick it looks (all black) and how easy it is on my eyes.
Make sure you document the steps you took so you can remember them in the future. I'm working on writing a guide right now and documenting my steps to go from a stock, locked, and not-rooted tablet to a rooted unlocked and custom flash tablet.
I really hope I was able to clarify some things. I am by NO MEANS an expert but I've spent many hours experimenting and think that I wish I had someone to answer my questions when I was first learning, rather than learning by mistake.
Hopefully this helps,
Opethfan89

Hi, I use Energy rom which I find pretty good, you will need to update to JB first as Energy, CM10 & Clean rom are all JB bootloader compliant. My tab came with JB pre installed so not sure what the best way to update is but would assume since you still have stock recovery would be with OTA update (popup notice). Here is a guide to update to JB but I think this is if you have already installed a custom recovery as it looks like you flash back to stock recovery first, thats why I think if your getting update notice and still have stock recovery, go with that.
http://forum.xda-developers.com/showthread.php?t=1845377
Once you have updated to JB stock here is a guide to install custom recovery (CWM or TWRP), root & install custom roms.
http://forum.xda-developers.com/showthread.php?t=2041627
Here is link to TWRP recovery (I had issues with CWM).
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps.

opethfan89 said:
Lex,
You have alot of the same questions I do/did,
[..]
Hopefully this helps,
Opethfan89
Click to expand...
Click to collapse
I can only click the thanks button once, but I clicked the f- out of it that one time. Although I already got to the point where my stuff is backed up, it is really good for my/our fellow adventure-seekers to have an answer to these FAQuestions. It's awesome you took the time and effort to type that much words to help out someone you don't even know. Thanks again!
pjc21 said:
Hi, I use Energy rom which I find pretty good,
[..]
Hope this helps.
Click to expand...
Click to collapse
Same goes for you! Tomorrow I will be trying as much ROMS as I can to see which one suits me best. Also repeating this process is the best way to learn something and since I'm unbrickable, I am going to flash the hell out of it for a few days. I'll try to post my steps and findings here so I (and perhaps others with the same trouble) can benefit from it in the future.

Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:

pjc21 said:
Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:
Click to expand...
Click to collapse
It's upgrading now. Of course I forgot I lost root with the last OTA update and I forgot to make sure I rooted the thing so it was able to use the rootkeeper after upgrading to JB. I hope there is some documentation on rooting JB, because at the time this all happened root was not possible yet. It's past 1 AM over here, so I guess it's best to save this quest for later when I had some sleep.
Edit:
Just for kicks I tried 'Root Checker' and it said 'no root'. Then I saw 'Rootkeeper' was installed. Opened it up, tapped the restore button... Device rooted! Guess my memory is really failing big time... One down, # to go.
Edit2:
Installed TWRP:
Just downloaded the .blob from their website and
put it in the platform-tools folder.
Then renamed it to TWRP.blob.
Turned off tablet,
plugged in USB cable in the tablet ONLY,
hold volumeDown button,
plug into laptop holding button,
waiting...
choose USB logo,
open cmd-line in the platform-tools folder,
run command: "fastboot -i 0x0B05 flash recovery twrp.blob"
waiting...
Done. Let's see if it works...
Edit3:
At first I didn't understand how to get into TWRP (DOH!),
Hold volDown, power on, choose RCK.
Edit4:
Been having a fight with TWRP when I try to install CM10.1 (latest nightly: 20130121). Gives me an error status 7 or something...
Code:
Verifying update package...
assert failed: getprop("ro.product.device") == "tf300t" ||
getprop("ro.build.product") == "tf300t"
E:Error in /external_sdcard/CROMS/****.zip
(Status 7)
Error flashing zip ' /external_sdcard/CROMS/****.zip'
Of course, ****.zip is a long filename I didn't want to type completely here.
Will try to figure out whats wrong later today, first I'm going to try restoring the backup I made earlier, just to see how a complete backup works when the tablet is wiped back to factory settings.
Edit5:
The backup stuff is really cool! My tablet is back the way it was even though I wiped it completely!
Back to the ROM rumble... baked_tf300t_blackbean-6_jb-bl_b6.zip gives me the same error. Starting to get annoyed again... Let's try something different, CleanROM. Download is taking ages... I'm restoring again, so I can use the tablet for the rest of the day. As soon as I feel like it I will try again, for now I'm giving it 'the finger'.
Edit6:
Cleanrom is installing now. I guess CM (baked is CM based right?) was causing some trouble...
Done installing...
Wipe Cache/Dalvik...
Reboot...
Android is upgrading...
Might need to choose the small font, my screen is really clogged up with stuff. Didn't expect to keep my settings etc., thought it would be completely wiped. I'm going to restore and then reinstall with the highest DPI setting first, then I'll wander around the rom to check if I like it.
Edit7:
I think I'll stick with this one for a few days, runs fine if you ask me, maybe take the time to finally update my Galaxy Nexus to CM...

[Q] cwm 6.1 for tipo is out, can I use it with my german tipo?

cwm 6.1 for tipo is out. See >>HERE<<
Well, I am unshure to use it.
Will it brick my phone?
My Sony Xperia Tipo is german from Telekom.
- bootloader is locked
- firmware is 11.0.A.0.16
- rooted
Does a locked bootloader block installing CWM or cause trouble in any way?
Are there german users out there who have succesfully installed the mentioned CWM already?

killerhippy said:
cwm 6.1 for tipo is out. See >>HERE<<
Well, I am unshure to use it.
Will it brick my phone?
My Sony Xperia Tipo is german from Telekom.
- bootloader is locked
- firmware is 11.0.A.0.16
- rooted
Does a locked bootloader block installing CWM or cause trouble in any way?
Are there german users out there who have succesfully installed the mentioned CWM already?
Click to expand...
Click to collapse
If you're rooted already, you're good to go.I suggest flashing 4.22 though, it is really noticeably better in performance.You can root that with UnlockRoot, and install CWM/TWRP afterwards, whichever you'd like.

Steam. said:
If you're rooted already, you're good to go.I suggest flashing 4.22 though, it is really noticeably better in performance.You can root that with UnlockRoot, and install CWM/TWRP afterwards, whichever you'd like.
Click to expand...
Click to collapse
Good news. Thank you for your encouraging answer.
As I have so far noticed documentation on this forum, in the case of error doing recover attempts are made with windows software.
I am running linux, if windows is nescessary, does recover software work at a virtual machine running Windows XP with USB piped through? Or is there even linux software to manage that?
And, can you advise a good location I can read and follow instructions in the case of CWM installation problems?
Please excuse my nooby questions, my fone is the very first and only one I could afford and I have no experience so far.
I'd like to prepare as much as I can to avoid having a bricked device asking questions at a lost situation.

Cwm is fine for you take care while flashing a rom though it can cause a mess but dont worry I have been messed up before I got my tipo back running in 17 minuts
I got sollution very quickly and stepwise you are not a noob but I am so just sharing my xperience????
Sent from my ST21i using xda app-developers app

killerhippy said:
Good news. Thank you for your encouraging answer.
As I have so far noticed documentation on this forum, in the case of error doing recover attempts are made with windows software.
I am running linux, if windows is nescessary, does recover software work at a virtual machine running Windows XP with USB piped through? Or is there even linux software to manage that?
And, can you advise a good location I can read and follow instructions in the case of CWM installation problems?
Please excuse my nooby questions, my fone is the very first and only one I could afford and I have no experience so far.
I'd like to prepare as much as I can to avoid having a bricked device asking questions at a lost situation.
Click to expand...
Click to collapse
It's hardly brickable by root procedures, the only thing you could've run into was not getting the files copied to system, but since you're rooted you don't have any probs.Just DL the zip from the CWM thread, extract the files in some folder, connect phone with usb debugging on, and double click the start.bat
it will tell you when it's done, you can press any key to continue.at this point, disconnect the phone from the USB cable, power off, then start it up and tap volume down at the Sony logo.

Steam. said:
It's hardly brickable by root procedures, the only thing you could've run into was not getting the files copied to system, but since you're rooted you don't have any probs.Just DL the zip from the CWM thread, extract the files in some folder, connect phone with usb debugging on, and double click the start.bat
it will tell you when it's done, you can press any key to continue.at this point, disconnect the phone from the USB cable, power off, then start it up and tap volume down at the Sony logo.
Click to expand...
Click to collapse
Success!!!
Thank you so much, tusharkulkarni008 and Steam.
There were no errors at all, though I had to fetch an adb executable first which I checked working with "adb shell".
I successfull opened cwm and did my very first full system and data backup!
Splendid, now I am able to do more exciting things with my fone!
So, I learned, installing CWM is nothing but copying files to system partition. It does not depend on an unlocked bootloader, it just needs a rooted fone.

unlocked BL is only required for flashing a custom kernel, which is required for most custom roms around here, they are all based on FXP release,CM10.

Updating advice please ! Reroot failure

Hi everybody ! Ill try to keep it simple as I'm sure its covered somewhere but here goes ....
Ive been using my shield portable, rooted, for ages now no problems.
Like many Ive updated it in short ever since nothing whatsoever has worked properly , most annoyingly the screen doing backflips when you go near it and hundreds endless strange updates when rebooting.
Anyway I don't think you or I or any of us want to waste time trying to figure out why its done any of this but I just want to be able to fix it. I guess I'm going to have to start again somehow! its worth noting here that all my backup apps like Helium now don't seem to work.
After the update I of course ReRooted and it appears fine from boot loader , still says unlocked. but upon usage its clearly very confused about whether its rooted or not !
In short its useless. Advice please My kung Fu warriors
May your arrows fly straight and true

I have no idea about the various issues, but I would perform a factory reset, and clear cache and dalvik cache using at least 3 swipes per each function. The method of rooting I recommend is by flashing a zip of SuperSU from a custom recovery menu. CWM or TWRP are both available for the NSP. After flashing SuperSU, when you reboot and go into SuperSu you'll see that it's installed (locked down tighter) as a system app.
Downloads:
SuperSU (latest stable version) v2.65
CWM Recovery Menu (latest version) v6.0.4.4
TWRP (Modified recovery (based on TWRP v2.8.7.0)
Sorry. This is the best I can offer you right now. If this doesn't work I would reflash the stock images of whatever OTA you wanna be on. The images can be found @:
SHIELD Open Source Resources and Drivers. You'll need at least the platform-tools portion of the Android SDK (to use Fastboot to flash from recovery). A user friendly PC app that can basically do all this sort of stuff is Shield Ram v1.1. You might find that easier to use.
Oh and here's the latest Minimal ADB and Fastboot Drivers installer [v1.3.1]
If you need further help, let me know.

Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again

[/COLOR]
Marrhead said:
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
Click to expand...
Click to collapse
Yeah, pretty much the rule is generally "as long as you can still see the screen, it's probably fixable". Sounds to me like your best bet, would be to download the OTA you wanna be on, and flash a new install to your Shield. It's the quickest way from A-B. I'm about 99% sure that this would solve the problem (as long as you re-root it properly). Though if you have your reasons, you can try some of the other things first. You're welcome and let me know how things go!

So where does one get the latest OTA?
cheers

Marrhead said:
So where does one get the latest OTA?
cheers
Click to expand...
Click to collapse
I did link up the main Nvidia page that would lead to the OTA images, but here's a direct link to DL just the OTAs:
Edit: you can get there through the link I included in my previous post: SHIELD Open Source Resources and Drivers. I'm having issues with editing posts, and all sorts of odd **** with the link trying to post a more direct link. It's an Nvidia site, just scroll down to Shield Portable Recovery OS Images (something like that).
Unfortunately there are only Linux and Windows downloads available. I'm not sure what your best option would be, as you have a Mac. You could contact Nvidia support, and see what they say about it. Sorry, but I don't think I can probably help much more than this.When I contacted Nvidia support about a year ago, they were pretty helpful. Hopefully you get this sorted soon. Oh and the OTAs are flashed via a terminal/command prompt. So if you can emulate DOS on your Mac (which I don't see why not...DOSbox? maybe) then that sounds to me like the solution.

Ok , hit another brick wall. Im using a windows computer now, followed all the instructions i can find, and now the bootloader seems dysfunctional.
Ive got adb and fastboot and its recognising the device but once rebooted into bootloader which loads fine, the commands say no device found and nothing works in this mode.
If i hit recovery mode then a little dead android appears! poor little guy.
I tried shield ram but it had same problems, seems to run fine but cant find shield once its in bootloader...
Ive got the image zip of the update i want to flash but no idea if im doing it right- not sure how to use it.
Help!

ZTE Blade A450 infected with Ghost Push virus. No luck so far, need help!

Hi! This is my first post on this amazing forum!
So, this is gonna be tough... So bare with me. As I said, this tread is about a ZTE Blade A450.
My phone is infected with Ghost Push virus. That means that the device is full with malicious software in its root, which is not removable by recovery. Once the device is connected to the internet, lots of infected, unwanted apps start downloading and installing on their own, making the device mostly unusable.
I will make a list of the things I have tried, in order to get rid of it.
1. As mentioned above, wiping data/recovery. Virus is part of the system, so it's reinstalled along with Android.
2. Tried installing Stubborn Trojan Killer. This app needs internet access to work, so when connected, the scanning and fixing procedure gets interrupted by the installation of those infected apps. No luck there.
3. Tried flashing the official ZTE update for my model through sd card. I failed, because the update I download from ZTE's support site is corrupted (can't unzip it on pc). No luck there.
Now I am in the process of trying to flash a custom ROM. I can't find anything for my device, it's not listed in CWM or TWRP too. It's seems like I am stuck and nothing works.
I need help on this one and your best advice possible!
Thanks in advance!

Anyone please?

iKnewIt said:
Anyone please?
Click to expand...
Click to collapse
You're only allowed to bump a thread once every 24 hours, please consider this in future. Thanks, and good luck getting your answer!

iKnewIt said:
Hi! This is my first post on this amazing forum!
So, this is gonna be tough... So bare with me. As I said, this tread is about a ZTE Blade A450.
My phone is infected with Ghost Push virus. That means that the device is full with malicious software in its root, which is not removable by recovery. Once the device is connected to the internet, lots of infected, unwanted apps start downloading and installing on their own, making the device mostly unusable.
I will make a list of the things I have tried, in order to get rid of it.
1. As mentioned above, wiping data/recovery. Virus is part of the system, so it's reinstalled along with Android.
2. Tried installing Stubborn Trojan Killer. This app needs internet access to work, so when connected, the scanning and fixing procedure gets interrupted by the installation of those infected apps. No luck there.
3. Tried flashing the official ZTE update for my model through sd card. I failed, because the update I download from ZTE's support site is corrupted (can't unzip it on pc). No luck there.
Now I am in the process of trying to flash a custom ROM. I can't find anything for my device, it's not listed in CWM or TWRP too. It's seems like I am stuck and nothing works.
I need help on this one and your best advice possible!
Thanks in advance!
Click to expand...
Click to collapse
iKnewIt said:
Anyone please?
Click to expand...
Click to collapse
So my first question is, is your phone rooted? Second, is USB-Debugging enabled, and if it is, does MTK Droid Tools detect/recognize your device?
You can answer me anytime if you still need some help.
Sent from my ZTE BLADE L5 PLUS using XDA-Developers mobile app

Rooting LGMS631 (Metro) Running 6.0

Hi there,
I know this is probably redundant but I've been searching these forums and I'm a bit overwhelmed. Mainly I am trying to discern whether I need to factory reset my phone before I root it or not. If anyone would be kind enough to break it down for a rooting noob, but fairly tech savvy chick, I would really appreciate it. Or just direct me to the most applicable thread for my situation. I have a PC running Windows 8.1 also, if that helps.
Thanks!!!

http://forum.xda-developers.com/lg-g-stylo/how-to/guide-lg-g-stylo-how-to-root-t-mobile-6-t3333916
Factory reset is not necessary.

stuck
i tried following the guide , igot the bootloader unlocked but when i tried to do the flash recovery.img it kept saying it couldn;t find the directory. i moved the img file to the same place as where the adb is installed but that didn't help. i ended up rebooting my phone and it was in oem state. I installed a backup for now but I tried to attempt it again and i couldn't get it to come up in the adb devices anymore. Advice?

never mind
fabuliz said:
i tried following the guide , igot the bootloader unlocked but when i tried to do the flash recovery.img it kept saying it couldn;t find the directory. i moved the img file to the same place as where the adb is installed but that didn't help. i ended up rebooting my phone and it was in oem state. I installed a backup for now but I tried to attempt it again and i couldn't get it to come up in the adb devices anymore. Advice?
Click to expand...
Click to collapse
i figured it out, thanks for your guidance

dammit
I swear I did everything right but now my phone is on LG screen and I cant do anything

fabuliz said:
I swear I did everything right but now my phone is on LG screen and I cant do anything
Click to expand...
Click to collapse
I think there is a typo in this set of directions.
Try this one:
http://androidforums.com/threads/guide-how-to-root-t-mobile-6-0-update.1008880/
(Step 7 is correct here)