Develop Bugs

[Guide][TOOL] FASTBOOTROOT (deprecated)

(DEPRECATED)
I no longer support or care to support this is someone wants to take over and deal with this and the complaints go for it. It has not been tried on the 2.2.2 version of android in case you want to try it.
Tired of all those funky ways of rooting? Wanna just push a button and be rooted?
Guess what I've got something for you.
Introducing FastbootRoot (patent not pending) for the virgin mobile optimus v
FastbootRoot was designed with simplicity in mind. The easy to use ui makes rooting your lg optimus easy and quick without all those adb commands. It takes the guess work out ( is this right, what does he mean by that? ) of rooting your phone.
Features:
flash a custom recovery
this feature only flashes a custom recovery without rooting your phone giving you the ability to back up your current system without root. I put this in here in case of needing to return the phone for warranty matters
flash the entire shebang
This flashes a new boot image, a new system image*, and custom recovery.
Revert to stock
thanks to destundead we now have the stock system image and boot combined with my stock recovery we are good to go
New experimental install windows xp fastboot drivers
My goal is to fully automate this process and to make this as painless as possible for the new users. This new feature is untested and will either work or it won't. Give me some feedback if it does or doesn't.
--------------------------How to Use--------------------------
Download fastbootroot from here and place it on your desktop.
Download the usb drivers from here
On your phone turn on usb debugging by pushing menu, then settings, then applications, then development, and then usb debugging.
Install the drivers ( I find that rebooting after the drivers have been installed will install a whole new set of drivers. I recommend this method)
unzip fastbootroot and inside double click the fastbootroot file. Make your selection and your done.
Here's a video on using it and a little explanation
watch it here
WHAT THE FUTURE HOLDS:
no need to install usb drivers
Enjoy this and remember this works fully on windows 7 and I tested it myself. No matter what there's always room for user error though in which case I take no responsibility if things go wrong.
PROBLEMS AND COMPLAINTS
Some people are reporting problems like drivers not installing or other things. First off if you have a problem you need to state exactly what operating system you are using (windows 7, windows vista, or windows xp).
This only works with the virgin mobile optimus v. Make sure you have the virgin mobile optimus v (not a optimus t, m or a picture of the v pasted on top of a w490)
Tell me what you did exactly don't lie. I know from experience when someone says, 'I did this I definitely didn't do that', whether or not they are holding something back. The more info you can give the better if your holding something back that's gonna delay the process.
This is free. I ask for donations but they aren't required at all. So when your asking for more things remember this is free.
Like my work donate to me herehttps://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FEP8NQ8J49MX8
*the new system image is stock with root, flash_image and busybox installed

It's fully automated?
Sent from my VM670 using XDA App

overthinkingme said:
It's fully automated?
Sent from my VM670 using XDA App
Click to expand...
Click to collapse
yep the only thing that you gotta do is download fastbootroot and the lg drivers. It will take care of everything else for you. I will say that I've tested this and my earlier variant of it quite a few times. I even made a video for the other one.

Downloading this now. will give it a try. Thanks!
--bornagainpenguin

This is for lg optimus v for virgin mobile, right?
Sent from my SGH-T959 using Tapatalk

i get a write error suspended reset port change on my phone when trying to run this? it says waiting on device on the fast boot system? any ideas what im doin wrong thanks

shaynes vibrant said:
i get a write error suspended reset port change on my phone when trying to run this? it says waiting on device on the fast boot system? any ideas what im doin wrong thanks
Click to expand...
Click to collapse
your in fastboot by now you should be good unless you did something crazy. What will happen is windows will automatically install the fastboot drivers and do it's thing and you'll be good

Asadullah said:
your in fastboot by now you should be good unless you did something crazy. What will happen is windows will automatically install the fastboot drivers and do it's thing and you'll be good
Click to expand...
Click to collapse
This does not seem to be happening. How can I abort the fastboot procedure so I can reboot and try again?
--bornagainpenguin

Hello? Please someone be there who can help me!
The detection sequence you describe did not work, Windows is not finding the drivers properly. Is it safe to reboot the machine while in fastboot? Can I unplug the USB without bricking my phone?
--bornagainpenguin

If nothing has flashed, I'm sure you're fine. It dependant on how far it got .
Would op mind posting the manual way to root through fast boot?
Sent from my VM670 using XDA App

bornagainpenguin said:
Hello? Please someone be there who can help me!
The detection sequence you describe did not work, Windows is not finding the drivers properly. Is it safe to reboot the machine while in fastboot? Can I unplug the USB without bricking my phone?
--bornagainpenguin
Click to expand...
Click to collapse
yes your okay to unplug your phone the process either works all the way or not at all I'm confused as to why it didn't install the drivers though. I guess I'll just have to add them to the batch

overthinkingme said:
If nothing has flashed, I'm sure you're fine. It dependant on how far it got .
Click to expand...
Click to collapse
How do I know?
Right now the screen says:
Code:
Fastboot mode started
gpio_12c: invalid khz: 0
b1: i2c write error
udc_start()
-- suspend --
--reset --
-- portchange --
-- reset --
-- portchange --
STALL GET_DESCRIPTOR 128 6 1006 0 18
-- reset --
-- portchange --
-- reset --
-- portchange --
I removed the battery and the phone restarted without issues. Not sure why things did not go the way they're supposed to--could it be because I had the drivers from the ROMTOOLS package installed before? NOTE: Prior to trying this procedure I uninstalled all of those and rebooted before installing the drivers linked here.
Another thought, OP says he is running Windows Seven; I am on Windows XP. Could this have anything to do with my trouble?
--bornagainpenguin
UPDATE: I tried installing the drivers included with the ROMTOOLS package and my phone was recognized again. No luck when trying to run fastboot. Not sure why this is happening or why I am unable to use the drivers OP linked to. They seem to install when clicked but the system doesn't seem to think the drivers apply to this phone for some reason...

Okay what happened was your fastboot drivers didn't install correctly I'm in the process of uploading a video to show you how to install the fastboot drivers.
I wrote this while before your last post yes there is a problem with windows xp. It doesn't download them like it would on windows 7. I can test all day long on windows 7 but not on xp. The method in the video should work for xp users

Asadullah said:
Okay what happened was your fastboot drivers didn't install correctly I'm in the process of uploading a video to show you how to install the fastboot drivers
Click to expand...
Click to collapse
I appreciate the effort, but unless the video is closed captioned it may not do me much good. I am hard of hearing (one of the reasons why I picked this phone was its high T4 rating which works well with my hearing aids and telecoil adapter --think headphones for hard of hearing people) so cannot always hear audio on videos very good.
--bornagainpenguin

bornagainpenguin said:
I appreciate the effort, but unless the video is closed captioned it may not do me much good. I am hard of hearing (one of the reasons why I picked this phone was its high T4 rating which works well with my hearing aids and telecoil adapter --think headphones for hard of hearing people) so cannot always hear audio on videos very good.
--bornagainpenguin
Click to expand...
Click to collapse
It's recorded in 780 hd using camstasia. Even if you can't hear it you'll be able to follow along the process is very simple

http://www.youtube.com/watch?v=aTE30yd-P_U
here's the video

I've integrated the fastboot drivers into the next release for windows xp I need a beta tester before I release this.

Does this just root our existing system, or does it install a whole new rooted image (requiring us to reinstall all of our programs and settings)?
I have XP, by the way. If it just roots, I would be willing to beta test (but if it doesn't work, if it doesn't work, I want to be able to get back to where I was as my phone works well).

This is F*****KIN GREAT!!!! Thanks!!

I'm having bootloop issues and I see a post here which suggests that one way to fix the situation is with fastboot. Do you know if fastboot can help me? If so, how?
--bornagainpenguin

[GUIDE] Rooting Sprint Intercept froyo 2.2 [06-02-11]

I've successfully permanently rooted my Sprint Intercept with the latest 2.2 froyo on it without installing custom kernels and wanted to share steps I took since there is some confusion and differences.
Original guide link.
Things you'll need:
Root files.
Samsung drivers.
Windows 7/vista/xp 32 bit.
Steps:
Install Samsung drivers
Reboot your PC
Reboot your phone, connect it to your PC with a usb cable
Put your phone in debugging mode (menu->settings->applications->development)
Extract root files to your c:\intercept-root folder (or any folder you wish)
Start windows command line (start->run->CMD)
Change to your "intercept-root" folder
Execute START_ROOT command
Follow instructions
Once done, don't forget to install Superuser apk.

after you rooted it you were able to put a different rom on it right. trying to clear out the garbage that comes on it.

shonok said:
after you rooted it you were able to put a different rom on it right. trying to clear out the garbage that comes on it.
Click to expand...
Click to collapse
No, this is just simply to root and remove stuff you don't want. I suggest Titanium backup. There is no proper recovery for the intercept that I know of. The one existing can be flashed and it does work but has some issues with what it backs up and what it restores. It's not complete and may create problems.
If you are rooting the latest 2.2 froyo, after removing all sprint apps you are left with true bare stock so there is really no need for anything else. Make sure you don't remove the sprint vm even if you are using google voice. It needs to be on because of system integration.

you mae one error. the drivers can't be installed on windows 7. I have gotten the drivers from the moment to work once but now its nothing. my computer no longer recognizes the phone when i plug it into the computer. which means that i cant root it or anything. sucks and i need serious help.

hmmm, same problem
Find a friend with a XP laptop and use that?
Glad to know - i have failed at rooting my intercept a few times and have been using my windows 7 box. Trying these instructions from a laptop - will report back!

Success
Using nothing but a old crappy dell laptop runing windows XP I was able to gain perma root using the instructions provided here. On my first run of the script the process failed, I simply did what the program told me to (run the script again) and it worked like a charm.
OP - thank you so very much for taking the time to post.
Question for anyone: now that I have root, I *really* want to be able to use my Intercept as a wi-fi hotspot. Can I do this? Where do I start?

No errors. I got drivers under Windows 7 working but I clearly said it has to be 32 bit as 64 does not work. Check your version.

entropy.of.avarice said:
Using nothing but a old crappy dell laptop runing windows XP I was able to gain perma root using the instructions provided here. On my first run of the script the process failed, I simply did what the program told me to (run the script again) and it worked like a charm.
OP - thank you so very much for taking the time to post.
Question for anyone: now that I have root, I *really* want to be able to use my Intercept as a wi-fi hotspot. Can I do this? Where do I start?
Click to expand...
Click to collapse
Download wireless tether app. I've had troubles with it in the past so if that one doesn't work try Barnacle.

how to flash cmo1 custom recovery after phone is rooted?

Just throw intercept root on sdcard and run
All I had to do it throw the root on the sdcard. Run it from the file manager, and then download barnacle. Sweet! Done!

Ignorance1 said:
how to flash cmo1 custom recovery after phone is rooted?
Click to expand...
Click to collapse
I don't believe there is a supported recovery for the intercept. There is one hacked up but there are some issues with it so I don't recommend it.
Sent from my Nexus S 4G using XDA App

obsanity said:
I don't believe there is a supported recovery for the intercept. There is one hacked up but there are some issues with it so I don't recommend it.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
There is no problems with the custom recovery. I recommend it if you want to try custom roms/themes. Check sdx for all things intercept
Sent from my PG06100 using Tapatalk

Can you fix/update the links, please? I need to files for root, drivers, etc. Everything I need to root my backup phone, please.

ThunderOKC said:
Can you fix/update the links, please? I need to files for root, drivers, etc. Everything I need to root my backup phone, please.
Click to expand...
Click to collapse
Yeah, me too.
Looking to root my Intercept, but the 4shared link is broken
UPDATE: OK, I think this is what he was linking to. But my Antivirus doesnt like it. It says it's a virus. A severe virus.

[Q] Galaxy Nexus ToolKit, firmware build selection question

Hey Guys,
New to the forum here and quite a noob on Android Systems. The GNex is my 1st smart phone and I've had it for 6 months now.
Wanting to root, unlock, and flash the new JB rom onto my phone and is using the ToolKit for the process.
-----------------------------------------------------------------------------------------------------------------------------------------
The original problem is now immaterial, what is bothering me now is installing drivers.....I cannot seem to find a way to properly install the proper drivers for my galaxy nexus. All my laptop would do is install the stock drivers upon connecting the phone to the laptop.
It doesn't matter what drivers im trying to install the condition is the same. I've so far tried out two ways, 1st is following the step by step instruction from efrant, 2nd is installing using the Galaxy Nexus ToolKit v7.0.
For a android noob like me I really have no idea what is going on here @@"
oh and what role does "USB debugging" play in installing drivers? when should it be ticked and when should it not???
----------------------------------------------------------------- below is my original question posted --------------------------------------
However during the 1st step where I need to select my firmware build, I realised the IMM76k build is listed under CDMA where my GNex has this build but is a GSM model.
How should I proceed?? Choose a similar build under GSM or choose the correct build but under CDMA instead??
thanks guys

I would root,unlock, and flash recovery via adb so incase something doesn't work you'll know what happened. Also if you want to use the toolkit just select the correct version under gsm and install the drivers. It should work

I personally would not use a toolkit, as you learn nothing by going that route.
If you want to do it yourself, look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
I personally would not use a toolkit, as you learn nothing by going that route.
If you want to do it yourself, look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
actually I was going to do it your way by following through all the steps you have listed out. Like you have said somewhere its like learning math 1st before using a calculator.
However I found myself stuck at the very first part.....installing drivers....
Before yesterday I have not tried to install any driver myself. I guess the only driver that was ever installed to my PC is the one that automatically runs when you plug your phone into a computer for the first time.
When I was following your steps, I first went into device manager --> galaxy nexus --> details --> uninstall driver
and then I have no idea how to install the drivers that I have DL from following your steps. I remember in the instructions you said to plug in my GNex and I should be able to direct the PC to install whatever driver I want, but instead the PC just automatically installed the original drivers again...
So today I decided to give the toolkit a go. As you have seen the 1st problem I ran into was the mixed up variants.....(what does "build code" stand for anyways??)
And the second problem im having now is, again.....it wouldn't install the universal driver. Or at least it does not seem to have installed....
Well, now that I've got your attention D) I would like to follow your steps again if I can get pass the driver issue....I like the JB rom you have uploaded better anyways~~ fan of original stuff from Google!
thanks!!!

Just to mention, my purpose of doing all this is to get to JB faster, and maybe learn more about my device on the way.
My GNex is a GSM model, yakjuzs, build code is IMM76k (this is the odd part) if these information would help solving my problem.
I normally prefer stock google released ROMs.

@CloakedUltraling, installing the drivers is the only tricky part. You need to get to the point where you see something like "Android 1.0" in your device manager with a yellow exclamation point.
To get to that point, right click on anything you see related to Samsung or Android in device manager and click uninstall. Then go to View in the menu at the top and select show hidden devices, and uninstall anything related to Samsung or Android. Then reboot your PC, and once booted, plug your device (while it is booted into the bootloader) to your PC.
Now, you should see something like "Android 1.0". Right-click on that and select update driver, then follow the menu to manually install it, and navigate to the directory where you unzipped 1wayjonny's driver. This needs to be done TWICE: once when your device is booted into the bootloader, and once when it is booted normally.

i was doing some reading since I've missed out the backup step....lol
and I realised that having ADB installed seems to be a pre-requisite for pretty much everything...and which I have not done.
Is this the case for removing/installing drivers as well? ie, do I need ADB installed before doing all this??
OHHHH and Android SDK as well....this looks REALLY important but I have not had any knowledge of this either. Guess I should start from the Android SDK first??

CloakedUltraling said:
i was doing some reading since I've missed out the backup step....lol
and I realised that having ADB installed seems to be a pre-requisite for pretty much everything...and which I have not done.
Is this the case for removing/installing drivers as well? ie, do I need ADB installed before doing all this??
OHHHH and Android SDK as well....this looks REALLY important but I have not had any knowledge of this either. Guess I should start from the Android SDK first??
Click to expand...
Click to collapse
SDK is not required for you (unless you are developing... )
Drivers need to be installed before you can use adb and fastboot - one for each.
Sent from my Galaxy Nexus using Tapatalk 2

Trying to Root - Driver install issue

I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer

Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.

I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app

Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .

What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.

Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little

Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.

So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there

Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now

Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...

i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250

Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier

The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!

I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus

The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT

[Q] What should I do to restore my Nexus 7 (2013) to work on which I tried to root?

Hello,
I tried to root my new Nexus 7 (2013). I am not able to post the link of the tutorial which I followed (from androidrootz). I tried contacting the author of that tutorial - he did try his best but was not able to change the state.
When about to complete the entire process, close to the finish - I am not able to get inside the "Recovery Mode" to install Super User SU. i.e. When I press recovery mode in the bootloader I get the Google logo and it stays there till battery runs out.
Now when I start the tablet normally, I get the Google logo and the nexus logo. Then nexus logo stays there till the battery runs out.
I am a developer and I kinda need the tablet to run. My main purpose of rooting the tablet is to use certain admin feature and install a custom ROM.
If I could straighten up my tablet to work the way it does - that would really great. I am not bothered about the loss of data at all.
I could use both Windows and Mac to get things in order. At this moment I am not sure what the problem is nor do I know what to do.
If someone could guide me thro' to get the tablet up and running the normal, I highly appreciate it.
Thank you and regards,
Karsnen.

karsnen said:
Hello,
I tried to root my new Nexus 7 (2013). I am not able to post the link of the tutorial which I followed (from androidrootz). I tried contacting the author of that tutorial - he did try his best but was not able to change the state.
When about to complete the entire process, close to the finish - I am not able to get inside the "Recovery Mode" to install Super User SU. i.e. When I press recovery mode in the bootloader I get the Google logo and it stays there till battery runs out.
Now when I start the tablet normally, I get the Google logo and the nexus logo. Then nexus logo stays there till the battery runs out.
I am a developer and I kinda need the tablet to run. My main purpose of rooting the tablet is to use certain admin feature and install a custom ROM.
If I could straighten up my tablet to work the way it does - that would really great. I am not bothered about the loss of data at all.
I could use both Windows and Mac to get things in order. At this moment I am not sure what the problem is nor do I know what to do.
If someone could guide me thro' to get the tablet up and running the normal, I highly appreciate it.
Thank you and regards,
Karsnen.
Click to expand...
Click to collapse
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.

sfhub said:
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.
Click to expand...
Click to collapse
It worked. Thank you so much.
I just want to know, if you could recommend a guide for rooting the new nexus 7 on windows machine, what would that be?
Thank you once again.

Check in the stickies for detailed instructions. If you just want a simple summary:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339

sfhub said:
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.
Click to expand...
Click to collapse
So I'm using a Mac OSX 10.8.4, and the new Nexus 7 (2013) version. I unlocked my bootloader, but I cannot get it into recovery mode, and I'm a little nervous. This is my first android device, but I've been an avid iOS jailbreaker since the OG iPhone. Can any of you point me to an extremely thorough guide on how to both fix my current issues, and then properly Unlock, Recovery, Root, and Flash Custom ROMs to this tablet?
Thank you so much.

tr00gle said:
So I'm using a Mac OSX 10.8.4, and the new Nexus 7 (2013) version. I unlocked my bootloader, but I cannot get it into recovery mode, and I'm a little nervous. This is my first android device, but I've been an avid iOS jailbreaker since the OG iPhone. Can any of you point me to an extremely thorough guide on how to both fix my current issues, and then properly Unlock, Recovery, Root, and Flash Custom ROMs to this tablet?
Thank you so much.
Click to expand...
Click to collapse
Buddy,
I was in the exact similar position as you are. Do not fear. Just follow the response I got above. It will help you.
Just follow it.
regards,
Karsnen.

karsnen said:
Buddy,
I was in the exact similar position as you are. Do not fear. Just follow the response I got above. It will help you.
Just follow it.
regards,
Karsnen.
Click to expand...
Click to collapse
Are the commands the same in terminal, or should I run windows in a VM to use the command line?

The only cmd in that post is flash-all
It is the same. Get into the directory and enter flash-all when you have to, in the terminal.

When I'm in the VM in windows, I go to the directory, but then it says "flash-all" is not a valid command. What am I doing wrong? It won't work in Terminal either. Can you please walk me through it. I feel so stupid as is, but I can't figure out what I'm doing wrong.

tr00gle said:
When I'm in the VM in windows, I go to the directory, but then it says "flash-all" is not a valid command. What am I doing wrong? It won't work in Terminal either. Can you please walk me through it. I feel so stupid as is, but I can't figure out what I'm doing wrong.
Click to expand...
Click to collapse
Did you unpack the google image download twice? (per the instructions) Once to get the tar from the tgz and a second to get the files from the tar.

sfhub said:
Did you unpack the google image download twice? (per the instructions) Once to get the tar from the tgz and a second to get the files from the tar.
Click to expand...
Click to collapse
Ok, I MUST be using the wrong guide or something, because I don't have any files with a .tar extension. I promise I'm not this dumb, but I can feel my frustration making me dumber. Halp

course ndighdl
tr00gle said:
Ok, I MUST be using the wrong guide or something, because I don't have any files with a .tar extension. I promise I'm not this dumb, but I can feel my frustration making me dumber. Halp
Click to expand...
Click to collapse
OK, i forgot to download the image files from google. Now I'm doing it, and it says fastboot is not a valid command, and nothing is happening.

tr00gle said:
OK, i forgot to download the image files from google. Now I'm doing it, and it says fastboot is not a valid command, and nothing is happening.
Click to expand...
Click to collapse
Did you do step #3 in the guide?
http://forum.xda-developers.com/showthread.php?t=2428194

sfhub said:
Did you do step #3 in the guide?
http://forum.xda-developers.com/showthread.php?t=2428194
Click to expand...
Click to collapse
Is that link to the guide? there wasn't one on that link. I appreciate you replying this many times already, but I just need one set of steps to follow, that are clear and detailed. That's all. Do I need to use windows, mac or linux? I have a macbook pro, but I can run windows or linux in parallels if necessary. I just need to KNOW. Please.