Database Info

[Q] Am I rooted or unlocked??

Sent my phone to Square Trade before I got the 4.0.4 update (was previously on 4.0.2 with T-Mobile). They put a new "main circuit board" in my phone (sent it in for power button inop).
Well when I got my phone back the first thing I noticed was an "unlocked lock" symbol during boot up. Then I found that that it was updated to 4.0.4 and in my app drawer the Superuser app (which I updated to v3.0.7 (41)) is present.....
Here is the specs under the "about phone" section in Settings:
Build number: IMM76D
Baseband version: I9020XXKI1
Kernel version:
3.0.8-g6656123
[email protected] #1
Thu Feb 2 16:56:02 PST 2012
I've never rooted before -so I don't know how to confirm that I am. However I noticed that in the Superuser app, when I go to check for updates it says that my installed version is LEGACY -and it says a new version of SU BINARY was found. When I tap on "update" it says: CHECKING FOR BUSY BOX... NOT FOUND, and then GAINING ROOT ACCES... FAIL!
Also when attempting to try out Droid Wall and Adblock they both say that I am not rooted.
Does this mean that I am not rooted?? -even though that "unlocked lock" symbol is present at start up??
If they rooted my phone wrong, what can I do to root it correctly??
-and-
How to I return to stock un-rooted 4.0.4 if I ever need to??
Any help would be GREATLY appreciated.

The unlocked symbol when you start up your phone (under the Google logo, right?) just means your bootloader is unlocked, which is the first step in actually rooting the phone.
As for Superuser, even non-rooted phones can install it from the Market/Play Store (like you have), doesn't necessarily mean you're rooted.
Did you install Superuser or did they put it on the phone?

They put it on my phone. I just updated it from the Play Store when I was putting all my apps back on my phone.
Sent from my Nexus S using XDA

Maybe they just wanted to see whether or not you were rooted?

So I can go ahead and follow the "how to root i9020T" guide under the stickied General section of this Nexus S forum? ....and I should be ok?
I figure that if my bootloader is already unlocked I might as well go all the way and finally root this phone, right? That or lock it up again.
My main concern is since I didn't know where they left of, I wasn't sure where to begin/pick back up in finishing the root process.
If I follow the guide from the top I should be safe though, right?
Sent from my Nexus S using XDA

MotorcycleKopp said:
So I can go ahead and follow the "how to root i9020T" guide under the stickied General section of this Nexus S forum? ....and I should be ok?
I figure that if my bootloader is already unlocked I might as well go all the way and finally root this phone, right? That or lock it up again.
My main concern is since I didn't know where they left of, I wasn't sure where to begin/pick back up in finishing the root process.
If I follow the guide from the top I should be safe though, right?
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
if you already have a custom recovery, just flash any of the custom roms(or kernels) and youll have root. if not, flash a custom recovery then a custom rom(or kernel). all the custom roms come with su binaries. yea, its that easy.

So I'm not sure if they put custom recovery on my phone.... how can I tell??

MotorcycleKopp said:
So I'm not sure if they put custom recovery on my phone.... how can I tell??
Click to expand...
Click to collapse
power off>hold volume up+power>volume rocker to select recovery>power to select

OK, when I do that process I got what looked like a dead Android??

MotorcycleKopp said:
OK, when I do that process I got what looked like a dead Android??
Click to expand...
Click to collapse
ha! dead android, lol.
youll need to flash a recovery via fastboot(probably clockworkmod recovery).

Ok.... flashing recovery is ALWAYS where I get lost when I read up on rooting.
Could you/someone point me in the right direction please?? (via instructions or a link to some GOOD & CURRENT instructions and files).
Can I just follow instructions from http://forum.xda-developers.com/showthread.php?t=895545 and start from the top -so that I get a feel of how to do this from the beginning????
-and if I follow the instructions from this post, will I still be running 4.0.4??
This dead android really concerns me a bit!!

That guide is perfect. If you use, it will install a custom recovery on your phone, which can then be USED to install 4.0.4 on your phone again. If you don't really want root access, I'd stay where you are right now.
Anyhow, if you DO decide to follow the guide, you can skip the part where it says to type "fastboot oem unlock" (beginning of part 2) because that command unlocks the bootloader, and your phone already has an unlocked bootloader (shown bythe unlocked lock you see when you turn your phone on).

OK.... so I'm following the guide, BUT when I go to "update driver software" I point it to where I downloaded the "android-sdk_r13-windows.zip" file, but it won't let me select it. I also tried extracting the file directly onto my C:\ drive, but it won't let me select it there either.
What am I missing here??
(running Windows XP 32 bit, by the way)

Do you have either WinZip, Winrar, or 7-zip installed on your computer? You need them to extract the file, which will give you a folder. Point the driver installer to that folder after you've extracted it

Well I got the file extracted just fine. Problem is that when it won't let me select ANYTHING when I try to update the driver (the "OK" is dulled out when I point it to where I extracted the file to).
BTW, at the current state, next to "Android 1.0" in my Device Manager it shows a yellow "question mark & exclamation mark", and it is a sub of "other devices" (with a yellow "question mark" next to that as well).
Did I miss a step????

Try picking just the folder where the extracted folder is, that might work. As for the yellow exclamation mark, it's normal. That's what the drivers you install are going to fix

Still won't let me chose anything.....
One thing I noticed is that in the instructions it says to point it to "(..\android-sdk-windows\google-usb_driver)" .....but I don't have anything that says "\google-usb_driver" at the end of the file name. I only have "android-sdk-windows" -even after I extracted the file.
All I have inside the "android-sdk-windows" folder are: add-ons, platforms, tools, SDK Manager, and SDK Readme. None of them have anything that say "google-usb_driver" in them.
Where do I find this "google-usb_driver"??

Scroll down on this page
http://developer.android.com/sdk/win-usb.html
Actually, it might be easier to try this out
http://forum.xda-developers.com/showthread.php?t=1589251

Hmmm... that one-click root method looks awesome, but since it was only uploaded yesterday I'm a little bit weary of it.
I tried to get that google-usb_driver, but with the sdk r13 it won't let me unless I update to r17. I'm thinking of just going to http://developer.android.com/sdk/index.html and getting the latest sdk r17 exe file & trying to go from there. Only concern is that on the guide here on xda it says "from sdk r14 forward Google removed the fastboot command so I'd have to make the fastboot command myself" -will this be an issue or is that easily done??
(I seriously can't believe I'm running into wall after wall with this.
I REALLY appreciate all the help thus far, by the way)

See the first link from my last post for a driver
Sent from my Nexus S 4G

[Q] Rooting, unlocking & updating madness

Having been a member on this forum for years I must admit it has been incredible the wealth of information I've gained from it. I've had all sorts of phones/pdas and I'ved used this site to help me get the most out of it and to help m "tame" the device and stop rubbish from the vendors being installed on there when I don't want it.
A couple of years ago I got an HTC Desire. Great phone although limited memory. I was happy with it. Didn't bother to root it or anything. I then got a Motorola Xoom. Didn't bother rooting that either. I got myself an HTC Sensation now. I decided one day that I was going to unlock/root the thing to see if I could do it.
Somehow, I think I managed it. I haven't really noticed a difference but then I haven't put a custom rom on it. On all my old Windows mobiles I always had a custom rom.
Now, going back to the Xoom. It's an original Xoom. I bought it in May 2011. It is running Android 3.2 after Motorola sent out an update. All is good.
However, I would like to have ICS on it. This is where my problems begin. I've tried following so many different how-to's on how to do this unyet none so far have worked. So, either I'm completely stupid or, the guides are not easy to follow or the process (that is always touted as easy) is not very easy.
So I am asking for help. Here is what I understand are the steps that I need to acheive.
1. I need to unlock the device
2. I need to install a recovery image
3. I need to install ICS
Questions: I *think* I have done 1. How do I check? After what I believe is a convoluted process, I have installed the Android SDK. I have the drivers for the device on the [Windows 7 64bit] PC and I can see it listed when I type adb devices.
Why do I need to unlock the device? What does the act of unlocking it do? When I followed this:
http://forum.xda-developers.com/showthread.php?t=1242241
I got to step 3. I typed in the first command:
adb reboot bootloader
After much faffing around I found out from another site I needed USB Debugging enabled. Nobody told me this. No, it isn't obvious that I need this.
The boot screen appeared and gave a message at the top and then I typed in:
fastboot oem unlock
I followed the instructions on the screen. I unlocked the device. It took a while. When it rebooted I found I had to set the device back up again as if it was the first time I'd used it. "Great!" I am thinking, I've lost everything. Thankfully I backed up what I wanted so I am not bothered. Slowly the apps appeared to come back after it synched with Google. I'm assuming stuff gets backed up somewhere.
I typed:
fastboot reboot
It rebooted.I typed:
adb reboot bootloader
It rebooted into the bootloader. Now here is where things started to go off track. I typed the next command:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
I get this:
unknown partition 'recovery-Tiamat-R4c-100611-1150-cwm.img'
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img'
So what now?
I cannot believe the process to unlock and flash a rom is so unbelievably convoluted. I've read dozens of walkthroughs, how-to's and forums and each one seems to be very similar unyet there is always something different on there to what I get on my screen or something doesn't happen quite the same way.
Here is what I am trying to acheive:
I have Android 3.2 on my Xoom and I would like it to be ICS.
We'll assume that I am completely stupid and need serious handholding to get to ICS. Is there anyone that can help with these seemingly simple steps?
One thing I keep reading is about the recovery image file. Is this related to Cyanogenmod? I am assuming as it is called a recovery image file it helps you get back when things go wrong.
Thanks and much love to the person that takes up the reigns and helps me out here.

Hi!
If you are rooted already that's pretty easy. But if not, try using LordAIOTool to root (yea it's mine and I think it's worth a try). After you are rooted flash a new recovery - download from development section - after, rename the recovery to recovery.img and then use the following commands on adb, fastboot and this recovery folder (simultaneously)
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Then after keep clicking the vol- after 2s of your tablet appears on Motorola logo. Then keep cycling until appears Android Recovery then press vol+
You are on recovery now, just select install zip from sdcard...
Good luck
Sent from my MZ601 using XDA Premium HD app

If you wanted your xoom rom'd, then you could try wesamothman's guide: http://forum.xda-developers.com/showthread.php?t=1717402 It is great for beginners and the experienced alike.
This is for the wifi only xoom MZ604. There is another guide by him i believe for the MZ602

Do I need to flash a new rom to get root on my MZ604? What is the easiest way to just root the stock 4.0.4 firmware? I have no desire for a different rom. I just want to root it.

Hey there.
If you don't want to flash a custom ROM and only want to root it, try this:
1) unlock your bootloader.
2) thru ADB, flash a recovery image.
3) thru Recovery, flash superuser flashable zip: http://www.4shared.com/zip/g3yzbrIa/...?cau2=403tNull

I ran the first couple of steps to unlocking. That is as far as I have got. As I said, I have tried so many of these walkthroughs and not one of them has all the steps. They all make an assumption somewhere along the line.
For example: xxlordxx replied with:
"If you are rooted already that's pretty easy".
I'm not, that is the problem.
Again:
1. adb reboot bootloader
2. fastboot flash recovery recovery.img <---- This didn't work and gave me the error I pointed out earlier and that is where it all stopped. Noone explains what to do when it goes wrong.
Anything passed this stage is irrelevant until I can sort out the problem above.
yosterwp, you mentioned wesamothmans guide. I will try that one as it looks a bit more "dummies guide-like" and it is for my exact device which is the MZ604 wifi only. I hadn't seen this one as it was only posted a couple of days ago
Just so I know, can someone anser these questions? I'm sure they're very simple but I don't know.
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
2. Is unlocking the same as setting s-off?
3. If not, what is the difference?
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
5. What is Cyanogenmod and do I need it or is this another custom rom?
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Thanks for everything so far. I will let you know how I get on with wesamothmans guide.

Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions

wesamothman said:
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
Click to expand...
Click to collapse
You did
Much love!

[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] Can anyone help me flash back to stock rom

I'm sorry if others have helped on this before but I can't find real clean instructions on how to do this. I bought a phone that has CM installed on it but can't active on Sprint because I can't do ##...#. I need to know how to get back to the stock rom that I don't have a back up of. Is there a easy way to reinstall the Sprint made rom? I did not root this phone myself but it came rooted so trying to figure this out with out a lot of back ground knowledge here. Thanks for your help.

adamsmiley said:
I'm sorry if others have helped on this before but I can't find real clean instructions on how to do this. I bought a phone that has CM installed on it but can't active on Sprint because I can't do ##...#. I need to know how to get back to the stock rom that I don't have a back up of. Is there a easy way to reinstall the Sprint made rom? I did not root this phone myself but it came rooted so trying to figure this out with out a lot of back ground knowledge here. Thanks for your help.
Click to expand...
Click to collapse
Use RSD Lite and an appropriate FXZ file from here.
http://forum.xda-developers.com/showthread.php?t=2095536

Do you have any where I can find help on this? I pull in my phone in AP Fastboot like I found on a different site pulled it in and went flashed but it failed with an error of "unknown fastboot command (getvar)"

Do you have any where I can find help on this? I pull in my phone in AP Fastboot like I found on a different site pulled it in and went flashed but it failed with an error of "unknown fastboot command (getvar)"

adamsmiley said:
Do you have any where I can find help on this? I pull in my phone in AP Fastboot like I found on a different site pulled it in and went flashed but it failed with an error of "unknown fastboot command (getvar)"
Click to expand...
Click to collapse
There's a couple of lines you need to remove from the XML file. Read the first post carefully.
Sounds like you put your phone in fastboot mode correctly, so you are almost there.

thanks so much that fixed it. I love the help from this site.

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)