Related
Hey guys,
I recently switched from an iPhone 4 to the G Note. Am a total Android noob. I have been checking out a lot of threads in XDA and all the ones about rooting say that it can only be done in Windows. I have a Mac and I have no access to a windows machine(no bootcamp) other than a Virtual Windows Machine in parallels. Is it possible to root the G Note from a virtual machine? Is it safe? Anyone done it before?? Please help
I have read couple of review who are on virtual machine, but unfortunately they didn't succeed....
itismadhan said:
Hey guys,
I recently switched from an iPhone 4 to the G Note. Am a total Android noob. I have been checking out a lot of threads in XDA and all the ones about rooting say that it can only be done in Windows. I have a Mac and I have no access to a windows machine(no bootcamp) other than a Virtual Windows Machine in parallels. Is it possible to root the G Note from a virtual machine? Is it safe? Anyone done it before?? Please help
Click to expand...
Click to collapse
As long as your machine supports hardware virtualization, which is to say that your VM can directly access your hardware, like USB ports etc. then you should be fine. In other words, if when you plug in your Note, and your VM detects new hardware and starts installing the drivers, and you're able to open ADB to your device successfully, then you're good to go.
Read this, super one click also support root galaxy note
http://forum.xda-developers.com/showthread.php?t=803682
Which have mac support
Thanks Dr.Ketan and Jade Eye Wolf. I am now stuck between a rock and a hard place! Btw, Dr.Ketan that link you gave me doesn't have G Note on their supported list. Also can I do CWM after rooting from Super One click?
Latest version of superclick have zergrush exploit added, same as only available root method for note. Yes you can use cwm after root, but no idea abt how to do on mac
Hey Guys just wanted to let y'all know that I did Root my G Note from a Virtual Machine using Dr.Ketan's methon(Root + CWM) and Its fine!!! Thanks to all! Dr.Ketan esp
Hello forums!
Well, this my be a noob-like question, or not, I have no idea. So, here it goes...
My Sony Xperia T does not want to be rooted no matter what method I use. Bootlocker unlock is not allowed, but I have seen many root when they have this too, so it's not that causing the problem.
I used DoomLord's rooting toolkit first of all, to be told by the application that my phone LT30p is not accepted, even though the root includes that phone...
I then used Bin4ry's root with restore, and once again, that didn't work. I was taken to the service menu and had to click on Display, but that didn't work. The rooting toolkit just didn't do anything, just sat there...
Then I tried SRS Root, and that didn't work either.
I have PC companion, and I have USB Debugging and Unknown sources all enabled AND I have the ADB drivers... what is the problem!
This has been bugging me for a long time, I could do with some help!
Thanks in advance,
Joe.
Install ADB Driver first -_-
What is your OS on PC ?
Yenkazu said:
Install ADB Driver first -_-
What is your OS on PC ?
Click to expand...
Click to collapse
Yeah I have installed the ADB Driver, and I am running Windows 8.
CommandoOS said:
Yeah I have installed the ADB Driver, and I am running Windows 8.
Click to expand...
Click to collapse
Known issue, ADB driver cannot working under Windows 8
Just switch to older OS
Or find another PC without Windows 8 inside
XD
Yenkazu said:
Known issue, ADB driver cannot working under Windows 8
Just switch to older OS
Or find another PC without Windows 8 inside
XD
Click to expand...
Click to collapse
Aweeeeesome!
Thanks man, let me go test this on my laptop!
Okay, new problem. On my laptop, I have installed PC Companion, the device drivers have installed but now, when I try to add adb drivers it will not let me, and when I use the ADB Installer, it is not recognizing my device.
CommandoOS said:
Okay, new problem. On my laptop, I have installed PC Companion, the device drivers have installed but now, when I try to add adb drivers it will not let me, and when I use the ADB Installer, it is not recognizing my device.
Click to expand...
Click to collapse
Try disable any antivirus or similar program like that
Don't use non specific ADB driver
I guess, installing PCC it's enough
Btw, I never use any Sony software now
The best ADB driver you can find, by using ADB driver from flashtool
XD
Okay well, I got the drivers working (thanks to you) but...
dom...dom. doooooooooooom!
Still not working. For example, when using Bin4ry's root, I get to the part where you have to sit on service tests>display and nothing happens, and after about 10 minutes, it simply says root failed in console, but device does restart, but is not rooted.
CommandoOS said:
Okay well, I got the drivers working (thanks to you) but...
dom...dom. doooooooooooom!
Still not working. For example, when using Bin4ry's root, I get to the part where you have to sit on service tests>display and nothing happens, and after about 10 minutes, it simply says root failed in console, but device does restart, but is not rooted.
Click to expand...
Click to collapse
I had same problem as you
I installed flashtool then installed all driver, and i used the root thing on flashtool and it worked perfectly
CommandoOS said:
Okay well, I got the drivers working (thanks to you) but...
dom...dom. doooooooooooom!
Still not working. For example, when using Bin4ry's root, I get to the part where you have to sit on service tests>display and nothing happens, and after about 10 minutes, it simply says root failed in console, but device does restart, but is not rooted.
Click to expand...
Click to collapse
Don't use Binary method
Using Doomlord easy root
What the Build number your current OS ?
Yeah I have tried that, even though it clearly says that the Xperia T can be used with it:
Hi, I recently got a Xperia T and couldn't get it to root.
After messing around I finally got it to Root. What I had to do was use Bin4ry's root method first choosing option 2.
Once that was done, I then had to use Doomlord's easy root. After that was done I ran SU which deleted the version from Bin4ry's root and success, my phone was rooted.
I don't know why I have to use Bin4ry's method and the Dommlord's but I do know the only way to get my phone to root is by doing both root methods starting with Bin4ry's first.
I know for a fact this is the case because I re-flashed my phone to stock, trying different methods, in different orders. The only way to get it to root was to do Bin4ry's and then Doomlord's one after the other.
Tried it, it didn't work for me Thanks anyway dude.
CommandoOS said:
Tried it, it didn't work for me Thanks anyway dude.
Click to expand...
Click to collapse
Sorry Mate
Just use this
http://forum.xda-developers.com/showthread.php?t=2378400
I already am running that firmware?
CommandoOS said:
I already am running that firmware?
Click to expand...
Click to collapse
It's a little different
Already rooted
=)
Just find what suitable for you
Odexed or Deodexed
How do I add it. I am new to this, I understand I must seem like a noob but I guess everyone has to start somewhere.
Could you please tell me how I can add it safely?
CommandoOS said:
How do I add it. I am new to this, I understand I must seem like a noob but I guess everyone has to start somewhere.
Could you please tell me how I can add it safely?
Click to expand...
Click to collapse
you must downgrade to JB firmware that can be rooted using Binary or Doomlord method
After that, root, install CWM for locked bootloader
Then, follow instruction from the OP ( link above )
Just Google if you need more information
Yes but how can I downgrade? What do I need to do? I have looked for tutorials, I can't seem to find any.
CommandoOS said:
Yes but how can I downgrade? What do I need to do? I have looked for tutorials, I can't seem to find any.
Click to expand...
Click to collapse
All in One Thread
Just find what info you need
http://forum.xda-developers.com/showthread.php?t=1903137
Q&A for [MOD]One Click Root and custom recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD]One Click Root and custom recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Droid 1 Rooting in 2015
I'm having issues rooting my completely stock Android 2.2.3 US Motorola Droid on Verizon with build FRK76 with baseband C_01.43.01P. I am running Windows 10 Tech Preview and Arch Linux, and can jump over to a Windows 8.1 machine if necessary. I have drivers and can see my droid in Device Manager as Android ADB Interface (with USB debugging on), Motorola A855 USB Device, and Motorola Flash Interface (in Bootloader).
I have rooted two more modern devices, but this one is escaping me.
Universal Androot, z4root, SuperOneClick, RSD Lite, and One Click Root are all failing for me. The methods that ship with adb.exe aren't seeing the phone when I run "adb devices":C:\...\Desktop\droid_oneclick>adb devices
List of devices attached
[nothing here but the next command prompt]
That makes me think there may be some compatibility issues with Windows 10, but still, the .apk's didn't work either, and it looks like I'm stuck.
Is there a well-defined method without broken links documented somewhere I just haven't seen yet? Are there 'bad drivers' out there preventing adb from seeing it or known incompatibilities between particular drivers and software? Have all the exploits been patched out of my phone?
Physicist1616 said:
I'm having issues rooting my completely stock Android 2.2.3 US Motorola Droid on Verizon...
Is there a well-defined method without broken links documented somewhere I just haven't seen yet?
Click to expand...
Click to collapse
Are there 'bad drivers' out there preventing adb from seeing it or known incompatibilities between particular drivers and software? Have all the exploits been patched out of my phone?
Click to expand...
Click to collapse
I found my answer to both points. This guide worked. I'm not allowed to post the guide link. Frustrating.
And to explain my ADB and RSDLite issues, it looks like the USB ports on the top of my computer count as a USB hub and these devices just don't see it.
Mods, or readers who see this post before mods, it's on droidforums dot net. The rest of the link is /threads/root-droid-1-regardless-of-os-version.74028/
Hey everyone,
So I bought the Blu R1 HD 16gb/2gb on amazon for 60 bucks, super stoked with its performance and look (although who can complain for the price of a family meal?).
My only problem is that I've been unable to root it. I know that I can easily root it with a computer, but for whatever reason my computer is unable to install any drivers for anything! Does anyone know of a rooting app that is compatible with the phone, or a way to root it with out a computer?
Please don't respond telling me how to install drivers, as I've tried everything; short of upgrading windows, that is.
P.S. Tried a bunch of apps already, none have supported rooting the R1 HD yet. I've tried kingo, king, towel, z4, and a bunch of others.
Thanks in advance!
Dude really? there is no other computer you could use to do it? your brother/sister father/mother some friend anything?... so sad
onlykhaz said:
Dude really? there is no other computer you could use to do it? your brother/sister father/mother some friend anything?... so sad
Click to expand...
Click to collapse
Yeah, they're all mac users, and android doesn't connect to it correctly.
ActuallyAFrog said:
Yeah, they're all mac users, and android doesn't connect to it correctly.
Click to expand...
Click to collapse
i dont (haven't anyway) use mac but @ColtonDRG , who does alot on this forum, uses MACos, so i do beleive there is support for mac
ActuallyAFrog said:
Hey everyone,
So I bought the Blu R1 HD 16gb/2gb on amazon for 60 bucks, super stoked with its performance and look (although who can complain for the price of a family meal?).
My only problem is that I've been unable to root it. I know that I can easily root it with a computer, but for whatever reason my computer is unable to install any drivers for anything! Does anyone know of a rooting app that is compatible with the phone, or a way to root it with out a computer?
Please don't respond telling me how to install drivers, as I've tried everything; short of upgrading windows, that is.
P.S. Tried a bunch of apps already, none have supported rooting the R1 HD yet. I've tried kingo, king, towel, z4, and a bunch of others.
Thanks in advance!
Click to expand...
Click to collapse
You're doing it wrong. We don't use ****ty rooting apps to root, we do it the RIGHT way. You have to install TWRP and flash SuperSU. You can do this the original way using SPFT, or the (more recommended) way of converting to OEM non-Prime, unlocking the bootloader, and using fastboot to flash TWRP.
ActuallyAFrog said:
Yeah, they're all mac users, and android doesn't connect to it correctly.
Click to expand...
Click to collapse
No. No. You could not be more wrong. Android connects to macOS MORE correctly than it connects to Windows. It doesn't even need any drivers! At Google, they don't use Windows, they use macOS and Linux. That said, we don't have any SPFT for Mac, unfortunately, but that's MediaTek's fault, and there's no reason you couldn't use a Linux live USB to do it.
mrmazak said:
i dont (haven't anyway) use mac but @ColtonDRG , who does alot on this forum, uses MACos, so i do beleive there is support for mac
Click to expand...
Click to collapse
I use macOS sometimes, yes, but there is no SPFT for it. I use Linux mostly.
ColtonDRG said:
No. No. You could not be more wrong. Android connects to macOS MORE correctly than it connects to Windows. It doesn't even need any drivers! .
Click to expand...
Click to collapse
Well @ColtonDRG I wasn't really saying that it won't work, I was saying they don't like me fiddling with their computers, cause as a kid I messed up some of their stuff, and they really haven't gotten over it yet.
But say I could use one, those things would be all to root it? I would just get the necessary programs, convert OEM to non-prime, unlock the bootloader (assuming mine is locked), flash TWRP, and then Super SU? I'd be done with it in an hour or two?
ActuallyAFrog said:
Well @ColtonDRG I wasn't really saying that it won't work, I was saying they don't like me fiddling with their computers, cause as a kid I messed up some of their stuff, and they really haven't gotten over it yet.
But say I could use one, those things would be all to root it? I would just get the necessary programs, convert OEM to non-prime, unlock the bootloader (assuming mine is locked), flash TWRP, and then Super SU? I'd be done with it in an hour or two?
Click to expand...
Click to collapse
You might need to convert your phone to the OEM non-Prime version first, but yes. There is no version of SPFT for macOS, so you'll need to use Windows or Linux for that, but the rest can be done on any OS. The whole process only takes me about 10 minutes, but if you don't know what you're doing, it would be reasonable to assume that you could do it in about a half an hour.
EDIT: Also my comment was in direct response to you saying:
"Yeah, they're all mac users, and android doesn't connect to it correctly."
Which implies that Macs cannot manipulate Android devices, which is simply not true.
ColtonDRG said:
You might need to convert your phone to the OEM non-Prime version first, but yes. There is no version of SPFT for macOS, so you'll need to use Windows or Linux for that, but the rest can be done on any OS. The whole process only takes me about 10 minutes, but if you don't know what you're doing, it would be reasonable to assume that you could do it in about a half an hour.
Click to expand...
Click to collapse
So I'll be good using only Mac as long as I don't need to switch my OEM?
ActuallyAFrog said:
So I'll be good using only Mac as long as I don't need to switch my OEM?
Click to expand...
Click to collapse
No. The Prime version of the phone requires SPFT to root, so you will need it either way. You can use SPFT to covert to the OEM version and then root using fastboot, or you can use SPFT to root the Prime version. I personally highly recommend converting.
Niki Kidman said:
Considering you had already cost "big money" to buy the root software. Maybe it's better for you to make good use of it... Try to change a computer...
Click to expand...
Click to collapse
Try Linux, I just got phone yesterday, rooted, unlocked bootloader, removed amazon stuff and compiled kernel.
Sent from my R1 HD using Tapatalk
vampirefo said:
Try Linux, I just got phone yesterday, rooted, unlocked bootloader, removed amazon stuff and compiled kernel.
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
It's been a long time since I rooted any phone or played around with adb or my linux mint (14). Would it be possible for you to tell me which guide you may have used for linux. I am using a windows 10 computer and cannot follow noob friendly guide for the life of me. My computer won't recognize the phone at all and I have disabled driver verification. Any help would be awesome.
Thanks
sid0101 said:
It's been a long time since I rooted any phone or played around with adb or my linux mint (14). Would it be possible for you to tell me which guide you may have used for linux. I am using a windows 10 computer and cannot follow noob friendly guide for the life of me. My computer won't recognize the phone at all and I have disabled driver verification. Any help would be awesome.
Thanks
Click to expand...
Click to collapse
I explained how I rooted in below post.
http://forum.xda-developers.com/showthread.php?p=68477232
If you can't follow it, then you need to stick with Windows method.
Sent from my R1 HD using Tapatalk
I used to run linux on my SM-T810 using Linux Deploy and after a lot of troubleshooting, got it to work. This was back during the 5.1.1 days. Now that I'm on 6.0.1, I tried to reinstall linux but I can't seem to find a way to enable loop device support nor find a kernel/ROM that supports it. Are there any that have loop device support? Otherwise are there any tutorials on customizing a kernel to do this?
I could not find one. If I am able to, I'am willing to compile one. I created the following thread:
http://forum.xda-developers.com/tab-s2/help/kernel-loop-device-support-t810-t3515588
In the mean time you could try if Termux or GNURoot Debian do what you need.