Hello everyone.
I was wondering if it would be possible to root my galaxy nexus using my tablet, which is 2013 version nexus 7, running none other than 4.3. I have an otg cable and keyboard and all the equipment I think I would need. Would I be able to root my phone or any other phones/ unlock them or unlock the bootloaders? I have a great terminal app that I would most likely need. Please tell me all that i would need to do different than on another computer including Fastboot and ADB, as well as drivers.
Gorantheg said:
Hello everyone.
I was wondering if it would be possible to root my galaxy nexus using my tablet, which is 2013 version nexus 7, running none other than 4.3. I have an otg cable and keyboard and all the equipment I think I would need. Would I be able to root my phone or any other phones/ unlock them or unlock the bootloaders? I have a great terminal app that I would most likely need. Please tell me all that i would need to do different than on another computer including Fastboot and ADB, as well as drivers.
Click to expand...
Click to collapse
There was a way to setup adb and fastboot on Android devices a while back. Not sure if it was kept up to date and still works. But if it does then yes you can use a tablet to root your device.
Anyone know how to do this. Can i run ADB and Fastboot in any way on my nexus 7?
Gorantheg said:
Anyone know how to do this. Can i run ADB and Fastboot in any way on my nexus 7?
Click to expand...
Click to collapse
Searching is difficult
cupfulloflol said:
Searching is difficult
Click to expand...
Click to collapse
That one is out of date. I guess i should make a request on an updated version of that, since i am mostly just a noob compared to the rest of all you guys.
Related
I can't seem to get this to work. I'm trying to unlock my phone using the nexus toolkit but when I put my phone into fastboot mode and click the unlock option on the toolkit I just get '< waiting for device >'. Every video I watch just shows them plugging the phone in and then having the program unlock it for them. It's not doing the same for me. Any suggestions?
Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.
063_XOBX said:
Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.
Click to expand...
Click to collapse
Every guide and video I find uses that method. Do you have a link to the other method?
http://forum.xda-developers.com/showthread.php?t=1529058
063_XOBX said:
http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
I still get the 'waiting for device' when I do it this way too. I have the most current samsung drivers. I also did everything to set up ADB.
uninstall the drivers and reinstall using the naked drivers.
So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
jahames said:
So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
Click to expand...
Click to collapse
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart
StuMcBill said:
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart
Click to expand...
Click to collapse
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
jahames said:
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
Click to expand...
Click to collapse
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?
StuMcBill said:
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?
Click to expand...
Click to collapse
Was working with the 4.4.2 image. Going to give the 4.4 a shot now
Same thing with 4.4...still stuck with the flo bootloader
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
jahames said:
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
Click to expand...
Click to collapse
You flashed a recovery for flo. Flash one for deb.
Edit:
http://techerrata.com/browse/twrp2/deb
Reasonably sure I had a deb recovery, but apparently redownloading and reflashing the CWM image did the trick. Thanks!
if you ever have problems try nexus root toolkit. It works wonders if you ever severely mess up any nexus device.
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
same issue
Richieboy67 said:
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
It is here
http://www.wugfresh.com/
It is a toolkit that makes these things very easy. I have used this many times and have never had any issues with it.
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
LinearEquation said:
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Richieboy67 said:
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Click to expand...
Click to collapse
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
LinearEquation said:
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
Click to expand...
Click to collapse
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Richieboy67 said:
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Click to expand...
Click to collapse
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
LinearEquation said:
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
Click to expand...
Click to collapse
While not disastrous, I kind of know what you mean, I started with Wug's (and it is a great toolkit), but once I flashed my own kernel (I used francos app to autoflash so did not have to use recovery or fastboot), I did not realize that by using Wug's a week later that it would flash over that kernel to run those commands and NOT replace francos (I found I was back on stock), lucky by then I had learned enough to recover and no damage was done, but it does point out that my reliance had caused me more work and a bit of worry in the long run.
Still Wug's NRT is a great toolkit...but it should be used as a tool, not a replacement for knowing what to do without it.
Hi All
having a problem here, windows 7 detect my phone, but in Hansoon 2000 and launch the cmd Getvar All, cmd unable to detect my phone
FYI my phone was already rooted and s-off, i totally forget how i did it
Reason to use Hansoon 2000 is because i had downloaded the official Lollipop update (1.44GB Asia) but have no means and ways to flash it even with twrp build in.
There is not supersu and does not seems root after i have **** up the OS.
Hope anyone here can guide me step by step, i getting confuse after looking for information on google and on XDA forums
Regards
Andy
cosmickiller said:
Hi All
having a problem here, windows 7 detect my phone, but in Hansoon 2000 and launch the cmd Getvar All, cmd unable to detect my phone
FYI my phone was already rooted and s-off, i totally forget how i did it
Reason to use Hansoon 2000 is because i had downloaded the official Lollipop update (1.44GB Asia) but have no means and ways to flash it even with twrp build in.
There is not supersu and does not seems root after i have **** up the OS.
Hope anyone here can guide me step by step, i getting confuse after looking for information on google and on XDA forums
Regards
Andy
Click to expand...
Click to collapse
i can help you over teamviewer just pm me.
cosmickiller said:
Hi All
having a problem here, windows 7 detect my phone, but in Hansoon 2000 and launch the cmd Getvar All, cmd unable to detect my phone
FYI my phone was already rooted and s-off, i totally forget how i did it
Reason to use Hansoon 2000 is because i had downloaded the official Lollipop update (1.44GB Asia) but have no means and ways to flash it even with twrp build in.
There is not supersu and does not seems root after i have **** up the OS.
Hope anyone here can guide me step by step, i getting confuse after looking for information on google and on XDA forums
Regards
Andy
Click to expand...
Click to collapse
You shouldn't use toolkits. Are you s-off?
Yes S-off
xunholyx said:
You shouldn't use toolkits.
Click to expand...
Click to collapse
Agreed. Why use a toolkit for what is accomplished with a single adb command? Toolkit just adds unnecessary complexity, and another point of potential failure.
Is the phone in recovery or booted into OS? getvar is an adb command, and adb only works under those conditions. Also, adb needs to be activated in the phone's settings.
question is pretty simple. i have used this software before to root my devices (galaxy ace,fit) and it works good.
oneclickroot.com
i am wondering if it will work on my nexus 7 2013 tablet. has anybody tried it?
i prefer it because its easy just 1 click.
i only want to root my device to use applications and have no intentions of using custom roms so do i have to unlock the boot loader?
thank you.
raghubabu1961 said:
i only want to root my device to use applications and have no intentions of using custom roms so do i have to unlock the boot loader?
Click to expand...
Click to collapse
Hi!
Yes, you need to unlock the bootloader before rooting your tablet.
Use NRT - is a simplest way.
Hey guys, coming from a Nexus device and thinking about getting either the OnePlus 3t or the new 5, and I was wondering, for fastboot mode to work correctly, do I use google's usb driver from the sdk or do OnePlus devices have their own driver I need from somewhere else? Thanks and sorry for the quick noob question, I'm coming from a Nexus so it's a little different.
H4X0R46 said:
Hey guys, coming from a Nexus device and thinking about getting either the OnePlus 3t or the new 5, and I was wondering, for fastboot mode to work correctly, do I use google's usb driver from the sdk or do OnePlus devices have their own driver I need from somewhere else? Thanks and sorry for the quick noob question, I'm coming from a Nexus so it's a little different.
Click to expand...
Click to collapse
I just use the regular minimal adb drivers that you can get from here on XDA
H4X0R46 said:
Hey guys, coming from a Nexus device and thinking about getting either the OnePlus 3t or the new 5, and I was wondering, for fastboot mode to work correctly, do I use google's usb driver from the sdk or do OnePlus devices have their own driver I need from somewhere else? Thanks and sorry for the quick noob question, I'm coming from a Nexus so it's a little different.
Click to expand...
Click to collapse
The drivers you have for Nexus devices should work fine with the OnePlus 3(T). I tested it myself, I don't need to switch drivers after getting the OP3, Fastboot detects it just fine with the old driver I had for Nexus 6P.
F4uzan said:
The drivers you have for Nexus devices should work fine with the OnePlus 3(T). I tested it myself, I don't need to switch drivers after getting the OP3, Fastboot detects it just fine with the old driver I had for Nexus 6P.
Click to expand...
Click to collapse
Awesome thanks! I hope to get the 5 when it releases! Those Pixel phones are just....... bleh. One more quick question, what is firmware all about? On a Nexus, you never had to worry about it at all for some reason, I notice with OnePlus devices, a lot of the rom threads say "make sure you have the newest firmware installed" and it's something I never had to mess with before. Thanks for all your help guys! Much appreciated!
With each OOS release there is a Firmware integrated, and if you switch to a custom ROM the firmware will not get updated so you need to flash it manually (there is a thread with all firmwares collected).
PlayingLikeAGenius said:
With each OOS release there is a Firmware integrated, and if you switch to a custom ROM the firmware will not get updated so you need to flash it manually (there is a thread with all firmwares collected).
Click to expand...
Click to collapse
So simply put, just keep it updated yeah? Is there any harm in flashing a newer rom and keeping an outdated firmware?
I don't think it is a problem but the devs often test their rooms with the newest that's why they say you should use the newest, because they know it works
PlayingLikeAGenius said:
I don't think it is a problem but the devs often test their rooms with the newest that's why they say you should use the newest, because they know it works
Click to expand...
Click to collapse
Awesome! Thanks for the reply! Hopefully will be getting my hands on the 5!
H4X0R46 said:
Awesome! Thanks for the reply! Hopefully will be getting my hands on the 5!
Click to expand...
Click to collapse
Drivers: The OP3 when connected to the PC/Laptop creates a CD drive on the PC/Laptop. It contains all the drivers you need for adb to work. As Puddi Puddin said, the minimal drivers themselves work, the CD drive is there just in case you need it.
Firmware: Some custom ROMs refuse to work without the firmware recommended for it. So just go by the recommendations of the developer and remember to check the firmware when you change/update the ROM.
tnsmani said:
Drivers: The OP3 when connected to the PC/Laptop creates a CD drive on the PC/Laptop. It contains all the drivers you need for adb to work. As Puddi Puddin said, the minimal drivers themselves work, the CD drive is there just in case you need it.
Firmware: Some custom ROMs refuse to work without the firmware recommended for it. So just go by the recommendations of the developer and remember to check the firmware when you change/update the ROM.
Click to expand...
Click to collapse
Cool, to change the firmware, is it an img you flash with fastboot? What's the file name and command?
H4X0R46 said:
Cool, to change the firmware, is it an img you flash with fastboot? What's the file name and command?
Click to expand...
Click to collapse
It is a zip file. Check the thread for Collection of Firmware and Modems by Jamal (for OP3) here in XDA.
tnsmani said:
It is a zip file. Check the thread for Collection of Firmware and Modems by Jamal (for OP3) here in XDA.
Click to expand...
Click to collapse
Awesome thanks! Getting used to the way these phones work lol thanks a million!