So I just picked up this device couple days ago. It's running 4.4.2
This has surely been asked before but how do I root this build? I only found TUTs for 4.3 here on xda
Thanks
PS. This is my first nexus device
//Sent from somewhere in your house
Wug's Nexus Root Toolkit v1.8.2
http://forum.xda-developers.com/showthread.php?t=2389107
lzzar said:
So I just picked up this device couple days ago. It's running 4.4.2
This has surely been asked before but how do I root this build? I only found TUTs for 4.3 here on xda
Thanks
PS. This is my first nexus device
//Sent from somewhere in your house
Click to expand...
Click to collapse
Fastboot commands to unlock bootloader and install TWRP. Then flash a root zip.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
Fastboot commands to unlock bootloader and install TWRP. Then flash a root zip.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which command is to unlock the bootloader?
//Sent from somewhere in your house
lzzar said:
Which command is to unlock the bootloader?
//Sent from somewhere in your house
Click to expand...
Click to collapse
fastboot oem unlock
okay so I unlocked the bootloader and flashed recovery. I can boot normally but not into recovery. it gives me the android with the red triangle.
I know the BL is unlocked cause I see the lock symbol at the Google screen
I tried both cwm and twrp
Help?
lzzar said:
okay so I unlocked the bootloader and flashed recovery. I can boot normally but not into recovery. it gives me the android with the red triangle.
I know the BL is unlocked cause I see the lock symbol at the Google screen
I tried both cwm and twrp
Help?
Click to expand...
Click to collapse
It sounds like you still have the stock recovery installed instead of the custom one you're trying to flash. What command are you using to flash the custom recovery? It should be:
fastboot flash recovery [insert recovery filename here].img
Then, use the volume buttons to boot into recovery from the bootloader. Your custom recovery should boot up.
Yeah I used that command. I have used it before on my Optimus 3D
//Sent from somewhere in your house
lzzar said:
Yeah I used that command. I have used it before on my Optimus 3D
//Sent from somewhere in your house
Click to expand...
Click to collapse
Are you using the proper TWRP? You may try the command again.
Edit: In order to flash you have to CD from a folder containing adb.exe and fastboot.exe. Otherwise nothing will flash. Download this folder https://docs.google.com/file/d/0B_nizg6yUZ0NbWNvZHFMR1h6LVE/preview?pli=1 and Stick TWRP in the folder. That folder was put together by Rootjunky.com http://m.youtube.com/watch?v=6k4rCaMPSQ8
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Nevermind guys, I got it working! !
Changed a little stuff (usb port and cable, wiped data before flashing)
//Sent from somewhere in your house
@lzzar Glad you got it figured out.
Short story for anyone who might find this thread after seeing the Red Triangle.
I saw an article on Android Police that there was 32gb refurbs for sale for $170. So, clearly we (XDA members) are not the same as normal users when it comes to troubleshooting and fixing problems. So, I bought my 2 sons 1 each and my wife 1 as well. While my sons are very young (single digit ages), I've taught them how to run code. The N7's arrived yesterday and after they went to bed, I fired up the computer and had all 3 tabs going at once updating from 4.3 to 4.4.2, charging, downloading,....
Unlocked all 3 Bl's and proceeded to install TWRP and ROM/Kernels. Point to remember is that I had too many things going on at once. On the very first recovery.img flash, I got the laying down android with red triangle. Flashed the recovery.img again and again the red triangle, all the while I was downloading ROMs and Kernels on my PC.
Then I realized what I was doing wrong. After flashing the recovery.img, I booted into the OS, then powered off and used the key combo to boot into recovery. Wrong!! What step did I miss? After flashing fastboot flash recovery recovery.img, I had forgotten to Volume up and boot into recovery from straight from there.
Once I realized my blunder, I was much happier. After that, it took me under an hour to install recoveries on all 3, flash ROMs and Franco r13, boot and reflashed SuperSU. Too many things going on at once and maybe a few too many drinks as well.
Yes, the exact same mistake with booting into OS after flashing was what I did too
//Sent from somewhere in your house
Related
I tried rooting and installing a custom recovery. I got the bootloader unlocked. But when putting in fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.ing I'm getting this message fastboot is not a recognized as internal or external command. I had the files needed dowloaded so I don't know why it would not work I tried on 2 different computers got same message on both computers I played around for hours trying before giving up. Now that the bootloader is unlocked will I still get updates and be able to install them? Also did I do anything to the stock recovery? Because when in bootloader mode and I scroll to recovery it will just boot to a black screen with the Android guy on his back and a red stomach and I can't do anything but then after a few minutes it will reboot and turn on and work just fine so is there no stock recovery? Will it hurt any thing if I leave it unlocked?
Sent from my SGH-T889 using xda app-developers app
carlgraser said:
I tried rooting and installing a custom recovery. I got the bootloader unlocked. But when putting in fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.ing I'm getting this message fastboot is not a recognized as internal or external command. I had the files needed dowloaded so I don't know why it would not work I tried on 2 different computers got same message on both computers I played around for hours trying before giving up. Now that the bootloader is unlocked will I still get updates and be able to install them? Also did I do anything to the stock recovery? Because when in bootloader mode and I scroll to recovery it will just boot to a black screen with the Android guy on his back and a red stomach and I can't do anything but then after a few minutes it will reboot and turn on and work just fine so is there no stock recovery? Will it hurt any thing if I leave it unlocked?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I just replied to your other post in a different section. Glad to see you found the correct place for you to be with that second generation N7. I'll give you the response I posted there. Check out this post. Should get you going in the right direction. Just remember you have to have the tablet in fastboot for those commands to work. This post gives you a zip that has all the files you need. You can just work from that folder with fastboot and flash the recovery that way. Obviously, you can disregard that bootloader stuff because it's for the first generation N7. You just want that platform-tools.zip. That is basically how I do it. I just work from within a folder that has fastboot with the command prompt...hope it helps.
http://forum.xda-developers.com/show....php?t=2150251
Like the title say I have problem rooting my nexus 7 on Mac.
It's the second one that I have, the first one I got it rooted with techfanatic one click toolkit, but with this one it didn't worked, the only difference that I see is that the one that I have now is on jss15q while when I rooted the other one it was still on jss15j.
So since the one click method haven't worked I tried to do it manually.
I got the latest twrp for flo, the latest super su file and done so:
I navigated in the platform tools, typed ./fastboot OEM unlock selected yes and it unlocked , after I did ./fastboot flash recovery ... and it flashed.
After I pressed start to transfer the super su on my tablet bit it got stuck forever on the x logo.
I tried many times and it didn't worked.
I even tried to wipe data factory reset in twrp but it says failed.
I don't know what to do now, help please.
Sent from my Nexus 4 using xda app-developers app
Does rebooting the bootloader between unlocking and flashing the recovery is necessary, would it make it work?
Sent from my Nexus 4 using xda app-developers app
jonathanxx1 said:
Does rebooting the bootloader between unlocking and flashing the recovery is necessary, would it make it work?
Click to expand...
Click to collapse
For what it's worth, I didn't reboot after unlocking and ended up in a boot loop. Doing a factory reset from (stock) recovery fixed that. Rooting went without problems after that.
jonathanxx1 said:
Like the title say I have problem rooting my nexus 7 on Mac.
It's the second one that I have, the first one I got it rooted with techfanatic one click toolkit, but with this one it didn't worked, the only difference that I see is that the one that I have now is on jss15q while when I rooted the other one it was still on jss15j.
So since the one click method haven't worked I tried to do it manually.
I got the latest twrp for flo, the latest super su file and done so:
I navigated in the platform tools, typed ./fastboot OEM unlock selected yes and it unlocked , after I did ./fastboot flash recovery ... and it flashed.
After I pressed start to transfer the super su on my tablet bit it got stuck forever on the x logo.
I tried many times and it didn't worked.
I even tried to wipe data factory reset in twrp but it says failed.
I don't know what to do now, help please.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
which recovery did you flash? From what I see it should have worked if you used a flo recovery...
mssam said:
which recovery did you flash? From what I see it should have worked if you used a flo recovery...
Click to expand...
Click to collapse
First I flashed twrp for flo 2.6.1 but it ended up in a black screen so I flashed 2.6.0 and it's fine.
BTW I managed to root it.
What I did is I unlocked the bootloader ./fastboot OEM unlock and what I did different is I booted up the tablet , without flashing straight away the recovery.
After the boot I did a quick setup (WiFi and all that) USB debugging on and transfered the super su 1.55 and after I powered off the tablet and booted up on recovery .
In recovery I flashed twrp 2.6.0 , booted up in twrp recovery and there I flashed the super su and boom, rooted.
I will never use a toolkit anymore , the way to go is manually, also you learn how it all work when you do it manually.
Sent from my Nexus 4 using xda app-developers app
jonathanxx1 said:
First I flashed twrp for flo 2.6.1 but it ended up in a black screen so I flashed 2.6.0 and it's fine.
BTW I managed to root it.
What I did is I unlocked the bootloader ./fastboot OEM unlock and what I did different is I booted up the tablet , without flashing straight away the recovery.
After the boot I did a quick setup (WiFi and all that) USB debugging on and transfered the super su 1.55 and after I powered off the tablet and booted up on recovery .
In recovery I flashed twrp 2.6.0 , booted up in twrp recovery and there I flashed the super su and boom, rooted.
I will never use a toolkit anymore , the way to go is manually, also you learn how it all work when you do it manually.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Glad to hear you got it working... :good:
I might be doing something wrong but I can't flash any recovery ROMs to my HTC One. I used rumrunner S-off today and gained root access with my stock ROM. I tried using command prompt to flash a TWRP recovery ROM, and it only worked once but now whenever I try to do it it says either "cannot load image" or gives me a partition error.
I tried going into recovery with the one I flashed and when it says entering recovery mode it either goes into a continuous reboot cycle or proceeds to the lockscreen. I tried using flashify today too and it says my device isn't compatible with any of the recovery ROMs.
Please help, I'm so frustrated and all I want to do is flash Android Revolution to my HTC! Also, was I supposed to factory reset my phone before all this? Because I still have all my apps, photos, data, etc.
P.S. I'm a noob at this stuff so I might be doing something wrong.
Try Flashify from the play store. Put the recovery on the Flashify app and flash if.
sent from my HTC One
jbh00jh said:
Try Flashify from the play store. Put the recovery on the Flashify app and flash if.
sent from my HTC One
Click to expand...
Click to collapse
No luck. Flashify won't install anything
ak074 said:
we will need more information about what all you've been trying and the results.
s-off was successful?
bootloader locked/unlocked?
what are you typing into the cmd prompt?
result from that cmd?
where did you get the recovery from? are you sure it's for the vzw htc one?
etc...
Click to expand...
Click to collapse
S-off was successful.
Bootloader is unlocked (And somehow the phone became rooted in the process)
cmd prompt: fastboot flash recovery recovery.img
cmd prompt kept saying something about unable to load the image
Got the recovery from ClockWork Mod - It is Verizon HTC One version
Thank you guys for your concern but I figured it all out. I used an all-in-one toolkit and it flashed my recovery without a problem. Now I have a Nandroid backup for stock rooted ROM, and flashed BoneStock onto my device! It is all working great and my battery life rocks!
shadowskaya said:
No luck. Flashify won't install anything
Click to expand...
Click to collapse
OK first off make sure the recovery you are trying to flash ends in m7vzw.img second, Flashify doesn't work for everyone so you might have to do it from adb on your computer. And finally, there is no android revolution rom for the Verizon htc one.
The developer of Flashify has a thread in Android developing and hacking/ apps and games / Flashify. Sometimes these threads have updates posted before the play store does. Start at the back of the thread and read toward the beginning,find the latest info faster (about a 25 page thread).
Sent from my Galaxy Tab 10.1
shadowskaya said:
Thank you guys for your concern but I figured it all out. I used an all-in-one toolkit and it flashed my recovery without a problem. Now I have a Nandroid backup for stock rooted ROM, and flashed BoneStock onto my device! It is all working great and my battery life rocks!
Click to expand...
Click to collapse
You should try to do these things without using all-in-one kits. It's best to know what was done in case something goes wrong in the future. My guess is you were most likely trying to flash the wrong recovery.
Well, at least you're up and running!
karn101 said:
You should try to do these things without using all-in-one kits. It's best to know what was done in case something goes wrong in the future. My guess is you were most likely trying to flash the wrong recovery.
Well, at least you're up and running!
Click to expand...
Click to collapse
Thank you for the tip, I will remember that the next time I flash a recovery to something. It was the correct recovery, but for some reason the fastboot and adb wouldn't flash it. Maybe I just needed a reboot of pc or something...
Had the same issue after s-off with twrp. Ended up flashing cwm touch instead and it works just as well. Although I do miss twrp.
Sent from my One using XDA Premium 4 mobile app
So, I need to send my Nexus 7 back in for factory inspection/repairs, since it decides to reboot multiple times a day on its own. I had my N7 running CM w/ TWRP. I've flashed my device back to stock and everything, however it fails to boot up to the stock recovery. In it's stead I just get an Android man lying on his side open with a red exclamation in a triangle. I can't link the image directly, but http //i stack imgur com/kcSE4 jpg. Periods where there are spaces, except for right after the http, there is the usual colon.
I've tried running Restore Stock Recovery thru the Nexus Root Toolkit. I've tried manually flashing the recovery.img with fastboot flash recovery recovery.img while in the bootloader. I'm not sure what else to try. Is there anyone that could help me?
I get the recovery thing too and I've never installed a custom ROM or recovery (although I did flash twrp once but I did not install it) its not really a big deal for me be cause if I ever need a recovery I can flash one from my computer But I would like to know why this happens anyway.
Sent from my Nexus 7 using XDA Premium 4 mobile app
mugzylol said:
I get the recovery thing too and I've never installed a custom ROM or recovery (although I did flash twrp once but I did not install it) its not really a big deal for me be cause if I ever need a recovery I can flash one from my computer But I would like to know why this happens anyway.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm just primarily afraid that my warranty would be voided if they discovered that the recovery was missing. I can flash
TWRP back just fine, but not stock.
EDIT: Never mind. I apologize for my ignorance. I found out that you go to the recovery menu from that screen by holding the Power button and then pressing the Vol Up button. No more assistance shall be needed.
Yoou are saying that after flashing stock recovery you see a android with open stomach and exclamination mark
But android with open stomach and exclamination mark showing in recovery means it is stock recovery of nexus 7
I have a nexus 7
When it was not rooted i tried to boot to recovery i got the same
After rooting i get twrp in recovery
Sent from my Nexus 7
Hello everyone,
Tonight I finally took up the task of rooting my Nexus 7 (2013). After I unlocked the bootloader I went to flash twrp as a custom recovery. After I did that the tablet is now stuck on the teamwin logo. The logo appears for 5 seconds, the screen flashes, and then it does it again. The tablet won't accept any commands from the computer and I'm just super worried that I messed up big and that it might be bricked. I followed the video XDA put up and downloaded the files linked. This is my first root and I have no idea what to do. Thanks everyone
joshjovovich said:
Hello everyone,
Tonight I finally took up the task of rooting my Nexus 7 (2013). After I unlocked the bootloader I went to flash twrp as a custom recovery. After I did that the tablet is now stuck on the teamwin logo. The logo appears for 5 seconds, the screen flashes, and then it does it again. The tablet won't accept any commands from the computer and I'm just super worried that I messed up big and that it might be bricked. I followed the video XDA put up and downloaded the files linked. This is my first root and I have no idea what to do. Thanks everyone
Click to expand...
Click to collapse
I have now found that the tablet is in a recovery boot loop because I likely installed the wrong recovery for the device. It is running Android 5.0.2
joshjovovich said:
I have now found that the tablet is in a recovery boot loop because I likely installed the wrong recovery for the device. It is running Android 5.0.2
Click to expand...
Click to collapse
Sorry I forgot one more thing. When I connect the device to the computer it doesn't show up so I can't give it commands through command prompt. All I can do is be in the main bootloader screen and if I try to go into Recovery Mode or Start the tablet enters the loop with the teamwin logo flashing over and over again.
joshjovovich said:
Sorry I forgot one more thing. When I connect the device to the computer it doesn't show up so I can't give it commands through command prompt. All I can do is be in the main bootloader screen and if I try to go into Recovery Mode or Start the tablet enters the loop with the teamwin logo flashing over and over again.
Click to expand...
Click to collapse
If you can go into the Bootloader, did you try to flash the correct recovery or your stock recovery?
and what happens if you boot the tablet to the system (not recovery)?
@AbyssBreak Sorry, I forgot to put an update out last night. I did download the stock files from google which contained the boot loader and recovery image. I used the command "adb devices" in command prompt and it showed up blank. I decided to just try to flash the stock recovery so I placed the recovery image in the the platform-tools folder of android SDK and it managed to flash it to the device. Turned the tablet off and it started up like normal again. Quite a relief :laugh: Left the boot loader unlocked in case some time I do want to try again.
joshjovovich said:
@AbyssBreak Sorry, I forgot to put an update out last night. I did download the stock files from google which contained the boot loader and recovery image. I used the command "adb devices" in command prompt and it showed up blank. I decided to just try to flash the stock recovery so I placed the recovery image in the the platform-tools folder of android SDK and it managed to flash it to the device. Turned the tablet off and it started up like normal again. Quite a relief :laugh: Left the boot loader unlocked in case some time I do want to try again.
Click to expand...
Click to collapse
If you want to try again then try to usw the Nexus Root Toolkit from WugFresh, its the easiest way to root your device. :good:
11_SHOOTER_11 said:
If you want to try again then try to usw the Nexus Root Toolkit from WugFresh, its the easiest way to root your device. :good:
Click to expand...
Click to collapse
Okay. I will be rooting it once I come back from a road trip. Thanks for the tip! Are you sure that The Nexus Toolkit supports Android 5.0.2? I haven't found anything that does. Chainfire's CF Auto Root doesn't support anything above Android 5.0. Same with Towelroot from geohot. @11_SHOOTER_11
Sent from my Nexus 7 using XDA Free mobile app
joshjovovich said:
Okay. I will be rooting it once I come back from a road trip. Thanks for the tip! Are you sure that The Nexus Toolkit supports Android 5.0.2? I haven't found anything that does. Chainfire's CF Auto Root doesn't support anything above Android 5.0. Same with Towelroot from geohot. @11_SHOOTER_11
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
A definite yes on Nexus Root Toolkit supporting Android 5.0.2, at least in the latest version (2.0.4) - I used it today to get the latest TWRP installed on my own Nexus 7 (2013).
joshjovovich said:
@AbyssBreak Sorry, I forgot to put an update out last night. I did download the stock files from google which contained the boot loader and recovery image. I used the command "adb devices" in command prompt and it showed up blank. I decided to just try to flash the stock recovery so I placed the recovery image in the the platform-tools folder of android SDK and it managed to flash it to the device. Turned the tablet off and it started up like normal again. Quite a relief [emoji23] Left the boot loader unlocked in case some time I do want to try again.
Click to expand...
Click to collapse
When did you try adb devices? While in the bootloader? Or in recovery? Trying adb devices while in bootloader will not work, much like fastboot devices won't work when in recovery or in the Android system.
computerslayer said:
A definite yes on Nexus Root Toolkit supporting Android 5.0.2, at least in the latest version (2.0.4) - I used it today to get the latest TWRP installed on my own Nexus 7 (2013).
Click to expand...
Click to collapse
Okay. Good to know. Once I root my Nexus 7 one of the things I wanted to do was overclock the CPU. Would you know if that is safe with this device and if so what should I set the maximum frequency to?
nhizzat said:
When did you try adb devices? While in the bootloader? Or in recovery? Trying adb devices while in bootloader will not work, much like fastboot devices won't work when in recovery or in the Android system.
Click to expand...
Click to collapse
I tried it while in the boot loader. Since I flashed the wrong recovery I could not access the recovery.
joshjovovich said:
I tried it while in the boot loader. Since I flashed the wrong recovery I could not access the recovery.
Click to expand...
Click to collapse
Adb devices will never work in bootloader. Try fastboot devices in bootloader.