Related
(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
Greetings fellow GNex owners and enthusiasts!
I've been trying to root my Galaxy Nexus unsuccessfully for the past week.
Here's what I've done so far:
1. I Unlocked the bootloader as per Droid-Life's instructions using an old method with the cmd prompt. (The complete How-To guide on their website) I installed the SDK on a windows 7 64-bit machine and went ahead with the process. This worked fine.
(*Note: My Gnex is stuck on 4.0.2 and it won't pull an update. I've tried the method of clearing the data from the framework app and resetting the clock to 1969 multiple times without success. probably 10-15 times.)
2. Since that I've tried uninstalling/reinstalling drivers, rebooting, and then rebooting some more. I've tried every available "noob-proof" method out there and i can't get it to work.
Tried Galaxy Nexus Tooklit v5.6
With and without the included drivers. tons of reboots and re-tries. root always fails.
Wugfresh's Toolkit 1.3
with and without the included drivers. tons of reboots and re-tries. root always fails.
Manually pushing CWM Recovery and SU to the phone with cmd promt via other tutorials floating around the internet, etc. Pushing CWM Recovery fails. Can't even get the temporary flash going to install SU
NOTHING works.
Is it because I unlocked the bootloader manually using an older method first?? I'm pretty sure I've been following the various instructions with each method accurately.
Can someone shed some light on me? I don't necessarily want to mess with kernels and custom ROMs. I just want to be able to wirelessly tether like I could with my OG and D2.
Thanks in advance,
Thanassi
Check my sig and try my method?
Haha.
But I'm guessing driver error.
The simplest method for getting drivers is to download and install pdanet on your PC. Then simply try again.
http://junefabrics.com/android/
I've had to root my phone 3 times and each time took 3 tries before it took. As mentioned before also make sure your drivers are good. And su files.
bow chicka wow wow.
Check my signature. Try that out.
TADA!! You're rooted, and you can flash stock 4.0.4 (And root it, at the same time ^^)
LG familyguy59\Beatsleigher
I'm a noob too.
I followed the following method:
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
shohratshankar said:
I'm a noob too.
I followed the following method:
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
Click to expand...
Click to collapse
As I am most likely NOT going to watch this video; Does it contain any Rundll32 commands?
If not, then the tutorial can't be all that good...
Because you need to tell Windows, that it should NOT always search Windows Update, for drivers. They're mostly crap, to be as nice, as I can...
familyguy59 said:
As I am most likely NOT going to watch this video; Does it contain any Rundll32 commands?
If not, then the tutorial can't be all that good...
Because you need to tell Windows, that it should NOT always search Windows Update, for drivers. They're mostly crap, to be as nice, as I can...
Click to expand...
Click to collapse
U don't need to watch the Video, you can read the details given in the site with the screenshots. Totally simplified.
No SDK, no rundll32 .... just installing of drivers and using command prompt
shohratshankar said:
U don't need to watch the Video, you can read the details given in the site with the screenshots. Totally simplified.
No SDK, no rundll32 .... just installing of drivers and using command prompt
Click to expand...
Click to collapse
Yes. You don't need the SDK, as a matter of fact
The Rundll32 part, is a fact, when installing the drivers...
It has the following effect:
You have installed ADB drivers (no Rundll32). You are flashing away, and all of a sudden. BANG! Everything stoppen. Phone's bricked... Why? Windows thought it is being smart, and installed new drivers, whilst you were working. However, with the RunDll32 command, you can tell Windows, that YOU want to install the drivers manually, and check manually. Of course, you can turn this off, if you want. No prob. but I personally recommend leaving it off
It's saved many phones' lives ^^
so you are having trouble with the adb or fastboot drivers? is so i had this problem too and sometimes even have to reinstall those drivers after flashing a rom.
i had to manually install the drivers using device manager, just select the android device and go to update driver. Choose "Browse my computer for driver software" then pick "Let me pick from a list of device drivers on my computer" then choose Google in that list.
Error
familyguy59 said:
Check my signature. Try that out.
TADA!! You're rooted, and you can flash stock 4.0.4 (And root it, at the same time ^^)
LG familyguy59\Beatsleigher
Click to expand...
Click to collapse
I get an error message with this application whenever I attempt to do something.
tried that
shohratshankar said:
I'm a noob too.
I followed the following method:
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
Click to expand...
Click to collapse
Yea I tried that one too. Didnt work. pushing CWM Recovery always fails
thanassi44 said:
Yea I tried that one too. Didnt work. pushing CWM Recovery always fails
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=24360114&postcount=10
GSM only??
efrant said:
http://forum.xda-developers.com/showpost.php?p=24360114&postcount=10
Click to expand...
Click to collapse
Just followed that link but the CWM Recovery is for GSM. My nexus is LTE Verizon. Will this work?
Thanassi
thanassi44 said:
Just followed that link but the CWM Recovery is for GSM. My nexus is LTE Verizon. Will this work?
Thanassi
Click to expand...
Click to collapse
No, just replace the recovery with the late version. Look for it in the dev section. It has its own thread.
Sent from my Galaxy Nexus using Tapatalk 2
FINALLY! Have Root.
efrant said:
No, just replace the recovery with the late version. Look for it in the dev section. It has its own thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for all your responses and suggestions. I finally got something to work. After some more driver swapping and rebooting, now on an XP machine, I got wugfresh's toolkit 1.3 to flash cwm recovery and I was able to install su. The program then ran an automated script to allow permanent flashing of cwm recovery. Got my titanium backup and from manager back, as well as wireless tether. Thank you all for your attention and patience!
Had such a hard time with this phone that I was beginning to have buyers remorse. Now its been set free.
thanassi44 said:
I get an error message with this application whenever I attempt to do something.
Click to expand...
Click to collapse
Sorry, but I've tested this program, over and over. I use it, myself. I never habe any problems...
But, I'm in the making, of a Youtube video. I'll post it, in my thread Then maybe you can see, what you did wrong
thanassi44 said:
I get an error message with this application whenever I attempt to do something.
Click to expand...
Click to collapse
Hang on... Did you install the scnd. file, within the ISO? If not, there's your problem...
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
So about two weeks ago, while installing a new rom, I managed to format my storage before flashing the rom. After doing that, there obviously was no rom to flash. Or anything else for that matter. My phone now can only boot into recovery mode. When trying to turn it on, it goes as far as the google screen showing the unlock icon. I would surely appreciate any help from you guys. Thank you in advance and I apologize for anything noobish i have or undoubtedly will say in the future.
By the way, here is my set up:
Verizon Galaxy Nexus
Windows Vista 32 bit PC
Again, Thank you
I am not near my PC but you have to enter into fast boot mode and push your ROM.zip to your phone using adb
Sent from my Nexus 4 using xda app-developers app
When i last tried that, ADB would not recognize my phone
jaysondasher said:
When i last tried that, ADB would not recognize my phone
Click to expand...
Click to collapse
If you are running a custom recovery, ADB should work. You probably are having driver issues.
Fastboot, flash stock. If you're phone isn't being recognized, install drivers.
Sent from my Galaxy Nexus using xda app-developers app
cupfulloflol said:
If you are running a custom recovery, ADB should work. You probably are having driver issues.
Click to expand...
Click to collapse
ADB does work on a custom recovery. You're right, he's having driver issues, he's just too lazy to search. THIS QUESTION has been answered a zillion times and is well documented in efrant 101 stickied on General section.
a manta wrote this.
---------- Post added at 04:42 AM ---------- Previous post was at 04:39 AM ----------
peikojose said:
I am not near my PC but you have to enter into fast boot mode and push your ROM.zip to your phone using adb
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Go read efrant 101 sticked on General section, please.
jaysondasher said:
When i last tried that, ADB would not recognize my phone
Click to expand...
Click to collapse
Of course, fastboot mode doesn't have ADB. Only fastboot.
a manta wrote this.
I don't think it's a problem of me being "lazy". I have been searching for over 2 weeks to find a post that helped me, and I wasn't able to because people on here seem to assume you know exactly what you're talking about, and throw around fancy android lingo that I'm unfamiliar with.
But I have uninstalled the drivers I previously had for my nexus and am going to try again. I also deleted ADB I think, so I'll have to get that again.
So, I installed Samsung's drivers, then went to adb and tried to sideload a rom, but was given the error: "device not found". I had my phone plugged in and booted into the recovery mode. I dont know what I'm doing wrong.
To the OP i really hope you get things sorted out. But some advice if you really do not know anything about your device, about rooting or how to use your device in conjunction with a computer then you need to do a lot more reading and research. Using ADB, Fastboot and being able to have your computer recognize your Gnex is all the first essential part of beginning to unlock the bootloader and rooting the device. So you should be very familiar with this unless you either had someone else root your phone or you used a root toolkit which is the reason why you don't understand what the steps may be or the wording. Toolkit are the worst to use just because of that reason. Also the fact that you wiped your internal memory also leads me to believe you don't know what you where doing because before it deleted it it asked you 'are you sure'. Please spend some time reading and learning educate yourself, do not expect anyone to solve it for you. Every rom, every guide and post on here always starts off by warning you that you are solely responsible for what you are about to do. Read, read and read again.
Sent from the future via Tapatalk 4
jaysondasher said:
I don't think it's a problem of me being "lazy". I have been searching for over 2 weeks to find a post that helped me, and I wasn't able to because people on here seem to assume you know exactly what you're talking about, and throw around fancy android lingo that I'm unfamiliar with.
But I have uninstalled the drivers I previously had for my nexus and am going to try again. I also deleted ADB I think, so I'll have to get that again.
Click to expand...
Click to collapse
fancy android lingo?
This 'lingo' that gets tossed around is the basic knowledge one should know when customizing (rooting/flashing/modifying) their Android device.
Would you go and start modifying the engine in your car without some basic understanding of how it works, or what the parts are called and located?
Why would you treat your electronic devices any other way?
That post tells me you didn't even read the damn sticky I was talking about.
If you had read this, you would understand the "fancy android lingo" by now. And @jaysondasher, I have another link for you, here.
Have a nice day.
Don't boot into recovery. Boot into boot loader mode. Power and both volume buttons. Then, using fastboot flash stock.
Sent from my Galaxy Nexus using xda app-developers app
was able to get it figured out. Sorry if I frustrated any of you, but thank you for your help.
Sent from my Galaxy Nexus using xda app-developers app
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.